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 : 26-04-2017

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

  • ora-29831 : operator binding not found
  • ora-12981 : cannot drop column from an object type table
  • ora-12666 : Dedicated server: outbound transport protocol different from inbound
  • ora-19210 : column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'
  • ora-31207 : DBMS_LDAP: PL/SQL - Invalid LDAP search time value.
  • ora-03248 : Too much of segment creation activity during migration
  • ora-09847 : soacon: ARCH unable to open named pipe.
  • ora-36671 : (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used.
  • ora-01558 : out of transaction ID's in rollback segment string
  • ora-24790 : cannot mix OCI_TRANS_RESUME and transaction isolation flags
  • ora-29955 : error occurred in the execution of ODCIINDEXEXCHANGEPARTITION routine
  • ora-08315 : sllfrb: Error reading file
  • ora-12590 : TNS:no I/O buffer
  • ora-28536 : error in processing Heterogeneous Services initialization parameters
  • ora-13865 : Module name must be specified
  • ora-22898 : existing scope clause on "string" points to a table other than the one mentioned in the referential constraint
  • ora-07244 : ssfccf: create file failed, file size limit reached.
  • ora-12536 : TNS:operation would block
  • ora-14109 : partition-extended object names may only be used with tables
  • ora-22347 : No changes to type specified for ALTER TYPE
  • ora-30157 : An invalid argument was given to operating system call
  • ora-31523 : could not find change source string for CDC change set string
  • ora-12065 : unknown refresh group identifier string
  • ora-19851 : OS error while managing auxiliary database string
  • ora-01224 : group number in header string does not match GROUP string
  • ora-19603 : cannot backup or copy active file with KEEP .. UNRECOVERABLE option
  • ora-12642 : No session key
  • ora-34276 : (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.
  • ora-03203 : concurrent update activity makes space analysis impossible
  • ora-28275 : Multiple mappings for user nickname to LDAP distinguished name exist.
  • 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.