PQ67297: SE_TABLE IN REPOSITORY NOT INITIALIZED CORRECTLY WHEN RUNNING DB2390.SQL | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description L3 is aware of this problem and it should go to SM component. . Customer is using WAS V4.03 with repository on system 390. The customer is using db2390.sql script to create the tables in the repository. The db2390 script runs successfully and creates the tables, however WAS requires a row inserted in to SE_TABLE for sequence numbers(?). When WAS is started the error is thrown that SE_TABLE is corrupted(admin trace). If the customer manually adds a dummy record in SE_TABLE then the problem goes away. The following cmd can be used to insert the dummy record. . db2 connect to was40 user db2admin using db2admin insert into ejsadmin.se_table (MSG_ID, NODE_NAME, SERVER_NAME, MSG_TIME) values(0, '0', '0', '1000') Note: "ejsadmin" should be replaced with whatever db schema currently in use. The value 1000 is the default size of the logs specified through com.ibm.ejs.sm.adminServer.seriousEventLogSize in admin.config.Local fix Manually create the dummy record in WAS repositoryProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0.3 or 4.0.4 * * users with a repository on DB2/390. * **************************************************************** * PROBLEM DESCRIPTION: SE table in repository not initialized * * correctly when running db2390.sql * **************************************************************** * RECOMMENDATION: * **************************************************************** The user is on WAS 4.0.3 with repository on system 390 and is using db2390.sql script to create the tables in the repository. The db2390 script runs successfully and creates the tables, however WAS requires a row inserted into SE_TABLE for sequence numbers and log size. When WAS is started the error is thrown that SE_TABLE is corrupted. If a dummy record is manually added in SE_TABLE, then the problem will no longer occur.Problem conclusion WAS will insert one row into SE_TABLE with the sequence number and serious event log size if no row exists in the SE_TABLE during WAS startup no matter if the createTable flag is set to false. WAS will also check the table and insert the row if the users delete all entries in SE_TABLE accidently.Temporary fix The test fix has been tested by DB2 team and placed in wasdoc0\a pars.Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ67297
IBM Group: Software Group
Modified date: Dec 9, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.