Posted by
s.kumar on
Apr 24, 2023; 6:16am
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/ebs-patch-or-INSTANCE-ebs-patch-services-tp5198p11824.html
Hello Erman,
I've some questions reg. the same. In our DEV env. I was about to install a patch and the adop session failed in the PREPARE phase itself as follows (excerpts from the adop.log) :
****************************************
[EVENT] preparing the seed tables needed for autoconfig execution.
[PROCEDURE] [START 2023/04/21 12:50:13] Preparing autoconfig related seed data tables
[STATEMENT] Sourcing Patch edition environment <APPL_TOP_path>/APPSERPDEV_<hostname>.env
[ERROR] Cannot connect to database
[ERROR] Error Message: ORA-12521: TNS:listener does not currently know of instance requested in connect descriptor (DBD ERROR: OCIServerAttach)
****************************************
When I did the tnsping to the tns entry for this <DEVDB_ebs_patch> service and when I tried to connect to the DB using this ens entry (apps/<apps_password>@<DEVDB_path> - which connects to the service name <DEVDB_ebs_patch>) after setting the patch edition, I'm getting the same error.
I checked on the DB nodes (4 node RAC / 12c multi-tenant) and found that, the service <DEVDB_ebs_patch> wasn't started. And the service_name parameter is also not set with this value as well. But I see an entry in dba_services and in the tnsnames.ora for <DEVDB_ebs_patch>
To confirm, I cross checked with the UAT env. where, I see the service <UATDB_ebs_patch> up and running. Also there's an entry for <UATDB_ebs_patch> in tnsnames.ora. But here too, the service_names parameter is not set to <UATDB_ebs_patch>
From the above 2, I'm not sure if the service_names parameter plays a role here (If not, then how the ebs_patch service is started and up in UAT but not in DEV instance)
So, is "ORA-12521" due to the service <DEVDB_ebs_patch> not up and running ?
EBS maintenance guide status thus about the prepare phase :
"Checks to see if the patch service has been created. adop requires that a special database service exists for the purpose of connecting to the patch edition. This service is created automatically, but its continued existence is validated on each prepare"
I hope it talks about this <DEVDB_ebs_patch>" service only. Does this mean that this ebs_patch service will be started automatically by adop prepare phase, if it's not already up ? Or, it'll only be created by adop prepare phase, if it doesn't exist, but should be started manually and will not be started automatically, if it exists already ?
Thanks for your inputs in advance.
Kumar.