at one point in the databaseProperties test it sets that SYSTEM pageSize. This is likely causing at least some of the problems. Best would be to change the
test to unset the system property after it does the test it is trying to do. I don't see an existing utility, so may need to add one.
Do you know in the new environment if the test is run with autocommit on or off? I would suggest running the test with autocommit off and then run an abort at the end
of the script.
Here is a web hit on how to delete
a system property:
How to Remove a System Property
I thought I could remove a system property by setting its value to null, but it turns out that System.setProperty(key, val) will throw NullPointerException when either key or value is null. Here are 2 ways to remove or clear a system property:
1. clearProperty(String key) introduced in JDK 1.5.
Properties sysProps = System.getProperties();
When java security manager is enabled, Both methods need specific permissions to succeed. Approach 1 requires PropertyPermission "key", "read,write". Approach 2 requires a much wider permission: PropertyPermission "*", "read,write", because you are free to modify/remove all system properties with the returned object from System.getProperties()