1 Release Notes

CPU

Any CPU supported by BS2000/OSD V5.0, V6.0, or V7.0, with the XS31 HSI.

Memory

Main memory must be at least 512 MB.

Terminal

9750-compatible.

Disk Space

Total static requirements for the Oracle Database software are approximately 700 000 PAM pages. Dynamic requirements (for example, SQL files, host language programs, output spool files) depend on Oracle Database usage.

Database Space

Minimum database (DB) size is about 200 000 PAM pages, and the minimum log file size is 10000 PAM pages. These values may be changed as part of the installation process.

Operating System

The following are the operating system requirements:

• BS2000/OSD V5.0C as of correction package 2/2006

• BS2000/OSD V6.0B

• BS2000/OSD V7.0

Communication System

One of the following communication systems is required:

• openNet Server V3.1 as of correction package 2/2006

• openNet Server V3.2

Language Compilers and Run-Time Environment for Oracle Applications

If high-level languages, such as C or COBOL, are used to interface with the Oracle Database, then the following versions are supported:

• COBOL85 Version V2.3

• COBOL2000 V1.2 and higher

• CPP V3.0 and higher

• CRTE 2.5 as of correction package 2/2006; V2.6 and higher

openUTM Software

You need openUTM V5.3.

Other Software

The following products are used during the installation and execution of the Oracle Database:

• CRTE-BASYS (V1.5 and higher)

• SDF

• SDF-P

• EDT

• LMS

For transferring the Oracle Database 10g software to your BS2000/OSD server during installation you need interNet Services ftp.

For Oracle Real Application Clusters you need the following:

• HIPLEX MSCF V3.0 and higher

• SM2 V14.0, openSM2 V6.0 and higher

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.

Oracle Spatial Data Option

The SDO_GEORASTER feature is not supported.

Oracle Real Application Clusters (Oracle RAC)

Oracle Clusterware is not supported. Consequently, Oracle Clusterware utilities like SRVCTL are not supported.

Oracle RAC on BS2000/OSD is based on the platform specific clusterware BS2000 HIPLEX MSCF.

Native Compilation of PL/SQL and Java

Native Compilation of PL/SQL and Java is not supported.

ALTER DATABASE … RESIZE

ALTER DATABASE ... RESIZE to make a database file smaller is not supported anymore on BS2000. This operation has no effect on the corresponding BS2000 files.

Database files can be resized larger however, both manually (with ALTER) and automatically as they fill (when a tablespace is defined with AUTOEXTEND).

IEEE Standard Floating Point Number Restrictions

The new 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 will produce unpredictable results with both local and remote Oracle databases.

Datatypes FLOAT and DOUBLE of SQL*Loader and External Tables

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 will produce unpredictable results.

Use the external, non-binary data type FLOAT EXTERNAL instead.

Oracle Scheduler

External Jobs are not supported

Oracle JDBC OCI Drivers

Oracle JDBC OCI drivers are not supported.

XML Database (XML DB)

The following components are not supported:

• WebDAV access

• HTTP access

• FTP access

Oracle XML Developers Kit (XDK)

Refer to the XML chapter in this guide.

BS2000/OSD file types of spool files

Oracle Database 10g release 2 can read SAM, ISAM, and PAM files and can create ISAM and PAM files. If you want the Oracle Database to write to a SAM file, then you need to preallocate the appropriate list or log file using the following BS2000 FILE command:

FCBTYPE=SAM

INIT.ORA parameters

A few initialization parameters in the INIT.ORA file, described in the generic documentation are not supported by Oracle Database 10g release 2 for BS2000/OSD. Refer to Appendix C, "Initialization Parameters and the Parameter File" for more information.

Archiving to Tape

Archiving to tape is not supported; log archive files must always be created as disk files. You may, however, use normal BS2000 backup procedures to back up the log archive files created by the archive process.

SQL*Loader

Multithreading functionality of direct path loads is not supported on BS2000

Import and Export

This section provides information about known problems and restrictions when using the Import and Export utilities.

• Avoid ASCII/EBCDIC conversions being done by the operating system, ftp, or PERCON. Import and Export perform their own conversions; additional conversions will render the files unusable.

• Import and Export on tapes are not possible to or from more than one tape.

Datapump Import and Datapump Export

This section provides information about known problems and restrictions when using Datapump Import and Datapump Export:

• Avoid ASCII/EBCDIC conversions being done by the operating system, ftp or PERCON. Import and Export perform their own conversions; additional conversions will render the files unusable.

• Tapes are not supported with Datapump Export and Datapump Import.

Globalization Support

User-defined character sets implemented by means of Customizing Locale Data (as described in the Oracle Database Globalization Support Guide) are not supported in this release.

