某sde问题排查过程

电话描述

:sde的服务起不起来,查看sde的日志如下:

Mon Mar  1 22:59:57 2010 - ****** Spatial Database I/O Manager ******

Mon Mar  1 22:59:57 2010 - SDE System Startup Initiated . . .

Mon Mar  1 22:59:57 2010 - Validated System Paths.

Mon Mar  1 22:59:57 2010 - SDE IOMGR going into background . . .

Mon Mar  1 22:59:57 2010 - System Parameter table 'SERVER_CONFIG' Read.

Mon Mar  1 23:00:08 2010 - ERROR: Cannot Initialize Shared Memory

Mon Mar  1 23:01:43 2010 - ****** Spatial Database I/O Manager ******

Mon Mar  1 23:01:43 2010 - SDE System Startup Initiated . . .

Mon Mar  1 23:01:43 2010 - Validated System Paths.

Mon Mar  1 23:01:43 2010 - SDE IOMGR going into background . . .

Mon Mar  1 23:01:43 2010 - System Parameter table 'SERVER_CONFIG' Read.

Mon Mar  1 23:01:43 2010 - ERROR: Cannot Initialize Shared Memory

Mon Mar  1 23:34:36 2010 - ****** Spatial Database I/O Manager ******

Mon Mar  1 23:34:36 2010 - SDE System Startup Initiated . . .

Mon Mar  1 23:34:36 2010 - Validated System Paths.

Mon Mar  1 23:34:36 2010 - SDE IOMGR going into background . . .

Mon Mar  1 23:34:36 2010 - System Parameter table 'SERVER_CONFIG' Read.

Mon Mar  1 23:34:47 2010 - ERROR: Cannot Initialize Shared Memory

Tue Mar  2 00:08:54 2010 - ****** Spatial Database I/O Manager ******

Tue Mar  2 00:08:54 2010 - SDE System Startup Initiated . . .

Tue Mar  2 00:08:54 2010 - Validated System Paths.

Tue Mar  2 00:08:54 2010 - SDE IOMGR going into background . . .

Tue Mar  2 00:08:54 2010 - System Parameter table 'SERVER_CONFIG Read.

Tue Mar  2 00:09:05 2010 - ERROR: Cannot Initialize Shared Memory

Tue Mar  2 01:22:12 2010 - ****** Spatial Database I/O Manager ******

Tue Mar  2 01:22:12 2010 - SDE System Startup Initiated . . .

Tue Mar  2 01:22:12 2010 - Validated System Paths.

Tue Mar  2 01:22:12 2010 - SDE IOMGR going into background . . .

Tue Mar  2 01:22:12 2010 - System Parameter table 'SERVER_CONFIG' Read.

Tue Mar  2 01:22:12 2010 - ERROR: Cannot Initialize Shared Memory

Tue Mar  2 08:32:36 2010 - ****** Spatial Database I/O Manager ******

Tue Mar  2 08:32:36 2010 - SDE System Startup Initiated . . .

Tue Mar  2 08:32:36 2010 - Validated System Paths.

Tue Mar  2 08:32:36 2010 - SDE IOMGR going into background . . .

Tue Mar  2 08:32:36 2010 - System Parameter table 'SERVER_CONFIG' Read.

Tue Mar  2 08:32:36 2010 - ERROR: Cannot Initialize Shared Memory

Tue Mar  2 08:34:44 2010 - ****** Spatial Database I/O Manager ******

Tue Mar  2 08:34:44 2010 - SDE System Startup Initiated . . .

Tue Mar  2 08:34:44 2010 - Validated System Paths.

Tue Mar  2 08:34:44 2010 - SDE IOMGR going into background . . .

Tue Mar  2 08:34:44 2010 - System Parameter table 'SERVER_CONFIG' Read.

Tue Mar  2 08:34:44 2010 - ERROR: Cannot Initialize Shared Memory

Tue Mar  2 08:46:09 2010 - ****** Spatial Database I/O Manager ******

Tue Mar  2 08:46:09 2010 - SDE System Startup Initiated . . .

Tue Mar  2 08:46:09 2010 - Validated System Paths.

