OCRBACKUP Generates Huge Trace Files on ASM Instances
(Doc ID 2745689.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
On ASM instances, huge trace files (which have following info) are generated regularly.
<< Trace file on ASM instance >>
------------------------------------------------------
*** MODULE NAME:(crsctl.bin@<hostname> (TNS V1-V3))
(kfzuser) : 120e92158
ubuf= (invalid)
clus= (invalid)
osnm=grid (valid)
osid= (invalid)
flags=0x4 styp=O/S name
------------------------------------------------------
------------------------------------------------------
*** MODULE NAME:(crsctl.bin@<hostname> (TNS V1-V3))
(kfzuser) : 120e92158
ubuf= (invalid)
clus= (invalid)
osnm=grid (valid)
osid= (invalid)
flags=0x4 styp=O/S name
------------------------------------------------------
Above trace files are generated when getting OCR backup.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |