Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

michael.riksman

Hi,

 

·         your ODBC driver version

psqlODBC is v11.01.000.

 

SQL_DRIVER_ODBC_VER reports “3.51”

[6608-0.002]    info.c[PGAPI_GetInfo]71: entering...fInfoType=77

[6608-0.002]    info.c[PGAPI_GetInfo]1032: p='03.51', len=0, value=0, cbMax=12

 

·         your PostgreSQL database version

v10.9 x86

Running on Windows 10 32-bit

 

·         any error messages you saw on the screen

 

The client application (Rockwell FactoryTalk), has a button which can automatically create the tables in an existing database.

It created a table successfully that DID NOT have a TIMESTAMP column. But I had to manually create two tables that had a TIMESTAMP column.

When I clicked ‘OK’ to accept the changes, I get this error;

 

 

FactoryTalk works fine with Microsoft SQL ODBC.

 

·         the debug log (mylog_????.log) file (you will have to enable the mylog driver option)

 

Attached.

 

 

 

 

 

 

I ran the ODBC Test tool, and connected via ODBC version 2 (as this is what FactoryTalk appears to be using)

[2892-0.001]odbcapi30.[SQLSetEnvAttr]477: Entering att=200,2

 

I then ran a GetTypeInfo on SQL_TIMESTAMP(11), and it returns SQL_SUCCESS

 

But in the logs, it shows this;

[6608-1677.216]odbcapiw.c[SQLGetTypeInfoW]1015: Entering

[6608-1677.216]    info.c[PGAPI_GetTypeInfo]1115: entering...fSqlType=93

[6608-1677.216]statement.[SC_recycle_statement]812: entering self=0052D2E0

[6608-1677.216] qresult.c[QR_Constructor]173: entering

[6608-1677.216] qresult.c[QR_Constructor]242: leaving

[6608-1677.216]statement.[SC_set_Result]531: (0052D2E0, 00539F48)

[6608-1677.216] qresult.c[QR_Destructor]344: entering

[6608-1677.216]    bind.c[extend_column_bindings]718: entering ... self=0052D370, bindings_allocated=0, num_columns=19

[6608-1677.216]    bind.c[extend_column_bindings]762: leaving 004F8C30

[6608-1677.216] qresult.c[QR_set_num_fields]40: entering

[6608-1677.216] qresult.c[QR_set_num_fields]44: leaving

 

It appears the fSQLType changed from SQL_TIMESTAMP(11) to SQL_TYPE_TIMESTAMP(93)…? Could this be what is causing the issue?

 

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 


mylog_DatalogEd_15404.log (179K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

Inoue, Hiroshi-2
Hi Michael,

Could you try the test driver if I provide a Windows test driver?

regards,
Hiroshi Inoue

On 2019/07/18 18:18, [hidden email] wrote:

Hi,

 

·         your ODBC driver version

psqlODBC is v11.01.000.

 

SQL_DRIVER_ODBC_VER reports “3.51”

[6608-0.002]    info.c[PGAPI_GetInfo]71: entering...fInfoType=77

[6608-0.002]    info.c[PGAPI_GetInfo]1032: p='03.51', len=0, value=0, cbMax=12

 

·         your PostgreSQL database version

v10.9 x86

Running on Windows 10 32-bit

 

·         any error messages you saw on the screen

 

The client application (Rockwell FactoryTalk), has a button which can automatically create the tables in an existing database.

It created a table successfully that DID NOT have a TIMESTAMP column. But I had to manually create two tables that had a TIMESTAMP column.

When I clicked ‘OK’ to accept the changes, I get this error;

 

 

FactoryTalk works fine with Microsoft SQL ODBC.

 

·         the debug log (mylog_????.log) file (you will have to enable the mylog driver option)

 

Attached.

 

 

 

 

 

 

I ran the ODBC Test tool, and connected via ODBC version 2 (as this is what FactoryTalk appears to be using)

[2892-0.001]odbcapi30.[SQLSetEnvAttr]477: Entering att=200,2

 

I then ran a GetTypeInfo on SQL_TIMESTAMP(11), and it returns SQL_SUCCESS

 

But in the logs, it shows this;

[6608-1677.216]odbcapiw.c[SQLGetTypeInfoW]1015: Entering

[6608-1677.216]    info.c[PGAPI_GetTypeInfo]1115: entering...fSqlType=93

[6608-1677.216]statement.[SC_recycle_statement]812: entering self=0052D2E0

[6608-1677.216] qresult.c[QR_Constructor]173: entering

[6608-1677.216] qresult.c[QR_Constructor]242: leaving

[6608-1677.216]statement.[SC_set_Result]531: (0052D2E0, 00539F48)

[6608-1677.216] qresult.c[QR_Destructor]344: entering

[6608-1677.216]    bind.c[extend_column_bindings]718: entering ... self=0052D370, bindings_allocated=0, num_columns=19

[6608-1677.216]    bind.c[extend_column_bindings]762: leaving 004F8C30

[6608-1677.216] qresult.c[QR_set_num_fields]40: entering

[6608-1677.216] qresult.c[QR_set_num_fields]44: leaving

 

It appears the fSQLType changed from SQL_TIMESTAMP(11) to SQL_TYPE_TIMESTAMP(93)…? Could this be what is causing the issue?

 

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]



ウイルス フリー。 www.avg.com
Reply | Threaded
Open this post in threaded view
|

Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

michael.riksman
Hi Hiroshi,

I’ll try anything! Would be great to use PostgreSQL with an industrial software like Rockwell.

Thanks :)

Regards,

Michael Riksman

Sent from iPhone

On 23 Jul 2019, at 1:14 am, Inoue, Hiroshi <[hidden email]> wrote:

 Hi Michael,

Could you try the test driver if I provide a Windows test driver?

regards,
Hiroshi Inoue

On 2019/07/18 18:18, [hidden email]<mailto:[hidden email]> wrote:
Hi,


·         your ODBC driver version

psqlODBC is v11.01.000.



SQL_DRIVER_ODBC_VER reports “3.51”

[6608-0.002]    info.c[PGAPI_GetInfo]71: entering...fInfoType=77

[6608-0.002]    info.c[PGAPI_GetInfo]1032: p='03.51', len=0, value=0, cbMax=12



·         your PostgreSQL database version

v10.9 x86

Running on Windows 10 32-bit



·         any error messages you saw on the screen

The client application (Rockwell FactoryTalk), has a button which can automatically create the tables in an existing database.
It created a table successfully that DID NOT have a TIMESTAMP column. But I had to manually create two tables that had a TIMESTAMP column.
When I clicked ‘OK’ to accept the changes, I get this error;

<image001.png>

FactoryTalk works fine with Microsoft SQL ODBC.


·         the debug log (mylog_????.log) file (you will have to enable the mylog driver option)

Attached.






