User`s guide

Known Restrictions, Problems, and Workarounds
Release Notes 1-3
■ Oracle Data Pump Import and Oracle Data Pump Export
■ Globalization Support
■ Oracle Call Interface
■ ADRCI
■ Connecting from Oracle Database 10g clients
■ Utilities in the POSIX environment
■ Oracle Net Services
■ Oracle Net BEQ Protocol
■ Oracle Protocol Support for TCP/IP
■ POSIX Subsystem
1.4.1 General Notes
The German characters ä, ö, ü and ß, cannot be used in the names of tables, columns,
fields, synonyms, and so on. This is because these characters are converted into
bracket symbols (for example, {). The characters can, however, be stored as data.
1.4.2 Oracle Spatial
The SDO_GEORASTER feature is not supported.
1.4.3 Oracle Real Application Testing
Workload Replay is not supported in this release.
1.4.4 ALTER DATABASE … RESIZE
The operation ALTER DATABASE ... RESIZE , to make a database file smaller, is not
supported on BS2000. This operation has no effect on the corresponding BS2000 files.
However, database files can be altered to larger sizes either manually, by using ALTER
or automatically, when a tablespace is defined with
AUTOEXTEND .
1.4.5 IEEE Standard Floating Point Number Restrictions
The BINARY FLOAT and BINARY DOUBLE data types are not supported for
customer-written database applications running on BS2000/OSD.
Attempts to store or fetch these types from an application program running on
BS2000/OSD produces unpredictable results with both local and remote Oracle
databases.
1.4.6 SQL*Loader
The binary data types FLOAT and DOUBLE of SQL*Loader are not supported on
BS2000/OSD. Using these data types with SQL*Loader and External Tables produces
unpredictable results.
Use the external, non-binary data type FLOAT EXTERNAL instead.
Multithreading functionality of direct path loads is not supported on BS2000.