Timeline for Using arcpy CreateDatabaseConnectionString to access feature class in Oracle database - why doesn't this work consistently?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22 at 15:35 | history | edited | Vince | CC BY-SA 4.0 |
formatting
|
| Aug 22 at 15:34 | comment | added | Vince | If you have a solution, enter it as an Answer. OPs should not need to write any comments, because they have the Question to curate. | |
| Aug 22 at 14:20 | comment | added | Matt Leonard | The solution I've arrived at is a different approach: I set up the script to run as a custom script tool within ArcGIS Pro, and I made the workspace a parameter for the tool, so the user can enter a saved .sde database connection as input in the tool interface. When they do so, they will be prompted to enter user name and password for that database if they haven't already. Then the tool runs. Within the script that the tool is referencing, feature classes from within the workspace will be accessed as input for arcpy tools. It seems to work. | |
| Aug 22 at 14:18 | comment | added | Matt Leonard | The database has multiple feature classes with the same name but different schema "prefixes". The FC names look like "DSGN.ENG_TRACK" and "ENG.ENG_TRACK" - when the tool is run, it accesses the wrong ENG_TRACK. I tried entering "ENG.ENG_TRACK" as the instance parameter and tried entering "ENG" as the schema parameter. Still, we cannot figure out how to make this tool access the correct feature class. | |
| Aug 20 at 14:18 | history | edited | Matt Leonard | CC BY-SA 4.0 |
Added requested clarification about differences between two tested input feature classes.
|
| Aug 19 at 19:14 | comment | added | Vince | Please Edit the Question in response to requests for clarification | |
| Aug 19 at 19:00 | comment | added | Matt Leonard | I compared properties of the two feature classes. The only differences I can see are: The FC that did not work is a Line FC, while the one that worked is a Point FC (not sure why this would matter); and the one that did not work has the properties "COGO Enabled: No" and "Split Model: Update/Insert" while the one that worked does not have these properties. | |
| Aug 16 at 19:21 | comment | added | Vince | Are all the feature classes registered with the geodatabase? If you use native SDO_Geometry and Query Layers, sometimes the FC2FC won't work. More information about the differences between working and non-working tables may be necessary. Geometry storage, field types, feature dataset participation,... | |
| Aug 16 at 15:49 | history | asked | Matt Leonard | CC BY-SA 4.0 |