DevTest Database troubleshooting.
All supported versions of DevTest.
All supported Windows, Linux and UNIX platforms.
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 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 if a database password has expired and needs to be reset.
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.
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.
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.
If there is still an issue after verifying all of the above, then please open a support case from CA Support Online.