Andreas' Adventures

A while back I had the problem that my CRS information was lost . Now I had found that when I did a crs_start of the component I received the following error: CRS-0254 authorization failure Some investigation showed that the problem was related to the fact that the component was not owned by the oracle user. Using crs_getperm ora.ORCL.db showed the problem. oracle@myhost:/opt/oracle/crs/bin>./crs_getperm ora.ORCL.db Name: ora.ORCL.db owner:root:rwx,pgrp:system:r-x,other::r--, This can be solved by doing the following: crs_setperm ora.ORCL.db -o oracle crs_setperm ora.ORCL.db -g dba Now it works again. cu Andreas

Due to a crash a part of the CRS information was lost. Until now I have not found out how this could happen in the first place. The effects were strange. The instances would not start and there was no indication of an error in the alert_log. Doing some research in the CRS revealed that the ora.ORCL.db was gone while the ora.ORACL.oracl1.inst was still there. Creating a new file in the CRS profiles and using crs_register did do the trick. Such a file should look like this: NAME=ora.ORCL.db TYPE=application ACTION_SCRIPT=/opt/oracle/crs/bin/racgwrap PLACEMENT=balanced CHECK_INTERVAL=600 RESTART_ATTEMPTS=1 FAILOVER_DELAY=0 FAILURE_INTERVAL=60 FAILURE_THRESHOLD=1 AUTO_START=1 SCRIPT_TIMEOUT=600 ACTIVE_PLACEMENT=0 OPTIONAL_RESOURCES= REQUIRED_RESOURCES= RESTART_ATTEMPTS=1 STOP_TIMEOUT=0 UPTIME_THRESHOLD=7d HOSTING_MEMBERS= USR_ORA_ALERT_NAME= USR_ORA_CHECK_TIMEOUT=0 USR_ORA_CONNECT_STR=/ as sysdba USR_ORA_DEBUG=0 USR_ORA_DISCONNECT=false USR_ORA_FLAGS= USR_ORA_IF= USR_ORA_INST_NOT_SHUTDOWN=...