Thanks guys, for the feedback. I wasn't aware of the DRDA tracing
tool, that's pretty handy. Although, in this case it didn't provide me
much more information than I had before. I finally found the problem,
and I'm posting this in case anyone else encounters it.
After reading that the CLI config parameter DB2OPTIMIZATION=5 should
invoke a 'SET CURRENT QUERY OPTIMIZATION 5' statement for you, behind
the scenes when you connect, I decided to turn on the cli TRACE flag
in my db2cli.ini file to see if it was actualy doing this. I then
attached, connected to the database and then terminated. I then went
to look in the trace file ... and it didn't exist. Multiple attempts
of setting the trace flag on and off still resulted in no trace file
being produced. In fact, no changes I made to the db2cli.ini file
appeared to be recognized by my connection attempts. I finally tracked
the problem down to the fact the OS (WinNT) PATH environment variable
had been hosed by the installation program of a vendor who shall
remain nameless, but eternally reviled. The way it was hosed was by
the install program pre-pending it's own directory path at the front
of the PATH variable, with an imbedded space in the path name, like
so:
%SystemRoot%\system32;%SystemRoot%;C:\Program
Files\Symantec\pcNowhere\;C:\PROGRA~1\SQLLIB\BIN;C :\PROGRA~1\SQLLIB\FUNCTION;C:\PROGRA~1\SQLLIB\SAMP LES\REPL
Everything after the space is unrecognized, so the SQLLIB and
SQLLIB\BIN directories where not included in the PATH variable.
Changing 'Program files' to 'PROGRA~1', and rebooting, did the trick.
"PM \(pm3iinc-nospam\)" <PM(pm3iinc-nospam)@sympatico.ca> wrote in message news:<PpwSb.6548$qU3.577896@news20.bellglobal.com> ...[color=blue]
> On v8, you can trace the drda stream with the db2drdat tool.
> You can also start db2cctrc to start the cc in trace mode.
>
> Places i'd check :
> db2set -all
> db2cli.ini (possibly 2 locations / user / system)
> tools setup/environment settings (in cc/dev center, ...)
> db2diag.log
> CURRENT EXPLAIN MODE, CURRENT EXPLAIN SNAPSHOT
>
> apars search i've made (you may try with other keywords)
>
http://www-306.ibm.com/cgi-bin/db2ww...2&totalSize=10
> JR18599 may relate. (could try it and try to output to null device?)
> fixed in fp4 but there is also a fp4.a because of an hiper apar on fp4....
>
>
> PM
>
> "Sean C." <dba_fla@yahoo.com> a écrit dans le message de
> news:2f9c2d92.0401091126.2da40490@posting.google.c om...[color=green]
> > Helpful folks,
> >
> > I've just migrated our test server from V7.2 -FP11 to V8.1.3, on WinNT[/color]
> 4.0.[color=green]
> > Everything went pretty darn smoothly, however I get the following errors
> > when using the Control Center:
> >
> > Click on the 'Event Monitor' folder, and an error dialog box
> > appears containing the following text:
> >
> > [IBM][CLI Driver][DB2/NT] SQL0713N The replacement value for
> > "CURRENT QUERY OPTIMIZATION" is invalid. SQLSTATE=42815
> >
> >
> > {SQLDriverConnect}
> >
> > Explanation:
> >
> > Either the value specified in the SET <special-register>
> > statement is not a valid value of the indicated special register,
> > or the value specified is NULL as a result of an indicator
> > variable.
> >
> > The statement cannot be executed.
> >
> > User Response:
> >
> > Correct the replacement value and/or any indicator variables.
> > See the SQL Reference for an explanation of the valid values of
> > each special register.
> >
> > sqlcode : -713
> >
> > sqlstate : 42815
> >
> >
> >
> > Also, if I right click on a database name and choose the
> > 'Configure Parameters' menu selection, I get an error dialog containing:
> >
> >
> > The replacement value for "<special-register>" is
> >
> > invalid.
> >
> > Explanation:
> >
> > Either the value specified in the
> > SET <special-register>
> > statement is not a valid value of the
> > indicated special register,
> > or the value specified is NULL as
> > a result of an indicator
> > variable.
> >
> > The statement cannot be
> > executed.
> >
> > User Response:
> >
> > Correct the replacement value
> > and/or any indicator variables.
> > See the SQL Reference for an
> > explanation of the valid values of
> > each special register.
> >
> >
> > sqlcode : -713
> >
> > sqlstate : 42815
> >
> >
> > These exact errors occur regardless of which of the 5 databases
> > in the instance I select.
> >
> >
> > Within the db2diag.log are these entries which I'm not sure are
> > relevant or not:
> >
> > 2004-01-09-10.14.22.261000 Instance:DB2 Node:000
> > PID:332(db2syscs.exe) TID:420 Appid:*LOCAL.DB2.003D49151420
> > database monitor sqm.start_evmon Probe:32 Database:WOETEST
> >
> > DIA0001E An internal error occurred. Report the following error code :
> > "ZRC=0x840D000C".
> >
> > 2004-01-09-10.14.22.261001 Instance:DB2 Node:000
> > PID:332(db2syscs.exe) TID:420 Appid:*LOCAL.DB2.003D49151420
> > database monitor sqm.evmgr::log_ev_err Probe:1 Database:WOETEST
> >
> > DiagData
> > 0x3717CD00 : 0x840D000C
> >
> >
> >
> > Disconcertingly, when I do a search on the DB2 tech support search page,
> > using 'SQL0713' as a search argument, I get no hits whatsoever.
> >
> > Does anyone have any suggestions, insights, or links I could pursue?
> >
> > Any feedback would be greatly appreciated,
> > Sean[/color][/color]
