ORA-16711: the resource guard index is out of bounds
Cause: Internal error
Action: Contact Oracle Support Services.
Cause: Internal error
Action: Contact Oracle Support Services.
Wednesday, 28 March 2012
ORA-16710: the resource guard is out of memory
ORA-16710: the resource guard is out of memory
Cause: The resource guard was unable to allocate memory while trying to service a request.
Action: Disable broker management of the configuration, shut down Oracle, increase SGA size, and restart.
Cause: The resource guard was unable to allocate memory while trying to service a request.
Action: Disable broker management of the configuration, shut down Oracle, increase SGA size, and restart.
ORA-16709: standby archived log location settings conflict with flash recovery area
ORA-16709: standby archived log location settings conflict with flash recovery area
Cause: The flash recovery area was already set up on the standby database for storing incoming archived logs from the primary database. In this case, the StandbyArchiveLocation and AlternateLocation properties should not be used for setting up a standby archived log location. The Data Guard broker raised this error because it detected one of the following: (1) the user attempted to use the StandbyArchiveLocation or AlternateLocation properties to set up a standby archived log location; (2) On the standby database, a local destination corresponding to the StandbyArchiveLocation or AlternateLocation property was still set up to store archived logs from the primary database.
Action: If you get this error when trying to set property StandbyArchiveLocation or AlternateLocation (case (1) above), avoid setting these properties. If you get this error after a broker health check (case (2) above), reenable the standby database to clear the error.
Cause: The flash recovery area was already set up on the standby database for storing incoming archived logs from the primary database. In this case, the StandbyArchiveLocation and AlternateLocation properties should not be used for setting up a standby archived log location. The Data Guard broker raised this error because it detected one of the following: (1) the user attempted to use the StandbyArchiveLocation or AlternateLocation properties to set up a standby archived log location; (2) On the standby database, a local destination corresponding to the StandbyArchiveLocation or AlternateLocation property was still set up to store archived logs from the primary database.
Action: If you get this error when trying to set property StandbyArchiveLocation or AlternateLocation (case (1) above), avoid setting these properties. If you get this error after a broker health check (case (2) above), reenable the standby database to clear the error.
ORA-16708: the state supplied to resource guard is invalid
ORA-16708: the state supplied to resource guard is invalid
Cause: The state name specified is invalid for the database.
Action: Check the state name and reissue the request.
Cause: The state name specified is invalid for the database.
Action: Check the state name and reissue the request.
ORA-16707: the value of the property string is invalid, valid values are string
ORA-16707: the value of the property string is invalid, valid values are string
Cause: An invalid property value was entered while broker management of the database was disabled.
Action: Reset the value to a correct one.
Cause: An invalid property value was entered while broker management of the database was disabled.
Action: Reset the value to a correct one.
ORA-16706: no resource guard is available
ORA-16706: no resource guard is available
Cause: No resource guard is available to service the request.
Action: Contact Oracle Support Services.
Cause: No resource guard is available to service the request.
Action: Contact Oracle Support Services.
ORA-16705: internal error in resource guard
ORA-16705: internal error in resource guard
Cause: Internal error
Action: Contact Oracle Support Services.
Cause: Internal error
Action: Contact Oracle Support Services.
Subscribe to:
Posts (Atom)