You can implement an Oracle-only backing store for use with any Cache object management option. At system startup, data is loaded into the cache from the backing store. During regular operation, the cache persists the data that is written to it in the backing store. This happens at the end of each RTC.
Backing store functionality has been tested with Oracle 10g Enterprise Edition and Oracle Database 10g Express Edition (see the readme file for specific version information). You can download the Express Edition for development use from the Oracle web site.
Instructions in this chapter assume you are working with a local database for testing. For production deployments, you might have to ask a database administrator to create a database user for you. You should then be able to run the other SQL scripts yourself, logged on as the user created by the administrator.
Every entity, property, or state machine whose name exceeds 30 characters in length has an entry in the generated
yourname.aliases file (For example,
acme.aliases). This file has no entries if all names have 30 characters or less.
Note that you must run the be-oradeploy utility again, after updating the
yourname.aliases file (as mentioned in the procedure.)
If you add, change, or delete ontology object definitions, the backing store schema will no longer match your ontology. You must update the backing store schema so it still matches the ontology. See
Updating an Existing Oracle Database Schema for details