Because of some significant structural changes to the 4.0 data model, the upgrade from 3.4 to 4.0 will be slightly more involved than past upgrades. Much of this process can be automated, however it is important that an expert on the site being upgraded becomes familiar with the details of the upgrade process.
The process involves the following major steps:
- Load the 4.0 data model into a new schema.
- Use the tools provided in resequence.sql on the old schema to guarantee that all integer primary keys occupy non overlapping ranges.
- Use 'sqlplus -S service_name/service_password < user-group-types.sql' to generate a parties data model from the 3.4 user group metadata. This should probably be checked to make sure there are no naming conflicts, etc.
- Use core-migrate.sql to migrate data from the old schema to the new schema.
- For each module or package in use, use package-name-migrate.sql to move data from the old schema to the new schema.