RAC Troubleshooting
This is the one section what will be updated frequently as my experience with RAC grows, as RAC has been around for a while most problems can be resolve with a simple google lookup, but a basic understanding on where to look for the problem is required. In this section I will point you where to look for problems, every instance in the cluster has its own alert logs, which is where you would start to look. Alert logs contain startup and shutdown information, nodes joining and leaving the cluster, etc.
Here is my complete alert log file of my two node RAC starting up.
The cluster itself has a number of log files that can be examined to gain any insight of occurring problems, the table below describes the information that you may need of the CRS components
1. $ORA_CRS_HOME/crs/log : contains trace files for the CRS resources
2. $ORA_CRS_HOME/crs/init : contains trace files for the CRS daemon during startup, a good place to start
3. $ORA_CRS_HOME/css/log : contains cluster reconfigurations, missed check-ins, connects and disconnects from the client CSS listener. Look here to obtain when reboots occur
4. $ORA_CRS_HOME/css/init : contains core dumps from the cluster synchronization service daemon (OCSd)
5. $ORA_CRS_HOME/evm/log : log files for the event volume manager and eventlogger daemon
6. $ORA_CRS_HOME/evm/init : pid and lock files for EVM
7. $ORA_CRS_HOME/srvm/log : log files for Oracle Cluster Registry (OCR)
8. $ORA_CRS_HOME/log : log files for Oracle clusterware which contains diagnostic messages at the Oracle cluster level
As in a normal Oracle single instance environment, a RAC environment contains the standard RDBMS log files, these files are located by the parameter background_dest_dump. The most important of these are
9. $ORACLE_BASE/admin/udump : contains any trace file generated by a user process
10. $ORACLE_BASE/admin/cdump : contains core files that are generated due to a core dump in a user process
Now lets look at a two node startup and the sequence of events
First you must check that the RAC environment is using the connect interconnect, this can be done by either of the following
Logfile ## The location of my alert log, yours may be different
/u01/app/oracle/admin/racdb/bdump/alert_racdb1.log
ifcfg command oifcfg getif
table check select inst_id, pub_ksxpia, picked_ksxpia, ip_ksxpia from x$ksxpia;
Oradebug SQL> oradebug setmypid
SQL> oradebug ipc
Note: check the trace file which can be located by the parameter user_dump_dest
system parameter cluster_interconnects
Note: used to specify which address to use
Random Posts
Blog Archive
ORACLE DBA
Search This Blog
Blog Archive
-
▼
2011
(101)
-
▼
July
(79)
- oracle RAC Commands
- 10g ORACLE
- Thirupal_Boreddy_oracle_DBA: Thirupal_Boreddy_orac...
- To monitor job progress[RMAN]
- systemstate and hang analyse
- Thirupal_Boreddy_oracle_DBA: systemstate and hang ...
- UNIX raw filesystem commands for dba
- Thirupal_Boreddy_oracle_DBA: Thirupal_Boreddy_orac...
- ENQUEUE LOCK:
- Thirupal_Boreddy_oracle_DBA: Thirupal_Boreddy_orac...
- The Archiver hung alerts
- How to register database with RMAN recovery catalog
- Thirupal_Boreddy_oracle_DBA: Procedure to relocate...
- dbms_metadata
- Thirupal_Boreddy_oracle_DBA: systemstate and hang ...
- set date format
- Thirupal_Boreddy_oracle_DBA: systemstate and hang ...
- Static Parameter
- HSMP cluster commands:
- HSMP cluster commands:
- systemstate and hang analyse
- OMS Commands
- Thirupal_Boreddy_oracle_DBA: OMS Commands
- crs commands
- crs commands
- crs commands
- Process for clearing down archivelogs via Rman
- Thiru: Process for clearing down archivelogs via Rman
- Converting to archive log mode in RAC
- Thiru: Converting to archive log mode in RAC
- Steps for VIP Relocation
- Thiru: Converting to archive log mode in RAC
- Add space in RAC DB TABLESPACES:
- Thiru: Process for clearing down archivelogs via Rman
- Chang Archive log destination
- Thiru: Chang Archive log destination
- Manual Archive Backup
- Thiru: Manual Archive Backup
- Thiru: To monitor job progress[RMAN]
- Thiru: Thirupal_Boreddy_oracle_DBA: ENQUEUE LOCK:
- Thiru: Chang Archive log destination
- RMAN Checks
- Thiru: RMAN Checks
- ASM – basic things to look for
- Thiru: RMAN Checks
- Killing a Hanging CRSD Daemon;
- Thiru: ASM – basic things to look for
- Useful CRS Commands
- Thiru: Useful CRS Commands
- Thiru: Useful CRS Commands
- Useful CRS Commands
- Thiru: Useful CRS Commands
- Operating System Commands
- Thiru: Useful CRS Commands
- Tracing a SQL session
- Check cluster name
- The Archiver hung alerts
- Log file locations in RAC
- Thiru: Tracing a SQL session
- System state dump and Hanganalyze
- Thiru: The Archiver hung alerts
- RAC - Healthchecking the Startup of Oracle for a g...
- Thiru: Log file locations in RAC
- RAC - Stopping everything Oracle-related for a giv...
- Thiru: Procedure to relocate services in RAC nodes
- Enabling Archive Logs in a RAC Environment
- Adding a new vote disk
- Thiru: Enabling Archive Logs in a RAC Environment
- Export of table Partition
- Flashback setup in RAC
- Voting Disk
- Post database creation CRS Health check
- RAC Troubleshooting
- Change the parameters for RAC database
- Compressed Export and Import
- Adding the space to tablespace
- Change db_recovery_file_dest_size
- Restarting SSH broker in the event of a hang
- Thiru: Thirupal_Boreddy_oracle_DBA: oracle RAC Com...
-
▼
July
(79)
Thirupal Boreddy. Powered by Blogger.
My Blog List
Followers
Lorem 1
Technology
Circle Gallery
‹
›
Shooting
Racing
News
Lorem 4
Tagged with: RAC Troubleshooting
About Oracle DBA World
WePress Theme is officially developed by Templatezy Team. We published High quality Blogger Templates with Awesome Design for blogspot lovers.The very first Blogger Templates Company where you will find Responsive Design Templates.
Subscribe to:
Post Comments (Atom)
QUERY FOR CPU USAGE
select a.target_name as HOST, to_char(a.rollup_timestamp,' dd-Mon-yy::hh24:mi') as "DAY-TIME", sum(c.cpu_count) as ...


No comments