This chapter describes the RAIMA to SQLite (+NGA) conversion. If you already use NGA archiving, see the chapter Conversion Settings.
Notes before Migrating a RAIMA Database
This migration results in losing all instances of active alerts. Active alert instances are currently not exported into an ASCII file. Alerts might be re-triggered with last values
when importing the ASCII file.
NGA does not cover all Value Archive features (RAIMA) yet.
Make a backup of the project before the migration.
If you are using a time-limited WinCC OA license (e.g. an evaluation license) during the migration, please ensure that the expiry date of the license is
sufficiently far in the future. This is particularly important for very large databases to be migrated. If the license expires during the migration period, this can lead to data
loss.
Automatic Migration of a RAIMA database to SQLite
Open the Project Administration 3.20 and double-click for list of older projects:
Figure 1. Doubleclick for list of older projects:Figure 2. The older projects are shown. Select the project you want to upgrade:
and click the Upgrade project button. The Upgrade project panel is opened. Check the Upgrade to the SQLite project
(+NGA) check box and check the check box Save project before upgrading and click OK.
Note: Create a backup of your project before you start the upgrade by checking the check box Save project before upgrading . It creates
a back up of your whole project.
Figure 3. Upgrade Project
A warning is shown that you must have a valid 3.20 license when converting the project. Otherwise the conversion could lead to a corrupted project:
Figure 4. A warning about a valid license
Click on Continue to convert the project. The NGA migration panel is opened. Configure the Value Archive → NGA Group assignment and
save it- see chapter Migration Panel - NGA Migration.
Click on the Migrate button to start the Migration. An information about the historical data is shown (see figure below). Click on OK
to start the Migration. The button converts the project from ValArch to NGA archiving.
Note: NOTE the historical data is not imported here. You must import the historical data separately after the migration from RAIMA to SQLite via the NextGen Archiver (NGA) Importer. This is only required if you did not use NGA archiving before and converted your project now.
Figure 5. Start the Project Migration
A warning about the backup settings that are not automatically converted is shown:
Figure 6. Warning about Backup Settings
Adapt the backup settings via the Storage settings.
The project is converted and an upgrade message is shown:
Figure 7. Project has been upgraded message
The converted and migrated project is shown in the 3.20 Project Administration panel. You can start the project:
Figure 8. Converted and Migrated Project
