Oracle Database 11 g - Online Public Access Catalog

More documents

Recommendations

Info

400 CHAPTER 9 ■ STORAGE MANAGEMENTASMCMD> cp +data/DBA11g1/DATAFILE/ALERT_D1.267.631889077+FRA/DBA11G1/alert_d1.dbfsource +data/DBA11g1/DATAFILE/ALERT_D1.267.631889077target +FRA/DBA11G1/alert_d1.dbfcopying file(s)...file, +FRA/dba11g1/alert_d1.dbf, copy committed.The syntax to copy files between one local diskgroup to another local diskgroup is straightforward.You can copy files between one diskgroup to another diskgroup or even to the samediskgroup. You can also leverage the copy command to copy files from ASM to a local file system.As the last example, we’ll copy the docs_d4 datafile to the /oradata/DBATOOLS/ directory on thefile system:ASMCMD> cp +DATA/DBA11G1/DATAFILE/DOCS_D4.276.631890065/oradata/DBATOOLS/docs_d4.dbfsource +DATA/DBA11G1/DATAFILE/DOCS_D4.276.631890065target /oradata/DBATOOLS/docs_d4.dbfcopying file(s)...file, /oradata/DBATOOLS/docs_d4.dbf, copy committed.Metadata Backup and RestoreAs far as the ASM ecosystem is concerned, there isn’t much to back up. The only files that canbe backed up are the initialization file or the spfile depending on the database standards for thecompany. Possibly, the $ORACLE_BASE/diag directory may need to be backed up if you are interestedin preserving the log files.Oracle Database 11g provides the capability to back up the ASM diskgroup structure andattributes including ASM aliases, directories, or templates. In Oracle Database 10g, objectssuch as aliases, directories, or templates have to be manually re-created after the restore. Priorto Oracle Database 11g, ASM metadata for the diskgroups could not be backed up because themetadata resides on the disk headers. We recommend that DBAs utilize the ASM MetadataBackup and Restore (AMBR) utility coupled with a solid RMAN backup strategy to provide thecomplete database recovery solution. Using the AMBR tools, you can protect the diskgroupstructures since AMBR tools provide the facility to back up and restore the original ASM diskgroupwith the same template and alias directory structures. Oracle Database 11g introducesAMBR’s md_backup and md_restore commands to provide a comprehensive level of protectionfor the ASM environment. Extensions to the asmcmd utility provide this extra level of protectionfor ASM:• md_backup [-o ] [-g diskgroup_name [-g diskgroup_name …]]• md_restore [ -t full|nodg|newdg]-fi -g dgname [-g dgname] [–o] [-of ][-i] [-l< log_file>]Backup Diskgroup Using md_backupThe md_backup command captures information about ASM disks, diskgroup and failure groupconfigurations, and template and alias directory structures, and it creates a user-designated
CHAPTER 9 ■ STORAGE MANAGEMENT 401backup text file. The md_restore command uses this text file and converts it into SQL commands torestore the custom user-defined metadata for the diskgroups. You can view the ASM alert logfile to see the SQL generated by the md_restore command. We’ll provide an example of this inthe next section when we demonstrate a complete ASM diskgroup backup and recovery.With the md_backup command, users have the option to back up one or more diskgroups.The diskgroup names are delimited by commas. By default, the MDB file is created in the currentworking directory. This can be overwritten by providing a fully qualified file name. Not specifyingthe diskgroup(s) to the md_backup command will, by default, build metadata information for alldiskgroups that are mounted.Because the MDB file is a text file, users will be tempted to modify this file. You should beextremely cautious when modifying this file because ASM does not validate the syntax or accuracyof the flat file. The md_restore command simply converts this file into SQL statements andexecutes it. Please back up this file before making any modifications to it. Having said all this,modifying the MDB backup file can be very useful. You can manipulate this file so that onlycertain ASM objects are restored instead of restoring the entire diskgroup.You will see in the “Metadata Backup and Restore Demonstration” section that the MDBfile has four distinct sections: disk information, diskgroup information, alias information, andtemplate information. This tag is used by the md_restore command to locate the section in thebackup file.■Caution As mentioned, please exercise caution when modifying the MDB backup file. User errors cancause sections to be skipped.In the disk section of the MDB file labeled as DISKSINFO, information about diskgroupname, disk label name, disk path, OS size/ASM size of the disk, and failgroup name will becaptured. For the diskgroup section labeled as DGINFO, characteristics of the diskgroup name,redundancy type, ASM/RDBMS compatibility, and AU size will be captured. For the alias directioninformation section labeled as ALIASINFO, the MDB file has information about the diskgroup name,directory level, and alias name with the full path of the alias entry. Lastly, the template sectionlabeled as TEMPLATEINFO houses relevant information for all system and nonsystem (user-defined)templates. For each template, the diskgroup name, template name, redundancy, stripe, andsystem designator is stored. All of this information is pertinent to the md_restore command.Restore Diskgroup Using md_restoreThe md_restore command of asmcmd performs an ASM metadata restore for a diskgroup. This utilityreads the MDB backup file and essentially builds the required SQL statements to rebuild all thecomponents of the diskgroup including templates, aliases, directories, and diskgroup names.This utility restores only the ASM diskgroup metadata information. Coupled with RMAN, youcan achieve a higher level of data protection. You must still have a good RMAN backup. After asuccessful restore of the ASM diskgroup metadata, you can restore the database using RMAN.This utility has several options. It can be used to restore the MDB backup file as is, or it canperform transformations of the diskgroup name. At the same time, you have the option to restorejust one diskgroup or multiple diskgroups or all the diskgroups specified in the backup file.
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 429: 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 472 and 473: 442 CHAPTER 10 ■ DATA GUARDselect
Page 474 and 475: 444 CHAPTER 10 ■ DATA GUARDby Dat
Page 476 and 477: 446 CHAPTER 11 ■ APPLICATION DEVE
Page 478 and 479: 448 CHAPTER 11 ■ APPLICATION DEVE
Page 480 and 481:
450 CHAPTER 11 ■ APPLICATION DEVE
Page 482 and 483:
Page 484 and 485:
Page 486 and 487:
Page 488 and 489:
Page 490 and 491:
Page 492 and 493:
Page 494 and 495:
Page 496 and 497:
Page 498 and 499:
Page 500 and 501:
Page 502 and 503:
Page 504 and 505:
Page 506 and 507:
Page 508 and 509:
Page 510 and 511:
Page 512 and 513:
Page 514 and 515:
Page 516 and 517:
Page 518 and 519:
Page 520 and 521:
Page 522 and 523:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?