Tue Mar  2 08:46:09 2010 - SDE IOMGR going into background . . .

Tue Mar  2 08:46:09 2010 - System Parameter table 'SERVER_CONFIG' Read.

Tue Mar  2 08:46:09 2010 - ERROR: Cannot Initialize Shared Memory

Tue Mar  2 09:11:08 2010 - ****** Spatial Database I/O Manager ******

Tue Mar  2 09:11:08 2010 - SDE System Startup Initiated . . .

Tue Mar  2 09:11:08 2010 - Validated System Paths.

Tue Mar  2 09:11:08 2010 - SDE IOMGR going into background . . .

Tue Mar  2 09:11:09 2010 - System Parameter table 'SERVER_CONFIG' Read.

Tue Mar  2 09:11:11 2010 - ERROR: Cannot Initialize Shared Memory

Tue Mar  2 09:19:27 2010 - ****** Spatial Database I/O Manager ******

Tue Mar  2 09:19:27 2010 - SDE System Startup Initiated . . .

Tue Mar  2 09:19:27 2010 - Validated System Paths.

Tue Mar  2 09:19:27 2010 - SDE IOMGR going into background . . .

Tue Mar  2 09:31:15 2010 - ****** Spatial Database I/O Manager ******

Tue Mar  2 09:31:15 2010 - SDE System Startup Initiated . . .

Tue Mar  2 09:31:15 2010 - Validated System Paths.

Tue Mar  2 09:31:15 2010 - SDE IOMGR going into background . . .

ERROR: Cannot Initialize Shared Memory,从字面上看无法分配内存了，

当时我的第一反应是不是server_config表中的某项内存太大了，另外系统的内存剩余的太小了，导致无法分配，经过确认不是上述的问题，然后让用户将sdemon -o start 的反馈结果发过来，如下

$ sdemon -o start

Please enter ArcSDE DBA password:

-------------------------------------------------------

ArcSDE 9.3.1  for
Oracle10g Build 1632 Thu Feb 26 12:05:37  2009

-------------------------------------------------------

ST_Geometry Schema Owner: (SDE) Type Release: 1007

Instance initialized for((sde)) . . .

Connected to instance . . .

C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/1: No such file or directory

WARNING: SDETMP: Setting temp path to /tmp

SQL Stmt: <alter indextype SDE.st_spatial_index using SDE.st_domain_methods>

DBMS Connection established...

Error -51 in purge unused shared entries.

DBMS error code: -6508

Error in PL/SQL block to clean  upleftover entries for SDE instance

ORA-06508: PL/SQL: could not find program unit being called

ERROR: Cannot Initialize Shared Memory (-51)

Could not start ArcSDE -- Check Network, $SDEHOME disk, DBMS settings and dbinit.sde.

发现出现了ORA-06508错误了，发现这个错误确定并不是内存不够，而且是分配内存的组件出问题了，但是让我比较纳闷的是系统正常运行的话，不可能无缘无故的出现这种错误，一定是用户动了什么东西，经确认，用户是在将数据删除之后再重新到入(expdp,impdp)后，服务起不来的，并且导入的过程还有错误，错误如下

Processing object
type SCHEMA_EXPORT/VIEW/VIEW

ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling DBMS_METADATA.CONVERT []

ORA-06502: PL/SQL: numeric or value error

LPX-00225: end-element tag "COL_LIST_ITEM" does not match start-element tag "NAME"

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95

ORA-06512: at "SYS.KUPW$WORKER", line 6307

----- PL/SQL Call Stack -----

object
line  object

handle    number  name

7000000d2b48b58     15032  package body SYS.KUPW$WORKER

7000000d2b48b58      6372  package body SYS.KUPW$WORKER

7000000d2b48b58     12391  package body SYS.KUPW$WORKER

7000000d2b48b58      3346  package body SYS.KUPW$WORKER

7000000d2b48b58      6972  package body SYS.KUPW$WORKER

7000000d2b48b58      1314  package body SYS.KUPW$WORKER

70000012280fe98         2  anonymous block

基本上确认KUPW$WORKER.PUT_DDLS出现问题，只能通过oracle的方式先将这个问题解决了才能启动sde的服务，具体如何结合见下一次。