We're at udb 8.2 64 bit on AIX 5.2 . I'm logged in as instance owner.

>db2advis -d dxdmis01 -i xxx1.sql -m IMCP -o xxx1.out

No catalog node table space name has been specified on the command line. Using default

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

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

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

SQLCABC = 136
SQLCODE = -805
SQLERRMC = NULLID.DB2ADVIO 0X5142316D564F4A55
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]

The question is why can't UDB find the package for db2advis?
I'm unaware of any prior steps required to run db2advis.

TIA,
Ruby

In addition:
db2 list packages for all | grep -i db2adv
DB2ADVCA NULLID INSGIPDM 8 Y 0 CS U
DB2ADVIN NULLID INSGIPDM 8 Y 0 CS U
DB2ADVIS NULLID INSGIPDM 2 Y 0 CS U

So where is DB2ADVIO ?

as of 8.2, don't know why, you must specify the user and password, I had the same problem.

yes..it ran successfully after supplying username passwd

try this

db2advis -d dbname -i your.sql -a username/passwd -o opfile

As an FYI:
Assume that one issued:
db2advis -d db-alias -i xxx1.sql -m IMCP -o xxx1.out -a user/password
One must tack on a -c tablespace to the command for the simulated catalog tablespace.

There is text in the db2advis system command info in the V8 info center (
http://publib.boulder.ibm.com/infoce...help/index.jsp) for the -c
option:

-c tablespace-name
Specifies the name of a table space (file name or directory) in which to
create the simulation catalog table space on the catalog database
partition group. The default is USERSPACE1.
It is recommended that the user create the table space employed for the
simulation instead of using the default USERSPACE1. In addition, the ALTER
TABLESPACE DROPPED TABLE RECOVERY OFF statement should be run on this
table space to improve the performance of the db2advis utility. When the
utility completes, turn the history back on for the table space. In a
partitioned database environment, the user-created table space must be
created only on the catalog partition of the database