ORACLE 19C 数据库的目录结构及日志路径

Grid Infrastructure(GI),集群软件是搭建RAC的基础,是RAC逻辑层次当中的集群层,是RAC重要的组成部分,同样也是RAC高可用性的保障。GI包含两个最主要的组件:Clusterware集群软件和ASM存储软件。Clusterware是Oracle的集群解决方案,ASM是Oracle的存储解决方案,这两大方案的数据库共同构成了RAC高可用解决方案。
相对于Oracle单实例来说,部署安装和维护GI都增加了难度,尤其在日常的维护和故障处理过程中,各种日志的查看更加重要,本文主要对Oracle 19c 下的目录结构和路径进行介绍和说明。

  1. GI软件的安装目录是
[grid@dkf diag]$ echo $ORACLE_HOME/
/u01/app/19.3.0/grid/
  1. GI集群的目录结构:
    注:当前目录/u01/app/grid/diag
.
├── afdboot
├── apx
├── asm
│   └── +asm
│       ├── +ASM
│       │   ├── alert
│       │   │   └── log.xml
│       │   ├── cdump
│       │   ├── hm
│       │   ├── incident
│       │   ├── incpkg
│       │   ├── ir
│       │   ├── log
│       │   │   ├── attention
│       │   │   ├── attention.log
│       │   │   ├── ddl
│       │   │   ├── debug
│       │   │   ├── hcs
│       │   │   ├── imdb
│       │   │   └── test
│       │   ├── metadata
│       │   │   ├── ADR_INTERNAL.mif
│       │   ├── metadata_dgif
│       │   ├── metadata_pv
│       │   ├── stage
│       │   ├── sweep
│       │   └── trace
│       │       ├── alert_+ASM.log
│       │       └── cdmp_20220614104538
│       └── i_1.mif
├── asmcmd
│   ├── user_grid
│   │   └── dkf
│   │       ├── alert
│   │       │   └── alert.log
│   │       └── trace
│   └── user_oracle
│       └── dkf
│           ├── alert
│           │   └── alert.log
│           └── trace
├── asmtool
│   └── user_grid
│       └── host_626160142_110
│           ├── alert
│           │   └── log.xml
│           ├── cdump
│           ├── incident
│           ├── incpkg
│           ├── log
│           │   ├── attention
│           │   ├── debug
│           │   └── test
│           ├── metadata
│           ├── metadata_dgif
│           ├── metadata_pv
│           ├── stage
│           ├── sweep
│           └── trace
│               └── alert.log
├── bdsql
├── clients
│   └── user_grid
│       └── host_626160142_110
│           ├── alert
│           │   └── log.xml
│           ├── cdump
│           ├── incident
│           ├── incpkg
│           ├── log
│           │   ├── attention
│           │   ├── debug
│           │   └── test
│           ├── metadata
│           ├── metadata_dgif
│           ├── metadata_pv
│           ├── stage
│           ├── sweep
│           └── trace
│               └── sqlnet.log
├── crs
│   └── dkf
│       └── crs
│           ├── alert
│           │   └── log.xml
│           ├── cdump
│           ├── incident
│           ├── incpkg
│           ├── log
│           │   ├── attention
│           │   ├── debug
│           │   └── test
│           ├── metadata
│           ├── metadata_dgif
│           ├── metadata_pv
│           ├── stage
│           ├── sweep
│           └── trace
│               ├── alert.log
├── diagtool
├── dps
├── em
├── gsm
├── ios
├── kfod
│   └── dkf
│       └── kfod
│           ├── alert
│           │   └── log.xml
│           ├── cdump
│           ├── incident
│           ├── incpkg
│           ├── log
│           │   ├── attention
│           │   ├── debug
│           │   └── test
│           ├── metadata
│           ├── metadata_dgif
│           ├── metadata_pv
│           ├── stage
│           ├── sweep
│           └── trace
│               ├── alert_+ASM.log
│               ├── alert_dkf006.log
├── lsnrctl
├── netcman
├── ofm
├── plsql
├── plsqlapp
├── rdbms
└── tnslsnr
    └── dkf
        └── listener
            ├── alert
            │   └── log.xml
            ├── cdump
            ├── incident
            ├── incpkg
            ├── log
            │   ├── attention
            │   ├── debug
            │   └── test
            ├── metadata
            ├── metadata_dgif
            ├── metadata_pv
            ├── stage
            ├── sweep
            └── trace
                └── listener.log

  1. Oracle集群件诊断日志文件存储在diag/目录中,GI中的每个组件在diag/目录中拥有各自的目录:看下跟日志相关的路径如下:
