Create remote Oracle databases on Windows for a stand-alone prod server

For remote Oracle databases, copy ojdbc14.jar from the remote Oracle server to the WebSphere Portal machine...

The Oracle databases must be created manually before configuring WebSphere Portal.

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.

Determine if your Oracle server will be remote or local to the WebSphere Portal installation.

After installing the database software for WebSphere Portal, set the buffer pools allocated to the Oracle database in order for WebSphere Portal to communicate with the Java Content Repository database. Use the following recommended values as a guide. Refer to the Oracle product documentation for information on how to set the buffer pools. Recommended initial buffer pool sizes:

db_block_size = 8192 db_cache_size = 300M db_files = 1024 log_buffer = 65536 open_cursors = 1500 pga_aggregate_target = 200M pre_page_sga = true processes = 300 shared_pool_size = 200M

For IBM Java Content Repository, the open_cursors value may 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 you have more than 875 parallel servers, you should set the parallel_max_servers to 1200.


Prerequisites

Installing Oracle

Creating users
Refer to the following instructions for creating tablespaces:

  1. In the database directory, create the data directory data and the index directoryindex.

  2. Create tablespaces using the following commands as examples: Substitute the values of your environment for the following variables:

    • &jcrdb. is the name of the database created to store user data.

    • &dbpath. is the directory where created the database; the default path is /oracle/oradata.

    Ensure that the '.' is included in the variables when you substitute the values of your environment with these variables.

    Use the same table space names listed in the commands. The table space names cannot be customized or modified.

    create tablespace ICMLFQ32 datafile '&dbpath./&jcrdb./data/&jcrdb._ICMLFQ32_01.dbf' size 300M reuse autoextend on next 10M maxsize UNLIMITED extent management local autoallocate;

    create tablespace ICMLNF32 datafile '&dbpath./&jcrdb./data/&jcrdb._ICMLNF32_01.dbf' size 25M reuse autoextend on next 10M maxsize UNLIMITED extent management local autoallocate;

    create tablespace ICMVFQ04 datafile '&dbpath./&jcrdb./data/&jcrdb._ICMVFQ04_01.dbf' size 25M reuse autoextend on next 10M maxsize UNLIMITED extent management local autoallocate;

    create tablespace ICMSFQ04 datafile '&dbpath./&jcrdb./data/&jcrdb._ICMSFQ04_01.dbf' size 150M reuse autoextend on next 10M maxsize UNLIMITED extent management local autoallocate;

    create tablespace ICMLSNDX datafile '&dbpath./&jcrdb./index/&jcrdb._ICMLSNDX_01.dbf' size 10M reuse autoextend on next 10M maxsize UNLIMITED extent management local autoallocate;

    1. Set the size, autoextend, and maxsize values according to your environment.

      For example, you may want to change the maxsize to a set value rather than UNLIMITED.

    2. Consult your Database Administrator for specific guidance about creating tablespaces for your environment.

    3. Refer to the Oracle command reference for more information about using the create tablespaces command.


Parent topic:

Set up a remote Oracle database on Windows for a stand-alone production server


Previous topic:

Creating users


Next topic:

Modifying database properties