Symptom

Could not execute 'EXPORT REORG_LOCATIONS_EXPORT AS CSV INTO '/tmp'' SAP DBTech JDBC: [258]: insufficient privilege: Not authorized

Solution

Execute with the same schema user and grant EXPORT in system privilege 

Hope this helps!!!

Abraham

Grant select privilege on table in sys schema

Symptom

SAP DBTech JDBC: [259]: invalid table name: REORG_PLAN_EXPORT: line 1 col 12 (at pos 11)

Could not execute 'CREATE TABLE REORG_PLAN_EXPORT AS (SELECT * FROM SYS.REORG_PLAN_)'

SAP DBTech JDBC: [258]: insufficient privilege: Not authorized

Solution

You need select authorization on schema SYS in order to execute this.

If you want to grant select access on SYS schema then you can grant SAP_INTERNAL_HANA_SUPPORT role to the user

How to check GPFS file systems logs

1.How to check  GPFS file systems logs

1. Go to path /var/ad/ras
2. ls -latr|grep mmfs
3. You will find the below files :

mmfs.log.previous
mmfs.log.latest

2. Start the GPFS file system:

Command :mmsatrtup

3. To identify which nodes in the cluster have daemons up or down, issue:

mmgetstate -L -a

Hope this helps!!!

Abraham

Copy User Variants for Table Controls

Symptom

You want to copy a variant created by 1 user to other users.

Solution 

1. Use program RSTCX_COPY_TCVARIANT.

2. In se38 execute the program .

3. Provide the input details :

Program name : Program name of the t-code in which you want to set the variant

User : User who created the variant

Variant Name: name of the variant to be assigned

For User : List of users to whom variant has to be copied

Hope this helps!!!

Abraham

How do you cancel a running backup in HANA

To cancel a running backup, please use the following 3 SQL statements in HANA studio:

1. Get the backup_id of your running backup:

select BACKUP_ID from "SYS"."M_BACKUP_CATALOG" where entry_type_name = 'complete data backup' and state_name = 'running'  order by sys_start_time desc

2. Cancel the backup

backup cancel <backup_id>

3. Confirm the backup has cancelled

select state_name from "SYS"."M_BACKUP_CATALOG" where backup_id = <backup_id>

4. Check to  make sure there are no running backups still

select * from  "SYS"."M_BACKUP_CATALOG" where STATE_NAME = 'running';

If the backup still exists, you can try to cancel the thread through the commands:

ALTER SYSTEM CANCEL SESSION <Session_ID> ;

ALTER SYSTEM DISCONNECT SESSION <Session_ID> ;

From backend Linux

1. As per the SAP Note 2452735 confirm there are no backup currently running.

select * from "SYS"."M_BACKUP_CATALOG" where STATE_NAME = 'running';

2. Run the ps command to get the listing of zombie hdbbackint processes belonging to the database backup

ps -ef | grep hdbbackint | grep COMPLETE

Sending signal 9 using the "kill" command will destroy the process running on the client. 

kill -9 PID

where PID is the process id of the zombie hdbbackint process. 

You will need to be a root user to execute the kill command

Include authorization profile in a role

Steps how to include a authorization profile in a role.

1. T-code PFCG --->Give Role Name --->Eg: TEST_SAP_ALL
2. Create as single role .

3. Provide a description and Click on Authorization TAB

4. Save Now Yes

5. Click on Change Authorization Data

6.Do not Select template

7.

8.

9.

10.Then you can see the role has complete authorization.

11. Generate the profile using the generate button .

Hope this helps!!!

Abraham

Resource Usage Exceeds Limit ,Resource =Number Buffer

Symptom

Logs in SM21

Resource Usage Exceeds Limit (Resource =Number Buffer,Limit =1000,Curr=1099)

Server Resources are exhausted with high usage ,too many number buffer

Reason and Prerequisites

Current Number Range Buffer exceeded the allocated number 

Check T-code - SM56

Solution

1. Check which objects are having maximum number of entries.

Goto -->Entries

2.  Reset the number range buffer in SM56

Goto--> Number Range Buffer --> Reset

Also a system restart will clear the number range buffer 

Hope this helps!!!

Abraham

SAP HANA STUDIO Installation

Steps to install SAP HANA Studio - Windows

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

2.       Provide S-User Id and Password

3.       Support Packages and Patches à By Alphabetical Index(A-Z)à H àSAP HANA Platform EditionàSAP HANA PLATFORM EDIT 2.0àSAP HANA STUDIO àSAP HANA STUDIO2àSelect the OS àSelect the required SAR File à Download the file

4.       Create a folder in your C drive as HANA Studio and Copy the SAR file in it.

