The problem occurs in cases where changes of spatial data are made before an exception is raised within a distributed transaction. When the exception is raised, the distributed transaction is aborted but since Oracle Spatial depends on temporary tables the spatial changes are not rolled back adequately and are left hanging.
Any subsequent changes of related spatial data will cause an ORA-14450 to be raised.
The error message is:
ORA-14450: attempt to access a transactional temp table already in use
2 comments:
The same problem has been experienced by others and is described here and here.
An update on the issue is found here.
Post a Comment