Skip to main content

EBS Prepare phase encountered Error Message: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor (DBD ERROR: OCIServerAttach)

Error:
[EVENT]     Creating database patch edition.
    [PROCEDURE] [START 2018/12/03 11:05:43] Creating patch edition if it does not exist
    Existing patch edition found, so no need to create.
    [PROCEDURE] [END   2018/12/03 11:05:43] Creating patch edition if it does not exist
[PROCEDURE] [START 2018/12/03 11:05:43] Performing steps for CLONE from run file system to patch file system
[PROCEDURE] [START 2018/12/03 11:05:43] Preparing seed data tables
[STATEMENT] Sourcing Patch edition environment /u01/applprod/fs1/EBSapps/appl/APPSPREPROD2_preprodapp.env
[ERROR]     Cannot connect to database
[ERROR]     Error Message: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor (DBD ERROR: OCIServerAttach)
[ERROR]     Error calling ad_zd_log. Refer to log file for details.
[ERROR]     Error calling ad_zd_log. Refer to log file for details.
[ERROR]     Error calling ad_zd_log. Refer to log file for details.
[ERROR]     Error calling ad_zd_log. Refer to log file for details.
[ERROR]     Error calling ad_zd_log. Refer to log file for details.
[ERROR]     Error calling ad_zd_log. Refer to log file for details.
[ERROR]     Cannot connect to database
[ERROR]     Error Message: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor (DBD ERROR: OCIServerAttach)
[ERROR]     Error calling ad_zd_log. Refer to log file for details.
[UNEXPECTED]Error calling runPendingClone subroutine.


Solution:


To implement the solution test the following steps in a development instance and then migrate accordingly:
Current parameter value
SQL> show parameter local
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
local_listener                       string      (ADDRESS =(PROTOCOL=TCP)(HOST=
                                                 epc-db-clint01.epcco.com)(PO
                                                 RT=1524))

1. Ensure a valid backup exists before testing the solution.
2. Check if the local_listener is set incorrectly by using:
At the RDBMS HOME:
sqlplus / as sysdba
SQL>show parameter local_listener

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
local_listener                       string      PREPROD2_LOCAL

In this scenario PREPROD2 is the SID used in this Environment
3. If the local listener value returned is incorrect, change it to the correct value in the init.ora parameter file.
4. Restart the Database tier and the listener.
show parameter output after changes
SQL> show parameter local
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
local_listener                       string      PREPROD2_LOCAL

5. Execute the "adop phase=prepare" again and confirm the error no longer occurs.









After this run prepare phase with restart=yes option it will run successful.

Comments

Popular posts from this blog

How To Create LVM Using vgcreate in Linux

Logical Volume Management (LVM) creates a layer of abstraction over physical storage, allowing you to create logical storage volumes. With LVM in place, you are not bothered with physical disk sizes because the hardware storage is hidden from the software so it can be resized and moved without stopping applications or unmounting file systems. You can think of LVM as dynamic partitions. For example, if you are running out of disk space on your server, you can just add another disk and extend the logical volume on the fly. Below are some advantages of using Logical volumes over using physical storage directly: •Resize storage pools: You can extend the logical space as well as reduce it without reformatting the disks. •Flexible storage capacity: You can add more space by adding more disks and adding them to the pool of physical storage, thus you have a flexible storage capacity. •Use of striped, mirrored and snapshot volumes: Striped logical volume that stripes data across two or ...

EBS Standby Role Tranistion using standby database and standby application Tier

 Role Transitions A database can operate in either a primary or standby role - these roles are mutually exclusive. Oracle Data Guard enables you to change these roles dynamically by issuing SQL commands, and supports the following transitions: Switchover Allows the primary database to switch roles with one of its standby databases. There is no data loss during a switchover. After a switchover, each database continues to participate in the Oracle Data Guard configuration with its new role. Failover Changes a standby database to the primary role in response to a primary database failure. The following role transitions are discussed: 6.1 Performing a Switchover 6.2 Performing a Failover 6.3 Performing a Switchback to the Primary Following A Switchover/Failover Each of these three transitions requires some application configuration to be performed. Most of the application configuration step...
TRANSPARENT APPLICATION FAILOVER FOR RAC RAC provides near-continuous availability by hiding failures from end-user clients and application server clients. This provides continuous, uninterrupted data access. Transparent Application Failover (TAF) is what applications use to sync up with Oracle RAC availability. TAF in the database reroutes application clients to an available database node in the cluster when the connected node fails. Application clients do not see error messages describing loss of service. if the users connection to Node 1 dies, their transaction is rolled back but they can continue work without having to manually reconnect. To get a good understanding of how the TAF architecture works, it is helpful to walk through a failover scenario where a user is querying the database to retrieve 1000 rows from the database. Assume that the user is connected to Node 1/ Instance 1. 1.      The heartbeat mechanism between the various nodes...