Posts

Showing posts from August, 2016

10 Steps to Analyze AWR Report in Oracle

10 Steps to Analyze AWR Report in Oracle As you have  Generated AWR Report in Oracle , Next task is to  Analyze AWR Report in Oracle . By  Reading AWR Report    you can easily solve issues like Slow database, high wait events, Slow query and many more. Though It's a lengthy report but  Analyzing or Reading relevant part of AWR Report can help to troubleshoot issues in easy and fast manner. AWR stands for  Automatically workload repository , Though there could be many types of database performance issues, but when whole database is slow, then there are two possibilities. 1. Issue with Database Machine.  OS Watcher  is the best tool to start. 2. If Database performance issue, Then AWR Report is the place to look at . In case if a particular query is not performing well, i would suggest to look at execution plan of the query, stats of underlying table etc. In this case AWR won't help much. Recommendations before getting an AWR Report. 1. Collect Multiple AWR Repo
Dataguard Rolling Upgrade using transient logical standby I was successfully able to complete rolling upgrade using Dataguard for one of our environment and application downtime was reduced to just 2 minutes from 4 hours. Below are the high level steps performed and case study for this rolling database upgrade. Current Dataguard configuration looks like as below: Primary database: rec2p455 running on server dgtest02. Physical standby database: rec3p455 running on server dgtest03 . 1. Review prerequisites and best practices from Dataguard Rolling upgrade white paper. a. Enable flashback and created a guaranteed restore point on each databases for flashaback purpose b. Install upgraded ORACLE_HOME 11.2.0.4 on each servers dgtest02 and dgtest03 servers. c. Make sure that your physical standby database is configured correctly to support switchover operations. Below parameters should be configured correctly on these databases - On primary rec2p455 - alter system set db_unique_name=&

Apply CPU Patch in a DataGuard Physical Standby Database Configuration

Apply CPU Patch in a DataGuard Physical Standby Database Configuration I seen lot of questions in OTN on patching of DataGuard, Recently I have applied CPU Patch on production database, I like to give step-by-step procedure how to apply  CPUJAN2012 ( 13343244 ). Standby is in MAXIMUM PERFORMANCE Mode with Data Broker Enabled. When managing with broker, there are some steps which we need to manage with Broker instead of SQL. Which is highly recommended, If not there may be issues in Broker configuration. 1. In Primary disable log shipping to the standby & Stop MRP on standby 2. Shutdown Standby Database & Listener 3. Install CPU patch on Standby 4. Shutdown Primary database & Listener. 5. Apply Patch on Primary & Run Post installation Scripts (catbundle.sql) 6. Re-enable Log shipping on Primary 7. Monitor the redo apply from Primary to Standby