Making an Oracle Connection with Schematodoc Starts with Creating a Local Net Service Name

SchemaToDoc – Making an Oracle Connection

Making an Oracle connection with SchemaToDoc starts with creating a Local Net Service Name on the machine that’s running SchemaToDoc. The name you give to the Local Net Service Name (see page 5 of this document) is the name that SchemaToDoc needs for the connection.

The Service Name you enter will be the Global Name you gave to your Oracle server when you created it. (“OracleDB.schematodoc” is an example; your Global Name will be different.)

The Host name is the name of the machine hosting the Oracle server. (“CPQ65402758618” is an example; your Host name will be different.)

This is the most important part of the process as far as SchemaToDoc is concerned; this is the name you will use on the SchemaToDoc connection screen. You can use any name you want for the Net Service Name.

You can view a list of existing Net Service Names by selecting the test option for the Oracle Net Configuration Assistant.

Then view the drop down.

The next thing you need for a connection is the name of a database schema. Here’s a list of schemas for my database. I will try to connect to the HR schema.

Now we are ready to use SchemaToDoc to connect to our Oracle database. We will use the Net Service Name (“MyServiceName”) and a schema name (“HR”) to do the log on. The schema name is case sensitive; it must be in ALL CAPS.

If the connection is successful, the SchemaToDoc Document Builder screen appears.

Other Requirements for Running SchemaToDoc Against an Oracle Database

Requirement: You must have the Oracle Client tools installed on the SchemaToDoc machine. That client must include the Oracle Windows Interfaces component and its subcomponent - Oracle Provider for OLE DB.

Is the Requirement Installed: Run the Oracle Universal Installer and check for Installed Products. You should be able to open the tree (Oracle Homes/OraHome/Oracle Database/Oracle Windows Interfaces) to see the Oracle Provider for OLE DB component. If it’s not present, follow the steps on the next page to install it.

Installing the Oracle Provider for OLE DB Component: Start by running the Oracle Universal Installer to install the Oracle Client on the SchemaToDoc machine.

Install the Administrator version of the Client or select the Custom installation.

If you select the Custom installation, make sure you select the Oracle Windows Interfaces component for installation. Even if it’s already installed, select the component in order to force Oracle to reinstall it with all of its options.

After you run the installation re-check your installed product list to make sure the necessary component was installed.

1