Planning for Oracle

When planning to transfer data to Oracle, you should consider the databases and user information, such as database names, what data is stored, and the database space needed.

Before you begin:

Review the "Database considerations" topic.
Ensure the database that you plan to use is supported by this version of WebSphere Portal Express. Refer to Supported hardware and software for the list of supported databases.

The database names and users in this topic are suggested values and provide consistency throughout the documentation. Replace these values with values in your environment.

The Feedback function is not configured by default. It must first be turned on by following the steps in Enable logging, otherwise the Feedback tables will not be created in the new database.
Java Content Repository is a data repository that runs on Oracle to store data for applications such as Personalization, Document Manager, and Web Content Management.

Review the different databases shown in the following table and replace these values with the values in your environment; schema names must be different when the database is shared. WebSphere Portal Express can be configured to use a single shared database if different database users are chosen for each database listed below. On Oracle, a single database configuration can significantly reduce consumption of system resources by the database management system. Using separate table spaces for all databases listed below can improve scalability and performance.

Application	Database name	Space required
WebSphere Portal Express Used for the portal (at a minimum) or to hold all data. Stores information about user customization, such as pages, and user profile and login information.	`release` `comm` `cust`	Depends on the number of users and portal objects, such as pages and portlets.
Document Manager, Personalization,Web Content Management Contains documents, personalization rules, personalization campaigns, and document library configuration information.	`jcrdb`	Depends on the size and number of documents created and uploaded by the Document Manager , the number and size of Personalization rules and campaigns, and the number and size of items and elements created in Web Content Management.
Feedback Contains the information that is logged by your Web site for analysis of site activity and generating reports.	`fdbkdb`	Depends on the amount of traffic to the site. The amount of data that is logged per login-enabled page can vary.
LikeMinds Contains the recommendations to be displayed to users when their interactions with your Web site have been analyzed and predictions generated.	`lmdb`	Depends on the amount of traffic to the site.

Review the tables and types of objects owned by each user. The architecture allows each of the following users to exist in the same database. All table spaces are approximately 2.8 GB by default. The size increases with the use of Java Content Repository.

Application	Database user placeholder	Function
WebSphere Portal Express	`releaseusr` `communityusr` `customizationusr`	Core user who owns approximately 230 tables, used for WebSphere Portal Express core objects, which includes tables that store the user customizations made to pages.
Java Content Repository	`icmadmin`	Java Content Repository user who owns at least 1130 tables. The number could be higher depending on usage.
Feedback	`feedback`	Feedback user who owns approximately 50 tables used for logging site and personalization usage.
LikeMinds	`lmdbusr`	LikeMinds user who owns approximately 15 tables used to hold the Web site usage analysis routines and recommendation text.