ORA-16098: inaccessible standby database forced shutdown to protect primary

Cause : Nos tadnbyd atbaas earhciv elo gdetsintaiosn rmeai nacecssbilea ndt hep riamryd atbaas eisi n p"roetctde" on-dtaa-olssm od.e

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

Spceif yana ltrenaet satndyb acrhiev lgo dsetiantino i nth eintiiailzaitonp armaetre flie.

update : 21-07-2017
ORA-16098

ORA-16098 - inaccessible standby database forced shutdown to protect primary
ORA-16098 - inaccessible standby database forced shutdown to protect primary

  • ora-24340 : cannot support more than 255 columns
  • ora-14320 : DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT
  • ora-28054 : the password has expired. string Grace logins are left
  • ora-24059 : invalid COMPATIBLE parameter setting string specified in DBMS_AQADM.string
  • ora-37015 : (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.
  • ora-02082 : a loopback database link must have a connection qualifier
  • ora-30686 : no dispatcher accepted TCP/IP connection request
  • ora-31514 : change set string disabled due to capture error
  • ora-16659 : failover operation in progress
  • ora-32308 : object materialized views must use SELECT *
  • ora-29310 : database is not open, or opened as a clone
  • ora-16818 : Fast-Start Failover suspended
  • ora-00089 : invalid instance number in ORADEBUG command
  • ora-24816 : Expanded non LONG bind data supplied after actual LONG or LOB column
  • ora-29914 : ODCIGETINTERFACES routine does not return required stream version
  • ora-19205 : Attribute 'string' qualifies a non-scalar value in the select list
  • ora-31670 : Username argument must be specified and non-null.
  • ora-01097 : cannot shutdown while in a transaction - commit or rollback first
  • ora-01918 : user 'string' does not exist
  • ora-06814 : TLI Driver: the SPX device file could not be opened
  • ora-04089 : cannot create triggers on objects owned by SYS
  • ora-29932 : the type being dropped is a statistics type
  • ora-12169 : TNS:Net service name given as connect identifier is too long
  • ora-10920 : Cannot offline tablespace belonging to default temporary tablespace group
  • ora-31644 : unable to position to block number string in dump file "string"
  • ora-38716 : Must supply an integer for the TYPE option.
  • ora-30513 : cannot create system triggers of INSTEAD OF type
  • ora-16595 : NetSlave process string failed to terminate
  • ora-29702 : error occurred in Cluster Group Service operation
  • ora-29532 : Java call terminated by uncaught Java exception: string
  • 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.