nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

GeoDatabase Connection Properties Fails

rbae

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...

Najděte více příspěvků označených jako

Accepted answers

KoryKramer

It is fixed in Pro 2.3

Esri Support Home

All comments

KoryKramer

It is fixed in Pro 2.3

Esri Support Home

mvolz47

I am testing Pro 2.3 Beta (Early Adopter program) and this connection error does not occur so it looks like this bug has been fixed, but we'll see in final release of Pro 2.3.

KoryKramer

Michael, I apologize that the issue has not been fixed yet. It looks like the first issue, at the time, was not reproducible. The issue that is open with the development team is BUG-000096686. As you've stated, because the resolution of this bug is important for you to migrate to ArcGIS Pro, you might consider escalating the bug: https://community.esri.com/groups/technical-support/blog/2016/03/28/how-to-escalate-a-defect/#more-8840

mvolz47

Kory:

There are 2 ESRI bugs associated with this issue and they have different resolutions:

The bugs both represent the same issue but the original bug says a fix is Not in Current Product Plan, but the newer bug for the same issue says a fix is In Product Plan. Can you explain why the same bug has different resolutions?

The resolution of this bug is important to my org (The workaround does not meet our security requirements) for our eventual migration to Pro, so would you know if there is an update of when this bug will be fixed?

Latest patch 2.2.2 has not addressed this issue.

KoryKramer

Looks like April 18th, 2018

mvolz47

I was doing my testing for this issue only using an Oracle Instant Client as that is the architecture my org is planning to go with moving forward with Pro. Does anyone know if this bug would also exist in Pro if I try to connect to an Oracle database with the standard Oracle client?

Kory: In addition, this bug now says In Product Plan. Would you know when this bug changed from New to In Product Plan?

mvolz47

The issue still occurs in Pro 2.2 that was just released. Kory would you have any idea when development will get to fixing this bug as it would be important when Pro is used to manage an SDE database?

Currently we would need ArcMap/ArcCatalog still going for quite some time due to this bug as well as other big ticket items not available yet in Pro - Publishing from Pro to Server (there is a light at the end of this tunnel and it is sometime in 2019 - TY Thomas Colson), Parcel Fabric, and ArcHydro tools for flood modeling.

mvolz47

This issue is still occurring in Pro Beta 2.2.

KoryKramer

There isn't a hard and fast rule on when we see the status change. I agree that in calendar terms it of course isn't new, and on this particular issue I can say that it is being actively investigated. There are a few different statuses that a development team can assign to a bug and while it is being looked at and considered, the team might not be ready to commit to "In Product Plan" but they also might not want to mark it as "Not In Current Product Plan"... again, I'll check in with that team to see if they can provide an honest assessment on the status.

mvolz47

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)?

KoryKramer

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.]

mvolz47

Kory:

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

rbae

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

mvolz47

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?

KoryKramer

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."

AbhijeetKulkarni

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?

AbhijeetKulkarni

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

XanderBakker

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?

AbhijeetKulkarni

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‌

Asrujit_SenGupta

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?

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.