db2 V7.2 trap after FP5

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Massimiliano Campagnoli - 04 Jul 2006 09:08 GMT

Hi All,
I know that db2 V7.2 is no more supported and nor OS/2 is supported
anymore but I wonder if someone here can give me some help on this.

Platform: DB2 V7.2 FixPak 14
OS: OS/2 (actually ECS 1.2 latest fixpak)

I've migrated our production database from DB2 V5.2 to V7.2 GA for OS/2
which is the latest available for this platform. Migration succeded and
database works OK.
But after installing the latest FixPak 14 I am not able any more to
execute some query against our database. In particular there is a query
over a view that gives the following errors in DB2DIAG.LOG (and a trap
file).
Please note that this happens with all fixpak from FixPak 5 to FixPak
14 (while FixPak 4 still works). Moroever I've tried to eliminate some
columns from the select statement inside the view and magically the
query worked again.

----

2006-07-04-09.45.49.610000 Instance:DB2 Node:000
PID:156(DB2SYSC.EXE) TID:11 Appid:*LOCAL.DB2.060704134536
data_management sqldmPrefetchList Probe:462 Database:DBASTORI

LIST PREFETCH got list in reverse order.
72 0...55f4 ffff U...

2006-07-04-09.45.49.620000 Instance:DB2 Node:000
PID:156(DB2SYSC.EXE) TID:11 Appid:*LOCAL.DB2.060704134536
global_services sqlzerdm Probe:40 Database:DBASTORI

55f4 ffff U...

2006-07-04-09.45.49.640000 Instance:DB2 Node:000
PID:156(DB2SYSC.EXE) TID:11 Appid:*LOCAL.DB2.060704134536
relation_data_serv sqlrr_dump_ffdc Probe:17 Database:DBASTORI
DIA3876C A data management services programming error occurred.

2006-07-04-09.45.49.650000 Instance:DB2 Node:000
PID:156(DB2SYSC.EXE) TID:11 Appid:*LOCAL.DB2.060704134536
relation_data_serv sqlrr_dump_ffdc Probe:17 Database:DBASTORI
DIA9999E An internal error occurred. Report the following error code :
"0xFFFFF455".

Data Title:SQLCA PID:156 TID:11 Node:000
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 2
sqlerrmc: 85
sqlerrp : sqlripfrU¶
sqlerrd : (1) 0xFFFFF455 (2) 0x00000055 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

Dump File:C:\SQLLIB\DB2\15611.000 Data:SQLCA
Dump File:C:\SQLLIB\DB2\15611.000 Data:DB2RA

Data Title:CREATOR PID:156 TID:11 Node:000
4e55 4c4c 4944 2020 NULLID

Data Title:PACKAGE PID:156 TID:11 Node:000
5351 4c43 3239 4436 SQLC29D6

Dump File:C:\SQLLIB\DB2\15611.000 Data:CREATOR
Dump File:C:\SQLLIB\DB2\15611.000 Data:PACKAGE
Dump File:C:\SQLLIB\DB2\15611.000 Data:REQUEST TYPE
Dump File:C:\SQLLIB\DB2\15611.000 Data:Recursive dump_sect
Dump File:C:\SQLLIB\DB2\15611.000 Data:PACKAGE ENTRY
Dump File:C:\SQLLIB\DB2\15611.000 Data:USED_IN_UOW BIT VECTOR
Dump File:C:\SQLLIB\DB2\15611.000 Data:SECTION NUMBER
Dump File:C:\SQLLIB\DB2\15611.000 Data:SECTION DIR ENTRY
Dump File:C:\SQLLIB\DB2\15611.000 Data:cursor name
Dump File:C:\SQLLIB\DB2\15611.000 Data:cache cb

Data Title:section stmt PID:156 TID:11 Node:000
5345 4c45 4354 202a 2046 524f 4d20 4d4f SELECT * FROM MO

5649 4d45 4e54 4920 5748 4552 4520 4e55 VIMENTI WHERE NU

4d45 524f 4f52 4449 4e45 3d31 3430 3030 MEROORDINE=14000

Dump File:C:\SQLLIB\DB2\15611.000 Data:section stmt
Dump File:C:\SQLLIB\DB2\15611.000 Data:sentptr
Dump File:C:\SQLLIB\DB2\15611.000 Data:sentptr->sectlen
Dump File:C:\SQLLIB\DB2\15611.000 Data:sentptr->cache_cb
Dump File:C:\SQLLIB\DB2\15611.000
Data:sentptr->cache_cb->cached_sectptr
Dump File:C:\SQLLIB\DB2\15611.000
Data:sentptr->cache_cb->cached_sectptr->thread_list
Dump File:C:\SQLLIB\DB2\15611.000 Data:calculated section size (1): not
including thread list
Dump File:C:\SQLLIB\DB2\15611.000 Data:calculated section size(2):
including thread structure
Dump File:C:\SQLLIB\DB2\15611.000 Data:thd_table
Dump File:C:\SQLLIB\DB2\15611.000 Data:thd_table->size
Dump File:C:\SQLLIB\DB2\15611.000 Data:calculated section size(3):
including thread list table
Dump File:C:\SQLLIB\DB2\15611.000 Data:the_section
Dump File:C:\SQLLIB\DB2\15611.000 Data:Relocated section
Dump File:C:\SQLLIB\DB2\15611.000 Data:Section relocated; reltables
dumped
Dump File:C:\SQLLIB\DB2\15611.000 Data:section ptr
Dump File:C:\SQLLIB\DB2\15611.000 Data:section size
Dump File:C:\SQLLIB\DB2\15611.000 Data:dynamic ptr
Dump File:C:\SQLLIB\DB2\15611.000 Data:dynamic size
Dump File:C:\SQLLIB\DB2\15611.000 Data:shared dynamic ptr
Dump File:C:\SQLLIB\DB2\15611.000 Data:shared dynamic size
Dump File:C:\SQLLIB\DB2\15611.000 Data:dynamic section header
Dump File:C:\SQLLIB\DB2\15611.000 Data:offset in section
Dump File:C:\SQLLIB\DB2\15611.000 Data:opcode
Dump File:C:\SQLLIB\DB2\15611.000 Data:agg_mode
Dump File:C:\SQLLIB\DB2\15611.000 Data:section1
Dump File:C:\SQLLIB\DB2\15611.000 Data:dynamic buffer

