Posts

Showing posts with the label 12c

Oracle 12c Capture Privilege Usage

Image
From Oracle 12.1 we have the ability to "record" the usage of permissions in our application and then we can narrow the permissions only to the minimal requirement. Installation CREATE USER YOSSI IDENTIFIED BY YOSSI; GRANT DBA, RESOURCE TO YOSSI; A user defined condition, when user is YOSSI (type = G_CONTEXT). BEGIN     DBMS_PRIVILEGE_CAPTURE.create_capture ( name => 'yossi_pol', TYPE => DBMS_PRIVILEGE_CAPTURE.g_context, condition => 'SYS_CONTEXT(''USERENV'', ''SESSION_USER'') = ''YOSSI''' );     DBMS_PRIVILEGE_CAPTURE.enable_capture ( 'yossi_pol' ); END; / Verify that the capture is defined and enabled COLUMN ROLES                FORMAT a20 COLUMN CONTEXT              FORMAT a30 COLUMN ENABLED              FORMAT a7   SELECT name ,        TYPE ,        enabled ,    ...

Data Guard / Far Sync Best Practice - control protection levels

I have just came across a meta parameter called DB_ULTRA_SAFE that sets the values for all of mentioned parameters in Far Sync Best Practice Recommendations (for Oracle 12.1) . When DB_ULTRA_SAFE=DATA_ONLY   • DB_BLOCK_CHECKING => MEDIUM.   • DB_LOST_WRITE_PROTECT => TYPICAL.   • DB_BLOCK_CHECKSUM => FULL. When DB_ULTRA_SAFE=DATA_AND_INDEX   • DB_BLOCK_CHECKING => FULL.   • DB_LOST_WRITE_PROTECT => TYPICAL.   • DB_BLOCK_CHECKSUM => FULL. When DB_ULTRA_SAFE=OFF   • When any of DB_BLOCK_CHECKING, DB_BLOCK_CHECKSUM, or DB_LOST_WRITE_PROTECT are explicitly set, no changes are made.

Using Standby as an Alternate for Far Sync (12c): Limitations and Considerations

Image
Based on Oracle 12.1 The Recommended Data Guard configuration is in Maximum Availability mode, when using Far Sync which is located near the Primary: Primary Database  à Far Sync Instance - Network input/output (I/O) is synchronous (Sync). Far Sync Instance  à  Standby Database – Network I/O is asynchronous (Async). Primary Database  à  Standby Database  – As an alternate (when Far Sync is not reachable), network I/O is asynchronous (Async). Using SQL If you do not use Data Guard Broker (dgmgrl), use the parameters specified below. ·         Primary On the Primary Database Mandatory Parameters Parameter Value Remarks LOG_ARCHIVE_DEST_2 point to Far Sync service Alternate log_archive_dest_3 Switches to the standby destination, after the number of failures specified in the next parameter is reached. max_failure 1 This val...

Oracle 12c Release 2 New Features for Active Data Guard

Hi , At Oracle Open World 2016 I collected the main improvements and changes   are going to be implemented in Oracle Database 12 Release 2 : 1.        Data Guard Creation with dbca, support automatic creation of Standby database and Far Sync instance   not for RAC (at this point) command : dbca -silent -createDuplicateDB     - PrimartDBConnectionString myprymary.domin:1523/chicago.domain     - gdbName chicago.domain -sid boston     - initParams instance_name=boston -createAsStandby     - customScripts /tmp/test.sql 2.        Multi-Instance Redo Apply, Parallel, multi-instance recovery - when standby is RAC, all of its instances will use the MRP0 process for applying 3.        Supports Diagnostic Pack on Active Data Guard   AWR+ADDM Reports for Standby are kept in the Primary 4.  ...