Tuesday 26 February 2019

SAPINST is not .exe file

Symptom:

You have downloaded the SWPM and extracted the .SAR file .

File got successfully extracted but the unable to launch sapinst.



Cause:

SWPM sar file might have got extracted ,but due to some issues ,it may not have got fully extracted or the downloaded SAR file will be having some issues.
The size of the sapinst file will be less.

Solution:

Download the latest version of the SWPM.

Extract the SWPM sar file again and check the size of the sapinst





Hope this helps!!!
Abraham


How to download the latest version of SAPHOSTAGENT

Download the latest version SAPHOSTAGENT from service marketplace.

https://launchpad.support.sap.com/#/softwarecenter

INSTALLATIONS & UPGRADES  -> A-Z Index -> H

SAP HOST AGENT -> <SELECT PLATFORM>  -> SAPHOSTAGENT_*.SAR


Hope this helps!!!
Abraham

Installation media of RDBMS HANA Client in SWPM

Steps to Download Installation Media of RDBMS HANA Client

Download

https://launchpad.support.sap.com/#/softwarecenter

Support Packages and Patches -> A-Z Index -> H

SAP HANA PLATFORM EDITION -> SAP HANA PLATFORM EDIT. 1. 0

HANA CLIENT -> SAP HANA CLIENT 1.0

<SELECT PLATFORM> -> IMDB_CLIENT100_*.SAR


Extracting the .SAR file

SAPCAR -xvf  IMDB_CLIENT100_*.SAR

The extracted files will be having a folder SAP_HANA_CLIENT which will be having LABEL.ASC file


Hope this helps!!!
Abraham

Wednesday 20 February 2019

How to extract the multipart Installation media of SAP in Linux

Symptom:

You have downloaded the installation media.
The media may conatin 2 or 3parts , which will be combination of .exe and .rar files

Solution:

1. Download the the required installation media from the service market place.

For Eg :

2. Move the file to your linux server .

3. Use the below command to extract the file.You need to give  the command only for the part-1 file.RAR will automatically extract the rest of the files also.

unrar x  <FILE_1>  <DESTINATION>



Hope this helps!!!
Abraham



How to Install and Use RAR on Linux.

Steps:

1. Go to   http://www.rarlab.com and dowload the latest RAR required for your system.

2. Untar the downloaded package using the below command :

tar -zxvf <downloaded_file>.gz

Eg: tar -zxvf rarlinux-x64-5.7.b1.tar.gz

A rar directory will be created which has the rar and unrar utilities.

3. Now copy the rar and unrar to the bin directory using the below commands

cd rar

cp rar unrar /bin

4. Now to extract the file , go to the location of the file to be extracted and use the below command:

unrar x <File to be unrar>  <Destination>


Hope this helps!!!
Abraham







Tuesday 19 February 2019

SAPCAR: Permission denied

Symptom:


When you are trying to extract a file using the SAPCAR utility in Linux , getting message as below:
SAPCAR: Permission denied

Solution:

Give the full permission to SAPCAR file using CHMOD command:

chmod 777 SAPCAR



Hope this helps!!!
Abraham

How to solve sapcar: command not found

Symptom:

You are trying to extract a file using SAPCAR with root user and you are getting the below message:

HDBTST:~/HDB_db # sapcar -xvf IMDB_SERVER100_122_23-70000762.SAR
If 'sapcar' is not a typo you can run the following command to lookup the package that contains the binary:
    command-not-found sapcar
-bash: sapcar: command not found



Solution:

Specify the location of the SAPCAR utility as below :

<SAPCAR utility location>/SAPCAR -xvf   <filename>.SAR


Hope this helps!!!
Abraham




Monday 18 February 2019

How to edit the parameters of Shadow Instance during Upgrade

Steps:

1. Go to the UPGRADE directory :

<Upgrade Directory>\SUM\abap\system\<SID>\SYS\profile

2. Here you can find the shadow system profiles.


