Note: This is a new host that has not yet been created. If the database already exists, you need to perform the database refreshing operation!
Environment: SUSE Linux Enterprise Server 11 sp1 (x86_64)
Upgrade the Oracle database from 11.2.0.3.0 to 11.2.0.3.7 PSU (latest). The patch is 16619892.P16619892_112030_Linux-x86-64.zip
Recommended reading: Considerations for upgrading the memory of the Oracle Database Server
Decompress the package with an orac
Create the PSU 11.2.0.3.8 and then create the database.
SQL> alter session set nls_date_format = 'yyyy-mm-dd hh24: mi: ss'; Session altered. SQL> select created from v $ database; CREATED --------------------------------------- ---------------------------------------- ---------------------------------------- -2015-06-10 13:31:51 -------------> database creation time SQL> set pages 100 lines 120SQL> col action format a6SQL> col namespace format a10SQL>
Create the PSU 11.2.0.3.8, and then the database, 11.2.0.3.8psu.
SQL> alter session set nls_date_format = 'yyyy-mm-dd hh24: mi: ss'; Session altered. SQL> select created from v $ database; CREATED --------------------------------------- ---------------------------------------- ---------------------------------------- -2015-06-10 13:31:51 -------------> database creation time SQL> set pages 100 lines 120SQL> col action format a6SQL> col namespace forma
Recently circulated online through with bypass permissions to implement illegal update table data, there is a greater risk. For CPU bugs in the July 2014 PSU repair, recommended upgrade corresponding PSU, if the conditions are not allowed, you can temporarily avoid the risk through the _with_subquery parameterDatabase version InformationSql> select * from V$version;BANNER------------------------------------
Tags: root user site completed after port exec occupies the bug agent data"Introduction to the Environment"System environment: Solaris + Oracle 11R2 + OGG + Scripting timed task statistics collection"Background description"Based on group security checks, vulnerability scanning of database versions is required, vulnerabilities in RBDMS and JVM types exist in vulnerability scanning, and vulnerabilities need to be fixed by upgrading the small version of the PSU
The following is the data Guard CPU/PSU patch installation method for a detailed analysis of the introduction, the need for friends can refer to the next
Non-Data guard patch installation tutorials refer to the [Oracle] CPU/PSU patch installation detailed tutorial, where Data Guard requires primary and standby to be patched at the same time, so the steps are more complex and the main steps are as follows:1
Tags: 11.2.0.4 PSU 18011627282436 = 27107360 (PSU) + 26925532 (OJVM)
0. In order to avoid installing patches running data dictionary scripts and system background jobs conflict, view Autotask, if there is enabled, first disable, after the patch and then enable.Su-oraclesqlplus "/as sysdba" set Lin pages 10000COL client_name format a40col consumer_group format A30col window_gr OUP FORMAT a30select clie
Non-Data guard patch installation tutorials refer to the [Oracle] cpu/psu patch installation tutorial, where Data Guard requires primary and standby to be patched at the same time, so the steps are more complex and the main steps are as follows:
Stop log transport service at primary;
Close the standby database, standby software on the patch (note: Do not need to make a patch for the standby database), start standby for Mount state, do not enable man
Oracle 11g + RAC + RHEL6.5 + udev + ASM + PSU Installation Summary
1. Preparations before installation:
Operating System: RHEL6.5
Storage: Huawei, multi-path configured
Bind the business network card and heartbeat network card and pass the redundancy test.
YUM source configuration
BASH/SSL vulnerability patches
2. Check System Requirements
A. LINUX version
Cat/etc/issue
B. Memory (at least 1 GB)
Grep MemTotal/proc/meminfo
C. SWAP PartitionWhen
GI Play Auto Patch command#/u01/oracle/app/grid/opatch/opatch AUTO/U01/SOFT/18706472-OCMRF/U01/SOFT/OCM.RSPexecuting/u01/oracle/app/grid/perl/bin/perl/u01/oracle/app/grid/opatch/crs/patch11203.pl-patchdir/u01/soft-patchn
Oracle has released a large number of Patchset patch sets from 8i to 11gr2. Sometimes, when we want to download these patch sets from MyOracleSupport, we may not be able to find the patch number (patchidnumber) at once ), the following describes the Patchset and PSU PatchNumber indexes up to 11.2.0.3: PatchsetPSUPa
Oracle has released a large number of Patchset patch sets from 8i to 11gr2. Sometimes when we want to download these patch sets from My Or
Disk back panel: Eclectic
In the tower server where the rack server or the hard drive slot is higher, the SAS Hba/raid card is generally not connected to the hard drive directly with the SAS cable, but through the disk backplane to facilitate the hard drive Plug and unplug. Disk Backplane is also a typical internal connection application, one side of the hard drive, the other side even Hba/raid card. Drive-side say, unified as a SFF-8482 socket, SAS
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 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
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
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
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
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
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.