Unable to register materialized view with database

[Joey_NL]

Hi there,

We have two materialized views in an Oracle 19c database that we want to register with an enterprise geodb. 
Logging in as data owner, checked and there are no locks.

Trying to accomplish this from ArcGIS Pro 3.2 selecting an existing field (OBJECT_ID, NUMBER(38,0)) results in an error that I can't update the view. Understandable, I don't want to update the view, I just want to register it with the geodb as given in this help doc.

I have trawled through the forums and stackexchange and keep finding advice to use sde commandline tools to issue a command similar to the one below, but these tools aren't available anymore. I can't see any way in the GUI or in the ArcPy snippet to push the same -C USER switch.

sdetable -o register -t DINOLOKET.GDW_LKS_GWO_SA -c OBJECT_ID -C USER

I feel like I'm missing something here but am a bit stuck where to go further, so would very much appreciate your advice.

[MarceloMarques · Accepted solution]

Hello @Joey_NL  

sde commandline tools are deprecated. Those were in use a long time ago with ArcSDE  9.x and 10.1.

Please, open a ticket with esri tech support to investigate the issue further. It might be necessary to collect an ArcSDE Intercept and an Oracle Trace to determine the cause of the issue.

[Joey_NL]

Thanks @MarceloMarques  - was hoping there was a quicker fix, but good to know. Will contact our colleagues at ESRI NL. Have a good weekend.

[VinceAngelo]

Why do you need the MV registered? Is it going to participate in geodatabase behavior?  If you just want to render from it, making a Query Layer of the unregistered table would likely suffice.

Conflicts that could be created between the ArcSDE metadata and geodatabase metadata was the reason the ancient command-line utilities were deprecated long, long, ago. Even if you could make a 10.2.2 sdetable function, you could only harm the integrity of a modern geodatabase.

Registration of views is a relatively new feature. If you haven't installed a service pack to 3.2, you probably ought to, at least 3.2.1, but the 3.2.4 terminal release is likely to be better.

- V

[Joey_NL]

Hey @VinceAngelo ,

Sorry for my delay. We wanted to register a materialised view so that we could set up relates. Upon further investigating this isn't possible as it's an older oracle geodatabase that won't be upgraded so we will handle this another way.

Thanks for the hint, we have already started the rollout of the patch to 3.2.4 it just needs to get through our IT approvals process.

Thanks for the advice!