CRS diagnostic collection tool Mandatory argument 'crshome' is missing.

diagcollection.pl fails with mandatory argument 'crshome' is missing

# Usage:

# diagcollection --collect :: collects diagnostic information

#                --clean   :: cleans up diagnostic information archive

#                --coreanalyze   :: extracts diag info from core files

Run the diagcollection.pl script as the root user to collect diagnostic information from an Oracle Clusterware installation.

The additional information provides to oracle support services to resolve internal issues. When I try to collect crs logs using diagcollection.pl got the below error message.

diagcollection.pl fails with mandatory argument 'crshome' is missing

[root@linux1 bin]# ./diagcollection.pl collect

Production Copyright 2004, 2005, Oracle.  All rights reserved

Cluster Ready Services (CRS) diagnostic collection tool

diagcollection

    --collect

             [--crs] For collecting crs diag information

             [--oh]  For collecting oracle home diag information

             [--all] Default.For collecting all diag information.

             [--core] UNIX only. Does not package core files.

             [--afterdate] UNIX only. Collects archives from the specified date.

             [--crshome] Argument that specifies the CRS Home location

             NOTE:

             1. You can also do the following

                ./diagcollection.pl --collect --crs --oh

             2. ORACLE_HOME env variable needs to be set.

     --clean        cleans up the diagnosability

                    information gathered by this script

     --coreanalyze  UNIX only. Extracts information from core files

                    and stores it in a text file

[root@linux1 bin]# pwd

/u01/app/oracle/product/10.2.0/crs/bin

 [root@linux1 bin]# ./diagcollection.pl --collect

Production Copyright 2004, 2005, Oracle.  All rights reserved

Cluster Ready Services (CRS) diagnostic collection tool

Mandatory argument 'crshome' is missing.

As per oracle document this bug from 10.2.0.4 to 11.1.0.6. Tried the below workaround it was working fine.

 [root@linux1 bin]# pwd

/u01/app/oracle/product/10.2.0/crs/bin

 [root@linux1 bin]# export ORA_CRS_HOME=/u01/app/oracle/product/10.2.0/crs

 [root@linux1 bin]# ./diagcollection.pl --collect --crs --crshome $ORA_CRS_HOME

Production Copyright 2004, 2005, Oracle.  All rights reserved

Cluster Ready Services (CRS) diagnostic collection tool

The following CRS diagnostic archives will be created in the local directory.

crsData_linux1.tar.gz -> logs,traces and cores from CRS home. Note: core files will be packaged only with the -core option.

ocrData_linux1.tar.gz -> ocrdump, ocrcheck etc

coreData_linux1.tar.gz -> contents of CRS core files in text format

Collecting crs data

/bin/tar: Removing leading `/' from member names

Collecting OCR data

Collecting information from core files

[root@linux1 bin]# ./diagcollection.pl --clean --crs --crshome $ORA_CRS_HOME

Production Copyright 2004, 2005, Oracle.  All rights reserved

Cluster Ready Services (CRS) diagnostic collection tool

Cleaning up tar and gzip files

Done

Have a great day.. :)