How to Perform Database Repairs
m (→What is the "Trainz Database"?) |
m (→Trainz Wiki) |
||
(42 intermediate revisions by one user not shown) | |||
Line 1: | Line 1: | ||
− | The information in this Wiki Page applies to | + | <table width=1000> |
+ | <tr valign="top"> | ||
+ | <td>The information in this Wiki Page applies to '''TANE''', '''TRS19''', '''Trainz Plus''' and '''TRS22'''.<br> | ||
+ | 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 will be required.</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | |||
+ | <table width=1000> | ||
+ | <tr valign="top"> | ||
+ | <td width=375> | ||
__TOC__ | __TOC__ | ||
− | + | </td> | |
+ | <td> | ||
+ | <table cellpadding=2 bgcolor="Aquamarine"> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:LinkWiki.PNG|link=]]</td> | ||
+ | <td>The section describing how to create a '''Clean Install''' (i.e. containing only '''Base''' and '''Built-in''' assets) has been moved to its own Wiki Page. This can be found at:- | ||
+ | :'''[[How_to_Create_a_Clean_Install|How to Create a Clean Install]]''' | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <br> | ||
+ | <table width=1000> <!-- BEGIN Nav Buttons Table --> | ||
+ | <tr valign="top"> | ||
+ | <td width=729><span id="stepWhat"></span> </td> | ||
+ | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75>[[file:NextDown.png|link=#stepWhy|alt=Next Down|Next Down]]</td> | ||
+ | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
='''What is the "Trainz Database"?'''= | ='''What is the "Trainz Database"?'''= | ||
− | <table | + | <table width=1000 bgcolor="lightcyan" cellpadding=2> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[ | + | <td width=10>[[image:BlueDot10x10.png|link=]]</td> |
<td>The '''Trainz Database''' contains all the installed assets</td> | <td>The '''Trainz Database''' contains all the installed assets</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | < | + | |
− | 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. | + | <table width=1000> |
+ | <tr valign="top"> | ||
+ | <td>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. | 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. | + | 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.</td> |
+ | </tr> | ||
+ | </table> | ||
<br> | <br> | ||
− | <table width= | + | <table width=1000> |
<tr> | <tr> | ||
− | <td> | + | <td>[[file:DBR_EDBR20.png|link=]]</td> |
− | [[file:DBR_EDBR20.png]] | + | |
− | </td> | + | |
</tr> | </tr> | ||
</table> | </table> | ||
<br> | <br> | ||
− | + | <table width=1000> <!-- BEGIN Nav Buttons Table --> | |
− | + | <tr valign="top"> | |
+ | <td width=729><span id="stepWhy"></span> </td> | ||
+ | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75>[[file:NextUp.png|link=#stepWhat|alt=Next Up|Next Up]]</td> | ||
+ | <td width=75>[[file:NextDown.png|link=#stepHow|alt=Next Down|Next Down]]</td> | ||
+ | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
+ | ='''Why Would a Database Repair (DBR) Be Needed?'''= | ||
− | = | + | <span style="font-weight: 700; font-size: 15px;">A Quote from N3V</span> |
− | <table | + | <table width=1000> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td> | + | <td> </td> |
− | <td> | + | <td>"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".</td> |
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | |||
− | <table | + | <table width=1000> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[file: | + | <td>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.</td> |
− | <td> | + | </tr> |
− | + | </table> | |
− | + | <br> | |
− | + | <table width=1000 bgcolor=#000000> | |
− | + | <tr valign="top"> | |
+ | <td> | ||
+ | <table bgcolor=#ffffe0> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:PencilTips.PNG|link=]]</td> | ||
+ | <td>A common, but not exclusive, cause of database problems and even '''CTD'''s (crashes to desktop) may be your antivirus program. Everytime '''Trainz''' accesses the database your AV program may perform a scan of the database.<br><br> | ||
+ | Adding '''TANE.exe''', '''TRS19.exe''' and '''TRS22.exe''' to your AV programs '''real time scan''' exclusion list can potentially resolve many of these issues by preventing the AV from accessing the database. | ||
</td> | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <br> | ||
+ | <table width=1000> <!-- BEGIN Nav Buttons Table --> | ||
+ | <tr valign="top"> | ||
+ | <td width=729><span id="stepHow"></span> </td> | ||
+ | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75>[[file:NextUp.png|link=#stepWhy|alt=Next Up|Next Up]]</td> | ||
+ | <td width=75>[[file:NextDown.png|link=#stepEDBR|alt=Next Down|Next Down]]</td> | ||
+ | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
+ | ='''How to Perform a Database Repair (a DBR)'''= | ||
− | <table | + | <table width=1000 bgcolor="lightcyan" cellpadding=2> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[ | + | <td width=10>[[image:BlueDot10x10.png|link=]]</td> |
− | <td> | + | <td>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.</td> |
</tr> | </tr> | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table | + | This is the simplest and (usually) the fastest option.<br> |
+ | |||
+ | <table bgcolor=#000000> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td | + | <td> |
− | + | <table bgcolor=#ffffb0> | |
− | + | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[file: | + | <td>[[file:NotePad.PNG|link=]]</td> |
− | <td><font size | + | <td><span style="font-size: 17px;">'''Notes:'''</span><br> |
− | <table | + | ---- |
+ | Perform a '''DBR''' if you have:- | ||
+ | <table> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[ | + | <td width=10>[[image:DotPoint.JPG|10px|link=]]</td> |
− | <td> | + | <td>'''unexpected problems''' with missing content</td> |
</tr> | </tr> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td | + | <td>[[image:DotPoint.JPG|10px|link=]]</td> |
− | + | <td>content '''errors with installed assets''' (particularly if those assets did not previously show any problems)</td> | |
− | + | ||
</tr> | </tr> | ||
− | + | <tr valign="top"> | |
− | + | <td colspan=2>A '''DBR''' updates your database, revalidates the content and can often clear up any corruption that has occurred.</td> | |
− | <tr> | + | |
− | <td colspan= | + | |
− | + | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | </td> | |
− | + | </tr> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | < | + | |
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[file: | + | <td colspan=2> |
− | <td> | + | <table bgcolor=#ffffe0> |
+ | <tr valign="top"> | ||
+ | <td>[[file:PencilTips.PNG|link=]]</td> | ||
+ | <td>If you have installed a new asset that '''Content Manager''' reports has having '''missing''' or '''unknown''' assets then a '''DBR''' is '''very unlikely''' to find those missing assets. | ||
+ | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</td> | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | </td> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</tr> | </tr> | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table | + | <table width=1000> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td colspan= | + | <td colspan=2><span style="font-weight: 700; font-size: 17px;">Steps:</span></td> |
− | + | ||
</tr> | </tr> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[ | + | <td width=25>[[image:DotPoint1.JPG|link=]]</td> |
− | <td><font size | + | <td><span style="font-size: 17px; font-weight: 700;">Open the Developer Menu</span> |
− | <table | + | <table> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td> | + | <td colspan=2>From either the '''Launcher''' (below left) or '''Content Manager''' (below right) open the '''Developer''' menu and select the '''Rebuild Database''' option</td> |
− | + | ||
</tr> | </tr> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td | + | <td>[[file:DBR_EDBR01.png|link=]]</td> |
− | + | <td>[[file:DBR_EDBR02.png|link=]]</td> | |
− | + | ||
− | + | ||
− | < | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</td> | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | + | <table width=1000> | |
− | + | ||
− | <table | + | |
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[file: | + | <td>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. |
− | <td> | + | <table> |
− | + | <tr valign="top"> | |
− | + | <td width=25>[[image:DotPoint1Blue.png|link=]]</td> | |
− | + | <td>'''Scanning for deleted asset files'''<br> | |
+ | [[file:DBR_EDBR03.png|link=]]</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint2Blue.png|link=]]</td> | ||
+ | <td>'''Scanning for added asset files'''<br> | ||
+ | [[file:DBR_EDBR04.png|link=]]</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint3Blue.png|link=]]</td> | ||
+ | <td>'''Importing built in assets'''<br> | ||
+ | [[file:DBR_EDBR06.png|link=]]</td> | ||
</tr> | </tr> | ||
− | |||
− | |||
− | |||
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[ | + | <td>[[image:DotPoint4Blue.png|link=]]</td> |
− | <td | + | <td>'''Rebuilding cached asset data'''<br> |
− | + | [[file:DBR_EDBR07.png|link=]]</td> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | </td> | |
− | < | + | </tr> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td> | + | <td>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.</td> |
− | + | ||
</tr> | </tr> | ||
</table> | </table> | ||
+ | <br> | ||
+ | <table width=1000> <!-- BEGIN Nav Buttons Table --> | ||
+ | <tr valign="top"> | ||
+ | <td width=729><span id="stepEDBR"></span> </td> | ||
+ | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75>[[file:NextUp.png|link=#stepHow|alt=Next Up|Next Up]]</td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
− | <table | + | ='''How to Perform an Extended Database Repair (an EDBR)'''= |
− | <tr> | + | |
− | <td | + | <table width=1000 bgcolor="lightcyan" cellpadding=2> |
− | + | <tr valign="top"> | |
+ | <td width=10>[[image:BlueDot10x10.png|link=]]</td> | ||
+ | <td>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</td> | ||
</tr> | </tr> | ||
+ | </table> | ||
+ | <br> | ||
+ | <table width=XXX bgcolor=#000000 cellpadding=2> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
<td> | <td> | ||
− | # | + | <table width=XXX-4 bgcolor=#ffffb0 cellpadding=2> |
− | + | <tr valign="top"> | |
+ | <td width=25>[[image:NotePad.PNG|link=]]</td> | ||
+ | <td><span style="font-size: 17px;">'''Notes:'''</span><br> | ||
+ | ---- | ||
</td> | </td> | ||
</tr> | </tr> | ||
− | </ | + | <tr valign="top"> |
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>An '''EDBR''' is a more complex, slower and potentially more troublesome repair process</td> | ||
</tr> | </tr> | ||
− | <tr> | + | <tr valign="top"> |
− | <td | + | <td>[[image:DotPoint.JPG|10px|link=]]</td> |
− | + | <td>An '''EDBR''' puts every single asset in the database through the same error and compliance checks that are run when a new asset is installed</td> | |
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>Perform an '''EDBR''' if you have '''serious problems''' with your database that a DBR does not fix</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | </td> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</tr> | </tr> | ||
+ | </table> | ||
+ | <br> | ||
+ | <table bgcolor=#ff0000> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | |||
− | |||
− | |||
− | |||
<td> | <td> | ||
− | # | + | <table bgcolor=#fcbcbc> |
− | + | <tr valign="top"> | |
− | + | <td>[[file:Stop.PNG|link=]]</td> | |
− | + | <td><span style="font-size: 15px; font-weight: 700;">CAUTION:</span><br> | |
− | + | It is not unusual for '''Content Manager''' to display a list of faulty assets '''after an EDBR''' that were not shown as faulty before the '''EDBR''' was run | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</td> | </td> | ||
− | |||
</tr> | </tr> | ||
− | </table | + | </table> |
− | + | </td> | |
− | + | ||
− | + | ||
− | + | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | <br> | |
− | <table | + | <table width=1000> |
− | <tr> | + | <tr valign="top"> |
− | <td colspan= | + | <td colspan=2><span style="font-weight: 700; font-size: 17px;">Steps:</span></td> |
− | + | ||
</tr> | </tr> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[ | + | <td width=25>[[image:DotPoint1.JPG|link=]]</td> |
− | <td><font size | + | <td><span style="font-size: 17px; font-weight: 700;">Open the Developer Menu</span></td> |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | </td> | + | |
</tr> | </tr> | ||
− | <tr> | + | <tr valign="top"> |
− | <td colspan= | + | <td colspan=2> |
− | ----</td> | + | <table> <!-- BEGIN Step 1 table --> |
+ | <tr valign="top"> | ||
+ | <td>[[file:DBR_EDBR01.png|link=]]</td> | ||
+ | <td>[[file:DBR_EDBR02.png|link=]]</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | <table> | |
− | <table | + | |
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[ | + | <td colspan=2>From either the '''Launcher''' (left) or '''Content Manager''' (right):-</td> |
− | <td> | + | </tr> |
− | + | <tr valign="top"> | |
− | + | <td width=25>[[image:DotPoint1Blue.png|link=]]</td> | |
− | + | <td>open the '''Developer''' menu</td> | |
− | + | </tr> | |
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint2Blue.png|link=]]</td> | ||
+ | <td>hold down the <span style="font-weight: 700; font-size: 15px; color: white; background-color: black;"> Ctrl </span> key</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint3Blue.png|link=]]</td> | ||
+ | <td>select the '''Rebuild Database''' option</td> | ||
+ | </tr> | ||
+ | </table> | ||
</td> | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
<br> | <br> | ||
− | + | A possible result of an EDBR.<br> | |
+ | <table width=1000> | ||
+ | <tr> | ||
+ | <td> | ||
+ | [[file:DBR_EDBR10.png|link=]] | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <br> | ||
+ | <table width=1000> <!-- BEGIN Nav Buttons Table --> | ||
+ | <tr valign="top"> | ||
+ | <td width=729><span id="bottom"></span> </td> | ||
+ | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75>[[file:NextUp.png|link=#stepEDBR|alt=Next Up|Next Up]]</td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75> </td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
---- | ---- | ||
---- | ---- | ||
− | |||
='''Trainz Wiki'''= | ='''Trainz Wiki'''= | ||
− | <table | + | <table width=1000> |
<tr valign="top"> | <tr valign="top"> | ||
− | |||
<td> | <td> | ||
− | < | + | <table width=500 cellpadding=2 bgcolor=#ffffff> |
+ | <tr valign="top"> | ||
+ | <td width=80>[[image:TrainzWiki.png|link=]]</td> | ||
+ | <td> | ||
+ | <span style="font-size: 17px;">'''More Tutorials and Guides to Using Trainz'''</span><br> | ||
*'''<span class="plainlinks">[http://online.ts2009.com/mediaWiki/index.php/HowTo How to Guides]</span>''' | *'''<span class="plainlinks">[http://online.ts2009.com/mediaWiki/index.php/HowTo How to Guides]</span>''' | ||
*'''[[Driver Commands List]]''' | *'''[[Driver Commands List]]''' | ||
Line 302: | Line 347: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | </td> | |
+ | <td> | ||
+ | <table width=500 cellpadding=4 bgcolor="aquamarine"> | ||
+ | <tr valign="top"> | ||
+ | <td width=50>[[image:LinkWiki.PNG|link=]]</td> | ||
+ | <td> | ||
+ | <span style="font-size: 17px;">'''Related Links'''</span><br> | ||
+ | *'''[[How to Create a Clean Install|How to Create a Clean Install and Alternative User Data Folders]]''' | ||
+ | *'''[[Using Content Manager to Update Assets|Using Content Manager to Update Assets]]''' | ||
+ | *'''[[Understand Content Manager Status Labels|Understand Content Manager Status Labels]]''' | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | ---- | ||
+ | This page was created by Trainz user '''<span class="plainlinks">[http://online.ts2009.com/mediaWiki/index.php/User:Pware pware]</span>''' in January 2019 and was last updated as shown below. | ||
+ | ---- | ||
[[Category:How-to guides]] | [[Category:How-to guides]] |
Latest revision as of 16:00, 20 November 2023
The information in this Wiki Page applies to TANE, TRS19, Trainz Plus and TRS22. 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 will be required. |
|
|
[edit] 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. |
[edit] Why Would a Database Repair (DBR) Be Needed?
A 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. |
|
[edit] 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: | |||||
Open the Developer Menu
|
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.
|
||||||||
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. |
[edit] 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: | |||||||||||
Open the Developer Menu | |||||||||||
|
A possible result of an EDBR.
|
[edit] Trainz Wiki
|
|
This page was created by Trainz user pware in January 2019 and was last updated as shown below.