Hi Naveen, Thanks for confirming it works in RAM to DB case for you. As for DB to RAM, that's not supported by Ignite and you need to use tools like Oracle Golden Gate to move the changes from Oracle to Ignite: https://dzone.com/articles/syncing-a-gridgain-in-memory-computing-cluster-and
-- Dens On Wed, Mar 21, 2018 at 7:34 AM, Naveen <[email protected]> wrote: > Hi Denis > > It works perfectly fine, probably I am first one to try dual backing stores > - native and Oracle. > > I was able to update the data in underlying backing store Oracle with below > settings > > <property name="readThrough" value="true"/> > <property name="writeThrough" value="true"/> > <property name="writeBehindEnabled" value="true"/> > <property name="writeBehindFlushFrequency" > value="120000"/> > > > All the updates always happen thru RAM to DB, however my requirement is, > first data gets updated by external systems in DB first and that should get > reflected in RAM, can we achieve this just be setting some properties ? > > It works fine, for new records if it is not there in RAM and there in DB, > it > gets it from DB and load it to RAM, however if we update any column in DB > which is not reflecting in RAM. > > Thanks > Naveen > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
