Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
We need more info to help but one thing you may want look at is your
Isolation level. if you are not using dirty read you may run into
locking problems of this type.
Russ...
}----------
}From: Peter Jennings[SMTP:peter_jennings*@uk.ibm.com]
}Sent: Monday, January 20, 1997 2:57 PM
}To: informix-list@rmy.emory.edu
}Subject: SQL code -246, ISAM code -154 problem.
}
}Running OnLine V5.0 under AIX.
}We have a begin/commit process that locks a
}parent record by updating a column with its
}current contents. We find that if two users
}try to update different rows in the same child
}table, the first will suceed and the other fail
}with SQL code -246, ISAM code -154.
}The two users are accessing different rows
}in both the parent and the child tables.
}This only happens if the first user has not
}reached the 'commit' before the second user
}trys to update.
}Both the tables have row mode locking set.
}
}1st User User 2
}begin work begin work
}lock parent row x lock parent row y
}. .
}. .
}update child row m .
}. update child row n (fails)
}. .
}. .
}commit .
} update child row n (OK)
} .
} commit
}
}Peter Jennings.
}
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.