If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Error help: SQLSTATE=51002 after running for abit

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-11-04, 09:22
ApoPen ApoPen is offline
Registered User
 
Join Date: Jul 2004
Location: Ottawa, Canada
Posts: 58
Exclamation Error help: SQLSTATE=51002 after running for abit

Using Db2 Version 8.2 and jdbc type 4 driver; after a period of time I get the following error:

DB2 SQL error: SQLCODE: -805, SQLSTATE: 51002, SQLERRMC: NULLID.SYSLH203 0X5359534C564C3031

All selects get this error once it occurs, after about an hour of operation.

A few questions if anyone can help:

1) What causes this error to happen all of a sudden?

2) I came across a post that said calling the following commands helps:

db2 bind @db2cli.bnd blocking all grant public
db2 bind @db2ubind.bnd blocking all grant public

If so, what is this doing and why do i need to do this?
Reply With Quote
  #2 (permalink)  
Old 11-11-04, 09:55
J Petruk J Petruk is offline
Registered User
 
Join Date: Mar 2004
Location: Toronto, ON, Canada
Posts: 513
Quote:
Originally Posted by ApoPen
Using Db2 Version 8.2 and jdbc type 4 driver; after a period of time I get the following error:

DB2 SQL error: SQLCODE: -805, SQLSTATE: 51002, SQLERRMC: NULLID.SYSLH203 0X5359534C564C3031

All selects get this error once it occurs, after about an hour of operation.

A few questions if anyone can help:

1) What causes this error to happen all of a sudden?

2) I came across a post that said calling the following commands helps:

db2 bind @db2cli.bnd blocking all grant public
db2 bind @db2ubind.bnd blocking all grant public

If so, what is this doing and why do i need to do this?
I used to have that same problem, not sure exactly why it takes so long to hit but at any rate the bind seemed to resolve it.

Binding creates the package on the target database. Packages contain sql statements and the bind operation generates corresponding access plans.

The other way to resolve is to grant the id the BINDADD priveledge, then it should auto-bind.

jono
__________________
--
Jonathan Petruk
DB2 Database Consultant
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On