DR issue (Switch over)

[Former Member]

Hi,

We are unable to start SAP after switchover. error in dw_w0

ORA-01017: Invalid username/password; logon denied

OPS$users on DR site showing- OPS$STANDBY\EC7ADM and OPS$STANDBY\SAPSERVICEEC7.

Pls suggest do I need to create OPS$PRIMARY\EC7ADM, OPS$PRIMARY\SAPSERVICESR3 and OPS$PRIMARY\SAPSERVICEEC7  on DR site server and delete above standby ops$users ?

Database is working fine after switchover but SAP is not starting. Ours' is ECC6.0, Oracle 11.2.0.3 (patch set 5), Windows 2k3.

Unlocked SAPSR3 but getting locked after starting MMC.

Regards

[Former Member · Accepted solution]

Hi,

I assume that the domain/workgroup name is "STANDBY" that you want to start the SAP. Under this circumstance, "OPS$STANDBY\EC7ADM" and "OPS$STANDBY\SAPSERVICEEC7" users must be exist in the SAPUSER table. Additionally, check the grants to the OPS$ users. Pelase check the notes;

50088  Creating OPS$ users on Windows NT/Oracle

361641  Creating OPS$ users on UNIX

Best regards,

Orkun Gedik

[Former Member · Accepted solution]

Hi,

Created users as per 50088, referred notes - 562863, 400241.  SAP is not starting on Physical Standby after swtichover.

Pls find below dev_w0 and dev_w0.old logs:

dev_w0

C  Logon as OPS$-user to get SAPSR3's password

C  Connecting as /@EC7 on connection 0 (nls 0) ... (dbsl 720 090112, non-unicode)

C  Attaching to database server EC7 (con=0, svchp=136ED5E8, srvhp=136EDEC0)

C  Starting user session: OCISessionBegin(con=0, usr='/', svc=136ED5E8, srv=136EDEC0, usr=1382B8E0)

C     OCIStmtExecute() failed with -1=OCI_ERROR

C     SQL error 942:

C  Could not read session ID from V$MYSTAT. rc=-1.

C  Now '/@ EC7' is connected: con=0, nls=0, session=-1, time='2012-10-15 11:48:55'

C     OCIStmtExecute() failed with -1=OCI_ERROR

C     SQL error 980:

C  *** ERROR => ORA-980 when accessing table SAPUSER

[dbsloci.c    15076]

C  Disconnecting from connection 0 ...

C  Closing user session (con=0, svc=136ED5E8, usr=1382B8E0)

C  Disconnected (con=0) from ORACLE.

C  SAPUSER error or connect error 99=DBSL_ERR_DB, oerr=980.

B  ***LOG BY2=> sql error 980    performing CON [dbsh         1246]

B  ***LOG BY0=> ORA-00980: synonym translation is no longer valid [dbsh         1246]

B  ***LOG BY2=> sql error 980    performing CON [dblink       544]

B  ***LOG BY0=> ORA-00980: synonym translation is no longer valid [dblink       544]

M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1490]

M  in_ThErrHandle: 1

M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   11321]

M 

M  Info for wp 0

dev_W0.old

C  Logon as OPS$-user to get SAPSR3's password

C  Connecting as /@EC7 on connection 0 (nls 0) ... (dbsl 720 090112, non-unicode)

C  Attaching to database server EC7 (con=0, svchp=136ED5E8, srvhp=136EDEC0)

C  Starting user session: OCISessionBegin(con=0, usr='/', svc=136ED5E8, srv=136EDEC0, usr=1382B8E0)

C     OCIStmtExecute() failed with -1=OCI_ERROR

C     SQL error 942:

C  Could not read session ID from V$MYSTAT. rc=-1.

C  Now '/@EC7' is connected: con=0, nls=0, session=-1, time='2012-10-15 11:48:55'

C     OCIStmtExecute() failed with -1=OCI_ERROR

C     SQL error 980:

C  *** ERROR => ORA-980 when accessing table SAPUSER

[dbsloci.c    15076]

C  Disconnecting from connection 0 ...

C  Closing user session (con=0, svc=136ED5E8, usr=1382B8E0)

C  Disconnected (con=0) from ORACLE.

C  SAPUSER error or connect error 99=DBSL_ERR_DB, oerr=980.

B  ***LOG BY2=> sql error 980    performing CON [dbsh         1246]