I ran the ODBC Test tool, and connected via ODBC version 2 (as this is what FactoryTalk appears to be using)
[2892-0.001]odbcapi30.[SQLSetEnvAttr]477: Entering att=200,2

I then ran a GetTypeInfo on SQL_TIMESTAMP(11), and it returns SQL_SUCCESS
<image002.png>

But in the logs, it shows this;
[6608-1677.216]odbcapiw.c[SQLGetTypeInfoW]1015: Entering
[6608-1677.216]    info.c[PGAPI_GetTypeInfo]1115: entering...fSqlType=93
[6608-1677.216]statement.[SC_recycle_statement]812: entering self=0052D2E0
[6608-1677.216] qresult.c[QR_Constructor]173: entering
[6608-1677.216] qresult.c[QR_Constructor]242: leaving
[6608-1677.216]statement.[SC_set_Result]531: (0052D2E0, 00539F48)
[6608-1677.216] qresult.c[QR_Destructor]344: entering
[6608-1677.216]    bind.c[extend_column_bindings]718: entering ... self=0052D370, bindings_allocated=0, num_columns=19
[6608-1677.216]    bind.c[extend_column_bindings]762: leaving 004F8C30
[6608-1677.216] qresult.c[QR_set_num_fields]40: entering
[6608-1677.216] qresult.c[QR_set_num_fields]44: leaving

It appears the fSQLType changed from SQL_TIMESTAMP(11) to SQL_TYPE_TIMESTAMP(93)…? Could this be what is causing the issue?



Regards,

Michael Riksman
Instrument and Control Specialist
Khalda Petroleum Co.
A KPC/Apache Corp. Joint Venture
Salam Base, Egypt
Mob: +20 122 0530603
Email: [hidden email]<mailto:[hidden email]>


[https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png]<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> ウイルス フリー。 www.avg.com<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Reply | Threaded
Open this post in threaded view
|

Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

Inoue, Hiroshi-2
Hi Michael,

Could you please try the test drivers 11.00.0100 on Windows at
https://winpg.jp/~inoue/psqlodbc/index.html
?

regards,
Hiroshi Inoue

On 2019/07/23 13:24, [hidden email] wrote:

> Hi Hiroshi,
>
> I’ll try anything! Would be great to use PostgreSQL with an industrial software like Rockwell.
>
> Thanks :)
>
> Regards,
>
> Michael Riksman
>
> Sent from iPhone
>
> On 23 Jul 2019, at 1:14 am, Inoue, Hiroshi <[hidden email]> wrote:
>
>  Hi Michael,
>
> Could you try the test driver if I provide a Windows test driver?
>
> regards,
> Hiroshi Inoue
>
> On 2019/07/18 18:18, [hidden email]<mailto:[hidden email]> wrote:
> Hi,
>
>
> ·         your ODBC driver version
>
> psqlODBC is v11.01.000.
>
>
>
> SQL_DRIVER_ODBC_VER reports “3.51”
>
> [6608-0.002]    info.c[PGAPI_GetInfo]71: entering...fInfoType=77
>
> [6608-0.002]    info.c[PGAPI_GetInfo]1032: p='03.51', len=0, value=0, cbMax=12
>
>
>
> ·         your PostgreSQL database version
>
> v10.9 x86
>
> Running on Windows 10 32-bit
>
>
>
> ·         any error messages you saw on the screen
>
> The client application (Rockwell FactoryTalk), has a button which can automatically create the tables in an existing database.
> It created a table successfully that DID NOT have a TIMESTAMP column. But I had to manually create two tables that had a TIMESTAMP column.
> When I clicked ‘OK’ to accept the changes, I get this error;
>
> <image001.png>
>
> FactoryTalk works fine with Microsoft SQL ODBC.
>
>
> ·         the debug log (mylog_????.log) file (you will have to enable the mylog driver option)
>
> Attached.
>
>
>
>
>
>
> I ran the ODBC Test tool, and connected via ODBC version 2 (as this is what FactoryTalk appears to be using)
> [2892-0.001]odbcapi30.[SQLSetEnvAttr]477: Entering att=200,2
>
> I then ran a GetTypeInfo on SQL_TIMESTAMP(11), and it returns SQL_SUCCESS
> <image002.png>
>
> But in the logs, it shows this;
> [6608-1677.216]odbcapiw.c[SQLGetTypeInfoW]1015: Entering
> [6608-1677.216]    info.c[PGAPI_GetTypeInfo]1115: entering...fSqlType=93
> [6608-1677.216]statement.[SC_recycle_statement]812: entering self=0052D2E0
> [6608-1677.216] qresult.c[QR_Constructor]173: entering
> [6608-1677.216] qresult.c[QR_Constructor]242: leaving
> [6608-1677.216]statement.[SC_set_Result]531: (0052D2E0, 00539F48)
> [6608-1677.216] qresult.c[QR_Destructor]344: entering
> [6608-1677.216]    bind.c[extend_column_bindings]718: entering ... self=0052D370, bindings_allocated=0, num_columns=19
> [6608-1677.216]    bind.c[extend_column_bindings]762: leaving 004F8C30
> [6608-1677.216] qresult.c[QR_set_num_fields]40: entering
> [6608-1677.216] qresult.c[QR_set_num_fields]44: leaving
>
> It appears the fSQLType changed from SQL_TIMESTAMP(11) to SQL_TYPE_TIMESTAMP(93)…? Could this be what is causing the issue?
>
>
>
> Regards,
>
> Michael Riksman
> Instrument and Control Specialist
> Khalda Petroleum Co.
> A KPC/Apache Corp. Joint Venture
> Salam Base, Egypt
> Mob: +20 122 0530603
> Email: [hidden email]<mailto:[hidden email]>



Reply | Threaded
Open this post in threaded view
|

RE: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

michael.riksman

Hi Hiroshi,

 

Firstly;

The changes you made meant that the ‘Create Tables’ is now working. Previously, it wouldn’t create ‘Float Table’ and ‘String Table’ – presumably because they were the two tables that had a TIMESTAMP column. I previously had to create them manually.

 

 

 

Secondly;

Now when I click 'OK', I get the following error instead. So it appears the TIMESTAMP issue is fixed (what was the problem!?), but now a new problem;

 

 

I have attached the mylog log.

 

Thanks for your time!

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

-----Original Message-----
From: Inoue, Hiroshi [mailto:[hidden email]]
Sent: Tuesday, 23 July 2019 7:07 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

 

Could you please try the test drivers 11.00.0100 on Windows at https://winpg.jp/~inoue/psqlodbc/index.html

?

 

regards,

Hiroshi Inoue

 

On 2019/07/23 13:24, [hidden email] wrote:

> Hi Hiroshi,

> 

> I’ll try anything! Would be great to use PostgreSQL with an industrial software like Rockwell.

> 

> Thanks :)

> 

