Recreating and Replacing Damaged Proprietary Production Databases

 

Before You Begin

If the production databases appear to be present but you see “Database 'production' could not be opened.” in the log files, the misc file in the production database or the config.ds file are damaged. You can replace the misc file, recreate the production database, or recreate the entire structure to resolve this issue.

Steps

To replace the misc file (if it is the only damaged file):

1. Create a new temporary database using the following command:
   
   manager\bin\tqdbu -i -d temp
   
   
2. Copy the misc file in the \data\temp directory and replace the misc file in the \data\production directory.
3. Clean up the temp database using the following command:
   
   manager\bin\tqdbu -r -d temp
   
   
4. Test the new database. 

Note: Running the tqdbu -l command can cause the same problem if the database is not readable.

To recreate the production database:

Note: This option might result is lost data.

1. Create a new temporary database using the following command:
   
   manager\bin\tqdbu -i -d temp
   
   
2. Copy the contents of the \data\temp folder and replace the contents in the \data\production folder.
3. Clean up the temp database using the following command:
   
   manager\bin\tqdbu -r -d temp
   
   
4. Test the new database.

Note: Running the tqdbu -l command can cause the same problem if the database is not readable.

To recreate the entire structure:

1. Shut down the TeamQuest Manager service.
2. Check that no processes are running by looking for tq processes.
3. Delete the config.ds file from the \data\cf\manager directory.
4. Delete the \data\production folder.
5. Run the following command:
   
   manager\bin\tqmgr -init
   
   Services should now be running against a production default database.