SDE user usage in ArcSDE

Reprinted from http://blog.csdn.net/sosdsh/archive/2007/03/30/1547231.aspx

SDE user usage in ArcSDE
 
As a space database solution, ArcSDE is widely used. In this short article, we will try to describe the working mechanism of SDE and briefly describe the space data.

How to Use SDE users in the library.
How ArcSDE works

ArcSDE is a middleware technology that cannot store space data. Its role can be understood as "space expansion" of databases ". In

In an oracle-based ArcSDE spatial database, ArcSDE stores a series of Oracle Objects used to manage spatial information. These objects are collectively referred to

A repository database, including spatial data dictionary and ArcSDE SoftwareProgramPackage. ArcSDE requires the SDE user to manage space resources

Item Inventory, which is similar to the data dictionary that must be managed by sys users in Oracle. Oracle data dictionaries are stored in the system tablespace.

A specific tablespace is also required when storing the ArcSDE space archives. Generally, it is used by default for convenience.

The name is also the table space management space data dictionary of Sde.

In the working mechanism of ArcSDE, the SDE user is responsible for the interaction between ArcSDE and Oracle. By maintaining the spatial data dictionary and running in SDE mode

The package in this mode to ensure read/write consistency of the spatial database. When the ArcSDE service is started

Verify and create and maintain an oracle session connection. The Connection Program is giomgr, that is, the ArcSDE server management process.

It is always in charge of listening to user connection requests and allocating corresponding gsrvr management processes (see note 1) to maintain the spatial data dictionary.

Security of ArcSDE

The security mechanism of ArcSDE relies entirely on Oracle. Spatial database users (including SDE) need the Oracle user password to access

Space Data. ArcSDE does not store any authentication information.

In Oracle, SDE requires the following minimum system permission settings:

Create procedure/create table/create sequence/create trigger/create session

It can be seen that SDE is also a common permission user in Oracle databases.

For Oracle, although SDE is a non-DBA user, SDE has a special role in the ArcSDE architecture and is the ArcSDE administrator.

. Only SDE can do some specific work, such as starting/stopping the ArcSDE service, terminating some user connections, and compressing multi-version databases.

. Although the SDE user is not a real Oracle DBA user, the software performs some specific

Like permission operation. Therefore, SDE users should be treated as Oracle DBA users, just like sys or system, which must be strictly protected

The password.

In ArcSDE, users can be divided into two categories at the permission management level:

1. space database administrator, only and only SDE

2. General users of spatial databases, including oracle users other than SDE who create and browse spatial data, use SDE users.

The recommendation follows two principles:

The SDE user is not used to load spatial data.
The table space of the SDE data storage archive is not used to store space data.
Special object permissions of Sde users

As a general Oracle Database User, SDE users can create their own tables or stored procedures; as the ArcSDE space database administrator

In object permission settings, ArcSDE automatically grants some object permissions to SDE. SDE users need these object permissions to ensure that ArcSDE

The integrity of Geodatabase. When a spatial database user creates a new Geodatabase object, ArcSDE

Grant permissions to SDE users. For example, if an ACTC user creates a Geodatabase element class named country

Generate the corresponding supporting tables of country (Table B, business table), namely, feature table and spatial

Index table ). At this time, the SDE user will automatically obtain the select permissions for tables country, f, and S. When the user

Country is registered as a version. In ACTC mode, Table A (Additions table) and Table D (deletions

Table ). In this case, the SDE user is granted the select, insert, update, and delete permissions for table A and Table D. Permission on these objects

The ACTC user does not receive any notification during the authorization process.

In the spatial database connection of ArcGIS desktop, the object permissions of Sde users are not reflected.

For spatial database connection, only the country table in the previous example can be observed. Other support tables are filtered out. If you need to view the complete SDE

The object permission granted to the user can be obtained through the user_tab_privs_recd view of oracle.

What specific work does the SDE user do?

In a spatial database, SDE, as the administrator, can perform operations that are not generally performed by users. The following is an example:

1. start/stop the ArcSDE Service

Only SDE can interact with Oracle to start or stop ArcSDE services. Operation:
Sdemon-o start/Shutdown (start/stop)
In this case, you need to submit the SDE user password.

2. terminate a space user connection

In a spatial database connection, you can use SDE to terminate a connection when the connection process is suspended or illegal. Operation:
First, obtain the connection information from the connection list.
Sdemon-O Info-I users
After obtaining the connection ID to be terminated, run the kill command.
Sdemon-o kill-T <connection ID>
<Connection ID> to complete this operation, you need to submit the SDE user password.

3. Compress multi-versioned Geodatabase)

In ArcSDE Geodatabase, as data editing is ongoing, the SDE Spatial Data Warehouse corresponds to metadata tables and user models.

Table A and table D will gradually increase, which will affect the access efficiency of space data. Therefore, compression of database versions is often required.

. After you confirm that the database does not have any locks, you can perform the compression operation:

Sdeversion-O compress-u SDE

To complete this operation, you must submit the SDE user password.

As the ArcSDE administrator, SDE also needs to complete other work. For example, when you control the storage of data segments and index segments of spatial data,

SDE users can use the sdedbtune command to improve database efficiency.

Note 1: This is a traditional application-server connection method.

The ArcSDE server process (giomgr) assigns a process named gsrvr to fully take charge of the metadata communication between the client and the server. ArcSDE

After version 8.1, a new connection method (direct-connection) will appear. In this connection method,

The gsrvr process function is embedded in client connection applications, such as arccatalog or other ESRI software products. In this way

The function is completed by connecting the client to the application.

Test environment: ArcSDE 9.0, Oracle 9.2.0.4.0, Windows NT

Refer:
1. config_tuning_gd_oracle
2. Understanding ArcSDE
3. Website: support.esri.com

 
SDE command example
1. sdeservice command
The sdeservice command is one of the many ArcSDE command lines and can only be used in Windows operating systems. This command can be used to change the SDE

User Password. ArcSDE is used to run programs on the background. In windows, all programs running on the background are used as the corresponding

Windows Services. These windows service information is stored in the Windows operating system registration

Table.
The ArcSDE service information is also stored in the Windows registry. You must use the sdeservice command to create a registry that supports ArcSDE.

Information. This command provides the information required to start the ArcSDE service (such as license) and

Command (the program to be run when the ArcSDE service starts ).
When creating the ArcSDE service, you must specify the SDE user password. The password is encrypted and stored in the registry. With this password,

Other ArcSDE service information in the system registry can be automatically started. The password used by the giomgr process to log on to the database as an SDE user

This is the SDE user password stored in the registry we mentioned above.
Sometimes, we may need to change some configuration information of the ArcSDE service. Although these modifications can be implemented through the Registry Editor

Using the sdeservice command to modify the registry is the safest way. Of course, it should be noted that there are some records (such as ArcSDE

The administrator password is encrypted and stored) can only be modified using the sdeservice command.
Generally, the database administrator needs to modify the password of the SDE user on a regular basis. In this case, modify the SDE in the database or Windows operating system.

The user password cannot start the ArcSDE service and must be modified in the registry. If this step is not performed, the ArcSDE service is willing

It cannot be started. To change the password in the registry, use the sdeservice-O modify command in.

Modify. This command can be used to modify the sdehome directory, SDE user, license server, and NLS language. Once the SDE user password is

The data warehouse and registry are modified. Then we can start the ArcSDE service.
(Figure 1)
Sdeservice-O modify-r <sdehome | sde_dba_password | license_server | nls_lang>
-P <old_db_asmin_password>-v <new_value> [-I <service>] [-q]
2. sdemon command
The sdemon command is a commonly used ArcSDE command line tool. The sdemon command is usually used to manage the ArcSDE service. Dozen

Open the command line window, type the sdemon command, and press Enter. The following figure is displayed: Image 1
Compared with other command line operations, the sdemon command line has fewer parameters. The following describes the functions of the above sdemon operations:
Sdemon-o status displays the ArcSDE service status
Sdemon-o start starts the ArcSDE Service
Sdemon-O shutdown to disable the ArcSDE Service
Sdemon-O pause: suspend the ArcSDE service and disable new connections.
After sdemon-O resume is suspended, it allows connection to the ArcSDE service again.
Sdemon-O info provides the ArcSDE service and the current connection information. Among them, users provides all the application server connections.

User connection information; config provides all ArcSDE service configuration information; stats displays the connection information of the ArcSDE service at that time; locks

Displays all currently locked layers, state, table, and objects information. vars displays all the corresponding

Environment variable settings
Sdemon-o kill-T <{All | PID}> disconnects the ArcSDE service, where all indicates that all connections are disconnected; PID

Indicates that the connection of the process ID is disconnected.
It must be noted that the sdemon command line can only listen to application server connections (layer-3 connections), because only these connections are composed

Giomgr processes (dedicated processes of the ArcSDE server) allocate them to the specified gsrvr process for monitoring. Level 2 connection (or direct connection)

), The gsrvr process function has been embedded into the client software, and the ArcSDE service does not directly interact with such a connection. Such

The secondary connection can be directly managed through the background database.
Other commonly used SDE command lines include sdelayer, sdetable, and sdeimport. For more information, see

Administrator command reference

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/sosdsh/archive/2007/03/30/1547231.aspx