topic Re: GeoDatabase Connection Properties Fails in ArcGIS Pro Questions

GeoDatabase Connection Properties Fails

rbae — Tue, 06 Feb 2018 20:31:28 GMT

Using ArcGIS Pro 2.1.1 with Oracle 12.1.0.2, I get the following error when I try to look at the GeoDatabase Connection Properties:

The connection works fine and I can do just about anything else with the GDB. The TNS as not an issue so it appears that it is an invalid error message...

Re: GeoDatabase Connection Properties Fails

Asrujit_SenGupta — Wed, 07 Feb 2018 03:44:21 GMT

Have you tried the below:

Closing and reopening ArcGIS Pro and then trying again?
Create a new connection to that Oracle db and try again?

Re: GeoDatabase Connection Properties Fails

AbhijeetKulkarni — Fri, 02 Mar 2018 05:17:26 GMT

I too have same problem with Pro 2.1.0.

Asrujit SenGupta‌, both suggested workarounds doesn't work.

Ryan Bae‌ - Alternate way I found was to create database connection using python window. This connection shows up 'GeoDatabase Connection Properties'.

import arcpy
arcpy.CreateDatabaseConnection_management("Path to your .sde file",
"connection_name.sde",
"DB",
"instance",
"DATABASE_AUTH",
"username",
"PWD",
"SAVE_USERNAME",
'TRANSACTIONAL');

Dan Patterson‌,Xander Bakker‌,Kory Kramer‌ Can you kindly help?

arcgispro 2.1‌

utility network data model‌

Re: GeoDatabase Connection Properties Fails

XanderBakker — Fri, 02 Mar 2018 11:20:44 GMT

Ryan Bae , it might be good to contact Esri Support and work through the problem with them.

abhijeet You mention that the connection shows up, but do you actually have access to the database through that connection?

Re: GeoDatabase Connection Properties Fails

AbhijeetKulkarni — Fri, 09 Mar 2018 09:05:13 GMT

Yes Xander, I do have access to the database with that connection. I used same username/pwd via python and it worked.

Re: GeoDatabase Connection Properties Fails

AbhijeetKulkarni — Tue, 17 Apr 2018 13:04:18 GMT

KKramer-esristaff‌, I could reproduce this issue consistently. Not sure if this is reported as bug already so wondering if you could help about it?

Re: GeoDatabase Connection Properties Fails

KoryKramer — Tue, 17 Apr 2018 13:15:11 GMT

Hi Abhijeet. We do have a bug logged that I think covers what is being described here. In that bug, the following workaround is listed:

"Use an Oracle Easy Connect string while connecting to the Oracle geodatabase."

Re: GeoDatabase Connection Properties Fails

MichaelVolz — Tue, 17 Apr 2018 13:38:33 GMT

I am using Pro 2.1.2 and I can connect to the Oracle database using the Instant Client with no problems, but when I try to access the Geodatabase Connection Properties I get the same issue.

Is the Oracle Easy Connect string different from using the Oracle Instant Client? Can you please elaborate more on the Oracle Easy Connect string?

Re: GeoDatabase Connection Properties Fails

KoryKramer — Tue, 17 Apr 2018 13:51:10 GMT

Working with enterprise database connections is not my forte so I actually can't elaborate with any authority. From a quick Google search I see that an Easy Connect string can be specified in Instant Client mode, so it doesn't seem like it is one or the other... but again, at this point I'm just Googling:

Instant Client FAQ

Re: GeoDatabase Connection Properties Fails

rbae — Tue, 17 Apr 2018 16:40:19 GMT

Kory,

Thank you for your help - the Oracle Easy Connect string did work for me. Since there is a bug logged for the TNSNames issue, I will mark this as resolved.

-Ryan

Re: GeoDatabase Connection Properties Fails

MichaelVolz — Tue, 17 Apr 2018 16:54:03 GMT

So I did some testing where I created a database connection but did not save the credentials (I unchecked Save user name and password) and I then clicked on Geodatabase Connection Properties. When I did this I saw the Connection Properties dialog box appear where it has truncated the first 2 letters of the instance which would cause initial ORA-12154 error as it cannot resolve the database instance because ArcPro changed the name by truncating the first 2 letters.

Re: GeoDatabase Connection Properties Fails

rbae — Tue, 17 Apr 2018 17:01:14 GMT

