Issue:
Oracle E-business suite R12.2 Upgrade File System Pre-install check Failed for :
-------------------ADX Database Utility Finished--------------- DB Version Check has failed. Not able to check the Database version. Please make sure the Database is at 11.2.0.3 or higher DB service_names Check has failed. Not able to check if ebs_patch as an entry exists in Database service_name parameter. Existing DB SID validation has failed. Connection to database failed. Unable to validate the current SID
Error in Log File: /tmp/06130314/06130314.log
---------------------------------------------------------------
ADX Database Utility
---------------------------------------------------------------
getConnection() -->
sDbHost : h2hdba
sDbDomain : dba.com
sDbPort : 1524
sDbSid : VISION
sDbUser : APPS
Trying to connect using SID...
getConnectionUsingSID() -->
JDBC URL: jdbc:oracle:thin:@h2hdba.dba.com:1524:VISION
Exception occurred: java.sql.SQLException: ORA-28040: No matching authentication protocol
Trying to connect using SID as ServiceName
getConnectionUsingServiceName() -->
JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=h2hdba.dba.com)(PORT=1524))(CONNECT_DATA=(SERVICE_NAME=VISION)))
Exception occurred: java.sql.SQLException: ORA-28040: No matching authentication protocol
Trying to connect using SID as ServiceName.DomainName
getConnectionUsingServiceName() -->
JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=h2hdba.dba.com)(PORT=1524))(CONNECT_DATA=(SERVICE_NAME=VISION.dba.com)))
Exception occurred: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=h2hdba.dba.com)(PORT=1524))(CONNECT_DATA=(SERVICE_NAME=VISION.dba.com)))
Connection could not be obtained; returning null
Cause:
DB Connectivity Issue.
The issue is caused by the default setting for allowed logon version in the Oracle 12c database.
Note that the SQLNET.ALLOWED_LOGON_VERSION parameter has been deprecated in 12c.
The parameter has been replaced with:
SQLNET.ALLOWED_LOGON_VERSION_SERVER
Solution:
To resolve the database connectivity issue, perform the following steps :
1. Review the sqlnet_ifile.ora or sqlnet.ora file and confirm the following entries are present:
SQLNET.ALLOWED_LOGON_VERSION_SERVER 2. Update the sqlnet_ifile.ora or sqlnet.ora settings for the above parameters to the lowest version level that is required in your environment. For example: a) If the initialization parameter SEC_CASE_SENSITIVE_LOGON is set to FALSE: SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8 b) If SEC_CASE_SENSITIVE_LOGON is set to TRUE SQLNET.ALLOWED_LOGON_VERSION_SERVER = 10
After this Database connectivity issue should be resolved.
Modify the service_names parameter to include ebs_patch as shown below and retry.
SQL> sho parameter service NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ service_names string ORCL SQL> alter system set service_names='ORCL','ebs_patch' scope=both ; System altered. SQL> sho parameter service NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ service_names string ORCL, ebs_patch
No comments:
Post a Comment