|
Problem(Abstract) |
The Scheduler LMPR table cannot be replicated by default.
This could cause a problem if you want to replicate the tables, The IBM®
WebSphere® Application Server Information Integrator 'Q Replication'
function requires primary keys or unique keys in order to perform database
replication. |
|
|
|
Cause |
The scheduler service utilizes several database tables to
persist the scheduled task data. The LMPR table does not contain a primary
key. Primary keys are usually required when performing advanced database
operations, such as replication. If a primary key is required and the
database supports primary key constraints with 508 bytes, then a primary
key can be created manually. However, some databases, such as Informix®
and DB2® z/OS® do not allow primary key constraints this large. |
|
|
Resolving the
problem |
Creating a primary key for the LMPR table on DB2:
- When using IBM DB2 version 7.2, verify that the
DB2_INDEX_2BYTEVARLEN registry value is set to on.
- When using IBM DB2 version 8, verify that the DB2_INDEX_TYPE2
registry value is set to off or not set at all.
- Determine what table prefix the scheduler configuration is using by
looking at the Scheduler resource in the WebSphere Application Server
Administration Console.
- Run the following SQL statement to add a primary key to the LMPR
table, using the same userid that was used to create the scheduler tables.
Substitute your table prefix name for ${TBLPFX}:
ALTER TABLE "${TBLPFX}LMPR" ADD PRIMARY KEY (LEASENAME,NAME)
- The LMPR table will now contain a primary key.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|