ps2 psu

1, first download the required PSU package P6880880_112000_linux-x86-64.zipPatch Package: P19121551_112040_linux-x86-64-psu4.zip2, decompression p6880880_112000_linux-x86-64.zip to the $oracle_home directory, the original backupUnzip-n p6880880_112000_linux-x86-64.zip-d $ORACLE _home3. View version number[Email protected] opatch]$./opatch versionOpatch version:11.2.0.3.6Opatch succeeded.To see if you are hitting the

InOracleIn the database, how do we checkCPU and PSU PatchesWhat about the installation? This article mainly introduces this part, hoping to help you. Normally, there are two methods: One is to log on to the database and check the DBA_REGISTRY_HIST View: MODDB2:[/home/oracle]$sqlplus/assysdba SQL*Plus:Release10.2.0.4.0-ProductiononThuAug1813:04:432011 Copyright(c)1982,2007,Oracle.AllRightsReserved. Connectedto: OracleDatabase10gEnterp

11.2.0.3.7 PSU patch upgrade Description: 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) requires that the database be upgraded from 11.2.0.3.0 to 11.2.0.3.7 PSU (latest), Patch: unzip with oracle user unzipping: oracle @ tb-dinggou3 :~ /Softs> unzip p16619892_1

Reference Document 278641.10. BackupSPFile of the Master and Standby libraryBacking up data from the main library1. Pause the log transfer to the standby library on the main libraryAlter system set Log_archive_dest_state_x=defer scope=both sid= ' * '2. Turn off the standby and the standby to monitor the PSU; do not need to execute catpatch/catbundle/catcpu these scripts; after patching, boot the repository to mount State and start the standby monitor(

Applying GI PSU using "Opatch Auto" fails with "the Opatch Component check failed" (document ID 1169036.1) Applies to:oracle database-enterprise edition-version 11.2.0.3 and laterInformation in this document applies to any platform.Checked for relevance on 11-mar-2013***SymptomsApplying Grid Infrastructure PSU using "Opatch Auto" fails with "the Opatch Component check failed" For example:11.2.0

For non-Data Guard patch installation tutorials, refer to [Oracle] CPU/PSU patch installation detailed tutorial. Data Guard requires both Primary and Standby patches, so the steps are more complex, the main steps are as follows:1. Stop the log transmission service in Primary;2. Shut down the Standby database, patch the Standby software (Note: Do not patch the Standby database), start the standby status as mount, and do not enable managed recovery;3. D

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

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. Stop log transfer service in primary; 2. Close the standby database, standby software on the patch (note: Do not need to be patched for the standby database), start standby for Mount state, do not

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