Managing Databases using Enterprise Manager (MOSC)

MOSC Banner

Invalid Server or Client Wallet Password Error when OEM connects with TCPS

in Managing Databases using Enterprise Manager (MOSC) 1 commentAnswered

We are using OEM 13.5. In updating our databases to using TLS, we're also converting OEM to communicate with these databases over TLS. We are going to the database in OEM, clicking Oracle Database->Target Setup->Monitoring Configuration, then changed the port and protocol to our TLS listener endpoint. When clicking Test Connection, we're receiving the following error: "Invalid Server or Client Wallet Password." Both the OMS and the database have auto-login wallets, so it shouldn't be trying to do anything with wallet passwords.

I am pretty sure the OMS wallet has the intermediate and root certificate the database we are trying to connect to uses. Are there any emctl commands that could check that? Or perhaps where the wallet goes after I secure the OMS with it? If it's maybe missing those trusted certs, how would I push the root and intermediate trusted certs to the OMS?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center