This section contains corrections to the following Oracle Documentation for this release:
Section 4.1, "Oracle Automatic Storage Management Administrator's Guide"
Section 4.2, "Oracle Clusterware Administration and Deployment Guide"
Section 4.3, "Oracle Database Administrator's Guide"
Section 4.4, "Oracle Database JDBC Java API Reference"
Section 4.5, "Oracle Database New Features Guide"
Section 4.6, "Oracle Database PL/SQL Packages and Types Reference"
Section 4.7, "Oracle Database VLDB and Partitioning Guide"
Section 4.8, "Oracle Real Application Clusters Administration and Deployment Guide"
Section 4.9, "Oracle Text Reference"
In Oracle Automatic Storage Management Administrator's Guide, in the section "volcreate" under "ASMCMD Volume Management Commands," the following warning applies:
WARNING:
Specifying --redundancy
unprotected means that Oracle ASM mirroring is not available for data recovery with the Oracle ADVM volume. The redundancy setting (normal) of the disk group does not provide mirroring for an unprotected Oracle ADVM volume. The unprotected configuration is not recommended for production environments as intermittent storage access failures can result in the loss of data. Backups are strongly recommended.
Note the following changes with regard to the Oracle Clusterware Administration and Deployment Guide.
In the Chapter titled "Rapid Home Provisioning," a section with the following text describing how to delete a Rapid Home Provisioning Client should be added:
To delete a Rapid Home Provisioning Client, execute the following steps:
On the Rapid Home Provisioning Server:
To query the list of working copies that have been provisioned on the Rapid Home Provisioning Client cluster, execute the following command:
$ rhpctl query workingcopy -client <client_name>
For each of the working copies listed in the output of the command in Step 1.a, execute the following command:
$ rhpctl delete workingcopy -workingcopy <workingcopy_name>
To query the list of users from the Rapid Home Provisioning Client cluster, execute the following command:
$ rhpctl query user -client <client_name>
To delete the user listed in the output of the command in Step 1.c, execute the following command:
$ rhpctl delete user -user <username> -client <client_name>
On the Rapid Home Provisioning Client cluster, execute the following:
Stop the Rapid Home Provisioning Client daemon with the following command:
$ srvctl stop rhpclient
Delete the Rapid Home Provisioning Client configuration using the following command:
$ srvctl remove rhpclient
On the Rapid Home Provisioning Server cluster, execute the following command to delete the client site configuration:
$ rhpctl delete client -client <client_name>
Note the following changes with regard to the Oracle Database Administrator's Guide.
Starting Oracle Database 11gR2, JDBC clients can use OracleDriver
to establish connections to a database from a java application.
Registering the JDBC drivers is no longer a prerequisite.
In the Oracle Database New Features Guide, part number E17906-16, the section titled "New Predefined PL/SQL Inquiry Directives" incorrectly documented the name of two inquiry directives available in Oracle Database 12c Release 1 (12.1). The $$PLSQL_OWNER
and $$PLSQL_TYPE
inquiry directives should be $$PLSQL_UNIT_OWNER
and $$PLSQL_UNIT_TYPE
.
The listno
parameter of the DBMS_UTILITY
was inadvertently excluded from the Oracle Database PL/SQL Packages and Types Reference. For example, the GET_PARAMETER_VALUE
function should read as follows:
This function gets the value of specified initialization parameter.
Syntax
DBMS_UTILITY.GET_PARAMETER_VALUE ( parnam IN VARCHAR2, intval IN OUT BINARY_INTEGER, strval IN OUT VARCHAR2, listno IN BINARY_INTEGER DEFAULT 1) RETURN BINARY_INTEGER;
Parameters
Parameter | Description |
---|---|
parnam |
Parameter name. |
intval |
Value of an integer parameter or the value length of a string parameter. |
strval |
Value of a string parameter. |
listno |
List item number. If retrieving parameter values for a parameter that can be specified multiple times to accumulate values, use this parameter to get each individual parameter. |
In Oracle Database VLDB and Partitioning Guide, it was incorrectly documented that interval partitioning was supported with XMLIndex. XMLIndex only supports range, list and hash partitioning with schemes.
Note the following changes with regard to the Oracle Real Application Clusters Administration and Deployment Guide.
In the section titled "Overview of In-Memory Column Store with Oracle RAC" in the Oracle Real Application Clusters Administration and Deployment Guide, the paragraph that begins with "On an Engineered System an object ..." needs to be changed to read as follows:
On an Engineered System, it is possible to duplicate or mirror objects populated in memory across the In-Memory Column Store (IM column store) in the cluster. This provides the highest level of redundancy. The DUPLICATE
clause is used to control how an object should be duplicated across the IM column stores in the cluster. If you specify just DUPLICATE
, then one mirrored copy of the data is distributed across the IM column stores in the cluster. If you want to duplicate the entire object in each IM column store in the cluster, specify DUPLICATE ALL
.
Note the following changes with regard to the Oracle Text Reference.
In the sub-section titled "Notes" under the main section titled "ALTER INDEX" in the Oracle Text Reference, the following item should be documented in the bulleted list:
You cannot have embedded blanks in section and field names.
According to Bug 21330358, field names cannot use embedded blanks. For example, my section
is an invalid section name since there is a blank just after my
. This applies to field names that are defined using "".
In Appendix B titled "Oracle Text Supported Document Formats" of the Oracle Text Reference Oracle Text does not extract text for the following file formats:
IBM Lotus Notes NSF (File ID) 7.x, 8.x
IBM Lotus Notes NSF (Windows, Linux x86-32 and Oracle Solaris 32-bit only with Notes Client or Domino Server) 8.x