Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / March 2007

Tip: Looking for answers? Try searching our database.

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

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
rawu - 20 Mar 2007 03:39 GMT
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 .
Serge Rielau - 23 Mar 2007 15:13 GMT
> last week , i get my db version from DB2/AIX64 8.1.10 down to DB2/
> AIX64 8.1.5  .
[quoted text clipped - 14 lines]
> 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
Signature

Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

rawu - 27 Mar 2007 09:21 GMT
> > last week , i get my db version from DB2/AIX64 8.1.10 down to DB2/
> > AIX64 8.1.5  .
[quoted text clipped - 23 lines]
> 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.
Serge Rielau - 27 Mar 2007 14:29 GMT
> 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
Signature

Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.