Using the SQL interactive interface in GUI mode

You can use the SQL interactive interface to configure the ObjectServer by issuing SQL commands.

About this task

Note: Only users that are members of a group granted the ISQL role can access an ObjectServer by using the SQL interactive interface. Only users that are members of a group granted the ISQLWrite role can update ObjectServer data by using the SQL interactive interface.

To open the SQL interactive interface in GUI mode:

Procedure

  1. From the Netcool/OMNIbus Administrator window, select the System menu button.
  2. Click SQL.
    The SQL pane opens.
  3. Complete this window as follows:
    SQL editor
    Use the text field and buttons in this area to issue commands. Type SQL in the text field, and use a semi-colon to separate multiple commands. You can use the SQL helper buttons and the additional buttons to facilitate the creation of SQL commands.
    When typing SQL commands within the Tivoli Netcool/OMNIbus SQL editor panels, you can type one or more characters and then press Ctrl+F1 to obtain a dialog box with a list of keywords that might match your entry. Select the required keyword and click OK to complete your entry. If only one keyword matches your typed characters, the keyword is automatically completed for you. If you press Ctrl+F1 after typing a database-related keyword, the dialog box provides a list of possible ObjectServer databases from which you can select. If you press Ctrl+F1 after typing a database name followed by a dot (for example: alerts.), you can press Ctrl+F1 again to view and select from a list of tables in the database.
    The following table describes the helper buttons.
    Table 1. SQL interactive interface buttons
    Button Description
    This figure shows the SQL Commands helper button.
    Click this button to select an SQL command from the pop-up menu. Based on the command that you select, complete the resulting window as follows:
    • Select: Select the database and table on which to run the SELECT command. Then, choose the table columns to select.
    • Insert: Select the database and table on which to run the INSERT command. Then, select the table columns in which to insert values. For each selected column, enter the value to insert. For insert statements, you must include the primary key. Primary keys are indicated with an asterisk (*).
    • Update: Select the database and table on which to run the command. Then, select the table columns to update. For each selected column, enter the new value. For update statements, you must exclude the primary key. Primary keys are indicated with an asterisk (*).
      Note: For inserts and updates to the alerts.status table, any existing conversions appear in the drop-down lists.
    • Delete: Select the table to delete.
    • Use: Select the database to use.
    • Service: Select a service name and a value. Values can be Good, Marginal, or Bad.
    This figure shows the Columns helper button.
    Click this button to select a table column name to add to the command. The column name is substituted for the corresponding event list row value when the tool runs. When prefaced with the @ symbol, the column name is substituted with the corresponding event list row value during execution. This can be used in an SQL query or restriction filter, such as: RemoteNodeAlias = '@LocalNodeAlias'
    This figure shows the Conversions helper button.
    Click this button to select from a list of available conversions. Double-click to add the conversion.
    This figure shows the Clear SQL helper button.
    Click this button to clear the entered SQL.
    This figure shows the SQL Keywords helper button.
    Click this button to bring up a list of keywords that complete the entered SQL.
    This figure shows the Check SQL Syntax helper button.
    Click this button to check the validity of the entered SQL syntax.
    This figure shows the Check SQL File helper button.
    Click this button to locate a file of type .sql or .ed and check the validity of its syntax. On completion, the results are displayed. (When you use an external editor to create or edit triggers and procedures, they are saved as .ed files.)
    This figure shows the SQL Submit helper button.
    Click this button to submit the SQL commands.
    After you complete the SQL command, click Submit.
    History
    This drop-down list provides a history of the SQL commands entered. You can select a previously-issued command from the list. You can also clear the list of previously-issued commands by right-clicking over the list and selecting Clear History.
    Result View
    After issuing the command, a visual representation of the table on which you performed the SQL command is displayed in this tab.
    Console View
    A command history is displayed in this tab.