By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,558 Members | 1,068 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 - works with indexes but not MV

P: n/a
Hello, I am using DB2-UDB 8.2, when running the design advisor, It
exists tells me that "catalog simulation requires that the server be at
level V8.0 or newer", although the DB2 version is 8.2 (with Fixpack 9).
When I remove "Materialized Views" from the recommendation and choose
only "Indexes", it works.

Any suggestions?
Command : db2advis -f -d TPCH -t 5 -i c:\q3.sql -m MI -o c:\advise.txt

Output :

Starting the Database Manager Now
execution started at timestamp 2005-06-10-16.12.37.816005
Using the default table space name USERSPACE1
found [21] SQL statements from the input file
Recommending indexes...
Recommending MQTs...
Multiple query optimization failed (groups of queries) SQLCODE=-1224
DB request error turning simulation suspend: rc = -1

SQL0901N The SQL statement failed because of a non-severe system
error.

Subsequent SQL statements can be processed. (Reason "Catalog
Simulation
requires that the server be at level V8.0 or newer

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

SQLCABC = 136
SQLCODE = -901
SQLERRMC = Catalog Simulation requires that the server be at level V8.0
or newer

SQLERRP =
sqlerrd[0] = 0
sqlerrd[1] = 0
sqlerrd[2] = 0
sqlerrd[3] = 0
sqlerrd[4] = 0
sqlerrd[5] = 0
SQLWARN =
SQLSTATE =
Critical SQLCODE. Exiting db2advis ...
DB request error turning simulation suspend: rc = -1

SQL0901N The SQL statement failed because of a non-severe system
error.
Subsequent SQL statements can be processed. (Reason "Catalog
Simulation
requires that the server be at level V8.0 or newer

Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Here is the answer I got:

"catalog simulation requires that the server be at level V8.0 or newer"
is found when a trap was found in DB2. What should be done is reporting
this to DB2 as a PMR and getting the trap file that was output in the
sqllib/db2dump directory so IBM can investigate.

Nov 12 '05 #2

P: n/a
"UnixSlaxer" wrote:
Hello, I am using DB2-UDB 8.2, when running the design
advisor, It
exists tells me that "catalog simulation requires that the
server be at
level V8.0 or newer", although the DB2 version is 8.2 (with
Fixpack 9).
When I remove "Materialized Views" from the recommendation and
choose
only "Indexes", it works.

Any suggestions?
Command : db2advis -f -d TPCH -t 5 -i c:q3.sql -m MI -o
c:advise.txt

Output :

Starting the Database Manager Now
execution started at timestamp 2005-06-10-16.12.37.816005
Using the default table space name USERSPACE1
found [21] SQL statements from the input file
Recommending indexes...
Recommending MQTs...
Multiple query optimization failed (groups of queries)
SQLCODE=-1224
DB request error turning simulation suspend: rc = -1

SQL0901N The SQL statement failed because of a non-severe
system
error.

Subsequent SQL statements can be processed. (Reason "Catalog
Simulation
requires that the server be at level V8.0 or newer

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

SQLCABC = 136
SQLCODE = -901
SQLERRMC = Catalog Simulation requires that the server be at
level V8.0
or newer

SQLERRP =
sqlerrd[0] = 0
sqlerrd[1] = 0
sqlerrd[2] = 0
sqlerrd[3] = 0
sqlerrd[4] = 0
sqlerrd[5] = 0
SQLWARN =
SQLSTATE =
Critical SQLCODE. Exiting db2advis ...
DB request error turning simulation suspend: rc = -1

SQL0901N The SQL statement failed because of a non-severe
system
error.
Subsequent SQL statements can be processed. (Reason "Catalog
Simulation
requires that the server be at level V8.0 or newer


With the error: "catalog simulation requires that the server be at
level V8.0 or newer", this is found when a trap was found in DB2.
What should be done is reporting this to DB2 as a PMR and getting the
trap file that was output in the sqllib/db2dump directory
so IBM can investigate.

Thanks
Danny

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/DB2-advis-wo...ict231461.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=804333
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.