Select to view content in your preferred language

Error apply asset package in enterprise database

693
5
Jump to solution
02-07-2024 07:06 AM
NadiaAlami
Occasional Contributor

Hi and good day everyone...
We try to migrate our utility network file geodatabase to enterprise  database, 
when try to apply asset package, we encounter error like below.
what should we do?

NadiaAlami_0-1707318124481.png

It is correct our step to migrate from file geodatabase to enterprise database for our Utility network db.
first, we create enterprise geodatabase then we create enterprise geodatabase user .
After that we run stage asset package then we apply asset package. 
We manage to do the first three steps but encounter error when to apply the asset package processing.
0 Kudos
3 Solutions

Accepted Solutions
RobertKrisher
Esri Regular Contributor

Your steps are correct, but there appears to be a problem with the isolation and system subnetwork fields. In those subnetwork name fields must be non-nullable, and they are in the default model. If you made any changes (or dropped and re-added these fields) then that may have set them to be nullable.

The easiest way to correct the issue in the asset package is to:

  1. create a copy of the table
  2. delete all the rows out of the copy
  3. set the subnetwork name fields in the copy to be non-nullable (this can only be done on an empty table)
  4. append the rows from the original table into the copy
  5. delete the original table, and rename the copy table to match the original table

View solution in original post

JoaquinMadrid1
Regular Contributor

Thank you, Robert, for identifying the issue and providing the detailed solution.

Also, Nadia, and as a side note, before applying an AP to an E-GDB we found very helpful to first run the Asset Package to Geodatabase GPTool (from Esri's Utility Network Package Tools). It would not resolve your problems, but it would encounter them and allow you to fix them in the AP before you invested a lot of effort working directly on an E-GDB.

View solution in original post

MikeMillerGIS
Esri Frequent Contributor

The quicker fix is to just delete these fields in the Asset Package.  When the tools apply the Asset Package, the call to Set Subnetwork Def with create the field with the correct settings.

View solution in original post

0 Kudos
5 Replies
RobertKrisher
Esri Regular Contributor

Your steps are correct, but there appears to be a problem with the isolation and system subnetwork fields. In those subnetwork name fields must be non-nullable, and they are in the default model. If you made any changes (or dropped and re-added these fields) then that may have set them to be nullable.

The easiest way to correct the issue in the asset package is to:

  1. create a copy of the table
  2. delete all the rows out of the copy
  3. set the subnetwork name fields in the copy to be non-nullable (this can only be done on an empty table)
  4. append the rows from the original table into the copy
  5. delete the original table, and rename the copy table to match the original table
JoaquinMadrid1
Regular Contributor

Thank you, Robert, for identifying the issue and providing the detailed solution.

Also, Nadia, and as a side note, before applying an AP to an E-GDB we found very helpful to first run the Asset Package to Geodatabase GPTool (from Esri's Utility Network Package Tools). It would not resolve your problems, but it would encounter them and allow you to fix them in the AP before you invested a lot of effort working directly on an E-GDB.

NadiaAlami
Occasional Contributor

thank you so much...we manage to solve it with your help

0 Kudos
NadiaAlami
Occasional Contributor

thank you so much...we manage to solve it with your help

0 Kudos
MikeMillerGIS
Esri Frequent Contributor

The quicker fix is to just delete these fields in the Asset Package.  When the tools apply the Asset Package, the call to Set Subnetwork Def with create the field with the correct settings.

0 Kudos