Мой блог

четверг, 1 мая 2014 г.

Установка PSU 11.2.0.3.10

GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.3.10 (INCLUDES DB PSU 11.2.0.3.10) (Patch)

Patch 18139678

Устанавливать так:

1. Stop the CRS managed resources running from DB homes.

# su - oraagent

$ emctl stop agent

# su - oradb

$ /u01/app/oradb/product/11.2.0.3/dbhome_1/bin/srvctl stop home -o /u01/app/oradb/product/11.2.0.3/dbhome_1 -s /export/home/oradb/state_file.oradb

2. Run the pre root script.

$su -

# /u01/app/11.2.0.3/grid/crs/install/roothas.pl -unlock

3. Unzipping

# su - oragrid

$cd /tmp

$unzip p18139678_112030_Linux-x86-64.zip

$ls -l
total 552336
drwxrwxr-x 4 oragrid oinstall 307 Jul 18 09:21 17592127
drwxr-xr-x 5 oragrid oinstall 302 Jul 18 09:21 18031683

4. Apply the CRS patch using.

Требования к OPatch version : 11.2.0.3.5

$ /u01/app/11.2.0.3/grid/OPatch/opatch napply -oh /u01/app/11.2.0.3/grid -local /tmp/17592127

$ /u01/app/11.2.0.3/grid/OPatch/opatch apply -oh /u01/app/11.2.0.3/grid -local /tmp/18031683

5. Run the pre script for DB component of the patch.

# su - oradb

$ /tmp/17592127/custom/server/17592127/custom/scripts/prepatch.sh -dbhome /u01/app/oradb/product/11.2.0.3/dbhome_1

6. Apply the DB patch.

$ /u01/app/oradb/product/11.2.0.3/dbhome_1/OPatch/opatch napply -oh /u01/app/oradb/product/11.2.0.3/dbhome_1 -local /tmp/17592127/custom/server/17592127
$ /u01/app/oradb/product/11.2.0.3/dbhome_1/OPatch/opatch apply -oh /u01/app/oradb/product/11.2.0.3/dbhome_1 -local /tmp/18031683

7. Run the post script for DB component of the patch.

$ /tmp/17592127/custom/server/17592127/custom/scripts/postpatch.sh -dbhome /u01/app/oradb/product/11.2.0.3/dbhome_1

8. Run the post script.

$su -

Run the post script.

# /u01/app/11.2.0.3/grid/rdbms/install/rootadd_rdbms.sh
# /u01/app/11.2.0.3/grid/crs/install/roothas.pl -patch

9. Start the CRS managed resources that were earlier running from DB homes.

# su - oradb

$ /u01/app/oradb/product/11.2.0.3/dbhome_1/bin/srvctl start home -o /u01/app/oradb/product/11.2.0.3/dbhome_1 -s /export/home/oradb/state_file.oradb

10. Проверяем:

$/u01/app/oradb/product/11.2.0.3/dbhome_1/OPatch/opatch lsinventory

$su - oragrid

$/u01/app/11.2.0.3/grid/OPatch/opatch lsinventory

вторник, 8 апреля 2014 г.

GAP Resolution

1. На STANDBY смотрим GAP:

$sqlplus "/as sysdba"

SQL*Plus: Release 11.2.0.3.0 Production on Fri Feb 7 10:24:00 2014

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning, Automatic Storage Management, OLAP, Data Mining

and Real Application Testing options

SQL> SELECT * FROM V$ARCHIVE_GAP;

THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#

---------- ------------- --------------

1 1744 1751

SQL>

2. На PRYMARY восстанавливаем логи:

$export ORACLE_SID=testdb

$rman target /

Recovery Manager: Release 11.2.0.3.0 - Production on Fri Feb 7 10:25:29 2014

connected to target database: testdb (DBID=97255669)

RMAN> connect catalog 'rman/passwd@catdb.sun.com';

connected to recovery catalog database

RMAN> run {

2> set archivelog destination to '/tmp';

3> restore archivelog from sequence 1744 until sequence 1751 thread 1;

4> }

executing command: SET ARCHIVELOG DESTINATION

Starting restore at 07-FEB-14

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=237 device type=DISK

channel ORA_DISK_1: starting archived log restore to user-specified destination

archived log destination=/tmp