Articles in this section

See more
Self help

Why is my History Chart not working?

Avatar
Raymond Angelo Gonzales
  • Updated
Follow
 

Reason 1 - My Active Console is not connected to the database.

The Active Console connects directly to the database. It gets its database connection details from two areas/settings:

1. The Gateway's Database logging section. Specific to Oracle, the sid, serverName and port settings must be filled up.

mceclip0.png

For other database servers, the serverName and port settings are enough.

2. The Active Console's Database settings as seen below:

Check if the database definitions are correct and if the Active Console's machine (desktop PC or laptop) has sufficient network access to the database and database server.

 

Reason 2 - The cell where I am executing the History Chart on has duplicates.
  1. Identify the cell where the history chart is executed. The cell will tell us what varname to look for.
  2. Query the Geneos database for duplicate varnames:
    • SELECT * FROM var_ref_table; - This will output all the varnames. Check if the varname in question has a duplicate.
    • SELECT * FROM version_table; - This will output the Geneos database schema version.
  3. After that, follow the steps in the guide How do I fix varname duplicates in Database Logging? to fix the issue. 

 

Reason 3 - The cell's (database logging item) value column datatype is not of type REAL or FLOAT

Attached is a sample table definition that shows a value column with a REAL or FLOAT datatype: https://itrs.zendesk.com/hc/article_attachments/115003569153/query_output.txt

The value column's datatype needs to be of type REAL or FLOAT.

 

Reason 4 - The cell's value column datatype is correct but my tables setting definition is not of type DOUBLE.
  1. Access the Gateway's Database Logging section.
  2. Go to the Database Item (databaseLogging > items) in question.
  3. Get the Table where the Database Item is being logged.
  4. Go to the Table (databaseLogging > tables)
  5. Check if the Type (databaseLogging > tables > table > type) is set to Double. If not, set it to Double. Once done, re-execute the History Chart.

 

Reason 5 - Missing database drivers/client libraries

The Console connects to all supported databases using JDBC, with the exception of MySQL this means the console does not need any additional librares or drivers other than those shipped with the console by default. In the case of MYSQL the user needs to download the MYSQL driver from here

http://dev.mysql.com/downloads/connector/j/

Selecting the 'Platform Independent' option (NOT Windows), and extract the JAR from the package.

The jar then needs to be added to the console install under here

\jars\JDBC

You will need to restart the console after doing this

 

Reason 6 - The language of the database server and the Active Console's JVM are different.

The console assumes that numbers will be returned using the decimal delimiter, where they are comma separated (which can be the case in a database set for German or French for example), then the conversion of the returned rows can fail.

Check the exception log, e.g.

Exception no.6 
Fri Apr 12 11:56:55 CEST 2013 java.lang.NumberFormatException: For input string: "26,4E0" 
sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)  

 

To resolve this issue:

  1. Edit the ActiveConsole.gc file, and ensure that the following is in place:

     
    -jvmargs 
     
    [....] 
     
    Duser.language=en

  2. After you have edited the ActiveConsole.gci file, restart the Console.

This should make the query from the database return dot delimited decimal values.

   

 

 

Related articles

Comments

0 comments

Please sign in to leave a comment.