Re: 589 error

>> From: "Scott F. Ford" <uunet!oregon.wvus.org!sford> >> To: informix-list@rmy.emory.edu >> Subject: 589 error >> Cc: sford@mark.wvus.org >> X-Informix-List-Id: <list.722> >> >> Here's another one gang.. >> >> ever heard of a -589 error? This isn't in any book I've ever seen. >> We're on a Unisys 6000/70, /80 TCP-IP network utilizing ISTAR. We get >> this when trying to update a remote engine's data base (4.1 online). Patient: "Doctor, it hurts when I do *this*..." Doctor: "Don't DO that, then!" [-: 4.X OnLine / I-STAR do not support updates of non-current databases; you may only update tables in the current database (whether it's local or remote). >> Thanks in advance for any info leading to the id of this one... With 5.0 OnLine and I-STAR's Two-Phase Commit, you will be able to update tables in noncurrent databases... >> Scott Ford, DBA | sford@wvus.org Full text of -589 follows: -589 Cannot update multiple sites within a single transaction. This database engine supports only "single-site update"; that is, the operations within one transaction may modify data at only one site in the network. Some preceding statement within this transaction has already modified data at one site; the current statement would modify data at a second site. The statement is not executed. Roll back the current transaction. Examine the application in the light of this restriction. Check the names of all tables that are affected by UPDATE, INSERT, and DELETE statements to make sure they are all in the same database, or in databases held by the same database engine. (Be sure to check the definition of any synonyms, since synonyms can make tables in external databases appear to be in the current database.) -- Alan Denney aland@informix.com {pyramid|uunet}!infmx!aland J.F.K. to Kruschev: "I'll leave Castro alone If you'll take away those missiles; they're too damn close to home." The CIA, the Cubans, and the underworld bosses Was (not Was) Decided that was it; they had to cut their losses... "11 Miles Per Hour"