ORA-16228: Insufficient recovery for logical standby

Cause : nIusffcieitna omnu tfor cevore yaw sur nof roligac ltsnabd ynitsnaittaoi.n

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

oCtnnieut oerocev rht eadatabesu isgnA TLRED TABASA EEROCEV RAMANEG DTSNABD YADATABES.

update : 29-06-2017

ORA-16228 - Insufficient recovery for logical standby
ORA-16228 - Insufficient recovery for logical standby

  • ora-06800 : TLI Driver: SQL*Net SPX client went away during reconnect
  • ora-08112 : a composite partition may not be coalesced as a whole
  • ora-08468 : mask option string is not supported
  • ora-08267 : destroy_ora_addr: cannot close nameserver
  • ora-33004 : (XSAGDNGL01) workspace object is not a relationship array.
  • ora-02254 : DEFAULT not allowed here
  • ora-24295 : max key length (string) for sorted hash cluster exceeded
  • ora-19633 : control file record string is out of sync with recovery catalog
  • ora-15205 : requested mirror side unavailable
  • ora-23503 : error occurred during IAS instantiation
  • ora-22866 : default character set is of varying width
  • ora-12585 : TNS:data truncation
  • ora-19729 : File string is not the initial version of the plugged in datafile
  • ora-30375 : materialized view cannot be considered fresh
  • ora-26505 : unexpected internal null
  • ora-06017 : NETASY: message receive failure
  • ora-27202 : skgfpen: sbtpcend returned error
  • ora-00486 : ASMB process terminated with error
  • ora-23614 : Script string does not exist
  • ora-38950 : Source platform string not cross platform compliant
  • ora-31602 : parameter string value "string" in function string inconsistent with string
  • ora-14010 : this physical attribute may not be specified for an index partition
  • ora-26534 : collision: tranID number ignored and purged
  • ora-03252 : initial extent size not enough for LOB segment
  • ora-02195 : Attempt to create string object in a string tablespace
  • ora-25527 : bad format of _DB_MTTR_SIM_TARGET
  • ora-24100 : error in ktz testing layer
  • ora-27101 : shared memory realm does not exist
  • ora-24048 : cannot create QUEUE_TABLE, user does not have access to AQ object types
  • ora-00271 : there are no logs that need archiving
  • 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.