Creating a Cluster

Create and configure a shared-disk cluster.


Complete the preparation steps for creating a cluster.

  1. In the Perspective Resources view, select a server, then select Resource > Administration Console.
  2. In the left pane of the Administration Console, select ASE Servers, click the drop-down arrow, then select Create Cluster.
    Optionally you can click ASE Servers, then from the menu bar, click Folder > Create Cluster.
  3. On the Introduction screen:
    • Provide a name for the cluster, or,
    • Import an existing cluster file.
    Note: Once you have entered the information to create a cluster into the wizard, you can export the information to a file on the final Summary screen.
  4. On the Options screen:
    1. Select your platform. All nodes must use the same operating system and 64-bit hardware architecture.
    2. Choose Shared or Private installation.
    3. Specify the number of instances allowed. The maximum number allowed is 4.
  5. On the Nodes screen, click Add to specify the hosts that will participate in the cluster. Provide the host name, the SCC agent port number, and the SCC agent user name and password.
  6. On the Quorum Device screen, enter the full path to the device. The quorum device is a communications medium and synchronization point that provides a location to perform cluster membership management. It also provides a persistent place to store configuration data used by instances and the Unified Agent.
    If a cluster agent plug-in exists, you can either accept the existing plug-in or create a new one.
  7. The Cluster Environment screen is specific to a shared installation. List any start-up parameters and trace flags. For a private installation, this information is specified when you define instances for the cluster.
    If a Veritas Cluster Server (VCS) base device is detected on the system, you are prompted to integrate the ASE Cluster Edition Dataserver with the Veritas Cluster Server. See Using the Cluster Edition with the Veritas Cluster Server in the Clusters Users Guide.
    If an LDAP environment is detected, see Using LDAP as a Directory Service in the Clusters Users Guide.
    If the devices you specify in the following steps do not include SCSI-3 PGR capability or support I/O fencing, you can continue, not continue, or ignore further messages regarding SCSI-3 PGR capability or I/O fencing support. This dialog does not appear if a VCS device is detected.
  8. On the Master Device screen, enter the full path to the device, the device size, database size, and the page size of the instance.
  9. On the System Procedures Device screen, enter the full path to the device, the device size, and the database size.
  10. On the System Database Device screen, enter the full path to the device, the device size, and the database size.
  11. (Optional) On the PCI Device screen, click to enable the PCI device, then enter the full path to the device, the device size, and the database size.
    See Java in Adaptive Server Enterprise for more information about PCI devices.
  12. On the Network Protocol screen, verify or update the network protocol:
    1. The UDP network protocol.
    2. Choose an unused starting port number for the cluster’s network interconnects.
    3. (Optional) Click the box if you have a secondary network available.
    4. (Optional) Click Validate Port to make sure the ports are not currently in use.
  13. On the Instance screen, click Add to add instances to the cluster.
    You see the Define Server Instance screen with the tabs General, Local System Temporary Database, and, for a private installation, Private.
  14. On the General tab:
    1. Select the node where the instance will be located.
    2. Enter the instance name.
    3. Select a query port number, then select Validate Port to make sure this port is available.
    4. Select a primary and secondary network address. The Secondary option is enabled if you specified on the Network Protocol screen that a secondary address is available.
    5. Provide a full path to the error log for this instance.
    6. List any start-up parameters for the instance.
    7. List any trace flags to use at start-up.
  15. The Local System Temporary Database tab shows default values for local temporary databases. A shared-disk installation requires a local system temporary database. Accept the defaults or change the database device values.
  16. (Optional) Click Summary to review the information you have provided.
  17. (Optional) Click Automatically start the cluster after it is successfully created.
  18. (Optional) Click Export to save the cluster information to a file.
  19. Click Next to create the cluster.
    Note: You cannot start this cluster from the command line using a run_server file. To start the cluster, the agent must be running on each node and the cluster must be registered with SAP Control Center.