ORA-13521: Unregister operation on local Database id (string) not allowed

Cause : The operation failed because the local database ID cannot be unregistered from the Workload Repository.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

check the database id and retry the operation.

update : 28-07-2017
ORA-13521

ORA-13521 - Unregister operation on local Database id (string) not allowed
ORA-13521 - Unregister operation on local Database id (string) not allowed

  • ora-14169 : invalid ALTER TABLE MODIFY SUBPARTITION option
  • ora-38460 : filtering based on datatype "string" not supported for XML Tags
  • ora-30457 : 'string.string' cannot be refreshed because of unmnanaged NOT NULL columns in container
  • ora-06532 : Subscript outside of limit
  • ora-29540 : class string does not exist
  • ora-00603 : ORACLE server session terminated by fatal error
  • ora-25427 : cannot downgrade database links after database link data dictionary has been upgraded
  • ora-14299 : total number of partitions/subpartitions exceeds the maximum limit
  • ora-02833 : Server was unable to close file
  • ora-16595 : NetSlave process string failed to terminate
  • ora-30051 : VERSIONS clause not allowed here
  • ora-13617 : The specified task string already executing
  • ora-01678 : parameter string must be pairs of pattern and replacement strings
  • ora-25954 : missing primary key or unique constraint on dimension
  • ora-01328 : only one build operation may occur at one time
  • ora-01542 : tablespace 'string' is offline, cannot allocate space in it
  • ora-00711 : new tablespace name is invalid
  • ora-36683 : (XSDPART21) Partition string dimensioned by more than one composite.
  • ora-25192 : invalid option for an index-organized table
  • ora-39311 : call to DBMS_SCHEMA_COPY.CLONE_RECOVERY is not legal
  • ora-00338 : log string of thread string is more recent than control file
  • ora-02187 : invalid quota specification
  • ora-12020 : materialized view string is not registered
  • ora-30953 : XML minoccurs value (string) violated
  • ora-15128 : ASM file name 'string' exceeds maximum length string
  • ora-22607 : image handle already generated
  • ora-29546 : badly formed resource: string
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-27067 : size of I/O buffer is invalid
  • ora-16543 : invalid request made to broker
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.