Autoconfig failed with invalid login

[satish]

Dear erman,


We  have applied below patches in R12.1.3 instance. DB is 11.1.0.7

 

Latest AD patch 23569686 R12.AD.B.delta.8

Latest Autoconfig Patch 27135427 R12.TXK.B.delta.4

Latest Rapid Clone consolidated patch 27102203 OAM

 

After applying patches and while running autoconfig.

 

---------------------------------------------------------------

ADX Database Utility

---------------------------------------------------------------

 

getConnectionUsingAppsJDBCConnector() -->

APPS_JDBC_URL='jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=ssshostname.ssst.org)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=SSSEBSTR)))'

Trying to connect using APPS_JDBC_URL

Exception occurred: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

 

Trying to get connection using SID based connect descriptor

getConnection() -->

sDbHost : ssshostname

sDbDomain : ssst.org

sDbPort : 1521

sDbSid : SSSEBSTR

sDbUser : APPS

Trying to connect using SID...

getConnectionUsingSID() -->

JDBC URL: jdbc:oracle:thin:@ssshostname.ssst.org:1521:SSSEBSTR

Exception occurred: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

 

Trying to connect using SID as ServiceName

getConnectionUsingServiceName() -->

JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ssshostname.ssst.org)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=SSSEBSTR)))

Exception occurred: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

 

Trying to connect using SID as ServiceName.DomainName

getConnectionUsingServiceName() -->

JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ssshostname.ssst.org)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=SSSEBSTR.ssst.org)))

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

 

Connection could not be obtained; returning null

 

-------------------ADX Database Utility Finished---------------

 

Exception occurred while preseeding variables in the context file: java.sql.SQLException: Could not get connection to the database

 

 

StackTrace:

java.sql.SQLException: Could not get connection to the database

at oracle.apps.ad.tools.configuration.CVMHelper.processNewContextFile(CVMHelper.java:935)

at oracle.apps.ad.context.CtxValueMgt.preSeed2Ctx(CtxValueMgt.java:1825)

at oracle.apps.ad.context.CtxValueMgt.processCtxFile(CtxValueMgt.java:1620)

at oracle.apps.ad.context.CtxValueMgt.main(CtxValueMgt.java:763)

 


Apps Jdbc url poiting to : (ADDRESS=(PROTOCOL=tcp)(HOST=ssshostname.ssst.org)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=SSSEBSTR) connection sting.

 

1)checked service name : SERVICE_NAME=SSSEBSTR is running in DB node and accepting connections.

 

SSSEBSTR is running on dbnode. We are able to connect with apps user to db from apps and db node.

 
Database service and listener is working fine.

 

And once again restarted listener and retested the issue. Still, we are getting the same error

 

[oracrp@ssshostname ~]$ lsnrctl status SSSEBSTR

 

LSNRCTL for Linux: Version 11.1.0.7.0 - Production on 06-MAY-2022 11:38:12

 

Copyright (c) 1991, 2008, Oracle. All rights reserved.

 

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=ssshostname.ssst.org)(PORT=1521)))

STATUS of the LISTENER

------------------------

Alias SSSEBSTR

Version TNSLSNR for Linux: Version 11.1.0.7.0 - Production

Start Date 06-MAY-2022 11:29:58

Uptime 0 days 0 hr. 8 min. 14 sec

Trace Level off

Security ON: Local OS Authentication

SNMP OFF

Listener Parameter File /u02/TEST/db/tech_st/11.1.0/network/admin/SSSEBSTR_ssshostname/listener.ora

Listener Log File /u02/TEST/db/tech_st/11.1.0/admin/SSSEBSTR_ssshostname/diag/tnslsnr/ssshostname/sssebstr/alert/log.xml

Listening Endpoints Summary...

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ssshostname.SSST.ORG)(PORT=1521)))

Services Summary...

Service "SSSEBSTR" has 2 instance(s).

Instance "SSSEBSTR", status UNKNOWN, has 1 handler(s) for this service...

Instance "SSSEBSTR", status READY, has 1 handler(s) for this service...

Service "SSSEBSTR_XPT" has 1 instance(s).

Instance "SSSEBSTR", status READY, has 1 handler(s) for this service...

The command completed successfully



[oracrp@ssshostname ~]$ sqlplus apps/******@SSSEBSTR

 

SQL*Plus: Release 11.1.0.7.0 - Production on Fri May 6 11:38:56 2022



Any suggestions please

=====-----=====-----=====

[ErmanArslansOracleBlog]

You got an invalid user pass error. It is an ORA- error directly coming from the database. So it is a pure db error.. So it reaches the database but got the invalid user pass error.. Dont worry about that ORA-12514.. It just tries with a different conn string when it fails in the other attempts..

That may be due to some characters in your apps password.. -- given that your db version is a very old one..
Also check the db parameter named -> SEC_CASE_SENSITIVE_LOGON..

Bytheway, I see you re doing some checks using sqlplus.. Use the apps node for those test.. Use the sqlplus from the apps node and see whether or not you are able to connect to the database.

Read the documentation/Readme of those patches that you applied.. There may be additional actions that you need to perform.. We are dealing with a very old DB version here..

[satish]

Dear erman,

As suggested,we did tests from app node and it worked.By the way, SEC_CASE_SENSITIVE_LOGON..  is false before and after applying the patches.

Thanks,
Satish

[ErmanArslansOracleBlog]

That may be caused by the SQLNET.ALLOWED_LOGON_VERSION (SQLNET.ALLOWED_LOGON_VERSION_SERVER & SQLNET.ALLOWED_LOGON_VERSION_CLIENT) setting.. Please check the sqlnet.ora for this.

[satish]

These parameters are not there in sqlnet.ora


(SQLNET.ALLOWED_LOGON_VERSION_SERVER & SQLNET.ALLOWED_LOGON_VERSION_CLIENT

[ErmanArslansOracleBlog]

1)Did you follow "Applying the Latest TXK Release Update Pack to Oracle E-Business Suite Release 12.1 (Doc ID 2421143.1)" for this task?
2) Did you apply the following patches as documented in the MOS note above? --Section 2: Apply Additional Critical Patches
Patch 29522970:R12.TXK.B
Patch 28685719:R12.TXK.B
Patch 23645824:R12.TXK.B
3)Is this a db tier autoconfig or apps tier autoconfig?
4)If it is the db tier autoconfig -> Did you rebuild the appsutil using the admkappsutil.pl and send it to the database tier?