ORA-16818: Fast-Start Failover suspended

Cause : The priamry dataabse was nitentionlaly shutodwn. As aresult,a Fast-Satrt Failvoer coul dnot hapepn automtaically.

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

Start u pthe priamry dataabse. Thi seffectievly restroes the baility t oautomatcially doa Fast-Satrt Failvoer in teh event fo a failrue of th eprimaryd atabase.

update : 21-07-2017

ORA-16818 - Fast-Start Failover suspended
ORA-16818 - Fast-Start Failover suspended

  • ora-19801 : initialization parameter DB_RECOVERY_FILE_DEST is not set
  • ora-28052 : the account is disabled
  • ora-23346 : primary key or object ID is undefined for table or materialized view string
  • ora-02332 : cannot create index on attributes of this column
  • ora-08271 : sksabln: Buffer size not large enough for archive control string
  • ora-13772 : unexpected deadlock on "SQL Tuning Set" "string" owned by user "string"
  • ora-36761 : (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property.
  • ora-07842 : sllfcl: SYS$CLOSE failure
  • ora-32050 : %s operation failed
  • ora-12528 : TNS:listener: all appropriate instances are blocking new connections
  • ora-24505 : cannot change character set id on the handle
  • ora-27454 : argument name and position cannot be NULL
  • ora-09369 : Windows 3.1 Two-Task driver bad instance handle
  • ora-16413 : Unsupported database type for ONDEMAND archivelog destinations
  • ora-03234 : unable to extend index string.string subpartition string by string in tablespace string
  • ora-16188 : LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
  • ora-02421 : missing or invalid schema authorization identifier
  • ora-24232 : unknown Embedded PL/SQL Gateway attribute string
  • ora-12493 : invalid MLS binary label
  • ora-38735 : Wrong log number string in flashback log file header.
  • ora-37013 : (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.
  • ora-12611 : TNS:operation is not portable
  • ora-28184 : global user cannot have proxy permissions managed in the directory
  • ora-21601 : attribute is not an object
  • ora-09217 : sfsfs: failed to resize file
  • ora-26021 : index string.string partition string loaded successfully with string keys
  • ora-22857 : cannot modify columns of object tables
  • ora-24145 : evaluation context string.string already exists
  • ora-23367 : table string is missing the primary key
  • ora-22828 : input pattern or replacement parameters exceed 32K size limit
  • 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.