Dynamic sql error code 206

Change your case, as it looks like your database layer is automatically quoting it if you use CamelCase.

A quick test in a Firebird 2.5 database here shows:

SQL> select t1.usuario, t1.NoExisto from sg_usuario t1;
Statement failed, SQLSTATE = 42S22
Dynamic SQL Error
-SQL error code = -206
-Column unknown
-T1.NOEXISTO
-At line 1, column 23


SQL> select t1.usuario, "t1.NoExisto" from sg_usuario t1;
Statement failed, SQLSTATE = 42S22
Dynamic SQL Error
-SQL error code = -206
-Column unknown
-t1.NoExisto
-At line 1, column 34

As you see, the database engine generates an error with camel case only when it gets the SQL query using quotes.

I suggest you to try myfield_id or use the correct case you have in your field name.

    select 
        table1.pkfield1,
        table1.field_no,
        table1.fk1_id,
        table1.fk2_id,
        table1.myfield_id, 
        table1.bfield,
        table2.desc1,
        table2.desc2,
        table2.desc3
    from table2
    right outer table1 on (table2.pk1_id = table1.fk1_id)
    Order by table1.fk1_id, table1.field_no desc

Submitted by: Ukrtelecom (ukrtelecom)

WORK —
insert into stat_wtmp (bill_serv_id,
login,
domain_name,
calling_station_id,
called_station_id,
nas_ip_address,
framed_ip_address,
nas_port_id,
session_id,
connect_info,
time_begin,
session_active,
cur_input_octets,
cur_output_octets,
/* connect_info,*/
time_end
)
values(:CUR_BILL_SERVICE_ID,
:login,
:domain_name,
:caller_id,
:called_id,
:nas_ip_addr,
:user_ip_addr,
:nas_port_id,
:session_id,
:connect_info,
:packet_timestamp,
:cur_session_active,
:input_octets,
:output_octets,
/* :connect_info,*/
:packet_timestamp);

NOT WORK —
insert into stat_wtmp (bill_serv_id,
login,
domain_name,
calling_station_id,
called_station_id,
nas_ip_address,
framed_ip_address,
nas_port_id,
session_id,
connect_info,
time_begin,
session_active,
cur_input_octets,
cur_output_octets,
connect_info,
time_end
)
values(:CUR_BILL_SERVICE_ID,
:login,
:domain_name,
:caller_id,
:called_id,
:nas_ip_addr,
:user_ip_addr,
:nas_port_id,
:session_id,
:connect_info,
:packet_timestamp,
:cur_session_active,
:input_octets,
:output_octets,
:connect_info,
:packet_timestamp);

Dynamic SQL Error.
SQL error code = -206.
unknown ISC error 336397210.
unknown ISC error 336397208.
FIELD — connect_info;
TABLE STAT_WTMP:

CREATE TABLE STAT_WTMP (
ID_WTMP_ITEM ID /* ID = INTEGER DEFAULT 0 */,
BILL_SERV_ID ID /* ID = INTEGER DEFAULT 0 */,
NAS_IP_ADDRESS IPADDRESS /* IPADDRESS = VARCHAR(15) */,
NAS_PORT_ID BIGINTEGER /* BIGINTEGER = BIGINT */,
TIME_BEGIN ACCOUNT /* ACCOUNT = INTEGER */,
TIME_END ACCOUNT /* ACCOUNT = INTEGER */,
SESSION_TIME COUNTER /* COUNTER = INTEGER */,
CALLING_STATION_ID VARCHAR128 /* VARCHAR128 = VARCHAR(128) */,
CALLED_STATION_ID VARCHAR128 /* VARCHAR128 = VARCHAR(128) */,
FRAMED_IP_ADDRESS IPADDRESS /* IPADDRESS = VARCHAR(15) */,
SESSION_ID VARCHAR128 /* VARCHAR128 = VARCHAR(128) */,
INPUT_OCTETS BIGINTEGER DEFAULT 0 /* BIGINTEGER = BIGINT */,
CUR_INPUT_OCTETS BIGINTEGER DEFAULT 0 /* BIGINTEGER = BIGINT */,
OUTPUT_OCTETS BIGINTEGER DEFAULT 0 /* BIGINTEGER = BIGINT */,
CUR_OUTPUT_OCTETS BIGINTEGER DEFAULT 0 /* BIGINTEGER = BIGINT */,
CONNECT_INFO VARCHAR64 /* VARCHAR64 = VARCHAR(64) */,
LOGIN VARCHAR32 /* VARCHAR32 = VARCHAR(32) */,
DOMAIN_NAME VARCHAR64 /* VARCHAR64 = VARCHAR(64) */,
SESSION_ACTIVE TRUEFALSE DEFAULT 1 /* TRUEFALSE = INTEGER */,
DATE_WR DATETIME DEFAULT ‘now’ /* DATETIME = TIMESTAMP */,
SPEED_UP VARCHAR16 /* VARCHAR16 = VARCHAR(16) */,
SPEED_DOWN VARCHAR16 /* VARCHAR16 = VARCHAR(16) */
);

Нравится ресурс? Помоги проекту!

информация о разделе

Данный раздел предназначается исключительно для обсуждения вопросов использования языка запросов SQL. Обсуждение общих вопросов, связанных с тематикой баз данных — обсуждаем в разделе «Базы данных: общие вопросы». Убедительная просьба — соблюдать «Правила форума» и не пренебрегать «Правильным оформлением своих тем». Прежде, чем создавать тему, имеет смысл заглянуть в раздел «Базы данных: FAQ», возможно там уже есть ответ.

[ Script execution time: 0,0345 ]   [ 15 queries used ]   [ Generated: 9.02.23, 10:34 GMT ]  

I updated today. jan 23.

It refuses to open the database at all in version 4.

In version 3, when I got the message on startup no database was displayed.
I would then exit out and start the program from quick start icon in the tray.

Again I got the same message but this time my database was open.

I could add to it but could not export it. It does save any changes on exit though.

Now I cannot access the current database.

here are the two messages.

WHEN I FIRST START THE PROGRAM:

There was an error during the execution of this program.
The application might become unstable and even useless.
It’s recommended that you save your work and close this application.

Dynamic SQL Error
SQL error code = -206
Column unknown
OLD.USEGLOBALFOLDERS

Exception log with detailed tech info. Generated on 01/23/2011 1:53 PM.
You may send it to the application vendor, helping him to understand what had happened.
Application title: EssentialPIM
Application file: C:Program Files (x86)EssentialPIMEssentialPIM.exe
Application: EssentialPIM 4.01
——————————————————————————
Exception class: EIBInterBaseError
Exception message: Dynamic SQL Error
SQL error code = -206
Column unknown
OLD.USEGLOBALFOLDERS
At line 5, column 10.
Exception address: 004CEEB3
——————————————————————————
Main thread ID = 2756
Exception thread ID = 2756
——————————————————————————
Active Controls:
1927376 ExceptionDialog TextMemo

——————————————————————————
Exception stack
Stack list, generated 01/23/2011 1:53 PM
[004CEEAE]{EssentialPIM.exe} IB.IBDataBaseError (Line 411, «IB.pas» + 38)
——————————————————————————
Call stack for main thread
Stack list, generated 01/23/2011 1:53 PM
(0004945E){ntdll.dll } [7795A45E]
——————————————————————————
System : Windows Vista Home Edition, Version: 6.0, Build: 1772, «Service Pack 2»
Memory: 4095; free 4095
Display : 1024×768 pixels, 32 bpp
——————————————————————————

NOW AFTER I EXIT AND TRY TO START WITH THE QUICK START ICONIN THE TRAY

There was an error during the execution of this program.
The application might become unstable and even useless.
It’s recommended that you save your work and close this application.

unsuccessful metadata update
STORE RDB$RELATION_FIELDS failed
attempt to store duplicate value (visible to active transactions) in unique index «RDB$INDEX_15».

Exception log with detailed tech info. Generated on 01/23/2011 1:54 PM.
You may send it to the application vendor, helping him to understand what had happened.
Application title: EssentialPIM
Application file: C:Program Files (x86)EssentialPIMEssentialPIM.exe
Application: EssentialPIM 4.01
——————————————————————————
Exception class: EIBInterBaseError
Exception message: unsuccessful metadata update
STORE RDB$RELATION_FIELDS failed
attempt to store duplicate value (visible to active transactions) in unique index «RDB$INDEX_15».
Exception address: 004CEEB3
——————————————————————————
Main thread ID = 2756
Exception thread ID = 2756
——————————————————————————
Active Controls:
1977843 ExceptionDialog TextMemo
1964083 MainForm
1954957 ExceptionDialog DetailsMemo
1945831 ExceptionDialog TextMemo
1936705 ExceptionDialog DetailsBtn
1927407 ExceptionDialog OkBtn
1927376 ExceptionDialog TextMemo

——————————————————————————
Exception stack
Stack list, generated 01/23/2011 1:54 PM
[004CEEAE]{EssentialPIM.exe} IB.IBDataBaseError (Line 411, «IB.pas» + 38)
——————————————————————————
Call stack for main thread
Stack list, generated 01/23/2011 1:54 PM
(0004945E){ntdll.dll } [7795A45E]
——————————————————————————
System : Windows Vista Home Edition, Version: 6.0, Build: 1772, «Service Pack 2»
Memory: 4095; free 4095
Display : 1024×768 pixels, 32 bpp
——————————————————————————
PrevExceptions:
1963522 Dynamic SQL Error
SQL error code = -206
Column unknown
OLD.USEGLOBALFOLDERS
At line 5, column 10

Thanks for any help you can give