Migrating from Earlier Versions : Upgrading the Legacy Backing Store from Version 3.0.0 or Earlier

Upgrading the Legacy Backing Store from Version 3.0.0 or Earlier
The Oracle-only backing store was deprecated in the 4.0 release  It is recommended that you create a JDBC backing store and migrate data from the legacy backing store to the JDBC backing store. See Migrate the Backing Store Implementation and Backing Store Data for guidelines.
Upgrade your legacy backing store only if you one of the following is true:
Your Oracle-only backing store was set up using an earlier version than 3.0.0. In this case you must upgrade the schema before you can migrate the data to a new JDBC backing store schema.
Updating Legacy Backing Store for Schema Change in 3.0.1
New BusinessEvents metadata tables were added to the backing store schema in 3.0.1. If you use a backing store in version 3.0.0 or earlier, you must run the create_tables.sql script provided in the current release. It adds the new tables to the schema. Running this script does not affect any existing tables (therefore there is no need to run be-oradeploy.exe). However it’s always a good idea to back up your data before performing any schema changes.
To Update an Oracle-Only Backing Store Schema to the 3.0.1 Schema
1.
2.
Login to the Oracle server as be_user, password be_user (or whatever username and password you are using, as set in the initialize_database.sql script).
3.
Navigate to the location of the scripts (by default in BE_HOME/bin) and open an SQLPlus prompt. Identify yourself as the user you logged in as.
4.
@create_tables.sql
Your database tables are now configured for use.