Home > Database, Oracle > Fixing incorrect crs_stat

Fixing incorrect crs_stat

September 8th, 2009

I was interested to find out how I can change the configuration of the oracle cluster nodeapps.
I had a problem with the listener running on both nodes.
The problem was an incorrect ACTION_SCRIPT=/u01/app/oracle/oracle/product/10.2.0/asm/bin/racgwrap
The path was incorrect due to previous installation that I did with the wrong path. This leads to unknown status in the application state as follows:

oracle@rac03:/u01/crs1020/crs/public> crs_stat -t
Name Type Target State Host
————————————————————
ora….SM1.asm application ONLINE ONLINE rac03
ora….03.lsnr application ONLINE UNKNOWN rac03
ora.rac03.gsd application ONLINE ONLINE rac03
ora.rac03.ons application ONLINE ONLINE rac03
ora.rac03.vip application ONLINE ONLINE rac03
ora….SM2.asm application ONLINE ONLINE rac04
ora….04.lsnr application ONLINE UNKNOWN rac04
ora.rac04.gsd application ONLINE ONLINE rac04
ora.rac04.ons application ONLINE ONLINE rac04
ora.rac04.vip application ONLINE ONLINE rac04

In order go fix this I exported the listener configuration by using the following for both nodes separately:

oracle@rac03:~> crs_stat -p ora.rac03.LISTENER_RAC03.lsnr > /u01/crs1020/crs/public/ora.rac03.LISTENER_RAC03.lsnr.cap

oracle@rac03:~> crs_stat -p ora.rac04.LISTENER_RAC04.lsnr > /u01/crs1020/crs/public/ora.rac04.LISTENER_RAC04.lsnr.cap

Now you have to edit the files with some text editor and apply the correct data in the file.

Stop the UNKNOWN applications as follows:

oracle@rac03:~> crs_stop -f ora.rac03.LISTENER_RAC03.lsnr

oracle@rac03:~> crs_stop -f ora.rac04.LISTENER_RAC04.lsnr

Unregister the unknown applications as follows:

oracle@rac03:~> crs_unregister ora.rac03.LISTENER_RAC03.lsnr
oracle@rac03:~> crs_unregister ora.rac04.LISTENER_RAC04.lsnr

Now register the applications again:

oracle@rac03:~> crs_register ora.rac03.LISTENER_RAC03.lsnr
oracle@rac03:~> crs_register ora.rac04.LISTENER_RAC04.lsnr

It’s time to start the services:

oracle@rac03:~> crs_start ora.rac03.LISTENER_RAC03.lsnr
oracle@rac03:~> crs_start ora.rac04.LISTENER_RAC04.lsnr

Now you can check the nodeapps again:

oracle@rac03:~> crs_stat -t
Name Type Target State Host
————————————————————
ora….SM1.asm application ONLINE ONLINE rac03
ora….03.lsnr application ONLINE ONLINE rac03
ora.rac03.gsd application ONLINE ONLINE rac03
ora.rac03.ons application ONLINE ONLINE rac03
ora.rac03.vip application ONLINE ONLINE rac03
ora….SM2.asm application ONLINE ONLINE rac04
ora….04.lsnr application ONLINE ONLINE rac04
ora.rac04.gsd application ONLINE ONLINE rac04
ora.rac04.ons application ONLINE ONLINE rac04
ora.rac04.vip application ONLINE ONLINE rac04

Another test:

oracle@rac03:~> srvctl status nodeapps -n rac03
VIP is running on node: rac03
GSD is running on node: rac03
Listener is running on node: rac03
ONS daemon is running on node: rac03

oracle@rac03:~> srvctl status nodeapps -n rac04
VIP is running on node: rac04
GSD is running on node: rac04
Listener is running on node: rac04
ONS daemon is running on node: rac04

Done.

Comments are closed.