psu sticker

In addition to the reprinted content, this article is original site: reposted from lovewifelovelife-Roger's Oracle technology blog. Link: OraclePSU updated on April 9,. PSU updated on April 9, mainly in four versions: 12.1.0.2, 12.1.0.1, 11.2.0.4, 11.2.0.3, and 11.1.0.7. +++ 10.2.0.4Ora Except for the reprinted content, this article is original site: reposted from the Oracle technology blog of love wife love life-Roger. Link: in fourth quarter of 2014

when doing an Oracle database upgrade from 11.2.0.1.0 to 11.2.0.2.8, there is no problem with the upgrade of the instance, there is no problem upgrading the PSU. When performing @?/rdbms/admin/catbundle PSU apply, only a subset of the information is displayed, i.e. termination of apply.The PSU information for 11.2.0.2.8 is not displayed in Dba_registry_history; s

When upgrading the Oracle database from 11.2.0.1.0 to 11.2.0.2.8, the software upgrade is normal, the instance upgrade is normal, and the psu is upgraded. Run @? /Rdbms/admin/catbundle psu when applying, only part of the information is displayed, that is, terminate apply.The psu information of 11.2.0.2.8 is not displayed in dba_registry_history; select * from dba

Supply # (# # # W). Check PSU. (Power Device # (# # # W) A predictive failure occurred. Please check the PSU. ) A power supply fan failure, too high temperature, or a power communication error caused an impending power failure to be alerted.e161c Power Supply # (# # # W) lost AC power. Check PSU cables. (Power supply # (# # # W) AC power is interrupted. Please c

when doing an Oracle database upgrade from 11.2.0.1.0 to 11.2.0.2.8, there is no problem with the upgrade of the instance, there is no problem upgrading the PSU. When you run the @?/rdbms/admin/catbundle PSU apply, only a subset of the information is displayed, which terminates apply.The PSU information for 11.2.0.2.8 is not displayed in Dba_registry_history; sel

The following is the latest psu information of my latest version 10.2.0.4 + for your reference! (Including 12c psu information ): +++ 10.2.0.4Oracle Database Patch Set Update Unix Comments between des Cpu10.2.0.4.1 8576156 Bash 10.2.0.4.0 mongodes CPU Jul 200910.2.0.4.2 8833280 Bash 10.2.0.4.0 des CPU Oct 200910.2.0.4.3 9119284 Bash 10.2.0.4.0 des CPU Jan 201010.2.0.4.4 9352164 Bash 10.2.0.4.0 des CPU Apr 2

Explain the environment: operating system: AIX 7.1Oracle version: Oracle RAC 11.2.0.3 before the 11.2.0.3.9 patch set, the RAC is not formally used, so you can simply hit the latest 11.2.0.3.11 patch set.The two sets of RAC that were newly installed today in the new PSU, also use Opatch Auto to hit the PSU, but one set of RAC is a patch with RAC and grid, and the other is patch grid-only patches. Very depre

Why didn't I hit Racdatabasehome during oracleraco patchauto?First explain the environment: OS: AIX 7.1Oracle version: Oracle Rac 11.2.0.3 before the release of the 11.2.0.3.9 Patch Set, Rac is not officially used, so simply hit the latest 11.2.0.3.11 patch set.Today, two sets of Rac were newly installed some time ago to form the latest psu, And the opatch auto method is also used to create psu, but one of

Oracle version: Oracle versions earlier than 11.2.0.3.9 have been installed with the patch set 11.2.0.3.9, and Rac has not yet been officially used. Therefore, we can simply hit the latest 11.2.0.3.11 patch set. Oracle version: Before Oracle Rac 11.2.0.3, the patch set 11.2.0.3.9 has been installed and is not yet officially used. Therefore, you can simply hit the latest 11.2.0.3.11 patch set. First explain the environment:Operating System: AIX 7.1Oracle version: Oracle Rac 11.2.0.3I used th

Why didn't Oracle RAC Opatch go to Rac database home during auto? First explain the environment:Operating System: AIX 7.1Oracle version: Oracle Rac 11.2.0.3I used the 11.2.0.3.9 patch set before and it was not officially used for Rac installation, So I simply hit the latest 11.2.0.3.11 patch set. Today, two sets of Rac were newly installed some time ago to form the latest psu, And the opatch auto method is also used to create

