Download Implementing Oracle9i Data Guard

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Database wikipedia , lookup

Extensible Storage Engine wikipedia , lookup

PL/SQL wikipedia , lookup

Clusterpoint wikipedia , lookup

Database model wikipedia , lookup

Object-relational impedance mismatch wikipedia , lookup

Oracle Database wikipedia , lookup

Transcript
Session id: 36226
Implementing Oracle9i Data
Guard
Michael New
Senior Technical Consultant
ThinkSpark
Data Guard - Outline




Concepts
Architecture
Best practices
Implementation
Concepts
 Differentiate High Availability approaches
 Enhanced protection modes
–
–
–
Maximum Protection
Maximum Availability
Maximum Performance
 Standby Redo Logs (SRLs)
 Automatic gap resolution
 Data Guard broker
–
–
Data Guard Manager (OEM)
Command-line interface (CLI)
Concepts
Protection Mode
Data loss Divergence
Maximum Protection
None
None
Maximum Availability
None
Some
Minimal
Yes
Maximum Performance
Architecture
Source: Oracle9i Data Guard Concepts and Administration
Architecture
 Log Transport (LGWR, ARC, FAL, RFS)
–
–
Archive log permissions, destinations, transmission,
reception & transmission failure resolution
LGWR or ARC can write from primary to standby
 Log Apply (MRP or LSP)
–
–
Managed recovery (not read-only) mode
SQL apply mode
 Role Management
–
–
Primary or Standby
Switchovers, graceful or forced failovers
 Data Guard Broker (DMON)
Best Practices
 FORCE LOGGING mode





Identical sites
Initialization parameters
Oracle network
Standby redo logs (SRLs)
Monitoring
FORCE LOGGING
Identical sites
init.ora
Oracle Net
SRLs
Monitoring
FORCE LOGGING Mode
 New feature to Release 9.2
 Prevents unlogged direct writes from
propagating to standby
 Overrides NOLOGGING transactions
 FORCE LOGGING
Identical sites
init.ora
Oracle Net
SRLs
Monitoring
Identical Sites
 Logical structures – partition names,
directories/files, privileges, accounts, etc.
 Network configurations
–
–
Oracle
O/S
 Hardware environments
FORCE LOGGING
 Identical sites
init.ora
Oracle Net
SRLs
Monitoring
Initialization Parameters….









Use SPFILE
Initialization settings (except 4)
No environment variables
STANDBY_ARCHIVE_DEST=LOG_ARCHIVE_DEST1
LOG_ARCHIVE_DEST_3 = … ALTERNATE …
LOG_ARCHIVE_DEST_1 = … ARCH …
FORCE LOGGING
Disable ARCHIVE_LAG_TARGET
Identical sites
Unset DB_CREATE_ONLINE_LOG_DEST_n
Tune CONTROL_FILE_RECORD_KEEP_TIME
 init.ora
Oracle Net
SRLs
Monitoring
Initialization Parameters
 LOG_ARCHIVE_DEST_2 attributes
– OPTIONAL
– LGWR
– ASYNC
– NOAFFIRM
– REOPEN
– MAX_FAILURE
– DELAY
– NET_TIMEOUT
FORCE LOGGING
Identical sites
 init.ora
Oracle Net
SRLs
Monitoring
Oracle Network…




Static SID registration
Connect-time failover
Alternate standby location
Session Data Unit (SDU) setting
FORCE LOGGING
Identical sites
init.ora
 Oracle Net
SRLs
Monitoring
Oracle Network
 Same network file structure
 Listeners
–
–
Database clients – stop stby lsnr
Redo log & DBA traffic
 tnsnames.ora files
–
–
–
Local node
database clients
DBAs
FORCE LOGGING
Identical sites
init.ora
 Oracle Net
SRLs
Monitoring
Standby Redo Logs







