|Applies To||RSA Product Set: RSA Identity Governance & Lifecycle|
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
Platform: Hardware Appliance
|Issue||The Oracle Automatic Storage Management (Oracle ASM) partition, when used on an RSA Identity Governance & Lifecycle Hardware Appliance, is formatted and managed by the Oracle ASM software. As such, it is not seen by typical operating system space usage commands, such as df -kh, du -a, or ls -ltr. The only way to see the ASM partition itself using an operating system command, is through a device command such as fdisk -l, run as the Linux root user. However, the fdisk command only shows you the size of the partition, not how much space is used within that partition.|
This article explains how to use the Oracle ASM Command-Line Utility (ASMCMD) to determine how much space is available and how much space is in use on the ASM partition on Oracle versions 11g and 12g.
|Resolution||To see the ASM partition space used on an RSA Identity Governance & Lifecycle hardware appliance, both the ORACLE_SID and ORACLE_HOME environment variables must be re-defined to point to the +ASM instance instead of the AVDB instance.The ORACLE_SID environment variable needs to be set to +ASM, and the ORACLE_HOME environment variable must be set to point to the ORACLE_GRID_HOME. This can be done using the Linux export command.|
Once the appropriate environment variables are defined, the Oracle ASM command asmcmd lsdg, can be used to see the actual ASM space used. This command can be run as either the Linux admin or oracle user.
NOTE: In the example below, only part of the information returned by this command is shown.
This output says there is approximately 143 GB of space available on the ASM partition, and approximately 133 GB of that space is currently available for use.
This could be an indication that there is very little or no space left on the local operating system partition, and is not indicative of space availability on ASM. When the local space is cleaned up, the lsdg command can return expected output.
The reason that both the ORACLE_SID and ORACLE_HOME environment variables need to be reset is to ensure that non-Grid commands function properly. Another way to do this would be to logoff, and login again, or by executing the RSA Identity Governance & Lifecycle script /home/oracle/setDeployEnv.sh.
If these environment variables are NOT redefined/reset, then execution of SQL*Plus to access the database might fail with an error like this: