Creating an instance of DB2 on Linux and Unix

This topic describes how to add a DB2 single-instance database using BMC Database Automation (BDA).

Before you begin

• A node must be available for provisioning and must meet all of the DB2 database prerequisites.

To create a single-instance DB2 database

1. From the Management Console, select the domain in the Grid within which you want to create a single-instance DB2 database.
2. In the Node Configuration section, select Provision > Add DB2 Instance.

3. In the Naming page, populate the following fields, and click Next.

   Field	Description
   Domain	Displays the location in which the new database will be created.
   Host	Displays the host on which this new database will be created.
   Version	Select the version of DB2 that you want to be installed.
   Template	(Optional) Select a BMC Database Automation template for this operation. See Managing templates for DB2. If you select a template, you can 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.
   Instance Name	Type the name of the new DB2 instance that you want to create. The name must match the name of the "instance user" for the instance. The name must be an alphanumeric value (including underscores), and cannot start with a number.

4. Click Next on the Custom Fields page.
5. If you have previously discovered a DB2 instance, select one of the following options in the Copy Selection page:
   1. Select Create New Copy to create a new DB2 copy and proceed to the next step to configure installation settings for the new copy.
   2. If a copy already exists, select that copy from the menu and proceed to Step 8 to configure the DB2 instance. 

6. In the Installation Settings page, populate the following fields, and click Next.

   Field	Description
   Installation Type	Select the type of installation you want for the DB2 instance: Root Copy. Specifies that the files in the DB2 copy will be owned by the root user. If this option is selected, the Installation Directory field displays where you must type the directory in which the files for the DB2 database product will be installed. Note: This type of installation enables you to create multiple instances, and ownership of those instances is associated with the user ID under which the instance was created. Non-root Copy. Specifies that the files in the DB2 copy will be owned by a user who does not have root privilege. If you select this option, the non-root user must already exist on the target host, which displays in the Non-root Copy User Name field. Non-root installations can have only one DB2 instance. The installation directory contains all the DB2 database product files and instance files with no soft links. Unlike root-owned copies, users installing non-root copies cannot choose where DB2 database products will be installed. Non-root installations are always placed in the $HOME/sqllib directory, where $HOME represents the non-root user's home directory. The layout of the subdirectories within the sqllib directory of a non-root is similar to that of a root installation.
   Installation Directory	(Root Copy installations only) Specify the installation directory of the DB2 root copy.
   Non-root Copy User Name	(Non-root Copy installations only) Displays the user name of the DB2 non-root copy.
   Copy Response File	Click Edit to edit the text of the response file that will be used to install the copy.

7. If the Configure DAS page displays (for root installations on nodes where a DB2 instance does not already exist), populate the following fields, and click Next.

   Field	Description
   Configure DAS	Select to configure the DB2 Administration Server (DAS).
   DAS User Options	Select Create New User to create a new DAS user. Selecting this option expands the dialog box to enable you to set new user options. Select Use Existing User to use a DAS user already created.
   User Name	Type the username in the field. If you selected Use Existing User, this username will be validated before proceeding to the next step in the wizard.
   UID	(New User Only) Type the UID for the DAS user, or leave the field blank for the next available UID.
   GID	(New User Only) Type the GID for the DAS user, or leave the field blank for the next available GID.
   Group Name	(New User Only) Type the name of the default group for the DAS user.
   Password	(New User Only) Type the DAS user's password.
   Confirm Password	(New User Only) Retype the DAS user's password.
   Home Directory	(New User Only) Type the full path of the DAS user's home directory, or leave blank to accept the default directory.

8. (For root installs configured with a DAS only) In the DAS Notifications Configuration page, populate the following fields, and click Next.

   Field	Description
   Configure Notifications	Select to configure DAS notifications. When you select this option, additional configuration options display, as detailed in the following descriptions.
   SMTP Server	Type the name of the SMTP server on which notifications will be sent.
   Contact List Location	Select Local or Remote from the menu list box to specify where the contact list for notifications resides. Selecting Remote displays additional options where you specify the remote server, username, and password for the server on which the contact list resides.