Tags: psu gi opatchPSU7 for 11.2.0.4 Database Linux X64 Install Step===============================================================================1. Download PSU to Local in Oracle support, PSU patch number: 207609822. Upload the PSU to the server and unzipUnzip P20760982_112040_linux-x86-64.zipCD 207609823. Check the

One, CPU and PSURecently, after upgrading the database from 9.2.0.6 to 11.2.0.4, it was found that ORA-02072 error occurred when 11.2.0.4 accessed other 9i libraries via Dblink, and found a solution via Google, which was to upgrade to PSU 11.2.0.4.8, Note the procedure for installing patches, and it is recommended that you carefully read the relevant sections of the patch Readme document before patching, and that all the details of the patch can be fo

latest bundle patches. The Windows bundle patch for Oracle's cluster software and database software is the same, such as the window bundle patch 16 (Patch number 16167942, which can be hit on a cluster or on a database).To learn about patch numbers for Windows Bundle patches, refer to the MOS documentation:Note 161549.1 Oracle Database, Networking and Grid Agent patches for Microsoft platformsCritical Patch Update (CPU):Quarterly releases, some patches to fix security, are cumulative. The Secur

After Oracle is upgraded to 11.2.0.3, there will be a series of Performance or Wrong Results. According to the metalink Document ID 1392633.1, the solution is as follows: ScopeThis note concerns itself with highly updated patches in 11.2.0.3 that are not supported in PSU updates, either because they contain optimizer layer fixes or because the PSU that will contain in them has not yet been released.Things t

Explore Oracle Database Upgrade 4 11.2.0.4.0PSU11.2.0.4.3 Explore Oracle Database Upgrade 411.2.0.4.0 PSU 11.2.0.4.3 1. Check the current database PSU Number: [oracle@db01 ~]$ cd/DBSoft/Product/11.2.4/db_1/OPatch/[oracle@db01 OPatch]$ lscrs docs emdpatch.pl jlib ocm opatch opatch.bat opatchdiag opatchdiag.bat opatch.ini opatch.pl opatchprereqs oplan[oracle@db01 OPatch]$./opatch versionOPatch Versi

In the test environment aix6106, after Patch: 10190759 is installed, database boot generates a ORA-07445: predictionencountered: coredump [PC: 0x0] [SIGILL] In the test environment aix6106, after Patch: 10190759 is installed, database boot produces a ORA-07445: exception encountered: core dump [PC: 0x0] [SIGILL] After Oracle is upgraded to 11.2.0.3, there will be a series of Performance or Wrong Results. According to the metalink Document ID 1392633.1, the solution is as follows: ScopeThis

also be 10.2.0.4 (not to rule out that you made a special patch for a component after the version of this component is unique, of course this is rare, not recommended). We can understand the version of the component in the database by querying the Dba_server_registry view. Fifth stands for the platform-related release number. In general, this digit is affected by another patch (not a patch set). After 10g Oracle introduced an update to the patch set released on the basis of a particular patch

; SELECT sum (object_name) N2 from dba_objects WHERE status= ' INVALID '; Sql> SELECT object_name from dba_objects WHERE status= ' INVALID ';--store the result in Excel or in a table so that it is easy to check after the patch is finished. 4, Patch Type Oracle database patches are typically divided into two CPUs and PSU patches. The full name of the Oracle PSU is patch Set update,oracle, a patch pac

With the power of the processor more and more, the demand for power is more and more high, "to find the object of matching", in fact, the purchase of power is not so? However, it is believed that most of our friends are not sure about the power supply until they enter the installation shop, because while the power consumption of the processor can be found from the official Intel and AMD websites, there are not many people who can actually find the Web site, not to mention the power consumption o

--------------------------------------------------------------------------------Oracle Error-29548:ora-29548:java System class reported:release of Java SystEM classes in the database (12.1.0.2.161018 1.6) does don't match that of the ORACLe executable (12.1.0.2.170117 1.6) had been detected in Fnd_web_sec. Validate_passWOrd.From Messige it is because the Oracle patch and the database of the Post install patch inconsistency caused by the Oracle program patch update, but there is no post install,