> Regards,

> 

> Michael Riksman

> 

> Sent from iPhone

> 

> On 23 Jul 2019, at 1:14 am, Inoue, Hiroshi <[hidden email]> wrote:

> 

>  Hi Michael,

> 

> Could you try the test driver if I provide a Windows test driver?

> 

> regards,

> Hiroshi Inoue

> 

> On 2019/07/18 18:18, [hidden email]> wrote:

> Hi,

> 

> 

> ·         your ODBC driver version

> 

> psqlODBC is v11.01.000.

> 

> 

> 

> SQL_DRIVER_ODBC_VER reports “3.51”

> 

> [6608-0.002]    info.c[PGAPI_GetInfo]71: entering...fInfoType=77

> 

> [6608-0.002]    info.c[PGAPI_GetInfo]1032: p='03.51', len=0, value=0, cbMax=12

> 

> 

> 

> ·         your PostgreSQL database version

> 

> v10.9 x86

> 

> Running on Windows 10 32-bit

> 

> 

> 

> ·         any error messages you saw on the screen

> 

> The client application (Rockwell FactoryTalk), has a button which can automatically create the tables in an existing database.

> It created a table successfully that DID NOT have a TIMESTAMP column. But I had to manually create two tables that had a TIMESTAMP column.

> When I clicked ‘OK’ to accept the changes, I get this error;

> 

> <image001.png>

> 

> FactoryTalk works fine with Microsoft SQL ODBC.

> 

> 

> ·         the debug log (mylog_????.log) file (you will have to enable the mylog driver option)

> 

> Attached.

> 

> 

> 

> 

> 

> 

> I ran the ODBC Test tool, and connected via ODBC version 2 (as this is

> what FactoryTalk appears to be using)

> [2892-0.001]odbcapi30.[SQLSetEnvAttr]477: Entering att=200,2

> 

> I then ran a GetTypeInfo on SQL_TIMESTAMP(11), and it returns

> SQL_SUCCESS <image002.png>

> 

> But in the logs, it shows this;

> [6608-1677.216]odbcapiw.c[SQLGetTypeInfoW]1015: Entering

> [6608-1677.216]    info.c[PGAPI_GetTypeInfo]1115: entering...fSqlType=93

> [6608-1677.216]statement.[SC_recycle_statement]812: entering

> self=0052D2E0 [6608-1677.216] qresult.c[QR_Constructor]173: entering

> [6608-1677.216] qresult.c[QR_Constructor]242: leaving

> [6608-1677.216]statement.[SC_set_Result]531: (0052D2E0, 00539F48)

> [6608-1677.216] qresult.c[QR_Destructor]344: entering

> [6608-1677.216]    bind.c[extend_column_bindings]718: entering ... self=0052D370, bindings_allocated=0, num_columns=19

> [6608-1677.216]    bind.c[extend_column_bindings]762: leaving 004F8C30

> [6608-1677.216] qresult.c[QR_set_num_fields]40: entering

> [6608-1677.216] qresult.c[QR_set_num_fields]44: leaving

> 

> It appears the fSQLType changed from SQL_TIMESTAMP(11) to SQL_TYPE_TIMESTAMP(93)…? Could this be what is causing the issue?

> 

> 

> 

> Regards,

> 

> Michael Riksman

> Instrument and Control Specialist

> Khalda Petroleum Co.

> A KPC/Apache Corp. Joint Venture

> Salam Base, Egypt

> Mob: +20 122 0530603

> Email:

> [hidden email]>

 


mylog_DatalogEd.log (7M) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

Inoue, Hiroshi-2
Hi Michael,

Do you define 'tagname' column of 'tagtable' as varchar with no column size?
If so, please try to change the column as varchar(..) with a explicit column size less than 256 .

regards,
Hiroshi Inoue

On 2019/07/23 15:12, [hidden email] wrote:

Hi Hiroshi,

 

Firstly;

The changes you made meant that the ‘Create Tables’ is now working. Previously, it wouldn’t create ‘Float Table’ and ‘String Table’ – presumably because they were the two tables that had a TIMESTAMP column. I previously had to create them manually.

 

 

 

Secondly;

Now when I click 'OK', I get the following error instead. So it appears the TIMESTAMP issue is fixed (what was the problem!?), but now a new problem;

 

 

I have attached the mylog log.

 

Thanks for your time!

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

-----Original Message-----
From: Inoue, Hiroshi [[hidden email]]
Sent: Tuesday, 23 July 2019 7:07 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

 

Could you please try the test drivers 11.00.0100 on Windows at https://winpg.jp/~inoue/psqlodbc/index.html

?

 

regards,

Hiroshi Inoue

 

On 2019/07/23 13:24, [hidden email] wrote:

> Hi Hiroshi,

> 

> I’ll try anything! Would be great to use PostgreSQL with an industrial software like Rockwell.

> 

> Thanks :)

> 

> Regards,

> 

> Michael Riksman

> 

> Sent from iPhone

> 

> On 23 Jul 2019, at 1:14 am, Inoue, Hiroshi <[hidden email]> wrote:

> 

>  Hi Michael,

> 

> Could you try the test driver if I provide a Windows test driver?

> 

> regards,

> Hiroshi Inoue

> 

> On 2019/07/18 18:18, [hidden email]> wrote:

> Hi,

> 

> 

> ·         your ODBC driver version

> 

> psqlODBC is v11.01.000.

> 

> 

> 

> SQL_DRIVER_ODBC_VER reports “3.51”

> 

> [6608-0.002]    info.c[PGAPI_GetInfo]71: entering...fInfoType=77

> 

> [6608-0.002]    info.c[PGAPI_GetInfo]1032: p='03.51', len=0, value=0, cbMax=12

> 

> 

> 

> ·         your PostgreSQL database version

> 

> v10.9 x86

> 

> Running on Windows 10 32-bit

> 

> 

> 

> ·         any error messages you saw on the screen

> 

> The client application (Rockwell FactoryTalk), has a button which can automatically create the tables in an existing database.

> It created a table successfully that DID NOT have a TIMESTAMP column. But I had to manually create two tables that had a TIMESTAMP column.

> When I clicked ‘OK’ to accept the changes, I get this error;

> 

> <image001.png>

> 

> FactoryTalk works fine with Microsoft SQL ODBC.

> 

> 

> ·         the debug log (mylog_????.log) file (you will have to enable the mylog driver option)

> 

> Attached.

> 

> 

> 

> 

> 

> 

> I ran the ODBC Test tool, and connected via ODBC version 2 (as this is

> what FactoryTalk appears to be using)

> [2892-0.001]odbcapi30.[SQLSetEnvAttr]477: Entering att=200,2

> 

> I then ran a GetTypeInfo on SQL_TIMESTAMP(11), and it returns

> SQL_SUCCESS <image002.png>

> 

