Hey Alex,
Can you hear me now? Hehe.





Please take a few minutes to provide feedback on the quality of service you received from our staff. The Department of Education values your feedback as a customer. Commissioner of Education Dr. Eric J. Smith is committed to continuously assessing and improving the level and quality of services provided to you.Simply use the link below. Thank you in advance for completing the survey.


http://data.fldoe.org/cs/default.cfm?staff=Ed.[Email address protected]




-----Original Message-----
From: Alex Levy
[mailto:db2udbdba-ezmlmshield-x85484487.[Email address protected]
Sent: Thursday, April 10, 2008 5:59 AM
To: LazyDBA Discussion
Subject: RE: Db2diag.log severe messages real or not?

Hello John
I'm shooting in the dark, not having seen these before, but as you've
had no
other replies:
a. Do you see anything on the load messages files?
b. Do you see any corresponding entries in the administration notify log
at
NOTIFYLEVEL=4 ?
c. Do you have any load-related registry variables left lying around
from
pre-V8? I'm thinking particularly of DB2_PARTITIONEDLOAD_DEFAULT and
that
deprecated autoloader one (can't remember the name)
d. If you're on HADR do you have DB2_LOAD_COPY_NO_OVERRIDE set or unset?
e. Running a list utilities show detail loop while a load is in progress
may
help you tie down the messages to a particular load phase.
f. if perchance this is memory related, does increasing the utility heap
size have any effect?

In extremis: the FUNCTION line in the log entry identifies the product
name
("DB2 UDB"), component name ("database utilities"), function name
("sqluRegisterLoadRestart ") that writes the message, as well as the
probe
point ("80") within the function. Since we don't have the source code,
only
a call to IBM Support can actually figure out what goes on at that probe
point.

Good Luck!
Alex Levy

-----Original Message-----
From: John Furlong
[mailto:db2udbdba-ezmlmshield-x69648215.[Email address protected]
Sent: 8 April 2008 16:40
To: LazyDBA Discussion
Subject: Db2diag.log severe messages real or not?



Our db2diag.log is littered with the following "severe" messages. Every
day we see the same group of 3 messages appearing on multiple
occasions. Loads are running during the time that these messages are
showing up in the diaglog, but the loads do not fail they are completing
ok.

Does anyone know what could possibly be causing these messages, and how
to remedy it, or if anything even needs to be done about it?

Thanks.


2008-04-06-08.05.35.858069-240 I17672185A408 LEVEL: Severe
PID : 626722 TID : 1 PROC : db2agent
(CDATA) 0
INSTANCE: db2p01 NODE : 000 DB : GD01
APPHDL : 0-783 APPID: *LOCAL.db2p01.090611003030
FUNCTION: DB2 UDB, database utilities, sqluRegisterLoadRestart, probe:80
MESSAGE : Load Error: Load restart/terminate is not necessary.

2008-04-06-08.05.35.858259-240 I17672594A382 LEVEL: Severe
PID : 626722 TID : 1 PROC : db2agent
(CDATA) 0
INSTANCE: db2p01 NODE : 000 DB : GD01
APPHDL : 0-783 APPID: *LOCAL.db2p01.090611003030
FUNCTION: DB2 UDB, database utilities, sqluLoadPartition, probe:50
MESSAGE : Load Error: Error loading table.

2008-04-06-08.05.35.859076-240 I17674352A405 LEVEL: Severe
PID : 626722 TID : 1 PROC : db2agent
(CDATA) 0
INSTANCE: db2p01 NODE : 000 DB : GD01
APPHDL : 0-783 APPID: *LOCAL.db2p01.090611003030
FUNCTION: DB2 UDB, database utilities, sqlu_register_table_load,
probe:50
MESSAGE : Load Error: Error acquiring partition resources.


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html




---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html

DB2 & UDB email list listserv db2-l LazyDBA home page