Database Reference
In-Depth Information
alter database backup controlfile to trace
Backup controlfile written to trace file /app/oracle/diag/rdbms/prddb/PRDDB_1/trace/PRDDB_1_
ora_1963.trc
Completed: alter database backup controlfile to trace
2010-05-12 02:00:00.097000 -07:00
Clearing Resource Manager plan via parameter
2010-05-12 13:37:06.902000 -07:00
Thread 1 advanced to log sequence 205 (LGWR switch)
Current log# 1 seq# 205 mem# 0: +PRDDB_DATA/prddb/onlinelog/group_1.261.715810991
2010-05-12 13:37:10.393000 -07:00
Archived Log entry 727 added for thread 1 sequence 204 ID 0xaff834aa dest 1:
Workshop—Monitoring Incidents and Problems
In this workshop, we will try to track and collect information required to help Oracle support complete their tasks of
diagnosing the problem. The workshop uses ADRCI (automatic diagnostic repository command interface).
Step 1
DBA gets an alert from the EM that the Instance 1 has crashed. DBA gets on the server to investigate the reason
for the crash. Browsing through the alert log, DBA notices that the instance had reported an ORA-0600 error. Being
a production database, the DBA's first primary task is to see if the instance will start and look at investigating the
problem as soon as possible. Because other instances in the cluster are up and running, the DBA is certain that
the database should be in good shape and there should be some sort of bug that the database must have been
encountered. After making some quick checks on the ASM instance, database listener, scan listener, and a good check
on the health of the clusterware on the instance, he/she moves to the next step of starting the instance.
Step 2
DBA finds all components on the server are in good health and starts the failed instance using the srvctl command
line interface. After the instance starts, the DBA verifies if the instance is useable and sessions are able to connect to
the database.
Step 3
Now that the instance is up and running, it's time to investigate the root cause of the problem and try to find a
permanent fix. Checking the alert log once again, and locating any trace files associated with the error is a good place
to start and get details regarding the error.
As a practice, it's good to check metalink if there are any bugs or situations reported by other customers.
Illustrated in Figure 18-6 is a lookup tool to identify ORA-00600 and ORA-07445 errors and the possible fixes. If this is a
known issue and a solution has already been identified, the tool provides the fixes and patches that maybe available.
 
Search WWH ::




Custom Search