Friday, March 6, 2015

Failed to establish dependency between database DBNAME and diskgroup resource

Failed to establish dependency between
database DBNAME and diskgroup resource


Today while working with client, found following error in alert log.


Default Temporary Tablespace will be necessary for a locally managed database in future release
Starting background process ASMB
Mon Jan 26 18:40:51 2015
ASMB started with pid=19, OS id=4843
Starting background process RBAL
NOTE: initiating MARK startup
Starting background process MARK
Mon Jan 26 18:40:52 2015
RBAL started with pid=20, OS id=4847
Mon Jan 26 18:40:52 2015
MARK started with pid=21, OS id=4849
NOTE: MARK has subscribed
NOTE: Loaded library: OSS
NOTE: Loaded library: System
SUCCESS: diskgroup DG_DATA was mounted
Mon Jan 26 18:40:57 2015
ERROR: failed to establish dependency between database ORCL and diskgroup resource ora.DG_DATA.dg
Database mounted in Exclusive Mode
Lost write protection disabled


Internal Bug 8304720 "ERROR: FAILED TO ESTABLISH DEPENDENCY BETWEEN DB and DISKGROUP"

"The db-dg dependency will be created later on if the diskgroup is used by the db again; the dependency can also be created manually through command line tool.

Automatically it will resolve itself later on when the db tries to use the diskgroup. Or we can manually establish the dependency through any command line utility."


For establishing dependencies between database and diskgroups, run srvctl from RDBMS home:

$ srvctl modify database -d DB_NAME -a DG_NAME1,DG_NAME2

For example:

$ srvctl modify database -d ORCL -a "DG_DATA,DG_FRA"



No comments:

Post a Comment