How to Perform Database Repairs
m (→How to Create a "Clean Database") |
m |
||
Line 1: | Line 1: | ||
The information in this Wiki Page applies to '''TANE''', '''TRS19''' and '''Trainz Plus'''.<br> | The information in this Wiki Page applies to '''TANE''', '''TRS19''' and '''Trainz Plus'''.<br> | ||
− | <table cellpadding= | + | <table cellpadding=4> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:TextBtn.png|link=|alt=Text]] </td> | <td>[[file:TextBtn.png|link=|alt=Text]] </td> | ||
Line 23: | Line 23: | ||
='''What is the "Trainz Database"?'''= | ='''What is the "Trainz Database"?'''= | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 64: | Line 64: | ||
When '''Trainz''' is operating there is a great deal of database activity going on with records being opened and closed, and data being read and written. Corruption of the data is always possible, particularly if the power supply is interrupted or the program is suddenly terminated (a "crash") while records are open or being written. For this reason, '''Content Manager''' comes equipped with automatic and manual database repair tools. | When '''Trainz''' is operating there is a great deal of database activity going on with records being opened and closed, and data being read and written. Corruption of the data is always possible, particularly if the power supply is interrupted or the program is suddenly terminated (a "crash") while records are open or being written. For this reason, '''Content Manager''' comes equipped with automatic and manual database repair tools. | ||
<br> | <br> | ||
− | <table bgcolor= | + | <table bgcolor=#000000 width=900> |
<tr valign="top"> | <tr valign="top"> | ||
<td> | <td> | ||
Line 90: | Line 90: | ||
='''How to Perform a Database Repair (a DBR)'''= | ='''How to Perform a Database Repair (a DBR)'''= | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 99: | Line 99: | ||
This is the simplest and (usually) the fastest option.<br> | This is the simplest and (usually) the fastest option.<br> | ||
− | <table bgcolor= | + | <table bgcolor=#000000 width=900> |
<tr valign="top"> | <tr valign="top"> | ||
<td> | <td> | ||
Line 123: | Line 123: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> |
<tr valign="top"> | <tr valign="top"> | ||
<td colspan="2"> | <td colspan="2"> | ||
Line 131: | Line 131: | ||
<td>[[file:Steps.PNG|link=]]</td> | <td>[[file:Steps.PNG|link=]]</td> | ||
<td><span style="font-size: 17px;">'''Steps:'''</span><br> | <td><span style="font-size: 17px;">'''Steps:'''</span><br> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DBR_EDBR01.png|link=]]</td> | <td>[[file:DBR_EDBR01.png|link=]]</td> | ||
Line 171: | Line 171: | ||
='''How to Perform an Extended Database Repair (an EDBR)'''= | ='''How to Perform an Extended Database Repair (an EDBR)'''= | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 179: | Line 179: | ||
<br> | <br> | ||
− | <table bgcolor= | + | <table bgcolor=#000000 width=800> |
<tr valign="top"> | <tr valign="top"> | ||
<td> | <td> | ||
Line 212: | Line 212: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> |
<tr valign="top"> | <tr valign="top"> | ||
<td colspan="2"> | <td colspan="2"> | ||
Line 220: | Line 220: | ||
<td>[[file:Steps.PNG|link=]]</td> | <td>[[file:Steps.PNG|link=]]</td> | ||
<td><span style="font-size: 17px;">'''Steps:'''</span><br> | <td><span style="font-size: 17px;">'''Steps:'''</span><br> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DBR_EDBR01.png|link=]]</td> | <td>[[file:DBR_EDBR01.png|link=]]</td> | ||
Line 259: | Line 259: | ||
='''How to Create a "Clean Database"'''= | ='''How to Create a "Clean Database"'''= | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#c1e7e7> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
Line 269: | Line 269: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table bgcolor= | + | <table bgcolor=#000000 width=900> |
<tr valign="top"> | <tr valign="top"> | ||
<td> | <td> | ||
Line 305: | Line 305: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> <!-- BEGIN Step table --> |
<tr> | <tr> | ||
<td colspan="2"> | <td colspan="2"> | ||
Line 383: | Line 383: | ||
</table> <!-- END Steps Table --> | </table> <!-- END Steps Table --> | ||
− | <table bgcolor= | + | <table bgcolor=#000000 width=600> |
<tr valign="top"> | <tr valign="top"> | ||
<td> | <td> | ||
Line 414: | Line 414: | ||
='''Trainz Wiki'''= | ='''Trainz Wiki'''= | ||
− | <table cellpadding= | + | <table cellpadding=4 bgcolor=#ffffff> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:TrainzWiki.png|link=]]</td> | <td>[[file:TrainzWiki.png|link=]]</td> |
Revision as of 07:42, 9 March 2022
The information in this Wiki Page applies to TANE, TRS19 and Trainz Plus.
This page is also available in text only format suitable for copying and pasting at How to Perform Database Repairs TEXT |
This guide will take you through the process of performing manual database repairs and clean database installs. Trainz will automatically perform database repairs when it detects corruption in the Trainz database but sometimes a manual repair or even a manual clean install of the database is required.
Contents |
What is the "Trainz Database"?
The Trainz Database contains all the installed assets |
In the earliest Trainz versions all the assets that came installed with Trainz, or that you installed from the DLS or downloaded as .cdp files, were stored as separate folders on your designated data drive. This made it easy to access the assets for editing and other operations. However the penalty was that each time you started Trainz it had to scan the assets to check their integrity and the more assets you had the longer the startup took. This led to a great many complaints from users.
Today, all installed Trainz assets are added as records in an asset database which has significantly sped up the startup process and has reduced the possibility of accidental data corruption by users. The penalty is that users can no longer access the installed assets by using Windows Explorer. Access to the assets in the database for editing and examination is through the Content Manager program.
Because it is a database manager, Content Manager also provides users with many more search, display and management options than were ever previously possible. Each entry in the display shown below is a single record in the Trainz database. Each entry can be easily opened for editing, it can be deleted, copied (cloned) and updated. New assets can be manually created or installed from other sources.
|
Why Would a Database Repair (DBR) Be Needed?
Quote from N3V
"In terms of DB repairs, it should only be necessary if the program is updated or crashes. My understanding of the additional repairs are for things that are done outside the program function [i.e. outside of Content Manager and Surveyor] (like manually adding content into the local data folder) so in that case the db repair 'discovers' the new content". |
When Trainz is operating there is a great deal of database activity going on with records being opened and closed, and data being read and written. Corruption of the data is always possible, particularly if the power supply is interrupted or the program is suddenly terminated (a "crash") while records are open or being written. For this reason, Content Manager comes equipped with automatic and manual database repair tools.
|
How to Perform a Database Repair (a DBR)
A DBR performs a "surface scan" of the database detecting missing content and content errors. It will update your database and can clean up some corrupted data. |
This is the simplest and (usually) the fastest option.
|
|
|||||
Steps:
|
|||||
|
The process will proceed automatically and unaided through a number of steps, only some of which are shown below. The time required for each step will vary enormously (some will take much longer than others) and the total time involved will depend on the number of assets installed, the speed of your system and other factors.
1. Scanning for deleted asset files
2. Scanning for added asset files
3. Importing built in assets
4. Rebuilding cached asset data
The Rebuilding Trainz Asset Database window will disappear if the DBR process has been successfully completed without finding any errors. If errors have been found then the window will remain on the screen to report on the number of errors and warnings.
How to Perform an Extended Database Repair (an EDBR)
An EDBR performs a "deep scan" of the database and checks that the data in every asset conforms to the rules for that type of asset |
|
|
|
|||||
Steps:
|
|||||
|
A possible result of an EDBR.
|
How to Create a "Clean Database"
Creating a Clean Database:-
|
|
|
|
|||||
Steps |
Create a Container:
|
||||
In Trainz Launcher:
|
|||||
Restart Trainz and Reconfigure Settings:
|
|
Trainz Wiki
More Tutorials and Guides to Using Trainz |
This page was created by Trainz user pware in January 2019 and was last updated as shown below.