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

db2advis in DB2 Version 8 Fixpax 7

P: n/a
Is anyone else having trouble using db2advis in V8 Fixpak 7?

I am getting this:

================================================== ===================
Using user id as default schema name. Use -n option to specify schema

SQL0805N Package "NULLID.DB2ADVIO 0X32415872414E4955" was not found.
SQLSTATE=51002

*************************************
* CONTENTS OF SQLCA *
*************************************

SQLCABC = 136
SQLCODE = -805
SQLERRMC = NULLID.DB2ADVIO 0X32415872414E4955
SQLERRP = SQLRACFI
sqlerrd[0] = 2148663405
sqlerrd[1] = 0
sqlerrd[2] = 0
sqlerrd[3] = 0
sqlerrd[4] = 0
sqlerrd[5] = 0
SQLWARN =
SQLSTATE = 51002
Critical SQLCODE. Exiting db2advis ...

0 solutions were evaluated by the advisor

exiting with error code [-805]
================================================== ========
Nov 12 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
In article <41**************************@posting.google.com >, Matthew
Dauphinee (md********@performics.com) says...
Is anyone else having trouble using db2advis in V8 Fixpak 7?

I am getting this:

================================================== ===================
Using user id as default schema name. Use -n option to specify schema

SQL0805N Package "NULLID.DB2ADVIO 0X32415872414E4955" was not found.
SQLSTATE=51002


Is this a pre-fp7 database? If so, you probably didn't run the
db2updv8 command against it.
Nov 12 '05 #2

P: n/a
Ian
Gert van der Kooij wrote:
In article <41**************************@posting.google.com >, Matthew
Dauphinee (md********@performics.com) says...
Is anyone else having trouble using db2advis in V8 Fixpak 7?

I am getting this:

================================================ =====================
Using user id as default schema name. Use -n option to specify schema

SQL0805N Package "NULLID.DB2ADVIO 0X32415872414E4955" was not found.
SQLSTATE=51002

Is this a pre-fp7 database? If so, you probably didn't run the
db2updv8 command against it.


I didn't think you have to run db2updv8 (I didn't), but there was a
new bind file (db2schema.bnd) that has to be bound in order to support
many of the new features in stinger. This is described in the
FixpackReadme.txt.

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----
Nov 12 '05 #3

P: n/a

I didn't think you have to run db2updv8 (I didn't), but there was a
new bind file (db2schema.bnd) that has to be bound in order to support
many of the new features in stinger. This is described in the
FixpackReadme.txt.


Thanks, I missed it.
Nov 12 '05 #4

P: n/a
I did run the BINDs for @db2ubind.lst, @db2cli.lst and db2schema.bnd.
I did however find that db2updv8 command in the release notes but it
was unclear if it was needed to go from v8fix6 to v8fix7, or from v7
to v8.

Thanks for the responses but I think i did as the FixpackReadme said.

Gert van der Kooij <ge**@invalid.nl> wrote in message news:<MP************************@news.xs4all.nl>.. .

I didn't think you have to run db2updv8 (I didn't), but there was a
new bind file (db2schema.bnd) that has to be bound in order to support
many of the new features in stinger. This is described in the
FixpackReadme.txt.


Thanks, I missed it.

Nov 12 '05 #5

P: n/a
I called DB2 support and this is in fact a bug with databases that
existed while in Fixpak 6 and are used after applying Fixpak 7. The
installation on Linux was incomplete. Their developers are looking
into it.

md********@performics.com (Matthew Dauphinee) wrote in message news:<41**************************@posting.google. com>...
I did run the BINDs for @db2ubind.lst, @db2cli.lst and db2schema.bnd.
I did however find that db2updv8 command in the release notes but it
was unclear if it was needed to go from v8fix6 to v8fix7, or from v7
to v8.

Thanks for the responses but I think i did as the FixpackReadme said.

Gert van der Kooij <ge**@invalid.nl> wrote in message news:<MP************************@news.xs4all.nl>.. .

I didn't think you have to run db2updv8 (I didn't), but there was a
new bind file (db2schema.bnd) that has to be bound in order to support
many of the new features in stinger. This is described in the
FixpackReadme.txt.


Thanks, I missed it.

Nov 12 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.