oracle 12 c psu,请教12c的psu和gi psu的问题

最新推荐文章于 2021-09-15 11:26:57 发布

weixin_39745269

最新推荐文章于 2021-09-15 11:26:57 发布

阅读量662

点赞数

文章标签： oracle 12 c psu

不明白就别回复了吧。。。

Go to primary content

Oracle® Database

Patch 25171037 - Database Patch Set Update 12.1.0.2.170418 (Includes CPUApr2017)

Released: April 18, 2017

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

Document 2228898.1 Patch Set Update and Critical Patch Update April 2017 Availability Document

Document 854428.1 Patch Set Updates for Oracle Products

Document 2229036.1 Oracle Database Patch Set Update 12.1.0.2.170418 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

From CPUJan2016 onwards, the 5th digit of the version number will be changed to reflect the release date in the format YYMMDD. See My Oracle Support Document 2061926.1 for more 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.2.170418 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".

To install the PSU 12.1.0.2.170418 patch, the Oracle home must have the 12.1.0.2.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 12.1.0.2.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 Database Vault installable. Review My Oracle Support Document 1195205.1 for details on how to apply this patch to a Database Vault environment.

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.

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.2.170418

Client-Only Installations

PSU 12.1.0.2.170418

Instant Client Installations

PSU 12.1.0.2.170418

