Troubleshooting and Best Practices for dr_validate.sh in DX NetOps
Article ID: 451932
Updated On:
Products
Issue/Introduction
This article provides best practices, common troubleshooting steps, and error resolution for the dr_validate.sh script used in
DX NetOps Data Repository installations and upgrades.
Use this guide to prepare your environment and resolve validation failures.
Environment
* DX NetOps Performance Management (Data Repository)
* All supported releases
Cause
Validation failures during dr_validate.sh execution typically arise from configuration mismatches, permission restrictions, or connectivity errors within the database cluster.
Resolution
To ensure successful execution of `dr_validate.sh`, perform the following steps:
- **Verify Database Credentials:**
Ensure the `drinstall.properties` file contains the correct database username (`dradmin`) and password. A common error is a duplicated password entry (e.g., `DbPwd=DbPwd=`), which causes authentication failures.
- **Check SSH Configuration:**
If the script fails after providing the root password or reports "Permission denied":
* Edit `/etc/ssh/sshd_config` and ensure `PermitRootLogin yes` is set.
* Restart the SSH service: `systemctl restart sshd`.
- **Schema Table Validation:**
The `dr_validate.sh` script performs core environment and ETL health checks. For custom schema validation (such as checking for `dauser` existence), ensure your environment is configured correctly. If you encounter missing table errors, manual database verification may be required using:
`psql -d <database_name> -c "SELECT to_regclass('dauser') IS NOT NULL;"`
- **Review Logs:**
If validation fails, check the detailed logs located in:
`/IMDataRepository_vertica/logs/`
For ETL-specific issues, check:
`/tmp/etlHealthLog.txt`
Additional Information
Feedback
