|
Hi, when i register OEM Edition, the command dbisql -nogui -c "uid=dba;pwd=sql" myscript.sql will make response "Authentication violation, how can i fix this error. Otherwise, when i used this command with dbisqlc utility,the exception did not occur? |
|
DBISQL is self-authenticating. If a DBISQL connection is reporting a -98 error, it is either
Please note that you cannot execute the database_authentication for a database that is running on an OEM edition. You either have to create the database on a non-OEM edition or provide an appropriately configured authenticate.sql that is used by create database (refer to the documentation for details). We are aware of some embedded SQL usage that may not enforce authentication. This will likely explain why DBISQLC is not affected. Thanks for answering! I tried placing the command below, but the same exception happened, which means that, when I execute the command below, perform the same response "Authentication violation". SET TEMPORARY OPTION CONNECTION_AUTHENTICATION='Company=xxx;Application=xxx;Signature=xxx'
(19 Aug '19, 23:08)
tampv2
2
That confirms (or at least strongly suggests) that the database_authentication option has not been set in the database. You cannot set that option on an OEM engine. The authenticate.sql file can be used to supply the database_authentication option when creating a database on an OEM engine.
(20 Aug '19, 07:56)
Chris Keating
|
