Tech Tip: Database Safeguards when Upgrading to DevTest 10.2

Document created by mazda03 Employee on Dec 20, 2017
Version 1Show Document
  • View in full screen mode

A common issue that occurs when upgrading DevTest is related to database permissions, which is difficult to resolve for both customers and technical support.

 

In previous versions of DevTest, user credentials are not checked until part of the upgrade has been completed. This can cause inconsistent database structures due to the specified database user not having write permissions.

 

In DevTest 10.2, a permissions check is performed at the beginning of the database upgrade. This checks the appropriate permission level prior to making modifications to the database. If the specified database user does not have write permissions, and error is generated in the event log and changes are rolled back to a previous good state. This applied to both the Registry and Enterprise Dashboard databases.

 

Example 1a: Here’s an example error in enterprisedashboard.log when upgrading the Enterprise Dashboard without write permissions:

 

Example 1b: Here’s an example success in enterprisedashboard.log when upgrading the Enterprise Dashboard with write permissions:

 

Example 2a: Here’s an example error in registry.log when upgrading the Registry without write permissions:

 

Example 2b: Here’s an example success in registry.log when upgrading the Registry with write permissions:

 

Refer to the DevTest 10.2 Release Notes and DevTest 10.2 product documentation for additional information.

Attachments

    Outcomes