Solaris clustered server: Create Oracle or Oracle RAC databases

Prerequisites

Solaris clustered server: Install Oracle or Oracle RAC

Solaris clustered server: Modify Oracle or Oracle RAC database properties

Create UNICODE character set databases.

For Oracle 10g databases obtain a copy of the ojdbc6.jar file from the Oracle JDBC driver download site, copy it to the WebSphere Portal machine, and update wkplc_dbtype.properties with

oracle.DbLibrary=/path/to/ojdbc6.jar

If we are using Oracle 11g databases, copy the ojdbc6.jar file from the Oracle server to the WebSphere Portal machine and update wkplc_dbtype.properties with

oracle.DbLibrary=/path/to/ojdbc6.jar

The typical location is...

ORACLE_HOME/sqldeveloper/jdbc/lib

When creating Oracle databases for use with WebSphere Portal:

• 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 the Oracle server will be remote or local to the WebSphere Portal installation.

• Ensure the database is registered with the Oracle listener. Use the tnsnames.ora file to describe this database and recycle the listener.

• Set the buffer pools allocated to the Oracle database :

  db_block_size = 8192 bytes
  db_cache_size = 307,200 bytes
  db_files = 1024 files log_buffer = 65536 bytes
  open_cursors = 1500 cursors
  pga_aggregate_target = 204,800 bytes
  pre_page_sga = true processes = 300 processes
  shared_pool_size = 204,800 bytes
  

  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, 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:

  FORCE

  Oracle uses the same execution plan for all SQLthat 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

  Oracle only shares the same execution plan for SQLthat 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.

  WebSphere Portal supports both options. Regardless of the option selected, portlet applications should not be affected.

Prerequisites

Solaris clustered server: Install Oracle or Oracle RAC

Solaris clustered server: Modify Oracle or Oracle RAC database properties

Parent: Solaris clustered server: Set up a remote Oracle or Oracle RAC database
Previous: Solaris clustered server: Modify Oracle or Oracle RAC database properties
Next: Solaris clustered server: Set up Oracle or Oracle RAC automatically or manually