某sde问题排查过程

0
分享 2015-12-14
电话描述 :sde的服务起不起来,查看sde的日志如下:
1:
Mon Mar 1 22:59:57 2010 - ****** Spatial Database I/O Manager ******
2:
Mon Mar 1 22:59:57 2010 - SDE System Startup Initiated . . .
3:
Mon Mar 1 22:59:57 2010 - Validated System Paths.
4:
Mon Mar 1 22:59:57 2010 - SDE IOMGR going into background . . .
5:
Mon Mar 1 22:59:57 2010 - System Parameter table 'SERVER_CONFIG'
Read.
6:
Mon Mar 1 23:00:08 2010 - ERROR: Cannot Initialize Shared Memory
7:
Mon Mar 1 23:01:43 2010 - ****** Spatial Database I/O Manager ******
8:
Mon Mar 1 23:01:43 2010 - SDE System Startup Initiated . . .
9:
Mon Mar 1 23:01:43 2010 - Validated System Paths.
10:
Mon Mar 1 23:01:43 2010 - SDE IOMGR going into background . . .
11:
Mon Mar 1 23:01:43 2010 - System Parameter table 'SERVER_CONFIG'
Read.
12:
Mon Mar 1 23:01:43 2010 - ERROR: Cannot Initialize Shared Memory
13:
Mon Mar 1 23:34:36 2010 - ****** Spatial Database I/O Manager ******
14:
Mon Mar 1 23:34:36 2010 - SDE System Startup Initiated . . .
15:
Mon Mar 1 23:34:36 2010 - Validated System Paths.
16:
Mon Mar 1 23:34:36 2010 - SDE IOMGR going into background . . .
17:
Mon Mar 1 23:34:36 2010 - System Parameter table 'SERVER_CONFIG'
Read.
18:
Mon Mar 1 23:34:47 2010 - ERROR: Cannot Initialize Shared Memory
19:
Tue Mar 2 00:08:54 2010 - ****** Spatial Database I/O Manager ******
20:
Tue Mar 2 00:08:54 2010 - SDE System Startup Initiated . . .
21:
Tue Mar 2 00:08:54 2010 - Validated System Paths.
22:
Tue Mar 2 00:08:54 2010 - SDE IOMGR going into background . . .
23:
Tue Mar 2 00:08:54 2010 - System Parameter table 'SERVER_CONFIG'
Read.
24:
Tue Mar 2 00:09:05 2010 - ERROR: Cannot Initialize Shared Memory
25:
Tue Mar 2 01:22:12 2010 - ****** Spatial Database I/O Manager ******
26:
Tue Mar 2 01:22:12 2010 - SDE System Startup Initiated . . .
27:
Tue Mar 2 01:22:12 2010 - Validated System Paths.
28:
Tue Mar 2 01:22:12 2010 - SDE IOMGR going into background . . .
29:
Tue Mar 2 01:22:12 2010 - System Parameter table 'SERVER_CONFIG'
Read.
30:
Tue Mar 2 01:22:12 2010 - ERROR: Cannot Initialize Shared Memory
31:
Tue Mar 2 08:32:36 2010 - ****** Spatial Database I/O Manager ******
32:
Tue Mar 2 08:32:36 2010 - SDE System Startup Initiated . . .
33:
Tue Mar 2 08:32:36 2010 - Validated System Paths.
34:
Tue Mar 2 08:32:36 2010 - SDE IOMGR going into background . . .
35:
Tue Mar 2 08:32:36 2010 - System Parameter table 'SERVER_CONFIG'
Read.
36:
Tue Mar 2 08:32:36 2010 - ERROR: Cannot Initialize Shared Memory
37:
Tue Mar 2 08:34:44 2010 - ****** Spatial Database I/O Manager ******
38:
Tue Mar 2 08:34:44 2010 - SDE System Startup Initiated . . .
39:
Tue Mar 2 08:34:44 2010 - Validated System Paths.
40:
Tue Mar 2 08:34:44 2010 - SDE IOMGR going into background . . .
41:
Tue Mar 2 08:34:44 2010 - System Parameter table 'SERVER_CONFIG'
Read.
42:
Tue Mar 2 08:34:44 2010 - ERROR: Cannot Initialize Shared Memory
43:
Tue Mar 2 08:46:09 2010 - ****** Spatial Database I/O Manager ******
44:
Tue Mar 2 08:46:09 2010 - SDE System Startup Initiated . . .
45:
Tue Mar 2 08:46:09 2010 - Validated System Paths.
46:
Tue Mar 2 08:46:09 2010 - SDE IOMGR going into background . . .
47:
Tue Mar 2 08:46:09 2010 - System Parameter table 'SERVER_CONFIG'
Read.
48:
Tue Mar 2 08:46:09 2010 - ERROR: Cannot Initialize Shared Memory
49:
Tue Mar 2 09:11:08 2010 - ****** Spatial Database I/O Manager ******
50:
Tue Mar 2 09:11:08 2010 - SDE System Startup Initiated . . .
51:
Tue Mar 2 09:11:08 2010 - Validated System Paths.
52:
Tue Mar 2 09:11:08 2010 - SDE IOMGR going into background . . .
53:
Tue Mar 2 09:11:09 2010 - System Parameter table 'SERVER_CONFIG'
Read.
54:
Tue Mar 2 09:11:11 2010 - ERROR: Cannot Initialize Shared Memory
55:
Tue Mar 2 09:19:27 2010 - ****** Spatial Database I/O Manager ******
56:
Tue Mar 2 09:19:27 2010 - SDE System Startup Initiated . . .
57:
Tue Mar 2 09:19:27 2010 - Validated System Paths.
58:
Tue Mar 2 09:19:27 2010 - SDE IOMGR going into background . . .
59:
Tue Mar 2 09:31:15 2010 - ****** Spatial Database I/O Manager ******
60:
Tue Mar 2 09:31:15 2010 - SDE System Startup Initiated . . .
61:
Tue Mar 2 09:31:15 2010 - Validated System Paths.
62:
Tue Mar 2 09:31:15 2010 - SDE IOMGR going into background . . .

