ORA-14400: inserted partition key does not map to any partition

This occured during our production cloud control upgrade to release 3. After it failed, i did a flashback database and got this same error with the SYSMAN user login.

Found the error and fix in metalink – 1493151.1

Reason for Failing:

A partition was missing from sysman.mgmt_audit table and no audit was being performed. So this caused issues with logging into sysman and upgrade.

to Fix (From metalink) – it works and now the upgrade is completed:

Case 1:

This is an upgrade specific issue. The mgmt_audit_master.prepopulate_days table is not initialized during upgrade, so new partitions are not being created.

job_queue_processes was left at 0 after the upgrading to

Set the job_queue_processes to a non-zero value, then verify the console login.

Case 2:

If the job_queue_processes value is already set to a value greater than 0:

1. Execute the following queries in repository DB:
SQL> update mgmt_audit_master set prepopulate_days=5 where prepopulate_days is null;
SQL> exec mgmt_audit_admin.add_audit_partition;

2. Restart the OMS:

./emctl stop oms -all

./emctl start oms

Cloud 12c Upgrade issues and resolutions

In the process of upgrading to EM12c Cloud control Version 3, i received a few errors that delayed the upgrade by months.   With the help of Oracle support, i finally resolved it today and finished he upgrade.

Error  #1 – “em target policy error”  

Fix – under the sysman account – “exec emd_maintenance.ENABLE_EM_SECURITY_POLICIES”  <==== FIX FOR Error

This was due to missing information below (BEFORE ERROR).

Executing Prereq Action

executing Action: select count(*) from (select ‘EM_TARGET_POLICY’ from dual where not exists (select policy_name from dba_policies where object_owner=upper(?) and pf_owner=upper(?) and object_name IN (‘MGMT_TARGETS’,’EM_MANAGEABLE_ENTITIES’)))

=========NEXT ERROR ================

After that was fixed, received the next error (at about 60/70 % upgraded)

INFO: oracle.sysman.top.oms:Securing OMS ……
INFO: oracle.sysman.top.oms:EM Key is secured and is backed up at /u01/app/oracle/middleware_3/oms/sysman/config/emkey.ora
INFO: oracle.sysman.top.oms:Adapter created successfully: emgc_USER
INFO: oracle.sysman.top.oms:Adapter created successfully: emgc_GROUP
INFO: oracle.sysman.top.oms:EM Key is secured and is backed up at /u01/app/oracle/middleware_3/oms/sysman/config/emkey.ora
INFO: oracle.sysman.top.oms:ORA-00001: unique constraint (SYSMAN.MGMT_OMS_PROPERTY_DEF_PK) violated
INFO: oracle.sysman.top.oms:ORA-06512: at “SYSMAN.EM_OMS_PROPERTIES”, line 420
INFO: oracle.sysman.top.oms:ORA-06512: at “SYSMAN.EM_OMS_PROPERTIES”, line 761
INFO: oracle.sysman.top.oms:ORA-06512: at “SYSMAN.EM_OMS_PROPERTIES”, line 589
INFO: oracle.sysman.top.oms:ORA-06512: at “SYSMAN.EM_OMS_PROPERTIES”, line 982
INFO: oracle.sysman.top.oms:ORA-06512: at line 1
INFO: oracle.sysman.top.oms:

==== BEFORE FIX =============== – No rows showing as SYSMAN

SYSMAN_apgrid10>select count(*) from mgmt_oms_property_def


Elapsed: 00:00:00.01
SYSMAN>show user
SYSMAN>connect sys as sysdba
SYS>select count(*) from sysman.mgmt_oms_property_def;


Elapsed: 00:00:00.01
SYS_apgrid10>show user

===========Fix =======

>grant exempt access policy to sysman;  <=== this is what you have to do to fix the unique constraint error

Grant succeeded.

Elapsed: 00:00:00.07
>select count(*) from sysman.mgmt_oms_property_def;


Elapsed: 00:00:00.10
>connect sysman
SYSMAN_apgrid10>select count(*) from mgmt_oms_property_def;