• Oracle Non-Spatial Reader/Writer
  • Quick Facts
  • Reader Parameters
  • Writer Parameters
  • Feature Types
    • Reader Feature Type Parameters
    • Writer Feature Type Parameters
    • User Attributes
    • Feature Representation
  • Troubleshooting

Oracle Non-Spatial Troubleshooting

The following suggestions can often help detect and resolve common Oracle database connection problems.

• Ensure you can connect to the database with the service, username, and password using SQL*Plus.
• Consider if you are using a tns alias (tnsnames.ora) or direct connection. The TNS Alias configuration is frequently overlooked when moving a workspace to a new system, and it's often a problem when a workspace containing a new Oracle Reader or Writer is published to an FME Server for the first time. Check the tnsnames.ora file for an entry.
• If using tnsnames.ora with the Oracle Instant Clients, ensure TNS_ADMIN environment variable is set and pointing to the folder containing the tnsnames.ora file.
• If you have had older versions of the Oracle Full client software installed, make sure that your PATH variable has the current version’s Oracle folder first, before any other Oracle software, including the WebDB package.
• Ensure that the bit version of the software being used matches the Oracle Client bit version. For example, FME 32-bit requires the Oracle 32-bit Client in the path.
• If you're using Database Connections in a workspace, ensure the connection has been published to the new system.
• The following environment variables should be defined: