This article explains what information and log files to collect and send to SAS Technical Support for troubleshooting execution failures of the verifyDB script.
Step 1: Collect Information about Your Deployed SAS® Solutions and SAS® Code Level
Collect the information about your deployed SAS® solutions and current SAS code level for further review by executing the following SETINIT procedure in your Base SAS® software:
proc setinit;
run;
To collect additional information (software releases, installed hot fixes, and so on), see SAS KB0036131, "Using the ViewRegistry Report and other methods to determine the SAS® 9.2 and later software releases and hot fixes that are installed."
Step 2: Enable verifyDB Debug Traces
Microsoft Windows operating environments:
1. Make a backup of the verifyDB.config file that resides in the SAS-configuration-directory\Applications\SASRiskGovernanceFrameworkAdministrativeTools\
dbscripts\ directory.
2. Append the following parameters to the verifyDB.config file:
log4j.category.com.sas.oprisk.framework=DEBUG
log4j.category.com.sas.oprisk.framework.server=DEBUG
UNIX operating environments:
- Make a backup of the verifyDB.config file that resides in the SAS-configuration-directory\Applications\SASRiskGovernanceFrameworkAdministrativeTools\
dbscripts\ directory. - Append the following parameters to the verifyDB.config file:
log4j.category.com.sas.oprisk.framework=DEBUG
log4j.category.com.sas.oprisk.framework.server=DEBUG
Step 3: Collect Log Files and Configuration Data
Collect the following log and configuration data for further review of the verifyDB script's execution failure by the SAS Technical Support Team.
Relevant verifyDB script log and configuration files:
- UNIX operating environments:
- SAS-configuration-directory/Lev1/Applications/SASRiskGovernanceFrameworkAdministrativeTools/
dbscripts/.java.login.config - SAS-configuration-directory/Lev1/Applications/SASRiskGovernanceFrameworkAdministrativeTools/
dbscripts/gemfire*.log - SAS-configuration-directory/Lev1/Applications/SASRiskGovernanceFrameworkAdministrativeTools/
dbscripts/verifyDB.log
If you have a multi-tiered SAS environment where middle-tier services are configured on a different node machine, collect the following files:
- SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_<*>/gemfire.log
- SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_<*>/gemfire-locator.sh
- SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_<*>/gemfire-start-locator-sas.sh
- Microsoft Windows operating environments:
- SAS-configuration-directory\Lev1\Applications\SASRiskGovernanceFrameworkAdministrativeTools\
dbscripts\.java.login.config - SAS-configuration-directory\Lev1\Applications\SASRiskGovernanceFrameworkAdministrativeTools\
dbscripts\gemfire*.log - SAS-configuration-directory\Lev1\Applications\SASRiskGovernanceFrameworkAdministrativeTools\
dbscripts\verifyDB.log
If you have a multi-tiered SAS environment where middle-tier services are configured on a different node machine, collect the following files:
- SAS-configuration-directory\Lev1\Web\gemfire\instances\ins_<*>\gemfire.log
- SAS-configuration-directory\Lev1\Web\gemfire\instances\ins_<*>\gemfire-locator.sh
- SAS-configuration-directory\Lev1\Web\gemfire\instances\ins_<*>\gemfire-start-locator-sas.sh
Relevant log and configuration files from the node machine for the middle-tier server:
-
- Under UNIX:
- the TAR file in SAS-configuration-directory/Lev1/Web/Logs/SASServer8_1
- SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer8_1/conf/server.xml
- the TAR file in SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer8_1/logs/*.log
- SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer8_1/logs/catalina.out
- SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer8_1/bin/setenv.sh
- the TAR file in SAS-configuration-directory/Lev1/Web/Logs/SASServer1_1
- SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/conf/server.xml
- the TAR file in SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/*.log
- SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/catalina.out
- SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/bin/setenv.sh
- SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_<*>/gemfire.log
- SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_<*>/gemfire-locator.sh
- SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_<*>/gemfire-start-locator-sas.sh
- SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/catalina.out
- Under Windows:
- the TAR file in SAS-configuration-directory\Lev1\Web\Logs\SASServer8_1
- SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer8_1\conf\server.xml
- the TAR file in SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer8_1\logs\*.log
- SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer8_1\logs\catalina.out
- SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer8_1\conf\wrapper.conf
- the TAR file in SAS-configuration-directory\Lev1\Web\Logs\SASServer1_1
- SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer1_1\conf\server.xml
- the TAR file in SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer1_1\logs\*.log
- SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer1_1\logs\catalina.out
- SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer1_1\conf\wrapper.conf
- SAS-configuration-directory\Lev1\Web\gemfire\instances\ins_<*>\gemfire.log
- SAS-configuration-directory\Lev1\Web\gemfire\instances\ins_<*>\gemfire-locator.sh
- SAS-configuration-directory\Lev1\Web\gemfire\instances\ins_<*>\gemfire-start-locator-sas.sh
Note: You can retrieve many of the files listed above by running the log-sweeper tool that is discussed in SAS Note 54813, "Using the PDATool for automated log, configuration data collection, and relevant health-check analysis for the deployed SAS® 9.4 environment services." Before you send the log-sweeper output to Technical Support, you must inventory the output and ensure that ALL of the files and logs listed above are found in the package.