[Oracle] Data Guard CPU/PSU patch installation tutorial

Source: Internet
Author: User

[Oracle] Data Guard CPU/PSU patch installation tutorial Data Guard requires both Primary and Standby to be patched, so the steps are more complex. The main steps are as follows: Stop the log transmission service in Primary; shut down the Standby database, patch the Standby software (Note: Do not need to patch the Standby database), start standby to mount, do not enable managed recovery; Disable Primary, install patches on the software and database of Primary; start the Primary database and re-enable the log transmission service; Start Redo Apply on Standby, so that the patch script on Primary will be automatically synchronized to Standby; check whether patches are installed for Primary and Standby. The following is a specific example: 1. stop log transmission in Primary [SQL] sys @ EPAY> select database_role from v $ database; DATABASE_ROLE PRIMARY sys @ EPAY> show parameter role name type value =----------- specified parameter string SERVICE = sta ASYNC VALID_FOR = (O NLINE_LOGFILES, PRIMARY_ROLE) D B _UNIQUE_NAME = epaybk 1_string log_a Rchive_dest_31 string sys @ EPAY> alter system set log_archive_dest_state_3 = defer scope = both; System altered. 2. install patch 2.1 on Standby's Oracle software to shut down database instances, listener, ASM instances, and so on. 2.2 check the opatch version. If not, download the latest version 2.3 and install patch 2.4 on Standby's Oracle software to start Standby to the mount status. Start listener (Note: Standby does not need to patch the database itself. patch 3.1 on Primary to shut down database instances, listener, ASM instances, and so on. 3.2 check the opatch version. If not, download the latest version 3.3 and patch it on the Oracle software of Primary 3.4 to patch the Primary database itself [SQL] cd $ ORAC LE_HOME/rdbms/admin sqlplus/nolog SQL> CONNECT/as sysdba SQL> startup SQL> @ catbundle. SQL psu apply SQL> QUIT 4. start Primary listener in Primary startup log transmission service 4.1, and force register services to listener [SQL] sys @ EPAY> alter system register; System altered in database instance 4.2. 4.3 restart log transmission [SQL] sys @ EPAY> alter system set log_archive_dest_state_3 = enable scope = both; System altered. note: When log transmission is started, the following error may occur in alert: [plain] ------------------- --------------------------------------- Check that the primary and standby are using a password file and remote_login_passwordfile is set to SHARED or EXCLUSIVE, and that the SYS password is same in the password files. returning error ORA-16191 ---------------------------------------------------------- according to the error message, it should be the master database in the CPU patch when the sys password is modified, this error can be solved by replacing the password file of the slave database with the password file of the master database. 5. standby starts Redo Apply5.1 open Standby database 5.2 enable Redo Apply [SQL] sys @ EPAY> alter database recover managed standby Database disconnect from session; database altered. 5.3 verify that Primary and Standby are synced on the primary end to query the maximum number of archive logs: [SQL] sys @ EPAY> select max (sequence #) from v $ archived_log; MAX (SEQUENCE #) -------------- 159 query uploaded archived logs on the standby end: [SQL] sys @ EPAY> select sequence #, applied from v $ archived_log; 5.4 from alert. log can be seen that three log files are synchronized (that is, the patch in primary is synchronized to standby) [plain] alter database recover managed standby database disconnect from session Attempt to start background Managed Standby Recovery process (epay) Wed Jul 10 06:03:48 2013 MRP0 started with pid = 29, OS id = 15030 MRP0: Background Managed Standby Recovery process started (epay) started logmerger process Wed Jul 10 06:03:53 2013 Managed Standby Recovery not using Real Time Apply Wed Jul 10 06:04:01 2013 Parallel Media Recovery started with 32 slaves Waiting for all non-current ORLs to be archived... all non-current ORLs have been archived. wed Jul 10 06:04:01 2013 Completed: alter database recover managed standby database disconnect from session Media Recovery Log/data/oradata/epay/archivelog/Alibaba Media Recovery Log/data /oradata/epay/archivelog/415159_814716635.dbf Media Recovery Waiting for thread 1 sequence 160 (in transit) 6. check whether the patch is successfully installed later. 6.1 in primary, standby points to opatch lsinventory6.2 respectively, and check whether the patch is successfully installed in the database.

Related Article

Contact Us

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.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.