Over the last few weeks I have been upgrading a number of Servoy solutions from either 5.2 or 6.0 to 6.1. At the same time we have been migrating our Oracle databases from one server to another more secure server. For inserts on almost every table I use Oracle sequences rather than Servoy sequences. Before the upgrades all of these Oracle sequences worked fine. Now I am finding that on some tables in two different solutions the inserts are failing because of ORA-00001: unique constraint, i.e the sequences Servoy is using are out of whack with what they should be.
On these tables Servoy has the tables defined as using the db_seq and it is correctly named. But the sequence number Servoy is inserting has no bearing on what Oracle says the sequence number should be. Sometimes it appears that Servoy has decided to instead use the servoy_seq. When it does that at least the inserts don't fail. Other times though I can't even figure out where Servoy is getting the sequence from. In those cases the inserts fail because Servoy uses a number that already exists in that table. If I switch the table to servoy_seq then it works but if I try switching the sequence back to the Oracle sequence it still fails, bringing up numbers in the same order it had before. This is a big problem. Is there a way to FORCE Servoy to use that Oracle sequence properly again? In the .dbi file for the table everything looks fine too with it naming the db sequence correctly...