CRS 10gR2/ 11gR1/ 11gR2 Diagnostic 收集指导
Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.2.0.2 - Release: 10.2 to 11.2
Oracle Server - Standard Edition - Version: 10.2.0.1 to 11.2.0.2 [Release: 10.2 to 11.2]
Information in this document applies to any platform.
Oracle Clusterware
目的
注释日志应该上传诊断Oracle Clusterware问题
解决办法
1. 总是使用远程诊断代理Note:314422.1提供节点信息
2. 保证系统日志是RDA的一部分,它通常是RDA的一部分如果RDA作为系统管理员运行,如果不是,请确保提供系统日志。
3. 如果你在运行root.sh时获得错误,请确保/tmp/crsctl.* files 被提供给分析员
4. 从$ORA_CRS_HOME用root运行以下命令
* $script /tmp/diag.log
* $env
* $id
* $cd $ORA_CRS_HOME/bin
* For 10gR2
设置变量
o Ensure that the environment variable ORA_CRS_HOME is set to the CRS home
o Ensure that the environment variable ORACLE_BASE is set
o Ensure that the environment variable HOSTNAME is set to the name of the host.
o $./diagcollection.pl -collect
* For 11gR1
o Execute diagcollection.pl by passing the crs_home as the following
o export ORA_CRS_HOME=/u01/crs
o $ORA_CRS_HOME/bin/diagcollection.pl -crshome=$ORA_CRS_HOME --collect
* For 11gR2
o Execute /bin/diagcollection.sh
将会在11gR2附加创建crsData_.tar.gz, ocrData_.tar.gz, oraData_.tar.gz and basData_.tar.gz,将会有os_.tar.gz和ipd_
5. 如果供应商集群产品被使用则上传供应商集群产品的日志
6. 如果没有被使用则上传oprocd 日志,在大多数平台上/var/opt/oracle/`hostname`/中能找到
7. 如果CRS被安装,那么运行如下选项(6a),而不是(6b)并且上传生成的cluvfy.log
(6a) CRS has been installed.
* cd $ORACLE_HOME/bin
* script /tmp/cluvfy.log ### run the following as oracle software owners id
* cluvfy stage -post crsinst -n all -verbose
* exit
(6b) CRS has not been installed.
* run runcluvfy.sh from the 10gR2 DVD or download cluvfy from OTN http://www.oracle.com/technology/products/database/clustering/cvu/cvu_do...
* set the environment variables CV_HOME to point to the cvu home, CV_JDKHOME to point to the JDK home and an optional CV_DESTLOC pointing to a writeable area on all nodes (e.g /tmp/cluvfy)
* cd $CV_HOME
* script cluvfy.log
* cluvfy stage -pre crsinst -n ## Replace node1,node2 with actual node names
* exit
请保证来自所有节点的以上信息被提供
新diagcollection.pl的特性
一个版本的全部详细特性的列表,通过帮助选项运行diagcollection,diagcollection的效用是和介绍一些新的详细地特性的设计来减少上传给分析员的日志或者跟踪文件的的大小。
* --nocore This option significantly reduces the size of the final file by excluding the core files
* --coreanalyze This option uses the OS specific debugger to get a stack from the core dump.
如果有许多内核文件,可能得一会时间
介绍一项附加的特性来减少诊断文件的大小,同11.1.0.x,启动,可能传输afterdatevar到diagcollection
这个选项将会在通过afterdatevar数据精细化后收集文件。
对于windows 环境而言
在命令窗口设置如下变量
ORACLE_HOME, ORA_CRS_HOME and ORACLE_BASE
set ORACLE_HOME=D:\oracle\ora102db
set ORA_CRS_HOME=D:\oracle\ora102crs
set ORACLE_BASE=D:\oracle
- it may be necessary to add perl to the PATH before running diagcollection.pl
The syntax for this is:
set PATH=%PATH%;
set PATH=%PATH%;E:\app\Administrator\product\11.1.0\db_1\perl\5.8.3\bin\MSWin32-x86-multi-thread
- Run the appropriate diagcollection.pl command.
%ORA_CRS_HOME%\bin\diagcollection.pl --collect
请注意diagcollection.pl的collects .log 文件,如果问题不是在当前的这个ocssd.log中那么请同diagcollection.pl收集到的文件一起上传ocssd.l0X和crsd.l0X文件。