(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 12.1.0.1.7 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.

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 12.1.0.2.170418 in the Oracle Home"

3.1 Patch Pre-Installation Instructions

Before you install PSU 12.1.0.2.170418, 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 12.1.0.2.x Database PSU Patch"

Section 3.1.2, "Environments with Grid Infrastructure"

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 12.1.0.2.x Database PSU Patch

From October 2014 onwards, the Oracle JavaVM Component 12.1.0.2.x 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

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

Grid Infrastructure PSU 12.1.0.2.170418 Patch 25434003 should be applied to the Grid Infrastructure home and Database home using the readme instructions provided with the patch.

3.1.3 Environment Checks

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:

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

unzip p25171037_12102_.zip

cd 25171037

opatch prereq CheckConflictAgainstOHWithDetail -ph ./

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

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

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.

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:

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.

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.

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.

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

unzip p25171037_12102_.zip

cd 25171037

opatch apply

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

3.3 Patch Post-Installation Instructions

After installing the patch, perform the following actions:

Apply conflict resolution patches as explained in Section 3.3.1.

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

Upgrade Oracle Recovery Manager catalog, as explained in Section 3.3.3.

The MD5 hash is no longer considered sufficiently secure, see Section 3.3.4.

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

Datapatch is run to complete the post-install SQL deployment for the PSU. For further details about Datapatch, including Known Issues and workarounds to common problems, see: Database 12c Post Patch SQL Automation (Doc ID 1585822.1).

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

Table 2 Steps to Run the Datapatch Utility for Standalone DB Versus Single/Multitenant (CDB/PDB) DB

Steps Standalone DB Steps Single/Multitenant (CDB/PDB) DB

% sqlplus /nolog

SQL> Connect / as sysdba

SQL> startup

SQL> quit

SQL> alter pluggable database all open;Foot 1

% cd $ORACLE_HOME/OPatch

SQL> quit

% ./datapatch -verbose

% cd $ORACLE_HOME/OPatch

% ./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 single/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. See My Oracle Support Document 1935365.1 Multitenant Unplug/Plug Best Practices for more information about the procedure for unplugging/plugging with different patch releases (in both directions).

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_sqlpatch view 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 Datapatch Known Issues.

Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/25171037/ for errors:

25171037_apply___.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.

This patch now includes the OJVM Mitigation patch (Patch:19721304). If an OJVM PSU is installed or planned to be installed, no further actions are necessary. Otherwise, the workaround of using the OJVM Mitigation patch can be activated. As SYSDBA do the following from the admin directory:

SQL > @dbmsjdev.sql

SQL > exec dbms_java_dev.disable

For more information on the OJVM mitigation patch, see Document 1929745.1 Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches.

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. The UPGRADE CATALOG command must be entered twice to confirm the upgrade.

$ rman catalog username/password@alias

RMAN> UPGRADE CATALOG;

RMAN> EXIT;

3.3.4 MD5 Hash Is No Longer Considered Sufficiently Secure

It has been determined that MD5 hash is no longer considered sufficiently secure. After this patch is applied, user creation is changed so that the MD5 hash is no longer generated by default. This only applies to users created after this patch is applied; existing users will not be changed. Review the following note to determine if you need to take further actions.

The MD5 hash is no longer considered sufficiently secure, see My Oracle Support Document 2194116.1 for more information.

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

You must execute the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" for any new database. There are no actions required for databases that have been upgraded.

For more information, see My Oracle Support, 12.1

BCA(Database Creation) does not execute ”datapatch (Doc ID 2084676.1).

4 Deinstallation

These instructions apply if you need to deinstall the patch.

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

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

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

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

4.1 Patch Deinstallation Instructions for a Non-RAC Environment

Follow these steps:

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

Run the OPatch utility specifying the rollback argument as follows.

opatch rollback -id 25171037

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

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

After deinstalling the patch, perform the following actions:

Section 4.2.1, "Run the datapatch Utility"

Section 4.2.2, "Upgrade Oracle Recovery Manager Catalog"

4.2.1 Run the datapatch Utility

Datapatch is run to complete the post-deinstall SQL deployment for the PSU. For further details about Datapatch, including Known Issues and workarounds to common problems, see: Database 12c Post Patch SQL Automation (Doc ID 1585822.1).

Follow these steps:

For each separate database running on the same shared Oracle home being patched, run the datapatch utility as described in Table 3. If this is Oracle RAC, run datapatch on only one instance.

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

Steps Standalone DB Steps Single/Multitenant (CDB/PDB) DB

% sqlplus /nolog

SQL> Connect / as sysdba

SQL> startup

SQL> quit

SQL> alter pluggable database all open;Foot 1

% cd $ORACLE_HOME/OPatch

SQL> quit

% ./datapatch -verbose

% cd $ORACLE_HOME/OPatch

% ./datapatch -verbose

The datapatch utility will then run the necessary rollback scripts. An entry will be added to the dba_registry_sqlpatch view 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 Datapatch Known Issues.

Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/25171037/ for errors:

25171037_rollback___.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.

4.2.2 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. The UPGRADE CATALOG command must be entered twice to confirm the upgrade.

$ rman catalog username/password@alias

RMAN> UPGRADE CATALOG;

RMAN> EXIT;

4.3 Patch Deinstallation Instructions for Oracle RAC Environment

Patch deinstallation instructions for Oracle RAC includes these environments:

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

Shut down the instance on the node.

Run the OPatch utility specifying the rollback argument as follows.

opatch rollback -id 25171037

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

Start the instance on the node as follows:

srvctl start instance

4.4 Patch Post-Deinstallation Instructions for Oracle 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 2229036.1 Oracle Database Patch Set Update 12.1.0.2.170418 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-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 '' conflicts with another user or role name

ORA-01921: role name '' conflicts with another user or role name

ORA-01927: cannot REVOKE privileges you did not grant

ORA-01952: system privileges not granted to 'WKSYS'

ORA-02289: sequence does not exist

ORA-02303: cannot drop or replace a type with type or table dependents

ORA-02443: Cannot drop constraint - nonexistent constraint

ORA-04043: object does not exist

ORA-06512: at line . If this error follow any of above errors, then can be safely ignored.

ORA-14452: attempt to create, alter or drop an index on temporary table already in use

ORA-29809: cannot drop an operator with dependent objects

ORA-29830: operator does not exist

ORA-29832: cannot drop or replace an indextype with dependent indexes

ORA-29844: duplicate operator name specified

ORA-29931: specified association does not exist

Issue 2

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

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

Please look at this stderr. You can re-run this make command.

Stderr output: ld: Invalid dynamic relocation needed for

read-only section, in input file

/scratch/installs/DB/64bit/DB/12101/server/lib/libpls12.a[pfrd.o], for symbol

.text at offset b00

...

ld: Invalid non-PIC relocation for symbol ".rodata" in file

"/scratch/installs/DB/64bit/DB/12101/server/lib/libpls12.a[plzsql.o]"

(section index 5, offset 0x92).

39651 errors.

...

ld: Invalid non-PIC relocation for symbol ".rodata" in file

"/scratch/installs/DB/64bit/DB/12101/server/lib/libpls12.a[plzsql.o]"

(section index 5, offset 0x92).

39651 errors.

...

ld: Invalid non-PIC relocation for symbol ".rodata" in file

"/scratch/installs/DB/64bit/DB/12101/server/lib/libpls12_pic.a[pfrdis.o]"

(section index 11, offset 0x19a2).

OUI-67008:OPatch Session completed with warnings.

Issue 3

On Solaris systems, the following ignorable warnings may be encountered during relinking of target dlopenlib:

+ make -f

$ORACLE_HOMEsqlplus/lib/ins_sqlplus.mk dlopenlib

_FULL_LIBNAME=$ORACLE_HOMEsqlplus/lib/libsqlplus.so _LIBNAME=libsqlplus

_LIBDIR=$ORACLE_HOMElib/ _LIBNAME_LIBS='$(libsqlplusLIBS)'

_LIBNAME_EXTRALIBS='$(libsqlplusEXTRALIBS)'

ld: warning: symbol '_init' not found, but .init section exists - possible

link-edit without using the compiler driver

ld: warning: symbol '_fini' not found, but .fini section exists - possible

link-edit without using the compiler driver

For more information, see My Oracle Support Document 2193336.1 Applying Oct2016 PSU or DBBP Version 12.1.0.2.161018 'LD: WARNING: SYMBOL '_INIT' NOT FOUND'.

Issue 4

Problem: While running Datapatch, an error from SYS.DBMS_QOPATCH is reported with the following message:

”input source is empty”, ”Error occurred in XML processing”

Or, the ORA:20001 error is returned.

Workaround: Follow these steps:

Go to the $ORACLE_HOME/QOpatch folder.

Check if there are xml_file.xml and stout.txt files in the folder.

If they exist, these files should be deleted.

Rerun Datapatch.

6 References

The following documents are references for this patch.

Document 1585822.1 Database 12c Post Patch SQL Automation

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 25171037.8 Database 12.1.0.2.170418 Patch Set Update (PSU)

Document 1591141.1 12.1.0.2 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 1924126.1 that documents all the non-security bugs fixed in each 12.1.0.2 Patch Set Update (PSU).

PSU 12.1.0.2.170418 contains the following new fixes:

Automatic Storage Management

19503821 - RMAN CATALOG EXTREMELY SLOW WHEN MIGRATING DATABASE FROM ASM TO FILE SYSTEM

24350831 - MMON HITS ORA-12751, TIME LIMIT VIOLATION DETECTED

Buffer Cache Management

21422580 - DBW USING 100% CPU WITH ENQ: RO - FAST OBJECT REUSE DURING TRUNCATE OR DROP TABL

25330273 - ADD CHANGES MISSING FROM FIX FOR BUG 21960504

Generic

16756406 - SR12.1.0.2RC - HNG - KPP_CONCATQ

17008068 - ORA-600 [QCTCTE1], [0] FROM AN ANONYMOUS PL/SQL BLOCK

19213447 - ORA-600 [QKAFFSINDEX3] ON MERGE QUERY

19593445 - SR12.2CDBCONC3 - TRC - KPDBSWITCH

20322560 - ORA-00600[K2QGIL:GTX][2][2] ON SHARED SERVER PROCESS

20569094 - REPLACE FUNCTION CORRUPT CLOB DATA

20703000 - INSERT INTO STAT TABLE HISTGRM$ FAILS WITH ORA-00932: INCONSISTENT DATATYPES

21164318 - FBDA: INTRODUCE UNIQUE INDEX ON TCRV TABLE: (RID,ENDSCN) (AVOIDS DUPLICATE ROWS)

21297872 - COMPLETE REFRESH OF MVIEW GIVES ORA-00600: [KKZDGDEFQ], [3], [13121], [144193],

21299490 - ORA 600 K2GUGPC: PTCNT> = TCNT

21889720 - HITTING ORA-03170 CONTINUOUSLY ON ONE STANDBY NODE

22062517 - WRONG RESULT WITH PARALLEL EXECUTION ON PARTITION

22520320 - WRONG RESULTS FROM PARALLEL SELECT COUNTING TO_NUMBER(NULL) AS ROWS

23096938 - Fix for bug 23096938

High Availability

19124336 - ORA-600 [KJBLCWSCN:!WR]CAN OCCUR WHEN HANDLING STALE BUT VALID WRITE COMPLETION

20250147 - ORA 600 [KJXMGMB_NREQ:!BAT]

20673810 - RECOVERY CAN STOP ONGOING REDO DUMP IF FILE OPEN FAILS WITH ORA-3113

20878790 - KJGCR_SERVICEGCR: KJGCR_METRICS: LOCAL METRIC CHECK NUMBER OF RT PROCESSES

21142837 - RMAN ACTIVE DUPLICATE FROM STANDBY ADG AS TARGET FAILS WITH RMAN-6053 RMAN-6025

21419850 - LX64_CDB:HIT ORA 600 [KJBRCRCVT:INRECOVERY] AND INSTANCE CRASHED

21868720 - RMAN-06054 ON BACKUP BASED DUPLICATE

21911701 - ORA-752 BRR FOR A REUSED BLOCK BY CONSISTENT READ CR

21977392 - ORA-600 [4193] ORA-10560: BLOCK TYPE 'KTU UNDO BLOCK' ON PHYSICAL STANDBY

22351572 - LGWR CRASH DUE TO ORA- 227 WITH NO CF CORRUPTION

25093739 - UPDATE DB activation.jar SIGNATURES TO WORK WITH LATEST JRE UPDATES

Oracle Multimedia

25079710 - UPDATE DB 12.1.0.2+12.2.0.1 ORDIM JAR SIGNATURES TO WORK WITH LATEST JRE UPDATES

Oracle Security

19383839 - UNIFIED AUDIT - NO LOGON OR FAILED LOGON ACTION CAPTURED

20543011 - Fix for bug 20543011

Oracle Space Management

16941434 - IMPDP SLOW WHEN USING SECUREFILE OVER A DATABASE/NETWORK LINK

20171986 - SLOW TRUNCATE ON 12.1.0.2 DUE TO "DFS LOCK HANDLE"

20368850 - ORA-600 [KDXLIN: SNO OUT OF RANGE]

20862087 - INDEX BECOMES CORRUPTED AFTER DIRECT INSERT ON COMPRESS TABLE

Oracle Utilities

25483815 - TRACKING BUG TO INCLUDE ORACHK 12.2.0.1.2 IN APRIL 2017 PSU

25490238 - PLACEHOLDER FOR TFA COLLECTOR VERSION 12.1.2.8.4 INCLUSION IN APR 2017 PSU

Oracle Virtual Operating System Services

22905130 - Fix for bug 22905130

Patch Automation

25475853 - DATAPATCH EXECUTION IS NOT HAPPENING FOR WINDOWS.X64 12.1.0.2 WINDBBP

25539063 - 12102170418DBBP_LINUX: LONGREADLEN NOT SET PROPERLY WHEN ROLLING BACK PATCH

25546608 - 12102170418DBBP

APATCH FAILED WITH "CAN'T CD TO /ROOT"

SQL*Plus

18440095 - Fix for bug 18440095

XML Database

24411921 - Fix for bug 24411921

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/us/corpora ... /support/index.html if you are hearing impaired.

Patch 25171037 - Database Patch Set Update 12.1.0.2.170418 (Includes CPUApr2017) for UNIX

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

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.

这个是psu的说明文件。请问这个是打gi的还是oracle的。如果是oracle的，我告诉你，gi也能打上。