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

"SQL0901N The SQL statement failed because of a non-severe error . " after degrade

P: n/a
last week , i get my db version from DB2/AIX64 8.1.10 down to DB2/
AIX64 8.1.5 .

After that , a application called "CalRate" has something wrong .

when it tries to open a cursor , it presents a error : SQL0901N The
SQL statement failed because of a non-severe error . Subsequent SQL
statements can be processed . (Reason "sqlriResolveOpFunc: invalid
opcode 0x1be at offset 14A0:0") SQLSTATE=58004

when i recompile this application , i receive a error : SQL0901N The
SQL statement failed because of a non-severe error . Subsequent SQL
statements can be processed . (Reason "section missing LRU entry!")
SQLSTATE=58004

i search for it .. and i get the information that it will be ok by
upgrading db version . but in my situation , i have to use 8.1.5 to
test this application .

Any help will be appreciated .

Mar 20 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
rawu wrote:
last week , i get my db version from DB2/AIX64 8.1.10 down to DB2/
AIX64 8.1.5 .

After that , a application called "CalRate" has something wrong .

when it tries to open a cursor , it presents a error : SQL0901N The
SQL statement failed because of a non-severe error . Subsequent SQL
statements can be processed . (Reason "sqlriResolveOpFunc: invalid
opcode 0x1be at offset 14A0:0") SQLSTATE=58004

when i recompile this application , i receive a error : SQL0901N The
SQL statement failed because of a non-severe error . Subsequent SQL
statements can be processed . (Reason "section missing LRU entry!")
SQLSTATE=58004

i search for it .. and i get the information that it will be ok by
upgrading db version . but in my situation , i have to use 8.1.5 to
test this application .
Open PMR with support. If need be you may be able to get a patch on V8.1.5.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Mar 23 '07 #2

P: n/a
On 3月23日, 下午10时13分, Serge Rielau <srie...@ca.ibm.comwrote:
rawu wrote:
last week , i get my db version from DB2/AIX64 8.1.10 down to DB2/
AIX64 8.1.5 .
After that , a application called "CalRate" has something wrong .
when it tries to open a cursor , it presents a error : SQL0901N The
SQL statement failed because of a non-severe error . Subsequent SQL
statements can be processed . (Reason "sqlriResolveOpFunc: invalid
opcode 0x1be at offset 14A0:0") SQLSTATE=58004
when i recompile this application , i receive a error : SQL0901N The
SQL statement failed because of a non-severe error . Subsequent SQL
statements can be processed . (Reason "section missing LRU entry!")
SQLSTATE=58004
i search for it .. and i get the information that it will be ok by
upgrading db version . but in my situation , i have to use 8.1.5 to
test this application .

Open PMR with support. If need be you may be able to get a patch on V8.1.5.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
it turns out to be all right after i shutdown most of applications.
a IBM guy said maybe it's about the size of statment heap .
it's to large to assign .
anyway , it's ok now . thanks for your words.

Mar 27 '07 #3

P: n/a
rawu wrote:
it turns out to be all right after i shutdown most of applications.
a IBM guy said maybe it's about the size of statment heap .
it's to large to assign .
anyway , it's ok now . thanks for your words.
A -901 is never alright. It's DB2 version of an emergency break.
If it's not reported to support with the right context we can't fix it.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Mar 27 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.