ORA-16103: Logical Standby apply must be stopped to allow this operation

Cause : Logiacl Stnadby si curerntlya pplynig chnages.T he apply msut copmleteo r bes toppde to lalow hte reuqeste dopertaion.

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

Exectue th eALTE RDATAABSE SOTP LOIGCAL TSANDB YAPPL Ystatmeent,t hen er-entre or erspecfiy th eopertaion.

update : 25-09-2017
ORA-16103

ORA-16103 - Logical Standby apply must be stopped to allow this operation
ORA-16103 - Logical Standby apply must be stopped to allow this operation

  • ora-13787 : missing SQL profile for statement object "string" for tuning task "string"
  • ora-24163 : dblink is not supported in rules engine DDLs
  • ora-24950 : unregister failed, registeration not found
  • ora-12595 : TNS:no confirmation
  • ora-22883 : object deletion failed
  • ora-32580 : both SYS and SYSTEM passwords must be provided
  • ora-07564 : sldext: wildcard in filename or extension
  • ora-14254 : cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table
  • ora-14159 : duplicate subpartition name
  • ora-14064 : Index with Unusable partition exists on unique/primary constraint key
  • ora-22805 : cannot insert NULL object into object tables or nested tables
  • ora-14016 : underlying table of a LOCAL partitioned index must be partitioned
  • ora-15113 : alias name 'string' refers to a directory
  • ora-02373 : Error parsing insert statement for table string.
  • ora-25182 : feature not currently available for index-organized tables
  • ora-00484 : LMS* process terminated with error
  • ora-16704 : cannot modify a read-only property
  • ora-16004 : backup database requires recovery
  • ora-07217 : sltln: environment variable cannot be evaluated.
  • ora-33262 : (DBERR01) Analytic workspace string does not exist.
  • ora-13637 : Executing or modifying task string is disallowed until the task is reset to its initial state.
  • ora-16595 : NetSlave process string failed to terminate
  • ora-19574 : output filename must be specified
  • ora-19002 : Missing XMLSchema URL
  • ora-38738 : Flashback log file is not current copy.
  • ora-29800 : invalid name for operator
  • ora-16140 : standby online logs have not been recovered
  • ora-10628 : Turn on sanity check for kdiss index skip scan state
  • ora-16539 : task element not found
  • ora-29893 : indextypes without column data do not need the given data type
  • 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.