db2advis fails on DB2 UDB V8.1 FixPack 10

[g***@vsnl.net]

I'm trying to use db2advis and it does not work. The errors received are as follows:

Using user id as default schema name. Use -n option to specify schema
CALL SYSPROC.GET_DBSIZE_INFO failed (workaround - use -l)

SQL1042C An unexpected system error occurred. SQLSTATE=58004

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

SQLCABC = 136
SQLCODE = -1042
SQLERRMC =
SQLERRP = SQLERFED
sqlerrd[0] = 0
sqlerrd[1] = 0
sqlerrd[2] = 0
sqlerrd[3] = 0
sqlerrd[4] = 0
sqlerrd[5] = 0
SQLWARN =
SQLSTATE = 58004
Critical SQLCODE. Exiting db2advis ...
The insert into the ADVISE_INSTANCE table has failed.

0 solutions were evaluated by the advisor

exiting with error code [-1042]

Thanks in advance.

[Mark A]

Post by g***@vsnl.net
Using user id as default schema name. Use -n option to specify schema
CALL SYSPROC.GET_DBSIZE_INFO failed (workaround - use -l)
SQL1042C An unexpected system error occurred. SQLSTATE=58004
*************************************
* CONTENTS OF SQLCA *
*************************************
SQLCABC = 136
SQLCODE = -1042
SQLERRMC =
SQLERRP = SQLERFED
sqlerrd[0] = 0
sqlerrd[1] = 0
sqlerrd[2] = 0
sqlerrd[3] = 0
sqlerrd[4] = 0
sqlerrd[5] = 0
SQLWARN =
SQLSTATE = 58004
Critical SQLCODE. Exiting db2advis ...
The insert into the ADVISE_INSTANCE table has failed.
0 solutions were evaluated by the advisor
exiting with error code [-1042]
Thanks in advance.

Did you update the database after installing the fixpack?

[g***@vsnl.net]

Don't know as I did not do the fix pack upgrade.

How can I verify if the database has been updated after the fixpack has been applied?

TIA.

[g***@vsnl.net]

Yes, it must have been done. However, I was not involved during the upgrade.

BTW, Quest central for DB2 works fine on this upgraded database. Does this interfere with DB2 tools - db2advis & db2expln?

[g***@vsnl.net]

It failed because of some invisible characters transported during copy & paste. Now it is working fine. The check before firing db2advis was to see that the SQL generates the visual explain without errors from a windows desktop. The syntax used for db2advis was ...

db2advis -d dbname -s "select * from employee where empid = 1" -t 100 -l 200

Thanks again for the input provided.