Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem: Why do we see crs process even after stopping CRS
[init.d/init.crsd, init.cssd, init.evmd]
After successful installation of Installation of 10.2.0.2, when stop the crs,
processes do not exist from OS.
ps -ef|grep init.
root 23 0 0 10:40:55 ? 0:06 pagetableinit_daemon
root 3585 1 0 16:07:00 ? 0:00 /bin/sh /sbin/init.d/init.cssd fatal
root 3455 1 0 16:06:59 ? 0:00 /bin/sh /sbin/init.d/init.evmd run
root 3458 1 0 16:06:59 ? 0:00 /bin/sh /sbin/init.d/init.crsd run
root 23 0 0 10:40:55 ? 0:06 pagetableinit_daemon
root 3585 1 0 16:07:00 ? 0:00 /bin/sh /sbin/init.d/init.cssd fatal
root 3455 1 0 16:06:59 ? 0:00 /bin/sh /sbin/init.d/init.evmd run
root 3458 1 0 16:06:59 ? 0:00 /bin/sh /sbin/init.d/init.crsd run
Symptoms:
$ORACLE_HOME/bin/crsctl check crs
Failure 1 contacting CSS daemon
Cannot communicate with CRS
Cannot communicate with EVM
Failure 1 contacting CSS daemon
Cannot communicate with CRS
Cannot communicate with EVM
ps -ef |grep d.bin
oracrsu 1586 29893 1 21:12:40 pts/0 0:00 grep d.bin
ps -ef|grep init
root 1 0 0 Jul 5 ? 0:20 init
root 23 0 0 Jul 5 ? 0:04 pagetableinit_daemon
oracrsu 1603 29893 0 21:12:47 pts/0 0:00 grep init
root 6470 1 0 Jul 5 ? 0:05 /bin/sh /sbin/init.d/init.crsd run
root 6584 1 0 Jul 5 ? 0:05 /bin/sh /sbin/init.d/init.cssd fatal
root 6471 1 0 Jul 5 ? 0:05 /bin/sh /sbin/init.d/init.evmd run
oracrsu 1586 29893 1 21:12:40 pts/0 0:00 grep d.bin
ps -ef|grep init
root 1 0 0 Jul 5 ? 0:20 init
root 23 0 0 Jul 5 ? 0:04 pagetableinit_daemon
oracrsu 1603 29893 0 21:12:47 pts/0 0:00 grep init
root 6470 1 0 Jul 5 ? 0:05 /bin/sh /sbin/init.d/init.crsd run
root 6584 1 0 Jul 5 ? 0:05 /bin/sh /sbin/init.d/init.cssd fatal
root 6471 1 0 Jul 5 ? 0:05 /bin/sh /sbin/init.d/init.evmd run
Solution:
This is an expected behavior. These are the init scripts which are spawned
from /etc/inittab as part of crs startup.
Basically there shouldn't be any crs daemons running. To check this execute below command:
ps -ef |grep d.bin
$ORA_CCRS_HOME/bin/crsctl check crs
Basically there shouldn't be any crs daemons running. To check this execute below command:
ps -ef |grep d.bin
$ORA_CCRS_HOME/bin/crsctl check crs
You can ignore them and go and upgrade the CRS.
If you want them to be stopped then you can follow below action plan:
1. Disable crs
crsctl disable crs
2. Restart node. Since crs is disabled, upon restart CRS will not come up.
3. Let the node comes up then enable crs
crsctl enable crs
This will not start CRS but it will just enable the crs startup upon node reboot.
If you want them to be stopped then you can follow below action plan:
1. Disable crs
crsctl disable crs
2. Restart node. Since crs is disabled, upon restart CRS will not come up.
3. Let the node comes up then enable crs
crsctl enable crs
This will not start CRS but it will just enable the crs startup upon node reboot.
References:
No comments:
Post a Comment