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

V8 migration - Control Center errors

P: n/a
Helpful folks,

I've just migrated our test server from V7.2 -FP11 to V8.1.3, on WinNT 4.0.
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
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
While the errors posted previously are still a problem, the task I was
trying to perform when they occured was to define a federated server.
I tried this using a script invoked locally on the server in a command
window, like so:

CREATE SERVER "CICTEST" TYPE DB2/NT VERSION 8.1.3 WRAPPER "DRDA"
AUTHORIZATION db2admin PASSWORD "----" OPTIONS ( NODE 'DBS6',DBNAME
'CICTEST' );

This produced the following error in the db2diag.log:

[IBM][CLI Driver] SQL30020N Execution failed because of a Distributed
Protocol Error that will affect the successful execution of subsequent
commands and SQL statements: Reason Code "0x124C". SQLSTATE=58009..
{SQLDriverConnect}

Nowhere on the DB2 website can I find an explanation for this reason
code, but I did find a reference in this newsgroup. It implied that
the communication data stream contained a syntax error. However, I get
no syntax error related to the CREATE command itself.

Would anyone have insight into this problem? This is preventing me
from testing a major aspect of our processing functionality on V8.

And, would anyone know why the value of my CURRENT QUERY OPTIMIZATION
special register seem to simply 'disappear' on an intermittant basis?

Any feedback would be appreciated,
Sean

db*****@yahoo.com (Sean C.) wrote in message news:<2f**************************@posting.google. com>...
Helpful folks,

I've just migrated our test server from V7.2 -FP11 to V8.1.3, on WinNT 4.0.
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

Nov 12 '05 #2

P: n/a
A 30020 is a catch-all error when something in the DRDA datastream goes
bad...your best bet would be to contact service.

Sean C. wrote:
While the errors posted previously are still a problem, the task I was
trying to perform when they occured was to define a federated server.
I tried this using a script invoked locally on the server in a command
window, like so:

CREATE SERVER "CICTEST" TYPE DB2/NT VERSION 8.1.3 WRAPPER "DRDA"
AUTHORIZATION db2admin PASSWORD "----" OPTIONS ( NODE 'DBS6',DBNAME
'CICTEST' );

This produced the following error in the db2diag.log:

[IBM][CLI Driver] SQL30020N Execution failed because of a Distributed
Protocol Error that will affect the successful execution of subsequent
commands and SQL statements: Reason Code "0x124C". SQLSTATE=58009..
{SQLDriverConnect}

Nowhere on the DB2 website can I find an explanation for this reason
code, but I did find a reference in this newsgroup. It implied that
the communication data stream contained a syntax error. However, I get
no syntax error related to the CREATE command itself.

Would anyone have insight into this problem? This is preventing me
from testing a major aspect of our processing functionality on V8.

And, would anyone know why the value of my CURRENT QUERY OPTIMIZATION
special register seem to simply 'disappear' on an intermittant basis?

Any feedback would be appreciated,
Sean

db*****@yahoo.com (Sean C.) wrote in message news:<2f**************************@posting.google. com>...
Helpful folks,

I've just migrated our test server from V7.2 -FP11 to V8.1.3, on WinNT 4.0.
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

Nov 12 '05 #3

P: n/a
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." <db*****@yahoo.com> a écrit dans le message de
news:2f**************************@posting.google.c om...
Helpful folks,

I've just migrated our test server from V7.2 -FP11 to V8.1.3, on WinNT 4.0. 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

Nov 12 '05 #4

P: n/a
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:<Pp*******************@news20.bellglobal.com> ...
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." <db*****@yahoo.com> a écrit dans le message de
news:2f**************************@posting.google.c om...
Helpful folks,

I've just migrated our test server from V7.2 -FP11 to V8.1.3, on WinNT

4.0.
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

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.