use of or and parenthesis crashes db2
| Author |
Message |
|
lwese..
#1 / 15
|
 use of or and parenthesis crashes db2 Hi, I am using UDB7.1 on NT and am having problems with the following query crashing db2: 01:SELECT t1.CLASS, 02: t1.AMOUNT, t1.CODE, t1.DESCRIPTION, t1.FACTOR_TYPE, t1.GROUPING, t1.FACTOR_ID,t1.PLACEMENT, 03: t1.IS_ACTIVE, t1.IS_COLLECTED_IN_DOWNPAYMENT, t1.IS_DEFAULT,t1.IS_DISPLAYED, t1.REQUIRED, 04: t1.STATE, t1.HAZARD_GROUP 05:FROM everest.FACTOR t1, everest.STATE t0 06:WHERE t0.ABBREVIATION = t1.STATE 07:and (t0.ABBREVIATION = 'FL' OR t0.ABBREVIATION = '00') 08:AND t1.PLACEMENT= 'Schedule Credit' 09:AND t1.IS_ACTIVE = 'true' 10:AND t1.IS_ACTIVE = 'true' 11:AND t1.CLASS IN ('factor.WCFactor') Line 7 with the OR enclosed within parenthesis is the culprit.
Abbreviation is a not null column. I can get rid of the parenthesis
(different result set) or use the IN clause like any normal human would
and it works fine. The problem is our sql is automatically generated
by an object mapper so I have little control over how it wants to
generate the clauses. Both oracle and sqlserver will handle this
statement without any problem. I have tried UDB7.1 for NT, Linux, and
NT workstation with identical results. Not knowing much about DB2 I'm
sure I'm missing something concerning the environment? Could it have
anything to do with the optimizer and runstats?
I don't find the db2diag.log particularly helpfull not knowing what I'm
looking for. listings like: DIA3816C A severe internal processing error
has occurred. are not too instructive.
thanks for any suggestions,
Luke
Sent via Deja.com http://www.***.com/
Before you buy.
|
| Fri, 02 May 2003 03:00:00 GMT |
|
 |
