Oracle® Database Patch 19121551

Skip Headers

Oracle® Database

Patch 19121551 - Database Patch Set Update 11.2.0.4.4 (Includes CPUOct2014)

 

Released: October 14, 2014

This document is accurate at the time of release. For any changes and additional information regarding PSU 11.2.0.4.4, see these related documents that are available at My Oracle Support (http://support.oracle.com/):

• Document 1912224.1 Patch Set Update and Critical Patch Update October 2014 Availability Document

• Document 854428.1 Patch Set Updates for Oracle Products

• Document 1911774.1 Oracle Database Patch Set Update 11.2.0.4.4 Known Issues

This document includes the following sections:

• Section 1, "Patch Information"

• Section 2, "Prerequisites"

• Section 3, "Installation"

• Section 4, "Deinstallation"

• Section 5, "Known Issues"

• Section 6, "References"

• Section 7, "Bugs Fixed by This Patch"

• Section 8, "Documentation Accessibility"

1 Patch Information

Patch Set Update (PSU) patches are cumulative. That is, the content of all previous PSUs is included in the latest PSU patch.

PSU 11.2.0.4.4 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".

To install the PSU 11.2.0.4.4 patch, the Oracle home must have the 11.2.0.4.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 11.2.0.4.0 or any PSU with a lower 5th numeral version than the one being installed.

This patch is Oracle RAC Rolling Installable.

This patch is Data Guard Standby-First Installable. See My Oracle Support Document 1265700.1 Oracle Patch Assurance - Data Guard Standby-First Patch Apply for details on how to remove risk and reduce downtime when applying this patch.

This patch contains a security fix due to which a SELECT query's plan MAY change under the following conditions:

• The SELECT queries a table protected with a Fined Grained Auditing policy

• And the policy condition is NULL

Table 1 describes installation types and security content. For each installation type, it indicates the most recent PSU patch to include new security fixes that are pertinent to that installation type. If there are no security fixes to be applied to an installation type, then "None" is indicated. If a specific PSU is listed, then applythat or any later PSU patch to be current with security fixes.

Table 1 Installation Types and Security Content

Installation Type	Latest PSU with Security Fixes
Server homes	PSU 11.2.0.4.4
Client-Only Installations	None
Instant Client Installations	None (The Instant Client installation is not the same as the client-only Installation. For additional information about Instant Client installations, see Oracle Call Interface Programmer's Guide.)

2 Prerequisites

This section includes the following section:

• Section 2.1, "OPatch Utility"

2.1 OPatch Utility

You must use the OPatch utility version 11.2.0.3.6 or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 11.2, which is available for download from My Oracle Support patch 6880880 by selecting the 11.2.0.0.0 release.

For information about OPatch documentation, including any known issues, see My Oracle Support Document 293369.1 OPatch documentation list.

3 Installation

These instructions are for all Oracle Database installations.

• Section 3.1, "Patch Pre-Installation Instructions"

• Section 3.2, "Patch Installation Instructions"

• Section 3.3, "Patch Post-Installation Instructions"

• Section 3.4, "Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of PSU 11.2.0.4.4 in the Oracle Home"

3.1 Patch Pre-Installation Instructions

Before you install PSU 11.2.0.4.4, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.

• Section 3.1.1, "Applying Database PSU Along Side the Oracle JavaVM Component 11.2.0.4.1 Database PSU Patch"

• Section 3.1.2, "Environments with Grid Infrastructure (GI)"

• Section 3.1.3, "Environment Checks"

• Section 3.1.4, "One-off Patch Conflict Detection and Resolution"

3.1.1 Applying Database PSU Along Side the Oracle JavaVM Component 11.2.0.4.1 Database PSU Patch

From October 2014 onwards, the Oracle JavaVM Component 11.2.0.4.1 Database PSU patch is also available as a separate patch. This patch is not Oracle RAC Rolling Installable. For customers wanting to install both patches together during a single downtime window, follow the various Patching Options listed in the My Oracle Support Document 1929745.1 - Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches.

3.1.2 Environments with Grid Infrastructure (GI)

If you are installing the PSU to an environment that has a Grid Infrastructure (GI) home, note the following:

• Grid Infrastructure PSU 11.2.0.4.4 Patch 19380115 should be applied to the Grid Infrastructure home and Database home using the readme instructions provided with the patch.

3.1.3 Environment Checks

1. Ensure that the $PATH definition has the following executables: make, ar, ld, and nm.

   The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin, in which case you can set your PATH definition as follows:

   export PATH=$PATH:/usr/ccs/bin
   

3.1.4 One-off Patch Conflict Detection and Resolution

For an introduction to the PSU one-off patch concepts, see "Patch Set Updates Patch Conflict Resolution" in My Oracle Support Document 854428.1 Patch Set Updates for Oracle Products.

The fastest and easiest way to determine whether you have one-off patches in the Oracle home that conflict with the PSU, and to get the necessary conflict resolution patches, is to use the Patch Recommendations and Patch Plans features on the Patches & Updates tab in My Oracle Support. These features work in conjunction with the My Oracle Support Configuration Manager. Recorded training sessions on these features can be found in Document 603505.1.

However, if you are not using My Oracle Support Patch Plans, the My Oracle Support Conflict Checker tool enables you to upload an OPatch inventory and check the patches that you want to apply to your environment for conflicts.

If no conflicts are found, you can download the patches. If conflicts are found, the tool finds an existing resolution to download. If no resolution is found, it will automatically request a resolution, which you can monitor in the Plans and Patch Requests region of the Patches & Updates tab.

For more information, see Knowledge Document 1091294.1, How to use the My Oracle Support Conflict Checker Tool.

Or, use the following steps to manually discover conflicts and resolutions:

1. Determine whether any currently installed one-off patches conflict with the PSU patch as follows:

   unzip p19121551_112040_<platform>.zip
   cd 19121551
   opatch prereq CheckConflictAgainstOHWithDetail -ph ./
   

2. The report will indicate the patches that conflict with PSU 19121551 and the patches for which PSU 19121551 is a superset.

   Note that Oracle proactively provides PSU 11.2.0.4.4 one-off patches for common conflicts.

3. Use My Oracle Support Document 1321267.1 Database Patch conflict resolution to determine, for each conflicting patch, whether a conflict resolution patch is already available, and if you need to request a new conflict resolution patch or if the conflict may be ignored.

4. When all the one-off patches that you have requested are available at My Oracle Support, proceed with Section 3.2, "Patch Installation Instructions".

3.2 Patch Installation Instructions

Conflicting patches should be rolled back before applying the patch, otherwise opatch apply will report conflicts again.

Follow these steps:

1. If you are using a Data Guard Physical Standby database, you must install this patch on both the primary database and the physical standby database, as described by My Oracle Support Document 278641.1.

2. If this is an Oracle RAC environment, install the PSU patch using the OPatch rolling (no downtime) installation method as the PSU patch is rolling Oracle RAC installable. Refer to My Oracle Support Document 244241.1 Rolling Patch - OPatch Support for RAC.

3. If this is not a Oracle RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.

4. Rollback any patches found during the One-off Patch Conflict Detection.

5. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:

   unzip p19121551_112040_<platform>.zip
   cd 19121551
   opatch apply
   

6. Install all resolutions to conflicts found during the One-off Patch Conflict Detection.

7. If there are errors, refer to Section 5, "Known Issues".

3.3 Patch Post-Installation Instructions

After installing the patch, perform the following actions:

1. Apply conflict resolution patches as explained in Section 3.3.1.

2. Load modified SQL files into the database, as explained in Section 3.3.2.

3.3.1 Applying Conflict Resolution Patches

Apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section 3.1.4, "One-off Patch Conflict Detection and Resolution".

3.3.2 Loading Modified SQL Files into the Database

The following steps load modified SQL files into the database. For an Oracle RAC environment, perform these steps on only one node.

1. For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA and run thecatbundle.sql script as follows:

   cd $ORACLE_HOME/rdbms/admin
   sqlplus /nolog
   SQL> CONNECT / AS SYSDBA
   SQL> STARTUP
   SQL> @catbundle.sql psu apply
   SQL> QUIT
   

   The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series PSU.

   For information about the catbundle.sql script, see My Oracle Support Document 605795.1 Introduction to Oracle Database catbundle.sql.

2. Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle or $ORACLE_BASE/cfgtoollogs/catbundle for any errors:

   catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.log
   catbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log
   

   where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 5, "Known Issues".

3.4 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of PSU 11.2.0.4.4 in the Oracle Home

There are no actions required for databases that have been upgraded or created after installation of PSU 11.2.0.4.4.

4 Deinstallation

These instructions apply if you need to deinstall the patch.

• Section 4.1, "Patch Deinstallation Instructions for a Non Oracle RAC Environment"

• Section 4.2, "Patch Post-Deinstallation Instructions for a Non Oracle RAC Environment"

• Section 4.3, "Patch Deinstallation Instructions for an Oracle RAC Environment"

• Section 4.4, "Patch Post-Deinstallation Instructions for an Oracle RAC Environment"

4.1 Patch Deinstallation Instructions for a Non Oracle RAC Environment

Follow these steps:

1. Verify that an $ORACLE_HOME/rdbms/admin/catbundle_PSU_<database SID>_ROLLBACK.sql file exists for each database associated with this ORACLE_HOME. If this is not the case, you must execute the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" against the database before deinstalling the PSU.

2. Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.

3. Run the OPatch utility specifying the rollback argument as follows.

   opatch rollback -id 19121551
   

4. If there are errors, refer to Section 5, "Known Issues".

4.2 Patch Post-Deinstallation Instructions for a Non Oracle RAC Environment

Follow these steps:

1. Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)

2. For each database instance running out of the ORACLE_HOME, connect to the database using SQL*Plus as SYSDBA and run the rollback script as follows:

   cd $ORACLE_HOME/rdbms/admin
   sqlplus /nolog
   SQL> CONNECT / AS SYSDBA
   SQL> STARTUP
   SQL> @catbundle_PSU_<database SID>_ROLLBACK.sql
   SQL> QUIT
   

   In an Oracle RAC environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.

3. Check the log file for any errors. The log file is found in $ORACLE_BASE/cfgtoollogs/catbundle and is named catbundle_PSU_<database SID>_ROLLBACK_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 5, "Known Issues".

4.3 Patch Deinstallation Instructions for an Oracle RAC Environment

Follow these steps for each node in the cluster, one node at a time:

1. Shut down the instance on the node.

2. Run the OPatch utility specifying the rollback argument as follows.

   opatch rollback -id 19121551
   

   If there are errors, refer to Section 5, "Known Issues".

3. Start the instance on the node as follows:

   srvctl start instance –d <db-unique-name> -n <nodename>
   

4.4 Patch Post-Deinstallation Instructions for an Oracle RAC Environment

Follow the instructions listed in Section Section 4.2, "Patch Post-Deinstallation Instructions for a Non Oracle RAC Environment" only on the node for which the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" were executed during the patch application.

All other instances can be started and accessed as usual while you are executing the deinstallation steps.

5 Known Issues

For information about OPatch issues, see My Oracle Support Document 293369.1 OPatch documentation list.

For issues documented after the release of this PSU, see My Oracle Support Document 1911774.1 Oracle Database Patch Set Update 11.2.0.4.4 Known Issues.

Other known issues are as follows.

Issue 1   

The following ignorable errors may be encountered while running the catbundle.sql script or its rollback script:

ORA-29809: cannot drop an operator with dependent objects
ORA-29931: specified association does not exist
ORA-29830: operator does not exist
ORA-00942: table or view does not exist
ORA-00955: name is already used by an existing object
ORA-01430: column being added already exists in table
ORA-01432: public synonym to be dropped does not exist
ORA-01434: private synonym to be dropped does not exist
ORA-01435: user does not exist
ORA-01917: user or role 'XDB' does not exist
ORA-01920: user name '<user-name>' conflicts with another user or role name
ORA-01921: role name '<role name>' conflicts with another user or role name
ORA-01952: system privileges not granted to 'WKSYS'
ORA-02303: cannot drop or replace a type with type or table dependents
ORA-02443: Cannot drop constraint - nonexistent constraint
ORA-04043: object <object-name> does not exist
ORA-29832: cannot drop or replace an indextype with dependent indexes
ORA-29844: duplicate operator name specified 
ORA-14452: attempt to create, alter or drop an index on temporary table already in use
ORA-06512: at line <line number>. If this error follow any of above errors, then can be safely ignored.
ORA-01927: cannot REVOKE privileges you did not grant

Issue 2   

Warnings may be returned during the re-link phase of 19121551. These warnings may be ignored.

warning: overriding commands for target `nmosudo'
warning: ignoring old commands for target `nmosudo'

See the following document for additional information.

Document 1562458.1 Relinking the DB Control 11.2.0.3 Agent Displays a Warning Message "overriding commands for target 'nmosudo'"

Issue 3   

On HP-UX systems, the following ignorable warnings may be encountered during the relinking of the oracle binary:

WARNING:OUI-67215:
OPatch found the word "failed" in the stderr of the make command.Please look at this stderr. You can re-run this make command.
 
cc: warning 487: Possibly incorrect message catalog.
total_lntt_bytes is 0, assuming size of .debug_lntt
Failed to mmap lntt temp file.

Issue 4   

On AIX systems, the following ignorable warnings may be encountered during the relinking of the oracle binary:

WARNING:OUI-67215:
OPatch found the word "failed" in the stderr of the make command.Please look at this stderr. You can re-run this make command.

ld: 0711-224 WARNING: Duplicate symbol: <symbol>
ld: 0711-345 WARNING: Duplicate symbol: <symbol>
ld: 0711-773 WARNING: Duplicate symbol: <symbol>
ld: 0711-783 WARNING: Duplicate symbol: <symbol>
ld: 0711-301 WARNING: Duplicate symbol: <symbol>
ld: 0711-415 WARNING: Duplicate symbol: <symbol>
ld: 0711-319 WARNING: Duplicate symbol: <symbol>

Issue 5   

On IBM: Linux on System Z, the following ignorable warnings may be encountered during relinking of e2eme binary:

OUI-67215:
OPatch found the word "warning" in the stderr of
the make command.

Please look at this stderr. You can re-run this
make command.
Stderr output:
ins_emagent.mk:113: warning: overriding commands for target `nmosudo'
ins_emagent.mk:52: warning: ignoring old
commands for target `nmosudo'

Issue 6   

If Oracle Database Vault is enabled, the following error can occur during the execution of the Post Installation or Deinstallation steps:

initjvmaux.drop_sros();
 
EXECUTE IMMEDIATE 'create or replace java system';
...
ORA-01031: insufficient privileges
ORA-06512: at "SYS.INITJVMAUX", line 535
ORA-06512: at line 3

To recover from this issue, see the following My Oracle Support Document 1935120.1 ORA-01031 during Post Install / De-install for Database PSU or OJVM PSU

6 References

The following documents are references for this patch.

Document 293369.1 OPatch documentation list

Document 360870.1 Impact of Java Security Vulnerabilities on Oracle Products

Document 1321267.1 Database Patch conflict resolution

Document 19121551.8 Database 11.2.0.4.4 Patch Set Update (PSU)

Document 1449750.1 11.2.0.4 Patch Set Updates - List of Fixes in each PSU

Document 1561792.2 Patching Assistant: Oracle Database/Client - Select PSU/SPU (aka CPU)

7 Bugs Fixed by This Patch

This patch includes the following bug fixes.

7.1 CPU Molecules

CPU molecules in PSU 11.2.0.4.4:

PSU 11.2.0.4.4 contains the following new PSU 11.2.0.4.4 molecules:

	19463893 - DB-11.2.0.4-MOLECULE-009-CPUOCT2014
	19463897 - DB-11.2.0.4-MOLECULE-010-CPUOCT2014
	19466309 - DB-11.2.0.4-MOLECULE-011-CPUOCT2014
	19544839 - DB-11.2.0.4-MOLECULE-012-CPUOCT2014
	19584068 - DB-11.2.0.4-MOLECULE-013-CPUOCT2014

7.2 Bug Fixes

See My Oracle Support Document 1611785.1 that documents all the non-security bugs fixed in each 11.2.0.4 Patch Set Update (PSU).

PSU 11.2.0.4.4 contains the following new fixes:

Advance Queuing

   14764829 - ORA-600 [KWQICGPC:CURSTA] WHEN USING AQ

Automatic Storage Management

   13955826 - ORA-15133 AND ORA-600 [KFGFINALIZE_2] IN ASM

Buffer Cache Management

   12747740 - NODE JOIN RECONFIGURATION (PCMREPLAY) DOES NOT SCALE WITH MORE LMS'S
   16494615 -  READ BY OTHER SESSION WAITS ON UNDO BLOCK
   17390160 - KCBL STATE OBJECT SEARCH CAN CAUSE CPU REGRESSION
   17586955 - ORA-600 [KTSPFMDB:OBJDCHK_KCBNEW_3]
   17951233 - ORA-600 [KCBLIN_3] [103] AFTER SETTING _PGA_MAX_SIZE AT 4G

Enterprise Manager

   18673304 - Fix for bug 18673304
   18673325 - Fix for bug 18673325
   18673342 - Fix for bug 18673342
   19211724 - Fix for bug 19211724

Generic

   9756271 - SOME SQL STATEMENTS INVOLVING CONNECT BY OR RECURSIVE WITH MAY CAUSE SEGV
   14245531 - LARGE AMOUNT OF TEMP SPACE IS USED DURING IAS LOADING
   16042673 - DATABASE HANG WHEN SYSTEM TRYING TO ADD INTERVAL PARTITION TO THE TABLE
   17037130 - EXADATA: ORA-4031 WITH HUGE ALLOCATION IN PRTMV
   17040527 - ALTER STORAGE (BUFFER_POOL KEEP) DOESN'T WORK UNTIL FLUSH LIBRARY CACHE
   17242746 - ORA-4025 ON RECURSIVE SQL FROM PLSQL
   17267114 - INVALID DATA IN SYS.TYPE$ WAS CAUSING DBMS_PICKLER.GET_METADATA ROUTINE TO FAIL
   17449815 - ORA-8102 ORA-1499 AFTER ORA-1/ORA-2291 BY MERGE WITH DML ERROR LOGGING
   17570240 - >6% REGRESSION SEEN IN PROFILE FROM NEW KPOSPFDRV OF WHICH 50% FROM SPRINTF
   17587063 - ORA-600 [QERGHFETCH:INC] REPORTED ON QUERY WITH CURSOR_SHARING=FORCE
   17705023 - ORA-600 [KKZUASID] ON MV REFRESH
   17824637 - ORA-1403 AFTER SESSION CONTEXT CHANGE
   17842825 - ORA-600 [KQRFRPO] AND INSTANCE CRASH
   17891946 - RCA: INSTANCE CRASH BY USER PROCESS
   17982555 - ORA-4020: DEADLOCK DETECTED WHILE TRYING TO LOCK OBJECT FUSION.SYS_PLSQ
   18199537 - "CHILD ROW CACHE OBJECTS" LATCH CONTENTION AND CONNECTING DB HANG
   18230522 - CORE DUMP WITH REFERENCE PARTITIONED OBJECTS AND FULL PARTITION-WISE JOIN
   18436307 - TRIGGER 'WHEN CONDITION' RETURNING FALSE WHEN TABLE HAS A SECURITY DBA_POLICY
   18973907 - NEW REMOTE RPC FOR NULL INDEX STATS HAS BEEN REMOVED
   19458377 - CHECKS TO ENSURE COMPATIBILITY OF BUNDLES WITH JOX CHANGES
   19554106 - CONFLICT RESOLVING FIX FOR BUNDLES FOR JOX CHANGES

High Availability

   14285317 - RMAN DUPLICATE FAILS ORA-01507 IF SOURCE HAS ARCHIVELOG MODE AND COLD BACKUP
   16692232 - RMAN BACKUP ARCHIVELOG ALL NOT BACKED UP DELETE ALL INPUT DOESNOT WORK AS EXPECT
   17006183 - ARCHIVER CONFUSES DESTINATIONS FOR EOR ARCHIVELOG UPON ROLECHANGE TO PRIMARY
   17232014 - INITIAL ALLOCATION FOR KJBR&KJBL ARE TOO LOW W/ LARGE CACHES DUE TO UB4 OVERFLOW
   17237521 - DELAY IN ARC0 STARTING UP
   18009564 - RMAN IS SENDING WRONG INFORMATION TO MML, THUS MML IS FAILING
   18280813 - INSERT /*+ APPEND */ STUCK IN GC CURRENT REQUEST

JavaVM

   19289642 - Fix for bug 19289642

Oracle Multimedia

   18262334 - PROCESSCOPY TO JPEG IMAGE FAILED FOR INDEX COLOR IMAGE

Oracle Security

   16524926 - APEX: ORA-1031 WITH ORACLE MULTIMEDIA AND REALM PROTECTED DB SCHEMA
   18264060 - AUDIT_TRAIL=*,EXTENDED DOES NOT WRITE BIND CORRECTLY WITH 16817814 FIX

Oracle Space Management

   14829250 - ET12.1TXN: ORA-7445 [KTBDBH] ON A MERGE TABLE

Oracle Transaction Management

   11733603 - ORA-54 WITH SELECT STATEMENT USING NOWAIT CLAUSE WITH NO CONCURRENT ACTIVE TX
   17787259 - TURNING MINACTSCN DUMP OFF SHOULD BE POSSIBLE

Oracle Utilities

   17036973 - CRASH IN CLUSTER_SET 

Oracle Virtual Operating System Services

   14657740 - ORA-600 [510] [0X2E4781268] [CACHE BUFFERS CHAINS]
   17299889 - XDB QUERIES ARE SLOW DUE TO TIME SPENT IN KGHFREMPTY
   18191164 - PERFORMANCE ISSUE SEEN WITH DIRECT NFS DUE TO SPIN IN RECONNECT CODE PATH
   18328509 - ORA-4030 AFTER UPGRADE TO 11.2.0.4 WITH SHARED SERVER AND JDBC THIN CLIENT

PL/SQL

   18641419 - Fix for bug 18641419

Patch Automation

   17343514 - REMOVE JAVA FROM CATBUNDLE
   19727057 - HANDLE JVMPSU.SQL IN CATBUNDLE

Server Manageability

   14084247 - STBH: ORA-1555 DUE TO WRH$_ACTIVE_SESSION_HISTORY NOT PURGED
   17042658 - ORA-600 [KEWRSP_SPLIT_PARTITION_2] ON UPGRADE FROM 11.2 TO 12.1

XML Database

   16198143 - WHILE USING DATA REDACTION  THERE ARE CHANGES FOR A CRASH  IN QMXSAXCREATEDOCTYP

8 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website athttp://www.oracle.com/us/corporate/accessibility/index.html.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visithttp://www.oracle.com/accessibility/support.html if you are hearing impaired.

---

Patch 19121551 - Database Patch Set Update 11.2.0.4.4 (Includes CPUOct2014) for UNIX

Copyright © 2006, 2014, 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 RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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 licensed through X/Open Company, Ltd.

This software or hardware and documentation may provide access to or information on 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. 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.

---

Copyright © 2006, 2014, Oracle and/or its affiliates. All rights reserved.

来自为知笔记(Wiz)