Skip to Content
avatar image
Former Member

dbs_ora_schema=SAPSR3 issue during upgrade

Hi Gurus,

I have started an upgrade using Ehpi tool. During the phase PREPARE_JSPM_QUEUE the tool starts the shadow instance and then dispwork stop and I got the error message in dispwork.log:

OCIStmtExecute() failed with -1=OCI_ERROR

C SQL error 942:

B ***LOG BZA=> table SVERS does not exist on database

dbs_ora_schema is set up with =SAPSR3.

The tool uses SAPSR3SHD user to connect to the DB which is OK.

But when the script perform select VERSION from SVERS; the table SVERS does not exist.

When I check using SqlPlus it is the same but if I perform the SQL using schema:

select VERSION from SAPSR3.SVERS; the result is 700.

I have checked the notes:

Note 400241 - Problems with ops$ or sapr3 connect to Oracle

Note 534765 - db connect fails because of wrong db schema in environment

I have cheked SAPSR3 is well setup. and granteed.

SAPSR3 should be like SAP<sid> but my sid is not SR3. Could it be the problem?

How can I check if the dbs_ora_schema is well setup?

Best regards

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Sep 01, 2009 at 04:46 PM

    you problem is OCI_ERROR,which is related to Oracle client Interface. I do not beleive that it is caused by the SVERS message.

    have you updated your kernel? maybe you are using a non-unicode kernel on a unicode system?

    try to find more error logs.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 02, 2009 at 11:22 AM


    Add comment
    10|10000 characters needed characters exceeded