Error while trying to Register With Geodatabase

TrentSchweitzer

I just updated from ArcPro 3.0.0 to 3.2.0 now the addin I created throws an error when trying to register a new table as a geodatabase. 

ERROR 999999: Something unexpected caused the tool to fail.
Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug,
and refer to the error help for potential solutions or workarounds.
This DB instance's release does not support this operation. [This DB instance's release does not support this operation.]
Failed to execute (RegisterWithGeodatabase). Failed at Wednesday, October 9, 2024 08:42:23 (Elapsed Time: 6.37 seconds)

From my code if a table is not registered as a geodatabase, I open it as a standalone table

using (Geodatabase geodatabase = new Geodatabase(connectionProperties))
                    using (Table worktable = geodatabase.OpenDataset<Table>(queryTableName))
                    {
                        var tableParams = new StandaloneTableCreationParams(worktable)
                        {
                            Name = queryTableName,
                        };

                        // creates the standalone table.
                        StandaloneTableFactory.Instance.CreateStandaloneTable(tableParams, MapView.Active.Map);
                    }

 

Then run this block of code to register it.

var uri = standaloneTable.URI;

            List<object> arguments = new List<object>
            {
                // URI of the standalone table to be projected on the map
                standaloneTable.URI,

                // OBJECTID Value column
                "UNIQ_ID",
            };

            // Takes the standalonetable URI and makes and registers with the geodatabase
            var results = await Geoprocessing.ExecuteToolAsync($"RegisterWithGeodatabase_management", Geoprocessing.MakeValueArray(arguments.ToArray()));

 

 Running ArcGis Pro 3.2.0

Oracle.ManagedDataAccess.Core 3.21.110

TrentSchweitzer

My worktables are using Date and Oracle Number (38) columns, so this at least sounds like the problem. I had been using Number(38) due to ArcMap Originally requiring that data type so I am assuming  now 'Long' is the preferred data type?

I was able to go though and add the registry key/value, this unfortunately did not resolve the issue.
I am currently running 3.2.0 though so is it possibly that I would need to update to 3.2.4 to try and resolve this?