Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Services Reference Manual Oracle Solaris Cluster 4.1 |
scalable_asm_diskgroup_proxy(5)
scalable_asm_instance_proxy(5)
SUNW.scalable_asm_diskgroup_proxy(5)
SUNW.scalable_asm_instance_proxy(5)
- resource type implementation for Oracle Solaris Cluster HA for SAP MaxDB
The SUNW.sapdb resource type represents the SAP MaxDB application in an Oracle Solaris Cluster configuration. The SAP MaxDB application requires the SAP xserver system. Therefore, you must set a dependency between the SAP MaxDB resource group and the SAP xserver resource group. Create this dependency when you register and configure the Oracle Solaris Cluster HA for SAP MaxDB data service. See Registering and Configuring HA for SAP MaxDB in Oracle Solaris Cluster Data Service for SAP MaxDB Guide.
Standard properties and extension properties that are defined for the SUNW.sapdb resource type are described in the subsections that follow. To set these properties for an instance of the SUNW.sapdb resource type, use the clresourcetype(1CL) command.
Standard resource properties are overridden for this resource type as follows:
10
2
Any time
3600
850
Any time
3600
120
Any time
For a description of these standard resource properties, see r_properties(5).
The extension properties of this resource type are as follows:
The option that is passed to the dbmcli command to start the SAP MaxDB database instance.
Note - For MaxDB version 7.4.3, set this property to db_online.
String
db_online
Not applicable
When disabled
The name of the MaxDB database instance in uppercase. This name is created when MaxDB is installed and configured. See Installing and Configuring SAP MaxDB in Oracle Solaris Cluster Data Service for SAP MaxDB Guide.
String
No default defined
Not applicable
When disabled
The UNIX user identity of the operating system (OS) user that administers the MaxDB database instance. This user's home directory contains the .XUSER.62 file that was created during the installation and configuration of MaxDB. See Installing and Configuring SAP MaxDB in Oracle Solaris Cluster Data Service for SAP MaxDB Guide.
String
No default defined
Not applicable
When disabled
Specifies whether the fault monitor fails over the MaxDB resource if the number of attempts to restart exceeds Retry_count within the time that Retry_interval specifies. The possible values of this extension property are as follows:
True – Specifies that the fault monitor fails over the MaxDB resource
False – Specifies that the fault monitor does not fail over the MaxDB resource
Boolean
True
Not applicable
Any time
Note - The Failover_mode=RESTART_ONLY setting matches the behavior of the Failover_enabled=False setting. The Failover_mode=LOG_ONLY setting goes a step further and prevents resources from restarting. Use the Failover_mode property instead of the Failover_enabled extension property to better control failover behavior. For more information, see the descriptions of the LOG_ONLY and RESTART_ONLY values for Failover_mode in r_properties(5).
The full path to the directory that contains the following programs and libraries for the MaxDB application:
Programs that are independent of the database software version
Libraries for the client runtime environment
Oracle Solaris Cluster HA for MaxDB determines the path to the dbmcli command from the value of this property. The dbmcli command resides in the bin subdirectory of the directory that this property specifies.
String
/sapdb/programs
Not applicable
When disabled
The maximum number of restarts by the process monitor facility (PMF) that are allowed for the fault monitor.
Integer
4
No range defined
Any time
The period of time in minutes during which the PMF counts restarts of the fault monitor.
Integer
2
No range defined
Any time
The full path to the directory under which files that store the process identities of MaxDB kernel processes are created. The process identities of MaxDB kernel processes are stored in the following files:
pid-dir/ppid/db-name
pid-dir/pid/db-name
The replaceable items in these file paths are as follows:
pid-dir is the directory that the Pid_Dir_Path extension property specifies
db-name is the name of the MaxDB database instance that the DB_Name extension property specifies
String
/var/spool/sql
Not applicable
When disabled
The timeout value in seconds that the fault monitor uses to probe an MaxDB database instance.
Integer
90
30–99,999
Any time
Determines whether the fault monitor restarts the MaxDB database instance if the parent kernel process is terminated. The possible values of this extension property are as follows:
True – Specifies that the fault monitor restarts the MaxDB database instance if the parent kernel process is terminated
False – Specifies that the fault monitor does not restart the MaxDB database instance if the parent kernel process is terminated
Boolean
False
Not applicable
Any time
The user key of the database user that administers the MaxDB database instance. This user key is created when MaxDB is installed and configured. See Installing and Configuring SAP MaxDB in Oracle Solaris Cluster Data Service for SAP MaxDB Guide.
String
No default defined
Not applicable
When disabled
Example 1 Creating a SUNW.sapdb Resource
# clresource create -g sapdbrg -t SUNW.sapdb \\ -p DB_Name=TST -p DB_User=dbadmin -p User_Key=DEFAULT \\ -p resource_dependencies=hsprs sapdbrs
This example shows the creation of a SUNW.sapdb resource that has the following characteristics:
The resource is named sapdbrs.
The resource is a member of a resource group that is named sapdbrg. The creation of this resource group is not shown in this example.
The resource is an instance of the SUNW.sapdb resource type. The registration of this resource type is not shown in this example.
The MaxDB database instance that is associated with this resource is named TST.
The UNIX user identity of the OS user that administers the MaxDB database is dbadmin.
The user key of the database user that administers the MaxDB database is DEFAULT.
The MaxDB resource depends on an HAStoragePlus resource that is named hsprs. The creation of the hsprs resource is not shown in this example.
This example does not show the creation of the logical host resource that the MaxDB resource uses.
See attributes(5) for descriptions of the following attributes:
|
clresourcegroup(1CL)clresourcetype(1CL), clresource(1CL), attributes(5), r_properties(5), SUNW.sap_xserver(5).