ERROR MESSAGE: The dr_validate shows this near the end of it's run.
Database is running and available for connectivity verification. ........[ OK ]
Validating connection to database host: <node001>
vsql: FATAL 2248: Authentication failed for username "dradmin"
Verifying database connection properties. failed ........................[FAIL]
Validating connection to database host: <node002>
vsql: FATAL 2248: Authentication failed for username "dradmin"
Verifying database connection properties. failed ........................[FAIL]
Validating connection to database host: cplcdb03
vsql: FATAL 2248: Authentication failed for username "dradmin"
Verifying database connection properties. failed ........................[FAIL]
Checking existing DB for ETL health.
vsql: FATAL 2248: Authentication failed for username "dradmin"
SYMPTOMS:
Database connectivity verification fails during validation
Authentication errors occur for the dradmin account
The script reports schema not found and ends with fatal errors
CONTEXT: Occurs when running the pre-upgrade validation script on the database cluster․
IMPACT: Prevents successful validation and blocks the product upgrade process․
The configuration file contained a duplicated password variable, causing the script to pass an improperly formatted string during database authentication․
It showed as "DbPwd=DbPwd=<passwd>" where it should be "DbPwd=<passwd>".
PREREQUISITES:
Administrator access to the database host
Access to modify installation properties
STEPS:
1․ EDIT CONFIGURATION FILE
Path: /opt/CA/IMDataRepository_vertica<release>/drinstall․properties
Update the password variable to remove the duplicated entry․
EXPECTED: File saves successfully with the corrected format․
2․ RE-RUN VALIDATION SCRIPT
Command: dr_validate․sh
EXPECTED: Validation completes successfully without authentication errors․