Testing, again with SQL*Plus, the executable crashed big time with a General Protection Fault. Step 2: Correcting the characterset of the database SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT=(SHA1) SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER=(SHA1) u01/app/oracle/product/****/dbhome_1/network/admin/sqlnet.ora On this database database server secure SQL*Net is enabled by We are not using an Autonomous database, so we still have a “server” we can connect to in OCI. ORA-12660: Encryption or crypto-checksumming parameters incompatibleĪ standard OCI Database installation enables secure SQL*Net. This is the road I traveled: Step 1: Disable SQL*Netįirst I tried making a connection with SQL*Plus from the same Oracle-home as Forms to the new database:
#Oracle 6i software
We could rebuild/redesign the old application to Oracle Apex, but that would be an entire project by itself.īut first we investigated if it was possible to connect this software from 1995 to the 21th century. We are talking Oracle Forms 6i client/server on Windows, 100% generated with Oracle Designer. But one of these databases had an Oracle Forms C/S frontend. My customer started to move all of his Oracle Databases to the Oracle Cloud Infrastructure (OCI).
But the world of enterprise IT isn’t like that. Everybody wants to work with the latest tools, the latest feautures.