> But in the logs, it shows this;

> [6608-1677.216]odbcapiw.c[SQLGetTypeInfoW]1015: Entering

> [6608-1677.216]    info.c[PGAPI_GetTypeInfo]1115: entering...fSqlType=93

> [6608-1677.216]statement.[SC_recycle_statement]812: entering

> self=0052D2E0 [6608-1677.216] qresult.c[QR_Constructor]173: entering

> [6608-1677.216] qresult.c[QR_Constructor]242: leaving

> [6608-1677.216]statement.[SC_set_Result]531: (0052D2E0, 00539F48)

> [6608-1677.216] qresult.c[QR_Destructor]344: entering

> [6608-1677.216]    bind.c[extend_column_bindings]718: entering ... self=0052D370, bindings_allocated=0, num_columns=19

> [6608-1677.216]    bind.c[extend_column_bindings]762: leaving 004F8C30

> [6608-1677.216] qresult.c[QR_set_num_fields]40: entering

> [6608-1677.216] qresult.c[QR_set_num_fields]44: leaving

> 

> It appears the fSQLType changed from SQL_TIMESTAMP(11) to SQL_TYPE_TIMESTAMP(93)…? Could this be what is causing the issue?

> 

> 

> 

> Regards,

> 

> Michael Riksman

> Instrument and Control Specialist

> Khalda Petroleum Co.

> A KPC/Apache Corp. Joint Venture

> Salam Base, Egypt

> Mob: +20 122 0530603

> Email:

> [hidden email]>


ウイルス フリー。 www.avg.com
Reply | Threaded
Open this post in threaded view
|

RE: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

michael.riksman

Looks like it already is. This is what was created when the CREATE TABLES button was pressed in FactoryTalk;

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

From: Inoue, Hiroshi [mailto:[hidden email]]
Sent: Wednesday, 24 July 2019 8:18 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

Do you define 'tagname' column of 'tagtable' as varchar with no column size?
If so, please try to change the column as varchar(..) with a explicit column size less than 256 .

regards,
Hiroshi Inoue

On 2019/07/23 15:12, [hidden email] wrote:

Hi Hiroshi,

 

Firstly;

The changes you made meant that the ‘Create Tables’ is now working. Previously, it wouldn’t create ‘Float Table’ and ‘String Table’ – presumably because they were the two tables that had a TIMESTAMP column. I previously had to create them manually.

 

 

 

Secondly;

Now when I click 'OK', I get the following error instead. So it appears the TIMESTAMP issue is fixed (what was the problem!?), but now a new problem;

 

 

I have attached the mylog log.

 

Thanks for your time!

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

-----Original Message-----
From: Inoue, Hiroshi [[hidden email]]
Sent: Tuesday, 23 July 2019 7:07 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

 

Could you please try the test drivers 11.00.0100 on Windows at https://winpg.jp/~inoue/psqlodbc/index.html

?

 

regards,

Hiroshi Inoue

 

On 2019/07/23 13:24, [hidden email] wrote:

> Hi Hiroshi,

> I’ll try anything! Would be great to use PostgreSQL with an industrial software like Rockwell.

> Thanks :)

> Regards,

> Michael Riksman

> Sent from iPhone

> On 23 Jul 2019, at 1:14 am, Inoue, Hiroshi <[hidden email]> wrote:

>  Hi Michael,

> Could you try the test driver if I provide a Windows test driver?

> regards,

> Hiroshi Inoue

> On 2019/07/18 18:18, [hidden email]> wrote:

> Hi,

> ·         your ODBC driver version

> psqlODBC is v11.01.000.

> SQL_DRIVER_ODBC_VER reports “3.51”

> [6608-0.002]    info.c[PGAPI_GetInfo]71: entering...fInfoType=77

> [6608-0.002]    info.c[PGAPI_GetInfo]1032: p='03.51', len=0, value=0, cbMax=12

> ·         your PostgreSQL database version

> v10.9 x86

> Running on Windows 10 32-bit

> ·         any error messages you saw on the screen

> The client application (Rockwell FactoryTalk), has a button which can automatically create the tables in an existing database.

> It created a table successfully that DID NOT have a TIMESTAMP column. But I had to manually create two tables that had a TIMESTAMP column.

> When I clicked ‘OK’ to accept the changes, I get this error;

> <image001.png>

> FactoryTalk works fine with Microsoft SQL ODBC.

> ·         the debug log (mylog_????.log) file (you will have to enable the mylog driver option)

> Attached.

> I ran the ODBC Test tool, and connected via ODBC version 2 (as this is

> what FactoryTalk appears to be using)

> [2892-0.001]odbcapi30.[SQLSetEnvAttr]477: Entering att=200,2

> I then ran a GetTypeInfo on SQL_TIMESTAMP(11), and it returns

> SQL_SUCCESS <image002.png>

> But in the logs, it shows this;

> [6608-1677.216]odbcapiw.c[SQLGetTypeInfoW]1015: Entering

> [6608-1677.216]    info.c[PGAPI_GetTypeInfo]1115: entering...fSqlType=93

> [6608-1677.216]statement.[SC_recycle_statement]812: entering

> self=0052D2E0 [6608-1677.216] qresult.c[QR_Constructor]173: entering

> [6608-1677.216] qresult.c[QR_Constructor]242: leaving

> [6608-1677.216]statement.[SC_set_Result]531: (0052D2E0, 00539F48)

> [6608-1677.216] qresult.c[QR_Destructor]344: entering

> [6608-1677.216]    bind.c[extend_column_bindings]718: entering ... self=0052D370, bindings_allocated=0, num_columns=19

> [6608-1677.216]    bind.c[extend_column_bindings]762: leaving 004F8C30

> [6608-1677.216] qresult.c[QR_set_num_fields]40: entering

> [6608-1677.216] qresult.c[QR_set_num_fields]44: leaving

> It appears the fSQLType changed from SQL_TIMESTAMP(11) to SQL_TYPE_TIMESTAMP(93)…? Could this be what is causing the issue?

> Regards,

> Michael Riksman

> Instrument and Control Specialist

> Khalda Petroleum Co.

> A KPC/Apache Corp. Joint Venture

> Salam Base, Egypt

> Mob: +20 122 0530603

> Email:

> [hidden email]>

 

ウイルス フリー。 www.avg.com

 

Reply | Threaded
Open this post in threaded view
|

Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

Inoue, Hiroshi-2
Hi Michael,

Aren't you setting the *Max Varchar* option as 254?
Please try to set the option >= the size of the column 'tagname'.

regards,
Hiroshi Inoue
 
On 2019/07/24 15:31, [hidden email] wrote:

Looks like it already is. This is what was created when the CREATE TABLES button was pressed in FactoryTalk;

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

From: Inoue, Hiroshi [[hidden email]]
Sent: Wednesday, 24 July 2019 8:18 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

