Setting SQLSTATE-specific Error Handling

  1. In Silk Performer, expand the Profiles node in the Project tree.
  2. Right-click the profile that you want to configure and choose Edit Profile.
    Tip: Alternatively, you can choose Settings > Active Profile from the menu bar.

    The Profile - [<profile name>] dialog box opens, and the Replay category is displayed in the shortcut list on the left.

  3. In the shortcut list, click the Database icon.
  4. Click the SQLSTATE tab.
  5. Use the Simulation exceptions list to define exceptions for specific ODBC error codes to prevent termination of the simulation. When a database error occurs, Silk Performer automatically terminates the entire simulation. This list includes all the exceptions that Silk Performer uses for handling database-specific errors. The Error field lists the native error code. The Class field ranks the severity of the error. Class 0 errors can be handled within a Silk Performer transaction. Class 1 errors end the transaction but do not cause the simulation to terminate.
  6. To add an error to the list of database-specific error exceptions, click the Add button. The Edit Error dialog box opens.
    1. In the Error field, add the error code for an error to be added to the exceptions list.
    2. In the Class field, add the error class.
    3. In the Description field, add a description for the error.
    4. Click OK.
  7. To edit an error, select it from the list, and click Edit. The Edit Error dialog box opens.
    1. Edit the error code, class, and description as required.
    2. Click OK.
  8. To remove an error from the exceptions list, select it and click the Remove button.
    1. Click Yes on the deletion confirmation dialog.
  9. On the Profile - [<profile name>] dialog box, click OK to save your changes.
Parent topic: Database Settings