TROUBLESHOOT OVERVIEW
This section describes how to troubleshoot OBDX setup.
Invalid database password
This topic contains troubleshooting information if you receive an error when attempting to connect to the database server.
If you get the following error:
Try one of the following:
- Verify that the database is running.
- Check Network connectivity between Weblogic Server and Database server.
- Check the database configuration in installer.properties file
- Verify that the entered password is correct.
cx_oracle module
This topic contains troubleshooting information about problems with cx_Oracle python module.
If you get the following error:
Execute the below command:
export LD_LIBRARY_PATH=/usr/lib/oracle/12.2/client64/lib:$LD_LIBRARY_PATH
python
import cx_Orace
cx_Oracle.__version
Failed Database Scripts
This topic contains troubleshooting information in case of database script failures.
If you get the following error in DB_installation.log:
Check the detailed log of the failed SQL file at <OBDX INSTALLER DIR>/ExecInstances/<DDMonthHHMM>/logs/db folder.
Failure of Policy Seeding
This topic contains troubleshooting information if policy seeding fails during installation.
If you get the following error:
Try one of the following:
- Check if Entitlement.log is created on following path <OBDX INSTALLER DIR>/ExecInstances/<DDMonthHHMM>/logs/db/ and contains any SEVERE errors for Entitlement policy seeding.
- Check if Task.log is created on following path <OBDX INSTALLER DIR>/ExecInstances/<DDMonthHHMM>/logs/db/ and contains any SEVERE errors for Task policy seeding.
Check the seedPolicies.log in <OBDX INSTALLER DIR>/ExecInstances/<DDMonthHHMM>/logs/db/ directory if itcontains any runtime errors generated during execution of the policies Seeding in OBDX schema
Fix the problem by following below steps:
- Login to OBDX installer server
- Browse to <OBDX INSTALLER DIR>\ installables\policies
- Edit Entitlement_log4j.properties & Task_log4j.properties . Replace <logs_path> with directory where policy seeding logs will be generated
For example:
- Run below command manually if “SEVERE” error logs are found in Task.log
java -jar -Djava.util.logging.config.file='<logs.properties>’ com.ofss.digx.utils.feed.data.task.jar "Task.csv" "INS-oracle.jdbc.OracleDriver,<OBDX Schema name>,<OBDX Schema password>,jdbc:oracle:thin:@<OBDX DB hostname or IP>:<OBDX DB listener port>/<OBDX Service Name>"
For example:
java -jar -Djava.util.logging.config.file='Task_log4j.properties’ com.ofss.digx.utils.feed.data.task.jar ‘Task.csv’ "INS-oracle.jdbc.OracleDriver,OBDX_THP181,Welcome#1,jdbc:oracle:thin:@10.44.169.255:1521/OBDX"
- Run below command manually if “SEVERE” error logs are found in Entitlement.log
java -jar -Djava.util.logging.config.file='<logs.properties>’ com.ofss.digx.utils.entitlement.feed.data.jar ‘Resources.csv,Entitlement.csv,Day0Policy.csv’ 'OBDX' "INS-oracle.jdbc.OracleDriver,<OBDX Schema name>,<OBDX Schema password>,jdbc:oracle:thin:@<OBDX DB hostname or IP>:<OBDX DB listener port>/<OBDX Service Name>"
For example:
java -jar -Djava.util.logging.config.file='Entitlement_log4j.properties’ com.ofss.digx.utils.entitlement.feed.data.jar ‘‘Resources.csv,Entitlement.csv,Day0Policy.csv’ ‘OBDX’ "INS-oracle.jdbc.OracleDriver,OBDX_THP181,Welcome#1,jdbc:oracle:thin:@10.44.169.255:1521/OBDX"
- Post successfully execution, restart Managed server.