During exporting layers from SDE Database (ArcMap 10.1 SP1 for desktop (Build 3143)), to local file geodatabase, the records were exported fine (as I checked the tables) but on the map most of the points didn't appear, for some points are loosing the geometry.
The original layer appears normally on the ArcCatalog, but when exported the error happens.
- Check geometry tool results "null geometry” for the vanished points, "Repair Geometry" didn't solve it.
- Copying Features to a new layer on ArcMap, it copies the features with geometry & deletes the "null geometry".
- Copying the Layer to new file geodatabase (Copy/Paste) gave same error.
- Exporting to Shapefile also gave same error.
- Using XML Export/Import didn't manage the error.
- Using XML Export/Import didn't manage the error.
I'm sure there is something related to database, or versioning.
Any suggestions?
Thanks
I got this info from ESRI Support:
Export the SDE layers as XML file, and import that XML file to the local file geodatabase.
Also please make sure you are not falling under following category.
http://support.esri.com/en/
Bug: NIM090672: Specific Microsoft updates may result in data corruption with file geodatabases or shapefiles created on a network share
| Article ID: | 41119 |
|---|---|
| Bug Id: | NIM090672 |
| Software: | ArcGIS - ArcEditor 9.3.1, 10 ArcGIS - ArcInfo 9.3.1, 10 ArcGIS - ArcView 9.3.1, 10 ArcGIS for Desktop Advanced10.1 ArcGIS for Desktop Standard 10.1 ArcGIS for Desktop Basic 10.1 |
| Platforms: | Windows Windows 7, Server 2008 R2 |
Description
A recent Microsoft update (deployed as KB 2732673, KB 2775511, or KB 2824408) may result in data corruption when using ArcGIS on a Windows 7 system and writing data to remote data storage on a Windows Vista, Windows 7, or a Windows Server 2008/2008 R2 or 2012 system. This data corruption appears as truncation of a write request and has shown up in file geodatabases and shapefiles.
Additional Information
An error message referencing the ItemType appears when creating new datasets or items (tables, feature classes, feature datasets, raster datasets, and so forth) in a 10.x file geodatabase created on a network share.
For example, the following message is displayed when creating a new feature class:
"Failed to create feature class.
The item was not found. [ItemType:
{70737809-852C-4A03-9E22-2CECEA5B9BFA}]"
File geodatabases created with ArcGIS 9.3.1 return the following error when creating new datasets or items, renaming the file geodatabase, or accessing the geodatabase properties.
"Failed to connect to database.
This release of the Geodatabase is either invalid or out of data. [Invalid Geodatabase release]"
Additional Information
An error message referencing the ItemType appears when creating new datasets or items (tables, feature classes, feature datasets, raster datasets, and so forth) in a 10.x file geodatabase created on a network share.
For example, the following message is displayed when creating a new feature class:
"Failed to create feature class.
The item was not found. [ItemType:
{70737809-852C-4A03-9E22-2CECEA5B9BFA}]"
File geodatabases created with ArcGIS 9.3.1 return the following error when creating new datasets or items, renaming the file geodatabase, or accessing the geodatabase properties.
"Failed to connect to database.
This release of the Geodatabase is either invalid or out of data. [Invalid Geodatabase release]"
Cause
Microsoft has acknowledged the problem, identified the affected component as RDBSS.sys, and provided further details in this Windows SDK Support Team Blog.
Esri and Microsoft are working closely to understand what has changed in the RDBSS.sys component and how to resolve the problem.
How Microsoft made these updates available
KB 2732673 and KB 2824408 are hotfixes to address specific issues. The KB 2775511 update is a cumulative update that is available exclusively through the Windows Update Catalog.
Because this update is available only through the Windows Update Catalog, the KB 2775511 update is not considered a security update by Microsoft and is not being deployed broadly.
Esri and Microsoft are working closely to understand what has changed in the RDBSS.sys component and how to resolve the problem.
How Microsoft made these updates available
KB 2732673 and KB 2824408 are hotfixes to address specific issues. The KB 2775511 update is a cumulative update that is available exclusively through the Windows Update Catalog.
Because this update is available only through the Windows Update Catalog, the KB 2775511 update is not considered a security update by Microsoft and is not being deployed broadly.
Workaround
• If the patches listed above have not yet been installed, do not install them, per Microsoft's recommendation.
• If the patches listed above have been installed, Microsoft recommends uninstalling them until a solution is found.
• Create the file geodatabase or shapefile locally before copying it to the network share. Feature classes can then be created in the file geodatabase on the network share. Note that this is not applicable for raster datasets, attempting to create a raster dataset in the file geodatabase fails on the network share.
• Create and work with file geodatabases locally.
Additional Information and Updates
• June 27, 2013: Microsoft posted an update today on their Windows SDK Support Team Blog. The update states "The hotfix is currently still under development with the update being in testing. The update is on track to be released within the next 60 days (August 2013)."
• May 22, 2013: Microsoft is in regular communication with Esri and continues to have dedicated development staff working on the issue. A fix has not yet been identified.
• May 13, 2013: Microsoft has isolated the cause of this issue to an RDBSS.SYS component that was updated by a specific hotfix which is included as part of the Microsoft hotfix rollup KB 2775511. Additional information, including possible workarounds, can be found in this Microsoft Windows SDK Support Team Blog.
Esri and Microsoft continue to look for a solution to this issue.
• May 13, 2013: We have confirmed that the same issue occurs when working with shapefiles and results in an error message such as:
"Error opening feature class
Number of shapes does not match the number of table records".
• May 10, 2013: The specific Microsoft hotfix that exposed this issue has been identified. Esri and Microsoft are continuing to dedicate staff full-time to research the cause and provide a resolution as quickly as possible.
• May 6, 2013: Esri and Microsoft continue to work on this issue with dedicated full-time staff who are in regular, daily communication. These groups are currently working together with a simplified reproducible case.
• Our testing indicates that the behavior is reproducible with network shares created on Windows systems using the SMB 2.1 and SMB 3.0 protocols.
• Network shares created on Windows XP (SMB 1.0) and Windows Server 2008 (SMB 2.0) do not encounter this issue.
• The behavior is encountered when using a network share created on Windows 7 and Windows Server 2008 R2 machines.
• The issue is also not reproducible when the file geodatabase is created using the file geodatabase API.
Please contact Esri Support if other behaviors are noticed with new or existing file geodatabases after installing this specific Microsoft rollup.
• If the patches listed above have been installed, Microsoft recommends uninstalling them until a solution is found.
• Create the file geodatabase or shapefile locally before copying it to the network share. Feature classes can then be created in the file geodatabase on the network share. Note that this is not applicable for raster datasets, attempting to create a raster dataset in the file geodatabase fails on the network share.
• Create and work with file geodatabases locally.
Additional Information and Updates
• June 27, 2013: Microsoft posted an update today on their Windows SDK Support Team Blog. The update states "The hotfix is currently still under development with the update being in testing. The update is on track to be released within the next 60 days (August 2013)."
• May 22, 2013: Microsoft is in regular communication with Esri and continues to have dedicated development staff working on the issue. A fix has not yet been identified.
• May 13, 2013: Microsoft has isolated the cause of this issue to an RDBSS.SYS component that was updated by a specific hotfix which is included as part of the Microsoft hotfix rollup KB 2775511. Additional information, including possible workarounds, can be found in this Microsoft Windows SDK Support Team Blog.
Esri and Microsoft continue to look for a solution to this issue.
• May 13, 2013: We have confirmed that the same issue occurs when working with shapefiles and results in an error message such as:
"Error opening feature class
Number of shapes does not match the number of table records".
• May 10, 2013: The specific Microsoft hotfix that exposed this issue has been identified. Esri and Microsoft are continuing to dedicate staff full-time to research the cause and provide a resolution as quickly as possible.
• May 6, 2013: Esri and Microsoft continue to work on this issue with dedicated full-time staff who are in regular, daily communication. These groups are currently working together with a simplified reproducible case.
• Our testing indicates that the behavior is reproducible with network shares created on Windows systems using the SMB 2.1 and SMB 3.0 protocols.
• Network shares created on Windows XP (SMB 1.0) and Windows Server 2008 (SMB 2.0) do not encounter this issue.
• The behavior is encountered when using a network share created on Windows 7 and Windows Server 2008 R2 machines.
• The issue is also not reproducible when the file geodatabase is created using the file geodatabase API.
Please contact Esri Support if other behaviors are noticed with new or existing file geodatabases after installing this specific Microsoft rollup.
No comments:
Post a Comment