Tech Tips: What are the BEST PRACTICES for DevTest Database Troubleshooting

Document created by MarcyNunns Employee on Feb 27, 2017Last modified by MarcyNunns Employee on Nov 21, 2017
Version 5Show Document
  • View in full screen mode

Introduction:  

DevTest Database troubleshooting.

 

Environment:   

All supported versions of DevTest.

All supported Windows, Linux and UNIX platforms.

 

Instructions: 

 

Verify you are using an Enterprise Database like DB2, Oracle, SQL Server or MySQL.  Derby is strictly for demo purposes only.

 

Verify databases are not hosted on a virtual machine and are present within the same data center as the DevTest components.  The Workstation, Registry, Coordinator, Simulators and any Virtual Service environments require high-performance database access. Performance data is recorded directly to the database by these components. The port required to connect to the database must be bi-directional.   

 

Verify character set you are using for your external database, DevTest requires UTF-8 which is a 16-bit implementation.

 

Verify credentials being used to start the Enterprise Dashboard and Registry; not only must they be valid, but also have authority to Create, Read, Update and Delete tables as well as Alter on startup of both components.  Basically you will need DBA Authority the first time the Enterprise Dashboard or Registry is brought up if having DevTest create all the tables.

 

Verify connection string.  If you are sure your connection string is valid, use another JDBC database tool to connect to your database outside of DevTest. All DevTest components must be able to connect to the external database, so verify you can telnet to port the external database is running on.

 

Verify you are using the supported drivers.  Other drivers like jtds are not supported even though they may work.  The drivers specified to use in the local.properties and site.properties files is what you should be using. Tech Tips: JDBC Drivers Delivered with DevTest  

 

Verify Schema.  Enterprise Dashboard and Registry must each have their own schema.  Follow the documentation as to supported databases and the recommended size for each.  Do not point multiple Registries at the same database schema.

 

Do regular Database Maintenance.  Make sure your database has regular maintenance which includes checking for signs of corruption in the database, looking for problem areas, verifying it has all the required indexes (compare to DDL delivered with release), removing duplicate records, making sure database is not getting full and checking for any abnormalities in the database that might signal a problem.  Run statistics regularly.

 

Performance. To ensure correct performance when using an external database, the database server and DevTest server should have high network bandwidth and low latency.  When running in a distributed configuration, DevTest depends on server components having a high-bandwidth, low-latency connection to a well-maintained, enterprise-class database.

 

 

Additional Information: 

For further detail, add these properties to logging.properties file, they will show a more detail on the errors being incurred.  Once your issue has been resolved, remove these properties.

 

log4j.logger.com.mchange.v2.c3p0=DEBUG

log4j.logger.com.mchange.v2.resourcepool=DEBUG

 

If there is still an issue after verifying all of the above, then please open a support case from CA Support Online.

 

 

 

1 person found this helpful

Attachments

    Outcomes