Skip to the main content.
Downloads Thriftly Login
Downloads Thriftly Login
Group 762

Migrate and run DataFlex applications with Oracle, MS SQL Server, PostgreSQL, MySQL &  MariaDB.

flex2Crystal

Stuck in Crystal XI?  Upgrade and use the latest versions of Crystal Reports with DataFlex applications. 

BTR2SQL

Seamlessly convert from Btrieve transactional database to PostgreSQL, Oracle, and MS SQL Server.

thriftly-1

Quickly build multi-protocol web services with the same API. Supports JSON-RPC, REST, SOAP,  Thrift, and gRPC.

 Group 671-1

 

Why Mertech?

2 min read

Connecting Btrieve to an Oracle Database

Question: What do I input for the "server name" in the login dialog?

Answer: Using the "easy connect" naming method

(Information origin: https://docs.oracle.com/cd/B28359_01/server.111/b28301/)


The easy connect naming method provides TCP/IP connectivity to databases without the need to first configure Oracle Net Services. The connect identifier has the following format:

"[//]host[:port]/service_name"

where:

  • host
    is the name or IP address of the Oracle database host computer.
  • port (optional)
    is the TCP port number on which the Oracle Net listener listens for connections.
    If port is excluded, the standard port number 1521 is assumed.
  • service_name
    is one of the services defined by the database. If there are no service names specifically defined, then you can use the name of the service that the database creates by default. This service name defaults to the global database name, which consists of the database name (DB_NAME parameter) and domain name (DB_DOMAIN parameter).

For example, to connect to the database service orcl.us.example.com
on the host db.us.example.com, use the following for the "server name" in the BTR2SQL login dialog:

db.us.example.com/orcl.us.example.com


"Global Database Name"

The full name of the database which uniquely identifies it from any other database. The global database name is of the form "database_name.database_domain," for example, sales.us.acme.com.

The database name portion, sales, is a simple name you wish to call your database. The database domain portion, us.acme.com, specifies the database domain in which the database is located, making the global database name unique. When possible, Oracle Corporation recommends that your database domain mirror the network domain.


The global database name is the default service name of the database, as specified by the SERVICE_NAMES parameter in the initialization parameter file.


Local Naming

The local naming method stores connect descriptors, identified by their net service names, in a configuration file on the client named tnsnames.ora. This file is located in the Oracle_home/network/admin
directory. When you create a database using Oracle Database Configuration Assistant (DBCA), local naming is configured automatically. You must then use the Net Configuration Assistant to create connect descriptors and their corresponding net service names.


See http://download.oracle.com/docs/cd/B19306_01/network.102/b14213/tnsnames.htm for more information.


An Example using the Instant Client

Local Naming is the preferred method with BTR2SQL.


The Instant Client does not include a tnsnames.ora file (it doesn't even include the sub-directories). So, in the ORACLE_HOME location (for instance c:oracleinstantclient), create the folder "network" and under that create "admin". Now, edit c:oracleinstantclientnetworkadmintnsnames.ora. In here you might have something like:

ORCLTEST =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = myserver)(PORT = 1521))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = orcltestdb)

)

)


The easiest way to populate this information is to copy it from the tnsnames.ora file on the server (for instance, c:oracleproduct11.1.0db_1networkadmintnsnames.ora)


Once this file is in place on the client (and the oracle client dlls are in the system PATH), you would use "ORCLTEST" for the "Server Name" in the BTR2SQL login dialog.

 

Migrate Btrieve to SQL in a seamless way, try BTR2SQL!

 

Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Introduction Many independent software vendors (ISV) and corporate users still rely on applications that use a category of database collective called...

Read More
Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

COBOL applications are the foundation of numerous essential business functions, especially within the banking, insurance, and government sectors....

Read More
Application Modernization 101: Ultimate Guide to Digital Transformation

Application Modernization 101: Ultimate Guide to Digital Transformation

Imagine breaking free from the constraints of old, monolithic systems and embracing the agility and innovation of cloud-based solutions.

Read More