Do you define 'tagname' column of 'tagtable' as varchar with no column size?
If so, please try to change the column as varchar(..) with a explicit column size less than 256 .

regards,
Hiroshi Inoue

On 2019/07/23 15:12, [hidden email] wrote:

Hi Hiroshi,

 

Firstly;

The changes you made meant that the ‘Create Tables’ is now working. Previously, it wouldn’t create ‘Float Table’ and ‘String Table’ – presumably because they were the two tables that had a TIMESTAMP column. I previously had to create them manually.

 

 

 

Secondly;

Now when I click 'OK', I get the following error instead. So it appears the TIMESTAMP issue is fixed (what was the problem!?), but now a new problem;

 

 

I have attached the mylog log.

 

Thanks for your time!

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

-----Original Message-----
From: Inoue, Hiroshi [[hidden email]]
Sent: Tuesday, 23 July 2019 7:07 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

 

Could you please try the test drivers 11.00.0100 on Windows at https://winpg.jp/~inoue/psqlodbc/index.html

?

 

regards,

Hiroshi Inoue

 

On 2019/07/23 13:24, [hidden email] wrote:

> Hi Hiroshi,

> I’ll try anything! Would be great to use PostgreSQL with an industrial software like Rockwell.

> Thanks :)

> Regards,

> Michael Riksman

> Sent from iPhone

> On 23 Jul 2019, at 1:14 am, Inoue, Hiroshi <[hidden email]> wrote:

>  Hi Michael,

> Could you try the test driver if I provide a Windows test driver?

> regards,

> Hiroshi Inoue

> On 2019/07/18 18:18, [hidden email]> wrote:

> Hi,

> ·         your ODBC driver version

> psqlODBC is v11.01.000.

> SQL_DRIVER_ODBC_VER reports “3.51”

> [6608-0.002]    info.c[PGAPI_GetInfo]71: entering...fInfoType=77

> [6608-0.002]    info.c[PGAPI_GetInfo]1032: p='03.51', len=0, value=0, cbMax=12

> ·         your PostgreSQL database version

> v10.9 x86

> Running on Windows 10 32-bit

> ·         any error messages you saw on the screen

> The client application (Rockwell FactoryTalk), has a button which can automatically create the tables in an existing database.

> It created a table successfully that DID NOT have a TIMESTAMP column. But I had to manually create two tables that had a TIMESTAMP column.

> When I clicked ‘OK’ to accept the changes, I get this error;

> <image001.png>

> FactoryTalk works fine with Microsoft SQL ODBC.

> ·         the debug log (mylog_????.log) file (you will have to enable the mylog driver option)

> Attached.

> I ran the ODBC Test tool, and connected via ODBC version 2 (as this is

> what FactoryTalk appears to be using)

> [2892-0.001]odbcapi30.[SQLSetEnvAttr]477: Entering att=200,2

> I then ran a GetTypeInfo on SQL_TIMESTAMP(11), and it returns

> SQL_SUCCESS <image002.png>

> But in the logs, it shows this;

> [6608-1677.216]odbcapiw.c[SQLGetTypeInfoW]1015: Entering

> [6608-1677.216]    info.c[PGAPI_GetTypeInfo]1115: entering...fSqlType=93

> [6608-1677.216]statement.[SC_recycle_statement]812: entering

> self=0052D2E0 [6608-1677.216] qresult.c[QR_Constructor]173: entering

> [6608-1677.216] qresult.c[QR_Constructor]242: leaving

> [6608-1677.216]statement.[SC_set_Result]531: (0052D2E0, 00539F48)

> [6608-1677.216] qresult.c[QR_Destructor]344: entering

> [6608-1677.216]    bind.c[extend_column_bindings]718: entering ... self=0052D370, bindings_allocated=0, num_columns=19

> [6608-1677.216]    bind.c[extend_column_bindings]762: leaving 004F8C30

> [6608-1677.216] qresult.c[QR_set_num_fields]40: entering

> [6608-1677.216] qresult.c[QR_set_num_fields]44: leaving

> It appears the fSQLType changed from SQL_TIMESTAMP(11) to SQL_TYPE_TIMESTAMP(93)…? Could this be what is causing the issue?

> Regards,

> Michael Riksman

> Instrument and Control Specialist

> Khalda Petroleum Co.

> A KPC/Apache Corp. Joint Venture

> Salam Base, Egypt

> Mob: +20 122 0530603

> Email:

> [hidden email]>


ウイルス フリー。 www.avg.com
Reply | Threaded
Open this post in threaded view
|

RE: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

michael.riksman

Hi Hiroshi,

 

Spot on,

 

 

 

I set this to 255, and the error went away. However, when I tried to start the DataLog, I receive the following error;

 

 

Strange – considering that it must have connected in order for it to create the tables…?

 

Attached logs. They include opening up the configuration, clicking OK, and then trying to start the datalog.

 

Thanks again.

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

From: Inoue, Hiroshi [mailto:[hidden email]]
Sent: Wednesday, 24 July 2019 9:49 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

Aren't you setting the *Max Varchar* option as 254?
Please try to set the option >= the size of the column 'tagname'.

regards,
Hiroshi Inoue
 

On 2019/07/24 15:31, [hidden email] wrote:

Looks like it already is. This is what was created when the CREATE TABLES button was pressed in FactoryTalk;

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

From: Inoue, Hiroshi [[hidden email]]
Sent: Wednesday, 24 July 2019 8:18 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

Do you define 'tagname' column of 'tagtable' as varchar with no column size?
If so, please try to change the column as varchar(..) with a explicit column size less than 256 .

regards,
Hiroshi Inoue

On 2019/07/23 15:12, [hidden email] wrote:

Hi Hiroshi,

 

Firstly;

The changes you made meant that the ‘Create Tables’ is now working. Previously, it wouldn’t create ‘Float Table’ and ‘String Table’ – presumably because they were the two tables that had a TIMESTAMP column. I previously had to create them manually.

 

 

 

Secondly;

Now when I click 'OK', I get the following error instead. So it appears the TIMESTAMP issue is fixed (what was the problem!?), but now a new problem;

 

 

I have attached the mylog log.

 

Thanks for your time!

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

-----Original Message-----
From: Inoue, Hiroshi [[hidden email]]
Sent: Tuesday, 23 July 2019 7:07 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

 

Could you please try the test drivers 11.00.0100 on Windows at https://winpg.jp/~inoue/psqlodbc/index.html

?

 

regards,

Hiroshi Inoue

 

On 2019/07/23 13:24, [hidden email] wrote:

> Hi Hiroshi,

> I’ll try anything! Would be great to use PostgreSQL with an industrial software like Rockwell.

> Thanks :)

> Regards,

> Michael Riksman

> Sent from iPhone

> On 23 Jul 2019, at 1:14 am, Inoue, Hiroshi <[hidden email]> wrote:

