2 Oracle Beehive Database Requirements

This chapter describes Oracle Beehive database requirements, creating databases, and configuring database settings.

It covers the following topics:

General Requirements
Patches
Initialization Parameters
Logging Settings
Creating a Database
Using Oracle Real Application Clusters Database
Customizing Oracle Beehive Tablespaces Layout
Using Raw Storage
Upgrading Oracle Database 11g Release 1 to Oracle Database 11g Release 2
Post-Installation Procedures for Oracle Beehive Databases

General Requirements

Oracle Beehive requires an existing database with the following characteristics:

Supports Oracle Database 11g Release 1 and 2 (11.1.0.7, 11.2.0.1, 11.2.0.2, and 11.2.0.3) Enterprise Edition, installed on any supported operating system. Ensure that you have applied all the patches listed in the section "Patches".
Uses character set AL32UTF8 (Unicode)
Contains the following standard database components:
- Oracle XML DB
- Oracle interMedia (Oracle Multimedia in Oracle Database 11g)
- Oracle Text
- Partitioning
Contains Rules Manager and Expression Filter (Rules Manager and Expression Filter are installed automatically with Oracle Database 11g Enterprise Edition.)

Patches

Microsoft Windows

For Microsoft Windows (32-bit and 64-bit versions), install the latest patch bundle for your database.

Note:

Refer to latest Patchset Readme for information on: Patch Required for Upgraded Beehive Instances on Oracle Database 11.2.

The latest Patset Readme is available on the Beehive Documentation Library at: http://www.oracle.com/pls/bee2/homepage

Operating Systems Other Than Microsoft Windows

Install the following patches for Oracle Database 11g Release 1 (11.1.0.7):

9548753: MERGE REQUEST ON TOP OF 11.1.0.7.0 FOR BUGS 9128529 8499043
8537211: MERGE LABEL REQUEST ON TOP OF 11.1.0.7 FOR BUGS 6625210 7694979 7378322
8531282: MERGE LABEL REQUEST ON TOP OF 11.1.0.7 FOR BUGS 8352309 7586451
8499600: ORA-01555 ERRORS ON SECUREFILES READS EVEN UNDER LOW LOADS/NO UPDATE ACTIVITY
8487273: MERGE LABEL REQUEST ON TOP OF 11.1.0.7 FOR BUGS 8214576 7258928
8221425: STBH:HP:11G - ORA-04031: UNABLE TO ALLOCATE 912 BYTES OF SHARED MEMORY
7707103: RECOMPILATION OF LIBRARY UNIT GIVES END-OF-FILE COMMUNICATION CHANNEL
7690421: INVALID TZ VALUE IN TIMEZONE COLUMN PRODUCES ORA-01875
7685452: 10.2.0.5.0 : HP-PA : ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [4449], [],
7643188: SQL VERSION COUNT REPORTED IN AWR DOES NOT MATCH SQLSTATS FOR 1 SQL ID
7500792: HIGH GETS ON "KOKC DESCRIPTOR ALLOCATION LATCH" WITH MORE THAN 400 USERS
7313961: MISSING LSFEND IN DRUERE() CALLS ADDED FOR BUG 6499258
7311226: PARTITIONED TABLE AND FILTER BY OPTIMIZE_INDEX NOT PICKING UP WHERE IT LEFT OFF
7273988: TST&PERF:QUERY PLAN IS VERY BAD IN RDBMS_MAIN_LINUX_080623
7156912: ORACLE TEXT INDEXING HANGS ON A HTML DOCUMENT WITH LONG COMMENTS
7047984: ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [KJBCLOSE:MAS], [3], [1]...
6977167: ORA-04092: CANNOT ROLLBACK IN A TRIGGER RECEIVED REQUIRING INSTANCE BOUNCE
6782437: QUERY WITH MULTIPLE SUBQUERIES PERFORMING POORLY AFTER 10G UPGRADE
6750049: LIBNNZ10.SO DLOPEN FAILED WHEN TRYING TO START ONS (NODEAPPS)
6698219: DBMS_LINK ALLOWS PATH > 1024 CAUSING CORRUPT REPOSITORY
6355412: JOB CONSUMES 100% CPU FOR EXTENDED PERIODS
6263237: TCH11G: ORA-7445 WHILE RUNNING ADPATCH
6083201: MERGE STATEMENT WITH XML TYPE FAILS WITH ORA-7445 [FCLOSE()+29]

