![]() kgfnConnect2Int: sysasm=0 envflags=0x10 srvrflags=0x1 unam=crsuser_asm_001 password is NOT NULL pstr=_ocr Next, I went to the mentioned “ohasd_orarootagent_c” and found many many lines like these: Details at (:CRSAGF00113:) in D:\app\oracle\diag\crs\server001\crs\trace\c. ![]() Details are at "(:CLSN00140:)" in "D:\app\oracle\diag\crs\server001\crs\trace\ohasd_orarootagent_c". 14:17:52.417 CRS-5019: All OCR locations are on ASM disk groups, and none of these disk groups are mounted. So I checked the cluster alert.log first: After 10 minutes of waiting it simply timed out. When checking the progress of the startup via “crsctl stat res -t -init” we could see that it was stuck at starting “ora.storage” resource. ![]() The clusterware is 12.1.0.2 with the April 2017 BundlePatch installed. Beside the fact, that we could not identify any root cause for the reboot, there were no messages in the clusters alert.log, the ocssd.log or crsd.log, the clusterware did not start properly after the node came up again. A couple of days ago I experienced a node reboot in a Windows RAC cluster at a customers site.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |