Skip Headers

Oracle® Database

Patch 17552800 - 12.1.0.1.2 Patch Set Update

 

Released: January 14, 2014

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

This document includes the following sections:

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 12.1.0.1.2 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".

To install the PSU 12.1.0.1.2 patch, the Oracle home must have the 12.1.0.1.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 12.1.0.1.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 apply that 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 12.1.0.1.2


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:

2.1 OPatch Utility

You must use the OPatch utility version 12.1.0.1.1 or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 12.1, which is available for download from My Oracle Support patch 6880880 by selecting the 12.1.0.1.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.

3.1 Patch Pre-Installation Instructions

Database PSU 12.1.0.1.2 is packaged as a non-composite patch and hence installing it will rollback the prior PSU 12.1.0.1.1 and all 12.1.0.1.1 overlay patches applied. This will increase the downtime necessary to perform the installation. Before you install PSU 12.1.0.1.2, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.

3.1.1 Environments with Grid Infrastructure

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

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

3.1.2 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.3 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, follow these steps:

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

    unzip p17552800_12101_<platform>.zip
    cd 17552800
    opatch prereq CheckConflictAgainstOHWithDetail -ph ./
    
  2. The report will indicate the patches that conflict with PSU 17552800 and the patches for which PSU 17552800 is a superset.

    Note that Oracle proactively provides PSU 12.1.0.1.2 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

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 a RAC environment, install the PSU patch using the OPatch rolling (no downtime) installation method as the PSU patch is rolling RAC installable. Refer to My Oracle Support Document 244241.1 Rolling Patch - OPatch Support for RAC.

  3. If this is not a 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. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:

    unzip p17552800_12101_<platform>.zip
    cd 17552800
    opatch apply
    
  5. 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. Upgrade Oracle Recovery Manager catalog, as explained in Section 3.3.3.

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.3, "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 a RAC environment, perform these steps on only one node.

  1. For each database instance running on the Oracle home being patched, run the datapatch utility as described in Table 2.

    Table 2 Steps to Run the datapatch Utility for Single Tenant Versus Multitenant (CDB/PDB)

    Steps Single Tenant (non-CDB/PDB) Steps Multitenant (CDB/PDB)

    1

    % sqlplus /nolog

    1

    % sqlplus /nolog

    2

    SQL> Connect / as sysdba

    2

    SQL> Connect / as sysdba

    3

    SQL> startup

    3

    SQL> startup

    4

    SQL> quit

    4

    SQL> alter pluggable database all open;Foot 1 

    5

    % cd $ORACLE_HOME/OPatch

    5

    SQL> quit

    6

    % ./datapatch -verbose

    6

    % cd $ORACLE_HOME/OPatch



    7

    % ./datapatch -verbose


    Footnote 1 It is recommended the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open ) could be substituted to only open certain PDBs in the multitenant database. Doing so will result in the Post Install step only being run on the CDB and opened PDB's. To update a pluggable database at a later date (skipped or newly plugged in), open the database using the alter pluggable database command mentioned previously and rerun the datapatch utility.

    The datapatch utility will then run the necessary apply scripts to load the modified SQL files into the database. An entry will be added to the dba_registry_history and dba_registry_sqlpatch views reflecting the patch application. In the dba_registry_sqlpatch view, verify the Status for the APPLY is "SUCCESS". For any other status, refer to the following My Oracle Support note for additional information and actions: Document 1609718.1 What to do if the status of a datapatch action was not SUCCESS.

  2. Check the following log files in $ORACLE_HOME/sqlpatch/17552800/ for errors:

    17552800_apply_<database SID>_<CDB name>_<timestamp>.log
    

    where database SID is the database SID, CDB name is the name of the multitenant container database, and timestamp is of the form YYYYMMMDD_HH_MM_SS.

    In addition, you can check the log files for catbundle 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.3.3 Upgrade Oracle Recovery Manager Catalog

If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it:

$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;

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

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

4 Deinstallation

These instructions apply if you need to deinstall the patch.

4.1 Patch Deinstallation Instructions for a Non-RAC Environment

Follow these steps:

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

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

    opatch rollback -id 17552800
    
  3. If there are errors, refer to Section 5, "Known Issues".

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

