By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,870 Members | 1,212 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,870 IT Pros & Developers. It's quick & easy.

Long: DB2 crash because of logging failure

P: n/a
As I wrote last week, we have a problem with a DB2 V8 on Linux. Here is
what is in db2diag.log during online backup:

Starting a full database backup.

2004-04-01-02.33.54.760164 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.588325 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.636770 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.638569 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1880

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.690121 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.698624 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.700536 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.701645 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.750096 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.784768 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.786897 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.788458 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.830150 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.838766 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.840357 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.841499 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.890125 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.898940 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.900623 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.901914 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.950091 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.960600 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.963114 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.965105 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.56.022268 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.56.045394 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.56.065177 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.56.075595 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.56.162526 Instance:lzgneu Node:000
PID:6302(db2agent (idle)) TID:1024 Appid:*LOCAL.lzgneu.075DF1003202
database utilities sqlubcka Probe:130 Database:TELEMATX

Backup Complete.

Now we have an online backup, but _no_ log files since the timestamp of
this backup. The database was completely inoperable, and restoring the
online backup did not succeed because of missing log files.

What does this "TailPage" error mean? It is the first time I see this
error. Is it a hardware problem with the disk? Or what could be the
reason?

Please help!

Regards,
--
Burkhard Schultheis
Tele Data Electronic, Wagnerstr. 10, D-76448 Durmersheim
Email: sc********@tde-online.de
Phone: +49-7245-9287-21, Fax: +49-7245-9287-30
Nov 12 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Burkhard Schultheis wrote:
As I wrote last week, we have a problem with a DB2 V8 on Linux. Here is
what is in db2diag.log during online backup:

(dump snipped)


Burkhard,

1) Have you opened a call with IBM Support on this ?
2) Have you run a full diagnosis of the database (offline) using db2dart ?
3) Did you run out of space in your logging location ?
4) How did the logs disappear ?

I missed your previous posting so apologize if some of this has already been
covered.

Phil

Nov 12 '05 #2

P: n/a
Philip Nelson schrieb:

Burkhard,

1) Have you opened a call with IBM Support on this ?
Not yet. How to make it? Online?
2) Have you run a full diagnosis of the database (offline) using db2dart ?
I have no possibility for a remote connection. On Wednesday I will be at
the machine.
3) Did you run out of space in your logging location ?
No.
4) How did the logs disappear ?


We make an online backup every night, and if it's successful we remove
all logfiles before the first active logfile we got before the backup.
Now the database didn't write any logfile since the backup!

Regards,
--
Burkhard Schultheis
Tele Data Electronic, Wagnerstr. 10, D-76448 Durmersheim
Email: sc********@tde-online.de
Phone: +49-7245-9287-21, Fax: +49-7245-9287-30
Nov 12 '05 #3

P: n/a
Not an answer, only food for thoughts...

Not sure about ;
you say : online backup
log file says : Starting a full database backup.

Do you use this switch?
blk_log_dsk_ful / DB2_BLOCK_ON_LOG_DISK_FULL
(default is off)

0x8610000D -2045771763 SQLP_BADLOG -980 Log File cannot be used
SQL0980C A disk error occurred. Subsequent SQL statements
cannot be processed.

Explanation:

A disk error occurred that prevented successful execution of the
current and subsequent SQL statements. The application program
is not permitted to issue additional SQL statements. For example,
a recovery routine associated with the application program cannot
issue additional SQL statements. The database is marked as
needing recovery and all applications using the database are
prevented from accessing the database.

The statement cannot be processed.

User Response:

Record all error information from the SQLCA, if possible.
Terminate all applications using the database. Determine if the
error is a hardware error. Restart the database. If recovery is
not possible, restore the database from a backup copy.

If installing the sample database, drop it and install the
sample database again.

sqlcode : -980

sqlstate : 58005


You can also look at related apars (log disk full conditions)

http://www-1.ibm.com/support/search....SEPK9%2BSSJQXX
PM

"Burkhard Schultheis" <sc********@tde-online.de> a écrit dans le message de
news:c4*************@ID-100086.news.uni-berlin.de...
As I wrote last week, we have a problem with a DB2 V8 on Linux. Here is
what is in db2diag.log during online backup:

