Follow

arcserve-KB : Oracle Service Might not start on Replica after the Synchronization / Switchover is finished.

Last Update: 2016-04-07 10:40:49 UTC
Description:

Oracle Service Might not start on Replica after the Synchronization / Switchover is finished.

Cause:

Oracle recommends to use Standard Windows Account (mostly a local user from the oracle server) to start Oracle Services.
Image
Even if we have the same User Name in both Master and Replica (with the same password), these two users will differ with their USER ID.
Image
By default RHA synchronization would overwrite files on Replica.  As part of the process, the ACL of the files on Replica are overwritten to keep identical to master’s which results in the “Oracle User Account” losing access to database files.  User will experience unexpected error or failure when trying to start Oracle on Replica.


In the Master Server, when we look @ the ACL of the Oracle root directory of its database files, we will find the user name displayed

Image



However, when we look @ the properties for the replica, we will just see the userID (which indicates that the userID displayed is not associated with any user in Replica)

Image
 
Solution:

To overcome this problem, highlight the scenario, from the “Properties” tab in Right Pane, and expand Replication [Symbol] Optional Settings [Symbol] Replicate ACL [Symbol] set “Retain Local Account Names” to ON and save the scenario. Now, RHA will maintain the same user name on Replica and Oracle will work fine.

Image








Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments