 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion Groups Database Servers DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybaseDesktop Databases FileMakerFoxProMS AccessParadoxGeneral General DB TopicsDatabase TheoryRelated Topics Java Development.NET DevelopmentVB DevelopmentMore Topics ... |
Database Forum / DB2 Topics / April 2005UDB v 8.1 on win2000 - SQL0925N SQL COMMIT invalid for application execution
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 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... > Hi, > [quoted text clipped - 28 lines] > cheers > vijai > 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. >>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  SignatureSerge Rielau DB2 SQL Compiler Development IBM Toronto Lab It's NOT ok for twophase commit. >>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. > 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. 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 > Hi, > [quoted text clipped - 28 lines] > cheers > vijai |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.