1 Reply Latest reply: Jun 4, 2014 3:22 PM by Babu Baskar RSS

    Write privileges on Oracle Data Guard

    Pahadia

      Hi All,

                We have a situation where we are extracting data from Oracle Data Guard replication server to produce near real time reporting. We are using Oracle's Prebuild ODI ETLs to extract the data. One of this ODI ETL creates a table on source. But this is not allowed due to nature of  ODG which keeps read only copy of primary DB.

       

                 I can not modify the ODI ETL because it is prepackaged & provided by Oracle as standard tool. Also there are further dependencies of this table etc.

       

       

      Does anyone have any suggestion how do we get around with this issue ?  Specifically I am looking for option where Data Guard allow table creation/inserts on custom table (this table may or may not exist on primary server)

       

      Thanks & Regards

        • 1. Re: Write privileges on Oracle Data Guard
          Babu Baskar

          Why don't you think about logical standby database ?

           

          thank you , Babu

           

          2.1.2 Logical Standby Databases

          A logical standby database is initially created as an identical copy of the primary database, but it later can be altered to have a different structure. The logical standby database is updated by executing SQL statements. This allows users to access the standby database for queries and reporting at any time. Thus, the logical standby database can be used concurrently for data protection and reporting operations.

          Data Guard automatically applies information from the archived redo log file or standby redo log file to the logical standby database by transforming the data in the log files into SQL statements and then executing the SQL statements on the logical standby database. Because the logical standby database is updated using SQL statements, it must remain open. Although the logical standby database is opened in read/write mode, its target tables for the regenerated SQL are available only for read-only operations. While those tables are being updated, they can be used simultaneously for other tasks such as reporting, summations, and queries. Moreover, these tasks can be optimized by creating additional indexes and materialized views on the maintained tables.

          A logical standby database has some restrictions on datatypes, types of tables, and types of DDL and DML operations. See Appendix C for information on data type and DDL support on logical standby databases.

           

          Getting Started with Data Guard