473,397 Members | 1,985 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,397 software developers and data experts.

Long: DB2 crash because of logging failure

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
6 10202
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
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
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
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
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
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 thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

48
by: Joseph | last post by:
Hi I'm writing a commercial program which must be reliable. It has to do some basic reading and writing to and from files on the hard disk, and also to a floppy. I have foreseen a potential...
2
by: Per Bergland | last post by:
I have a system service written in C#. For some reason it fails to start on our external web server (running a tightened Windows 2000). If I try to start the services after logging on, it works...
6
by: VK | last post by:
I'm using window.open method in my script to open poup window. Recently Internet Explorer users reported that the script crashes on their machine with different runtime errors. See the bug:...
10
by: xixi | last post by:
i have db2 udb v8.1 on windows 64 bit 2003 server, after db2 server start , i found this in the db2diag.log, is this error? 2004-05-05-15.28.30.780000 Instance:DB2 Node:000...
44
by: Patrick | last post by:
Hello I have the following "easy" problem. I have a string which contains 1000 chars. Now my task is to cut the string at his 650 position. I tried strcpy, to copy the first 650 chars into...
12
by: benjamin.krulewitch | last post by:
I'm debugging an issue with a C program that causes the computer to crash, and I'm attempting to log information immediately before the crash occurs. I us my BKprintLog function (see below) to...
110
by: alf | last post by:
Hi, is it possible that due to OS crash or mysql itself crash or some e.g. SCSI failure to lose all the data stored in the table (let's say million of 1KB rows). In other words what is the worst...
6
by: bjornms | last post by:
The application i build in C#.net is crashing once a month. I can't reproduce the crash. Is there a way to track down where the program crashes, without putting logging everywhere in the code?...
3
by: nicholas.petrella | last post by:
I am currently trying to use the python logging system as a core enterprise level logging solution for our development and production environments. The rotating file handler seems to be what I...
0
by: emmanuelkatto | last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud. Please let me know. Thanks! Emmanuel
0
BarryA
by: BarryA | last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
1
by: nemocccc | last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
1
by: Sonnysonu | last post by:
This is the data of csv file 1 2 3 1 2 3 1 2 3 1 2 3 2 3 2 3 3 the lengths should be different i have to store the data by column-wise with in the specific length. suppose the i have to...
0
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
0
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
0
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
0
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.