Pitney Bowes MapXtreme - Manual (Page 238)

Chapter 11: Accessing Data from a DBMS
Troubleshooting
MapXtreme v7.1 245 Developer Guide
Troubleshooting
If you encounter problems with your SpatialWare or Oracle applications, use the following table to
help analyze and solve the problem.
Problem Description Possible Cause Solution
The table is not matchable. Data binding was attempted
against a SpatialWare layer. AddColumns is not currently
supported for SpatialWare
layers.
No object was found using
the index that you specified. A query was made against a
table that does not exist. Check that the table name is
correct and in the proper case.
Also, the table may need to be
mappable.
No spatial object is contained
in the result of the spatial
query. Use the EasyLoader Upload
utility to make the table a
mappable table.
A query was made against a
non-spatial table. Check the query for possible
syntax errors. Also make sure
that the result of the query
includes the field specified in the
spatial column in the
MapInfo_MapCatalog.
Map appears to have
incorrect zoom level. For
example, the map may be
zoomed out too far to identify
any geography. The MBR for a DBMS layer is
determined by the
MapInfo_MapCatalog table.
The table extents in the
MapCatalog result in a different
zoom level than the one you
desire for your output. Edit the extents (DB_X_LL,
DB_X_UR, DB_Y_LL,
DB_Y_UR) in the
MapInfo_MapCatalog using the
MapInfo Professional MBX tool,
MISETMBR.MBX.