Sometime ArcSDE administration commands are referred to as ArcSDe command line utilities. These commands are used by ArcSDE administrator to manage and monitor the use of an ArcSDE service and geodatabase. The commands are divided into two categories: server administration commands and data management commands.
Server administration commands:
Sdeconfig: manages the ArcSDE server configuration table (SERVER_CONFIG). SERVER_CONFIG stores parameters and values that define how the ArcSDE server uses memory.
Sdedbtune: manages parameters of the DBTUNE table. DBTUNE contains parameters and values, grouped by configuration keywords to specify how data is stored in the database.
Sdegcdrules: manages geocoding rules.
Sdegdbrepair: identifies and repairs any inconsistencies between the adds (A) and the deletes (D) tables of a versioned geodatabase.
Sdelocator: manages locators.
Sdelog: administers log files (used primarily for shared log files).
Sdemon: monitors and manages the ArcSDE service.
Sdeservice: manages the ArcSDE service on Windows.
Sdesetup: does the initial geodatabase creation within the DBMS, upgrades the geodatabase, and updates your license file.
Data management commads:
sdeexport: Creates an ArcSDE export file.
sdeimport: Imports data from an ArcSDE export file.
sdegroup: Merges features by combining their geometries into multipart shapes. Features are grouped by tiles or by a business table attribute.
sdelayer: Administers feature classes, including getting ArcSDE geometry information.
sderaster: Manages raster layers.
sdetable: Administers business tables and their data.
sdexinfo: Describes an ArcSDE export file.
sdexml: Administers XML columns.
cov2sde: Converts ArcInfo coverages to geodatabase feature classes.
sde2cov: Converts geodatabase feature classes to ArcInfo coverages.
sde2shp: Extracts features from a geodatabase feature class or log file and writes them to a shapefile.
sde2tbl: Converts geodatabase tables to INFO or dBASE Tables.
sdeversion: Manages geodatabase versions.
shp2sde: Converts shapefiles to geodatabase feature classes.
tbl2sde: Creates a table in the geodatabase, appends data to an existing table in the geodatabase, or replaces records in an existing table in the geodatabase.
Up to ArcSDE 9.2, some operations of data management commands can not be performed by ArcGIS Desktop software (ArcMap and ArcCatalog), including sdeexport, sdeimport, sdegroup, sdelayer, sderaster, sdetable, sdexinfo, sdexml. Functions of commands (cov2sde, sde2cov, sde2shp, sde2tbl, sdeversion, shp2sde, tbl2sde) can be performed by using ArcGIS Desktop software.
Note:
1. ArcSDE data management commands for loading data, such as shp2sde and cov2sde, cannot be used to load data into a feature class that is contained within a Geodatabase feature dataset. Only an ArcObjects application, such as ArcCatalog, ArcMap, and custom-built ArcObjects applications, can be used to load data into a feature class contained within a Geodatabase feature dataset.
2. If a feature class is created in ArcCatalog, using a command to delete it would leave orphaned records in the geodatabase system tables, as the ArcSDE commands are not geodatabase aware. The best way would be to manage them using ArcCatalog itself.
3. It is recommended not to manage standalone feature classes with command line utilities. Layers created with command line should be registered with the Geodatabase to avoid unnecessary issues (such as OBJECTID).
More Oracle DBA tips, please visit Oracle DBA Tips
Server administration commands:
Sdeconfig: manages the ArcSDE server configuration table (SERVER_CONFIG). SERVER_CONFIG stores parameters and values that define how the ArcSDE server uses memory.
Sdedbtune: manages parameters of the DBTUNE table. DBTUNE contains parameters and values, grouped by configuration keywords to specify how data is stored in the database.
Sdegcdrules: manages geocoding rules.
Sdegdbrepair: identifies and repairs any inconsistencies between the adds (A) and the deletes (D) tables of a versioned geodatabase.
Sdelocator: manages locators.
Sdelog: administers log files (used primarily for shared log files).
Sdemon: monitors and manages the ArcSDE service.
Sdeservice: manages the ArcSDE service on Windows.
Sdesetup: does the initial geodatabase creation within the DBMS, upgrades the geodatabase, and updates your license file.
Data management commads:
sdeexport: Creates an ArcSDE export file.
sdeimport: Imports data from an ArcSDE export file.
sdegroup: Merges features by combining their geometries into multipart shapes. Features are grouped by tiles or by a business table attribute.
sdelayer: Administers feature classes, including getting ArcSDE geometry information.
sderaster: Manages raster layers.
sdetable: Administers business tables and their data.
sdexinfo: Describes an ArcSDE export file.
sdexml: Administers XML columns.
cov2sde: Converts ArcInfo coverages to geodatabase feature classes.
sde2cov: Converts geodatabase feature classes to ArcInfo coverages.
sde2shp: Extracts features from a geodatabase feature class or log file and writes them to a shapefile.
sde2tbl: Converts geodatabase tables to INFO or dBASE Tables.
sdeversion: Manages geodatabase versions.
shp2sde: Converts shapefiles to geodatabase feature classes.
tbl2sde: Creates a table in the geodatabase, appends data to an existing table in the geodatabase, or replaces records in an existing table in the geodatabase.
Up to ArcSDE 9.2, some operations of data management commands can not be performed by ArcGIS Desktop software (ArcMap and ArcCatalog), including sdeexport, sdeimport, sdegroup, sdelayer, sderaster, sdetable, sdexinfo, sdexml. Functions of commands (cov2sde, sde2cov, sde2shp, sde2tbl, sdeversion, shp2sde, tbl2sde) can be performed by using ArcGIS Desktop software.
Note:
1. ArcSDE data management commands for loading data, such as shp2sde and cov2sde, cannot be used to load data into a feature class that is contained within a Geodatabase feature dataset. Only an ArcObjects application, such as ArcCatalog, ArcMap, and custom-built ArcObjects applications, can be used to load data into a feature class contained within a Geodatabase feature dataset.
2. If a feature class is created in ArcCatalog, using a command to delete it would leave orphaned records in the geodatabase system tables, as the ArcSDE commands are not geodatabase aware. The best way would be to manage them using ArcCatalog itself.
3. It is recommended not to manage standalone feature classes with command line utilities. Layers created with command line should be registered with the Geodatabase to avoid unnecessary issues (such as OBJECTID).
More Oracle DBA tips, please visit Oracle DBA Tips
