Oracle^® Business Intelligence Disconnected Analytics Administration and Configuration Guide > Synchronizing Applications in Oracle BI Disconnected Analytics > Step 5: Setting Up for Incremental Synchronization >

Examples of Incremental Synchronization Scripts

Suppose that you have a disconnected application called Paint. The following shows a sample disconnected application configuration file for the Paint application.

<remotecfg>

<application name="Paint" displayname="Paint Application" dir="app">

<repository name="Paint.rpd"/>

<webcatalog name="analytics.catalog"/>

</application>

<data dir="data" catalogfolder="/shared/disconnected">

<dataset name="my_incremental" incremental="true" subjectarea="Disconnected" syncmode="preprocessed">

<table name="R_DIM">

<sourcingreport name="r_dim"/>

<tablesql name="r_dim.sql"/>

</table>

<table name="R_FACT">

<sourcingreport name="r_fact"/>

<tablesql name="r_fact.sql"/>

</table>

</dataset>

</data>

</remotecfg>

To perform incremental synchronizations of the data for the fact and dimension tables, you can use scripts such as the following sample ones. Notice that these scripts are very similar to the ones that you can use for full downloads, as described in Scenario for Using SQL Scripts to Create Disconnected Tables and Indexes. These sample scripts for incremental synchronization have the following differences from scripts that are designed for full downloads:

• Existing tables are not dropped.
• Errors are ignored. Because a CREATE TABLE command is issued to retrieve the incremental data and the table already exists, it is useful to ignore the error that is generated and states that the table is already created.

Sample r_dim.sql Script

[IGNORE_ON_ERROR]

CREATE TABLE R_DIM (

customer_name varchar(50) NULL,

city varchar(50) NULL);

Sample r_fact.sql Script

[IGNORE_ON_ERROR]

CREATE TABLE R_FACT (

customer_name varchar(50) NULL,

amount float NULL);