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 : 27-06-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-38955 : Source platform string not cross platform compliant
  • ora-16707 : the value of the property string is invalid, valid values are string
  • ora-39727 : COMPATIBLE must be set to 10.0.0.0.0 or higher
  • ora-16035 : missing required keyword string
  • ora-29386 : plan or consumer group string is mandatory and cannot be deleted or modified
  • ora-37074 : (XSMCSESS02) Variable workspace object has no default aggmap.
  • ora-30515 : suspend triggers cannot have BEFORE type
  • ora-06044 : NETDNT: connect failed, byte count quota exceeded
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-01192 : must have at least one enabled thread
  • ora-12599 : TNS:cryptographic checksum mismatch
  • ora-02772 : Invalid maximum server idle time
  • ora-01126 : database must be mounted in this instance and not open in any instance
  • ora-24055 : cannot delete propagation status rows that are in prepared state
  • ora-07514 : scgcan: $deq unexpected return while canceling lock
  • ora-26737 : version string already has an export dump file
  • ora-22321 : method does not return any result
  • ora-16753 : resource guard could not open standby database
  • ora-38771 : unnamed datafile(s) added to control file by flashback recovery
  • ora-25197 : an overflow segment already exists for the indexed-organized table
  • ora-14013 : duplicate partition name
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-13458 : GeoRaster metadata SRS error
  • ora-28552 : pass-through SQL: call flow error
  • ora-38716 : Must supply an integer for the TYPE option.
  • ora-06124 : NETTCP: timeout waiting for ORASRV
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-12637 : Packet receive failed
  • ora-01921 : role name 'string' conflicts with another user or role name
  • ora-31449 : invalid value for change_set_name
  • 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.