Follow these steps:

  1. For each database instance running on the Oracle home being patched, run the datapatch utility as described in Table 3.

    Table 3 Steps to Run the datapatch Utility for Single Tenant Versus Multitenant (CDB/PDB)

    Steps Single Tenant (non-CDB/PDB) Steps Multitenant (CDB/PDB)

    1

    % sqlplus /nolog

    1

    % sqlplus /nolog

    2

    SQL> Connect / as sysdba

    2

    SQL> Connect / as sysdba

    3

    SQL> startup

    3

    SQL> startup

    4

    SQL> quit

    4

    SQL> alter pluggable database all open;Foot 1 

    5

    % cd $ORACLE_HOME/OPatch

    5

    SQL> quit

    6

    % ./datapatch -verbose

    6

    % cd $ORACLE_HOME/OPatch



    7

    % ./datapatch -verbose


    Footnote 1 It is recommended the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open ) could be substituted to only open certain PDBs in the multitenant database. Doing so will result in the Post Install step only being run on the CDB and opened PDB's. To update a pluggable database at a later date (skipped or newly plugged in), open the database using the alter pluggable database command mentioned previously and rerun the datapatch utility.

    The datapatch utility will then run the necessary rollback scripts. An entry will be added to the dba_registry_history and dba_registry_sqlpatch views reflecting the patch application. In the dba_registry_sqlpatch view, verify the Status for the ROLLBACK is "SUCCESS". For any other status, refer to the following My Oracle Support note for additional information and actions: Document 1609718.1 What to do if the status of a datapatch action was not SUCCESS.

  2. Check the following log files in $ORACLE_HOME/sqlpatch/17552800/ for errors:

    17552800_apply_<database SID>_<CDB name>_<timestamp>.log
    

    where database SID is the database SID, CDB name is the name of the multitenant container database, and timestamp is of the form YYYYMMMDD_HH_MM_SS.

    In addition, you can check the log files 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 a 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 17552800
    

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

  3. Start the instance on the node as follows:

    srvctl start instance
    

4.4 Patch Post-Deinstallation Instructions for a RAC Environment

Follow the instructions listed in Section Section 4.2, "Patch Post-Deinstallation Instructions for a Non-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 1593199.1 Oracle Database Patch Set Update 12.1.0.1.2 Known Issues.

Other known issues are as follows.

Issue 1   

The following ignorable errors may be encountered while running the datapatch/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

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 17552800.8 Database 12.1.0.1.2 Patch Set Update (PSU)

Document 1591141.1 12.1.0.1 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 Bug Fixes

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

PSU 12.1.0.1.2 contains the following new fixes:

Automatic Storage Management


17443671 - EXADATA: OUTPUT BUFFER FOR READ CONTROL MESSAGE PAYLOAD TOO SMALL

17263661 - Fix for bug 17263661

Generic


16406802 - CDB:DATAFILE LOST AS A RESULT OF DUPLICATE MAPPING PROVIDED IN FILE_NAME_CONVERT

16517900 - CDB: ADBCS CAN'T DETECT AND REPORT ORA-12721 FOR A PDB.

16527374 - [12100-LIN64-130318]CDB:ORA-07445:EM EXPRESS HOME GOT IO ERROR

16551086 - CDB:DBA_DIRECTORIES DOES NOT SHOW PDB DIRECTORIES WHEN PDB IN RESTRICTED MODE

16675739 - ORA-04088: ERROR DURING EXECUTION OF TRIGGER 'APEX_040200.APEX$_WS_WEBPG_SECTION

16682595 - LNX64-12.1-CDB:PER PDB INIT CHANGE TO DEFAULT, UNPLUG AND PLUG INTO ANOTHER CDB

16709437 - ORA-65074: EDITIONS NOT SUPPORTED FOR COMMON USERS

16757934 - CDB: OCI STRESS: ORA-01461: CAN BIND A LONG VALUE ONLY FOR INSERT INTO A LONG C

16790307 - SELECT QUERY COULD RETURN WRONG RESULTS DUE TO INCORRECT PARTITION PRUNING

16802693 - INCORRECT ORA_DICT_OBJ_OWNER FOR GRANT/REVOKE DDLS ON DIRECTORY OBJECTS

16822629 - SOURCE_FILE_NAME_CONVERT FOR PDBS IN ASM NEEDS TO BE SIMPLIFIED

16855292 - SELECT ON REF PARTITIONED TABLE USING FULL PIECEWISE JOINS SPINS DURING PARSE

16888264 - PLUGIN OF PDB RETURNS ORA-65149

17026503 - CDB: ORA-7445 [KPDBDDROPPDBAPPLYUNDO()+277] WHEN DROP PDB IN USE

17032726 - CDB + PDB UPGRADE HITS ORA-600 [KQLUDP2] ON RDBMS_MAIN_LINUX.X64_130625

17082983 - SYSTEST:CDB: ORA-600 [17147] & ORA-600 [KGHFRMRG:NXT]

17174391 - CDB: ORA-603 & ORA-600 [730], [2310696], [SPACE LEAK]

17217040 - LNX64-12.1-CDB:HIT ORA-600 [KQLPGCALLBACK: INV PDB] WHEN RUN MIXED WORKLOADS

17244462 - CDB: ORA-600 [KSPGSP2] ON ALTER PDB OPEN UPGRADE

17249820 - CDB:JDBC STRESS HIT ORA-7445 [KPDBSYNCEXEC]

17289787 - ORA-600 [QESHQBNEXTPIECE.1] RUNNING QUERIES FOR GROUP-BY QUERIES