Install the following patches for Oracle Database 11g Release 1 (11.1.0.7.2):

Note:

Install patches in the following order:

Oracle Database 11g Release 1 (11.1.0.7) patches as specified in this document
Oracle Database 11g Release 1 (11.1.0.7.2) Patch Set Update; for more information about Patch Set Updates, refer to Oracle My Support Note 854428.1
Oracle Database 11g Release 1 (11.1.0.7.2) as specified in the following list

9348916: MERGE REQUEST ON TOP OF 11.1.0.7.2 FOR BUGS 6856345 7284151 8465729 9010222
7047984: ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [KJBCLOSE:MAS], [3], [1]...
6782437: QUERY WITH MULTIPLE SUBQUERIES PERFORMING POORLY AFTER 10G UPGRADE
6625210: ORA-22370: INCORRECT USAGE OF METHOD ANYDATA INSERT

Install the following patches for Oracle Database 11g Release 2 (11.2.0.1):

9275876: PEOPLESOFT QUERY FAILED WITH CORE DUMP ORA 7445 QERIXGETKEY
9033671: REGR: ORA-07445: EXCEPTION ENCOUNTERED: CORE DUMP [KKQFPPDRV1()+66] [SIGSEGV]
9010222: APPS ST 11G ORA-00600 [KKSFBC-REPARSE-INFINITE-LOOP]
8772524: ORA-38500: EXPRESSION IS INVALID IF WE USE THE IN OPERATOR

Initialization Parameters

The database requires some initialization parameters to have a minimum value as specified in the following table:

Table 2-1 Minimum Values of Oracle Database Initialization Parameters

Property	Value
compatible	11.1.0.0.0 Note: Do not modify this parameter if it is already set to a higher value. Ensure that the value of this parameter is in the form `x.x.x.x.x` (for example, `11.1.0.7.0`). If this format isn't used, you may encounter a validation error stating that the compatible parameter is not of the proper minimum version.
db_block_size	Either this parameter must be set to 8192, or one of the following parameters have to be set: db_8k_cache_size db_16k_cache_size db_32k_cache_size The db_cache_size parameter specifies in bytes of the cache of standard block size buffers. Oracle Beehive will use this value for the block size of its tablespaces. If any of the db_nk_cache_size parameters are set, then Oracle Beehive will use the lowest value that is equal or greater than 8192. Refer to "Specifying Database Block Sizes" in Oracle Database Administrator's Guide for more information.
java_pool_size	50M (52428800)
job_queue_processes	10
processes	150
sga_max_size	1G
sga_target	500M
undo_retention	3600

Note:

You may have to increase the values of processes and sessions if you are using Oracle RAC.

To see all parameters (in alphabetical order) along with their current values, use the following SQL*Plus command:

SQL> SHOW PARAMETERS

You may display parameters that contain a specified string. For example, to display all parameters having COMPATIBLE in their names, use the following command:

SQL> SHOW PARAMETERS COMPATIBLE

Set initialization parameters with the ALTER SYSTEM command. For example, to set the COMPATIBLE parameter with the value 11.1.0.7.0, use the following command:

SQL> ALTER SYSTEM SET COMPATIBLE = '11.1.0.7.0' SCOPE = SPFILE;

Note:

After setting initialization parameters, restart the database.

Logging Settings

If your Oracle Beehive deployment is a production system, it is strongly recommended that you set the archive log mode of the database to ARCHIVELOG, which enables the archiving of the redo logs. Use the following command to determine the database's archive log mode:

SQL> SELECT LOG_MODE FROM SYS.V$DATABASE;

To set the archive log mode to ARCHIVELOG, use the following commands:

SQL> shutdown immediate
SQL> startup mount exclusive
SQL> alter database archivelog;
SQL> alter database open;

Creating a Database

You may use Database Configuration Assistant (DBCA) to create and configure a database. For more information about this tool, refer to "Creating a Database Using DBCA" in Chapter 2, "Installing Oracle Database and Creating a Database" in Oracle Database 2 Day DBA.

Tip:

When creating a database for Oracle Beehive with DBCA, you may choose any template. With DBCA, you may also turn on the archive log mode (by selecting the option Enable Archiving), set the character set to AL32UTF8, and set initialization parameters listed in "Initialization Parameters".

Using Oracle Real Application Clusters Database

Refer to "Configuring and Installing Oracle Beehive for Oracle RAC" for pre-installation and post-installation steps required for Oracle Beehive deployments that use Oracle Real Application Clusters (Oracle RAC) databases.

Customizing Oracle Beehive Tablespaces Layout

You may customize the layout of Oracle Beehive tablespaces with the script <Oracle home>/beehive/db/framework/beehive_custom_ts.sql. You may change tablespace names, initial size of the datafile, block size, and datafile autoextend options.

By default, Oracle Beehive uses eleven tablespaces. The beehive_custom_ts.sql script maps each tablespace to a placeholder. The Oracle Beehive Install Wizard uses these placeholders (instead of the real tablespace name) for configuration.

For example, in the beehive_custom_ts.sql script, the tablespace BEE_DATA is mapped to the placeholder ts_data:

REM Tables containing transactional data
DEFINE ts_data            = BEE_DATA
DEFINE ts_data_path       = ''
DEFINE ts_data_sz         = 512M
DEFINE ts_data_bsz        = 8192
DEFINE ts_data_ae         = ON
DEFINE ts_data_ae_nx      = 128M

You must specify the mapping between the placeholders, such as ts_data and ts_index, and the corresponding tablespaces. If one tablespace is to be shared across multiple placeholders, adjust the tablespace size accordingly.

This script creates a special view named bee_tablespaces, which then is used by the install scripts. You may drop the view after a successful installation. Since the tablespace mapping information can be reused for subsequent product reinstallations, the installation script does not drop it.

The script also produces an output file with the actual CREATE TABLESPACE commands. The output file name is create_beehive_tablespaces.sql

After making your changes to the script, run it with SYS privileges.

Minimum Tablespace Sizes

By default, Oracle Beehive tablespaces are created with autoextend enabled. If you prefer to manage the size of the Oracle Beehive tablespaces yourself, the total size of all Oracle Beehive tablespaces should be at least 15 GB.

Using Raw Storage

If you want to use a database that uses raw storage, customize the script <Oracle home>/beehive/db/framework/beehive_custom_ts.sql. Refer to "Customizing Oracle Beehive Tablespaces Layout" for more information about this script.

To use a raw device (which you have created and properly configured) for a particular tablespace, specify the full path of its datafile in the appropriate variable. For example, if you want to use a raw device for the BEE_DATA tablespace, specify the full path of its datafile in the ts_data_path variable.

In addition, set the variable APPEND_FILE_NAME to N.

After making your changes to the script, run it with SYS privileges.

Upgrading Oracle Database 11g Release 1 to Oracle Database 11g Release 2

If you upgrade Oracle Database 11g Release 1 (11.1.0.7) to Oracle Database 11g Release 2 (11.2) after installing Oracle Beehive, follow these steps:

Shut down Oracle Beehive:
```
beectl stop --all
```
Run the following SQL scripts as the BEE_CODE user in the specified order:
1. <Oracle Beehive home>/beehive/db/framework/ocs_stop_jobs.sql
2. <Oracle Beehive home>/db/dbclone/drop_expression_indexes.sql
3. <Oracle Beehive home>/db/dbclone/create_expression_indexes.sql
4. <Oracle Beehive home>/db/framework/ocs_enable_jobs.sql
Start Oracle Beehive:
```
beectl start --all
```

Post-Installation Procedures for Oracle Beehive Databases

After you have successfully installed Oracle Beehive, refer to "Oracle Beehive Database Post-Installation Procedures" for tuning recommendations to perform on your Oracle Beehive database.