topic Re: AMC on Oracle -- talendMeter_DB IO Error: Connection reset in Talend Studio

AMC on Oracle -- talendMeter_DB IO Error: Connection reset

Croix — Thu, 25 Jan 2018 17:01:58 GMT

Hi,

On longer running jobs, I keep getting a FATAL error with the message "talendMeter_DB IO Error: Connection reset". I know it is the AMC connection because if I turn the AMC off and run the job it completes without this error.

Does anyone know how to fix this issue?

We're using an Oracle ODA 12c for the AMC database.

Thanks!

Croix

Re: AMC on Oracle -- talendMeter_DB IO Error: Connection reset

Anonymous — Mon, 29 Jan 2018 07:11:04 GMT

Hello,

Could you please clarify in which Talend version/edition you are?

Here is online installation guide V 6.5 about:TalendHelpCenter:Compatible databases.

Could you please refer it to see if your Oracle ODA 12c is in the supported list?

Best regards

Sabrina

Re: AMC on Oracle -- talendMeter_DB IO Error: Connection reset

Croix — Wed, 07 Feb 2018 15:49:55 GMT

Hi,

The page connected to the link you shared said that Oracle 12c, the version we have, is not only supported but recommended so that's good.

The version of Talend we are using is the Talend Big Data Platform 6.2.1.

Thanks

Re: AMC on Oracle -- talendMeter_DB IO Error: Connection reset

Anonymous — Thu, 08 Feb 2018 09:16:42 GMT

Hello,

With your Talend Big Data Platform 6.2.1 subscription solution, could you please create a case on talend support portal so that we can give you a remote assistance on your AMC Oracle DB connection issue through support cycle with priority?

Best regards

Sabrina

Re: AMC on Oracle -- talendMeter_DB IO Error: Connection reset

Croix — Thu, 08 Feb 2018 16:53:50 GMT

Yes, I've already created a case with support.

Thank you!

Re: AMC on Oracle -- talendMeter_DB IO Error: Connection reset

Croix — Tue, 13 Feb 2018 15:16:56 GMT

I figured this issue out.

After I put a tFlowMeter and a tFlowMeterCatcher and wrote it to the AMC I stopped getting this error.

The way that I figured it out was that I looked in the flow meter table in the AMC database and noticed that there were almost no entries when I ran the job. I looked into it and figured out that the tFlowMeter and tFlowMeterCatcher wrote data to this table.

So, I think it was timing out because nothing was writing to the table. When I put these two components into the job and pointed them to the AMC flow meter table, the error went away.