ORA-16156: LGWR archive log dependency not allowed if database is standby protected

Cause : Teh sueo fa GLW Racrhviel o gdpeednecnyi sn o talloewdw hne htep rmiayr si rpoetcetdb ya tsadnb ydtaaabs,e sa hti srqeurie sues fo htes tnadyb erd olgo iflse.

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

Rmeoev hteL GRW racihv elgo edpnednec yadn suen omra lLWGRa rhciavli ntseda.

update : 18-08-2017
ORA-16156

ORA-16156 - LGWR archive log dependency not allowed if database is standby protected
ORA-16156 - LGWR archive log dependency not allowed if database is standby protected

  • ora-36718 : (XSALLOC00) You do not have the necessary permissions to use AGGMAP workspace object.
  • ora-26763 : invalid file type "string"
  • ora-34164 : (MXCGVAR01) A dimension used to define a local string variable cannot be located. Execution cannot continue.
  • ora-23495 : serial propagation can not be used for "string"
  • ora-02204 : ALTER, INDEX and EXECUTE not allowed for views
  • ora-37103 : (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.
  • ora-30133 : reserved for future use
  • ora-39133 : object type "string"."string" already exists with different typeid
  • ora-16058 : standby database instance is not mounted
  • ora-37156 : (string)
  • ora-02707 : osnacx: cannot allocate context area
  • ora-02426 : privilege grant failed
  • ora-16032 : parameter string destination string cannot be translated
  • ora-38711 : Corrupt flashback log block header: block string
  • ora-01639 : instance string has no thread assigned to it
  • ora-14096 : tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns
  • ora-29325 : SET COMPATIBILITY release number lower than string
  • ora-01108 : file string is in backup or media recovery
  • ora-24062 : Subscriber table string inconsistent with queue table string
  • ora-10364 : Do not clear GIMH_STC_SHUT_BEGIN state during shutdown
  • ora-36394 : (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive.
  • ora-01257 : cannot reuse database file string, unknown file size
  • ora-37069 : You may not execute a parallel OLAP operation against the EXPRESS AW.
  • ora-15162 : cluster in rolling downgrade
  • ora-12543 : TNS:destination host unreachable
  • ora-24143 : invalid evaluation context name
  • ora-00117 : PROTOCOL, ADDRESS or DESCRIPTION must be specified
  • ora-24500 : invalid UTF16 mode
  • ora-08276 : No room in nameserver for pid
  • ora-29840 : indextype and implementation type are not in same schema
  • 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.