|
Sailesh Krishnamurth
#2 / 15
|
use of or and parenthesis crashes db2
Luke> with the optimizer and runstats? I don't find the
Luke> db2diag.log particularly helpfull not knowing what I'm
Luke> looking for. listings like: DIA3816C A severe internal
Luke> processing error has occurred. are not too instructive.
How exactly do you identify it as a crash ? What is the error message
that you received. It will help if you post that. Also, if a db2agent
crashed, there should be stack trace files dumped along with the
db2diag.log ..
Try to rename your db2diag.log file just before you run your culprit
query .. then you should only be seeing entries corresponding to your
problems.
Also, you can try and set the DIAGLEVEL config parm to 4:
$ db2 update dbm cfg using DIAGLEVEL 4
$ db2stop
$ db2start
--
Toodle-pip
Sailesh Krishnamurthy
IBM Almaden Research Center
Ph: (408) 927-1913
|
| Fri, 02 May 2003 03:00:00 GMT |
|
|
|
Ed Vassie, BMC Software Lt
#3 / 15
|
use of or and parenthesis crashes db2 I agree with you. It should work. All I can think of is that DB2 has recognised that all your predicats
apart from t0.ABBREVIATION are on t1, and that t0.ABBREVIATION is
declared as equivalent to t1.STATE, and that DB2 is rewriting the query
to say (t1.STATE = 'FL' or t1.STATE = '00') and that this is not a
valid constrct for t1.STATE. (Or to put it another way, DB2 is
attempting predicate transitive closure on t1.STATE but t1.STATE does
not have the same format (data type and length) as t0.ABBREVIATION.)
If t0.ABBREVIATION is not fully identical with t1.STATE then the query
is unlikely to run as quickly as it could, even if the code worked.
Can you try to force your code generator to use t1. for all
predicates? This may fix the problem.
--
All information given is a personal opinion.
You are responsible for any changes to your environment.
Sent via Deja.com http://www.deja.com/
Before you buy.
|
| Sat, 03 May 2003 03:00:00 GMT |
|
|
|
lwese..
#4 / 15
|
use of or and parenthesis crashes db2 Quote: > How exactly do you identify it as a crash ? What is the error message
> that you received. It will help if you post that. Also, if a db2agent
> crashed, there should be stack trace files dumped along with the
> db2diag.log ..
Sailesh, By crashing I am referring to the client connection being dropped or
hung and the database stopping requiring a manual db2start.
Here is the exclusive DB2diag.log file under diag level 4
since this dosen't post very well I am emailing it seperately to you
2000-11-14-08.56.41.637000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
Error in agent servicing application with
coor_node:0000 ..
2000-11-14-08.56.41.730000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
Error in agent servicing application with
coor_agent_index:4d00
M.
2000-11-14-08.56.41.762000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
Error in agent servicing application with CLIENT PID:3333
38 338
2000-11-14-08.56.41.887000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
Error in agent servicing application with INBOUND APPLICATION ID:4431
3237 4641 3543 2e43 3030 412e 3030
D127FA5C.C00A.00
3131 3134 3136 3433 3331 1114164331
2000-11-14-08.56.42.027000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
Error in agent servicing application with INBOUND SEQUENCE NUMBER:3030
3031 0001
2000-11-14-08.56.42.137000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
Error in agent servicing application with OUTBOUND APPLICATION ID:
2000-11-14-08.56.42.230000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
Error in agent servicing application with OUTBOUND SEQUENCE NUMBER:
2000-11-14-08.56.42.324000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
Error in agent servicing application with AUTHORIZATION ID:4442 3241
444d 494e 0000 0000 0000 0000 DB2ADMIN........
0000 0000 0000 0000 0000 0000 0000
00 ...............
2000-11-14-08.56.42.465000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
Error in agent servicing application with PRODUCT SIGNATURE:5351 4c30
3730 3130 SQL07010
2000-11-14-08.56.42.574000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
Error in agent servicing application with APPLICATION NAME:6462 3262
702e 6578 65 db2bp.exe
2000-11-14-08.56.42.668000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:1 Database:EV23NT
value of ptr to db2ra_as_cb3000
a001 0.?.
2000-11-14-08.56.42.777000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:2 Database:EV23NT
contents of db2ra_as_cb7cfa 6b01 2808 1401 0000 0000 0000 0000
|k.(...........
0000 0000 0000 0000 3000 7301 0000
0000 ........0.s.....
0000 0000 6800 a001 0000 0000 0000
0000 ....h.?.........
5351 4c44 4232 5241 0200 0b00 0000 0000
SQLDB2RA........
0000 1000 0001 0000 5351 4c44 4232
5241 ........SQLDB2RA
0100 0300 0501 0122 0000 0000 1600
0000 ......."........
0200 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 3003 0000 0000 0000 0501
0112 ....0...........
0501 0122 0000 0501 0000 0000 0000
0000 ..."............
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0200 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 ........
2000-11-14-08.56.43.183000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:3 Database:EV23NT
value of ptr to ccb0000
0000 ....
2000-11-14-08.56.43.293000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:6 Database:EV23NT
contents of comm_handle5001 a001 3000 ec01 0000 0000 3000 7301
P.?.0......0.s.
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 ff7f
0000 ............?...
0c00 0000 0000 0000 0000 0000 b402
0000 ...............
0300 0000 0001 0000 ........
2000-11-14-08.56.43.637000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:7 Database:EV23NT
contents of comm_handle buffer001b 0000 0000 0000 5351
4c44 ........SQLD
2000-11-14-08.56.43.746000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
size of receive request area3003
0000 0...
2000-11-14-08.56.43.871000 Instance:DB2 Node:000
PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
base_sys_utilities sqleagnt_sigsegvh Probe:11 Database:EV23NT
contents of receive request area02b4 0000 3003 0000 a802 0000 5351
4c44 ...0......SQLD
4232 5241 e000 0000 0501 0200 0900 0a00 B2RA.......
...
8800 0000 0900 0080 fcfb 6b01 0000 0000 ?...
..€?k.....
0400 0040 0000 0000 0b00 0000 0400
c800 7301 0200 0000 0300 0040 d400 7301
0800 0000 0100 0040 d800 7301 0800
0100 0040 e000 7301 0800 0000 0100
e800 7301 0000 0000 0000 0000 0000 0000
.s.............
0000 0000 0500 00c0 0000 0000 f201
0000 ..............
0100 0040 f000 7301 0000 0000 0000
0000 0000 c900 0000 5351 4c43 3244
3031 .......SQLC2D01
4e55 4c4c 4944 2020 4141 4141 414b 4b50 NULLID
AAAAAKKP
5345 4c45 4354 2074 312e 434c 4153 532c SELECT
t1.CLASS,
2074 312e 414d 4f55 4e54 2c20 7431 2e43 t1.AMOUNT,
t1.C
4f44 452c 2074 312e 4445 5343 5249 5054 ODE,
t1.DESCRIPT
494f 4e2c 2074 312e 4641 4354 4f52 5f54 ION,
t1.FACTOR_T
5950 452c 2074 312e 4752 4f55 5049 4e47 YPE,
t1.GROUPING
2c20 7431 2e46 4143 544f 525f 4944 2c74 ,
t1.FACTOR_ID,t
312e 504c 4143 454d 454e 542c 2074 312e 1.PLACEMENT,
t1.
4953 5f41 4354 4956 452c 2074 312e 4953 IS_ACTIVE,
t1.IS
5f43 4f4c 4c45 4354 4544 5f49 4e5f 444f
_COLLECTED_IN_DO
574e 5041 594d 454e 542c 2074 312e 4953 WNPAYMENT,
t1.IS
5f44 4546 4155 4c54 2c20 7431 2e49 535f _DEFAULT,
t1.IS_
4449 5350 4c41 5945 442c 2074 312e 5245 DISPLAYED,
t1.RE
5155 4952 4544 2c20 7431 2e53 5441 5445 QUIRED,
t1.STATE
2c20 7431 2e48 415a 4152 445f 4752 4f55 ,
t1.HAZARD_GROU
5020 4652 4f4d 2065 7665 7265 7374 2e46 P FROM
everest.F
4143 544f 5220 7431 2c20 6576 6572 6573 ACTOR t1,
everes
742e 5354 4154 4520 7430 2057 4845 5245 t.STATE t0
WHERE
2074 302e 4142 4252 4556 4941 5449 4f4e
t0.ABBREVIATION
203d 2074 312e 5354 4154 4520 616e 6420 = t1.STATE
and
2874 302e 4142 4252 4556 4941 5449 4f4e
(t0.ABBREVIATION
203d 2027 464c 2720 4f52 2074 302e 4142 = 'FL' OR
t0.AB
4252 4556 4941 5449 4f4e 203d 2027 3030 BREVIATION
= '00
2729 2041 4e44 2074 312e 504c 4143 454d ') AND
t1.PLACEM
454e 543d 2027 5363 6865 6475 6c65 2043 ENT= 'Schedule
C
7265 6469 7427 2041 4e44 2074 312e 4953 redit' AND
t1.IS
5f41 4354 4956 4520 3d20 2774 7275 6527 _ACTIVE
= 'true'
2041 4e44 2074 312e 4953 5f41 4354 4956 AND
t1.IS_ACTIV
4520 3d20 2774 7275 6527 2041 4e44 2074 E = 'true' AND
t
312e 434c 4153 5320 494e 2028 2763 6f6d 1.CLASS IN
('com
2e6f 7765 6e73 756d 2e65 7665 7265
7374 .owensum.everest
2e66 6163 746f 722e 5743 4661 6374
6f72 .factor.WCFactor
2729 0000 0000 0000 0000 0000 0000
0000 ')..............
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000 0000 0000
0000 ................
0000 0000 0000 0000 0000
... read more »
|
| Sat, 03 May 2003 03:00:00 GMT |
|
|
|
David Sharp
#5 / 15
|
use of or and parenthesis crashes db2 If you could post the trap file, t310439.000, that would be helpful to. Cheers, David. Quote:
> > How exactly do you identify it as a crash ? What is the error message > > that you received. It will help if you post that. Also, if a db2agent > > crashed, there should be stack trace files dumped along with the > > db2diag.log .. > Sailesh,
> By crashing I am referring to the client connection being dropped or
> hung and the database stopping requiring a manual db2start.
> Here is the exclusive DB2diag.log file under diag level 4
> since this dosen't post very well I am emailing it seperately to you
> 2000-11-14-08.56.41.637000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
> Error in agent servicing application with
> coor_node:0000 ..
> 2000-11-14-08.56.41.730000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
> Error in agent servicing application with
> coor_agent_index:4d00
> M.
> 2000-11-14-08.56.41.762000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
> Error in agent servicing application with CLIENT PID:3333
> 38 338
> 2000-11-14-08.56.41.887000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
> Error in agent servicing application with INBOUND APPLICATION ID:4431
> 3237 4641 3543 2e43 3030 412e 3030
> D127FA5C.C00A.00
> 3131 3134 3136 3433 3331 1114164331
> 2000-11-14-08.56.42.027000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
> Error in agent servicing application with INBOUND SEQUENCE NUMBER:3030
> 3031 0001
> 2000-11-14-08.56.42.137000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
> Error in agent servicing application with OUTBOUND APPLICATION ID:
> 2000-11-14-08.56.42.230000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
> Error in agent servicing application with OUTBOUND SEQUENCE NUMBER:
> 2000-11-14-08.56.42.324000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
> Error in agent servicing application with AUTHORIZATION ID:4442 3241
> 444d 494e 0000 0000 0000 0000 DB2ADMIN........
> 0000 0000 0000 0000 0000 0000 0000
> 00 ...............
> 2000-11-14-08.56.42.465000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
> Error in agent servicing application with PRODUCT SIGNATURE:5351 4c30
> 3730 3130 SQL07010
> 2000-11-14-08.56.42.574000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
> Error in agent servicing application with APPLICATION NAME:6462 3262
> 702e 6578 65 db2bp.exe
> 2000-11-14-08.56.42.668000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:1 Database:EV23NT
> value of ptr to db2ra_as_cb3000
> a001 0. .
> 2000-11-14-08.56.42.777000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:2 Database:EV23NT
> contents of db2ra_as_cb7cfa 6b01 2808 1401 0000 0000 0000 0000
> |k.(...........
> 40f0 7301 3001 a001 0000 0000 0000 0000
> 0000 0000 0000 0000 3000 7301 0000
> 0000 ........0.s.....
> 0000 0000 6800 a001 0000 0000 0000
> 0000 ....h. .........
> 5351 4c44 4232 5241 0200 0b00 0000 0000
> SQLDB2RA........
> 0000 1000 0001 0000 5351 4c44 4232
> 5241 ........SQLDB2RA
> 0100 0300 0501 0122 0000 0000 1600
> 0000 ......."........
> 0200 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 3003 0000 0000 0000 0501
> 0112 ....0...........
> 0501 0122 0000 0501 0000 0000 0000
> 0000 ..."............
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0200 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 ........
> 2000-11-14-08.56.43.183000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:3 Database:EV23NT
> value of ptr to ccb0000
> 0000 ....
> 2000-11-14-08.56.43.293000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:6 Database:EV23NT
> contents of comm_handle5001 a001 3000 ec01 0000 0000 3000 7301
> P. .0......0.s.
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 0000
> 0000 ................
> 0000 0000 0000 0000 0000 0000 ff7f
> 0000 ............?...
> 0c00 0000 0000 0000 0000 0000 b402
> 0000 ...............
> 0300 0000 0001 0000 ........
> 2000-11-14-08.56.43.637000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:7 Database:EV23NT
> contents of comm_handle buffer001b 0000 0000 0000 5351
> 4c44 ........SQLD
> 2000-11-14-08.56.43.746000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:10 Database:EV23NT
> size of receive request area3003
> 0000 0...
> 2000-11-14-08.56.43.871000 Instance:DB2 Node:000
> PID:310(db2syscs.exe) TID:439 Appid:D127FA5C.BE0A.001114164258
> base_sys_utilities sqleagnt_sigsegvh Probe:11 Database:EV23NT
> contents of receive request area02b4 0000 3003 0000 a802 0000 5351
> 4c44 ...0......SQLD
> 4232 5241 e000 0000 0501 0200 0900 0a00 B2RA.......
> ...
> 8800 0000 0900 0080 fcfb 6b01 0000 0000 ?...
> ..€?k.....
> 0400 0040 0000 0000 0b00 0000 0400
> c800 7301 0200 0000 0300 0040 d400 7301
> 0800 0000 0100 0040 d800 7301 0800
> 0100 0040 e000 7301 0800 0000 0100
> e800 7301 0000 0000 0000 0000 0000 0000
> .s.............
> 0000 0000 0500 00c0 0000 0000 f201
> 0000 ..............
> 0100 0040 f000 7301 0000 0000 0000
> 0000 0000 c900 0000 5351 4c43 3244
> 3031 .......SQLC2D01
> 4e55 4c4c 4944 2020 4141 4141 414b 4b50 NULLID
> AAAAAKKP
> 5345 4c45 4354 2074 312e 434c 4153 532c SELECT
> t1.CLASS,
> 2074 312e 414d 4f55 4e54 2c20 7431 2e43 t1.AMOUNT,
> t1.C
> 4f44 452c 2074 312e 4445 5343 5249 5054 ODE,
> t1.DESCRIPT
> 494f 4e2c 2074 312e 4641 4354 4f52 5f54 ION,
> t1.FACTOR_T
> 5950 452c 2074 312e 4752 4f55 5049 4e47 YPE,
> t1.GROUPING
> 2c20 7431 2e46 4143 544f 525f 4944 2c74 ,
> t1.FACTOR_ID,t
> 312e 504c 4143 454d 454e 542c 2074 312e 1.PLACEMENT,
> t1.
> 4953 5f41 4354 4956 452c 2074 312e 4953 IS_ACTIVE,
> t1.IS
> 5f43 4f4c 4c45 4354 4544 5f49 4e5f 444f
> _COLLECTED_IN_DO
> 574e 5041 594d 454e 542c 2074 312e 4953 WNPAYMENT,
> t1.IS
> 5f44 4546 4155 4c54 2c20 7431 2e49 535f _DEFAULT,
> t1.IS_
> 4449 5350 4c41 5945 442c 2074 312e 5245 DISPLAYED,
> t1.RE
> 5155 4952 4544 2c20 7431 2e53 5441 5445 QUIRED,
> t1.STATE
> 2c20 7431 2e48 415a 4152 445f 4752 4f55 ,
> t1.HAZARD_GROU
> 5020 4652 4f4d 2065 7665 7265 7374 2e46 P FROM
> everest.F
> 4143 544f 5220 7431 2c20 6576 6572 6573 ACTOR t1,
> everes
> 742e 5354 4154 4520 7430 2057 4845 5245 t.STATE t0
> WHERE
> 2074 302e 4142 4252 4556 4941 5449 4f4e
> t0.ABBREVIATION
> 203d 2074 312e 5354 4154 4520 616e 6420 = t1.STATE
> and
> 2874 302e 4142 4252 4556 4941 5449 4f4e
> (t0.ABBREVIATION
> 203d 2027 464c 2720 4f52 2074 302e 4142 = 'FL' OR
> t0.AB
> 4252 4556 4941 5449 4f4e 203d 2027 3030 BREVIATION
> = '00
> 2729 2041 4e44 2074 312e 504c 4143 454d ') AND
> t1.PLACEM
> 454e 543d 2027 5363 6865 6475 6c65 2043 ENT= 'Schedule
> C
> 7265 6469 7427 2041 4e44 2074 312e 4953 redit' AND
> t1.IS
> 5f41 4354 4956 4520 3d20 2774 7275 6527 _ACTIVE
> = 'true'
... read more »
|
| Sat, 03 May 2003 03:00:00 GMT |
|
|
|
lwese..
#6 / 15
|
use of or and parenthesis crashes db2
Quote: > If you could post the trap file, t310439.000, that would be helpful
to.
> Cheers,
> David.
David, Here is the trap file. Where can I learn how to read one of these things? 26~2000-11-14-08.56.45.6520008~016B8B585~SQLCA136~SQLCA
?
SQL07010 0000026~2000-11-14-
08.56.45.6990008~0173003C5~DB2RA140~SQLDB2RA
08.56.45.9490008~016D56707~CREATOR8~NULLID 26~2000-11-14-
08.56.45.9800008~016D568E7~PACKAGE8~SQLC2D0126~2000-11-14-
08.56.46.0270008~0116E24412~REQUEST TYPE4~ 26~2000-11-14-
08.56.46.0740008~016B66B019~Recursive dump_sect4~ 26~2000-11-14-
4Um €3 0Wm N3 N3 ?k :
?
?
? /A
DB2ADMIN p p NYNND0B0N DDDDDD1
DB2ADMIN BNR N 26~2000-11-14-
08.56.46.1680008~016D573022~USED_IN_UOW BIT
08.56.46.2150008~01B1AC6014~SECTION NUMBER2~ 26~2000-11-14-
08.56.46.2620008~01B1AC3817~SECTION DIR ENTRY56~ |3 !
?" ???? 26~2000-11-14-
08.56.46.3080008~01B1B37C11~cursor name9~SQLCUR20126~2000-11-14-
08.56.46.3400008~0122F7888~cache cb152~`"
08.56.47.2930008~0121CD0012~section stmt498~SELECT t1.CLASS, t1.AMOUNT,
t1.CODE, t1.DESCRIPTION, t1.FACTOR_TYPE, t1.GROUPING,
t1.FACTOR_ID,t1.PLACEMENT, t1.IS_ACTIVE,
t1.IS_COLLECTED_IN_DOWNPAYMENT, t1.IS_DEFAULT, t1.IS_DISPLAYED,
t1.REQUIRED, t1.STATE, t1.HAZARD_GROUP FROM everest.FACTOR t1,
everest.STATE t0 WHERE t0.ABBREVIATION = t1.STATE and (t0.ABBREVIATION
= 'FL' OR t0.ABBREVIATION = '00') AND t1.PLACEMENT= 'Schedule Credit'
AND t1.IS_ACTIVE = 'true' AND t1.IS_ACTIVE = 'true' AND t1.CLASS IN
('com.owensum.everest.factor.WCFactor')26~2000-11-14-
08.56.47.5580008~016D403013~SQLD_AGENT_CB76~ ?!
€ 0 e[m 26~2000-11-14-
08.56.47.5900008~0174C0B012~SQLD_TRAN_CB328~`€?
t t
26~2000-11-14-
08.56.48.8240008~0174C9B08~SQLD_CCB760~
T t X?~
€ R t t?~
€ ^ f
k ????
t?? ?? t t
?
? ' 3? 0 t
0 ?? ?t
08.56.48.9020008~0174E6408~SQLD_CCB760~ %
& ????
? % % E?
' % 3? 0 t
0 e?!
??t
26~2000-11-14-
08.56.48.9800008~016D40907~SQLI_CB872~0
' 3? 0
t
t $?t
U
??? ??? ???
€ t 26~2000-11-14-
08.56.49.0270008~20021F308~SQLE_ACB1416~SQLEACB DB2SXAUT
?
? ? h
DB2ADMIN S RL
6 ?
DB2ADMIN.FACTOR
? 3k :?l :SN EV23NT
Quote: > EV23NT
D127FA5C.C00A.001114164331 0001 M M N # ?€?
7
)T ;X
N
7
N
LWESEMA
D127FA5C.BE0A.001114164258 db2bp.exe
t e? R
DDm ? h
` 26~2000-11-
14-08.56.49.1050008~0174BAA08~SQLP_ACB264~SQLPACB 0 } 0€?
????????????
26~2000-11-14-
08.56.49.1520008~01AC80309~SQLP_DBCB31040~SQLPDBCB EV23NT D:\DB2
\NODE0000\SQL00001
\SQLOGDIR\
p?
0 p 0t/< ??e9 2 ?? ?? ?? ??
?? ?? 9?e9
?
? :
?e9????
???????? } ;
???????????????? ??
?? 2
???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
???? ???? ???? ???? ???? ???? ???? ???? ????
????
????
?
}
:
<
SQLCA
?
SQL07010 0
? < ` # ( d?
? ,
? H
? ?
d ?
? 0
< P D
\ , t 4
€ ?
$
D ? ?
? \
L
d H H
? ? ? `
? X ? $
?
? T
D
p ?
D € `
P
?
? <
(
| `
? ?
?
X
8 8
p T
8 ? h
$
t ? h
D | ? l
`
?
D
e 4
... read more »
|
| Sun, 04 May 2003 03:00:00 GMT |
|
|
|
lwese..
#7 / 15
|
use of or and parenthesis crashes db2
Quote: > I agree with you. It should work. > All I can think of is that DB2 has recognised that all your predicats
> apart from t0.ABBREVIATION are on t1, and that t0.ABBREVIATION is
> declared as equivalent to t1.STATE, and that DB2 is rewriting the
query
> to say (t1.STATE = 'FL' or t1.STATE = '00') and that this is not a
> valid constrct for t1.STATE. (Or to put it another way, DB2 is
> attempting predicate transitive closure on t1.STATE but t1.STATE does
> not have the same format (data type and length) as t0.ABBREVIATION.)
> If t0.ABBREVIATION is not fully identical with t1.STATE then the query
> is unlikely to run as quickly as it could, even if the code worked.
> Can you try to force your code generator to use t1. for all
> predicates? This may fix the problem.
> --
> All information given is a personal opinion.
> You are responsible for any changes to your environment.
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Ed- t0.abbreviation and t1.state are both varchar(2) not null
Sent via Deja.com http://www.deja.com/
Before you buy.
|
| Sun, 04 May 2003 03:00:00 GMT |
|
|
|
David Sharp
#8 / 15
|
use of or and parenthesis crashes db2 Hi, It looks like you posted the dump file (310439.000), not the trap file. As a collegue pointed out, I gave the wrong name for a trap file on nt. On nt, I think it will be called 310439.TRP (but I could be wrong). In any case, the trap file should be an ascii text file that shows the registers and the calling stack at the time of the crash. FYI, the dump file you posted is a binary file. If you open a ticket with
the db2 service (you should!), they will ask for all your info, including
this dump file. They can format it for analysis.
Hope this helps,
David.
Quote:
> > If you could post the trap file, t310439.000, that would be helpful > to. > > Cheers, > > David. > David, Here is the trap file. Where can I learn how to read one of
> these things?
> 26~2000-11-14-08.56.45.6520008~016B8B585~SQLCA136~SQLCA
> ?
> SQL07010 0000026~2000-11-14-
> 08.56.45.6990008~0173003C5~DB2RA140~SQLDB2RA
> 08.56.45.9490008~016D56707~CREATOR8~NULLID 26~2000-11-14-
> 08.56.45.9800008~016D568E7~PACKAGE8~SQLC2D0126~2000-11-14-
> 08.56.46.0270008~0116E24412~REQUEST TYPE4~ 26~2000-11-14-
> 08.56.46.0740008~016B66B019~Recursive dump_sect4~ 26~2000-11-14-
> 4Um €3 0Wm N3 N3 ?k :
> ?
> ?
> ? /A
> DB2ADMIN p p NYNND0B0N DDDDDD1
> DB2ADMIN BNR N 26~2000-11-14-
> 08.56.46.1680008~016D573022~USED_IN_UOW BIT
> 08.56.46.2150008~01B1AC6014~SECTION NUMBER2~ 26~2000-11-14-
> 08.56.46.2620008~01B1AC3817~SECTION DIR ENTRY56~ |3 !
> ?" ???? 26~2000-11-14-
> 08.56.46.3080008~01B1B37C11~cursor name9~SQLCUR20126~2000-11-14-
> 08.56.46.3400008~0122F7888~cache cb152~`"
> 08.56.47.2930008~0121CD0012~section stmt498~SELECT t1.CLASS, t1.AMOUNT,
> t1.CODE, t1.DESCRIPTION, t1.FACTOR_TYPE, t1.GROUPING,
> t1.FACTOR_ID,t1.PLACEMENT, t1.IS_ACTIVE,
> t1.IS_COLLECTED_IN_DOWNPAYMENT, t1.IS_DEFAULT, t1.IS_DISPLAYED,
> t1.REQUIRED, t1.STATE, t1.HAZARD_GROUP FROM everest.FACTOR t1,
> everest.STATE t0 WHERE t0.ABBREVIATION = t1.STATE and (t0.ABBREVIATION
> = 'FL' OR t0.ABBREVIATION = '00') AND t1.PLACEMENT= 'Schedule Credit'
> AND t1.IS_ACTIVE = 'true' AND t1.IS_ACTIVE = 'true' AND t1.CLASS IN
> ('com.owensum.everest.factor.WCFactor')26~2000-11-14-
> 08.56.47.5580008~016D403013~SQLD_AGENT_CB76~ ?!
> € 0 e[m 26~2000-11-14-
> 08.56.47.5900008~0174C0B012~SQLD_TRAN_CB328~`€?
> t t
> 26~2000-11-14-
> 08.56.48.8240008~0174C9B08~SQLD_CCB760~
> T t X?~
> € R t t?~
> € ^
|
| Sun, 04 May 2003 03:00:00 GMT |
|
|
|
lwese..
#9 / 15
|
use of or and parenthesis crashes db2 Well, the TRP file is binary also. (a difference in 7.1?) Here is the first few characters
\SQLLIB\bin\db2syscs.exe Can you point me towards DB2 service and some idea of what it could cost
Our shop is a member of the Developer Partner program.
thanks, Luke
Quote: > Hi, > It looks like you posted the dump file (310439.000), not the trap file. As > a collegue pointed out, I gave the wrong name for a trap file on nt. On nt, > I think it will be called 310439.TRP (but I could be wrong). In any case, > the trap file should be an ascii text file that shows the registers and the > calling stack at the time of the crash. > FYI, the dump file you posted is a binary file. If you open a ticket
with
> the db2 service (you should!), they will ask for all your info,
including
> this dump file. They can format it for analysis.
> Hope this helps,
> David.
Sent via Deja.com http://www.deja.com/ Before you buy.
|
| Sun, 04 May 2003 03:00:00 GMT |
|
|
|
David Sharp
#10 / 15
|
use of or and parenthesis crashes db2 Hi, Sorry I can't help out more, can anyone else comment on: - how do you format a (binary) nt trap file - how do you find out about getting db2 service help David.
Quote:
> Well, the TRP file is binary also. (a difference in 7.1?) Here is the > first few characters
> \SQLLIB\bin\db2syscs.exe > Can you point me towards DB2 service and some idea of what it could cost
> Our shop is a member of the Developer Partner program.
> thanks, Luke
> > Hi,
> > It looks like you posted the dump file (310439.000), not the trap
> file. As
> > a collegue pointed out, I gave the wrong name for a trap file on nt.
> On nt,
> > I think it will be called 310439.TRP (but I could be wrong). In any
> case,
> > the trap file should be an ascii text file that shows the registers
> and the
> > calling stack at the time of the crash.
> > FYI, the dump file you posted is a binary file. If you open a ticket
> with
> > the db2 service (you should!), they will ask for all your info,
> including
> > this dump file. They can format it for analysis.
> > Hope this helps,
> > David.
> Sent via Deja.com http://www.deja.com/
> Before you buy.
|
| Mon, 05 May 2003 03:00:00 GMT |
|
|
|
Bob Harbu
#11 / 15
|
use of or and parenthesis crashes db2 Hmmm.. 1. I was sure that trap files were always ASCII and not binary - I thought
only section dumps were binary ... do not know on that one.
2. To contact DB2 UDB service in North America, you call 1-800-237-5511
Good luck!
Quote:
> Hi, > Sorry I can't help out more, can anyone else comment on: > - how do you format a (binary) nt trap file > - how do you find out about getting db2 service help > David.
> > Well, the TRP file is binary also. (a difference in 7.1?) Here is the
> > first few characters
> > \SQLLIB\bin\db2syscs.exe
> > Can you point me towards DB2 service and some idea of what it could cost
> > Our shop is a member of the Developer Partner program.
> > thanks, Luke
> > > Hi,
> > > It looks like you posted the dump file (310439.000), not the trap
> > file. As
> > > a collegue pointed out, I gave the wrong name for a trap file on nt.
> > On nt,
> > > I think it will be called 310439.TRP (but I could be wrong). In any
> > case,
> > > the trap file should be an ascii text file that shows the registers
> > and the
> > > calling stack at the time of the crash.
> > > FYI, the dump file you posted is a binary file. If you open a ticket
> > with
> > > the db2 service (you should!), they will ask for all your info,
> > including
> > > this dump file. They can format it for analysis.
-- Bob Harbus
DB2 UDB Data Management Consulting Services - IBM Toronto
|
| Mon, 05 May 2003 03:00:00 GMT |
|
|
|
Larry Menar
#12 / 15
|
use of or and parenthesis crashes db2 I believe the tool to format trap files on NT is "db2xprt". Quote:
> Hmmm.. > 1. I was sure that trap files were always ASCII and not binary - I thought
> only section dumps were binary ... do not know on that one.
> 2. To contact DB2 UDB service in North America, you call 1-800-237-5511
> Good luck!
> > Hi,
> > Sorry I can't help out more, can anyone else comment on:
> > - how do you format a (binary) nt trap file
> > - how do you find out about getting db2 service help
> > David.
> > > Well, the TRP file is binary also. (a difference in 7.1?) Here is the
> > > first few characters
> > > \SQLLIB\bin\db2syscs.exe
> > > Can you point me towards DB2 service and some idea of what it could cost
> > > Our shop is a member of the Developer Partner program.
> > > thanks, Luke
> > > > Hi,
> > > > It looks like you posted the dump file (310439.000), not the trap
> > > file. As
> > > > a collegue pointed out, I gave the wrong name for a trap file on nt.
> > > On nt,
> > > > I think it will be called 310439.TRP (but I could be wrong). In any
> > > case,
> > > > the trap file should be an ascii text file that shows the registers
> > > and the
> > > > calling stack at the time of the crash.
> > > > FYI, the dump file you posted is a binary file. If you open a ticket
> > > with
> > > > the db2 service (you should!), they will ask for all your info,
> > > including
> > > > this dump file. They can format it for analysis.
> --
> Bob Harbus
> DB2 UDB Data Management Consulting Services - IBM Toronto
-- Larry Menard IBM Workstation Database (DB2) Performance Team Defender of Geese and of all things Natural
|
| Mon, 05 May 2003 03:00:00 GMT |
|
|
|
Bob Harbu
#13 / 15
|
use of or and parenthesis crashes db2 Thanks for the information Larry - appreciate it...I would assume this is available only to service personnel as I did not see it installed on my machine. Quote:
> I believe the tool to format trap files on NT is "db2xprt".
> > Hmmm..
> > 1. I was sure that trap files were always ASCII and not binary - I thought
> > only section dumps were binary ... do not know on that one.
> > 2. To contact DB2 UDB service in North America, you call 1-800-237-5511
> > Good luck!
> > > Hi,
> > > Sorry I can't help out more, can anyone else comment on:
> > > - how do you format a (binary) nt trap file
> > > - how do you find out about getting db2 service help
> > > David.
> > > > Well, the TRP file is binary also. (a difference in 7.1?) Here is the
> > > > first few characters
> > > > \SQLLIB\bin\db2syscs.exe
> > > > Can you point me towards DB2 service and some idea of what it could cost
> > > > Our shop is a member of the Developer Partner program.
> > > > thanks, Luke
> > > > > Hi,
> > > > > It looks like you posted the dump file (310439.000), not the trap
> > > > file. As
> > > > > a collegue pointed out, I gave the wrong name for a trap file on nt.
> > > > On nt,
> > > > > I think it will be called 310439.TRP (but I could be wrong). In any
> > > > case,
> > > > > the trap file should be an ascii text file that shows the registers
> > > > and the
> > > > > calling stack at the time of the crash.
> > > > > FYI, the dump file you posted is a binary file. If you open a ticket
> > > > with
> > > > > the db2 service (you should!), they will ask for all your info,
> > > > including
> > > > > this dump file. They can format it for analysis.
-- Bob Harbus
DB2 UDB Data Management Consulting Services - IBM Toronto
|
| Mon, 05 May 2003 03:00:00 GMT |
|
|
|
Larry Menar
#14 / 15
|
use of or and parenthesis crashes db2 Sorry, I didn't realize that it was an Internal tool. ;-) Quote:
> Thanks for the information Larry - appreciate it...I would assume this is > available only to service personnel as I did not see it installed on my machine.
> > I believe the tool to format trap files on NT is "db2xprt".
> > > Hmmm..
> > > 1. I was sure that trap files were always ASCII and not binary - I thought
> > > only section dumps were binary ... do not know on that one.
> > > 2. To contact DB2 UDB service in North America, you call 1-800-237-5511
> > > Good luck!
> > > > Hi,
> > > > Sorry I can't help out more, can anyone else comment on:
> > > > - how do you format a (binary) nt trap file
> > > > - how do you find out about getting db2 service help
> > > > David.
> > > > > Well, the TRP file is binary also. (a difference in 7.1?) Here is the
> > > > > first few characters
> > > > > \SQLLIB\bin\db2syscs.exe
> > > > > Can you point me towards DB2 service and some idea of what it could cost
> > > > > Our shop is a member of the Developer Partner program.
> > > > > thanks, Luke
> > > > > > Hi,
> > > > > > It looks like you posted the dump file (310439.000), not the trap
> > > > > file. As
> > > > > > a collegue pointed out, I gave the wrong name for a trap file on nt.
> > > > > On nt,
> > > > > > I think it will be called 310439.TRP (but I could be wrong). In any
> > > > > case,
> > > > > > the trap file should be an ascii text file that shows the registers
> > > > > and the
> > > > > > calling stack at the time of the crash.
> > > > > > FYI, the dump file you posted is a binary file. If you open a ticket
> > > > > with
> > > > > > the db2 service (you should!), they will ask for all your info,
> > > > > including
> > > > > > this dump file. They can format it for analysis.
> --
> Bob Harbus
> DB2 UDB Data Management Consulting Services - IBM Toronto
-- Larry Menard IBM Workstation Database (DB2) Performance Team Defender of Geese and of all things Natural
|
| Tue, 06 May 2003 03:00:00 GMT |
|
|
|
Bob Harbu
#15 / 15
|
use of or and parenthesis crashes db2 I would see no reason why it would not be external as on AIX the trap files are in ASCII readable form - oh well :]=) Quote:
> Sorry, I didn't realize that it was an Internal tool. ;-)
> > Thanks for the information Larry - appreciate it...I would assume this is
> > available only to service personnel as I did not see it installed on my machine.
> > > I believe the tool to format trap files on NT is "db2xprt".
> > > > Hmmm..
> > > > 1. I was sure that trap files were always ASCII and not binary - I thought
> > > > only section dumps were binary ... do not know on that one.
> > > > 2. To contact DB2 UDB service in North America, you call 1-800-237-5511
> > > > Good luck!
> > > > > Hi,
> > > > > Sorry I can't help out more, can anyone else comment on:
> > > > > - how do you format a (binary) nt trap file
> > > > > - how do you find out about getting db2 service help
> > > > > David.
> > > > > > Well, the TRP file is binary also. (a difference in 7.1?) Here is the
> > > > > > first few characters
> > > > > > \SQLLIB\bin\db2syscs.exe
> > > > > > Can you point me towards DB2 service and some idea of what it could cost
> > > > > > Our shop is a member of the Developer Partner program.
> > > > > > thanks, Luke
> > > > > > > Hi,
> > > > > > > It looks like you posted the dump file (310439.000), not the trap
> > > > > > file. As
> > > > > > > a collegue pointed out, I gave the wrong name for a trap file on nt.
> > > > > > On nt,
> > > > > > > I think it will be called 310439.TRP (but I could be wrong). In any
> > > > > > case,
> > > > > > > the trap file should be an ascii text file that shows the registers
> > > > > > and the
> > > > > > > calling stack at the time of the crash.
> > > > > > > FYI, the dump file you posted is a binary file. If you open a ticket
> > > > > > with
> > > > > > > the db2 service (you should!), they will ask for all your info,
> > > > > > including
> > > > > > > this dump file. They can format it for analysis.
> > --
> > Bob Harbus
> > DB2 UDB Data Management Consulting Services - IBM Toronto
> --
> Larry Menard
> IBM Workstation Database (DB2) Performance Team
> Defender of Geese and of all things Natural
-- Bob Harbus
DB2 UDB Data Management Consulting Services - IBM Toronto
|
| Wed, 07 May 2003 03:00:00 GMT |
|
| |
|
