• oracle 10g/11g 命令对照,日志文件夹对照


    

     oracle 10g/11g  命令对照,日志文件夹对照

     

     oracle 11g 中不再建议使用的命令

    Deprecated Command

    Replacement Commands

    crs_stat

    crsctl check cluster -all

    crsctl stat res -t

    crs_register

    crsctl add resource

    crsctl add type

    crsctl modify resource

    crsctl modify type

    crs_unregister

    crsctl stop resource

    crsctl modify resource resource_name -attr "AUTO_START=never"

    crs_start

    crsctl start resource

    crsctl start crs

    crsctl start cluster

    crs_stop

    crsctl stop resource

    crsctl stop crs

    crsctl stop cluster

    crs_getperm

    crsctl getperm resource

    crsctl getperm type

    crs_profile

    crsctl add resource

    crsctl add type

    crsctl status resource

    crsctl status type

    crsctl modify resource

    crsctl modify type

    crs_relocate

    crsctl relocate resource

    crs_setperm

    crsctl setperm resource

    crsctl setperm type

    crsctl check crsd

    crsctl check crs

    crsctl check cssd

    crsctl check css

    crsctl check evmd

    crsctl check evm

    crsctl debug res log resource_name:level

    crsctl set log

    crsctl set css votedisk

    crsctl add css votedisk

    crsctl delete css votedisk

    crsctl query css votedisk

    crsctl replace votedisk

    crsctl start resources

    crsctl start resource -all

    crsctl stop resources

    crsctl stop resource -all

     

     

     

     

     

     

     

     

     

     

     

     

    Oracle 10g Log Directory Structure in Cluster Ready Services
    To diagnose any problem, the first thing examined by Oracle Support are theinstallation log files. Anyone who knows anything about database administrationknows the importance of the dump directories (bdump, udump, and cdump).Similarly, each component in the CRS stack has its respective directoriescreated under the CRS home:

     

    Log location

    Comment

    $ORA_CRS_HOME/crs/log

    Contains trace files for the CRS resources.

    $ORA_CRS_HOME/crs/init

    Contains trace files of the CRS daemon during startup. Good place to start with any CRS login problems.

    $ORA_CRS_HOME/css/log  

    The Cluster Synchronization (CSS) logs indicate all actions such as reconfigurations, missed check-ins, connects, and disconnects from the client CSS listener. In some cases, the logger logs messages with the category of auth.crit for the reboots done by Oracle. This could be used for checking the exact time when the reboot occurred.

    $ORA_CRS_HOME/css/init

    Contains core dumps from the Oracle Cluster Synchronization Service daemon (OCSSd) and the process ID (PID) for the CSS daemon whose death is treated as fatal. If abnormal restarts for CSS exist, the core files will have the format of core.<pid>.

    $ORA_CRS_HOME/evm/log

    PID and lock files for EVM. Core files for EVM should also be written here.

    $ORA_CRS_HOME/evm/init

    PID and lock files for EVM. Core files for EVM should also be written here.

    $ORA_CRS_HOME/srvm/log

    Log files for Oracle Cluster Registry (OCR), which contains the details at the Oracle cluster level.

    $ORA_CRS_HOME/log

    Log files for Oracle Clusterware (known as the cluster alert log), which contains diagnostic messages at the Oracle cluster level. This is available from Oracle database 10g R2.

     

     




     

    Oracle 11g Log Directory Structure

    Locations of OracleClusterware Component Log Files

    Component

    Log File LocationFoot 1 

    Cluster Health Monitor (CHM)

    The system monitor service and cluster logger service record log information in following locations, respectively:

    Grid_home/log/host_name/crfmond

    Grid_home/log/host_name/crflogd

    Oracle Database Quality of Service Management (DBQOS)

    Oracle Database QoS Management Grid Operations Manager logs:

    Grid_home/oc4j/j2ee/home/log/dbwlm/auditing

    Oracle Database QoS Management trace logs:

    Grid_home/oc4j/j2ee/home/log/dbwlm/logging

    Cluster Ready Services Daemon (CRSD) Log Files

    Grid_home/log/host_name/crsd

    Cluster Synchronization Services (CSS)

    Grid_home/log/host_name/cssd

    Cluster Time Synchronization Service (CTSS)

    Grid_home/log/host_name/ctssd

    Grid Plug and Play

    Grid_home/log/host_name/gpnpd

    Multicast Domain Name Service Daemon (MDNSD)

    Grid_home/log/host_name/mdnsd

    Oracle Cluster Registry

    Oracle Cluster Registry tools (OCRDUMP, OCRCHECK, OCRCONFIG) record log information in the following location:Foot 2 

    Grid_home/log/host_name/client

    Cluster Ready Services records Oracle Cluster Registry log information in the following location:

    Grid_home/log/host_name/crsd

    Oracle Grid Naming Service (GNS)

    Grid_home/log/host_name/gnsd

    Oracle High Availability Services Daemon (OHASD)

    Grid_home/log/host_name/ohasd

    Oracle Automatic Storage Management Cluster File System (Oracle ACFS)

    Grid_home/log/host_name/acfsrepl

    Grid_home/log/host_name/acfsreplroot

    Grid_home/log/host_name/acfssec

    Grid_home/log/host_name/acfs

    Event Manager (EVM) information generated by evmd

    Grid_home/log/host_name/evmd

    Cluster Verification Utility (CVU)

    Grid_home/log/host_name/cvu

    Oracle RAC RACG

    The Oracle RAC high availability trace files are located in the following two locations:

    Grid_home/log/host_name/racg

    $ORACLE_HOME/log/host_name/racg

    Core files are in subdirectories of the log directory. Each RACG executable has a subdirectory assigned exclusively for that executable. The name of the RACG executable subdirectory is the same as the name of the executable.

    Additionally, you can find logging information for the VIP in Grid_home/log/host_name/agent/crsd/orarootagent_root and for the database in $ORACLE_HOME/log/host_name/racg.

    Server Manager (SRVM)

    Grid_home/log/host_name/srvm

    Disk Monitor Daemon (diskmon)

    Grid_home/log/host_name/diskmon

    Grid Interprocess Communication Daemon (GIPCD)

    Grid_home/log/host_name/gipcd

     

     

    Clusterware daemonlogs are all under <GRID_HOME>/log/<nodename>

    Structure under<GRID_HOME>/log/<nodename>:


    ----这样来看是不是更清楚一些


    alert<NODENAME>.log - look herefirst for most clusterware issues
    ./admin:
    ./agent:
    ./agent/crsd:
    ./agent/crsd/oraagent_oracle:
    ./agent/crsd/ora_oc4j_type_oracle:
    ./agent/crsd/orarootagent_root:
    ./agent/ohasd:
    ./agent/ohasd/oraagent_oracle:
    ./agent/ohasd/oracssdagent_root:
    ./agent/ohasd/oracssdmonitor_root:
    ./agent/ohasd/orarootagent_root:
    ./client:
    ./crsd:
    ./cssd:
    ./ctssd:
    ./diskmon:
    ./evmd:
    ./gipcd:
    ./gnsd:
    ./gpnpd:
    ./mdnsd:
    ./ohasd:
    ./racg:
    ./racg/racgeut:
    ./racg/racgevtf:
    ./racg/racgmain:
    ./srvm:

  • 相关阅读:
    windows wsl2 卸载应用
    windows wsl2中ubuntu安装pip3
    href="#"与href="javascript:void(0)"的区别
    JavaScript 变量提升
    虚拟机升级之后.ubuntu找不到网络解决办法
    javascript 全局变量和局部变量
    flask celery使用
    flask magokit使用
    flask 缓存使用
    Linux设置/删除环境变量方法
  • 原文地址:https://www.cnblogs.com/yutingliuyl/p/7081937.html
Copyright © 2020-2023  润新知