Pitney Bowes MapInfo Professional - Manual (Page 198)

If you try to save a map with unsupported spatial geometry types in Oracle, these are the results:
• Spatial Geometry Types with All Unsupported Objects: If you have created a map that might
contain all of the unsupported objects and you are trying to save to Oracle, this message displays:
Table has unsupported objects (rounded rectangles, rectangles,
ellipses or arcs). Convert to regions and/or polylines?
Click Yes to convert the unsupported objects to regions or polylines; you would select No to decline
to convert the unsupported objects. If you decline, you cannot save the map you have created to the
Oracle database. A confirmation message explains that the operation is canceled.
• Spatial Geometry types with Region Objects Only: If you have created a map that contains region
objects only and you are trying to save to Oracle, this message displays:
Table has unsupported objects (rounded rectangles, rectangles, or
ellipses). Convert to regions?
Click Yes to convert the unsupported objects to regions; you would select No to decline to convert the
unsupported objects. If you decline, you cannot save the map you have created to the Oracle database.
• For Spatial Geometry types with Line Objects Only: If you have created a map that contains line
objects only and you are trying to save to Oracle, this message displays:
Arc is an unsupported object. Convert to polylines?
Click Yes to convert the unsupported objects to polylines; you would select No to decline to convert
the unsupported objects. If you decline, you cannot save the map you have created to the Oracle
database.
Oracle Operating System Authentication and Configuration
When you choose OS authentication for a user, the user account is maintained by the Oracle database,
but password administration and user authentication is performed by the Operating System (OS). With
OS authentication, your database relies on the underlying operating system to restrict access to database
accounts. A database password is not used for this type of login.
By default, Oracle allows operating-system-authenticated logins only over secure connections, which
precludes using Oracle .NET and a shared server configuration. This default restriction prevents a remote
user from impersonating another operating system user over a network connection.
Setting REMOTE_OS_AUTHENT to TRUE in the database initialization parameter file forces the RDBMS
to accept the client operating system user name received over a non-secure connection and use it for
account access.
Any change to this parameter takes effect the next time you start the instance and mount the database.
Generally, user authentication through the host operating system offers faster and more convenient
connection to Oracle without specifying a separate database user name or password. Also, user entries
correspond in the database and operating system audit trails.
Setting Prefix for OS Authenticated User
Set the initialization parameter OS_AUTHENT_PREFIX, and use this prefix in the Oracle database user
names. The OS_AUTHENT_PREFIX parameter defines a prefix that the Oracle database adds to the
beginning of every user's operating system account name. When a user attempts to connect, Oracle
compares the prefixed user name with the Oracle user names in the database.
For example, assume that OS_AUTHENT_PREFIX is set as follows:
OS_AUTHENT_PREFIX=OPS$
The initialization parameter OS_AUTHENT_PREFIX is case-sensitive in some operating systems.
Refer to your operating system specific Oracle documentation for more information about this
initialization parameter. Note:
If a user named tsmith is to connect to an Oracle database installation and be authenticated by the
Operating System, then the Oracle database checks whether a corresponding database user OPS$tsmith
MapInfo Professional 12.5 198
Working with Remote Tables from Specific Databases