Has anybody else encountered problems saving data to Oracle 8i Spatial?
We have encountered a curious and very annoying problem with a client site
which is using MapInfo Pro 6.0 (some unpatched, some patched to 6.0.0032)
to edit linked spatial tables stored in an Oracle 8.1.5 database running on
(I think) a Sun server.
It appears that during "core work hours", any attempt to save incremental
spatial edits to the Oracle database (e.g. changing the alignment of a road
centreline by moving a few nodes) causes MapInfo to fail with any one of
about five (5) different Oracle OCI errors. The actual error message is
almost random (within the set of five regulars). At other times MapInfo
will fail disasterously with an Application Error or, on at least one
occasion it simply shut down and vanished.
I have amassed some significant documentation regarding the errors - too
much to just post on the list - but if anybody would like to know more I
can certainly tell them.
The really curious bits are as follows:
1. We have an identical database (albeit on a Windows NT server) created by
exporting the Oracle database and then reimporting it. This is our
development database for ongoing support. It suffers from NONE of the
errors that the client database does.
2. The time-of-day issue is VERY significant. Prior to about 8:00 am and
after about 5:00 pm, the errors cease happening and edits seem to be saved
without a problem. We have escalated this within the client organisation
to try to get their IT people onto the case. At a guess it appears to be
either a resource profile issue (i.e. certain users granted access and
resources at certain times) or a database traffic issue (i.e. very busy
when lots of people are working on the server). I might add that their
server is used for much more than just the Oracle Spatial database which
itself has no more than about 4 users.
At this stage, as I said, we are hoping that the issue can be identified
and resolved by the client IT people.
However it would seem to indicate that MapInfo is behaving very
"ungracefully" when it encounters an unexpected failure during an Oracle
Spatial commit. Either the save works or it doesn't, and if it doesn't the
client program (in this case MapInfo) should handle the exception - ALL
exceptions - in a graceful manner. This is most certainly NOT the case at
the moment.
I would welcome any other user observations or comments on this matter. I
would be delighted if somebody from MapInfo could shed some light on the
subject, too!
Cheers,
David Jerrard
Exa-Min Technologies
Exa-Min Technologies Pty Ltd
2nd Floor, 143 Charlotte Street, BRISBANE
PO Box 12020, Elizabeth Street Q 4002
AUSTRALIA
Ph: +61 7 32100741 Fax: +61 7 32100738
Email: [EMAIL PROTECTED] WWW: http://www.geobasemap.com
_______________________________________________________________________
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, send e-mail to [EMAIL PROTECTED] and
put "unsubscribe MapInfo-L" in the message body.
