SQL0101N The statement is too long or too complex. SQLSTATE=54001

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • bhavna.k.dwivedi@gmail.com

    #1

    SQL0101N The statement is too long or too complex. SQLSTATE=54001

    Hi,
    I am getting the error "SQL0101N The statement is too long or too
    complex. SQLSTATE=54001" while trying to rebind a package on the
    database. I am connected as instance owner.Here's the info on the UDB
    software installed on db server -
    DB21085I Instance "pdpd154" uses "32" bits and DB2 code release
    "SQL08021"
    with level identifier "03020106".
    Informational tokens are "DB2 v8.1.0.83", "special_14190" ,
    "U803800_14190" , and
    FixPak "8".
    Product is installed at "/opt/IBM/db2/V8.1".

    The SP perfoms only selects on the db. There is no INSERT/UPDATE/
    DELTE. The selects are performed via a view (union all view on top of
    12 tables). Recently we added some more tables to the db and now the
    view has been recreated to include a total of 42 tables. After this we
    tried to rebind all the SPs and one of them is failing with the above
    error. I tried changing the STMTHEAP also. Earlier it was 4096; i
    changed it to 32768....but still no luck with the rebind.
    Please advise what can be done to resolve this.
  • w.l.fischer@googlemail.com

    #2
    Re: SQL0101N The statement is too long or too complex. SQLSTATE=54001

    On Sep 19, 7:45 pm, bhavna.k.dwiv.. .@gmail.com wrote:
    Hi,
    I am getting the error "SQL0101N  The statement is too long or too
    complex.  SQLSTATE=54001" while trying to rebind a package on the
    database. I am connected as instance owner.Here's the info on the UDB
    software installed on db server -
    DB21085I  Instance "pdpd154" uses "32" bits and DB2 code release
    "SQL08021"
    with level identifier "03020106".
    Informational tokens are "DB2 v8.1.0.83", "special_14190" ,
    "U803800_14190" , and
    FixPak "8".
    Product is installed at "/opt/IBM/db2/V8.1".
    >
    The SP perfoms only selects on the db. There is no INSERT/UPDATE/
    DELTE. The selects are performed via a view (union all view on top of
    12 tables). Recently we added some more tables to the db and now the
    view has been recreated to include a total of 42 tables. After this we
    tried to rebind all the SPs and one of them is failing with the above
    error. I tried changing the STMTHEAP also. Earlier it was 4096; i
    changed it to 32768....but still no luck with the rebind.
    Please advise what can be done to resolve this.
    You could try to reduce the optimization level and see if it helps...
    It's not only the length of the statement, but also the complexity of
    the execution plan that is generated.

    Comment

    Working...