9. In the Instance Configuration page, populate the following fields, and click Next.

   Field	Description
   Specify TCP/IP Service Name/Port	Select to manually configure TCP/IP for the DB2 instance. Selecting this option displays fields for you to type the service name and port number.
   Autostart Instance On System Startup	Select to automatically start the DB2 instance when you start the system.
   Start Instance On Job Completion	Select to start the DB2 instance after completion of a job.
   Instance Response File	Click Edit to edit the text of the response file that will be used to install the instance.

10. In the Instance User Configuration page, populate the following fields, and click Next.

    Field	Description
    Instance User Options	Select Create New User to create a new instance user. Selecting this option expands the dialog box to enable you to set new user options. Select Use Existing User to use a user already created.
    User Name	This field will display the name you provided in the Instance Name field in step 3.  It cannot be changed at this point. If you selected Use Existing User, this username will be validated before proceeding to the next step in the wizard.
    UID	(New User Only) Type the UID for the instance user, or leave the field blank for the next available UID.
    GID	(New User Only) Type the GID for the instance user, or leave the field blank for the next available GID.
    Group Name	(New User Only) Type the name of the instance user's default group.
    Password	(New User Only) Type the instance user's password.
    Confirm Password	(New User Only) Retype the instance user's password.
    Home Directory	(New User Only) Type the full path of the instance user's home directory, or leave blank to accept the default directory.

11. In the Fenced User Configuration page, populate the following fields, and click Next.

    Field	Description
    Fenced User Options	Select Create New User to create a new fenced user. Selecting this option expands the dialog box to enable you to set new user options. Select Use Existing User to use a user already created.
    User Name	Type the username in the field.  If you selected Use Existing User, this username will be validated before proceeding to the next step in the wizard.
    UID	(New User Only) Type the UID of the fenced user, or leave the field blank for the next available UID.
    GID	(New User Only) Type the (GID of the fenced user, or leave the field blank for the next available GID.
    Group Name	(New User Only) Type the name of the fenced user's default group.
    Password	(New User Only) Type the fenced user's password.
    Confirm Password	(New User Only) Retype the fenced user's password.
    Home Directory	(New User Only) Type the full path of the fenced user's home directory, or leave blank to accept the default directory.

12. In the Custom Scripts Configuration page, select any pre-provisioning or post-provisioning scripts that you want to run as follows, and click Next.

    Field	Description
    Pre-Provisioning Scripts	(Optional) Select the scripts that you want to run before either installing the DB2 copy or configuring the DB2 instance 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 Scripts	(Optional) Select the scripts that you want to run after configuring the DB2 instance and click to move them to the Selected list box. See also Managing pre-provisioning and post-provisioning script files.

13. 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.
    	SNMP	(Appears when SNMP is configured) Select to send the results of this job to an SNMP destination. See Configuring SNMP.
    Job Administration	Cleanup Agent Logs	(Optional) Select to automatically remove logs that are generated by BDA on the Agent after the job is complete.

14. 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. Selecting Use Existing Change Ticket displays the fields in the Use Existing Change Ticket section on this page. Selecting Create New Change Ticket displays the fields in the Create New Change Ticket section on this page.
    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.

15. 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.
16. 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.

      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.

17. Click Create DB2 Instance.
    If you disabled the Automatically Continue If All Tests Succeed and Skip Pre-Verification Tests options, you are prompted to click Continue after the pre-verification steps are done.
    The database 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.

18. (Optional) Click View Log to view log file details or Download Log Package to download full log details.
19. Check the Results section for the Success message.

20. Click Done and return to the Contents view of this domain.

    Note

    Detailed current and historical information about this action can be viewed in the Jobs section of the Management Console. See Monitoring jobs and viewing job history.