cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
pclark
AppDynamics Team (Retired)

Question

My application uses a Greenplum database. The calls to the database are JDBC, but we are not discovering the database out of the box. How can I fix this?

 

Answer

Refer to Using Node Properties to Detect JDBC Backends for more details on using these node properties. The values to use for Greenplum are detailed below.

 

Greenplum Simple using greenplum.jar

Use the following JDBC node properties and values:

 

jdbc-connections: value="com.ddtek.jdbc.greenplumbase.BaseConnection,com.ddtek.jdbcspygreenplum.SpyConnection,com.ddtek.jdbcx.greenplumbase.ddd"
jdbc-prepared-statements: value="com.ddtek.jdbc.greenplumbase.dddw,com.ddtek.jdbcspygreenplum.SpyPreparedStatement,com.ddtek.jdbcx.greenplumbase.ddn"
jdbc-statements: value="com.ddtek.jdbc.greenplumbase.dde_,com.ddtek.jdbc.greenplumbase.dde,com.ddtek.jdbcspygreenplum.SpyStatement,com.ddtek.jdbcx.greenplumbase.ddu"
jdbc-callable-statements: value="com.ddtek.jdbc.greenplumbase.ddk,com.ddtek.jdbc.greenplumbase.ddm,com.ddtek.jdbcspygreenplum.SpyCallableStatement,com.ddtek.jdbcx.greenplumbase.dda"

 

Greenplum Deluxe includes Pivotal Greenplum drivers

Use the following JDBC node properties and values:

 

jdbc-connections: value="com.ddtek.jdbc.greenplumbase.BaseConnection,com.ddtek.jdbcspygreenplum.SpyConnection,com.ddtek.jdbcx.greenplumbase.ddd,com.pivotal.jdbc.greenplumbase.BaseConnection,com.pivotal.jdbcspygreenplum.SpyConnection,com.pivotal.jdbcx.greenplumbase.ddf"

jdbc-prepared-statements: value="com.ddtek.jdbc.greenplumbase.dddw,com.ddtek.jdbcspygreenplum.SpyPreparedStatement,com.ddtek.jdbcx.greenplumbase.ddn,com.pivotal.jdbc.greenplumbase.dddk,com.pivotal.jdbcspygreenplum.SpyPreparedStatement,com.pivotal.jdbcx.greenplumbase.ddp"

jdbc-statements:
value="com.ddtek.jdbc.greenplumbase.dde_,com.ddtek.jdbc.greenplumbase.dde,com.ddtek.jdbcspygreenplum.SpyStatement,com.ddtek.jdbcx.greenplumbase.ddu,com.pivotal.jdbc.greenplumbase.ddd_,com.pivotal.jdbcspygreenplum.SpyStatement,com.pivotal.jdbcx.greenplumbase.ddw" jdbc-callable-statements: value="com.ddtek.jdbc.greenplumbase.ddk,com.ddtek.jdbc.greenplumbase.ddm,com.ddtek.jdbcspygreenplum.SpyCallableStatement,com.ddtek.jdbcx.greenplumbase.dda,com.pivotal.jdbc.greenplumbase.dde1,com.pivotal.jdbc.greenplumbase.dde3,com.pivotal.jdbcspygreenplum.SpyCallableStatement,com.pivotal.jdbcx.greenplumbase.ddb,cs.jdbc.driver"

 

Comments

Hi all,

any example for FISglobe drive to collect GT.M

on my controller auto detect this

protocol=jdbc:fisglobal|database=10.53.132.44:18032:SCA$IBS|locale=US:ENGLISH|timeOut=45|transType=M

but cannot show the SQL query like Oracle DB

Version history
Last update:
‎11-19-2018 07:08 AM
Updated by:
On-Demand Webinar
Discover new Splunk integrations and AI innovations for Cisco AppDynamics.


Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here
Contributors