Oracle Call Interface

The following features are currently not supported:

• OCI shared mode functionality

• OCI publish-subscribe functions

• OCI Thread package

SQL*Plus

The following remarks relate to SQL* Plus:

• SQL*Plus truncates input lines that exceed 511 characters. A warning message is displayed if the input lines exceed 511 characters.

• If you use the SQL*Plus -s option, it must be the first option entered at the prompt.

• Only the EDT editor is supported in this release. SQL*Plus accepts whatever editor you specify in the DEFINE_EDITOR command, but the editor is always EDT.

• The internal message buffer is limited to 76 characters, therefore, certain messages are truncated. This typically occurs if a message includes a second message. In such cases you will usually still refer to the message number part of the second message. For further information, refer to the manual relevant to the particular message, either the Oracle Database Error Messages, or Appendix A, "Oracle Error Messages for BS2000/OSD"of this guide.

• If ECHO is set to ON and TAB is set to ON and you specify a spool file, the listing of commands may be misaligned.

Oracle Net Services

The following remarks relate to Oracle Net Services:

• When you specify a name for the listener in the LISTENER.ORA file, Oracle recommends that the name is less than 20 characters long. If you use a listener name with more than 20 characters, you must specify a log directory (trace directory) and log file (trace file).

• The listener can be started only if the POSIX subsystem is running.

Oracle Net BEQ Protocol

The support of the handoff/direct handoff technique makes the BEQ protocol incompatible to the BEQ protocol of prior releases. For example, a 10g LISTENER cannot start a server of a 9i instance.

Oracle Protocol Support for TCP/IP

The Internet Assigned Numbers Authority (IANA) divided port numbers into three ranges:

• Well Known Ports from 0 through 1023

• Registered Ports from 1024 through 49151

• Dynamic, or Private Ports, or both, from 49152 through 65535

The Fujitsu Siemens documentation for TCP/IP on BS2000 recommends setting the privileged port to 2050. However, using a registered Oracle port number may cause conflicts (see http://www.iana.org/assignments/port-numbers). For example, if you set the port number for the listener process to 1521, any Oracle process, which should listen on such a registered port number, may fail with:

TNS-12545: Connect failed because target host or object does not exist
TNS-12560: TNS:protocol adapter error
TNS-00515: Connect failed because target host or object does not exist
BS2000 Error: 126: Can't assign requested address
BS2000 BCAM-RC: 40010020

The workaround is to use a non-privileged port, or to set the privileged port number to a value less than 1500, usually to 1024.

POSIX Subsystem

As a consequence of Java in the Database and the Oracle Management Agent, Oracle Database 10g on BS2000/OSD uses POSIX interfaces. For a non-POSIX user, this fact should not be visible with the following exceptions:

• You might get the following message:

  CCM0090: ALL UFS TERMINAL DEVICES ARE IN USE OR PERMISSION DENIED
  

  If the preceding message is displayed, you should ask the BS2000 administrator to increase the number of UFS devices (parameter NOSTTY in SYSSSI.POSIX-BC.version).

• The termination of the POSIX subsystem will also terminate the Oracle instance.

New Common Pool for Applications

Starting with Oracle Database 10g on BS2000, customer written applications use a separate shared code pool for common services such as Core, Globalization Support, and Net Services. The name of this new pool is "Client Common Pool". The placement of this pool can be controlled by the new ORAENV variable CLN_BASE.

This variable replaces the variable COM_BASE for customer written applications. The variable COM_BASE is now exclusively used for the server side common pool of the Oracle instance.

Subsystem POSIX Required

For proper execution of Oracle Database 10g on BS2000 the BS2000/OSD subsystem POSIX must be up and running.

ALTER DATABASE … RESIZE

ALTER DATABASE ... RESIZE to make a database file smaller is not supported anymore on BS2000/OSD (compared to Oracle9i on BS2000/OSD). This operation has no effect on the corresponding BS2000 files. However, database files can be resized to larger sizes.

Datatypes FLOAT and DOUBLE of SQL*Loader and External Tables

The binary data types FLOAT and DOUBLE of SQL*Loader are not supported anymore on BS2000/OSD (compared to Oracle9i on BS2000/OSD). Use the external, non-binary data type FLOAT EXTERNAL instead.

Default value of STATISTICS_LEVEL

The default value of the init.ora paramater STATISTICS_LEVEL has been changed to TYPICAL on BS2000/OSD. This is now the same default value as on the other Oracle platforms. In Oracle9i on BS2000/OSD, the default value was BASIC.

Obsolete ORAENV Variables

The following ORAENV variables are obsolete:

ALARM_TIMER_LIMIT
IMP_USERID_IGNORE