ORA-16257: Switchover initiated stop apply successfully completed

Cause : SQL Apply was stopped because of a switchover.

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

No action necessary, this informational statement is provided to record the event for diagnostic purposes.

update : 29-06-2017

ORA-16257 - Switchover initiated stop apply successfully completed
ORA-16257 - Switchover initiated stop apply successfully completed

  • ora-30182 : invalid precision specifier
  • ora-25020 : renaming system triggers is not allowed
  • ora-14258 : invalid partition description
  • ora-27370 : job slave failed to launch a job of type EXECUTABLE
  • ora-09878 : sstascre/sstasat: shmat error, unable to attach tas write page
  • ora-31420 : unable to submit the purge job
  • ora-14631 : the partition bounds do not match the subpartition bounds of the partition
  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-02066 : missing or invalid DISPATCHERS text
  • ora-14272 : only a partition with higher bound can be reused
  • ora-14166 : missing INTO keyword
  • ora-14635 : only one resulting subpartition can be specified for MERGE SUBPARTITIONS
  • ora-27451 : %s cannot be NULL
  • ora-39600 : Queue keys needs to be a suffix of cluster key.
  • ora-13066 : wrong feature geometry or element type
  • ora-01596 : cannot specify system in string parameter
  • ora-24045 : invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
  • ora-38410 : schema extension not allowed for the table name
  • ora-01954 : DEFAULT ROLE clause not valid for CREATE USER
  • ora-26030 : index string.string had string partitions made unusable due to:
  • ora-13762 : The string ranking measure is invalid.
  • ora-24023 : Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string]
  • ora-13266 : error inserting data into table string
  • ora-14108 : illegal partition-extended table name syntax
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-38101 : Invalid column in the INSERT VALUES Clause: string
  • ora-16159 : Cannot change protected standby destination attributes
  • ora-15110 : no diskgroups mounted
  • ora-16178 : Cannot specify remote destinations in archivelog manual mode
  • ora-00278 : log file 'string' no longer needed for this recovery
  • 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.