Use the Database Connection Properties dialog box to create or customize a database connection.
Direct mode does not require an Oracle Client to be installed on your workstation. dbForge Schema Compare for Oracle talks to the Oracle server directly, no third party libraries are required.
You can connect to a multi-threaded server using Direct mode. The server must be configured to use a specific port and TTC protocol. This can help you avoid firewall conflicts.
Direct mode advantages:
Direct mode restrictions:
You can return to a connection via an TNS at any time if restrictions above become critical for you.
Connection via the TNS
The TNS connection type is an appropriate option in any of the following circumstances:
A TNS connection uses an alias entry from a tnsnames.ora file. dbForge Schema Compare for Oracle uses only one tnsnames.ora file. You may have more than one on your local machine or want to use the tnsnames.ora file on a remote machine, so note that dbForge Schema Compare for Oracle looks sequentially for the tnsnames.ora file in the following locations:
You need to create the TNS_ADMIN environment variable in the case when the tnsnames.ora file exists but dbForge Schema Compare for Oracle doesn’t use it.
dbForge Schema Compare for Oracle uses connection via an TNS by default.
Connection via TNS Using OS Authentication
With OS authentication, Oracle Database uses a database user’s OS login credentials to authenticate that user. The user doesn’t provide a username or password to access the database, and Oracle Database doesn’t store and manage the account password. Local OS authentication can be used when the client and the database server are on the same machine. Remote OS authentication is possible but is not considered secure.