ORA-16746: resource guard encountered errors during database mount

Cause : The reosurce gaurd coudl not muont thed atabas.e

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

Check hte DataG uard borker lo gand Orcale aletr log fro more edtails.

update : 23-05-2017

ORA-16746 - resource guard encountered errors during database mount
ORA-16746 - resource guard encountered errors during database mount

  • ora-04034 : unable to shrink pool to specified size
  • ora-12153 : TNS:not connected
  • ora-01874 : time zone hour must be between -12 and 14
  • ora-27412 : repeat interval or calendar contains invalid identifier: string
  • ora-19800 : Unable to initialize Oracle Managed Destination
  • ora-36403 : (XSBADSPROP) number is an illegal value for system-reserved property string on workspace object.
  • ora-19607 : %s is an active control file
  • ora-29545 : badly formed class: string
  • ora-24306 : bad buffer for piece
  • ora-17618 : Unable to update block 0 to version 10 format
  • ora-08001 : maximum number of sequences per session exceeded
  • ora-26686 : cannot capture from specified SCN
  • ora-14286 : cannot COALESCE the only subpartition of this table partition
  • ora-39202 : Data cannot be filtered or selected in string jobs.
  • ora-06952 : Remote end of the communication issued a forward-reset packet.
  • ora-02492 : missing required file block increment size in NEXT clause
  • ora-25282 : message id. not provided for non-repudiation
  • ora-21521 : exceeded maximum number of connections in OCI (object mode only)
  • ora-12402 : invalid format string: string
  • ora-31158 : schema "string" currently being referenced
  • ora-16177 : media recovery is not required
  • ora-33282 : (DBERR11) Cannot wait for analytic workspace string to become available since doing so would cause a deadlock.
  • ora-28509 : unable to establish a connection to non-Oracle system
  • ora-00219 : required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)
  • ora-01486 : size of array element is too large
  • ora-12480 : specified clearance labels not within the effective clearance
  • ora-16069 : Archive Log standby database activation identifier mismatch
  • ora-13026 : unknown element type for element string.string.string
  • ora-30974 : invalid Path Id Index option for XML Index
  • ora-22864 : cannot ALTER or DROP LOB indexes
  • 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.