SRLs on all sites
Same # SRLs on all sites
Same SRL names on all sites
Redo logs & SRLs the same size
# SRL groups = 1 + (# redo log groups)
SRL groups < MAXLOGFILES
SRL members < MAXLOGMEMBERS
FORCE LOGGING
Identical sites
init.ora
Oracle Net
 SRLs
Monitoring
Monitoring




OEM Data Guard Diag Pack events
Alert log ORA- errors
Alert log non ORA- errors
V$ views - scripts (White Paper, Appendix 3)
FORCE LOGGING
Identical sites
init.ora
Oracle Net
SRLs
 Monitoring
Implementation….
 FORCE LOGGING
 Identical sites
– O/S clocks
– /etc/hosts
– Environment variables & DBA scripts
 Initialization parameters (SPFILE)
 Oracle network configuration files
 ARCHIVELOG mode & automatic archiving
 Backup primary database
 Create standby control file
Implementation
 Copy backup to standby site
 Recover standby database
–
Mount standby database
–
Create SRLs
–
Start new listeners
Recover standby
Place standby in managed recovery mode
Enable LOG_ARCHIVE_DEST_STATE_2 on primary
Set protection mode on primary
Verify standby works
–
–
–
–
–
 Enable Data Guard broker
Next Steps….
 Michael New, [email protected],
800-846-4082, ext. 104
 Recommended sessions
–
–
Oracle Data Guard: Maximum Data Protection at
Minimum Cost
Data Guard SQL Apply: Back to the Future
 Recommended demos and/or hands-on labs
–
Using Data Guard Manager to Manage a
Standby Database
Next Steps….
 See Your Business in Our Software
–
Visit the DEMOgrounds for a customized architectural
review, see a customized demo with Solutions Factory, or
receive a personalized proposal. Visit the DEMOgrounds
for more information.
 Relevant web sites to visit for more information
–
–
Oracle High Availability Guidelines & Recommendations:
M. Burke, 2003, ThinkSpark – [email protected]
Data Guard Overview:
http://otn.oracle.com/deploy/availability/htdocs/odg_overvie
w.html
Next Steps
 Relevant web sites to visit for more information
–
–
–
Data Guard Technical White Paper on OTN:
http://otn.oracle.com/deploy/availability/pdf/DG92_TWP.pdf
Data Guard Technology Overview Presentation on OTN:
http://otn.oracle.com/deploy/availability/pdf/DataGuardTech
nologyOverview.pdf
Data Guard Primary Site & Network Configuration Best
Practices:
http://otn.oracle.com/deploy/availability/pdf/MAA_DG_NetB
estPrac.pdf
Reminder –
please complete the
OracleWorld online session
survey
Thank you.
QUESTIONS
ANSWERS
Session id: 36226
Implementing Oracle9i Data
Guard
Michael New
Senior Technical Consultant
ThinkSpark
Implement B&R – DG is HA
(not B&R) Solution
 B&R addresses database integrity & recovery
 DG is HA solution to reduce MTTR, premised on
reliable B&R solution
 Without B&R, data loss possible with DG because of
–
–
–
–
–
Primary / secondary loss of network communication
Standby maintenance downtime
Hardware failure due to multiple devices
Hardware failure during role reversal
logical corruption (if propagated to the standby)
ThinkSparkThinkSpark
For more than 15 years, ThinkSpark has been a world-class technology
partner to those businesses that have invested in Oracle technologies
and solutions. ThinkSpark has delivered unmatched Oracle database
expertise, Oracle systems integration skills, Oracle education services
and Oracle license management insights to thousands of businesses
across the country and around the globe. Headquartered in Dallas,
ThinkSpark's more than 100 professionals serve clients across all
industries through facilities in Austin, Dallas, Houston, Las Vegas,
Oklahoma City and San Antonio. For more information about ThinkSpark,
call (888) 262-6043 from the U.S., Canada and Mexico or visit
ThinkSpark on the World Wide Web at http://www.thinkspark.com/.