
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ORA-25412 error occurred when applying to ORACLE ADW target
Hi,
I tested Oracle ADW taget, I met ora-25412 error often. "Oracle" says to change it to "OCIStmtPrepare2()" and use it.
Does Replicate use what function ? "OCIStmtPrepare2()" or "OCIStmtPrepare" ?
Replicate version : November 2021 (2021.11.469)
target oracle ADW version : 19.19
source oracle : 19.11
oracle client : 19.3
Regards
KwangHo
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This ORA error 25412 is relatively hard to find. It is clear that it has to do with TAF - Transparent Application Failover. This is something you really do not want to have active for the Replicate connection. It will non-transparently- deal with Oracle errors for you.
Replicate only uses OCIStmtPrepare. Some google searched search Oracle tells us OCIStmtPrepare is deprecated and they should all be replaced by OCIStmtPrepare2... to support TAF.
This can be disable by using Set OCI_ATTR_TRANSACTIONAL_TAF to FALSE ... but I think that cannot be done in Replicate today.
Other suggest to make the connection type "-failovertype NONE" instead of "-failovertype TRANSACTION". I think you can do that.
I think a support call / and or suggestion is in order. Replicate MIGHT want to switch to OCIStmtPrepare2. Personally I think it should just document a restriction connecting to TAF databases, hopefully with a setting/instructions to making it not even try. KISS
Hein.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi KwangHo,
As this is a Oracle error we would like to better understand when exactly it is happening. Could you please open a case for this issue and attach to the case the task diagnostic package and the task log where you get the error so we can further troubleshoot the problem.
Thanks & regards,
Orit

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
this is test environment of current customer. I will ask customer about reproduce this error. yesterday and today did not occurred . I will get new error log, I will create case.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK. Thanks!
Regards,
Orit

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This ORA error 25412 is relatively hard to find. It is clear that it has to do with TAF - Transparent Application Failover. This is something you really do not want to have active for the Replicate connection. It will non-transparently- deal with Oracle errors for you.
Replicate only uses OCIStmtPrepare. Some google searched search Oracle tells us OCIStmtPrepare is deprecated and they should all be replaced by OCIStmtPrepare2... to support TAF.
This can be disable by using Set OCI_ATTR_TRANSACTIONAL_TAF to FALSE ... but I think that cannot be done in Replicate today.
Other suggest to make the connection type "-failovertype NONE" instead of "-failovertype TRANSACTION". I think you can do that.
I think a support call / and or suggestion is in order. Replicate MIGHT want to switch to OCIStmtPrepare2. Personally I think it should just document a restriction connecting to TAF databases, hopefully with a setting/instructions to making it not even try. KISS
Hein.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Hein.
I checked replication status. It is OK. Tasks met ORA-25412 , After than tasks reconnect and recover last commit point or save point.
Best Regards,
KwangHo
