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

UDB v 8.1 on win2000 - SQL0925N SQL COMMIT invalid for application execution

P: n/a
Hi,

I am using UDB v 8.1 on win2000.

I have setup the ODBC datasources.

My application is connecting to the database and performing DML activities.
But I am getting the following error

SQL0925N SQL COMMIT invalid for application execution environment.
SQLSTATE=2D521

My db2cli.ini settings are
[DTPVPD02]
DEFERREDPREPARE=0
CURSORHOLD=0
CURRENTSCHEMA=VIPS
CONNECTTYPE=2
SYNCPOINT=2
AUTOCOMMIT=0
DBALIAS=DTPVPD02

Application works perfectly fine in UDB v7.2

Is the CONNECTTYPE=2 and SYNCPOINT=2 are supported in UDB v8.

If not what is the equivalent settings needs to be in db2cli.ini

Would appreciate your help.

cheers
vijai
Nov 12 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
You're not trying to commit in a stored procedure, right?

I'd guess you need to check your server side settings...one of the
servers doesn't have a tp monitor spm or somthing set up...

vijai kumar via DBMonster.com wrote:
Hi,

I am using UDB v 8.1 on win2000.

I have setup the ODBC datasources.

My application is connecting to the database and performing DML activities.
But I am getting the following error

SQL0925N SQL COMMIT invalid for application execution environment.
SQLSTATE=2D521

My db2cli.ini settings are
[DTPVPD02]
DEFERREDPREPARE=0
CURSORHOLD=0
CURRENTSCHEMA=VIPS
CONNECTTYPE=2
SYNCPOINT=2
AUTOCOMMIT=0
DBALIAS=DTPVPD02

Application works perfectly fine in UDB v7.2

Is the CONNECTTYPE=2 and SYNCPOINT=2 are supported in UDB v8.

If not what is the equivalent settings needs to be in db2cli.ini

Would appreciate your help.

cheers
vijai

Nov 12 '05 #2

P: n/a
"Sean McKeough" <mc******@nospam.ibm.com> wrote in message
news:42********@news3.prserv.net...
You're not trying to commit in a stored procedure, right?

I'd guess you need to check your server side settings...one of the servers
doesn't have a tp monitor spm or somthing set up...

It is OK to commit is a SP on DB2 for LUW.
Nov 12 '05 #3

P: n/a
From a udb environment command prompt; try:
db2 ? SQL0925N

I'd guess that the second point is your problem:

o A DB2 application precompiled or set to use CONNECT 2 in a
non-TP Monitor environment has issued a dynamic SQL COMMIT
statement, whereas only static SQL COMMITs are allowed.

Methods of fixing this problem are also suggested.
Phil Sherman


vijai kumar via DBMonster.com wrote:
Hi,

I am using UDB v 8.1 on win2000.

I have setup the ODBC datasources.

My application is connecting to the database and performing DML activities.
But I am getting the following error

SQL0925N SQL COMMIT invalid for application execution environment.
SQLSTATE=2D521

My db2cli.ini settings are
[DTPVPD02]
DEFERREDPREPARE=0
CURSORHOLD=0
CURRENTSCHEMA=VIPS
CONNECTTYPE=2
SYNCPOINT=2
AUTOCOMMIT=0
DBALIAS=DTPVPD02

Application works perfectly fine in UDB v7.2

Is the CONNECTTYPE=2 and SYNCPOINT=2 are supported in UDB v8.

If not what is the equivalent settings needs to be in db2cli.ini

Would appreciate your help.

cheers
vijai


Nov 12 '05 #4

P: n/a
Mark A wrote:
"Sean McKeough" <mc******@nospam.ibm.com> wrote in message
news:42********@news3.prserv.net...
You're not trying to commit in a stored procedure, right?

I'd guess you need to check your server side settings...one of the servers
doesn't have a tp monitor spm or somthing set up...


It is OK to commit is a SP on DB2 for LUW.

...if the proc is called by teh app.
If the proc is aclled by a function or a trigger commit and rollback are
verboten.

Cheers
Serge
--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab
Nov 12 '05 #5

P: n/a
It's NOT ok for twophase commit.

Mark A wrote:
"Sean McKeough" <mc******@nospam.ibm.com> wrote in message
news:42********@news3.prserv.net...
You're not trying to commit in a stored procedure, right?

I'd guess you need to check your server side settings...one of the servers
doesn't have a tp monitor spm or somthing set up...


It is OK to commit is a SP on DB2 for LUW.

Nov 12 '05 #6

P: n/a
"Sean McKeough" <mc******@nospam.ibm.com> wrote in message
news:42********@news3.prserv.net...
It's NOT ok for twophase commit.

Is that what SYNCPOINT=2 means? Is a two-phase commit needed?

I found this in the V8.1 CLI Guide and Reference (pg 336), but not exactly
sure what it means in regard to this question:

SYNCPOINT CLI/ODBC Configuration Keyword

Note: This keyword is not supported in DB2 Version 8, but is available for
backward compatibility only. Refer to the documentation for previous
versions of DB2 for information on this keyword at:
http://www.ibm.com/software/data/db2/library.
Nov 12 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.