Oracle Database 11 g - Online Public Access Catalog

More documents

Recommendations

Info

442 CHAPTER 10 ■ DATA GUARDselect last_failover_time, last_failover_reasonfrom v$fs_failover_stats;New Data Guard Manager PropertiesIn addition to the RedoCompression property, there are new Data Guard Manager propertiesworth mentioning, as shown in Table 10-1.Table 10-1. New Data Guard Manager PropertiesProperty NameFastStartFailoverAutoReinstateFastStartFailoverLagLimitFastStartFailoverPmyShutdownObserverConnectIdentifierDescriptionBy default, this parameter is set to true by the broker.This parameter specifies that the observer should automaticallyreinstate the primary database after a faststartfailover when connectivity to the primary is reestablished.If diagnostic or troubleshooting efforts arerequired on the primary database server, you shouldset this to false. This can be done using the followingcommand:DGMGRL> edit configuration set propertyFastStartFailoverAutoReinstate = false;Property "faststartfailoverautoreinstate" updatedThe minimum value is 10. By default, this parameter isset to 30. This parameter is applicable for MaximumPerformance fast-start failover configurations andspecifies the acceptable lag-time limit time in secondsthat the physical standby can fall behind the primarydatabase; otherwise, fast-start failover is not permitted.This can be done with the following command:edit configuration set propertyfaststartfailoverlaglimit = n;This attribute is ignored for SYNC destinations.By default, this parameter is set to false. If this value isset to true, the primary database will be shut down withthe abort option in the event of a fast-start failover. Thereare three possible triggering events for this:Redo generation stalls and the primary database losesconnectivity with the observer and standby databasefor longer than FastStartFailoverThreshold seconds.By a user-configured fast-start failover condition.The application invokes the DBMS_DG.INITIATE_FS_FAILOVER function (a new Oracle Database 11g PL/SQLpackage).DGMGRL> edit configuration set propertyFastStartFailoverPmyShutdown = false;Property "faststartfailoverpmyshutdown" updatedThis parameter sets the connect string that the observeruses to connect to the target database.
CHAPTER 10 ■ DATA GUARD 443There are new values for the FS_FAILOVER_STATUS column in the V$DATABASE dynamicview for fast-start-enabled databases. The valid values for this column are as follows:• tag under lag limit• tag over lag limitThe tag under lag limit value indicates that the database is valid for fast-start failover.The tag over lag limit value indicates that the database is behind and cannot perform a faststartfailover because the standby database apply is behind the FastStartFailoverLagLimitproperty.Detect Lost-Write Conditions Using a Physical StandbyMost everyone will agree that the highest priority of a DBA is to protect the data. DBAs areconstantly architecting and rearchitecting to find the best solution that will protect the enterprisefrom faults introduced by the inevitable such as block corruptions, lost writes, and faileddisks. Previously, DBAs were only able to architect database resilience strategies to protect againstlost-write failures using third-party hardware solutions. Oracle Database 11g Data Guard providesa mechanism to detect lost-write failures on the physical standby. With the proper architectureincluding the flashback recovery area, the database can recover from these lost-write faults.First, let’s discuss what lost-write failures are. A lost write can occur for several reasons.The most common reason is when the SAN disk array receives an acknowledgment for a successfuldisk block write to disk when it really did not. A subsequent read of an allegedly written blockwill return old content. The physical standby is now able to detect lost-write block corruptionsby comparing SCNs of the redo blocks on the primary database and SCNs of the blocks on thephysical standby database. Oracle Data Guard detects a lost-write corruption when the primarydatabase block SCN is lower than the standby database block SCN.There are steps for recovery when lost-write corruption is detected from the physicalstandby database. In addition, it is assumed that all the data contained on the corrupted lostwriteblock will be lost. When such errors are detected on the standby (ORA-00752) database,you must fail over to the physical standby:SQL> alter database activate standby database;DBAs must also realize that the old primary database must be completely rebuilt. The oldprimary database can no longer participate in a Data Guard configuration. The traditional optionssuch as flashing back the database or reinstating the database are not an option when dealingwith lost-write detection errors. For additional information on lost-write detection, pleaserefer to Chapter 2.Support of Heterogeneous OS Data Guard ConfigurationOracle Database 11g Data Guard now lifts the same OS requirements for a Data Guard configuration.The initial deployment of this heterogeneous Data Guard configuration is limited inscope. Effective with Oracle Database 11g, the Data Guard configuration can be composed of ahybrid of Linux and Windows primary and standby. Previously in Oracle Database10g, differentcombinations such as HP-UX PA-RISC and Itanium platforms were supported for the heterogeneousData Guard configuration. For a table of different platform combinations supported
Page 1:
The EXPERT’s VOIce ® IN ORACLEAl
Page 7:
Contents at a GlanceAbout the Autho
Page 11 and 12:
■CONTENTSixSQL*Plus New Features
Page 13 and 14:
■CONTENTSxiEnterprise Manager Int
Page 15 and 16:
■CONTENTSxiiiCombined Capture and
Page 17:
■CONTENTSxvImprovements in Redo T
Page 21:
About the Authors■SAM ALAPATI is
Page 24 and 25:
xxii■ACKNOWLEDGMENTSNothing I do
Page 26 and 27:
xxiv■INTRODUCTIONPerformance Mana
Page 28 and 29:
xxvi■INTRODUCTION• The easy add
Page 30 and 31:
xxviii■INTRODUCTION• The flashb
Page 32 and 33:
2 CHAPTER 1 ■ INSTALLING, UPGRADI
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
10 CHAPTER 1 ■ INSTALLING, UPGRAD
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
58 CHAPTER 2 ■ DATABASE DIAGNOSAB
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
100 CHAPTER 3 ■ DATABASE ADMINIST
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
168 CHAPTER 4 ■ PERFORMANCE MANAG
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
226 CHAPTER 5 ■ DATABASE SECURITY
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
266 CHAPTER 6 ■ BACKUP AND RECOVE
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 343 and 344:
CHAPTER 7■ ■ ■Data PumpDBAs a
Page 345 and 346:
CHAPTER 7 ■ DATA PUMP 315if test
Page 347 and 348:
CHAPTER 7 ■ DATA PUMP 317DBA11g1
Page 349 and 350:
CHAPTER 7 ■ DATA PUMP 319Encrypti
Page 351 and 352:
CHAPTER 7 ■ DATA PUMP 321Please b
Page 353 and 354:
CHAPTER 7 ■ DATA PUMP 323Remappin
Page 355 and 356:
CHAPTER 7 ■ DATA PUMP 325SELECT d
Page 357 and 358:
CHAPTER 7 ■ DATA PUMP 327Document
Page 359 and 360:
CHAPTER 7 ■ DATA PUMP 329SQL> sel
Page 361 and 362:
CHAPTER 7 ■ DATA PUMP 331SQL> sel
Page 363 and 364:
CHAPTER 7 ■ DATA PUMP 333DBMS_OUT
Page 365:
CHAPTER 7 ■ DATA PUMP 335If you a
Page 368 and 369:
338 CHAPTER 8 ■ ORACLE STREAMSLat
Page 370 and 371:
340 CHAPTER 8 ■ ORACLE STREAMSA s
Page 372 and 373:
342 CHAPTER 8 ■ ORACLE STREAMSSQL
Page 374 and 375:
344 CHAPTER 8 ■ ORACLE STREAMSThe
Page 376 and 377:
346 CHAPTER 8 ■ ORACLE STREAMSStr
Page 378 and 379:
348 CHAPTER 8 ■ ORACLE STREAMSDBM
Page 380 and 381:
350 CHAPTER 8 ■ ORACLE STREAMSPle
Page 382 and 383:
352 CHAPTER 8 ■ ORACLE STREAMSa p
Page 384 and 385:
354 CHAPTER 8 ■ ORACLE STREAMSSpl
Page 386 and 387:
356 CHAPTER 8 ■ ORACLE STREAMSpro
Page 388 and 389:
358 CHAPTER 8 ■ ORACLE STREAMSSup
Page 391 and 392:
CHAPTER 9■ ■ ■Storage Managem
Page 393 and 394:
CHAPTER 9 ■ STORAGE MANAGEMENT 36
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422: CHAPTER 9 ■ STORAGE MANAGEMENT 39
Page 443: CHAPTER 9 ■ STORAGE MANAGEMENT 41
Page 446 and 447: 416 CHAPTER 10 ■ DATA GUARD• Lo
Page 448 and 449: 418 CHAPTER 10 ■ DATA GUARDsql ch
Page 450 and 451: 420 CHAPTER 10 ■ DATA GUARDDBA11g
Page 452 and 453: 422 CHAPTER 10 ■ DATA GUARDWhile
Page 454 and 455: 424 CHAPTER 10 ■ DATA GUARDSQL> c
Page 456 and 457: 426 CHAPTER 10 ■ DATA GUARDSQL> a
Page 458 and 459: 428 CHAPTER 10 ■ DATA GUARD7. Swi
Page 460 and 461: 430 CHAPTER 10 ■ DATA GUARDwho ha
Page 462 and 463: 432 CHAPTER 10 ■ DATA GUARDSQL> s
Page 464 and 465: 434 CHAPTER 10 ■ DATA GUARDDynami
Page 466 and 467: 436 CHAPTER 10 ■ DATA GUARDSQL> B
Page 468 and 469: 438 CHAPTER 10 ■ DATA GUARDcomman
Page 470 and 471: 440 CHAPTER 10 ■ DATA GUARDCustom
Page 474 and 475: 444 CHAPTER 10 ■ DATA GUARDby Dat
Page 476 and 477: 446 CHAPTER 11 ■ APPLICATION DEVE
Page 522 and 523:
492 CHAPTER 11 ■ APPLICATION DEVE
Page 524 and 525:
Page 526 and 527:
Page 528 and 529:
Page 530 and 531:
Page 532 and 533:
Page 534 and 535:
Page 536 and 537:
Page 538 and 539:
Page 540 and 541:
Page 542 and 543:
Page 545 and 546:
CHAPTER 12■ ■ ■Data Warehousi
Page 547 and 548:
CHAPTER 12 ■ DATA WAREHOUSING 517
Page 549 and 550:
Page 551 and 552:
Page 553 and 554:
Page 555 and 556:
Page 557 and 558:
Page 559 and 560:
Page 561 and 562:
Page 563 and 564:
Page 565 and 566:
Page 567 and 568:
Page 569 and 570:
Page 571 and 572:
Page 573 and 574:
Page 575 and 576:
Page 577 and 578:
Page 579 and 580:
Page 581 and 582:
Page 583 and 584:
Page 585 and 586:
Page 587 and 588:
Page 589 and 590:
Page 591 and 592:
Page 593:
Page 596 and 597:
566 ■INDEXadvise failure command,
Page 598 and 599:
568 ■INDEXDBMS_ADDM package, 216-
Page 600 and 601:
570 ■INDEXcdump diagnostic direct
Page 602 and 603:
572 ■INDEXcursor_sharing paramete
Page 604 and 605:
574 ■INDEXdb_file_name_convert 's
Page 606 and 607:
576 ■INDEXDBMS-WORKLOAD_REPOSITOR
Page 608 and 609:
578 ■INDEXencrypt keyword, 243ENC
Page 610 and 611:
580 ■INDEXdefined, 112-114enablin
Page 612 and 613:
582 ■INDEXinsert command, 114, 56
Page 614 and 615:
584 ■INDEXmanually loaded plans,
Page 616 and 617:
586 ■INDEXOCISessionGet( ) method
Page 618 and 619:
588 ■INDEXusability improvements,
Page 620 and 621:
590 ■INDEXpga_aggregate_target in
Page 622 and 623:
592 ■INDEXreader farm, 421read-on
Page 624 and 625:
594 ■INDEXrestoring backup contro
Page 626 and 627:
596 ■INDEXserver_file_system opti
Page 628 and 629:
598 ■INDEXsynchronous capture, 33
Page 630 and 631:
600 ■INDEXOracle Audit Vault, 259
Page 632:
602 ■INDEXxmldiff command-line ut
show all

Oracle Database 11 g - Online Public Access Catalog

Create successful ePaper yourself

Delete template?

Save as template?