Documentation Updates and Clarifications

This section contains updates and clarifications for Adaptive Server documentation.

Installation Guide

Clarification for step 5: If Java in database is enabled, then as part of the upgrade or installation instructions, you must create a device for sybpcidb database. In a high availability system, the device name must be unique across the high availability nodes requiring you to use a different name for each node in the high availability system. Use device names like:

sybpcidb_dev1
sybpcidb_dev2

Chapter 8 note needs to be updated.

This section contains a note that needs to be revised. Please consider this note instead.

Note: The start policy can also be "Bring Offline (on Error Node Only)" or " Never Fallback" for secondary companion in Asymmetric High Availabilityconfiguration.

In Chapter 8 "Configuring Adaptive Server for Failover on IBM AIX HACMP" the filepath for the cluster log file has changed. /tmp/hacm/.out should be /var/hacmp/log/hacmp.out.

The text:

"Stop the HACMP subsystem with the takeover mode on the primary node (See your IBM documentation for information). This shuts down the primary companion and fails over its resources to the secondary companion"

should be changed to

"Stop the HACMP subsystem with the Move Resource Group mode on the primary node (See your IBM documentation for information). This shuts down the primary companion and fails over its resources to the secondary companion."

The text found in Chapter 8 should read:

"To resume normal companion mode between two companions that have been moved to suspended mode:

Resume normal companion mode. From the secondary companion, issue: sp_companion primary_companion_name, resume
Restart monitoring by bringing the resource group offline and then online.
- First select System management (C-SPOC) | HACMP Resource Group and Application Management | Bring a Resource Group Offline.
- First select System management (C-SPOC) | HACMP Resource Group and Application Management | Bring a Resource Group Online.

The text currently reads "HA_LOGIN - the login of the user with the sa_role and ha_role. This must be the same on the primary and secondary companion." When using HA_LOGIN add this username to 'hacmp' group and make sure /etc/es/objrepos/HACMPgroup & HACMPresource files have 'hacmp' group access.