I have been in a scenario recently where APPS account got locked during the cloning process as soon as I started the Oracle database TNS Listener.
Reason: Passwords are different in Prod and Test instance. Before I could run autoconfig (which requires Listener) to be up, another application from Oracle Fusion Middleware was trying to connect to the newly refreshed test instance.
In situations like this, you can restrict the access to DB by changing the sqlnet.ora file in $ORACLE_HOME/network/admin. Add the following entries:
tcp.validnode_checking = yes
tcp.invited_nodes = (testdb, testccm, your_desktop_IP)
Now restart the listener. Once the autoconfig is executed on database node the SQLNET.ora will be overwritten. You need to bounce the listener again to take off the restrictions made.
Reason: Passwords are different in Prod and Test instance. Before I could run autoconfig (which requires Listener) to be up, another application from Oracle Fusion Middleware was trying to connect to the newly refreshed test instance.
In situations like this, you can restrict the access to DB by changing the sqlnet.ora file in $ORACLE_HOME/network/admin. Add the following entries:
tcp.validnode_checking = yes
tcp.invited_nodes = (testdb, testccm,
Now restart the listener. Once the autoconfig is executed on database node the SQLNET.ora will be overwritten. You need to bounce the listener again to take off the restrictions made.
No comments:
Post a Comment