5.       Open Command prompt àSwitch to the HANA Studio Folder

6.       Extract the SAR file using command SAP CAR –xvf <NAME of SAR File>.SAR

This will take few minutes for extracting the files.

Download SAPCAR

7. Click on  hdbsetup.exe

8.Click Next 

9. Click Next

10. Click Install

11.Click Finish

Run SAP HANA STUDIO

1.       Go to Default installation directory à C:\Program Files\sap\hdbstudio

2. Double Click on hdbstudio.exe

3. It will open HANA Studio

4. Open Administration Console

5. Add system

Hope this helps!!!

Abraham

Upgrade BO 4.1 SP5 to BI 4.2 SP5

Update Media Download

SUPPORT PACKAGES AND PATCHES – B -> SBOP BI PLATFORM (ENTERPRISE)  -> SBOP BI PLATFORM 4.2 -> SBOP BI PLATFORM SERVERS 4.2

SUPPORT PACKAGES AND PATCHES – B -> SBOP BI PLATFORM (ENTERPRISE)  -> SBOP BI PLATFORM 4.2 -> SBOP BI PLATFORM CLIENTS 4.2

Upgrade Steps :

1. Stop instances- Server Intelligence and DB

2. Extract the SBOP  BI Platform Server files.

3.Prerequisite Check.

4. Nest starting with the update

5. Click Next,Accept the License Agreement

6. New licensce key message.

7. Provide the CMS and Administrator login Information

8.If you get a message as below , start the server intelligence and DB 

9.

10.

11. 

12.

13.

Hope this helps!!!

Abraham

Generate System info XML is missing

Symptom

Generate System info XML is missing

Reason and Prerequisites

Option SPAM->Utilities->Generate System info XML is missing

Solution

1. Update SPAM/SAINT to the latest version.

2. If incase the issue still exists , proceed as below.

3. SE38 ->Run Report RSLANG20 

4. If this is not successful and the option still is not visible.
5.Start Transaction -SE41
6. Program Name :"SAPMSPAM"
7.Status Field : enter "0100"
8.Click "Display"
9. Click the menu option "User Interface" -> "Activate"  ( or clicke the "Activate" icon)

Hope this helps!!!

Abraham

BI/BOBJ -The system is not configured for this application

Symptom

The system is not configured for this application.If you require configuration contact your system administrator.

Reason and Prerequisites

You have upgraded BI/Business Object system from 4.1 to 4.2

And now you are trying to login to the updated system BI system

Solution

1. Generate the license key for the newer version. (4.2)

2. Login to the CMC using administrator id .

3. Go to Lisence keys.

4. Delete the old license key and add the new key generated from service market place.

Hope this helps!!!

Abraham

No amount authorization For customers/vendors in Company Code :Message no. F5155

Symptom

No amount authorization For customers/vendors in Company Code :Message no. F5155

Solution

1. Go to T-code OLMR ->Authorization Management ->Define Tolerance groups.

2. Check if tolerance group is correctly mapped for each company code or not.

3. Also check if the user is mapped to that tolerance group or not .

OLMR ->Authorization Management ->Assign User Tolerance Group

Hope this helps!!!

Abraham

SUM:MAIN_POSTCLEAN/RUN_RSAIMMERGE_TRANSFER long running

Symptom

In the postprocessing module of an upgrade or an Enhancement Package installation, you notice extreme runtimes of the phase RUN_RSAIMMERGE_TRANSFER.

Reason and Prerequisites

In the phase RUN_RSAIMMERGE_TRANSFER, selects on the table E071 need to be performed.

On some customer databases these selects on the table E071 are very slow.

Solution

1. Recreate the index 1 on the table E071 (defined for the fields PGMID, OBJECT and OBJ_NAME).

2. Refresh the statistics for the table E071.

Alternatively, if creating an additional index is an option:

1. Create an index on the table E071 for the fields TRKORR, PGMID, OBJECT and OBJ_NAME.

2. Refresh the statistics for the table E071.

Repeat the phase RUN_RSAIMMERGE_TRANSFER.

Hope this helps!!!

Abraham

1909524 - "M_PREMA", "V_7BR_PREMA" and "V_T7BRAP" tables error in ACT_TRANS or ACT_UPG phase

Symptom

During upgrade process, the ACT_UPG phase terminates with DDIC ACTIVATION errors "TABLE XXXX was not activated" as per the below error message:

Directory:    <DIR_PUT>/SUM/abap/log
Name:         ACTUPG.ELG

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

DDIC ACTIVATION ERRORS and RETURN CODE in SAPAAAA731.ABC
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


   3 EDT014XActivate dependent table "M_PREMA"
   2WEAD275 Foreign key "M_PREMA"-"BUKRS" (dependency factor "REF" is
   incorrect here)
   2WEAD275 Foreign key "M_PREMA"-"OBRA" (dependency factor "REF" is
   incorrect here)
    1EEDT354 Search field "M_PREMA"-"FILIA" not contained in search help
    attachment
   3 EDT015 Dependent table "M_PREMA" was not activated
   3 EDO525XActivate dependent view "M_PREMA"
   1 EDH202 Check dependent search help "PREMA"
   1 EDH103 Search help "PREMA" is consistent
   3 EMC763 Key field "T7BRAP"-"GRPBR" missing
   2WEMC732 All fields are evaluated as key field
   3 EMC726 View must be created in the database
   3 EDO526 View was activated with warnings"M_PREMA"
    1EEDO519 "Table" "M_PREMA" could not be activated


   3 EDT014XActivate dependent table "V_7BR_PREMA"
   2WEAD275 Foreign key "V_7BR_PREMA"-"BUKRS" (dependency factor "REF" is
   incorrect here)
   2WEAD275 Foreign key "V_7BR_PREMA"-"OBRA" (dependency factor "REF" is
   incorrect here)
    1EEDT354 Search field "V_7BR_PREMA"-"FILIA" not contained in search help
    attachment
   3EDT015 Dependent table "V_7BR_PREMA" was not activated

   3 EDO525XActivate dependent view "V_7BR_PREMA"
   1 EDH202 Check dependent search help "HRPADBRA"
   1 EDH103 Search help "HRPADBRA" is consistent
   3 EMC763 Key field "T7BRAP"-"GRPBR" missing
   2WEMC732 All fields are evaluated as key field
   3 EMC726 View must be created in the database
   3 EDO526 View was activated with warnings"V_7BR_PREMA"
    1EEDO519 "Table" "V_7BR_PREMA" could not be activated

   3 EDT014XActivate dependent table "V_T7BRAP"
   1EEDT354 Search field "V_T7BRAP"-"FILIA" not contained in search help
   attachment
   3 EDT015 Dependent table "V_T7BRAP" was not activated
   3 EDO525XActivate dependent view "V_T7BRAP"
    1EEDO519 "Table" "V_T7BRAP" could not be activated
   1 ETP111 exit code : "8"

Environment

ABAP System, Enhancement Package Installation, Release Upgrade.

Reproducing the Issue

Start SUM tool.
In ACT_UPG phase, the error occurs.
Cause
The root cause of the issue is some fields were removed from the table T7BRAP. This action is delivered by standard packages however this is not reflecting in other objects like M_PREMA.

On the other hand M_PREMA is a Match code object which is obsolete.

Resolution

You can ignore this error and continue with the upgrade only for the specified tables.

Continue the upgrade by choosing the option 'Accept non-severe errors and repeat phase MAIN_SHDRUN/ACT_UPG' in SUM tool.

Hope this helps!!!

Abraham

2596913 - ACT_UPG: indexes for table "J_1BNFE_ACTIVE" have identical fields

Symptom

During upgrade to EHP 7 for ERP 6.0, below errors happen in phase MAIN_SHDRUN/ACT_UPG for Table J_1BNFE_ACTIVE

EDT012XActivate table "J_1BNFE_ACTIVE"
1EEDT509 Indexes "009" and "H33" for table "J_1BNFE_ACTIVE" have identical fields
1EEAD010 "Is valid for following DB systems:" " " " " " "
1EEAD010 "HDB" "(" "SAP HANA Database" ")"
1EEDT509 Indexes "008" and "HBE" for table "J_1BNFE_ACTIVE" have identical fields
1EEAD010 "Is valid for following DB systems:" " " " " " "
1EEAD010 "HDB" "(" "SAP HANA Database" ")"
2WEDT135 Flag: 'Incorrect enhancement category' could not be updated
3 EDT013 Table "J_1BNFE_ACTIVE" was not activated
3 EDT014XActivate dependent table "J_1BNFE_ACTIVE"
3 EDT038 Activation of dependent table "J_1BNFE_ACTIVE" successful
1EEDO519X"Table" "J_1BNFE_ACTIVE" could not be activated

Environment

EHP7 for ERP 6.0

Cause
This is a bug that new version of index still exists despite the deletion request.

Resolution

Refer Note : 

2596913 - ACT_UPG: indexes for table "J_1BNFE_ACTIVE" have identical fields

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

As introduced in below note, you need to manually delete below indexes by SE11 in the shadow instance. After this you can continue the upgrade by repeat the phase from where it stops.

