Database Reference
In-Depth Information
ssky4l4p4.localdomain(+ASM4) <--- '+APX4(ssky4l4p4)'
ssky4l4p4.localdomain(+ASM4) <--- '+ASM4(ssky4l4p4)'
ssky4l4p4.localdomain(+ASM4) <--- 'SSKYDB_2(ssky4l4p4)'
OCR/CRSD Master : ssky4l4p3
CRSD PE Master : ssky4l4p3
CRSD PE Standby : ssky4l4p4
CTSS Master : ssky4l4p3
UI Master : ssky4l4p3
ONS Master : ssky4l4p4
CHM Master : ssky4l4p3
CHM Replica : REPLICA has been deprecated from 12c
OCR Local/Writer connects ASM Instance
================ ======== ============
ssky4l4p2(Hub,OCR Local) ---> ssky4l4p4(+ASM4)
ssky4l4p5(Hub,OCR Local) ---> ssky4l4p2(+ASM1)
ssky4l4p3(Hub,OCR Writer) ---> ssky4l4p3(+ASM3)
ssky4l4p4(Hub,OCR Local) ---> ssky4l4p4(+ASM4)
Conclusion
In this chapter we looked at the various problem-solving diagnosis methods for different kinds of error situations.
ORA-0600
and
ORA-7445
are errors that normally cause great concern to the DBAs. Such concerns are genuine because
these errors are critical and could mean downtime for the production instance in certain cases.
Oracle has provided various methods of troubleshooting the instance and the database to gather information.
If any of the previously mentioned errors occur, it is advisable to collect the following information irrespective of what
is already generated by Oracle:
1.
Use the HM and ADR for creating problem definitions.
2.
Gather information from all instances using the RDA utility.
3.
If required, use
ORADEBUG
to freeze the instance and collect the system state dump as
illustrated in the flash freeze section previously.
4.
If a query is involved during the operation, the SQL Diagnosability functionality can be
used to create the required test case so that Oracle support can reproduce the problem.
5.
Zip these files and upload them to Oracle Support when the TAR is initially created.
Search WWH ::
Custom Search