DBA Issues Tips

Register other listeners with the Clusterware to startup automatically with Oracle Restart startup : -- Mandatory info(listener name, port no) will get from Listener.ora file . # vi /u01/app/grid/product/12.2.0/grid/network/admin/listener.ora --Use the srvctl add listener command with the following syntax: --log in as grid user srvctl add listener [-l listener_name] [-p endpoints] [-s] [-o Oracle_home] Option Description : -l listener_name -p endpoints -s Skip checking for port conflicts with the supplied endpoints -o Oracle_home (Oracle home for the listener. If omitted, the Oracle Grid Infrastructure home is assumed) $ srvctl add listener -l <listener_name> -s -p <port no> --To Start the same listener: $ srvctl start listener -l <Listener_name> -- To config under crsctl status $ srvctl config listener -l <listener_name> --Now above listener will comes under crsctl status. $ crsctl status res -t

How to Configure DB services to start by Automatically on cluster (oracle restart and cluster environments ) Services can be start with following Option : PRIMARY,PHYSICAL_STANDBY,LOGICAL_STANDBY,SNAPSHOT_STANDBY --If Service role option is "PRIMARY" then the service will not start automatically on a standby DB when clusterware/Oracle Restart start by "crsctl start has/crs" command, it need to be started manually. --With below option you can check the service configuration: $ srvctl config service -s <Service_Name> -d <database_name> --you can see what define on With Service role option, here below as mention Primary so it will auto restart on Primany only. Service role: PRIMARY --In order to get a service startup automatically when clusterware: $ srvctl modify service -d <DB_NAME> -s <service_name> -l 'PRIMARY,PHYSICAL_STANDBY' --Now will see that Service role cnfigured to startup automaticaly with "PRIMAR