[EN] Do not delete /tmp/.oracle or /var/tmp/.oracle folder contents

Today our RMAN backups suddenly started to get the following errors on a specific server.

RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row

RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows

ORACLE error from target database:

ORA-29701: unable to connect to Cluster Synchronization Service

 When we check the status of the css, we saw the following warning:

[oracle@hostx:/home/oracle:]crsctl stat res -t
CRS-4639: Could not contact Oracle High Availability Services
CRS-4000: Command Status failed, or completed with errors. 

Also the following warnings in asm alertlog:

Thu Dec 21 08:51:39 2017
NOTE: failed to discover disks from gpnp profile asm diskstring
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_rbal_10813676.trc:
ORA-29786: SIHA attribute GET failed with error [Attribute 'ASM_DISKSTRING' sts[184] lsts[0]]
ORA-29701: unable to connect to Cluster Synchronization Service
Thu Dec 21 09:21:39 2017
NOTE: failed to discover disks from gpnp profile asm diskstring
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_rbal_10813676.trc:
ORA-29786: SIHA attribute GET failed with error [Attribute 'ASM_DISKSTRING' sts[184] lsts[0]]
ORA-29701: unable to connect to Cluster Synchronization Service

Some notes on metalink say that this could be due to cleanup of /tmp/.oracle or /var/tmp/.oracle folders. We checked our /tmp/.oracle folder and it was completely empty. One of our system admin deleted everything to get some space.

To solve this problem just restart oracle clusterware.

crsctl stop has [-f]  --use -f if it does not stop gracefully.
crsctl start has