Results 1 to 4 of 4
  1. #1
    Join Date
    Oct 2012
    Posts
    4

    Unanswered: SQL Exception Info for exception at level 2

    Hi Everyone,

    Can anybody help me on this issue.

    An error occurred during implicit system action type "2". Information returned for the error includes SQLCODE "-206", SQLSTATE "42703" and message tokens "InstanceX.Column2".. SQLCODE=-727, SQLSTATE=56098, DRIVER=3.63.75

    InstanceX is also a table name.
    And I am using the DB2 Versions
    DB2 v9.5.0.7 Fixpack 7.

    Thank you,
    Munna.

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    Code:
    SQL0206N  "<name>" is not valid in the context where it is used.
    
    Explanation:
    
    This error can occur in the following cases:
    
    *  For an INSERT or UPDATE statement, the specified column is not a
       column of the table, or view that was specified as the object of the
       insert or update.
    *  For a SELECT or DELETE statement, the specified column is not a
       column of any of the tables or views identified in a FROM clause in
       the statement.
    *  For an assignment statement, the reference name does not resolve to
       the name of a column or variable.
    *  For an ORDER BY clause, the specified column is a correlated column
       reference in a subselect, which is not allowed.
    *  For a CREATE TRIGGER, CREATE METHOD, CREATE FUNCTION or CREATE
       PROCEDURE statement:
       *  The reference "<name>" does not resolve to the name of a column,
          local variable or transition variable.
       *  The condition name "<name>" specified in the SIGNAL statement has
          not been declared.
    
    *  For a CREATE TRIGGER statement:
       *  A reference is made to a column of the subject table without using
          an OLD or NEW correlation name.
       *  The left hand side of an assignment in the SET transition-variable
          statement in the triggered action specifies an old transition
          variable where only a new transition variable is supported.
    
    *  For a CREATE FUNCTION statement with a PREDICATES clause:
       *  The RETURN statement of the SQL function references a variable
          that is not a parameter or other variable that is in the scope of
          the RETURN statement.
       *  The FILTER USING clause references a variable that is not a
          parameter name or an expression name in the WHEN clause.
       *  The search target in an index exploitation rule does not match
          some parameter name of the function that is being created.
       *  A search argument in an index exploitation rule does not match
          either an expression name in the EXPRESSION AS clause or a
          parameter name of the function being created.
    
    *  For a CREATE INDEX EXTENSION statement, the RANGE THROUGH clause or
       the FILTER USING clause references a variable that is not a parameter
       name that can be used in the clause.
    
    The statement cannot be processed.
    
    User response:
    
    Verify that the names are specified correctly in the SQL statement. For
    a SELECT statement, ensure that all the required tables are named in the
    FROM clause. For a subselect in an ORDER BY clause, ensure that there
    are no correlated column references. If a correlation name is used for a
    table, verify that subsequent references use the correlation name and
    not the table name.
    
    For a CREATE TRIGGER statement, ensure that only new transition
    variables are specified on the left hand side of assignments in the SET
    transition-variable statement and that any reference to columns of the
    subject table have a correlation name specified.
    
    For a fullselect embedded in XQuery using the db2-fn:sqlquery function,
    a reference within the fullselect must be one of the following: a column
    in the context of the fullselect, a global variable, or a parameter
    passed to the new SQL context using an additional argument of the
    db2-fn:sqlquery function.
    
    sqlcode: -206
    
     sqlstate: 42703
    Andy

  3. #3
    Join Date
    Oct 2012
    Posts
    4
    Thanks Andy,

    I have everything that is here. The same query when using in WAS6.0 is working good but not WAS7.0. Is there any other property that needs to be set.

    Thanks,
    Kumar.

    Quote Originally Posted by ARWinner View Post
    Code:
    SQL0206N  "<name>" is not valid in the context where it is used.
    
    Explanation:
    
    This error can occur in the following cases:
    
    *  For an INSERT or UPDATE statement, the specified column is not a
       column of the table, or view that was specified as the object of the
       insert or update.
    *  For a SELECT or DELETE statement, the specified column is not a
       column of any of the tables or views identified in a FROM clause in
       the statement.
    *  For an assignment statement, the reference name does not resolve to
       the name of a column or variable.
    *  For an ORDER BY clause, the specified column is a correlated column
       reference in a subselect, which is not allowed.
    *  For a CREATE TRIGGER, CREATE METHOD, CREATE FUNCTION or CREATE
       PROCEDURE statement:
       *  The reference "<name>" does not resolve to the name of a column,
          local variable or transition variable.
       *  The condition name "<name>" specified in the SIGNAL statement has
          not been declared.
    
    *  For a CREATE TRIGGER statement:
       *  A reference is made to a column of the subject table without using
          an OLD or NEW correlation name.
       *  The left hand side of an assignment in the SET transition-variable
          statement in the triggered action specifies an old transition
          variable where only a new transition variable is supported.
    
    *  For a CREATE FUNCTION statement with a PREDICATES clause:
       *  The RETURN statement of the SQL function references a variable
          that is not a parameter or other variable that is in the scope of
          the RETURN statement.
       *  The FILTER USING clause references a variable that is not a
          parameter name or an expression name in the WHEN clause.
       *  The search target in an index exploitation rule does not match
          some parameter name of the function that is being created.
       *  A search argument in an index exploitation rule does not match
          either an expression name in the EXPRESSION AS clause or a
          parameter name of the function being created.
    
    *  For a CREATE INDEX EXTENSION statement, the RANGE THROUGH clause or
       the FILTER USING clause references a variable that is not a parameter
       name that can be used in the clause.
    
    The statement cannot be processed.
    
    User response:
    
    Verify that the names are specified correctly in the SQL statement. For
    a SELECT statement, ensure that all the required tables are named in the
    FROM clause. For a subselect in an ORDER BY clause, ensure that there
    are no correlated column references. If a correlation name is used for a
    table, verify that subsequent references use the correlation name and
    not the table name.
    
    For a CREATE TRIGGER statement, ensure that only new transition
    variables are specified on the left hand side of assignments in the SET
    transition-variable statement and that any reference to columns of the
    subject table have a correlation name specified.
    
    For a fullselect embedded in XQuery using the db2-fn:sqlquery function,
    a reference within the fullselect must be one of the following: a column
    in the context of the fullselect, a global variable, or a parameter
    passed to the new SQL context using an additional argument of the
    db2-fn:sqlquery function.
    
    sqlcode: -206
    
     sqlstate: 42703
    Andy

  4. #4
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    My guess it that the problem is at the WAS 7.0 system. You will have to ask on a WAS forum.

    Andy

Posting Permissions

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