Database transfer: Create Oracle database
Note that manual steps from the Configuration Wizard can be found in the IBM Knowledge Center.
- See the Oracle product documentation for instructions on creating databases.
- All databases must be created using Unicode Database and National character sets such as UTF8, AL32UTF8, or AL16UTF16.
- IBM recommends that all databases to be used with WebSphere Portal are configured in Dedicated Server Mode.
- If we are using Oracle 11g databases, configure database transfer and runtime with only the ojdbc6.jar.
- If we are using Oracle 12c databases, configure database transfer and runtime with the ojdbc7.jar and xdb6.jar.
- We must set the buffer pools allocated to the Oracle database in order for WebSphere Portal to communicate with the Java Content Repository database. Refer to the Oracle product documentation for information on how to set the buffer pools. Use these recommended buffer pool values as a guide for setting the values:
db_block_size = 8192 bytes db_cache_size = 1 gigabyte db_files = 1024 files log_buffer = 65536 bytes open_cursors = 1500 cursors pga_aggregate_target = 200 megabytes pre_page_sga = true processes = 300 processes shared_pool_size = 200 megabytes
- If we are using Java Content Repository, the open_cursors value might need to be increased based on the table count in the Java Content Repository schema.
- Raise the number of parallel servers as appropriate. For example, if we have more than 875 parallel servers, we should set the parallel_max_servers to 1200.
- The Oracle parameter CURSOR_SHARING allows similar SQL Statements to be shared when possible, which prevents parsing and establishing a new execution plan. The execution plan is used by Oracle to gather the data needed to satisfy a request. There are two options for CURSOR_SHARING. WebSphere Portal supports both options. Regardless of the option selected, portlet applications should not be affected. Contact the database administrator for further assistance on these options.
- FORCE
- When we select this option, Oracle uses the same execution plan for all SQLs that are similar in value even if the values are different. When we use this option, the execution plan may not provide optimum performance. For example, similar SQLs with different values may behave differently when executed running the same plan.
- EXACT
- When we select this option, Oracle only shares the same execution plan for SQLs that are identical and use the same values. This option removes the risk of a SQL statement being executed when optimum performance conditions do not exist.