As 'oracle' on each target server...
mkdir -p /u01/dba/LMS/CT_outputmkdir -p /u01/dba/LMS/CT_tmpscp -pr ${PATCH_SERVE}:/u01/dba/LMS/Oracle_Collection_Tool.zip /u01/dba/LMSecho "scp -pr /u01/dba/LMS/Oracle_Collection_Tool.zip $(hostname):/u01/dba/LMS"cd /u01/dba/LMSunzip Oracle_Collection_Tool.zipchmod -R +x CollectionAs 'root' on each target server...
cd /u01/dba/LMS/Collection/bin./Collection.sh -o /u01/dba/LMS/CT_output -L Y -p DB,CPUQ -t /u01/dba/LMS/CT_tmp-L Y indicates that you accept the license agreement. Omit this option if you wish to read the license agreement before accepting it.Once the Collection.sh script is complete, you should have two bz2 files in your output directory. You should consolidate the resultant bz2 files and send them to the LMS consultant, or review them yourself (see below).
To consolidate (as 'root')...
chown oracle /u01/dba/LMS/CT_output/*.bz2sudo -u oracle scp -pr /u01/dba/LMS/CT_output/*.bz2 ${PATCH_SERVE}:/u01/dba/LMS/CT_consolidatedecho "scp -pr $(hostname):/u01/dba/LMS/CT_output/*.bz2 /u01/dba/LMS/CT_consolidated"root is not in the sudoers file", simply login as 'oracle' and run...scp -pr /u01/dba/LMS/CT_output/*.bz2 eugsl-l-oem001:/u01/dba/LMS/CT_consolidatedThe file starting with "Collection" contains the results of the collection. Use the following command to extract the files...
gtar -xjvf Collection*.tar.bz2The .txt file under /u01/dba/LMS/CT_output/CPUQ is a good place to start.
This includes things like lparstat -i output which shows processor allocations.
The .csv files are best viewed in a spreadsheet or Python in a GUI environment.
The file under /u01/dba/LMS/CT_output/DBA_FUS shows database feature usage.
The files under /u01/dba/LMC/CT_output/DB include...
_dba_feature.csv _oraproducts.csv _session.csv _version.csv_license.csv _parameter.csv _summary.csv _v_option.csv_options.csv _segments.csv _users.csvThe file starting with "debug" contains the log files from the collection.
Use the following command to extract the files...
gtar -xjvf debug*.tar.bz2ORA-00942
ORA-00942: table or view does not existIn most cases this error can be ignored. The scripts will attempt to retrieve information about options that may not be installed.
CT-02801
DB: CT-02801: WARNING: CPUQ information is needed for Host: myhostname.com running Database Instance: ORCL1In this case the warning seems to be because the script has trimmed the domain from the hostname. I.e. it has collected the correct data but thinks it has not due to the difference in hostname with domain vs without. The content of the CPUQ_collected.log supports this theory...
CPUQ: CT-01000: COLLECTED: Machine Name: myhostnameAs 'oracle' on each target server...
scp -pr ${PATCH_SERVE}:/u01/dba/LMS/HW_CPUQuery.zip /u01/dba/LMSecho "scp -pr /u01/dba/LMS/HW_CPUQuery.zip $(hostname):/u01/dba/LMS"cd /u01/dba/LMSunzip HW_CPUQuery.zipAs 'root' on each target server...
cd /u01/dba/LMS/HW_CPUQuery/CPU_Query_Unixchmod u+x lms_cpuq.sh./lms_cpuq.shchown oracle /tmp/$(hostname -s)-lms_cpuq.txtsudo -u oracle scp -pr /tmp/$(hostname -s)-lms_cpuq.txt ${PATCH_SERVE}:/u01/dba/LMS/HW_CPU_consolidatedecho "scp -pr $(hostname):/tmp/$(hostname -s)-lms_cpuq.txt /u01/dba/LMS/HW_CPU_consolidated"root is not in the sudoers file", simply login as 'oracle' and run...scp -pr /tmp/$(hostname -s)-lms_cpuq.txt ${PATCH_SERVE}:/u01/dba/LMS/HW_CPU_consolidatedRefer to the documentation provided by Oracle.
The aim is to stage a zip file on ${PATCH_SERVE} that can be used according to the instructions in this document.
Stage the files in /u01/dba/LMS on ${PATCH_SERVE} and update this document accordingly.