Results 1 to 5 of 5
  1. #1
    Join Date
    Jul 2015
    Posts
    5

    Unanswered: Federation With Netezza Session Timeout

    As per a previous post, the business challenge I have is to pull data from a Netezza warehouse on a daily basis. Since the database name was 20 characters long, I was unable to CATALOG the database and run a CURSOR command.

    Per the suggestions here, we installed InfoSphere Federation server and were able to connect to the Netezza database via ODBC.

    After some hours of inactivity, when I tried to connect to the federated tables, I first received this error code:

    Unexpected error code "HY000" received from data source "NETEZZA_DATABASE". Associated text and tokens are "FATAL 1: Connection Terminated - session timeout exceede".. SQLCODE =-1822, SQLSTATE=560DB, DRIVER=3.67.28

    Subsequent attempts yield the following error code:

    A communication error "08S01" occurred sending or receiving data from the remote database.. SQLCODE=-30080, SQLSTATE=08001, DRIVER=3.67.28


    - Is there some sort of parameter I can set to have DB2 attempt to reconnect to the Netezza DB after an error or certain idle period?
    - If not, is there a CLP command that I could schedule to run immediately before the daily import that would open/reopen the connection to the Netezza DB?

  2. #2
    Join Date
    May 2012
    Location
    Canberra, Australia
    Posts
    176
    Provided Answers: 6
    I think the problem may be at the Netezza end. A db2trc may be required to see any underlying sqlcodes. This link is for a different problem but in some respects a similar message
    http://www-01.ibm.com/support/docvie...id=swg21377860
    Andy

    "All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can’t get them together again, there must be a reason. By all means, do not use hammer.” — IBM maintenance manual, 1975 "

  3. #3
    Join Date
    Jul 2015
    Posts
    5
    I wasn't able to find a way to fix the underlying issue, so what I've done is schedule an ALTER SERVER NZASVRNAME OPTIONS (SET PUSHDOWN 'Y') before each job, which seems to re-establish the federated connection.

  4. #4
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    pushdown has another meaning - have you tried native connection to your db without federation server - have you checked infocenter for specific settings to this type of db
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified
    http://www.infocura.be

  5. #5
    Join Date
    Jul 2015
    Posts
    5
    Quote Originally Posted by przytula_guy View Post
    pushdown has another meaning - have you tried native connection to your db without federation server - have you checked infocenter for specific settings to this type of db
    I run into the same issue with a direct connection to the Netezza database (session timeout after an hour or two).

    I arbitrarily selected re-applying PUSHDOWN just because I noted that when I changed a SERVER parameter, it somehow reactivated an otherwise broken connection.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •