|
View previous topic :: View next topic
|
| Author |
Message |
Amsar
New User
.jpg)
Joined: 26 Sep 2008
Posts: 84
Location: Chennai
|
|
|
|
Hi,
I am getting sqlocde = -206 for the column name MI_FUTURE_INFO in the select query.
Query:
| Code: |
,MI_RT_CLSF_IN
,MI_FUTURE_INFO
INTO :MI-BATCH-DATE
,:MI-TA-NBR |
Error Message:
| Code: |
DSNX200I -DBT3 BIND SQL ERROR
USING D2DAP001 AUTHORITY
PLAN=(NOT APPLICABLE)
DBRM=TATAJ120
STATEMENT=2747
SQLCODE=-206
SQLSTATE=42703
TOKENS=MI_FUTURE_INFO
CSECT NAME=DSNXORSO
RDS CODE=-100
DSNT233I -DBT3 UNSUCCESSFUL BIND FOR |
I have searched for the cause and i got this describtion.
Cause
This indicates a problem with the delimiters within SQL statements defined -- the delimiter for a character string literal versus the escape character used to delimit a column name.
I did't get exactly what is causing the problem. Anybody has any idea?
Thanks,
Amsar |
|
| Back to top |
|
 |
aishvarya_82
New User
Joined: 11 Nov 2008
Posts: 11
Location: Pune
|
|
|
|
Hi,
I think the problem is with the column MI_FUTURE_INFO.Check the column name again.
Thanks,
Aishvarya |
|
| Back to top |
|
|
Kjeld
Active User
Joined: 15 Dec 2009
Posts: 365
Location: Denmark
|
|
|
|
I think we need to see more of your query. From what I can tell from the part you provided the column names in the select does not match to the host variables in the INTO clause.
Doublecheck the column name against the physical table columns. |
|
| Back to top |
|
|
Amsar
New User
Joined: 26 Sep 2008
Posts: 84
Location: Chennai
|
|
|
|
kjeld & Aishvarya,
Thanks for your time and for your suggestion. 
I have got the issue, the issue was with the devlopment table, i was assumed that table stucture in prod and devlop is same.
but later i came to know this is the additional column which got added in prod and is not there in devlop and for testing purpose i have copied the prod code so for this new column name i was getting the sqlcode= -206 while bind.
Thanks,
Amsar |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Amsar wrote: |
| but later i came to know this is the additional column which got added in prod and is not there in devlop and for testing purpose i have copied the prod code so for this new column name i was getting the sqlcode= -206 while bind. |
so what are you going to do?
remove the column from your sql,
or attempt to have the development tables mirror production? |
|
| Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA
|
|
|
|
| Amsar wrote: |
kjeld & Aishvarya,
but later i came to know this is the additional column which got added in prod and is not there in devlop and for testing purpose i have copied the prod code so for this new column name i was getting the sqlcode= -206 while bind.
|
That strange, changes are usually made it develop before being made in prod. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
Craq, some people like to live dangerously!  |
|
| Back to top |
|
|
Amsar
New User
Joined: 26 Sep 2008
Posts: 84
Location: Chennai
|
|
|
|
Hi Craq,
Same thing surpised me also and that what was my assumption.
But it was emergancy change which was moved from qual region.
Hi Dick,
I am going to remove the column from my sql as i don't need that.
Thanks,
Amsar |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Amsar wrote: |
Hi Dick,
I am going to remove the column from my sql as i don't need that.
|
Amsar,
that is what all of us were afraid you would say! |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| But it was emergancy change which was moved from qual region. |
I know i probably shouldn't ask, but how did the database change(s) get into "qual" before "devlop". . .?
I've not seen "emergency repair" done in a "qual" environment before. . . Developers cannot usually "work" in "qual" and if there is new database definition going on, there will be new data going on and this all needs to be tested before promotion (qual or prod). |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
Dick,
I have seen situations where develop (UNIT) was so far out of sync with production (on going enhancements)
that the only way to repair prod was from qual.
it is expected that qual after being migrated to prod to fix the problem,
would be retrofitted in develop (UNIT).
now the question here is why don't they do that at the shop where the TS performs his magic? |
|
| Back to top |
|
|
Kjeld
Active User
Joined: 15 Dec 2009
Posts: 365
Location: Denmark
|
|
|
|
At my site we have multiple parallel development and test environments.
Each project or maintenance area have the resposibility to maintain databases and data for their application area in the environments they will use, which means that some databases might be left behind in a backlevel state, ie. if changes has been promoted through other environments after a project has been closed. |
|
| Back to top |
|
|
|
|
