Återställa efter en rådataexport
If your database somehow becomes damaged while you are using it, you will be prompted to create a Raw Data export. You should do so, using the
Raw Data Export function in the System module or, if you are working on the server, by launching the server application with the --rawdata parameter. The Raw Data option exports data in byte order, while the Database Text Backup option exports data in record order, on a register-by-register basis. When a database is damaged, the Raw Data option may create an export file where the Database Text Backup option fails. However, because the database is damaged, restoration from a Raw Data export is not guaranteed. Therefore, if the Raw Data option successfully creates an export file, you should then attempt to create a Database Text Backup, to make a successful restoration more likely.
If you need to restore a database from a Raw Data file, use the GUI application to follow these steps:
- Make sure the folder or directory containing your HansaWorld Enterprise application does not contain a "HANSA.HDB" file and launch the application.
- When the 'Welcome to HansaWorld' window appears, click the [Master Database] or [Single User Database] button as appropriate. Follow the instructions on the Creating a New Database - Server or the Creating a New Database - Single-user pages respectively.
- Referring to the 'Single-user' section on the Changing and Adding Companies page, create all the Companies as they were in the damaged database (in particular, the Codes must be the same as they were in the damaged database).
- Create all Fiscal Years exactly as they were in the damaged database (in every Company).
- In every Company, configure the Company Date and Numeric Format setting in the System module as follows:
- Date Order
- Month, Day, Year
- All three check boxes
- ticked
- Date separator
- / or -
- Decimal Separator
- . (a single full stop, not a comma)
- Thousand separator
- space (one single space)
- Ensure you are in the System module and use the Ctrl-Shift-I/⌘-Shift-I keyboard shortcut to open the 'Imports' window. Choose one of the options depending on where the Raw Data file is located and import it.
If the Raw Data file is large, you may prefer to use the command line (Linux or Mac OS X) or service (Windows) application for this step, as the speed benefit will be significant.
- Even if the Raw Data file is imported successfully, the database will not be useable because no indexes will be created. Therefore, you must immediately create a Database Text Backup and import that file to a new database. This will ensure the data is properly indexed. Again, you may prefer to use the command line (Linux or Mac OS X) or service (Windows) application to import the file.
- As mentioned in the introduction to this section, restoration from a Raw Data export is not guaranteed to be successful. In many cases, the damage in the original database will be confined to the indexes. This damage will usually be fixed by the process described above. However, it may be that the damage has caused records to be lost. To ascertain whether anything has been lost, you should print the reports that you commonly use and compare them with the most reports produced from the damaged database. Such reports will probably include the Trial Balance, Profit & Loss and Balance Sheet from the Nominal Ledger, the Sales Ledger report and the Open Invoice and Periodic Customer Statements from the Sales Ledger, the Purchase Ledger report and the Open Invoice and Periodic Supplier Statements from the Purchase Ledger, the Stock List and Item History from the Stock module, journals for commonly used registers such as the Invoice Journal and the Transaction Journal, and the main reports from any other important modules. If you know the last records that were entered to the original database before it was damaged, you can see if these records are also in the new database. You may also find it useful regularly to produce the Record Count report in the Technics module, which lists the number of records in each register. Comparing this report produced from the new database with the last one produced from the old database before it was damaged may give an idea of the number of records lost.
---
In this chapter:
