ORA-16773: error starting Redo Apply

Cause : There was an error starting Redo Apply on a physical standby database.

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

Check the Data Guard broker log and Oracle alert log for more details.

update : 25-04-2017
ORA-16773

ORA-16773 - error starting Redo Apply
ORA-16773 - error starting Redo Apply

  • ora-07407 : slbtpd: invalid exponent.
  • ora-24314 : service handle not initialized
  • ora-00292 : parallel recovery feature not installed
  • ora-09317 : szprv: insufficient privileges
  • ora-12024 : materialized view log on "string"."string" does not have primary key columns
  • ora-32631 : illegal use of objects in MODEL
  • ora-26577 : PRESERVE TABLE can not be used when dropping old style materialized view string.string
  • ora-38463 : invalid XML Tag list
  • ora-15080 : synchronous I/O operation to a disk failed
  • ora-33448 : (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.
  • ora-12004 : REFRESH FAST cannot be used for materialized view "string"."string"
  • ora-29965 : The specified binding does not exist
  • ora-27103 : internal error
  • ora-38955 : Source platform string not cross platform compliant
  • ora-10691 : Set background process core file type (Unix only)
  • ora-01060 : array binds or executes not allowed
  • ora-29358 : resource plan string does not exist
  • ora-32842 : value for property string cannot be altered
  • ora-24378 : user callbacks not allowed for this call
  • ora-02175 : invalid rollback segment name
  • ora-03202 : the scan limit specification is invalid
  • ora-29664 : Unable to generate the helper class for the defined type
  • ora-24408 : could not generate unique server group name
  • ora-27037 : unable to obtain file status
  • ora-02737 : osnpcl: cannot tell orapop to exit
  • ora-31447 : cannot create change tables in the SYS schema
  • ora-12830 : Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
  • ora-28671 : UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
  • ora-38610 : FI "string" name prefix is reserved for frequent itemset counting
  • ora-19202 : Error occurred in XML processingstring
  • 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.