Reply to this Message

Massimiliano Campagnoli - 04 Jul 2006 09:43 GMT

Ok,
I've rewritten the view that was causing the trap and now the trap
disappeared regardless the fixpak applied.

>From one side I am happy to have solved the problem but from the other

I would be very gratefull to the gurus of this forum if they could
teach me why a query rewrite has this effect.

The orginal view was:

CREATE VIEW MOVIMENTI
AS SELECT

T1.RIGAREGISTRO,
T1.CAUSALE,
T1.CODICEARTICOLO,
T3.DESCRIZIONE,
T1.QUANTITA,
T1.CODICELOTTO,
T1.DATAMOVIMENTO,
T1.CQGENITORE,
T7.CODICEARTICOLO AS ARTICOLOFIGLIO,
T1.BADGE,
T5.DATAORDINE,
T1.NUMEROORDINE,
T1.NUMERORIGA AS NUMERORIGAORDINE,
T5.RIFERIMENTO,
T5.CODICECLIENTE,
T6.NOMEBREVE,
T5.CODICEDESTINAZIONE,
T8.DATADDT,
T8.NUMERODDT,
T8.NUMERORIGA AS NUMERORIGADDT,
T9.DATAFATTURA,
T9.NUMEROFATTURA,
T9.NUMERORIGA AS NUMERORIGAFATTURA

FROM
REGISTROMAGAZZINO T1 JOIN ARTICOLI T3 ON
T1.CODICEARTICOLO=T3.CODICEARTICOLO
LEFT JOIN DDTCLIENTI T8 ON T1.RIGAREGISTRO = T8.RIGAREGISTRO
LEFT JOIN FATTURECLIENTI T9 ON T1.RIGAREGISTRO = T9.RIGAREGISTRO
LEFT JOIN LOTTI T2 ON T1.CODICELOTTO=T2.CODICELOTTO
LEFT JOIN TESTATAORDCLI T5 ON (T1.NUMEROORDINE=T5.NUMEROORDINE AND
T5.NUMEROORDINE > 0)
LEFT JOIN CLIENTIFORNITORI T6 ON (T5.CODICECLIENTE=T6.CODICECLIFO AND
T6.TIPO=1)
LEFT JOIN LOTTI T7 ON T1.CQGENITORE=T7.CODICELOTTO

;

and

the new reworked view is

CREATE VIEW MOVIMENTI
AS SELECT

T1.RIGAREGISTRO,
T1.CAUSALE,
T1.CODICEARTICOLO,
T3.DESCRIZIONE,
T1.QUANTITA,
T1.CODICELOTTO,
T1.DATAMOVIMENTO,
T1.CQGENITORE,
T7.CODICEARTICOLO AS ARTICOLOFIGLIO,
T1.BADGE,
T5.DATAORDINE,
T1.NUMEROORDINE,
T1.NUMERORIGA AS NUMERORIGAORDINE,
T5.RIFERIMENTO,
T5.CODICECLIENTE,
T6.NOMEBREVE AS NOMEBREVE,
T5.CODICEDESTINAZIONE,
T8.DATADDT,
T8.NUMERODDT,
T8.NUMERORIGA AS NUMERORIGADDT,
T9.DATAFATTURA,
T9.NUMEROFATTURA,
T9.NUMERORIGA AS NUMERORIGAFATTURA

FROM
REGISTROMAGAZZINO T1 JOIN ARTICOLI T3 ON
T1.CODICEARTICOLO=T3.CODICEARTICOLO
LEFT JOIN DDTCLIENTI T8 ON T1.RIGAREGISTRO = T8.RIGAREGISTRO
LEFT JOIN FATTURECLIENTI T9 ON T1.RIGAREGISTRO = T9.RIGAREGISTRO
LEFT JOIN LOTTI T2 ON T1.CODICELOTTO=T2.CODICELOTTO
LEFT JOIN LOTTI T7 ON T1.CQGENITORE=T7.CODICELOTTO
LEFT JOIN
(TESTATAORDCLI T5
INNER JOIN CLIENTIFORNITORI T6 ON (T5.NUMEROORDINE > 0 AND
T5.CODICECLIENTE=T6.CODICECLIFO AND T6.TIPO=1)
) ON (T1.NUMEROORDINE=T5.NUMEROORDINE)

;

Massimiliano Campagnoli ha scritto:

> Hi All,
> I know that db2 V7.2 is no more supported and nor OS/2 is supported
[quoted text clipped - 110 lines]
> Dump File:C:\SQLLIB\DB2\15611.000 Data:section1
> Dump File:C:\SQLLIB\DB2\15611.000 Data:dynamic buffer

Reply to this Message