Select to view content in your preferred language

un tables prefix in sde geodatabase

441
2
Jump to solution
03-06-2024 02:05 PM
PierreloupDucroix
Frequent Contributor

Hello,

I recently had to drop my test UN database in order to recreate it with a newly configured asset package.

Everything went smooth, but, when trying to restart my UN services, I had this error :

[DBMS table not found] [UN_806_DirtyAreas].

And indeed I noticed that now, all the UN system tables are prefixed by un_6_ instead of un_806_...

Is it a known behavior ? How can I restart or replace my services with the correct name ? I have to delete and republish them ?

--> Postegresql 14.6, UN 3.1, AGE 11.1

CEO of MAGIS
0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

The UN system tables do reference an internal identifier that isn't preserved when you create a new database or copy/paste items between databases.

If you open the map that you used to publish your original service and fix any broken layers, you can use that to overwrite your original service. If you don't have your original map (uh oh!) you can either recreate it (taking care to preserve your layer ids) or you can browse the file system of your ArcGIS Server machine to download a copy of the map that was used to publish the service.

View solution in original post

0 Kudos
2 Replies
RobertKrisher
Esri Regular Contributor

The UN system tables do reference an internal identifier that isn't preserved when you create a new database or copy/paste items between databases.

If you open the map that you used to publish your original service and fix any broken layers, you can use that to overwrite your original service. If you don't have your original map (uh oh!) you can either recreate it (taking care to preserve your layer ids) or you can browse the file system of your ArcGIS Server machine to download a copy of the map that was used to publish the service.

0 Kudos
PierreloupDucroix
Frequent Contributor

Thanks, Robert,

this is exactly what I did, unfortunately, I stopped the UN feature service before dropping the database, and could not restart it after (because of the error mentioned).

Then, as Pro is unable to overwrite a service that is stopped, I had to delete and recreate it using the original map, changing the itemID, and to fix broken layers in my user's APRX after.

Regards

CEO of MAGIS
0 Kudos