Register a Sybase database instance

The following sections provide instructions for using a wizard to register a self-managed Sybase database instance for monitoring with DPA.

If you register a database instance within the 14-day trial period, DPA begins monitoring the instance immediately. After the trial period, you must activate a license to monitor the database instance.

Options for creating the monitoring user

The DPA monitoring user must be created to enable DPA to monitor a database instance. If DPA is not integrated with CyberArk, the following options in the registration wizard determine how the monitoring user and utility package are created or configured.

If DPA is integrated with CyberArk, these options are not displayed. You must create the monitoring user.

• I will create the monitoring user manually.

  With this option, you run a script to create the monitoring user and another script to configure the database instance. Then you use the wizard to complete the registration. You are not prompted to enter privileged user credentials into DPA. The DPA monitoring user is not assigned the sa_role.

  For detailed information about the privileges granted to the monitoring user and the changes made to the database instance, see this article.

  To use this option, see Register a Sybase database instance and create the monitoring user yourself below.

• DPA will create/configure the monitoring user.

  With this option:

  • You must provide the credentials of a user with the sa_role so that DPA can create or configure the monitoring user.
  • The monitoring user is assigned the sa_role.

  DPA does not store the user credentials. To use this option, see Register a Sybase database instance and let DPA create the monitoing user below.

Register a Sybase database instance and create the monitoring user yourself

Task 1: Create the monitoring user

1. Copy one of the following scripts to a file. These scripts create the monitoring user.

   • For a Sybase 15.7 or later instance: CreateMonUserSybase15-7orLater.sql

   • For a Sybase instance earlier than 15.7: CreateMonUserSybaseBefore15-7.sql

2. Edit the script to update the user name and password values.

3. Copy the following script to a file: ConfigureDbInstanceSybase.sql.

   This script configures the database instance. The same script is used for all versions.

4. Connect to the Sybase database instance and the first script and then the second script. To ensure that the connected user has all the privileges needed to create the monitoring user, SolarWinds recommends connecting as a user with the sa_role to run the script.

Task 2: Complete the registration wizard

1. In the upper-left corner of the DPA home page, click Register DB Instance for Monitoring.
2. Under Self-managed, select SAP Sybase ASE.
3. If the monitoring user prompt is displayed, select I will create the monitoring user manually. Then click Next.

4. Complete the Connection information panel:

   1. Enter the host name or IP address of the server that hosts the database instance.

   2. Verify or update the port used for the connection.

      DPA monitors all databases within the instance. If more than one instance exists on the server, you must register each instance separately in DPA.

   3. Under SSL mode (if SSL mode is enabled), specify the type of secure socket layer (SSL) connections established between the instance and the DPA server.

      SSL connections are not available if LDAP is selected as the Connection method.

      SSL mode	Description
      Disable	SSL encryption is not used.
      Validate server certificate	SSL is enabled. The client verifies that the server is trustworthy by checking the certificate chain up to a trusted certificate authority (CA).
      Validate server certificate and match hostname	SSL is enabled. The client verifies the certificate chain and also verifies that the server hostname matches its certificate's Subject Alternative Name or Common Name (CN).

   4. Enter the user name and password of the monitoring user created previously. Or, if DPA is configured to use CyberArk, enter the CyberArk credentials query for the monitoring user.

   5. Click Next.

      DPA validates the connection information and the privileges of the monitoring user.

5. Specify the following Instance options.

   The instance name and group membership can be changed after registration.

   1. If your repository database is Oracle, choose the tablespace in the repository database to store DPA performance data for this monitored instance.

      By default, the performance data is stored in the default tablespace of the repository user. However, data for monitored instances can be stored in separate tablespaces.

   2. Enter the name that DPA will display to identify this database instance.

      The Display name field defaults to the name retrieved from the database instance.

   3. (Optional) If you have manually created instance groups, you can assign this database instance to one of the groups.

      If no manual groups exist, this option is not shown.

   4. (Optional) If you have existing alert groups, you can assign this database instance to one or more groups.

      If no alert groups exist, or the existing groups do not match this instance's database type, this option is not shown.

   5. Click Next.

6. Review the information on the Summary page. Click Back if you need to make changes. When the information is correct, click Register.

Register a Sybase database instance and let DPA create the monitoring user

Task 1: Identify the privileged user

When you register a database instance using this option, you must provide the credentials of a privileged user. During registration, the privileged user either creates the monitoring user or grants the required privileges to an existing user that you designate as the monitoring user. DPA does not store the credentials of the privileged user. 

For self-managed Sybase database instances, the privileged user requires the sa_role. To create a new monitoring user, the sso_role is also required. The privileged user cannot be the repository database user.

Task 2: Complete the registration wizard

1. In the upper-left corner of the DPA home page, click Register DB Instance for Monitoring.
2. Under Self-managed, select SAP Sybase ASE.
3. At the monitoring user prompt, select DPA will create/configure the monitoring user. Then click Next.

4. Complete the Enter Monitored Database Instance Connection Information panel:

   1. Enter the host name or IP address of the server that hosts the database instance.

   2. Verify or update the port used for the connection.

      DPA monitors all databases within the instance. If more than one instance exists on the server, you must register each instance separately in DPA.

   3. In the Admin Username and Password fields, enter credentials for the privileged user that DPA can use to register the instance.

      DPA does not use or store these credentials after you complete the wizard.

   4. Click Next.

      DPA validates the connection information and the privileges of the privileged user.

5. Create or specify the account that DPA will use to gather information (the monitoring user).

   To ensure that the account has the required permissions, SolarWinds recommends creating a new account.

   • To create a new account:

     1. Next to Create Monitoring User, select Yes.
     2. Enter a user name and password for the new account, or accept the default values.
     3. Click Next.

   • To specify an existing account:

     1. Next to Create Monitoring User, select No.

     2. Select either authentication method.

     3. Enter the user name and password of an existing account.

        DPA requires the monitoring user to have sa_role and mon_role privileges for data collection.

        DPA ignores data on the monitored database instance from the monitoring user. Make sure the monitoring user will not cause load on the monitored instance.

     4. Click Next.

        If your repository database is Oracle, the Oracle Repository Tablespace panel opens. If not, continue with step 7.

6. If your repository database is Oracle, choose the tablespace in the repository database to store DPA performance data for this monitored instance. Then click Next.

   By default, the performance data is stored in the default tablespace of the repository user. However, data for monitored instances can be stored in separate tablespaces.

   If your repository database is not Oracle, the wizard skips this step.

7. (Optional) Select the alert groups you want the new database instance to join. Then click Next.

   • If no alert groups exist, or the existing groups do not match the database type of this instance, the wizard skips this step.

   • Group membership can be changed after registration

8. Review the information, and click Register Database Instance.

9. When the registration is complete, click Finish to return to the DPA home page.

The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.