Release Notes
12c Release 1 (12.1)
E74140-01
October 2016
This document describes the features of Oracle Database on Fujitsu BS2000/OSD.
This release implements the features of Oracle Database 12c Release 1 Enterprise Edition. These features are listed and described in the generic Oracle Documentation and in Oracle Database Licensing Information and Oracle Database New Features Guide.
The following topics are covered in this chapter:
Oracle Database 12c Release 1 for Fujitsu BS2000/OSD (S series) is based on the /390 instruction set. It runs on the following Fujitsu BS2000 servers:
S Servers
SE Servers
SQ Servers
Oracle Database 12c Release 1 for Fujitsu BS2000/OSD (S series) runs on all Fujitsu BS2000 processors, in particular on the S servers and the /390-based system units of SE servers (SU /390).
Oracle Database 12c Release 1 for Fujitsu BS2000/OSD (S series) runs in the /390 compatibility mode on processors that are based on Intel x86 architecture. This applies for x86-based server units of the SE servers (SU x86) and for SQ servers.
Note:
Up to Oracle Database 11g Release 2, two software variants for the platform Fujitsu BS2000/OSD are released:
Oracle Database for Fujitsu BS2000/OSD (S Series)
Oracle Database for Fujitsu BS2000/OSD (SQ series)
Oracle Database for Fujitsu BS2000/OSD (SQ Series) is based on the Intel x86 instruction set. This variant runs on the Fujitsu BS2000 servers that are based on Intel x86 architecture, in particular on x86-based server units of the SE servers (SU x86) and on SQ servers.
Starting with Oracle Database 12c Release 1, a native variant for the Fujitsu BS2000 servers based on Intel x86 architecture will not be released. If you use Oracle Database 11g Release 2 for Fujitsu/BS2000 (SQ series), then you must upgrade to Oracle Database 12c Release 1 for Fujitsu BS2000/OSD (S series).
The logical and physical structure of a database does not depend on the Oracle Database software variant in use, Oracle Database 11g Release 2 for Fujitsu/BS2000 (S Series) or Fujitsu/BS2000 (SQ Series). Upgrade your database as described in Oracle Database Installation and Administration Guide for Fujitsu Siemens BS2000/OSD.
The following options are not supported on Oracle Database 12c Release 1 for Fujitsu BS2000/OSD:
Oracle Advanced Analytics
Oracle Database In-Memory
Oracle Data Mining
Oracle Database Vault
Oracle Label Security
Oracle On-Line Analytical Processing (OLAP)
Oracle RAC One Node
Oracle Real Application Clusters (Oracle RAC)
Oracle Spatial and Graph
Oracle TimesTen Application-Tier Database Cache (formerly known as Oracle In-Memory Database Cache)
The following features are not supported on Oracle Database 12c Release 1 for Fujitsu BS2000/OSD:
Cross Platform Transportable Tablespace
Database Configuration Assistant
Database Migration Assistant for Unicode
Database Upgrade Assistant
JIT in Oracle JavaVM
JavaScript Object Notification (JSON)
Native Compilation of Java and PL/SQL
OCCI
OPatch
Oracle Application Express
Oracle Automatic Storage Management
Oracle Configuration Manager
Oracle Direct NFS
Oracle Enterprise Manager Database Express
Oracle Globalization Development Kit
Oracle Heterogeneous Services
Oracle Instant Client
Oracle Java Server Pages
Oracle JDBC OCI drivers
Oracle Messaging Gateway
Oracle Multimedia
Oracle Secure Backup
Oracle Universal Installer
Oracle XML DB
Threaded Execution Mode
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 braces (for example, {). However, these characters can be stored as data.
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
.
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.
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.
A few initialization parameters in the INIT.ORA
file, described in the generic documentation are not supported by Oracle Database 12c Release 1 for BS2000/OSD. Refer to Oracle Database Installation and Administration Guide for Fujitsu Siemens BS2000/OSD for more information.
Consider the following information about Import and Export:
Avoid ASCII/EBCDIC conversions by the operating system, FTP, or PERCON. Import and Export utilities perform their own conversions. Additional conversions render the files unusable.
Import and export on tapes are not possible to or from more than one tape.
Consider the following information about Oracle Data Pump Import and Oracle Data Pump Export:
Avoid ASCII/EBCDIC conversions by the operating system, FTP, or PERCON. Oracle Data Pump Import and Oracle Data Pump Export utilities perform their own conversions. Additional conversions render the files unusable.
Tapes are not supported with Data Pump Export and Data Pump Import.
User-defined character sets implemented by Customizing Locale Data as described in Oracle Database Globalization Support Guide are not supported in this release.
The following features are currently not supported:
OCI shared mode functionality
OCI publish-subscribe functions
OCI Thread package
The following remarks relate to SQL*Plus:
SQL*Plus truncates and displays a warning message if the input lines exceed 511 characters.
If you use the SQL*Plus -s
option, then it must be the first option entered at the prompt.
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 must refer to the message number part of the second message.
See Also:
Oracle Database Error Messages Reference or Oracle Database Installation and Administration Guide for Fujitsu Siemens BS2000/OSD for more information about the error messageIf ECHO
is set to ON
, TAB
is set to ON,
and you specify a spool file, then the listing of commands may be misaligned.
When you connect from an Oracle Database 12c Release 1 client, such as SQL*Plus, that is running on an ASCII-based platform, such as Linux or Oracle Solaris, to an Oracle Database 12c Release 1 instance that is running on Fujitsu BS2000/OSD, then the connect fails with ORA-1821
error message if the NLS_LANG
environment variable is set.
This issue is tracked with Oracle bug 23266802.
This bug is fixed in Oracle Database 12c Release 2. If you use Oracle Database 12c Release 1 on the client side, then contact Oracle Support to request a patch for this bug.
This issue does not exist if you use previous Oracle Database releases on the client side, for example, Oracle Database 11g.
Oracle Database 10g clients can connect to Oracle Database 12c Release 1 instances on Fujitsu BS2000/OSD, if the initialization parameter SEC_CASE_SENSITIVE_LOGON
is set to FALSE
. Otherwise, the connection fails with the following message:
ORA-01017: invalid username/password; logon denied
The following data types are not supported:
Objects stored as VARRAYs
Objects (Simple and Nested ADTs without Collections)
XMLType data
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, then you must specify a log directory (trace directory) and a log file (trace file).
The listener can be started only if the POSIX subsystem is running.
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
Fujitsu documentation for TCP/IP on BS2000 recommends setting the privileged port to 2050. However, using a registered Oracle port number may cause conflicts. For example, if you set the port number for the listener process to 1521, then any Oracle process that tries to listen on such a registered port number may fail with the following error:
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.
You can find more details about service names and port numbers at
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml
Oracle® Database Release Notes, 12c Release 1 (12.1)
E74140-01
Copyright © 2016, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.