Hope this helps!!!
Abraham

How to download latest version of SAPCAR

Steps:

1. https://launchpad.support.sap.com/#/softwarecenter

2. SUPPORT PACKAGES&PATCHES -> BY Alphabetical Index(A-Z) -> S ->SAPCAR

3.  Select the platform and download the latest version.

4. Rename the SAPCAR_xxxx_xxxx.EXE to just SAPCAR.exe

5. In case of windows copy the SAPCAR.exe file to C:\Windows\System32

6. Double click and run the SAPCAR.exe file

Hope this helps!!!
Abraham


Thursday 14 February 2019

How To Download Latest Vesrion of SUM

Steps:

1. Login to www.service.sap.com

2. Click on Visit the SAP Support Portal .


SAP SUM

3. Select Tools ->Software Logistics Tools.

4. Click on Learn more about Software Logistics Tool

5. Under system maintenance Download SUM.


Software Update Manager

Hope this helps!!!
Abraham

Monday 11 February 2019

BRTools errors occur when accessing "database" directory

Symptom:

Determination of file status for spfileGEP.ora failed

After you use the Database Upgrade Assistant (DBUA) to apply Oracle patch set, BRBACKUP and BRCONNECT fail and the system issues error messages such as:
BR0252E Function CreateFile() failed for 'E:\oracle\SID\12102\database\spfileSID.ora' at location BrFileStatGet-2
BR0253E errno 5: Access is denied.
BR0273E Determination of file status for E:\oracle\SID\12102\database\spfileSID.ora failed.


Solution:



You must change the access authorizations so that they do not apply only to the database directory, but to all database files and the spfile. To avoid a large amount of manual steps, in BRCONNECT 7.00 Patch 39 and BRCONNECT 7.10 Patch 19, the workaround option "-SFP" (set file permissions) is provided for the "check" function. You can use this to perform a BRCONNECT call under the user <SID>ADM to set all of the required access authorizations, for example:

brconnect -u / -c -f check -SFP

In the process, the access authorizations to the following directories and the subdirectories and files under them are modified:
%ORACLE_HOME%\database,
<X>:\oracle\<DBDID>\origlog
<X>:\oracle\<DBDID>\mirrlog
<X>:\oracle\<DBDID>\sapdata<N>
If the system issues any warnings about Windows groups that do not exist (for example, ora_oper), you can ignore these.


Hope this helps!!!
Abraham



ORA-01031: insufficient privileges during ACT_UPG phase in upgrade

Symptom:

During phase ACT_UPG in upgrade ORA-01031 occurs.
Runtime Errors         DBSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Parameters:
P1 "DDPRS"
P2 "SQL code: 1031"
P3 "SQL message: ORA-01031: insufficient privileges"
P4 "SQL dbsl rc: 99"

Troubleshooting:

1. Check in ST22 in shadow instance, if any related runtime errors has occured.
2. From the run time error we can see the table having issues.
3. Also check the work process associated.
4. From St11 check the concerned workprocess trace.

ORA-1031 insufficient Privileges

Solution:

1. In ACT_UPG  phase if this issue occurs check roles assigned to SAPSR3 and SAPSR3SHD users:


SQL>Select grantee,granted_role from dba_role_privs where grantee =’SAPSR3’;


SQL>Select grantee,granted_role from dba_role_privs where grantee =’SAPSR3SHD’;

SAP DBA AND SAPCONN  role should be assigned .

Refere notes : 

134592 - Import of SAPDBA role (sapdba_role.sql)


834917 - Implementation of SAPCONN role (sapconn_role.sql)





2. If still the issue is not solved , grant permission on the table as below :

grant select, insert, update, delete on sapsr3.<Table> to SAPSR3;
grant select, insert, update, delete on sapsr3.<Table> to SAPSR3SHD;
grant select, insert, update, delete on sapsr3SHD.<Table> to SAPSR3SHD;
grant select, insert, update, delete on sapsr3shd.<Table> to SAPSR3;



Hope this helps!!!
Abraham

Tuesday 5 February 2019

Error in phases MAIN_SWITCH/JOB_RSVBCHCK2 or Checks after phase MAIN_INIT/JOB_RSVBCHCK* were negative

Symptom:

Error in phases MAIN_SWITCH/JOB_RSVBCHCK2 or MAIN_SWITCH/JOB_RSVBCHCK_D; Checks after phase MAIN_INIT/JOB_RSVBCHCK* were negative.

Cause:

1. The update requests have been canceled, but entries in tables related to the update process are not     empty and these tables must be empty during upgrade process.
2. Outstanding update requests (visible in transaction code SM13) and queued RFCs (visible with transaction code SMQ1) exist in the system.

Solution:

Scenario A: Error

Batchjob RSVBCHCK failed. 
Detected the following errors due to error summary in /<SUM_Directory/abap/log/PSVBCHCK.ELG:

1 ETH010XRSVBCHCK: Check of open update requests
2EETG050 Update records still exist - Please process

In Log file: PSVBCHCK.ELG

1 ETH010XRSVBCHCK: Check of open update requests
2EETG050 Update records still exist - Please process

Scenario B: Error

Batchjob RSVBCHCK failed. 
Detected the following errors due to error summary in ../SUM/abap/log/PSVBCHCK.ELG:

1 ETH010XRSVBCHCK: Check of open update requests

A2EEMCEX 151 Entries for application "xx" still exist in the extraction queue ->
Log file: PSVBCHCK.ELG
1 ETH010XRSVBCHCK: Check of open update requests

A2EEMCEX 151 Entries for application "xx" still exist in the extraction queue ->

Scenario C: Error

Batchjob RSVBCHCK failed. 
Detected the following errors due to error summary in /SUM_Directory/abap/log/PSVBCHCK.ELG:

1 ETH010XRSVBCHCK: Check of open update requests
2EETG050 Update records still exist - Please process

A2EEMCEX 151 Entries for application "xx" still exist in the extraction queue ->

In Log file: PSVBCHCK.ELG

1 ETH010XRSVBCHCK: Check of open update requests
2EETG050 Update records still exist - Please process

A2EEMCEX 151 Entries for application "xx" still exist in the extraction queue ->

Scenario A: Solution

Make sure that you have cleaned up all outstanding updates.

To find terminated or unresolved updates, proceed as follows:

Call transaction SM13.
Delete the default values for the client, user, and time.
Select all the update requests and clear them.
Use the delete/reorg functionality of the update report RSM13001 or RSM13002 as described on the WIKI page Reports RSM13001 and RSM1300

Scenario B: Solution

Please follow the steps described in the SAP Note 1083709 according to the reported error message A2EEMCEX 140 , A2EEMCEX 141, A2EEMCEX 149 or A2EEMCEX 151. 
See also the SAP Note  328181 
To be able to logon to each listed client, please unlock the system first and then logon. (see also the SAP KBA 1901463)
Make sure that you lock the system back after you executed the steps and then continue with the upgrade.

Scenario C:Solution

Execute the steps described in Scenario A   AND   in Scenario B.

Hope this helps!!!
Abraham


PREP_INIT/DB2_CHECKNOTES_INI failed

Symptom:

SUM phase fails at PREP_INIT/DB2_CHECKNOTES_IN.
Continue with phase PREP_INIT/DBCHK_INI



Solution:

1. Check the log files Checks.txt and Checks.log files.


2. In this case the issue was missing due to the missing DBA tools.

3. Download the required version of DBA tool (DBATL740O11_35-80000794.SAR)  to the exe folder in SUM directory . (Eg - <SUM_diectory>\abap\exe)

4. Repeat the phase, issue will be solved.

Refer Note : 2337629 - Replacement of target release kernel for upgrade/EHPI

https://launchpad.support.sap.com/#/notes/2337629






Hope this helps!!!
Abraham


