General issues


The following table lists the issues that you might face while working with the KM and the recommended solutions for the issues.

Issue

Resolution

SQL query is displayed even after deleting it 

Even if you delete all custom SQL queries from the configuration settings, the last executed SQL query is still displayed on the console, restart the PATROL Agent or enable the policy.

Configuration fails or connection is refused sometimes when you use JDBC to connect to DB

As JAVA is not compatible with the JRE, no data is collected and hence the MonitoringStatus parameter is in the offline state. To resolve this situation, check if the JAVA is compatible with the JRE that you have by using the envChecker utility.

If the connection is refused, verify the following:

  • inputs are valid
  • there is a firewall that prevents the connection
  • the port configured is not restricted
  • the password is encrypted in ASE. If it is encrypted, use the configuration for encrypted password.

You get the following error - Charset CESU-8 not recognized

Add the following to the JAVA setting either from the TrueSight console or from PATROL console KM command:

  • For PATROL console - On SYBASE, go to the KM command and click on Set JAVA Environment. Enter java argument -Dfile.encoding=CESU-8
  • For TrueSight console - Modify the existing policy by setting the JAVA Environment by entering java argument -Dfile.encoding=CESU-8

Need to close trigger events manually

Trigger events that you add to parameters need to be closed manually. You can also use standard events that close automatically. 

Create pconfig variables with value 1 at:

  • For all Sybase environments: /SYBASE/eventNotRequired
  • For a specific Sybase environment: /SYBASE/{envName}/eventNotRequired


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for Sybase 20.02