Chapter 24 Setting up a Backing Store Database : Backing Store Database Setup Overview

Backing Store Database Setup Overview
You can implement a 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.
If you use a limited-size cache, you must use a backing store so that data evicted from the cache is not lost.
This overview provides summary information about setting up the database, with references to the sections that provide detailed information.
You must also configure various properties to enable and configure backing store functionality. See Chapter 25, Project Configuration for Backing Store for details.
Backing Store Requirements
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.
Before You Begin Database Setup
Backing Store Database Setup Tasks
Backing store configuration tasks for each backing store, and background information are summarized below.
Resources Required for Setting Up the Database outlines all the resources you need to set up a backing store.
Backing Store Database Configuration Tasks explains several tasks you must complete in order to configure the database schema, including generating SQL scripts for your project and running them to create the database user and tables.
Extra Procedure to Handle Long Identifier Names
A known limitation in Oracle means that each identifier name cannot exceed 30 characters in length. If you have longer names, remember to complete Task C, Shorten Long Names Using the Aliases File, to give an alias to each long identifier name.
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.)
After You Finish Database Setup
You must also configure various properties to enable and configure backing store functionality. See Chapter 25, Project Configuration for Backing Store for details.
Maintaining a Backing Store—If Ontology Object Definitions Change
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 Backing Store Database Schema for details