Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Release Notes

- Previous: Monitoring
- Next: Samples

# PointBase

This section describes known and associated solutions related to PointBase.

Bug ID | Summary
--- | ---
6184797 | Setting the isolation levels on a connection pool for an application causes exceptions in PointBase. For a JDBC connection pool pointing to a PointBase database installation, setting the transaction-isolation-level pool attribute to any value other than the default (`Connection.TRANSACTION_READ_COMMITTED`) causes an exception. However, setting this same parameter to non-default values for pools pointing to other databases does not throw an exception. Solution For a JDBC connection pool pointing to a PointBase database installation, do not attempt to set the `transaction-isolation-level`.
6204925 | PointBase throws an exception if a network server and embedded drivers are used together. The bundled PointBase sometimes throws an exception if the network server driver and the embedded driver are simultaneously used. Solution Use either the embedded driver or the network server driver, but not both.
6264969, 6275448 | Upgrade problem where the default PointBase database is overwritten. When upgrading to Application Server Enterprise Edition 8.1 2005Q2 Update 2, the Update release patch overwrites the Pointbase default database. Solution Recreate or re-enter any scheme or data that existed prior to the upgrade. If you deployed applications with CMP beans with the generate table option, you must undeploy or redeploy the application to have the tables regenerated.

- Previous: Monitoring
- Next: Samples

- © 2010, Oracle Corporation and/or its affiliates