Oracle Autonomous Transaction Processing (ATP) database 19c is not working with KEPServerEX

[Vishalaksha]

Hello,

Our company's custom MES application uses an Oracle database on the backend and connects with the shopfloor PLCs using the KEPServerEX OPC server. We plan to migrate the MES application (Full-stack - database + Middleware + UI) and the OPC server machine to Oracle Cloud. Below are the existing configurations:

Oracle database 12c Rel 2

OPC Server

• Windows Server 2019
• KEPServer EX 6.9.584.0
• Oracle Instant Client 12c
• Oracle ODBC Driver 12c

As part of the migration, we want to upgrade the Oracle database to 19c and switch to the Oracle Autonomous Transaction Processing (ATP) database. We have set up the ODBC connection using the Oracle 12c ODBC driver and instant Client 19c (we also tried the 12c client). KEPServerEX can connect to the ATP database; it can read but not write. 

Desired Future Configurations

Oracle ATP database 19c

OPC Server

• Windows Server 2022
• KEPServer EX 6.17.240.0 (The older version 6.9.584.0 cannot even read from the Oracle database)
• Oracle Instant Client 12c (we also tried the 19c client)
• Oracle ODBC Driver 12c (Tried with 19c driver too)

Does anyone have experience using Oracle's ATP database to connect to the KEPServer EX, or any suggestions on how to solve this problem?

I would appreciate any insights.

Thanks

Vishal

[MKhatri]

Hello,

I would like to bring to your attention an important matter regarding system compatibility and the upgrade of Kepware from version 5 to version 6. I have attached an article with detailed information on this topic for your reference.

Furthermore, I would like to inform you that older versions of Kepserverex prior to version 16 may encounter issues with Oracle 19c. Therefore, I highly recommend that if you are considering upgrading to version 19c, you should also upgrade to the latest version of Kepware to ensure smooth operation.

For more information, please refer to the following links:

1. https://www.ptc.com/en/support/article/CS348235

2. https://www.ptc.com/en/support/article/CS281944

3. https://www.ptc.com/en/support/article/CS326229

Should you have any questions or require further clarification, please do not hesitate to reach out to me. Thank you for your attention to this matter.

Regards,

Mohit

[Vishalaksha]

Thanks, Mohit.

I have already gone through these articles. The issue is different, so here is the additional information. Oracle database 19c has two main database types: 1. a fully autonomous transaction processing (ATP) database and 2. a regular database (Enterprise, Standard, etc.). We have tried using the regular database 19c, and it works fine for us, but not the autonomous transaction processing database. KEPServerEX can write to the regular Oracle Enterprise 19c database but not the Oracle ATP database 19c.

The ATP database is fully functional, and the database user has full permission to write. We have also tested using the latest KEPServerEX version 6.17.240.0.

Thanks

Vishal

[MKhatri · Accepted solution]

Hello,

I would like to advise you to check the following link:

https://docs.oracle.com/en-us/iaas/autonomous-database-serverless/doc/connect-download-wallet.html#GUID-BE884A1B-034D-4CD6-9B71-83A4CCFDE9FB

It is essential to review the connection string entered in the Data Source Name (DSN) that was created. Additionally, there may be some settings that require adjustment. If we still faces issue, Please open up support ticket from mykepware.com to check into in details.

Regards,

Mohit

[Vishalaksha]

We found the solution. The details are below. I hope this will be useful for those who are looking forward to using the latest releases of the Oracle database and establishing a connection to Kepware. In addition to the below findings, we had some configuration issues with Oracle Wallet.

Oracle Database Type	DB Version	Oracle Client version	ODBC version	SQL Developer -DB	Kepware version	Results
ATP	19c	12.2 Instant Client	12.2.0.0	Connected	6.16	ODBC driver connected; Kepware was able to read data, but writing to the database has failed
DB System(DBaaS)	19c	12.2 Instant Client	12.2.0.0	Connected	6.16	Data R/W operations were successful
DB System(DBaaS)	23ai	12.2 Instant Client	12.2.0.0	Connected	6.16	Data R/W operations were successful
DB System(DBaaS)	19c	19.25 Instant Client/19c Full Client	19.0.0.0	Connected	6.16	ODBC driver connected to DB, but data communication failed with Kepware
DB System(DBaaS)	23ai	19.25 Instant Client/19c Full Client	19.0.0.0	Connected	6.16	ODBC driver connected to DB, but data communication failed with Kepware
ATP	19c	12.2 Instant Client	12.2.0.0	Connected	6.16	ODBC driver connected to DB, but data communication failed with Kepware
ATP	19c	19.25 Instant Client	19.0.0.0	Connected	6.16	ODBC driver connected to DB, but data communication failed with Kepware
ATP	19c	21.15 Instant Client	21.0.0.0	Connected	6.16	ODBC driver connected to DB, but data communication failed with Kepware
ATP	19c	19.24 Instant Client	19.0.0.0	Connected	6.17	Data R/W operations were successful
ATP	19c	21.15 Instant Client	21.0.0.0	Connected	6.17	Data R/W operations were successful
ATP	23ai	21.15 Instant Client	21.0.0.0	Connected	6.17	Data R/W operations were successful