>  Hi Michael,

> Could you try the test driver if I provide a Windows test driver?

> regards,

> Hiroshi Inoue

> On 2019/07/18 18:18, [hidden email]> wrote:

> Hi,

> ·         your ODBC driver version

> psqlODBC is v11.01.000.

> SQL_DRIVER_ODBC_VER reports “3.51”

> [6608-0.002]    info.c[PGAPI_GetInfo]71: entering...fInfoType=77

> [6608-0.002]    info.c[PGAPI_GetInfo]1032: p='03.51', len=0, value=0, cbMax=12

> ·         your PostgreSQL database version

> v10.9 x86

> Running on Windows 10 32-bit

> ·         any error messages you saw on the screen

> The client application (Rockwell FactoryTalk), has a button which can automatically create the tables in an existing database.

> It created a table successfully that DID NOT have a TIMESTAMP column. But I had to manually create two tables that had a TIMESTAMP column.

> When I clicked ‘OK’ to accept the changes, I get this error;

> <image001.png>

> FactoryTalk works fine with Microsoft SQL ODBC.

> ·         the debug log (mylog_????.log) file (you will have to enable the mylog driver option)

> Attached.

> I ran the ODBC Test tool, and connected via ODBC version 2 (as this is

> what FactoryTalk appears to be using)

> [2892-0.001]odbcapi30.[SQLSetEnvAttr]477: Entering att=200,2

> I then ran a GetTypeInfo on SQL_TIMESTAMP(11), and it returns

> SQL_SUCCESS <image002.png>

> But in the logs, it shows this;

> [6608-1677.216]odbcapiw.c[SQLGetTypeInfoW]1015: Entering

> [6608-1677.216]    info.c[PGAPI_GetTypeInfo]1115: entering...fSqlType=93

> [6608-1677.216]statement.[SC_recycle_statement]812: entering

> self=0052D2E0 [6608-1677.216] qresult.c[QR_Constructor]173: entering

> [6608-1677.216] qresult.c[QR_Constructor]242: leaving

> [6608-1677.216]statement.[SC_set_Result]531: (0052D2E0, 00539F48)

> [6608-1677.216] qresult.c[QR_Destructor]344: entering

> [6608-1677.216]    bind.c[extend_column_bindings]718: entering ... self=0052D370, bindings_allocated=0, num_columns=19

> [6608-1677.216]    bind.c[extend_column_bindings]762: leaving 004F8C30

> [6608-1677.216] qresult.c[QR_set_num_fields]40: entering

> [6608-1677.216] qresult.c[QR_set_num_fields]44: leaving

> It appears the fSQLType changed from SQL_TIMESTAMP(11) to SQL_TYPE_TIMESTAMP(93)…? Could this be what is causing the issue?

> Regards,

> Michael Riksman

> Instrument and Control Specialist

> Khalda Petroleum Co.

> A KPC/Apache Corp. Joint Venture

> Salam Base, Egypt

> Mob: +20 122 0530603

> Email:

> [hidden email]>

 

ウイルス フリー。 www.avg.com

 


mylog_DatalogEd.log (7M) Download Attachment
psqlodbc_DatalogEd.log (74K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

Inoue, Hiroshi-2
Hi Michael,

Could you send me directly the log of ODBC trace which can be turned on using ODBC Data Source Administrator?
Please note that ODBC trace is very heavy.

regards,
Hiroshi Inoue

On 2019/07/25 0:01, [hidden email] wrote:

Hi Hiroshi,

 

Spot on,

 

 

 

I set this to 255, and the error went away. However, when I tried to start the DataLog, I receive the following error;

 

 

Strange – considering that it must have connected in order for it to create the tables…?

 

Attached logs. They include opening up the configuration, clicking OK, and then trying to start the datalog.

 

Thanks again.

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

From: Inoue, Hiroshi [[hidden email]]
Sent: Wednesday, 24 July 2019 9:49 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

Aren't you setting the *Max Varchar* option as 254?
Please try to set the option >= the size of the column 'tagname'.

regards,
Hiroshi Inoue
 

On 2019/07/24 15:31, [hidden email] wrote:

Looks like it already is. This is what was created when the CREATE TABLES button was pressed in FactoryTalk;

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

From: Inoue, Hiroshi [[hidden email]]
Sent: Wednesday, 24 July 2019 8:18 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

Do you define 'tagname' column of 'tagtable' as varchar with no column size?
If so, please try to change the column as varchar(..) with a explicit column size less than 256 .

regards,
Hiroshi Inoue

On 2019/07/23 15:12, [hidden email] wrote:

Hi Hiroshi,

 

Firstly;

The changes you made meant that the ‘Create Tables’ is now working. Previously, it wouldn’t create ‘Float Table’ and ‘String Table’ – presumably because they were the two tables that had a TIMESTAMP column. I previously had to create them manually.

 

 

 

Secondly;

Now when I click 'OK', I get the following error instead. So it appears the TIMESTAMP issue is fixed (what was the problem!?), but now a new problem;

 

 

I have attached the mylog log.

 

Thanks for your time!

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

-----Original Message-----
From: Inoue, Hiroshi [[hidden email]]
Sent: Tuesday, 23 July 2019 7:07 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

 

Could you please try the test drivers 11.00.0100 on Windows at https://winpg.jp/~inoue/psqlodbc/index.html

?

 

regards,

Hiroshi Inoue

 

On 2019/07/23 13:24, [hidden email] wrote:

> Hi Hiroshi,

> I’ll try anything! Would be great to use PostgreSQL with an industrial software like Rockwell.

> Thanks :)

> Regards,

> Michael Riksman

> Sent from iPhone

> On 23 Jul 2019, at 1:14 am, Inoue, Hiroshi <[hidden email]> wrote:

>  Hi Michael,

> Could you try the test driver if I provide a Windows test driver?

> regards,

> Hiroshi Inoue

> On 2019/07/18 18:18, [hidden email]> wrote:

> Hi,

> ·         your ODBC driver version

> psqlODBC is v11.01.000.

> SQL_DRIVER_ODBC_VER reports “3.51”

> [6608-0.002]    info.c[PGAPI_GetInfo]71: entering...fInfoType=77

> [6608-0.002]    info.c[PGAPI_GetInfo]1032: p='03.51', len=0, value=0, cbMax=12

> ·         your PostgreSQL database version

> v10.9 x86

> Running on Windows 10 32-bit

> ·         any error messages you saw on the screen

> The client application (Rockwell FactoryTalk), has a button which can automatically create the tables in an existing database.

> It created a table successfully that DID NOT have a TIMESTAMP column. But I had to manually create two tables that had a TIMESTAMP column.

> When I clicked ‘OK’ to accept the changes, I get this error;

> <image001.png>

> FactoryTalk works fine with Microsoft SQL ODBC.

