So you have built a Geometric Network and encountered some errors in the process. Enter the NET_BUILDERR table, a resource to help you correct any potential problems uncovered during the build.The NET_BUILDERR table is a table that is output during the creation of the geometric network. The table is generated if errors are encountered and if the geometric network is owned by the user or the schema that builds the geometric network. This table is created n the same Feature Dataset where your network resides and can be easily previewed in ArcCatalog.When previewing this table in ArcCatalog, you will be able to see the Object ID, Class ID, and Errortype for each error encountered. In ArcGIS 9.x, the ClassID field corresponds with the ClassID found in the GDB_OBJECTCLASSSES table and identifies which feature class the ObjectIDs corresponded via the Layers table ‘Layer_id’. In ArcSDE 10 using the simplified geodatabase schema, this field now refers to the ObjectID in the ‘GDB_ITEMS’ table which will also enable you to determine which feature class the error corresponds with in the same way.Same functionality, same ID, different table…
The Net_BUILDERR table is used by the Network Build Errors command in ArcMap to identify and select the features with invalid geometries for review and correction. It can also be used for manual review. Remember that this table is user managed, so it will not automatically update after an error has been corrected.Related Links
- Identifying geometric network build errors
- Network build errors table- Repairing network feature geometry Jon D. - Geodata Support Analyst

---

How to add different-sized rasters with NoData Values 

One of the most common forum topics is on how to add two rasters with different spatial extents and get a result more than just where the two rasters overlap. Well, the reason the result is only those areas has to do with null values.

There are environment variables to modify to ensure that the rasters line up (snap raster) and the extent is preserved during the process (Spatial Extent). Fixing the environment setting alone will still not fix the output of the process. If you modify the spatial extent to match the "union of inputs", the output raster will have the correct spatial extent, but the only values will be the values where the two rasters overlapped. So what is going wrong?

Obviously it is the pixel values ... or, wait, I guess it isn't that obvious. Try this piece of wisdom provided by forum poster and Product Engineer, Eric R.

Pixel value + NoData Pixel = NoData Pixel
Pixel value + 0 = Pixel value
Pixel value + Nothing (because your extents are different) = Nothing.

You may be asking, "What is actually happening? Are the values being used in the analysis or not?" Well, the answer is they will be as long as part of that equation doesn't include a null value. If there is a null value present that will make the output null, then the output will not be correct. 

The next question is how to fix it. Bear in mind, both solutions require you to make the rasters that are being used as the inputs match in spatial extent, pixel registration and cell size. You can use the Copy Raster tool and set the appropriate environment settings to accomplish this. Once you have corrected the rasters, then there are two options depending on the desired output,1. Set the NoData values to a value of zero, so that when they're added together, the output will have the correct spatial extent and values from both rasters.2. Utilize the Con( IsNull ) workflow to include all of the pixels and add them where appropriate.

Con(IsNull("RasterSMALL"),"RasterBIG, ("RasterSMALL" + "RasterBIG"))

To recap, there are options to handle the NoData cells. Depending on what output you're trying achieve, there are different techniques. It's also important to understand the effect that NoData has when used in raster calculation. 

There is a related forum post that discusses using Python to sum multiple rasters together: Calculate sum of 2334 raster layers.Jeff S. - Geodata Raster Support Analyst

---

When using ArcSDE geodatabases, you may have noticed a change within the 10.0 release in how the upgrade process is now handled. Instead of using the Post Installation Wizard and selecting Repository Setup, as in previous releases, there is a new upgrade process. Upgrading your geodatabase is now performed within ArcCatalog using the new Upgrade Geodatabase (Data Management) tool.
The Upgrade Geodatabase (Data Management) Tool can be accessed in ArcCatalog via the Database Properties of a database connection under the General tab > Upgrade Status or within the Upgrade Geodatabase geoprocessing tool referencing an existing connection. For ArcSDE geodatabases, a direct connection to the geodatabase is necessary to run the upgrade.
 Post Installation Wizard at 10.0:
The Post Installation Wizard in 10.0 can be used for the following:

• Defining Database and SDE DBA User - Creating new ArcSDE enterprise geodatabases
• Repository Setup - Populate system repository tables (for new geodatabases only)
• Authorize ArcSDE - Perform Software Authorization of the geodatabase
• Create ArcSDE Service - If using application server service (when not using direct connections)

More changes are on the horizon to incorporate Post Installation functionality into the client tools for the 10.1 release, so stay tuned!

---