GoldenGate

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Goldengate with conditional parameters.

844166Mar 18 2011 — edited Apr 2 2011

Hi all,

I have one table source side which is need to be replicat on target side.

I want a conditional replicatio on this.

The situation is
==========
Target Side:
* one table TABLE_NEED having column NAME,FREQUENCY

Source Side:
* one table TABLE_NEED having coumn NAME,FREQUENCY,USED_BY
==========

Now I want conditional replication on the target side on column USED_BY

The value for this column (USED_BY) is dependent on the value of FREQUENCY column.

If FREQUENCY column is NULL then the value of the USED_BY is replicated to a value of NAME

and if FREQUENCY column is ANY VALUE then the value of the USED_BY is replicated to a value of FREQUENCY

Note: Other two columns NAME,FREQUENCY is just a simple replication. Only ti differs to the USED_BY column at target side.

WE CAN GO FOR THE TRIGGERS/PROCEDURES ON THE TARGET SIDE FOR THIS KIND OF UPDATES BUT THE REQUIREMENT IS TO GET THIS UPDATES ONLY THROUGH THE GOLDENGATE.

please please help me on this question.

dvohra21

It is documented.

"The Oracle.connect() method defaults to a false setting of the auto-commit flag. However, it also has signatures to set it explicitly. In the Oracle JDBC implementation, the auto-commit flag defaults to true."

Key Programming Considerations

kdario

Well, this is documentation for sqlj and first sentence just confirms what I said(that auto-commit by default should be false)

Just to clarify my original post:

When you retrieve jdbc connection in adf application(for example, in app module impl class), that connection already has autocommit=false (because framework will set this property)

Difference between adf 11.x and 12.x is in setting db proxy user (by using conn.openProxySession() ) :

In 11.x (which uses ojdbc6 driver) invocation of openProxySession() method will preserve autocommit=false

In 12.x (which uses ojdbc7 driver) invocation of openProxySession() method will reset autocommit to true (and adf app will not work correctly with this setting)

Dario

dvohra21

ojdbc7.jar is based on JDBC 4.1 and JDBC 4.1 still sets auto-commit to true by default.

"The default is for auto-commit mode to be enabled when the Connection object is

created."

http://download.oracle.com/otn-pub/jcp/jdbc-4_1-mrel-spec/jdbc4.1-fr-spec.pdf?AuthParam=1404073866_5e28356fa3b11ea367d6b…

Could auto commit be false for the PROXYTYPE_USER_NAME specified?

OracleConnection (Oracle Database JDBC Java API Reference)

dvohra21

CONNECTION_PROPERTY_AUTOCOMMIT_DEFAULT is true in both 11g and 12c.

http://docs.oracle.com/cd/E18283_01/appdev.112/e13995/constant-values.html#oracle_jdbc_OracleConnection_CONNECTION_PROPERTY_AUTOCOMMIT_DEFAULT

http://docs.oracle.com/cd/E16655_01/appdev.121/e17663/constant-values.html#oracle_jdbc_OracleConnection_CONNECTION_PROPERTY_AUTOCOMMIT_DEFAULT