Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
sms1_-_rebuild_database [2019/01/27 11:31] 127.0.0.1 external edit |
sms1_-_rebuild_database [2019/02/28 14:36] (current) admin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | =Error Message= | + | =====Error Message===== |
| - | + | ||
| Various database, key violation, index, or blob messages. | Various database, key violation, index, or blob messages. | ||
| + | =====Explanation of Process===== | ||
| + | The Database Rebuild utility is used to repair a database table. It does this by doing the following: | ||
| - | =Explanation of Process= | ||
| - | |||
| - | |||
| - | |||
| - | The Database Rebuild utility is used to repair a database table. | ||
| * Backs up the entire database (on DBRebuilder Ver 8.50.2005.09+). | * Backs up the entire database (on DBRebuilder Ver 8.50.2005.09+). | ||
| * Reads the existing table structure | * Reads the existing table structure | ||
| - | * Creates a new table with the same structure (fields, indexes, etc.)It was recently observed that the DBRebuild utility reverses the order of indexes in the new table. | + | * Creates a new table with the same structure (fields, indexes, etc.)It was recently observed that the DBRebuild utility reverses the order of indexes in the new table. In theory, this should not matter. In practice, it seems to be linked to at least one of the bugs in Cyrstal Reports 8.5 with Paradox tables. |
| * Opens the table without using any indexes, etc. | * Opens the table without using any indexes, etc. | ||
| * Copies all of the data to the new tables | * Copies all of the data to the new tables | ||
| - | * Deletes the old table. | + | * Deletes the old table. |
| * Renames/ | * Renames/ | ||
| - | |||
| - | |||
| This process requires exclusive access to the files, so the SMS and SSLIP and any other programs using the data must be closed. | This process requires exclusive access to the files, so the SMS and SSLIP and any other programs using the data must be closed. | ||
| - | |||
| - | |||
| Note: | Note: | ||
| - | * __All Users **must** be out of the system for this process.__ | ||
| + | * __All Users **must** | ||
| + | =====Severity===== | ||
| + | High. During the rebuild process, if the old table is damaged beyond the ability to read parts, the data may be truncated or not copied into the new table. Also, if the structure is damaged, indexes are frequently lost and not found in the resulting files. | ||
| - | =Severity= | + | =====Tier 1 Actions===== |
| - | |||
| - | |||
| - | High. During the rebuild process, if the old table is damaged beyond the ability to read parts, the data may be truncated or not copied into the new table. | ||
| - | |||
| - | |||
| - | |||
| - | =Tier 1 Actions= | ||
| - Close all copies of SMS and the SSLIP | - Close all copies of SMS and the SSLIP | ||
| - | - Run **Computer Management** (Start | Run ... CompMgmt.msc) to confirm that no files in the ..\Cyrious$\SMS hierarchy are open. If they are, close them. Refresh the screen after closing files to confirm no additional files appear. | + | - Run **Computer Management** |
| - Confirm you have the correct Data folder by looking at the modified date of the files in the data folder. | - Confirm you have the correct Data folder by looking at the modified date of the files in the data folder. | ||
| - Make a backup of the Data folder before running the DBRebuild if older than DBRebuilder Ver 8.50.2005.09 | - Make a backup of the Data folder before running the DBRebuild if older than DBRebuilder Ver 8.50.2005.09 | ||
| - | - Run the **DBRebuild** utility in ..\\Cyrious$\SMS\Utilities\DBRebuild. | + | - Run the **DBRebuild** |
| - If DBRebuild gives you an error running, see Troubleshooting DBRebuild below. | - If DBRebuild gives you an error running, see Troubleshooting DBRebuild below. | ||
| - | - Click on the **Verify All Tables** button. | + | - Click on the **Verify All Tables** |
| - | * Note any tables with errors. | + | * Note any tables with errors. This will need to be researched afterwards. |
| - | * If all tables say "Could Not Verify", | + | * If all tables say "Could Not Verify", |
| - If no tables could be verified, reboot the computer and start DBRebuild again. | - If no tables could be verified, reboot the computer and start DBRebuild again. | ||
| - | - If any tables are found with errors, check those tables and click **Rebuilt Checked**. | + | - If any tables are found with errors, check those tables and click **Rebuilt Checked**. |
| - If any tables could not be rebuilt, __elevate to Tier 2 support__. | - If any tables could not be rebuilt, __elevate to Tier 2 support__. | ||
| - Close DBRebuild | - Close DBRebuild | ||
| - Based on the issues found, additional verification steps should be undertaken such as: | - Based on the issues found, additional verification steps should be undertaken such as: | ||
| - | | + | |
| - | * Checking the validity of data on any corrupted tables | + | * Checking the validity of data on any corrupted tables |
| - | * Checking for missing data on any corrupted tables. | + | * Checking for missing data on any corrupted tables. |
| + | =====TroubleShooting DBRebuild===== | ||
| - | |||
| - | =TroubleShooting DBRebuild= | ||
| - Ensure SMS.exe or SSLIP.exe is not running in the Processes tab in the Task Manager | - Ensure SMS.exe or SSLIP.exe is not running in the Processes tab in the Task Manager | ||
| - Remapped to the local drive rather than the universal path | - Remapped to the local drive rather than the universal path | ||
| - Reboot server | - Reboot server | ||
| + | =====Task Information===== | ||
| - | |||
| - | =Task Information= | ||
| * Last Updated: 2/16/2015 | * Last Updated: 2/16/2015 | ||
| * Created By: Michael Nolan | * Created By: Michael Nolan | ||
| - | * Verified By: | + | * Verified By: |
| * Applies to All Versions | * Applies to All Versions | ||
| - | |||
| - | |||