This topic describes how to create a Sybase Dataserver by using BMC Database Automation. This section also applies to creating a Veritas Cluster Services (VCS) clustered Sybase Dataserver. Any differences are noted.
To create a Dataserver as a standalone database, populate the Naming page as follows, and click Next.
Field | Description |
---|---|
Domain | Displays the BMC Database Automation domain containing the target host. |
Host | Displays the host selected for this provisioning activity. |
Sybase Version | Select the wanted version of Sybase to be installed. |
Template | (Optional) Select a BMC Database Automation template for this operation. See Managing templates for Sybase. If you select a template, click Skip Ahead to advance directly to the next step that requires input. An informational message appears on these steps, in green type, listing the fields that require entries before advancing to the next step. |
Display Name | Type the name that appears in the Management Console for this object. |
To create a Dataserver for a VCS cluster, provision the Naming page as follows, and click Next.
Field | Description |
---|---|
Domain | Displays the wanted location in which to create this new Dataserver. |
VCS Cluster | Displays the name of the VCS cluster in which the Dataserver is created. |
Host | Displays the wanted host in the cluster on which to create this new Dataserver. |
Sybase Version | Select the wanted version of Sybase to be installed. |
Template | (Optional) Select a BMC Database Automation template for this operation. See Managing templates for Oracle on Windows. If you select a template, click Skip Ahead to advance directly to the next step that requires input. An informational message appears on these steps, in green type, listing the fields that require entries before advancing to the next step. |
Display Name | Type the name of the new Sybase Dataserver you want to create. |
VCS Resource Group | (Optional) Specify the name of the group in which the VCS resources for the Dataserver and backup server are located. If a VCS Resource Group is specified, it must be active on the host you selected. If the VCS resources for the Dataserver and backup server already exist in the VCS cluster in which the Dataserver is being created, then the name specified in the Display Name field must match the name specified in the Server property of the VCS Sybase resource. If the VCS resources do not already exist, you must create a pre-provisioning script to create the resources before BMC Database Automation creates the Dataserver and backup server. |
In the Settings page, populate the following fields, and click Next.
Field | Description |
---|---|
Sybase Destination Directory | Type the location on the host where the Sybase home is created. Must be a valid UNIX directory. |
Install User | Type the user name that owns the home being installed and runs the Sybase servers. |
Installer Template | Displays the Sybase installer template for the appropriate version, either 15 or 12. |
In the Licensing Configuration page, populate the following fields, and click Next.
Field | Applies to | Description |
---|---|---|
Configure Licensing |
| (Optional) Select if you want to configure licensing. |
License Options |
|
|
License Edition | Sybase version 15 only | Select the type of edition for the license. |
License Type | Sybase version 15 only | Select the type of license. |
License Hostname | Obtain License from SySAM Server | Type the host name of the SySAM server. This field is required when obtaining a license from a SySAM server. |
License Port Number | Obtain License from SySAM Server | Type the port number for connecting to the SySAM server. |
License File | Pre-generated License | Type the text of a pre-generated license obtained from Sybase. |
License Feature | Generate License | Type data obtained from Sybase in order to generate a license. |
License Feature Count | Generate License | Type data obtained from Sybase in order to generate a license. |
License Order | Generate License | Type data obtained from Sybase in order to generate a license. |
License Version | Generate License | Type data obtained from Sybase in order to generate a license. |
License Authorization Code | Generate License | Type data obtained from Sybase in order to generate a license. |
If you are configuring Sybase 15, in the SySAM Notification Configuration page, populate the following fields, and click Next.
Field | Description |
---|---|
Configure Notification | (Optional) Select if you want to configure SySAM license notifications for the Dataserver. |
SMTP Server Hostname | Type the hostname of the SMTP server through which SySAM license notification is sent. |
SMTP Server Port Number | Type the port number of the SMTP server. |
Sender Email | Type the email address that you want to appear as the sender of SySAM license notifications. |
Recipient Emails | Displays the email addresses of the people who you want to receive the SySAM license notifications. Click Add Email to add additional email addresses. |
Severity | Select the severity level of the messages that is sent. Choices are Informational, Warning, Error or None. |
In the Adaptive Server Configuration page, populate the following fields, and click Next.
Field | Description |
---|---|
Adaptive Name | Displays the name of the Dataserver (as specified in Step 1). |
Adaptive Hostname | Type a host name that resolves to the IP address on which the Dataserver will listen to requests. |
Adaptive Port Number | Type the port number of the port on which the Dataserver will listen to requests. |
Adaptive Log Path | Type the path to the Dataserver logs. It must be a valid UNIX file path. |
Adaptive Page Size | Select the page size for the Dataserver. |
SA Password | The SA password for the Dataserver. A valid entry contains either six or more characters in length or is blank (that is, no password). |
Adaptive Resource File | The resource file used to construct the Dataserver by using the srvbuildres utility. |
In the Adaptive Device Settings page, populate the following fields, and click Next.
Section | Field | Description |
---|---|---|
Master Device Settings | Master Device | Type the path to the master device. It must be a valid UNIX file path. |
| Master Device Size | Type the size of the master device.
|
| Master Database Size | Type the size of the master database.
|
System Procedure Device Settings | System Procedure Device | Type the path of the system procedure device. It must be a valid UNIX file path. |
| System Procedure Device Size | Type the size (MB) of the system procedure device. It must be at least 132 MB. |
| System Procedure Database Size | Type the size of the system procedure database.
|
System Device Settings | System Device | Type the path of the system device. It must be a valid UNIX file path. |
| System Device Size | Type the size of the system device (in MB).
|
| System Database Size | Type the size of the system database.
|
In the Backup Server Configuration page, populate the following fields, and click Next.
Field | Description |
---|---|
Configure Backup Server | (Optional) Select if you want to configure a backup server for the Dataserver. |
Backup Name | Type the name of the backup server. |
Backup Hostname | Type a host name that resolves to the IP address on which the backup server will listen to requests. |
Backup Port Number | Type the port number of the port on which the backup server will listen to requests. |
Backup Log | Type the path for the backup logs. Must be a valid UNIX file path. |
Backup Resource File | The resource file used to construct the backup server by using the srvbuildres utility. |
In the Monitor Server Configuration page, populate the following fields, and click Next.
Field | Description |
---|---|
Configure Monitor Server | Select if you want to configure a monitor server for the Dataserver (versions 12.5.4 through 15.5 only). |
Monitor Name | Type the name of the monitor server. |
Monitor Hostname | Type a host name that resolves to the IP address on which the monitor server will listen to requests. |
Monitor Port Number | Type the port number for the port on which the monitor server will listen to requests. |
Monitor Log | Type the path to the monitor server logs. It must be a valid UNIX file path. |
Monitor Resource File | The resource file used to construct the monitor server by using the srvbuildres utility. |
In the XP Server Configuration page, populate the following fields, and click Next.
Field | Description |
---|---|
Configure XP Server | Select if you want to configure an XP server for the Dataserver. |
XP Name | Type the name of the XP server. |
XP Hostname | Type a hostname that resolves to the IP address on which the XP server will listen to requests. |
XP Port Number | Type the port number of the port on which the XP server will listen to requests. |
XP Log | Type the path to the XP server logs. It must be a valid UNIX file path. |
XP Resource File | The resource file used to construct the XP server by using the srvbuildres utility. |
In the Localization Configuration page, populate the following fields, and click Next.
Field | Description |
---|---|
Configure Localization | Select if you want to configure localization for the Dataserver. |
Default Language | Select the default language of the Dataserver. |
Install Languages | Specify the install languages for the Dataserver. Must contain at least the language specified in the Default_Language field. |
Localization Resource File | The resource file used to localize the Dataserver by using the sqlloc utility. |
In the Character Set Configuration page, populate the following fields, and click Next.
Field | Description |
---|---|
Default Character Set | Select the default character set for the Dataserver. |
Install Character Set | Specify the character sets to be installed on the Dataserver. Minimally, the list must contain the character set specified in the Default Character Set field. |
Sort Order | Select the sort order for the Dataserver. This is determined by the Default Character Set field setting. |
In the Custom Scripts Configuration page, select the pre-provisioning and post-provisioning scripts as follows, and click Next.
Field | Description |
---|---|
Pre-Provisioning Script Directory | (Optional) Select the scripts that you want to run before the Sybase binaries are installed (or, if you are creating a Dataserver in an existing home, before the Dataserver is configured) and click to move them to the Selected list box. The scripts in Selected are run in the order listed. Use Move Up and Move Down to re-order the scripts when necessary. See also Managing pre-provisioning and post-provisioning script files. |
Post-Provisioning Script Directory | (Optional) Select the scripts that you want to run after this event and click to move them to the Selected list box. See also Managing pre-provisioning and post-provisioning script files. |
In the Job Options page, specify any of the following Job options, and click Next.
Type | Option | Description |
---|---|---|
Notification Emails | Email List | (Optional) Click Add Email to add email addresses to the notification list. |
Job Administration | Cleanup Agent Logs | (Optional) Select to automatically remove logs that are generated by BMC Database Automation on the Agent after the Job is complete. |
If the Change Control page displays, populate the following fields, and click Next.
Section | Field | Description |
---|---|---|
| Bypass Change Control | (Optional) Select to bypass using BMC Remedy ITSM to control the change process. Selecting this option removes the rest of the fields from this page. |
| Change Control Options | Select to determine whether to open a new BMC Remedy ITSM change ticket, or to use an existing BMC Remedy ITSM change ticket to control the change process.
|
Use Existing Change Ticket | ITSM Change ID | Specify the BMC Remedy ITSM change ticket number to associate with this change process. |
| ITSM Task ID | Specify the BMC Remedy ITSM task ID number to associate with this change process. |
Create New Change Ticket | Change Type | Assign the type of change for the new BMC Remedy ITSM change ticket. |
| Change Impact | Assign the impact level of this change process for the new BMC Remedy ITSM change ticket. |
| Change Urgency | Assign the urgency level for the new BMC Remedy ITSM change ticket. |
| Change Risk-Level | Assign the risk level of this change process for the new BMC Remedy ITSM change ticket. |
| Change Class | Assign the change class for the new BMC Remedy ITSM change ticket. |
| Change Summary | Type a summary of the change process. |
Note
The Change Control page appears only when change control is configured for your environment. See Configuring change control.
To create the database without having first run the pre-verification steps, select Skip Pre-Verification Tests.
Note
The Skip Pre-Verification Tests option should only be used when you are certain all tests can succeed. The option skips verification and advances directly to the actual provisioning activity.
Click Create Sybase Dataserver.
If you disabled the Automatically Continue If All Tests Succeed option, you are prompted to click Continueafter the pre-verification steps are done.
Note
If you close your browser or leave the pre-verification page before all checks are completed, the operation cannot continue.
After the pre-verification steps are completed or have been skipped, the Dataserver creation process begins and a progress page appears.
Note
If you close your browser, the operation continues. You can return to this page by using the Jobs page.
Click Done to complete this step and return to the Contents view of this domain.
Note
Detailed current and historical information surrounding BMC Database Automation Job activities can be viewed in the Jobs section of the Management Console. See Monitoring jobs and viewing job history.