You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@sqoop.apache.org by Ajit Koti <aj...@gmail.com> on 2014/09/16 00:01:43 UTC
Sqoop + DB2 Connection Close Error
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
Re: Sqoop + DB2 Connection Close Error
Posted by Anas Mosaad <AM...@eg.ibm.com>.
You'd like to know the application by listing the current applications
using the command "db2 list applications"
Once you get handle of the victim application, run DB2 command db2 force
application (<AppHandle>)
Best Regards,
_________________________________________________________________________________________________
Anas Mosaad
Information Management Specialist
IBM Big Data & Analytics
Phone: +201007434510
E-mail: amosaad@eg.ibm.com
From: Ajit Koti <aj...@gmail.com>
To: user@sqoop.apache.org,
Date: 09/16/2014 08:21 PM
Subject: Re: Sqoop + DB2 Connection Close Error
Yup will do that :)
On Tue, Sep 16, 2014 at 10:58 AM, Gwen Shapira <gs...@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 <aj...@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 <gs...@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 <aj...@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
Re: Sqoop + DB2 Connection Close Error
Posted by Ajit Koti <aj...@gmail.com>.
Sure will do that ,
Thanks
Ajit Koti
On Tue, Sep 16, 2014 at 12:22 PM, Gwen Shapira <gs...@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 <aj...@gmail.com> wrote:
> > Yup will do that :)
> >
> >
> >
> > On Tue, Sep 16, 2014 at 10:58 AM, Gwen Shapira <gs...@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 <aj...@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 <gs...@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 <aj...@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
Re: Sqoop + DB2 Connection Close Error
Posted by Gwen Shapira <gs...@cloudera.com>.
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 <aj...@gmail.com> wrote:
> Yup will do that :)
>
>
>
> On Tue, Sep 16, 2014 at 10:58 AM, Gwen Shapira <gs...@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 <aj...@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 <gs...@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 <aj...@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
Re: Sqoop + DB2 Connection Close Error
Posted by Ajit Koti <aj...@gmail.com>.
Yup will do that :)
On Tue, Sep 16, 2014 at 10:58 AM, Gwen Shapira <gs...@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 <aj...@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 <gs...@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 <aj...@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
Re: Sqoop + DB2 Connection Close Error
Posted by Gwen Shapira <gs...@cloudera.com>.
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 <aj...@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 <gs...@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 <aj...@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
Re: Sqoop + DB2 Connection Close Error
Posted by Ajit Koti <aj...@gmail.com>.
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 <gs...@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 <aj...@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
Re: Sqoop + DB2 Connection Close Error
Posted by Gwen Shapira <gs...@cloudera.com>.
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 <aj...@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
Re: Sqoop + DB2 Connection Close Error
Posted by Ajit Koti <aj...@gmail.com>.
Thanks for the response will try that out.
Ajit
Sorry, i don't have any experience with DB2, but i guess you can try the
latest version of sqoop (1.4.5).
Another thing is you can pass the --verbose flag to get more details.
~Pratik
On Mon, Sep 15, 2014 at 3:01 PM, Ajit Koti <aj...@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
>
Re: Sqoop + DB2 Connection Close Error
Posted by pratik khadloya <ti...@gmail.com>.
Sorry, i don't have any experience with DB2, but i guess you can try the
latest version of sqoop (1.4.5).
Another thing is you can pass the --verbose flag to get more details.
~Pratik
On Mon, Sep 15, 2014 at 3:01 PM, Ajit Koti <aj...@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
>