Chapter 12: Active-Passive Configuration for Sun Cluster 3.0

Configuring the Adaptive Server resource group

Modify the Adaptive Server resource type registration file SY.ase. This file is located in $SYBASE/$SYBASE_ASE/SC-3_0/etc/. Find the line for the resource type property, RT_BASEDIR, which specifies the location of the Adaptive Server high availability agent. Change the value to point to the installation location of $SYBASE/$SYBASE_ASE/SC-3_0/bin.

For example:
```
RT_BASEDIR=/sybase/ASE-12_5/SC-3_0/bin/
```
Create or edit a file that contains Adaptive Server login information for the System Administrator and the user you added for the fault monitor. The default file is $SYBASE/$SYBASE_ASE/SC-3_0/etc/ase_login_file. If you use another file at a different location, specify the full path for the resource extension property Dataserver_login_file when configuring the SY.ase resource. Create or edit a file that contains Adaptive Server login information for system administrator and the user you added for the fault monitor. The default file is $SYBASE/$SYBASE_ASE/SC-3_0/etc/ase_login_file.

The file consists of two lines; the first line is the login and password of the System Administrator, and the second line is the login and password of monitor_user. The fault monitoring program, ase_monitor, performs the thorough probe as user monitor_user.
```
login_type <tab> login_string
login_type <tab> login_string
```
Valid values for login type are “encrypted” and “normal”. If you set login_type to “normal”, the value of the login_string is in the form “login_name/password”. If you set login_type to “encrypted”, the value of login_string is the encrypted string you get from the haisql utility (located in $SYBASE/$SYBASE_ASE/bin). Sybase recommends usage of “encrypted” login_type so the sensitive information in the file is well protected. To use haisql to generate the encrypted login string:
1. Run haisql with no arguments to generate the encrypted string for a given login_name and password:
```
/$SYBASE/ASE-12_5/bin/haisql
Enter Username: sa
Enter Password:
TWAS8n1jSF2gBsvayUlw97861.cyTKaS1YhavBRQ2qKcJwtx.TmFBarGS2Kl553WDR7g8m5vrf86t@K4CU62HEccm4zkeexsP9E=FeuvX
```
2. Copy and then paste the encrypted string to the ase_login_file.
The following is an example of the ase_login_file using the “encrypted” login type:
```
encrypted
TWAS8n1jSF2gBsvayUlw97861.cyTKaS1YhavBRQ2qKcJwtx.TmFBarGS2Kl553WDR7g8m5vrf86t@K4CU62HEccm4zkeexsP9E=FeuvX
encrypted
rX2S8n1jSF2gBuD0q=AXEXKCZvzGcK5K3kWnp_P+e4avf=67kYVSzy7+h640@97FSP_dlkH_oV2Zima5+7tUyHnsm4zmSIHIUnKSTPoTD
```
The following is an example of the ase_login_file using “normal” login type:
```
normal    sa/sa_password
normal     monitor_user/monitor_user_password
```
The two lines of the ase_login_file may use different login types. You should protect the ase_login_file with proper access permissions, particularly if you are not using the encrypted login strings. Perform the following to make the file readable only to the “root” user after editing the file with proper login_type and login_string values:
```
chmod 400 ase_login_file
chown root ase_login_file
chgrp sys ase_login_file
```
Create or edit the sysc_input_file and run syscadm, which registers the resource type, creates the resource group, adds resources to the resource group, and establishes resource dependencies. For example:
```
syscadm -c primary 
-f $SYBASE/$SYBASE_ASE/SC-3_0/etc/sysc_input_file
```
For more information, see “Using the syscadm script”.

You can also run the steps performed by the syscadm command manually. See “Configuring the resource group manually” for more information.

For a list of the extension properties see Table 10-1.
Run scswitch to:
- Move the resource group to managed state.
- Enable all resources and their monitors.
- Bring the resource group online on the primary node.
```
scswitch -Z -g resource_group_name
```
For example:
```
scswitch -Z -g rg_MONEY
```

View this book as PDF