Michael,

I think you nailed it. I was able to reproduce this as well. I then added a TNS entry that duplicated the original, minus the first two characters of the TNS Name, and it worked.

Re: GeoDatabase Connection Properties Fails

MichaelVolz — Tue, 17 Apr 2018 17:13:17 GMT

This thread is answered if your org allows the use of Oracle Easy Connect which my org does not for both security and maintenance reasons during enterprise upgrades. Hopefully, the diagnosis I have provided will help ESRI to fix the root cause of this issue for newer versions of Pro.

Re: GeoDatabase Connection Properties Fails

KoryKramer — Tue, 17 Apr 2018 21:08:53 GMT

Thanks for the comments here rbae‌ and mvolz47‌ I just wanted to pass along that the truncation behavior noted here has been included in the notes of the defect that the development team is assessing.

Re: GeoDatabase Connection Properties Fails

MichaelVolz — Tue, 17 Apr 2018 21:55:32 GMT

Thanks for passing that info along to development Kory.

Re: GeoDatabase Connection Properties Fails

KoryKramer — Tue, 17 Apr 2018 21:57:07 GMT

You're welcome!

Re: GeoDatabase Connection Properties Fails

Asrujit_SenGupta — Wed, 18 Apr 2018 04:29:47 GMT

By "Oracle Full\Administrator Client" and "Oracle Instant Client", you refer to the type of Oracle Database Client software. -- Oracle Database Client Installation Types

The clients use a connect identifier in the connect string to connect to a service. Easy Connect method enables clients to connect to a database server without any configuration. EZCONNECT - Oracle FAQ

Connect to Oracle from ArcGIS—Help | ArcGIS Desktop

Either type the Oracle TNS name in the Instance text box, or provide one of the following Oracle Easy Connect strings:
The name of the Oracle server/Oracle service name or ID
For example, if Oracle is installed on myserver and myosvc is the Oracle service name, type the following:
myserver/myosvc
The name of the Oracle server:Oracle port number/Oracle service name or ID
In this example, Oracle is installed on myserver, is listening on port 60000, and myoservice is the Oracle service name.
myserver:60000/myoservice
The URL of the Oracle server
The URL for the same instance shown in the last example would be the following:
//myserver:60000/myoservice
The name of the Oracle server (You can use this if the Oracle listener on the server is configured to point to a default instance.)
The IP address of the Oracle server/Oracle service name or ID
For example, if the address of the server is 10:10:10:10, and the Oracle service name is orasvc, type 10:10:10:10/orasvc.
For IPV6 addresses, place brackets around the address, for example, [4000:ab5:0:0:f666:d191:77f5:e2bd]/orasvc.
The IP address of the Oracle server:Oracle port number/Oracle service name or ID
In this example, the IP address is 10:20:30:40, port is 59999, and Oracle service is myomy1: 10:20:30:40:59999/myomy1.
An IPV6 address for the same port and service would look like the following: [6543:ef4:0:1:f587:l249:12f9:a3cd]:59999/myomy110:20:30:40:59999/myomy1.
Be sure your Oracle instance is configured to allow Easy Connect. If you have the full Oracle client installed but want to use Easy Connect syntax to connect, be sure the sqlnet.ora file on the client is configured to allow the use of Easy Connect and the Oracle server is configured to allow Easy Connect syntax. Also note that if your Oracle instance is not listening on the default Oracle port number, you must use connection syntax that includes the port number.

Re: GeoDatabase Connection Properties Fails

MichaelVolz — Wed, 18 Apr 2018 13:41:07 GMT

Kory:

Would you be able to share the bug # that you say was logged for the tnsnames issue?

Re: GeoDatabase Connection Properties Fails

KoryKramer — Wed, 18 Apr 2018 14:09:51 GMT

This is the bug I was referring to that is open and under investigation:

[BUG-000096686: Unable to access 'Geodatabase Connection Properties' when connection is created using the Transparent Network Substrate (TNS) name for an Oracle geodatabase.]

Re: GeoDatabase Connection Properties Fails

MichaelVolz — Wed, 18 Apr 2018 14:15:10 GMT

Kory:

I created a tech support case and this is the bug that the analyst associated my case with. My question on this bug is that it's status is New but it was created almost 2 years ago (5/23/2016), which does not seem new at all. As such when does a Bug move out of New status (e.g. time period)?