EM13c: Saving A Configured Deployment Procedure Fails with: Procedure Configuration with the same name already exists ORA-00001 Error

(Doc ID 2299188.1)

Last updated on FEBRUARY 06, 2018

Applies to:

Enterprise Manager Base Platform - Version to [Release 13.2]
Information in this document applies to any platform.


Using a custom deployment procedure based on the standard Oracle RAC Database Provisioning procedure; the Operators access a configured version of the procedure where some values are pre-populated and locked.
After upgrade to EM 13c, saving the configured procedure with the same name as before the migration results in an error:

 [2017-02-23T02:56:49.266-05:00] [EMGC_OMS2] [ERROR] [] [oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter] [tid:]] [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'userId: GZT98S_SA] [ecid:]] 005IIroWQf53f5tLkeP5iZ0001G40000ri,0:1] [APP: emgc] [DSID:]] 0000LddppHu3f5tLkeP5iZ1Ofa55000002] ADF_FACES-60096:Server Exception during PPR, #1

javax.el.ELException: oracle.sysman.emSDK.app.exception.EMSystemException
 Caused by: oracle.sysman.emSDK.app.exception.EMSystemException
 Caused by: oracle.sysman.emSDK.core.job.procedure.exception.PAFException:
 Procedure Configuration with the same name already exists.

Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001:
 unique constraint (SYSMAN.MGMT_JOB_UK) violated
 ORA-06512: at "SYSMAN.EM_PAF_CONFIG", line 39
 ORA-06512: at line 1


Saving the procedure with a different name seems to work at first attempt, however, changing and saving any value shows the same error again.




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms