Database Administration Guide
This section identifies considerations that the database administrator may want to be aware of in setting up and maintaining WebLogic Portal databases.
For a discussion of database environment considerations for team development, see the section "Creating a Shared Portal Domain" in the Production Operations Guide at http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/prodOps/index.html.
For additional details on database-specific considerations and recommendations, see the individual database sections in this document.
Information included in this section includes:
A database character set determines which languages can be represented in the database. A database's sort order, or collation, determines the rules by which characters are sorted and compared.
For a globalized WebLogic Portal application, you should plan a database's character set and/or sort order before you set up the database. Changing an existing database's character set and sort order can be a time- and resource-intensive task. Typically a change can be made only if the target character set is a subset of the source or original.
The following sections describe character set and sort order considerations for Portal-supported databases.
For Oracle, you define the character set when you create the database.
AL32UTF8
. UTF8
character set is a common selection. You can retrieve information about an Oracle database's character set and sort order by querying the SYS.NLS_DATABASE_PARAMETERS
table.
For SQL Server, you can define both an instance level and a database level character set and sort order. The default instance level character set for a SQL Server is determined by the locale setting for the Windows operating system. The following sample output from the sp_helpsort
stored procedure shows a common instance level sort order:
Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode Data.
The sample database creation script is located at WL_HOME
\portal\db\sql_server\2000\admin\create_database.sql
defines the WebLogic Portal database with the settings COLLATE SQL_Latin1_General_CP1_CS_AS
. Note that this specifies a case-sensitive definition. Setting the database to case-sensitive allows Content Management queries to function the same for SQL Server as they do for other databases. If Content Management search queries are not written for a case-sensitive environment, you may obtain unexpected results.
You can use the sp_helpdb <
dbname
>
stored procedure to display a SQL Server database's character set and sort order.
For Sybase, you define the character set and sort order when you create the Sybase instance. A commonly used Sybase character set and sort order definition is:
You can use the sp_helpsort
stored procedure to display information about an instance's character set and sort order.
For DB2 databases, you can set character encoding for each database individually. The default character encoding is determined by the operating system.
A commonly used DB2 character encoding is UTF-8
.
You can examine the DB2 CODESET
configuration parameter to determine a database's codeset.
The following sections describe special considerations, recommendations, and requirements for index placement, CLOB/BLOB/TEXT/IMAGE data storage, and behavior tracking.
For Oracle databases, use the rebuild_indexes.sql
script to place indexes into a WEBLOGIC_INDEX tablespace. Run this script manually after creating the WebLogic Portal database to move indexes into their own tablespace.
For SQL Server and Sybase, as of 8.1 SP4 the Data Definition Language (DDL) for non-clustered indexes is defined with ON WEBLOGIC_INDEX
to place indexes into their own file group or segment. You must define the WEBLOGIC_INDEX
file group or segment before running WebLogic Portal database creation or upgrade scripts. For detailed information about SP4 database changes, see the Upgrade Guide at http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/upgrade/index.html.
This section describes recommendations and special considerations for tables that contain CLOB/BLOB (Oracle/DB2) or TEXT/IMAGE (Sybase/SQL Server) data.
As a general rule, for optimal performance with any of the supported Portal database platforms, CLOB/BLOB/TEXT/IMAGE table data should be physically stored separately from non-CLOB/BLOB/TEXT/IMAGE data. However, to simplify deployment and to allow for flexibility in your configuration, the default Portal database schema is not deployed with separated data. To determine if your specific application is a candidate for separating CLOB/BLOB/TEXT/IMAGE storage, assess the following considerations in your environment:
If you want to change your storage allocations, see your database documentation for specific details on changing CLOB/BLOB/TEXT/IMAGE settings.
The following additional tables contain CLOB/BLOB or TEXT/IMAGE data types; you can experiment with storage changes to determine the effect on performance.
Behavior tracking is typically used to track visitor behavior by recording events.
Due to the large number of rows that can be written to the BT_EVENT table when behavior tracking is enabled, you might want to use a separate database (or tablespace and schema, depending upon your DBMS) to store behavior tracking data.
For each database type other than PointBase, the following sections include instructions for creating a separate database for behavior tracking events:
Some third-party behavior tracking reporting tools extract data from the BT_EVENT table data and place it into another set of database tables. For more information on reporting and analytics tools, see the Portal Solutions Catalog at http://dev2dev.bea.com/products/wlportal/psc/Reporting_Analytics_BI.jsp.
Some databases provide the ability to cache or "pin" database tables into memory. Choose a database caching implementation based on the WebLogic Portal components that are deployed for your application and how you deploy them.
The following text summarizes the support provided by each database type for caching or pinning database tables. Depending on your environment, focus your caching strategy on small tables and frequently referenced tables.
DBCC PINTABLE (database_id, table_id)
to pin tables to the buffer cache.sp_objects_stats
to identify hot objects that may benefit from their own cache. Use a Sybase monitoring tool or sp_sysmon
to determine if cache hit ratios are acceptable. BUFFERPOOLs
to cache database data and describes configuring bufferpools as the single most important tuning area. DB2 allows you to assign individual tables and indexes to a BUFFERPOOL
. Note: See the individual database chapters for additional details on database-specific considerations.
For Oracle and SQL Server databases, an 8K page/block size is the default.
For DB2 an 8K bufferpool is defined for the WebLogic Portal tables and indexes that require this larger pool size (higher than the 4K default).
For Sybase databases an 8K pagesize is required for several WebLogic Portal tables and indexes.
A Sybase instance's default locking mechanism is "ALL PAGES". For concurrency, locking can also be defined for each table in a Sybase database.
In 8.1 SP4 the following WebLogic tables are defined with LOCK
DATAROWS
for Sybase. Other WebLogic Portal tables for Sybase (excluding those defined in collaboration_create_tables.sql
) are defined with LOCK
DATAPAGES
.
Based on your usage of WebLogic Portal components with a Sybase database, you may decide to modify additional tables to LOCK
DATAROWS
.
The size required for your WebLogic Portal database(s) depends on many factors, including the following:
The following sections describe some WebLogic Portal database tables that you should monitor closely for growth due to increasing data volumes.
The BT_EVENT table can grow significantly if Behavior Tracking is enabled.
The following database tables store personalization data; monitor them for data growth.
The following tables involve the Portal Framework and/or Web Services for Remote Portlets (WSRP) and can potentially be high volume tables; monitor them for data growth.
BOOK_DEFINITION
. There is always at least one book instance, namely the primary instance; all other instances represent customization by administrators or end users. This table can grow significantly if extensive user customization occurs. The following database tables store content management (CM) and versioning (CMV) data; monitor them for data growth.
SUBJECT
for a BOOK
might have a value of FINANCE
. This table can grow significantly if Content Management is used to store large quantities of data. This table will likely be the largest Content Management table because it stores the actual content associated with each Content Node.
Content search within WebLogic Portal typically performs best when accessing database indexes associated with the content repository. In some situations the Oracle optimizer, based on database statistics, will choose to perform tablespace scans instead of using indexes to access the data. Most often this will result in a much slower response time than if an index was used.
To improve response time, verify that the following Oracle initialization parameter reads:
optimizer_mode=choose.
In addition to ensure that Oracle indexes are given greater preference over tablespace scans, the following two initialization parameters can be altered:
optimizer_index_cost_adj (range 0-100)
optimizer_index_caching (range 0-100)
Refer to your Oracle documentation for the impact of each of these settings to make sure it is right for your installation.
Each DBMS has its own utility or commands for updating the database statistics used by its query optimizer. A DBA should schedule periodic jobs to maintain database statistics.
The statistics that you collect for your database often provide information on the organization of tables and indexes in your database.
Normal DML operations (for example, DELETE
, INSERT
, UPDATE
) that the WebLogic Portal application performs can affect table and index organization; this can affect database performance. Refer to your database vendor product documentation for details on utilities that are available for table and index reorganization and for information on determining when a re-organization should occur.
Use the same procedures for backup and recovery of WebLogic Portal databases as you use for other data. The following text lists some general recommendations:
Perform periodic test restores to ensure that your backups are sound.
If you are using the optional commerce functionality in a Portal domain configured for XA, then you must move the weblogic.jdbc.jts.commercePool JNDI name from the portalFrameworkPool to the cgDataSource-nonXA JDBC Tx Data Source. For information about using commerce functionality, see Adding Commerce Services to an Application in the WebLogic Workshop Help.
The Propagation Utility guides you through the process of propagating the configuration contents, including portal framework, datasync, and security data, of one portal domain environment to another. For example, the Propagation Utility can play a role whenever you move a portal application from a staging environment to the production environment.
You should be aware of the usage of this utility, and you may need to back up databases prior to propagation. For more information about this utility, contact BEA customer support.
To prevent network latency issues, you should locate your database and your WebLogic Portal instances in the same data center. This recommendation is especially important when you use the Propagation Utility, to ensure that a large propagation process can complete successfully.