sqoop-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ajit Koti <ajitk...@gmail.com>
Subject Re: Sqoop + DB2 Connection Close Error
Date Tue, 16 Sep 2014 20:32:49 GMT
Sure will do that ,


Thanks
Ajit Koti

On Tue, Sep 16, 2014 at 12:22 PM, Gwen Shapira <gshapira@cloudera.com>
wrote:

> Do you want to also open a Sqoop bug report in issues.apache.org? This
> will allow us to track the issue, work-around and a real fix in the
> future.
>
> On Tue, Sep 16, 2014 at 10:20 AM, Ajit Koti <ajitkoti@gmail.com> wrote:
> > Yup will do that :)
> >
> >
> >
> > On Tue, Sep 16, 2014 at 10:58 AM, Gwen Shapira <gshapira@cloudera.com>
> > wrote:
> >>
> >> I don't know enough DB2 to help. If your organization has a DBA, its
> >> her job to know :)
> >>
> >> On Tue, Sep 16, 2014 at 8:56 AM, Ajit Koti <ajitkoti@gmail.com> wrote:
> >> > Hi,
> >> >
> >> > Thanks for the response.
> >> >
> >> >  Its not a blocker, We get the required data , but not sure how to
> close
> >> > the
> >> > connections which are opened by sqoop.
> >> >  If we don't close them , we would soon run over the max open
> connection
> >> > limit.
> >> >
> >> > Thanks
> >> > Ajit Koti
> >> >
> >> > On Mon, Sep 15, 2014 at 8:49 PM, Gwen Shapira <gshapira@cloudera.com>
> >> > wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> 1. I think it may be a bug. Most databases don't care if we try to
> >> >> close database without closing the transaction first. Its possible
> >> >> that Sqoop misses this step and DB2 errors out.
> >> >>
> >> >> 2. Is this a blocker for you? It looks like you should be getting all
> >> >> your data. Perhaps you can work-around with a small script that will
> >> >> kill the leftover transaction and connection on the DB2 side?
> >> >>
> >> >> Gwen
> >> >>
> >> >> On Mon, Sep 15, 2014 at 3:01 PM, Ajit Koti <ajitkoti@gmail.com>
> wrote:
> >> >> > Hi,
> >> >> >
> >> >> >
> >> >> > I am using db2jcc4.jar , sqoop 1.4.2,
> >> >> > When sqoop tries to close the connection, it throws the below
> >> >> > warning,
> >> >> >
> >> >> >
> >> >> >
> >> >> > 14/09/15 16:30:39 INFO mapreduce.ImportJobBase: Transferred 24.4863
> >> >> > KB
> >> >> > in
> >> >> > 14.0591 seconds (1.7417 KB/sec)
> >> >> > 14/09/15 16:30:39 INFO mapreduce.ImportJobBase: Retrieved 578
> >> >> > records.
> >> >> > 14/09/15 16:30:39 INFO util.AppendUtils: Appending to directory
> test
> >> >> > 14/09/15 16:30:39 INFO util.AppendUtils: Using found partition
36
> >> >> > 14/09/15 16:30:39 INFO tool.ImportTool: Saving incremental import
> >> >> > state
> >> >> > to
> >> >> > the metastore
> >> >> > 14/09/15 16:30:39 INFO tool.ImportTool: Updated data for job:
> >> >> > db2_test_fetch44
> >> >> >
> >> >> > 14/09/15 16:30:39 WARN tool.BaseSqoopTool: Error while closing
> >> >> > connection:
> >> >> > com.ibm.db2.jcc.am.SqlException: [jcc][t4][10251][10308][4.14.119]
> >> >> > java.sql.Connection.close() requested while a transaction is in
> >> >> > progress
> >> >> > on
> >> >> > the connection.
> >> >> > The transaction remains active, and the connection cannot be
> closed.
> >> >> > ERRORCODE=-4471, SQLSTATE=null
> >> >> >
> >> >> >
> >> >> > Has anyone faced it before , any workarounds and any suggestion
> would
> >> >> > be
> >> >> > helpful.
> >> >> >
> >> >> > Thanks
> >> >> > Ajit
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Thanks
> >> > Ajit Koti
> >> > about.me/ajitkoti
> >
> >
> >
> >
> > --
> > Thanks
> > Ajit Koti
> > about.me/ajitkoti
>



-- 
Thanks
Ajit Koti
about.me/ajitkoti

Mime
View raw message