Stream component 'st_0_ORACLE - database' terminated (Error)

[guilherme-matte]

Hey guys!

We have a process that seems to be running fine, but I'm always getting the following error, not sure whether I should act on it or not. The task runs normally, and data is still being updated on the targe tables.

Stream component 'st_0_ORACLE- db gisprod' terminated
Stream component failed at subtask 0, component st_0_ORACLE- db gisprod
Error executing source loop

Any ideas what it could be?

[john_wang]

Hello @guilherme-matte ,

Thanks for reaching out!

It's hard to tell by the piece of error this time. In general it's a source side problem, maybe it was missing a redo log for continuing the CDC , or network broken etc (as we did not get the diagnostic package I can not tell more here). You may go to Replicate Console --> Monitor (rather than Designer perspetive) --> Tools --> Log Management --> SOURCE_CAPTURE, set it to "Trace" (or "Verbose") then check the task log file (on Windows the default location is "C:\Program Files\Attunity\Replicate\data\logs") to get great detailed information. Take note set it to Verbose may get huge size task log file (depends on the data volume) so please set it back to INFO as earlier as possible.
BTW, set the max task log file 1G auto-rollover to make sure the log file is easy to transfer/read:

If you need additional assistance please open support ticket and attach the Diag Packages(here is community area all attachments are public, please do not attach Diag Packages here).

Hope this helps.

Regards,
John.

[Steve_Nguyen · Accepted solution]

you should set ENABLE=BROKEN

see article

https://community.qlik.com/t5/Official-Support-Articles/Task-using-Oracle-as-Source-or-Target-is-get...

[guilherme-matte]

Thank you for the inputs guys, i will try these options and get back to you as soon as i have something. 

Cheers!

[guilherme-matte]

Hello guys!

I've changed the log method, but it has been 10 days since I have not seen the error message anymore.

Guess I will wait again for the message to try the Enable=Broken. Also will stick with the INFO logging method, since I'm not sure when I'm going to see the error message again.

Are there any downsides to using the Enable=Broken ? Should I try using it anyways? 

Kind Regards!

[Dana_Baldwin]

Hi @guilherme-matte 

No harm in setting enable=broken. There will be a small number of additional packets sent between the server & client to confirm that the server process serving the client is still there. Here's some additional information on it: dbi Blog (dbi-services.com)

Thanks,

Dana