ORA-16236: Logical Standby metadata operation in progress

Cause : The requested operation failed because a Logical Standby metadata operation, such as DBMS_LOGSTDBY.SET_TABLESPACE or DBMS_LOGSTDBY.INSTANTIATE_TABLE, has not finished.

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

Wait for the Logical Standby metadata operation to finish, then re-enter or respecify the operation.

update : 23-07-2017
ORA-16236

ORA-16236 - Logical Standby metadata operation in progress
ORA-16236 - Logical Standby metadata operation in progress

  • ora-22975 : cannot create a PRIMARY KEY-based REF to this object view
  • ora-24368 : OCI mutex counter non-zero when freeing a handle
  • ora-09850 : soacon: Archmon unable to lock named pipe.
  • ora-02832 : Segment deallocation failed - segment not on list
  • ora-37154 : OLAP API initialization error: (case string)
  • ora-03132 : two-task default value overflow
  • ora-00323 : Current log of thread string not useable and all others need archiving
  • ora-33338 : (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
  • ora-16217 : prepare to switchover has not completed
  • ora-12624 : TNS:connection is already registered
  • ora-32842 : value for property string cannot be altered
  • ora-10919 : Default temporary tablespace group must have at least one tablespace
  • ora-00371 : not enough shared pool memory, should be atleast string bytes
  • ora-30197 : reserved for future use
  • ora-02793 : Close of asynchronous I/O failed.
  • ora-31217 : DBMS_LDAP: PL/SQL - Invalid LDAP newparent.
  • ora-12804 : parallel query server appears to have died
  • ora-00229 : operation disallowed: already hold snapshot control file enqueue
  • ora-00297 : must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START
  • ora-19030 : Method invalid for non-schema based XML Documents.
  • ora-32614 : illegal MODEL SELECT expression
  • ora-12514 : TNS:listener does not currently know of service requested in connect descriptor
  • ora-19764 : database id string does not match database id string in control file
  • ora-25118 : invalid DUMP DATAFILE/TEMPFILE option
  • ora-22895 : referenced table "string" in schema "string" is not an object table
  • ora-23485 : Column group "string" must consist of a single numeric column only
  • ora-10589 : Test recovery had to corrupt string data blocks in order to proceed
  • ora-06558 : buffer in dbms_pipe package is full. No more items allowed
  • ora-30450 : refresh_after_errors was TRUE; The following MVs could not be refreshed: string
  • ora-39219 : directory object name is too long
  • 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.