Monday 4 February 2019

PREP_EXTENSION/CONFLICT_CHECK running for a long time

Symptom:

SUM phase:Configuration/PREP_EXTENSION/CONFLICT_CHECK running for a very long time.

Log file location: <SUM directory>\SUM\abap\log\CONFLCHK.LOG

Example log file entries ,you can see hanging at:

3 ETQ399 "SAPK-60779INEAHR","894","CSP","EA-HR","607","EA-HR 607: SP 0079","01"
3 ETQ399 "SAPKE604C9","895","CSP","SAP_HR","604","SP C9 for SAP_HR 604","01"
3 ETQ399 "SAPK-60780INEAHR","896","CSP","EA-HR","607","EA-HR 607: SP 0080","01"

Solution:

Run statistics for below tables using T-code DB20 or via Se38 using RSANAORA

Tables:

TADIR
TFDIR
SMODILOG
VRSD
E070
DOKIL
E071
OCSCMPLOBJ

If the number of entries in the above tables are ,more it will take more time.


Hope this helps!!!
Abraham

PREP_INPUT/DBQUERY_PRE - Error

Symptom:

SUM phase PREP_INPUT/DBQUERY_PRE  fails.
ERROR: Password for 'SYSTEM' does not work, please reenter.
Error while trying to retrieve text for error ORA-12557
BR0310E Connect to database instance <SID> failed

Solution:

1. Reset the upgrade.

2. Update the oracle instant client by following the below notes :

819829 - Oracle Instant Client Installation and Configuration on Unix or Linux
998004 Update the Oracle Instant Client on Windows

3. Start the upgrade again.

Hope this helps!!!
Abraham


Syntax error in program "SAPLSUG2 " during Upgrade

Symptom:

Runtime Errors         SYNTAX_ERROR
Date and Time          05/08/2015 10:57:09


Short text
Syntax error in program "SAPLSUG2 ".

What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLFSBP_SWITCH_USAGE" had to be terminated becauseit has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLSUG2 " in include "LSUG2U04" in
line 71: "Field "GC_RELEASE_UNKNOWN" is unknown. It is neither in one of the spe"
"cified tables nor defined by a "DATA" statement. "DATA" statement."

Solution:

1.  Reset the current run of upgrade. Implement SAP Note 1766587 and 1768517 and then restart the SUM from scratch.

2. A workaround is:

Modify the Include RSUGSINC:
replace line 31 in RSUGSINC (which is currently an empty line) with

DATA: GC_RELEASE_UNKNOWN      LIKE CVERS-RELEASE   VALUE '???'.
You will need to provide a Developer key for this, as it is considered a modification.

If the object shows up in SPAU later please choose "return to SAP standard" to process the object.




Hope this helps!!!
Abraham



Upgrade Still Running,Logon not possible

Symptom:

When trying to login to shadow instance with user other than DDIC , message shown as  "Upgrade Still Running,Logon Not Possible"

Solution :

1. To unlock the SAP system, enter the following commands. 

The system may be either the original SAP system or the shadow system, depending on which one the error occurred.

Original SAP system
cd /<update directory>/abap/bin
./SAPup unlocksys

Shadow system
cd /<update directory>/abap/bin
SAPup unlockshd


2. To lock the original SAP system or shadow system again, enter the following commands:

Original SAP system
cd /<update directory>/abap/bin
./SAPup locksys

Shadow system
cd /<update directory>/abap/bin
SAPup lockshd

Refer Note : 1901463 - How to unlock the SAP system to perform correction(s) during an upgrade


Still if the issue is not solved , perform the following steps :

E:\>tp unlocksys GEP pf=E:\Upgrade\SUM\abap\var\DEFAULT.TPP

Wait for approximately 5 mins and then execute below also:

E:\>E:\Upgrade\SUM\abap\bin\SAPup unlockshd GEP

Wait for another 5 minutes and try logging in to the system.

Hope this helps!!!
Abraham