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

DB2Advisor error

P: n/a
I currently test 8.2 Enterprise eval.
When i run "db2advis -d testowa -m I -f -i c:\zap.sql" all is ok and i
get index recomendation.
When i run "db2advis -d testowa -m IM -f -i c:\zap.sql" ( to show
recommended MQTs) i get information (sorry from poor translation from
polish)

SQL0104N Founds unexpected element "," after text "1048576,
000000) > 4". Dposiible elements are: "SELECTIVITY". SQLSTATE=42601

*************************************
* SQLCA CONTENTS *
*************************************

SQLCABC = 136
SQLCODE = -104
SQLERRMC = ,ˇ1048576,000000) > 4ˇSELECTIVITY

SQLERRP = SQLNP012
sqlerrd[0] = 2149187693
sqlerrd[1] = 0
sqlerrd[2] = 0
sqlerrd[3] = 0
sqlerrd[4] = 4294966591
sqlerrd[5] = 0
SQLWARN =
SQLSTATE = 42601
Critical SQLCODE error. Closing db2advis

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


P: n/a
Looks like an error in the SQL statements, there is a ",".

Ivan

Bartosz Gorzynski wrote:
I currently test 8.2 Enterprise eval.
When i run "db2advis -d testowa -m I -f -i c:\zap.sql" all is ok and i get index recomendation.
When i run "db2advis -d testowa -m IM -f -i c:\zap.sql" ( to show
recommended MQTs) i get information (sorry from poor translation from polish)

SQL0104N Founds unexpected element "," after text "1048576,
000000) > 4". Dposiible elements are: "SELECTIVITY". SQLSTATE=42601

*************************************
* SQLCA CONTENTS *
*************************************

SQLCABC = 136
SQLCODE = -104
SQLERRMC = ,ˇ1048576,000000) > 4ˇSELECTIVITY

SQLERRP = SQLNP012
sqlerrd[0] = 2149187693
sqlerrd[1] = 0
sqlerrd[2] = 0
sqlerrd[3] = 0
sqlerrd[4] = 4294966591
sqlerrd[5] = 0
SQLWARN =
SQLSTATE = 42601
Critical SQLCODE error. Closing db2advis


Nov 12 '05 #2

P: n/a
Maybe, but analysed statement is
SELECT
SPRZEDAZ.SPRZEDAZ.ZAKLAD,SPRZEDAZ.SPRZEDAZ.DATAFAK/100,SUM(SPRZEDAZ.SPRZEDAZ.WARTOSCN)
FROM SPRZEDAZ.SPRZEDAZ GROUP BY
SPRZEDAZ.SPRZEDAZ.ZAKLAD,SPRZEDAZ.SPRZEDAZ.DATAFAK/100 ORDER BY
SPRZEDAZ.SPRZEDAZ.ZAKLAD,SPRZEDAZ.SPRZEDAZ.DATAFAK/100;

or this same without ; using -s option (anad works in command center)
select
sprzedaz.sprzedaz.zaklad,sprzedaz.sprzedaz.datafak/100,sum(sprzedaz.sprzedaz.wartoscn)
from sprzedaz.sprzedaz group by
sprzedaz.sprzedaz.zaklad,sprzedaz.sprzedaz.datafak/100 order by
sprzedaz.sprzedaz.zaklad,sprzedaz.sprzedaz.datafak/100;

Ivan Popivanov napisa≥(a):
Looks like an error in the SQL statements, there is a ",".

Ivan

Bartosz Gorzynski wrote:
I currently test 8.2 Enterprise eval.
When i run "db2advis -d testowa -m I -f -i c:\zap.sql" all is ok and


i
get index recomendation.
When i run "db2advis -d testowa -m IM -f -i c:\zap.sql" ( to show
recommended MQTs) i get information (sorry from poor translation from


polish)

SQL0104N Founds unexpected element "," after text "1048576,
000000) > 4". Dposiible elements are: "SELECTIVITY". SQLSTATE=42601

*************************************
* SQLCA CONTENTS *
*************************************

SQLCABC = 136
SQLCODE = -104
SQLERRMC = ,ˇ1048576,000000) > 4ˇSELECTIVITY

SQLERRP = SQLNP012
sqlerrd[0] = 2149187693
sqlerrd[1] = 0
sqlerrd[2] = 0
sqlerrd[3] = 0
sqlerrd[4] = 4294966591
sqlerrd[5] = 0
SQLWARN =
SQLSTATE = 42601
Critical SQLCODE error. Closing db2advis


Nov 12 '05 #3

P: n/a
"Bartosz Gorzynski" wrote:
Maybe, but analysed statement is
SELECT
SPRZEDAZ.SPRZEDAZ.ZAKLAD,SPRZEDAZ.SPRZEDAZ.DATAFAK/100,SUM(SPR
ZEDAZ.SPRZEDAZ.WARTOSCN)

FROM SPRZEDAZ.SPRZEDAZ GROUP BY
SPRZEDAZ.SPRZEDAZ.ZAKLAD,SPRZEDAZ.SPRZEDAZ.DATAFAK/100 ORDER
BY
SPRZEDAZ.SPRZEDAZ.ZAKLAD,SPRZEDAZ.SPRZEDAZ.DATAFAK/100;

or this same without ; using -s option (anad works in command
center)
select
sprzedaz.sprzedaz.zaklad,sprzedaz.sprzedaz.datafak/100,sum(spr
zedaz.sprzedaz.wartoscn)

from sprzedaz.sprzedaz group by
sprzedaz.sprzedaz.zaklad,sprzedaz.sprzedaz.datafak/100 order
by
sprzedaz.sprzedaz.zaklad,sprzedaz.sprzedaz.datafak/100;

Ivan Popivanov napisa≥(a):
Looks like an error in the SQL statements, there is a ",".

Ivan

Bartosz Gorzynski wrote:

 >>I currently test 8.2 Enterprise eval.
 >>When i run "db2advis -d testowa -m I -f -i c:zap.sql"
all is ok and

i

 >>get index recomendation.
 >>When i run "db2advis -d testowa -m IM -f -i
c:zap.sql" ( to show
 >>recommended MQTs) i get information (sorry from poor
translation from

 >>polish)
 >>
 >>SQL0104N Founds unexpected element "," after text
"1048576,
 >>000000) > 4". Dposiible elements are:
"SELECTIVITY". SQLSTATE=42601
 >>
 >>*************************************
 >>* SQLCA CONTENTS *
 >>*************************************
 >>
 >>SQLCABC = 136
 >>SQLCODE = -104
 >>SQLERRMC = ,ˇ1048576,000000) > 4ˇSELECTIVITY
 >>
 >>SQLERRP = SQLNP012
 >>sqlerrd[0] = 2149187693
 >>sqlerrd[1] = 0
 >>sqlerrd[2] = 0
 >>sqlerrd[3] = 0
 >>sqlerrd[4] = 4294966591
 >>sqlerrd[5] = 0
 >>SQLWARN =
 >>SQLSTATE = 42601
 >>Critical SQLCODE error. Closing db2advis


This is a known problem whose fix is going into FP10 of V8.2. The PMR
that first reported this was 20433, 265, 631. The problem was
that on systems where commas are used in numbers instead of
the american decimal (e.g., 8,5 instead of 8.5), db2advis was
getting errors such as below when processing statements it
generates with floats.

If this is a statement that is in your workload the fix is to change
the commas to decimals before inputting the queries to db2advis.

If not from your workload queries, then the PMR will fix the problem.
Contact IBM DB2 service to ask for a patch if needed now.

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-Advisor-...ict218486.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=804336
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.