Issues connecting to SDE Geodatabase (Oracle)

Considerations

The following 3 example errors were encountered when using the TNSNames alias and setting the Instance to sde:oracle11g:bpesri in the ArcGIS Database Connection Manager.

Here is the entry from the tnsnames.ora file:

bpesri =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = bp-esri)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = bpesri)
    )
  )

The first "bpesri" is known as the tns alias name. HOST indicates the hostname, and the SERVICE_NAME represents the SID or service name of the database instance. Each example shows what the error message might look like when returned by the FME Flow Job log (which will likely be similar to FME Form). Typically, the tnsnames. An ora file is placed on each individual system, and these can get out of sync between a local desktop system and the FME Flow system, where you publish workspaces.

Example 1 - Bad Alias or missing Alias in tnsnames.ora file.

Could not open the Enterprise Geodatabase. The error number from ArcObjects is: '-2147216072'. The error message from ArcObjects is: {Underlying DBMS error[ORA-12154: TNS: could not resolve the connect identifier specified No extended error.]}

Please ensure the connection parameters are correct (server=`bpesri', instance=`sde:oracle11g:bpesri', user=`support', password=`***', database=`', version=`SDE.DEFAULT')

Example 2 - Bad service name with good alias and hostname in tnsnames.ora file

Could not open the Enterprise Geodatabase. The error number from ArcObjects is: '-2147155559'. The error message from ArcObjects is: {Failure to access the DBMS server}

Please ensure the connection parameters are correct (server=`bpesri', instance=`sde:oracle11g:bpesri', user=`support', password=`***', database=`', version=`SDE.DEFAULT')

Example 3 - bad hostname with correct alias and correct service name

Could not open the Enterprise Geodatabase. The error number from ArcObjects is: '-2147216072'. The error message from ArcObjects is: {Underlying DBMS error[ORA-12545: Connect failed because target host or object does not exist No extended error.]}

Please ensure the connection parameters are correct (server=`bpesri', instance=`sde:oracle11g:bpesri', user=`support', password=`***', database=`', version=`SDE.DEFAULT')

Why This Happens

The cause for these error messages is normally related to a bad tnsnames.ora entry related to the hostname, sid, or alias name.

Another possible cause is the syntax in the tnsnames file.ora file. For example, a syntax issue in an earlier tnsname entry causes later tnsnames to be ignored in the tnsnames.ora file. Move the entry you are working with to the top of the file, and you may find it starts working... This would indicate an issue with another TNS entry in the file.

How to Resolve It

The solution to all of these errors is to confirm that the TNSNames.ora file in use on the FME Flow system matches or contains the same entries as the one on your local FME Form system, where the workspace runs properly.

Search