Starting a full database backup.

2004-04-01-02.33.54.760164 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.588325 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.636770 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.638569 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1880

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.690121 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.698624 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.700536 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.701645 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.750096 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.784768 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.786897 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.788458 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.830150 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.838766 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.840357 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.841499 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.890125 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.898940 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.900623 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.901914 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.950091 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.55.960600 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.963114 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.55.965105 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.56.022268 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

TailPage 0 does not match pagelsn 0023CEBF0FFB and firstlsn 0023CEBF8000

PID:1293 TID:1024 Node:000 Title: SQLP_DBCB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

PID:1293 TID:1024 Node:000 Title: SQLP_LFPB
Dump File:/home/lzgneu/sqllib/db2dump/12931024.000

2004-04-01-02.33.56.045394 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:909

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.56.065177 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgwlp Probe:1350

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.56.075595 Instance:lzgneu Node:000
PID:1293(db2loggw (TELEMATX)) TID:1024 Appid:none
data protection sqlpgasn2 Probe:1520

DIA8414C Logging can not continue due to an error.
ZRC=0x8610000D

2004-04-01-02.33.56.162526 Instance:lzgneu Node:000
PID:6302(db2agent (idle)) TID:1024 Appid:*LOCAL.lzgneu.075DF1003202
database utilities sqlubcka Probe:130 Database:TELEMATX

Backup Complete.

Now we have an online backup, but _no_ log files since the timestamp of
this backup. The database was completely inoperable, and restoring the
online backup did not succeed because of missing log files.

What does this "TailPage" error mean? It is the first time I see this
error. Is it a hardware problem with the disk? Or what could be the
reason?

Please help!

Regards,
--
Burkhard Schultheis
Tele Data Electronic, Wagnerstr. 10, D-76448 Durmersheim
Email: sc********@tde-online.de
Phone: +49-7245-9287-21, Fax: +49-7245-9287-30

Nov 12 '05 #4

P: n/a
PM (pm3iinc-nospam) CGO schrieb:

You can also look at related apars (log disk full conditions)

http://www-1.ibm.com/support/search....SEPK9%2BSSJQXX


This search was not helpful. But I made a search for "Tailpage" and it
gave me address
http://www-1.ibm.com/support/docview...id=swg1JR18294.

And that's very interesting! I interpret this page, that it is an error
in DB2 IBM cannot fix, or am I wrong? But that is really bad news. Could
that be, there is an error which can cause a crash, and IBM cannot fix
it?

Regards,
--
Burkhard Schultheis
Tele Data Electronic, Wagnerstr. 10, D-76448 Durmersheim
Email: sc********@tde-online.de
Phone: +49-7245-9287-21, Fax: +49-7245-9287-30
Nov 12 '05 #5

P: n/a
That APAR was fixed in v8 fixpak 2:

http://www-306.ibm.com/cgi-bin/db2ww...aparno=JR18294

Burkhard Schultheis wrote:
PM (pm3iinc-nospam) CGO schrieb:

You can also look at related apars (log disk full conditions)

http://www-1.ibm.com/support/search....SEPK9%2BSSJQXX

This search was not helpful. But I made a search for "Tailpage" and it
gave me address
http://www-1.ibm.com/support/docview...id=swg1JR18294.

And that's very interesting! I interpret this page, that it is an error
in DB2 IBM cannot fix, or am I wrong? But that is really bad news. Could
that be, there is an error which can cause a crash, and IBM cannot fix
it?

Regards,


Nov 12 '05 #6

P: n/a
Blair Adamache schrieb:
That APAR was fixed in v8 fixpak 2:

http://www-306.ibm.com/cgi-bin/db2ww...aparno=JR18294


But this was V8.1 with fixpak 2! Yesterday I installed fixpak 5 and
restored from old ixf files. yesterday we made a call to IBM, and in a
few minutes I will speak to an IBM employee.

Regards,
--
Burkhard Schultheis
Tele Data Electronic, Wagnerstr. 10, D-76448 Durmersheim
Email: sc********@tde-online.de
Phone: +49-7245-9287-21, Fax: +49-7245-9287-30
Nov 12 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.