cancel
Showing results for 
Search instead for 
Did you mean: 

DR switchover issue

Former Member
0 Kudos

Hi,

We are able to switchover the database, but SAP is not starting after switchover on DR site.

Archive logs are transferring to DR site and getting applied.

Same passwords were maintained both on Primary and DR sites.

dev_w0 showing error:

      • ERROR => CONNECT failed with sql error '28000'

[dbsloci.c 11239]

B ***LOG BY2=> sql error 28000 performing CON [dbsh#3 @ 1208] [dbsh 1208 ]

B ***LOG BY0=> ORA-28000: the account is locked [dbsh#3 @ 1208] [dbsh 1208 ]

B ***LOG BY2=> sql error 28000 performing CON [dblink#8 @ 433] [dblink 0433 ]

B ***LOG BY0=> ORA-28000: the account is locked [dblink#8 @ 433] [dblink 0433 ]

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

M in_ThErrHandle: 1

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

I unlocked the SAPSR3 user on DR site with alter user SAPSR3 account unlock, but getting locked every time whenever I have started MMC

Primary site has ownership of SIDADM for all SAP services

DR site has owner ship of SIDADM for SAPOSCOL and SAPSERVICESID for SAPSID_00 and SAPSID_01

Because of ownership issue this is happening pls suggest ?

Pls suggest

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Before switching the standby to primary, its recommended to stop the shipping and sync process of archive logs.

What is the process you followed to swithch over?

And always stop the primary server for such testings (before switching the standby to primary), so it doesn't creates issues when you revert back.

*If you are able to login into sqlplus (manually), then the issue should be minor one with OPS$ mechanism/connectivity.

Regards,

Nick Loy

Former Member
0 Kudos

Hi,

1) Check whether you are able to connect to the database by using SQLPlus, manually

2) Execute the steps, below;

select username from dba_users order by username;

Then, exetcute the command on command line for each database user, provided by the SQL statement, above

brconnect -c -u / -f chpass -o <database user> -p <password>

Best regards,

Orkun Gedik

Former Member
0 Kudos

Hi,

We will get same problem when we switchover back to Primary ?

Regards

Former Member
0 Kudos

Hi,

>

> We will get same problem when we switchover back to Primary ?

>

> Regards

Under the normal conditions, it should work, but it is hard to say without connecting to your system.

In order to be safe side, be sure that the both systems are located under the same domain for the OPS$ mechanism

Best regards,

Orkun Gedik

Former Member
0 Kudos

Hi ,

In case of our DEV DR , all OP$ from Primary host exists but working fine, we have not changed SAPSR3 passwords

Regards

Former Member
0 Kudos

Hi ,

>

> In case of our DEV DR , all OP$ from Primary host exists but working fine, we have not changed SAPSR3 passwords

>

> Regards

Hi,

As I noted that it is hard to understand without connection to your system. But, I can say that

1) If both on systems, SAPUSER tables has same owner, such as "<OPS$DOMAIN>\<SID>ADM".SAPUSER and the table contains same password, belongs to SAPSR3 user.

2) SAPSR3 users has the same password (same password must be used as step 1) on both systems

It should work, without any problem after switchover.

Best regards,

Orkun Gedik