Hi Everyone,
Been having a few issues with Oracle and gast:
1. Constraints, Constraints, Constraints - clearing out the database before the migration using "DELETE FROM .." causes Oracle to chuck exceptions about constraint violations. I've changed the gast code to wipe out the database and rebuild the bits we need leaving the tables to be filled by the migration empty - gets round the problems of having to identify and disable constraints.
2. Gast's migration facility has a bug (I think) in the way it chooses the owner of migrated metadata records:
Index: src/org/fao/gast/gui/panels/migration/oldinst/Worker.java
--- src/org/fao/gast/gui/panels/migration/oldinst/Worker.java (revision 1153)
+++ src/org/fao/gast/gui/panels/migration/oldinst/Worker.java (working copy)
@@ -330,7 +330,7 @@
if (usrGrps.size() == 0)
throw new Exception("No editor for metadata --> id:"+id);
- String owner = ((Element) privil.get(0)).getChildText("id");
+ String owner = ((Element) usrGrps.get(0)).getChildText("id");
//--- no, ok we can store it
3. The dreaded "Transaction not serializable" or "can't be serialized" error pops up too many times to be amusing - seems the way to overcome this is to switch to read_committed which I've done for oracle in our working copy of jeeves (oracle specific by checking the url). So far its been absent but we'll see how this shapes up and there may be other implications?
4. Writing nulls to columns in Oracle through jdbc (new fields on metadata table) causes "invalid column type" exceptions - one way round a nasty oracle only hack to supply jdbc column types is to make the default for these (few) columns null and then avoid writing nulls. Works ok for me so far.
Might have some commits if these changes shape up - but surely others have run into these kinds of problems? (using 10g and latest recommended ojdbc drivers from oracle technology network site)
Cheers,
Simon