Hi everybody,
About this error I got on the database (posted below). For what I could
make out with db2 support is that this query is building a very long
access plan. It's really long. The workaround db2 tech suggested are to
lower the optimization level and to disable hash joins. Since this
database is a datawarehouse production one, I think it will have a very
heavy impact on performance. So I didn't do it. Instead, I will work on
re-writing the query, and see if data can be denormalized or summarized
before, create new indexes, etc.
If anyone can think of anything else, I'll be more grateful than what I am
already.
Thanks again,
Ricardo
"Richard" <db2udbdba-ezmlmshield-x50036223.[Email address protected]
06/25/2007 05:18 PM
To
"LazyDBA Discussion" <[Email address protected]
cc
Subject
Re: ADM0001C A severe error has occurred.
-901 looks like a timeout. Should also be a related 68 code
NOTICE TO RECIPIENT: If you are not the intended recipient of this
e-mail, you are prohibited from sharing, copying, or otherwise using or
disclosing its contents. If you have received this e-mail in error,
please notify the sender immediately by reply e-mail and permanently
delete this e-mail and any attachments without reading, forwarding or
saving them. Thank you.
"Ricardo Ortega "
<db2udbdba-ezmlmshield-x88877887.[Email address protected]
06/25/2007 04:21 PM
To
"LazyDBA Discussion" <[Email address protected]
cc
Subject
ADM0001C A severe error has occurred.
Hi everybody,
Today I found this entry in instance.nfy (production database):
ADM0001C A severe error has occurred. Examine the administration
notification log and contact IBM Support if necessary.
So, as instructed in the error itself I went to the db2diag.log to see
what I could find there and I found this:
DIA8118 Failure processing SQL statement.
ZRC=0x8012007E
PID:1564684 TID:1 Node:000 Title: SQLCA
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 45
sqlerrmc: sqlridummy: invalid opcode 6 at offset 21a8:0
sqlerrp : sqlridum
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
followed by dump information.
I've been trying to find information about this error and I have been
unable to. Does anyone knows what this means or could guide on how to find
out?
Thanks in advance,
Ricardo
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
DB2 & UDB email list listserv db2-l LazyDBA home page