> ·         the debug log (mylog_????.log) file (you will have to enable the mylog driver option)

> Attached.

> I ran the ODBC Test tool, and connected via ODBC version 2 (as this is

> what FactoryTalk appears to be using)

> [2892-0.001]odbcapi30.[SQLSetEnvAttr]477: Entering att=200,2

> I then ran a GetTypeInfo on SQL_TIMESTAMP(11), and it returns

> SQL_SUCCESS <image002.png>

> But in the logs, it shows this;

> [6608-1677.216]odbcapiw.c[SQLGetTypeInfoW]1015: Entering

> [6608-1677.216]    info.c[PGAPI_GetTypeInfo]1115: entering...fSqlType=93

> [6608-1677.216]statement.[SC_recycle_statement]812: entering

> self=0052D2E0 [6608-1677.216] qresult.c[QR_Constructor]173: entering

> [6608-1677.216] qresult.c[QR_Constructor]242: leaving

> [6608-1677.216]statement.[SC_set_Result]531: (0052D2E0, 00539F48)

> [6608-1677.216] qresult.c[QR_Destructor]344: entering

> [6608-1677.216]    bind.c[extend_column_bindings]718: entering ... self=0052D370, bindings_allocated=0, num_columns=19

> [6608-1677.216]    bind.c[extend_column_bindings]762: leaving 004F8C30

> [6608-1677.216] qresult.c[QR_set_num_fields]40: entering

> [6608-1677.216] qresult.c[QR_set_num_fields]44: leaving

> It appears the fSQLType changed from SQL_TIMESTAMP(11) to SQL_TYPE_TIMESTAMP(93)…? Could this be what is causing the issue?

> Regards,

> Michael Riksman

> Instrument and Control Specialist

> Khalda Petroleum Co.

> A KPC/Apache Corp. Joint Venture

> Salam Base, Egypt

> Mob: +20 122 0530603

> Email:

> [hidden email]>



ウイルス フリー。 www.avg.com
Reply | Threaded
Open this post in threaded view
|

RE: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

michael.riksman

Hey,

 

I turned it on;

 

But the only time something is written to the trace is when I open up the configuration window, and click OK;

 

postgreSQL

51 ‘Tags in Model’

SQLpostgres.LOG

Microsoft SQL

17 ‘Tags in Model’

SQLmsql.LOG

 

 

But when I right-click and start the DataLog;

 

 

Nothing is added to the SQL.LOG file/ODBC Tracing.

 

 

Data is successfully being logged to Microsoft SQL at this point – but still no additional data in the ODBC Tracing.

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

From: Inoue, Hiroshi [mailto:[hidden email]]
Sent: Thursday, 25 July 2019 1:00 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

Could you send me directly the log of ODBC trace which can be turned on using ODBC Data Source Administrator?
Please note that ODBC trace is very heavy.

regards,
Hiroshi Inoue

On 2019/07/25 0:01, [hidden email] wrote:

Hi Hiroshi,

 

Spot on,

 

 

 

I set this to 255, and the error went away. However, when I tried to start the DataLog, I receive the following error;

 

 

Strange – considering that it must have connected in order for it to create the tables…?

 

Attached logs. They include opening up the configuration, clicking OK, and then trying to start the datalog.

 

Thanks again.

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

From: Inoue, Hiroshi [[hidden email]]
Sent: Wednesday, 24 July 2019 9:49 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

Aren't you setting the *Max Varchar* option as 254?
Please try to set the option >= the size of the column 'tagname'.

regards,
Hiroshi Inoue
 

On 2019/07/24 15:31, [hidden email] wrote:

Looks like it already is. This is what was created when the CREATE TABLES button was pressed in FactoryTalk;

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

From: Inoue, Hiroshi [[hidden email]]
Sent: Wednesday, 24 July 2019 8:18 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

Do you define 'tagname' column of 'tagtable' as varchar with no column size?
If so, please try to change the column as varchar(..) with a explicit column size less than 256 .

regards,
Hiroshi Inoue

On 2019/07/23 15:12, [hidden email] wrote:

Hi Hiroshi,

 

Firstly;

The changes you made meant that the ‘Create Tables’ is now working. Previously, it wouldn’t create ‘Float Table’ and ‘String Table’ – presumably because they were the two tables that had a TIMESTAMP column. I previously had to create them manually.

 

 

 

Secondly;

Now when I click 'OK', I get the following error instead. So it appears the TIMESTAMP issue is fixed (what was the problem!?), but now a new problem;

 

 

I have attached the mylog log.

 

Thanks for your time!

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

-----Original Message-----
From: Inoue, Hiroshi [[hidden email]]
Sent: Tuesday, 23 July 2019 7:07 AM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi Michael,

 

Could you please try the test drivers 11.00.0100 on Windows at https://winpg.jp/~inoue/psqlodbc/index.html

?

 

regards,

Hiroshi Inoue

 

On 2019/07/23 13:24, [hidden email] wrote:

> Hi Hiroshi,

> I’ll try anything! Would be great to use PostgreSQL with an industrial software like Rockwell.

> Thanks :)

> Regards,

> Michael Riksman

> Sent from iPhone

> On 23 Jul 2019, at 1:14 am, Inoue, Hiroshi <[hidden email]> wrote:

>  Hi Michael,

> Could you try the test driver if I provide a Windows test driver?

> regards,

> Hiroshi Inoue

> On 2019/07/18 18:18, [hidden email]> wrote:

> Hi,

> ·         your ODBC driver version

> psqlODBC is v11.01.000.

> SQL_DRIVER_ODBC_VER reports “3.51”

> [6608-0.002]    info.c[PGAPI_GetInfo]71: entering...fInfoType=77

> [6608-0.002]    info.c[PGAPI_GetInfo]1032: p='03.51', len=0, value=0, cbMax=12

> ·         your PostgreSQL database version

> v10.9 x86

> Running on Windows 10 32-bit

> ·         any error messages you saw on the screen

> The client application (Rockwell FactoryTalk), has a button which can automatically create the tables in an existing database.

> It created a table successfully that DID NOT have a TIMESTAMP column. But I had to manually create two tables that had a TIMESTAMP column.

> When I clicked ‘OK’ to accept the changes, I get this error;

> <image001.png>

> FactoryTalk works fine with Microsoft SQL ODBC.

> ·         the debug log (mylog_????.log) file (you will have to enable the mylog driver option)

> Attached.

> I ran the ODBC Test tool, and connected via ODBC version 2 (as this is

> what FactoryTalk appears to be using)

> [2892-0.001]odbcapi30.[SQLSetEnvAttr]477: Entering att=200,2

> I then ran a GetTypeInfo on SQL_TIMESTAMP(11), and it returns

> SQL_SUCCESS <image002.png>

> But in the logs, it shows this;

