Oracle logging
If a failover or degeneration occurs in the event of a failure in PRIMECLUSTER operation with Oracle, solve the problem referring to the Oracle alert log or trace log.
PRIMECLUSTER Wizard for Oracle logging
PRIMECLUSTER Wizard for Oracle provides information what kind of failure is detected and what corrective action should be taken in the following log files:
/var/opt/reliant/log/FJSVclora_<OracleSID>*.log /var/opt/reliant/log/FJSVclora_<ListenerName>*.log
The log file formats are as follows:
Date/type/ID/text 2002/04/25 15:18:40 [Info] [1101] Starting Oracle detector 2002/04/25 15:18:40 [Info] [1102] Connected to Oracle 2002/04/25 15:18:40 [Error] [1299] ORA-01034 Oracle not available.
Date
Output in the format of YYYY/MM/DD HH:MM:SS.
Type
Indicates classification. (Information, Error, Warning)
ID
Indicates a message number.
Text
Indicates message content.
Note
There is no restriction of space or memory for log files. RMS manages the log files.
The log files will be used for troubleshooting. Do not delete or delete the files.
