Autoconfig Failing with error on Stansby node (EBS 12.2.7 with db 19c)

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Autoconfig Failing with error on Stansby node (EBS 12.2.7 with db 19c)

karthikmca.bhc
Hi Support,

I am getting below error while performing action item 5.1 Configuration 1: Standby Application Tiers Connected to the Standby Database from Note ID 2617787.1

I have converted the standby database as snapshot standby as given in the document and while performing below action items im getting error while connecting to ebs pdb database using its service name.

7. Remove the applications configuration.
$ cd $ORACLE_HOME
$ source <PDB_NAME>_<NODE_NAME>.env
$ sqlplus apps/<apps_password>@<pdb_name>
SQL> exec fnd_conc_clone.setup_clean;
SQL> exec ad_zd_fixer.clear_valid_nodes_info;

8. Run AutoConfig on the database tier.

[oracle@p2esprodstby admin]$ tnsping PROD
TNS Ping Utility for Linux: Version 19.0.0.0.0 - Production on 24-SEP-2020 01:18:24
Copyright (c) 1997, 2019, Oracle.  All rights reserved.
Used parameter files:
/u01/oracle/db/tech_st/19.3.0.0/network/admin/EBSPDB_p2esprodstby/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST = p2esprod.energy-esi-dubai.com)(PORT = 1521)) (CONNECT_DATA = (SID = PROD)))
OK (10 msec)

[oracle@p2esprodstby admin]$ tnsping PRODSTBY
TNS Ping Utility for Linux: Version 19.0.0.0.0 - Production on 24-SEP-2020 01:18:31
Copyright (c) 1997, 2019, Oracle.  All rights reserved.
Used parameter files:
/u01/oracle/db/tech_st/19.3.0.0/network/admin/EBSPDB_p2esprodstby/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = p2esprodstby.energy-esi-dubai.com)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = PRODSTBY)))
OK (10 msec)

[oracle@p2esprodstby admin]$ tnsping EBSPDB
TNS Ping Utility for Linux: Version 19.0.0.0.0 - Production on 24-SEP-2020 01:18:38
Copyright (c) 1997, 2019, Oracle.  All rights reserved.
Used parameter files:
/u01/oracle/db/tech_st/19.3.0.0/network/admin/EBSPDB_p2esprodstby/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = p2esprodstby.energy-esi-dubai.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = EBSPDB)))
OK (10 msec)

SQL> select name from v$active_services;

NAME
----------------------------------------------------------------
r1227cdbXDB
ebspdb
SYS$BACKGROUND
SYS$USERS
ebs_EBSPDB
PRODSTBY
EBSPDB_ebs_patch
PROD_CFG
8 rows selected.

[oracle@p2esprodstby ~]$ lsnrctl status
LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 22-SEP-2020 17:57:32
Copyright (c) 1991, 2019, Oracle.  All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
------------------------
Alias                     PRODSTBY
Version                   TNSLSNR for Linux: Version 19.0.0.0.0 - Production
Start Date                24-SEP-2020 01:12:06
Uptime                    0 days 0 hr. 2 min. 48 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/oracle/db/tech_st/19.3.0.0/network/admin/listener.ora
Listener Log File         /u01/oracle/diag/tnslsnr/p2esprodstby/prodstby/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=p2esprodstby.energy-esi-dubai.com)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Services Summary...
Service "EBSPDB" has 1 instance(s).
  Instance "PROD", status UNKNOWN, has 1 handler(s) for this service...
Service "PROD" has 1 instance(s).
  Instance "PROD", status READY, has 1 handler(s) for this service...
Service "PRODSTBY" has 1 instance(s).
  Instance "PROD", status READY, has 1 handler(s) for this service...
Service "PROD_CFG" has 1 instance(s).
  Instance "PROD", status READY, has 1 handler(s) for this service...
Service "r1227cdbXDB" has 1 instance(s).
  Instance "PROD", status READY, has 1 handler(s) for this service...
The command completed successfully

[oracle@p2esprodstby admin]$ sqlplus apps/apps@ebspdb
SQL*Plus: Release 19.0.0.0.0 - Production on Thu Sep 24 01:14:02 2020
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle.  All rights reserved.
Last Succssful login time: Thu Sep 24 2020 01:13:47 +04:00
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
SQL>exit

[oracle@p2esprodstby ~]$ cd /u01/oracle/db/tech_st/19.3.0.0/appsutil/scripts/EBSPDB_p2esprodstby
[oracle@p2esprodstby EBSPDB_p2esprodstby]$ sh adautocfg.sh
Enter the APPS user password:
The log file for this session is located at: /u01/oracle/db/tech_st/19.3.0.0/appsutil/log/EBSPDB_p2esprodstby/09240123/adconfig.log

AutoConfig is configuring the Database environment...

AutoConfig will consider the custom templates if present.
        Using ORACLE_HOME location : /u01/oracle/db/tech_st/19.3.0.0

Value of s_dbcset is AL32UTF8

Character set is not present in the allowed list. Need to add orai18n.jar to the CLASSPATH.

Library orai18n.jar exists.

Value of s_dbcset is AL32UTF8

Character set is not present in the allowed list. Need to add orai18n.jar to the CLASSPATH.

Library orai18n.jar exists.
        Classpath                   : :/u01/oracle/db/tech_st/19.3.0.0/jdbc/lib/ojdbc8.jar:/u01/oracle/db/tech_st/19.3.0.0/appsutil/java/xmlparserv2.jar:/u01/oracle/db/tech_st/19.3.0.0/appsutil/java:/u01/oracle/db/tech_st/19.3.0.0/jlib/netcfg.jar:/u01/oracle/db/tech_st/19.3.0.0/jlib/ldapjclnt19.jar:/u01/oracle/db/tech_st/19.3.0.0/jlib/orai18n.jar

        Using Context file          : /u01/oracle/db/tech_st/19.3.0.0/appsutil/EBSPDB_p2esprodstby.xml

Context Value Management will now update the Context file

        Updating Context file...COMPLETED

        Attempting upload of Context file and templates to database...ERROR: InDbCtxFile.uploadCtx() : Exception : Unable to connect to database;  refer to the log file details.
oracle.apps.ad.autoconfig.oam.InDbCtxFileException: Unable to connect to database;  refer to the log file details.
        at oracle.apps.ad.autoconfig.oam.InDbCtxFile.uploadCtx(InDbCtxFile.java:192)
        at oracle.apps.ad.autoconfig.oam.CtxSynchronizer.uploadToDb(CtxSynchronizer.java:332)
        at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBCtx(FileSysDBCtxMerge.java:762)
        at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBFiles(FileSysDBCtxMerge.java:233)
        at oracle.apps.ad.context.CtxValueMgt.processCtxFile(CtxValueMgt.java:1721)
        at oracle.apps.ad.context.CtxValueMgt.main(CtxValueMgt.java:787)
FAILED
COMPLETED

Updating rdbms version in Context file to db19
Updating rdbms type in Context file to 64 bits
Configuring templates from ORACLE_HOME ...

AutoConfig completed with errors.

Please find attached error logs.

Please provide fix. adconfig.logtxkCreateEBSPDBService.logtxkSetADOPPatchSrvName.logtxkCfgUtlfileDir.logtxkSetUnicodeCharSet.logNetServiceHandler.logvalidate_apps_password.log


Reply | Threaded
Open this post in threaded view
|

Re: Autoconfig Failing with error on Stansby node (EBS 12.2.7 with db 19c)

ErmanArslansOracleBlog
Administrator
Gathered info:

IPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=XXX)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=XXX)))
WARNING:     Exception occurred: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection

Checking with tnsping is not enough. Can you connect your db using sqlplus?

sqlplus username/password@host:port/service_name

sqlplus username/password@<hostname>:1521/<service_name>
Reply | Threaded
Open this post in threaded view
|

Re: Autoconfig Failing with error on Stansby node (EBS 12.2.7 with db 19c)

karthikmca.bhc
Please find below output that you requested.

[oracle@p2esprodstby ~]$ sqlplus apps/apps@p2esprodstby.energy-esi-dubai.com:1521/ebspdb

SQL*Plus: Release 19.0.0.0.0 - Production on Thu Sep 24 13:01:34 2020
Version 19.3.0.0.0

Copyright (c) 1982, 2019, Oracle.  All rights reserved.

Last Successful login time: Thu Sep 24 2020 02:18:37 +04:00

Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
SQL>

Reply | Threaded
Open this post in threaded view
|

Re: Autoconfig Failing with error on Stansby node (EBS 12.2.7 with db 19c)

karthikmca.bhc
[oracle@p2esprodstby ~]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Thu Sep 24 13:14:07 2020
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
SQL> set lines 900 pages 200
SQL> col NAME format a20
SQL> select con_id,name,open_mode from v$containers;

    CON_ID NAME                 OPEN_MODE
---------- -------------------- ----------
         1 CDB$ROOT             READ WRITE
         2 PDB$SEED             READ ONLY
         4 EBSPDB               READ WRITE

SQL> show pdbs;

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         4 EBSPDB                         READ WRITE NO

SQL> select name,db_unique_name,cdb,open_mode from v$database;

NAME                 DB_UNIQUE_NAME                 CDB OPEN_MODE
-------------------- ------------------------------ --- --------------------
PROD                 PRODSTBY                       YES READ WRITE

SQL> show parameter local_listener

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
local_listener                       string      (ADDRESS=(PROTOCOL=tcp)(HOST=1
                                                 92.168.1.172)(PORT=1521))

SQL> show parameter service

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
service_names                        string      PROD

SQL> conn apps/apps@p2esprodstby.energy-esi-dubai.com/ebspdb
Connected.

SQL> conn apps/apps@p2esprodstby.energy-esi-dubai.com/ebspdb
Connected.


[oracle@p2esprodstby ~]$ cat /etc/hosts
127.0.0.1       localhost.localdomain   localhost
::1             localhost6.localdomain6 localhost6
192.168.1.172   p2esprodstby.energy-esi-dubai.com       p2esprodstby
192.168.1.171   p2esprod.energy-esi-dubai.com   p2esprod

Attached tnsnames.ora and listener.ora for your analysis.

tnsnames.ora
listener.ora
Reply | Threaded
Open this post in threaded view
|

Re: Autoconfig Failing with error on Stansby node (EBS 12.2.7 with db 19c)

karthikmca.bhc
Attached latest autoconfig.log and error logs for your analysis.

adconfig.log
txkCfgUtlfileDir.logtxkSetUnicodeCharSet.log
tnsnames.ora
listener.ora



Reply | Threaded
Open this post in threaded view
|

Re: Autoconfig Failing with error on Stansby node (EBS 12.2.7 with db 19c)

karthikmca.bhc
Reply | Threaded
Open this post in threaded view
|

Re: Autoconfig Failing with error on Stansby node (EBS 12.2.7 with db 19c)

ErmanArslansOracleBlog
Administrator
Okay. Looking at the latest adconfig log..
It seems generally your connections are obtained.. (it first tries with SID and fails, but then it tries with SERVICE NAME and it connects)


However, now you have 2 errors for the following;
      afdbprf.sh              INSTE8_PRF         1
      adcrobj.sh              INSTE8_APPLY       1

These scripts try to connect to DB using SID.. (SID only -- not the service name) and that's why they fail.

Enter value for 1: Enter value for 2: Enter value for 3: ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor

Your listener accepts PROD as SID.. But they are tring with EBSPRD as SID. Service "EBSPDB" has 1 instance(s).

Here ->
Service "EBSPDB" has 1 instance(s).
  Instance "PROD", status UNKNOWN, has 1 handler(s) for this service...
Service "PROD" has 1 instance(s).
  Instance "PROD", status READY, has 1 handler(s) for this service...

Please check the document 2617787.1, probably you have a misconfiguration for your STANDBY ORACLE SID.