11.07.2015 Views

Oracle Database 11 g - Online Public Access Catalog

Oracle Database 11 g - Online Public Access Catalog

Oracle Database 11 g - Online Public Access Catalog

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CHAPTER 10 ■ DATA GUARD 435NAME VALUE UNIT SETTING DYNAMIC---------------------- ------ ---------- --------- --------APPLY_SERVERS 5 SYSTEM YESEVENT_LOG_DEST DEST_EVENTS SYSTEM YES_TABLELOG_AUTO_DELETE TRUE SYSTEM YESLOG_AUTO_DEL_ 1440 MINUTE SYSTEM YESRETENTION_TARGETMAX_EVENTS_RECORDED 10000 SYSTEM YESMAX_SERVERS 9 SYSTEM YESMAX_SGA 30 MEGABY SYSTEM YESPREPARE_SERVERS 1 SYSTEM YESPRESERVE_COMMIT_ORDER TRUE SYSTEM NORECORD_APPLIED_DDL FALSE SYSTEM YESRECORD_SKIP_DDL TRUE SYSTEM YESRECORD_SKIP_ERRORS TRUE SYSTEM YESRECORD_UNSUPPORTED_ FALSE SYSTEM YESOPERATIONS13 rows selected.Support for VPD and FGA<strong>Oracle</strong> <strong>Database</strong> <strong>11</strong>g logical standby provides support for row-level security (VPD) and finegrainedauditing (FGA) by replicating the DBMS_RLS and DBMS_FGA packages. Now securityimplementations from the primary database server replicate to the logical standby database.This will automatically enable by default if the logical standby database is created from an <strong>Oracle</strong><strong>Database</strong> <strong>11</strong>g database. <strong>Database</strong>s upgraded to <strong>Oracle</strong> version <strong>11</strong>.1 will need to have this featureenabled manually. When the DBMS_RLS and DBMS_FGA procedures are executed on the primarydatabase, additional information is captured in the redo logs, which allows the logical standbyto rebuild the procedural call. Both the primary and logical standby must have the compatibilityset to <strong>11</strong>.1 to have security enabled with VPD and FGA.DBMS_SCHEDULER Support<strong>Oracle</strong> <strong>Database</strong> <strong>11</strong>g Data Guard logical standby now provides support for DBMS_SCHEDULER.The scheduler is capable of running jobs on both the primary and logical standby databases.Using the DBMS_SCHEDULER.SET_ATTRIBUTE procedure, you can set the database_role attributeto be the primary database or logical standby. By setting this attribute, you specify that thejobs can run only when operating in that particular database role.A job created on the primary database will, by default, run only in the primary databaserole. Let’s take an example of a job that already exists in the database called EDBA_UPDATE andchange the database role attribute to logical standby using the set_attribute procedure:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!