B  ***LOG BY0=> ORA-00980: synonym translation is no longer valid [dbsh         1246]

B  ***LOG BY2=> sql error 980    performing CON [dblink       544]

B  ***LOG BY0=> ORA-00980: synonym translation is no longer valid [dblink       544]

M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1490]

M  in_ThErrHandle: 1

M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   11321]

M 

M  Info for wp 0

Pls suggest

Regards

[Former Member · Accepted solution]

>> ORA-00980: synonym translation is no longer valid

Did you created synonym, sapuser table and set the grants regarding to the notes I mentioned? This error occurs when the sapuser table does not available.

Best regards,

Orkun Gedik

[Former Member · Accepted solution]

Hi,

After creating users as per note-50088, executed below scripts;

SQL> grant dba, sapdba, connect, resource to "OPS$STANDBY\EC7ADM";

Grant succeeded.

SQL> create table "OPS$STANDBY\EC7ADM".SAPUSER (USERID VARCHAR2(256), PASSWD VARCHAR2(256));

Table created.

SQL> insert into "OPS$STANDBY\EC7ADM".SAPUSER values ('SAPSR3','sap');

1 row created.

SQL> alter user SAPSR3 identified by sap;

User altered.

SQL> grant connect, resource to "OPS$STANDBY\SAPSERVICEPRD";

Grant succeeded.

SQL> CREATE PUBLIC SYNONYM SAPUSER FOR "OPS$STANDBY\EC7ADM.SAPUSER";

Synonym created.

SQL> COMMIT;

Commit complete.

Regards

[Former Member · Accepted solution]

Execute the statements;

SQL> CREATE USER "OPS$STANDBY\EC7ADM" DEFAULT TABLESPACE SYSTEM TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;
SQL> CREATE USER "OPS$STANDBY\SAPSERVICEEC7" DEFAULT TABLESPACE SYSTEM TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;
SQL> GRANT CONNECT, RESOURCE, SAPDBA TO "OPS$STANDBY\EC7ADM";
SQL> GRANT CONNECT, RESOURCE, SAPDBA TO "OPS$STANDBY\SAPSERVICEEC7";
SQL> CREATE TABLE "OPS$STANDBY\EC7ADM".SAPUSER (USERID VARCHAR2(256), PASSWD VARCHAR2(256));
SQL> INSERT INTO "OPS$STANDBY\EC7ADM".SAPUSER VALUES ('SAPSR3', '<password>');
SQL> CREATE SYNONYM "OPS$STANDBY\SAPSERVICEEC7".SAPUSER FOR "OPS$STANDBY\EC7ADM".SAPUSER;

SQL> CONNECT /
SQL> GRANT SELECT, UPDATE ON "OPS$STANDBY\EC7ADM".SAPUSER TO "OPS$STANDBY\SAPSERVICEEC7";

SQL> CONNECT /as sysdba
SQL> GRANT CONNECT, RESOURCE TO "OPS$STANDBY\SAPSERVICEEC7";
SQL> GRANT CONNECT, RESOURCE TO "OPS$STANDBY\EC7ADM";

Change the password at the OS level;

brconnect -c -u / -f chpass -o OPS$STANDBY\SAPSERVICEEC7 -p <password>
brconnect -c -u / -f chpass -o OPS$STANDBY\EC7ADM -p <password>

Best regards,

Orkun Gedik

[Former Member]

Thanks Orkun.. Working fine

[Former Member]

Nice to hear this You'r welcome

[Former Member]

Hi,

Ours is ABAP+Java, ABAP working fine, No java process in SAP MMC and no process in jcmon pf=...... command.  Do we need execute same scripts for SAPSR3DB, we executed for SAPSR3 ?

Pls suggest

[Former Member]

Hi,

For the J2EE instance, you should check the database password on the config tool.

But first, you should check the java trace files in order to identify the root cause.

Best regards,

Orkun Gedik

[Former Member]

Hi,

Do we need to run SGEN every time after switchover as we are getting compiling status after every switchover though we have executed SGEN on both Primary and standby databases after switchover ?

Pls suggest

Regards

[Former Member]

Hi,

Do we need to run SGEN every time after switchover as we are getting compiling status after every switchover though we have executed SGEN on both Primary and standby databases after switchover ?

Pls suggest

Regards

[Former Member]

>>ORA-01017: Invalid username/password; logon denied

Follow Note 1576837  - ORA-01017: invalid username/password