SmartIO provides application templates to optimize caching for databases running on VxVM volumes. SmartIO uses the templates to apply policies to particular types of volumes in the database. For example, caching policies for index volumes and data volumes.
To apply a SmartIO sybase caching template for a VxVM volume
# export SYBASE=/sybase
Where /sybase
is the Sybase home directory.
# sfcache app cachearea=cachearea_name sybase \ {olap|oltp} db_username db_server [db_name]
Where:
olap or oltp indicates the type of application load. OLAP, or Online Analytical Processing, applications process workloads intended for multi-dimensional analytical queries. OLTP, or Online Transaction Processing, applications process transaction-oriented workloads, such as for data entry and retrieval transaction processing.
db_user_name indicates the Database User Name.
db_server indicates the Database Server Name.
db_name indicates the database name. The database name is optional. If database name is not specified, then the command runs for all databases under the user db_user_name.
For example:
# sfcache app cachearea=sfcachearea_1 sybase olap sa VXVMSYBS vmdb
The log file is/etc/vx/log/sfcache.log
.
For example:
Enabling caching for sybdg/DB1DATA sfcache enable sybdg/DB1DATA Disabling caching for sybdg/DB1LOG Sfcache disable sybdg/DB1LOG
To apply a SmartIO oracle caching template for a VxVM volume
# sfcache app cachearea=cachearea_name oracle \ {olap|oltp} oracle_user_name ORACLE_HOME \ ORACLE_SID [ASM_HOME [ASM_SID]]
Where:
olap or oltp indicates the type of application load. OLAP, or Online Analytical Processing, applications process workloads intended for multi-dimensional analytical queries. OLTP, or Online Transaction Processing, applications process transaction-oriented workloads, such as for data entry and retrieval transaction processing.
oracle_user_name indicates the user name of the Oracle user.
ORACLE_HOME indicates the directory where the Oracle software is installed. Usually the ORACLE_HOME value is stored in the bash.rc
file or the profile
file of the Oracle user.
ORACLE_SID indicates the System ID used to uniquely identify the database.
ASM_HOME indicates the directory where the ASM software is installed.
ASM_SID indicates the System ID for the ASM instance. By default, the value is +ASM. For multiple instances of ASM, the value may differ.
The following examples show the variations of the app command for the Oracle database.
The first example shows the Oracle database created directly on VxVM volumes. In this scenario, the ASM_HOME and ASM_SID values are not applicable.
Example of Oracle on Raw volumes:
# sfcache app cachearea=sfcachearea_1 oracle olap oracle /ora_base/db_home rawdb
The next example shows the Oracle ASM database created on VxVM volumes. In this scenario, you must specify the ASM_HOME. If required, specify the ASM_SID.
Example of Oracle ASM:
# sfcache app cachearea=sfcachearea_1 oracle oltp oracle /orabin/dbbase/dbhome \ testdb /orabin/gridhome
The log file is /etc/vx/log/sfcache.log
.
Example log file for Oracle on Raw volumes:
Fri Jun 7 22:04:31 IST 2013 sfcache app cachearea=sfcachearea_1 oracle olap oracle /ora_base/db_home rawdb Enabling caching for rawdg/rawvol02 /usr/sbin/vxprint -v -g rawdg -e 'v_name="rawvol02"' /usr/sbin/vxprint -g rawdg -F %cache_area_type rawvol02 /usr/sbin/vxprint -g rawdg -F %iscachevol rawvol02 /usr/sbin/vxprint -g rawdg -F %caching rawvol02 /usr/sbin/vxprint -o alldgs -q -v -e 'v_cachearea_vm=on' Enabling caching for rawdg/rawvol06 /usr/sbin/vxprint -v -g rawdg -e 'v_name="rawvol06"' /usr/sbin/vxprint -g rawdg -F %cache_area_type rawvol06 /usr/sbin/vxprint -g rawdg -F %iscachevol rawvol06 /usr/sbin/vxprint -g rawdg -F %caching rawvol06 /usr/sbin/vxprint -o alldgs -q -v -e 'v_cachearea_vm=on' Disabling caching for rawdg/rawvol01 /usr/sbin/vxprint -v -g rawdg -e 'v_name="rawvol01"' /usr/sbin/vxprint -g rawdg -F %cache_area_type rawvol01 /usr/sbin/vxprint -g rawdg -F %iscachevol rawvol01 /usr/sbin/vxprint -g rawdg -F %caching rawvol01
Example log file for Oracle ASM:
Enabling caching for testdg/testvol /usr/sbin/vxprint -v -g testdg -e 'v_name="testvol"' /usr/sbin/vxprint -g testdg -F %cache_area_type testvol /usr/sbin/vxprint -g testdg -F %iscachevol testvol /usr/sbin/vxprint -g testdg -F %caching testvol /usr/sbin/vxprint -o alldgs -q -v -e 'v_cachearea_vm=on' Enabling caching for testdg/testvol2 /usr/sbin/vxprint -v -g testdg -e 'v_name="testvol2"' /usr/sbin/vxprint -g testdg -F %cache_area_type testvol2 /usr/sbin/vxprint -g testdg -F %iscachevol testvol2 /usr/sbin/vxprint -g testdg -F %caching testvol2 /usr/sbin/vxprint -o alldgs -q -v -e 'v_cachearea_vm=on'