Monday, 11 February 2019

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