Setting up an Oracle-Only Backing Store : Updating an Existing Oracle Database Schema

Updating an Existing Oracle Database Schema
If you change the project ontology, that is, if you create, alter or delete a concept or an event, you must update the backing store schema so it matches the updated ontology. You must do this before you deploy the updated project.
Not all changes can be automatically migrated. Manual migration is required for such changes.
What the Schema Migration Utility Can and Can’t Handle Automatically
The migration utility handles the following:
The utility can handle only certain changes to existing entities and attributes, depending on the datatype and on Oracle functionality. The utility does not handle changes to the data type of an existing attribute, for example, changing a String attribute to a number attribute.
If the utility encounters any change in the schema that cannot be migrated automatically, then the migration script is not generated. In this case, migrate the data and the schema manually. Contact TIBCO support for assistance about handling of specific changes.
To Update an Existing Backing Store Database Schema
Before you begin:
1.
2.
Save existing copies of yourname.sql and yourname.aliases so you can compare them with the files you will generate for the changed project.
3.
Open the be-oradeploy.tra file for editing and set the following properties:
be.oracle.schemamigration.url=DbURL
be.oracle.schemamigration.user=username
be.oracle.schemamigration.pswd=password
Where the username and password are those you set up in Task D, Run the Initialize Database Script to Create the Oracle User.
The properties enable the program to compare the schema of the existing database with the schema of the project EAR file, to generate the schema alteration script.
4.
Run the be-oradeploy.exe utility as explained inOracle-Only Backing Store Database Configuration Tasks, Task B, Generate the SQL Scripts, using the updated EAR file.
5.
If any of the new or changed definitions result in entries in the yourname.aliases file, follow instructions in Task C, Shorten Long Names Using the Aliases File. You must use the same aliases again for entity types (definitions) that used aliases before. Remember to generate the scripts again, as instructed in Task C.
6.
Run the newly-generated script yourname_alter.sql script.
Your database tables are now configured for use.