Results 1 to 2 of 2

Thread: SQL090SN Error

  1. #1
    Join Date
    Jan 2008
    Posts
    8

    Unanswered: SQL090SN Error

    I am getting an error

    Error: 0xC0047062 at datareader, DataReader Source 1 [1]: System.Data.Odbc.OdbcException: ERROR [57014] [IBM][CLI Driver][DB2] SQL0905N Unsuccessful execution due to resource limit being exceeded. Resource name = "ASUTIME", limit = "000000001191" CPU seconds ("000009999999" service units) derived from "SYSIBM.DSNRLST01". SQLSTATE=57014

    when iam running a package in SSIS sql 2005

    what should i be doing any sugestions appriciated...Thanks

  2. #2
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    You should first read up on the error message. There you will find a more verbose Explanation as well as a suggested User Response:
    $ db2 "? sql905"


    SQL0905N Unsuccessful execution due to resource limit being exceeded.
    Resource name = "<resource-name>", limit = "<limit-amount1>" CPU
    seconds ("<limit-amount2>" service units) derived from
    "<limit-source>".

    Explanation:

    The execution of the SQL statement was terminated because a resource
    limit was exceeded.

    The name of the resource whose limit was exceeded is "<resource-name>".
    It is also the name of the column in the resource limit specification
    table from which the limit was derived. The limit that was exceeded in
    CPU seconds is "<limit-amount1>" and in service units it is
    "<limit-amount2>". The "<resource-name>" may be ASUTIME, which is the
    number of CPU seconds permitted for each SQL statement. The maximum
    number of CPU seconds permitted is "<limit-amount1>". The maximum number
    in service units is "<limit-amount2>".

    The source used to derive the limit-amount is "<limit-source>" and is
    either the name of a resource limit specification table or a 'system
    parameter'. If the source is a system parameter, the resource limit
    specification table did not contain an applicable entry or an error
    occurred while accessing the table. In either case, the limit is
    obtained from an install (system) parameter.

    User response:

    Determine why this SQL statement took so long and take appropriate
    action. Consider simplifying the SQL statement, restructuring tables and
    indexes, or contacting the installation group responsible for
    maintaining the resource limit specification tables.

    An application program that receives this return code can execute
    additional SQL statements.
    p.s: It would be nice if you would let us know your DB2 version and platform. Some details on the SQL statement would also be helpful.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

Posting Permissions

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