> [6608-1677.216]odbcapiw.c[SQLGetTypeInfoW]1015: Entering

> [6608-1677.216]    info.c[PGAPI_GetTypeInfo]1115: entering...fSqlType=93

> [6608-1677.216]statement.[SC_recycle_statement]812: entering

> self=0052D2E0 [6608-1677.216] qresult.c[QR_Constructor]173: entering

> [6608-1677.216] qresult.c[QR_Constructor]242: leaving

> [6608-1677.216]statement.[SC_set_Result]531: (0052D2E0, 00539F48)

> [6608-1677.216] qresult.c[QR_Destructor]344: entering

> [6608-1677.216]    bind.c[extend_column_bindings]718: entering ... self=0052D370, bindings_allocated=0, num_columns=19

> [6608-1677.216]    bind.c[extend_column_bindings]762: leaving 004F8C30

> [6608-1677.216] qresult.c[QR_set_num_fields]40: entering

> [6608-1677.216] qresult.c[QR_set_num_fields]44: leaving

> It appears the fSQLType changed from SQL_TIMESTAMP(11) to SQL_TYPE_TIMESTAMP(93)…? Could this be what is causing the issue?

> Regards,

> Michael Riksman

> Instrument and Control Specialist

> Khalda Petroleum Co.

> A KPC/Apache Corp. Joint Venture

> Salam Base, Egypt

> Mob: +20 122 0530603

> Email:

> [hidden email]>

 

 

ウイルス フリー。 www.avg.com

 


SQLmsql.LOG (357K) Download Attachment
SQLpostgres.LOG (790K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

Inoue, Hiroshi-2
Hi,

On 2019/07/25 15:27, [hidden email] wrote:

Hey,

 

I turned it on;

 

But the only time something is written to the trace is when I open up the configuration window, and click OK;

 

postgreSQL

51 ‘Tags in Model’

SQLpostgres.LOG

Microsoft SQL

17 ‘Tags in Model’

SQLmsql.LOG

 

 

But when I right-click and start the DataLog;

 

 

Nothing is added to the SQL.LOG file/ODBC Tracing.

 

 

Data is successfully being logged to Microsoft SQL at this point – but still no additional data in the ODBC Tracing.


So there seems no ODBC API call.
Would you like to see the page www.plctalk.net/qanda/archive/index.php/t-109368.html ?

regards,
Hiroshi Inoue

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]


ウイルス フリー。 www.avg.com
Reply | Threaded
Open this post in threaded view
|

RE: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

michael.riksman

Hey,

 

I’m not sure what happened, but after restarting the PC, it started working. I am sure I restarted after installing the driver, but perhaps I didn’t…?

 

But we have data!

 

THANK YOU SO MUCH!

 

I am curious – what was the original error with TIMESTAMP? What lines of code did you change?

 

Thanks.

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

From: Inoue, Hiroshi [mailto:[hidden email]]
Sent: Friday, 26 July 2019 2:29 PM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi,

On 2019/07/25 15:27, [hidden email] wrote:

Hey,

 

I turned it on;

 

But the only time something is written to the trace is when I open up the configuration window, and click OK;

 

postgreSQL

51 ‘Tags in Model’

SQLpostgres.LOG

Microsoft SQL

17 ‘Tags in Model’

SQLmsql.LOG

 

 

But when I right-click and start the DataLog;

 

 

Nothing is added to the SQL.LOG file/ODBC Tracing.

 

 

Data is successfully being logged to Microsoft SQL at this point – but still no additional data in the ODBC Tracing.


So there seems no ODBC API call.
Would you like to see the page www.plctalk.net/qanda/archive/index.php/t-109368.html ?

regards,
Hiroshi Inoue


 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

ウイルス フリー。 www.avg.com

 

Reply | Threaded
Open this post in threaded view
|

Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

Inoue, Hiroshi-2
Hi Michael,

On 2019/07/28 16:45, [hidden email] wrote:

Hey,

 

I’m not sure what happened, but after restarting the PC, it started working. I am sure I restarted after installing the driver, but perhaps I didn’t…?

 

But we have data!

 

THANK YOU SO MUCH!

 

I am curious – what was the original error with TIMESTAMP? What lines of code did you change?


I would commit the following change.

diff --git a/info.c b/info.c
index 452dabf..c2dc0aa 100644
--- a/info.c
+++ b/info.c
@@ -1155,8 +1155,8 @@ PGAPI_GetTypeInfo(HSTMT hstmt,
        {
                EnvironmentClass        *env = CC_get_env(conn);

-               /* Filter unsupported data types */
-               if (EN_is_odbc2(env))
+               /* Filter unsupported data types when fSqlType = SQL_ALL_TYPES */
+               if (SQL_ALL_TYPES == fSqlType && EN_is_odbc2(env))
                {
                        switch (sqlType)
                        {

Since commit 778571, SQLGetTypeInfo() filters SQL_TYPE_DATE, SQL_TYPE_TIME and SQL_TYPE_TIMESTAMP for ODBC 2.x applications. However it doesn't seem appropriate to filter them for individual SQLGetTypeInfo(.., SQL_DATE/TIME/TIMESTAMP) because  Microsoft ODBC driver manager calls SQLGetTypeInfo(.., SQL_TYPE_DATE/TIME/TIMESTAMP) of ODBC 3.x drivers when ODBC 2.x applications call SQLGetTypeInfo(.., SQL_DATE/TIME/TIMESTAMP).

  ** The behavior of unixODBC  is different.

regards,
Hiroshi Inoue

 

Thanks.

 

 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]

 

From: Inoue, Hiroshi [[hidden email]]
Sent: Friday, 26 July 2019 2:29 PM
To: Michael Riksman (Salam - Gas)
Cc: [hidden email]
Subject: Re: Rockwell FactoryTalk Says 'SQL_TIMESTAMP data type is not supported'

 

Hi,

On 2019/07/25 15:27, [hidden email] wrote:

Hey,

 

I turned it on;

 

But the only time something is written to the trace is when I open up the configuration window, and click OK;

 

postgreSQL

51 ‘Tags in Model’

SQLpostgres.LOG

Microsoft SQL

17 ‘Tags in Model’

SQLmsql.LOG

 

 

But when I right-click and start the DataLog;

 

 

Nothing is added to the SQL.LOG file/ODBC Tracing.

 

 

Data is successfully being logged to Microsoft SQL at this point – but still no additional data in the ODBC Tracing.


So there seems no ODBC API call.
Would you like to see the page www.plctalk.net/qanda/archive/index.php/t-109368.html ?

regards,
Hiroshi Inoue


 

Regards,

 

Michael Riksman

Instrument and Control Specialist

Khalda Petroleum Co.

A KPC/Apache Corp. Joint Venture

Salam Base, Egypt

Mob: +20 122 0530603

Email: [hidden email]


ウイルス フリー。 www.avg.com