Note 1737650 - EHP7 for SAP ERP 6.0 SP Stacks - Release & Information Note

---------------------------------------------------------------
The ABAP Dictionary activation might fail due to duplicate indexes on table "J_1BNFE_ACTIVE". In that case delete indexes 008 and 009 in ABAP Dictionary and repeat the phase.
---------------------------------------------------------------

Hope this helps!!!

Abraham

2704297 -EDT201 Table "SSCPARADETERM" for logging is too long (key<"250", data division<"16.000" necessary)

Symptom

Activation error occurred in ACT_UPG, ACT_TRANS or DDIC_ACTIVATION phase during system update/upgrade using SUM tool or SPAM tool as below:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB73115.<SID>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3 EDT619XActivate technical settings for "SSCPARADETERM"

1EEDT201 Table "SSCPARADETERM" for logging is too long (key<"250", data division<"16.000" necessary)

3 EDT622 Technical settings for "SSCPARADETERM" were not activated

1EEDO536X"Technical Settings" "SSCPARADETERM" could not be activated


TP 199 ######################################
TP 155 ABAP Dictionary: Activation

DO 578 The following errors or warnings have occurred:

DO 536 Technical Settings SSCPARADETERM could not be activated
D0 313 (E- Table SSCPARADETERM for logging is too long (key<, data division< necessary))
DO 536 Technical Settings SSC_SUBACT could not be activated
D0 313 (E- Table SSC_SUBACT for logging is too long (key<, data division< necessary))



Important: This error can occurs with different tables, as long as the 'Log Data Changes' is enable for that table.

Environment

SAP NetWeaver release independent

Reproducing the Issue

Repeat the upgrade phase using SUM or SPAM tool.

Cause
Table logging was switched on (activated) for a table whose row width is larger than 16,000 bytes or key field length larger than 250 bytes, during system update/upgrade by the corresponding package.

In this example, table logging for table SSCPARADETERM was delivered by package SAPK-73122INSAPBSFND (SAP_BS_FND, release 731 SP22). As in the newly-delivered version, its key field length is larger than 250 bytes, error occurred.

Solution

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

In order to avoid this error, the implementation of the SAP Note 2513147 is necessary previous to the start of the Upgrade. If this is not possible, the following workarounds can be applied:

1. Implement the corrections of the SAP Note 2513147 manually as SNOTE is locked during system update/upgrade. Important: If the SUM tool is used the corrections should be applied on the Shadow Instance;
2. It is possible to disable the table logging (SAP Help) and repeat the phase. After the upgrade is complete, you can enable the table logging again and implement SAP Note 2513147; To do so, proceed as below:

Go to SE11 and input table name in field 'Database table';

Select change (F6);

Select Technical Settings (Ctrl + Shift + F9);

Uncheck the box 'Log Data Changes';

Save the technical settings;

Save the table;

Repeat the upgrade phase.

If the activation error of tables "SSCPARADETERM" and "SSC_SUBACT" are the only activation errors in ACT_UPG or ACT_TRANS phase, then you can simply ignore this error. You can activate the tables after the upgrade has been finished (using SE11 transaction) and implement the SAP Note 2513147 as well.

After ignoring the activation error in ACT_UPG or ACT_TRANS phase during system update/upgrade, the new version will remained non-activated after system update/upgrade and a "Revised" version for technical setting on the table will be created. It is necessary for to activate the "Revised" version on the technical setting for the table manually in transaction SE11.
In this example, for table SSCPARADETERM, you need to display table SSCPARADETERM in SE11, then click icon "Technical Settings", you will find an icon named "Revised<->Active", click it to switch between "Revised" version and "Active" version. You will find that in "Revised" version, "Log data changes" is checked, but in active version not. You need to activate the Revised version manually.

Hope this helps!!!

Abraham

Only startdbs.cmd process available in SAP MMC

Symptom:

When you try starting a SAP system  from SAP MMC , you will see only startdbs.cmd in Process List.

The message server will be started , but dispatcher will not be seen in Process list.

Solution:

1. Check if you have the correct Kernel installed in the SAP system, check with the Product Availability Matrix(PAM).

2. Check if you have the correct oracle instant client installed.

     Refer below SAP Note:

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

Hope this helps!!!

Abraham

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

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

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

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

How To Download Latest Vesrion of SUM

Steps:

1. Login to www.service.sap.com

2. Click on Visit the SAP Support Portal .

3. Select Tools ->Software Logistics Tools.

4. Click on Learn more about Software Logistics Tool

5. Under system maintenance Download SUM.

Hope this helps!!!

Abraham

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.

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

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 RSM13002 

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