Infrastructure at your Service

Working on Enterprise Manager 12.1.0.4 version at a client’s site, we would like to know if oracle database target in 18c version could be discovered and monitored, even if Enterprise Manager 12.1.0.4 does not support Oracle 18c database targets.

Installing the agent 12c on the target host did not cause any problem, the oracle database 18c discovery ran successfully, but the database was seen as down in the Enterprise Manager 12.1.0.4 console.

We tried several tricks without any positive results, but running the following command shows us that this was a connection problem:


[email protected]:/home/oracle/:> emctl getmetric agent DB18,oracle_database,Response
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation.
All rights reserved.
Status,State,oraerr,Archiver,DatabaseStatus,ActiveState0,UNKNOWN,
Failed to connect: java.sql.SQLException: 
ORA-28040: No matching authentication protocol,UNKNOWN,UNKNOWN,UNKNOWN

With Oracle 18c, the default value for SQLNET.ALLOWED_LOGON_VERSION parameter is 12, it means that database clients using pre-12c jdbc thin drivers cannot authenticate to 18c database servers.

The workaround is to add in the database server sqlnet.ora the following lines:

SQLNET.ALLOWED_LOGON_VERSION_SERVER=11
SQLNET.ALLOWED_LOGON_VERSION_CLIENT=11

We restart the database and the agent, and the Oracle database 18c is displayed up and running in Enterprise Manager 12.1.0.4:

Some more tests showed us that everything is working fine: incident management, performance, top activity ..aso

Nevertheless do not forget that oracle database target version 18c are not supported with Enterprise Manager 12.1.0.4. I will recommand to use the last Enterprise Manager 13.3 last version in order to administer and monitor Oracle database 18c.

3 Comments

  • David says:

    Great article. I learned something new. I have a oem 12c5 environment and wanted to monitor and manage a 12.2 DataGuard environment. I was able to discover the environment, but just as had happened with the client case you reported above, the database status showed as down. When I get back home from vacation, I’m going to try the sqlnet.ora entries you listed above. Thanks for this post – David

  • David says:

    Great post. I ran nto the same issue, but experienced a different result. I have a OEM 12.1.0.5 environment with a 12.1.0.2 Repository. I have a target database that’s 12.2.0.1. I successfully discovered and promoted the DB, but the status shows as Down. I added the two sqlnet.ora statements you recommended, but the DB still shows as Down and now I get the following error from emctl getmetric agent PRIMEDB.localdomain,oracle_database,Response:
    Oracle Enterprise Manager Cloud Control 12c Release 5
    Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
    Status,State,oraerr,Archiver,DatabaseStatus,ActiveState
    0,UNKNOWN,Failed to connect: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
    ,UNKNOWN,UNKNOWN,UNKNOWN

    Any idea why this is happening?

  • David says:

    Never mind. I figured it out.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Pierre Sicot
Pierre Sicot

Senior Consultant