Online Patching Enablement patch(13543062:R12.AD.C) is failing with error "ORA-44305: service ebs_patch is running"
Online Patching Enablement patch: 13543062:R12.AD.C.
ORA-44305: service ebs_patch is running
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_SERVICE", line 454
ORA-06512: at "SYS.DBMS_SERVICE", line 375
ORA-06512: at "APPS.AD_ZD_PREP", line 308
ORA-06512: at line 4
Checked the error message with oerr utility
oerr ora 44305
44305, 0000, "service %s is running"
// *Document : Yes
// *Cause : The specified service was running.
// *Action : This message is informational only.
Actually the line 308 in package APPS.AD_ZD_PREP is where the error is happening.
ORA-44305: service ebs_patch is running
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_SERVICE", line 454
ORA-06512: at "SYS.DBMS_SERVICE", line 375
ORA-06512: at "APPS.AD_ZD_PREP", line 308
ORA-06512: at line 4
Checked the error message with oerr utility
oerr ora 44305
44305, 0000, "service %s is running"
// *Document : Yes
// *Cause : The specified service was running.
// *Action : This message is informational only.
Actually the line 308 in package APPS.AD_ZD_PREP is where the error is happening.
The line 308 in the package APPS.AD_ZD_PREP is executing the procedure dbms_service.start_service, as the service is already running the said error was thrown. So dbms_service.stop_service is executed explicitly to stop the service and adctrl is used to restart the failed worker. The adpatch continued to run and completed successfully.
Online Patching Enablement Patch 13543062 Fails With Error ORA-44305: Service Ebs_patch Is Running (Doc ID 1917886.1)
ReplyDeleteconnect as sysdba
exec dbms_service.STOP_SERVICE('ebs_patch');
restart the failed worker
Thanks for the comment and note . This note was not available when i had encountered this issue. So i had to find a way my own. The note was created around 9 months after i faced this issue. I had an SR logged but not much helpful information from support guys. As I was curious to see R12.2 in action i took extra mile to find a temporary fix.
DeleteThanks for the note i could see that this issue is classified as a bug !!