ERROR: Cannot Initialize Shared Memory,从字面上看无法分配内存了, 当时我的第一反应是不是server_config表中的某项内存太大了,另外系统的内存剩余的太小了,导致无法分配,经过确认不是上述的问题,然后让用户将sdemon -o start 的反馈结果发过来,如下
1:
$ sdemon -o start
2:
Please enter ArcSDE DBA password:
3:
-------------------------------------------------------
4:
ArcSDE 9.3.1 for
Oracle10g Build 1632 Thu Feb 26 12:05:37 2009
5:
-------------------------------------------------------
6:
ST_Geometry Schema Owner: (SDE) Type Release: 1007
7:
Instance initialized for
((sde)) . . .
8:
Connected to instance . . .
9:
C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/1: No such file or directory
10:
WARNING: SDETMP: Setting temp path to /tmp
11:
SQL Stmt: <alter indextype SDE.st_spatial_index using
SDE.st_domain_methods>
12:
DBMS Connection established...
13:
Error -51 in
purge unused shared entries.
14:
DBMS error code: -6508
15:
Error in
PL/SQL block to clean upleftover entries for
SDE instance
16:
ORA-06508: PL/SQL: could not find program unit being called
17:
ERROR: Cannot Initialize Shared Memory (-51)
18:
Could not start ArcSDE -- Check Network, $SDEHOME disk, DBMS settings and dbinit.sde.

发现出现了ORA-06508错误了,发现这个错误确定并不是内存不够,而且是分配内存的组件出问题了,但是让我比较纳闷的是系统正常运行的话,不可能无缘无故的出现这种错误,一定是用户动了什么东西,经确认,用户是在将数据删除之后再重新到入(expdp,impdp)后,服务起不来的,并且导入的过程还有错误,错误如下
1:
Processing object
type SCHEMA_EXPORT/VIEW/VIEW
2:
ORA-39125: Worker unexpected fatal error in
KUPW$WORKER.PUT_DDLS while
calling DBMS_METADATA.CONVERT []
3:
ORA-06502: PL/SQL: numeric or value
error
4:
LPX-00225: end-element tag "COL_LIST_ITEM"
does not match start-element tag "NAME"

5:
ORA-06512: at "SYS.DBMS_SYS_ERROR"
, line 95
6:
ORA-06512: at "SYS.KUPW$WORKER"
, line 6307
7:
----- PL/SQL Call Stack -----
8:
object
line object

9:
handle number name
10:
7000000d2b48b58 15032 package body SYS.KUPW$WORKER
11:
7000000d2b48b58 6372 package body SYS.KUPW$WORKER
12:
7000000d2b48b58 12391 package body SYS.KUPW$WORKER
13:
7000000d2b48b58 3346 package body SYS.KUPW$WORKER
14:
7000000d2b48b58 6972 package body SYS.KUPW$WORKER
15:
7000000d2b48b58 1314 package body SYS.KUPW$WORKER
16:
70000012280fe98 2 anonymous block

基本上确认KUPW$WORKER.PUT_DDLS出现问题,只能通过oracle的方式先将这个问题解决了才能启动sde的服务,具体如何结合见下一次。
文章来源:http://blog.csdn.net/liufeng1980423/article/details/6076820

0 个评论

要回复文章请先登录注册