[DB2-L] Antwort: [DB2-L] z/OS V8 Status RW,UTRW and no Utility active

Ruediger Kurtz

[DB2-L] Antwort: [DB2-L] z/OS V8 Status RW,UTRW and no Utility active
Roy,

we doubt that this is the true reason behind our problem, although one never knows.
However, we didn't restart our DB2s yesterday (or the day before) and as I was frequently checking the status of our databases yesterday because of some online-loads, I am pretty certain that this particular tablespace was not in UTRW status.
But thanks a lot all the same - and regards to the guys at SE, you know whom.


Rüdiger Kurtz
Abteilung Informatik Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg

Telefon 09561 96-3914
Telefax 09561 96-3678
E-Mail [login to unmask email]
Internet www.HUK.de

=============
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Werner Strohmayr.
Vorstand: Rolf-Peter Hoenen (Sprecher), Dieter Beck, Wolfgang Flaßhoff, Stefan Gronbach, Klaus-Jürgen Heitmann, Christian Hofer, Dr. Wolfgang Weiler.
=============



________________________________

Von: DB2 Data Base Discussion List [mailto:[login to unmask email] Im Auftrag von Roy Boxwell
Gesendet: Dienstag, 26. Juni 2007 14:01
An: [login to unmask email]
Betreff: [DB2-L] Antwort: [DB2-L] z/OS V8 Status RW,UTRW and no Utility active



Hi!

You could have hit this "old" bug

PQ91102: START OF DB2 ON RECOVERY SITE DBET CONTAINS INVALID UTRW STATES

During database exception table checkpoint processing, DB2
puts out a dummy hash chain log record if no table entries
are on the hash chain. This log record is needed to merge
log records during a DB2 data-sharing group restart. However,
if the table entries on the hash chain have only non-logged
data, DB2 did not put out any log records for that hash chain;
consequently, group restart could not merge the log records
correctly and old database exception states were applied and
kept as current. The fix is to put out a dummy hash chain
log record if none of the hash table entries have any data to
be logged.


R710 PSY UQ91314 UP04/08/18 P F408
R810 PSY UQ91315 UP04/08/18 P F408


Looks like your problem but the PTF is very old......



Roy Boxwell
SOFTWARE ENGINEERING GMBH
-Product Development-
Robert-Stolz-Straße 5
40470 Düsseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]
http://www.seg.de

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Siegfried Fürst, Gerhard Schubert
--------------------------------------------------------------------------------- Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm