If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Sqlstate=42703

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old
Registered User
 
Join Date: Jan 2011
Posts: 1
Sqlstate=42703

When i try to dynamically insert the data into the table, i am getting this follwoing error,
PROC_FCT: [IBM][CLI Driver][DB2/AIX64] SQL0206N "Column name is not valid in the context where it is used. SQLSTATE=42703
Reply With Quote
  #2 (permalink)  
Old
Registered User
 
Join Date: Jan 2003
Posts: 4,098
You have a column name that is not valid in the context that you are using it. Please post your SQL and the underlying tables DDL and maybe you will get a better answer.

Andy
Reply With Quote
  #3 (permalink)  
Old
Registered User
 
Join Date: Jan 2010
Posts: 335
db2 ? SQL0206N


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.
* When referencing a field in a row type variable, the reference name
does not resolve to the name of any field in the row type.
* For an ORDER BY clause, the specified column is a correlated column
reference in a subselect, which is not allowed.
* For a SELECT statement in a parameterized cursor constructor, the
reference to "<name>" does not match a column or in-scope variable.
Local variables and routine SQL parameters are not considered in
scope for parameterized cursors.
* For a standalone compound SQL (compiled) statement:
* The reference "<name>" does not resolve to the name of a column or
local variable that is in scope.
* The condition name "<name>" specified in the SIGNAL statement has
not been declared.
* When referencing a field in a row type variable, the reference
name does not resolve to the name of any field in the row type.

* 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 reference "<name>" resolves to the name of a local variable
that is not available in the current scope.
* The condition name "<name>" specified in the SIGNAL statement has
not been declared.
* When referencing a field in a row type variable, the reference
name does not resolve to the name of any field in the row type.

* 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.
* For a parameterized cursor variable reference, a local SQL variable
or SQL parameter referenced in the select statement used in the
definition of a parameterized cursor variable is not available in the
current scope.

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 standalone compound SQL statement, CREATE FUNCTION, CREATE
PROCEDURE, or CREATE TRIGGER statement, verify that the columns or
variables are available in the scope of the current compound SQL
statement.

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
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On