16450169 - Fix for bug 16450169

16462834 - Fix for bug 16462834

16721594 - Fix for bug 16721594

High Availability


16057129 - FREQUENTLY GETTING CORRUPTION ON STANDBY DATABASE ON ZFSSA STORAGE

16769019 - ORA-1403 MAY OCCUR IN OGG WITH INLINE LOB OPT AND DEDUP FETCH FOR PK UPDATE

16874123 - RMAN RESTORE DOES NOT CREATE GUID DIRECTORY FOR PRE-12C DATABASE

17184677 - LOGICAL STANDBY SQL APPLY ERRORS OR POTENTIAL DATA CORRUPTION

17311728 - FETCH BASED LCRS MAY NOT ENUMERATE SUPPLEMENTAL TRAILING NULLS

JavaVM


16977973 - Fix for bug 16977973

Oracle Diagnostics Infrastructure


16864562 - Fix for bug 16864562

17019974 - Fix for bug 17019974

Oracle Multitenant


16972213 - TT12.1.0.2SQLFUZZ2: PASSWORD COMMAND DOESN'T REQUIRE FORCE OPEN IN READ-ONLY PDB

17068536 - TT12.1.0.2SQLFUZZ2: SET CONTAINER VIA DBMS_SQL ORA-600 [KKAE_SET_SESSION_EDITION

17308691 - TT12.1.0.2SQLFUZZ2: PDB OPEN FORCE DOESN'T THROW SYNC ERROR WHILE PDB OPEN DOES

17324822 - TT12.1.0.2SQLFUZZ2: PDB SYNC DOESN'T SYNC DELEGATE OPTION FOR EXISTING CMN ROLE

17439871 - TT12.1.0.2SQLFUZZ2: DROP CMN USR THROWS ORA-600 [KQLOBJLOD-NO-RESULT-FROM-PROC$]

17171530 - Fix for bug 17171530

Oracle Net Services


17572525 - NETWORK: SUPPORT USE OF RSA CRYPTO LIBRARY IN FIPS MODE

Oracle Security Service


16410570 - ZT SHOULD PROVIDE AN API FOR TURNING ON FIPS MODE

17570606 - Fix for bug 17570606

Oracle Space Management


13521413 - INTEGRATED EXTRACT ABENDS WITH " FORMATTING ERROR"

16347904 - ORA-600 [KDBLKCHECKERROR] ON COMPRESSED TABLES WITH DML WORKLOAD

17362796 - WRONG RESULTS OR ORA-600 [KDMV_CHECK_ROW_1:IMCU

Oracle Spatial


17088068 - Fix for bug 17088068

Oracle Storage Server Service Layer


17080436 - DUMP MAP ELEMENTS OF COMPLETED BUFFERS IN KCFIS

17179261 - EXAMGMT: CONTINOUS ONLINE REQUESTS FROM AUTO MGMT FOR ALREADY ONLINED DISKS

17465741 - ORA-600 KCFIS_DECR_OVERHEADMEM_LEN_1 WITH LARGE FILE CREATION / HIGH REDUNDANCY

Oracle Streams


16275522 - STRM: MISSING MVDD FOR DDL ALTER TABLE ON VIRTUAL COLUMNS (DONOT_APPLY)

16585173 - CDB: FEW XSTREAMS APIS ARE SUPPORTED ONLY IN THE ROOT

16741246 - ORA-60 DEADLOCK ABORTS APPLY PROCESS RATHER THAN ROLLBACK AND RETRY.

16796277 - CAPTURE DOES NOT SEND CHANGES QUICKLY WHEN SCHEDULED JOB RUNS EVERY SECOND

17205719 - OGG: IR SHOWS INCORRECT DML STATS NOT MATCHING WITH ACTUAL DMLS APPLIED

17441661 - OGG: IR REPEATEDLY ABENDS DUE TO ORA-26808/ORA-07445 [KNASPLCR()+248]

Oracle Virtual Operating System Services


17579911 - DB12105: FLEX CLUSTER OOP PATCHING ROLLING MODE - FAILS AT PREROOTPATCH SCRIPT

Patch Automation


17343514 - REMOVE JAVA FROM CATBUNDLE

17442449 - FOR ROLLBACK, DATAPATCH GETS EXECUTED IN FIRST NODE INSTEAD OF LAST NODE

17596344 - DATAPATCH ORA-6502 ERRORS WITH LARGE NUMBER OF PATCH FILES

17922172 - DATAPATCH APPLIED BOTH SUB-PATCHES AND IN THE WRONG SEQUENCE

17981677 - DATAPATCH DOES NOT REMOVE PATCH AFTER ROLLBACK

Server Manageability


14852021 - SPAWRIO COMPUTES INCORRECT %READS AND %OPT

8 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://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 visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.


Patch 17552800 - 12.1.0.1.2 Patch Set Update Release 12.1.0.1.2 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.