.
├── asm
│   └── +asm
│       ├── +ASM
│       │   ├── alert
│       │   │   └── log.xml
│       │   ├── log
│       │   │   ├── attention
│       │   │   └── attention.log
│       │   └── trace
│       │       ├── alert_+ASM.log
│       │       └── cdmp_20220614104538
│       └── i_1.mif
├── asmcmd
│   ├── user_grid
│   │   └── dkf
│   │       ├── alert
│   │       │   └── alert.log
│   │       └── trace
│   └── user_oracle
│       └── dkf
│           ├── alert
│           │   └── alert.log
│           └── trace
├── asmtool
│   └── user_grid
│       └── host_626160142_110
│           ├── alert
│           │   └── log.xml
│           └── trace
│               └── alert.log
├── clients
│   └── user_grid
│       └── host_626160142_110
│           ├── alert
│           │   └── log.xml
│           └── trace
│               └── sqlnet.log
├── crs
│   └── dkf
│       └── crs
│           ├── alert
│           │   └── log.xml
│           └── trace
│               └── alert.log
├── kfod
│   └── dkf
│       └── kfod
│           ├── alert
│           │   └── log.xml
│           └── trace
│               ├── alert_+ASM.log
│               └── alert_dkf006.log
└── tnslsnr
    └── dkf
        └── listener
            ├── alert
            │   └── log.xml
            └── trace
                └── listener.log

其中:
在19c中,日志路径发生了非常大的变化,与Oracle集群件相关的调试日志文件存储在/u01/app/grid/diag/crs/dkf/crs/trace目录中。

HAS的日志信息:

[grid@dkf trace]$ ls ohas*
ohasd_cssdagent_grid.trc   ohasd_oraagent_grid_2.trm  ohasd_oraagent_grid_5.trc  ohasd_oraagent_grid_7.trm    ohasd.trc
ohasd_cssdagent_grid.trm   ohasd_oraagent_grid_3.trc  ohasd_oraagent_grid_5.trm  ohasd_oraagent_grid.trc      ohasd.trm
ohasd_oraagent_grid_1.trc  ohasd_oraagent_grid_3.trm  ohasd_oraagent_grid_6.trc  ohasd_oraagent_grid.trm
ohasd_oraagent_grid_1.trm  ohasd_oraagent_grid_4.trc  ohasd_oraagent_grid_6.trm  ohasd_orarootagent_grid.trc
ohasd_oraagent_grid_2.trc  ohasd_oraagent_grid_4.trm  ohasd_oraagent_grid_7.trc  ohasd_orarootagent_grid.trm
[grid@dkf trace]$ 

OCSSD日志:

[grid@dkf trace]$ ls ocssd.*
ocssd.trc  ocssd.trm
[grid@dkf trace]$ 

EVMD

[grid@dkf trace]$ ls evm*
evmd.trc  evmd.trm  evmlogger.trc  evmlogger.trm
[grid@dkf trace]$ 
  1. 对于数据库的日志和ASM的日志,可以使用如下SQL在数据库或ASM实例中查看相应的目录:
select name,value from v$diag_info;

数据库

SQL> set line 500
SQL> set pagesize 500
SQL> col name for a30
SQL> col value for a100
SQL> select name,value from v$diag_info;

NAME                           VALUE
------------------------------ ----------------------------------------------------------------------------------------------------
Diag Enabled                   TRUE
ADR Base                       /u01/app/oracle
ADR Home                       /u01/app/oracle/diag/rdbms/dkf006/dkf006
Diag Trace                     /u01/app/oracle/diag/rdbms/dkf006/dkf006/trace
Diag Alert                     /u01/app/oracle/diag/rdbms/dkf006/dkf006/alert
Diag Incident                  /u01/app/oracle/diag/rdbms/dkf006/dkf006/incident
Diag Cdump                     /u01/app/oracle/diag/rdbms/dkf006/dkf006/cdump
Health Monitor                 /u01/app/oracle/diag/rdbms/dkf006/dkf006/hm
Default Trace File             /u01/app/oracle/diag/rdbms/dkf006/dkf006/trace/dkf006_ora_59261.trc
Active Problem Count           1
Active Incident Count          1
ORACLE_HOME                    /u01/app/oracle/product/19.3.0/dbhome_1

12 rows selected.

SQL> 

ASM实例:

SQL> set line 500
SQL> set pagesize 500
SQL> col name for a30
SQL> col value for a100
SQL> 
SQL> select name,value from v$diag_info;

NAME                           VALUE
------------------------------ ----------------------------------------------------------------------------------------------------
Diag Enabled                   TRUE
ADR Base                       /u01/app/grid
ADR Home                       /u01/app/grid/diag/asm/+asm/+ASM
Diag Trace                     /u01/app/grid/diag/asm/+asm/+ASM/trace
Diag Alert                     /u01/app/grid/diag/asm/+asm/+ASM/alert
Diag Incident                  /u01/app/grid/diag/asm/+asm/+ASM/incident
Diag Cdump                     /u01/app/grid/diag/asm/+asm/+ASM/cdump
Health Monitor                 /u01/app/grid/diag/asm/+asm/+ASM/hm
Default Trace File             /u01/app/grid/diag/asm/+asm/+ASM/trace/+ASM_ora_58845.trc
Active Problem Count           0
Active Incident Count          0
ORACLE_HOME                    /u01/app/19.3.0/grid

12 rows selected.

SQL> 
  1. 其实GI的日志也可以通过adrci工具进行查看:
    在grid用户下查看:
[grid@dkf diag]$ adrci

ADRCI: Release 19.0.0.0.0 - Production on Fri Dec 23 05:55:02 2022

Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.

ADR base = "/u01/app/grid"
adrci> show log

Choose the home from which to view diagnostic logs:

1: diag/asm/+asm/+ASM
2: diag/crs/dkf/crs
3: diag/clients/user_grid/host_626160142_110
4: diag/tnslsnr/dkf/listener
5: diag/asmtool/user_grid/host_626160142_110
6: diag/asmcmd/user_oracle/dkf
7: diag/asmcmd/user_grid/dkf
8: diag/kfod/dkf/kfod
Q: to quit

Please select option: 
  • 2
    点赞
  • 10
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
Oracle 19c提供了自动化备份工具RMAN(Recovery Manager),可以通过编写备份脚本自动备份数据库。以下是使用RMAN进行自动化备份的详细步骤和命令: 1. 创建备份脚本 在Oracle 19c系统中,可以使用任何文本编辑器(如vi、nano等)创建备份脚本。以下是一个备份脚本的示例: ``` run { allocate channel c1 type disk; backup as compressed backupset database plus archivelog; release channel c1; } ``` 该脚本包括了备份数据库和归档日志的命令。其中,`allocate channel`命令用于指定备份设备类型,例如磁盘(type disk)或磁带(type sbt)。`backup`命令用于备份数据库和归档日志。`compressed backupset`参数用于启用备份集压缩,可以减少备份文件的大小。`plus archivelog`参数用于备份归档日志。 2. 运行备份脚本 使用RMAN工具运行备份脚本。以下是命令示例: ``` rman target / catalog rman/rman@example.com cmdfile=backup_script.rman log=backup.log ``` 其中,`target`参数用于指定备份的目标数据库,`catalog`参数用于指定RMAN目录数据库的连接信息(如果使用了RMAN目录数据库)。`cmdfile`参数用于指定备份脚本文件路径,`log`参数用于指定备份日志文件名和路径。 3. 查看备份结果 备份完成后,可以查看备份日志文件以确认备份是否成功。以下是日志文件示例: ``` RMAN> run { 2> allocate channel c1 type disk; 3> backup as compressed backupset database plus archivelog; 4> release channel c1; 5> } 6> allocated channel: c1 channel c1: SID=11 device type=DISK Starting backup at 07-JAN-22 channel c1: starting compressed full datafile backup set channel c1: specifying datafile(s) in backup set input datafile file number=00001 name=/u01/app/oracle/oradata/orcl/system01.dbf input datafile file number=00002 name=/u01/app/oracle/oradata/orcl/sysaux01.dbf ... backup set complete, elapsed time: 00:02:53 channel c1: starting compressed archive log backupset channel c1: specifying archive log(s) in backup set input archive log thread=1 sequence=1 RECID=1 STAMP=1234567890 input archive log thread=1 sequence=2 RECID=2 STAMP=1234567891 ... backup set complete, elapsed time: 00:01:36 released channel: c1 RMAN> ``` 备份成功后,可以看到备份脚本中指定的设备类型、备份数据库和归档日志的时间和文件名等信息。 以上是使用RMAN进行自动化备份的基本步骤和命令。需要根据实际情况进行适当的调整和配置。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

kuifeng.dong

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值