Error 'Invalid Client or Server wallet' when testing the Monitoring Configuration of Target DB over TCPS
(Doc ID 2463134.1)
Last updated on JULY 13, 2022
Applies to:
Enterprise Manager for Oracle Database - Version 13.2.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Target Database is configured for Monitoring over TCPS.Updated the Moniotoring Configuration of the target database on EM console and changed 'Connection Protocol' to TCPS.
When trying to Test Connection , error below is popped up
'Invalid Client or Server wallet'
Error below is logged in <EM INSTANCE HOME>/em/EMGC_OMS1/sysman/log/emoms.trc
JDBC SSL Connection Error: PKIX Path Failed, Path Does Not Chain With Any Of The Trust Anchors with Oracle Wallet
or
Failed to connect: java.sql.SQLRecoverableException: IO Error: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors
or
Failed to connect: java.sql.SQLRecoverableException: IO Error: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors
On the Monitoring Agent Home on the target server, Error below is logged in <AGENT INSTANCE HOME>/sysman/log/gcagent_sdk.trc file
Failed to connect: java.sql.SQLRecoverableException: IO Error: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |