Shulou(Shulou.com)06/01 Report--

Today, I will talk to you about the log system of the Oracle RAC environment, which may not be well understood by many people. in order to make you understand better, the editor has summarized the following content for you. I hope you can get something according to this article.

In an Oracle RAC environment, the log system is more complex than that of a single system: see the following figure:

Briefly introduce the log architecture in Oracle cluster environment. When you encounter a problem, you can quickly find the required log file and locate the problem in time.

File path of 1.Oracle cluster log

The logs involved in the Oracle cluster are mainly located in the "$GRID_HOME/log" and "$ORACLE_HOME/log" directories.

two。 Log directory structure

Log structure of the clusterware layer:

Grid@rac1:/home/grid > tree-d $ORACLE_HOME/log

/ opt/rac/11.2.0/grid/log

|-- crs

|-- diag

| | `--clients |

| | `--user_root |

| | `--host_1874443374_76 |

| |-- alert |

| |-- cdump |

| |-- incident |

| |-- incpkg |

| |-- lck |

| |-- metadata |

| |-- stage |

| |-- sweep |

| | `--trace |

`--rac1

|-- admin

|-- agent

| |-- crsd |

| | |-- oraagent_grid |

| | |-- oraagent_oracle |

| | `--orarootagent_root |

| | `--ohasd |

| |-- oraagent_grid |

| |-- oracssdagent_root |

| |-- oracssdmonitor_root |

| | `--orarootagent_root |

|-- client

|-- crsd

|-- cssd

|-- ctssd

|-- diskmon

|-- evmd

|-- gipcd

|-- gnsd

|-- gpnpd

|-- mdnsd

|-- ohasd

|-- racg

| |-- racgeut |

| |-- racgevtf |

| | `--racgmain |

`--srvm

42 directories

Log structure of the RMDBS layer:

Oracle@rac1:/opt/rac/oracle/diag/rdbms/rac > tree-d rac1

Rac1

|-- alert

|-- cdump

|-- hm

|-- incident

|-- incpkg

|-- ir

|-- lck

|-- metadata

|-- stage

|-- sweep

`--trace

11 directories

Where "rac1" is the hostname.

3. Log directory function description

1) the CRS log is stored in the "$GRID_HOME/log//crsd" directory and will be archived every 10m.

2) the CSS log is stored in the "$GRID_HOME/log//cssd" directory and will be archived every 20m.

3) EVM logs are stored in the "$GRID_HOME/log//evmd" directory

4) the log corresponding to the RACG executable is recorded in the racg directory in the "$GRID_HOME/log/" and "$ORACLE_HOME/log/" directories

5) the "$GRID_HOME/log//client" and "$ORACLE_HOME/log//client" directories record log information corresponding to srvctl, ocrdump, ocrconfig, and ocrcheck commands.

Alert logs of 4.Oracle cluster

The alert log file in the Oracle RAC environment is the same as the alert log for a single instance of Oracle. The file is located in the "in $ORACLE_BASE/rdbms//trace" directory with a naming convention of "alert_.log"

This warning log records important warnings about the rdbms level of the Oracle cluster.

Oracle@rac1:/opt/rac/oracle/diag/rdbms/rac/rac1/trace > more alert_rac1.log

Starting up:

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-64bit Production

With the Partitioning, Real Application Clusters, OLAP, Data Mining

And Real Application Testing options.

Using parameter settings in client-side pfile/ opt/rac/oracle/admin/rac/pfile/init.ora on machine rac1

System parameters with non-default values:

Processes = 150

Nls_language = "SIMPLIFIED CHINESE"

Nls_territory = "CHINA"

Memory_target = 1584m

Control_files = "+ DATA2/rac/controlfile/current.260.781821965"

Db_block_size = 8192

Compatible = "11.2.0.0.0"

Log_archive_dest_1 = "LOCATION=+DATA2"

Log_archive_format = "yangdb_%t_%s_%r.dbf"

Db_create_file_dest = "+ DATA2"

Undo_tablespace = "UNDOTBS1"

Instance_number = 1

Remote_login_passwordfile= "EXCLUSIVE"

Db_domain = ""

Dispatchers = "(PROTOCOL=TCP) (SERVICE=racXDB)"

Remote_listener = "scan:1521"

Audit_file_dest = "/ opt/rac/oracle/admin/rac/adump"

Audit_trail = "DB"

Db_name = "rac"

Open_cursors = 300

Diagnostic_dest = "/ opt/rac/oracle"

Cluster communication is configured to use the following interface (s) for this instance

10.10.10.10

Cluster interconnect IPC version:Oracle UDP/IP (generic)

IPC Vendor 1 proto 2

Sat Apr 28 20:50:38 2012

PMON started with pid=2, OS id=16042

Sat Apr 28 20:50:38 2012

VKTM started with pid=3, OS id=16044 at elevated priority

VKTM running at (10) millisec precision with DBRM quantum ms

Sat Apr 28 20:50:39 2012

GEN0 started with pid=4, OS id=16048

Sat Apr 28 20:50:39 2012

DIAG started with pid=5, OS id=16050

Sat Apr 28 20:50:39 2012

DBRM started with pid=6, OS id=16052

5. Summary

Being familiar with the location and function of log files in Oracle cluster environment helps to quickly locate the location of the fault and make good use of it.

ORA-29780: unable to connect GPnP daemon [CLSGPNP_ERR]

After installing 11GR2 Grid, you encountered the following error when creating a disk group using asmca:

Started getting following error

ORA-29780: unable to connect to GPnP daemon [CLSGPNP_ERR]

Google is related to environment variables: (CRS/GRID is working properly).

Grid@rac1 / oragrid/dbs > env | grep ORA

GRID_HOME=/opt/11.2.0/grid

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.