Creating a Sybase Dataserver

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.

Before you begin

• A node is available to be used for provisioning.
• The node meets all of the system requirements defined in the Adaptive Server Enterprise Installation Guide.
• Sybase Adaptive Server media is mounted on the node as described in Sybase media location requirements.

To create a Sybase Dataserver

1. From the Management Console, select the node on which you want to create a Sybase Dataserver.
2. Select Provision > Add Sybase Dataserver.
3. To create a Dataserver as a standalone database, provision the Naming page as follows, and click Next. The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
4. To create a Dataserver for a VCS cluster, provision the Naming page as follows, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
5. If a Sybase home exists for the version of the database being provisioned, either select an existing home for the Dataserver, or select Create New Home in the Use Existing Homes field of the Use Existing Home page, and click Next.
    If you selected an existing home, the wizard skips to the Adaptive Server Configuration step.
6. If a Sybase home does not exist for the version of the database being provisioned, select Create New Home in the Use Existing Homes field of the Use Existing Home page, and click Next.
7. In the Settings page, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
8. In the Licensing Configuration page, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
9. If you are configuring Sybase 15, in the SySAM Notification Configuration page, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
10. In the Adaptive Server Configuration page, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    
11. In the Adaptive Device Settings page, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    
12. In the Backup Server Configuration page, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    
13. In the Monitor Server Configuration page, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    
14. In the XP Server Configuration page, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    
15. In the Localization Configuration page, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    
16. In the Character Set Configuration page, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    
17. In the Custom Scripts Configuration page, select the pre-provisioning and post-provisioning scripts as follows, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    
18. In the Job Options page, specify any of the following Job options, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    

19. If the Change Control page displays, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    

    Warning

    Note

    The Change Control page appears only when change control is configured for your environment. See Configuring-change-control.

20. In the Summary page, review the provisioning information.
     To make changes, do the following:
    1. Click Go to to return to the provisioning step that you want to edit.
    2. Make your changes.
    3. Click Save and Review to return to the Summary page.
21. Specify your verification preferences.
     For additional information, see Understanding pre-verification tests.
    • To continue with database creation after the pre-verification tests have been successfully run without manual intervention, select Automatically Continue If All Tests Succeed.

    • To create the database without having first run the pre-verification steps, select Skip Pre-Verification Tests. 

      Warning

      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.

22. Click Create Sybase Dataserver.
     If you disabled the Automatically Continue If All Tests Succeed option, you are prompted to click Continue after the pre-verification steps are done. 

    Warning

    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. 

    Warning

    Note

    If you close your browser, the operation continues. You can return to this page by using the Jobs page.

23. Click the magnifying glass icon to view log file details.
24. If this procedure was not successful, see Troubleshooting.

25. Click Done to complete this step and return to the Contents view of this domain. 

    Warning

    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.