早上，同事让我帮忙打开131上的虚拟机进行测试，登录到机器上，顺利将数据库启动后，同事使用Desktop连接后，接着报
发现是没有启动监听，继续登录到机器上将监听也启动起来，本来以为同事可以顺利连接了，但是使用Desktop连接接着报
我这边测试也是同样的问题。
从字面上描述Geodatabase无效或者是过期了，以前低版本（9.x）客户端访问高版本Geodatabase会碰到类似这样的问题。
但是这个Geodatabase一直是我维护的，版本是10.2.1，我使用的Desktop版本是10.3.1,高版本的客户端是可以连接低版本的Geodatabase的，因此可以排除版本的问题。
使用10046 trace查看后台执行的SQL语句，
ARSING IN CURSOR #425905872 len=30 dep=0 uid=91 oct=3 lid=91 tim=1590922638 hv=2231185647 ad='7ff5bd5cf88' sqlid='aux1zx62guc7g'
SELECT * FROM SDE.sde_xml_doc1
END OF STMT
PARSE #425905872:c=0,e=688,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,plh=2943407123,tim=1590922636
WAIT #425905872: nam='SQL*Net message to client' ela= 3 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1590922702
WAIT #425905872: nam='SQL*Net message from client' ela= 1164 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1590923916
CLOSE #425905872:c=0,e=8,dep=0,type=0,tim=1590923958
=====================
PARSING IN CURSOR #425905872 len=30 dep=0 uid=91 oct=3 lid=91 tim=1590924644 hv=2371270856 ad='7ff5bd58858' sqlid='5t38y1u6pdf68'
SELECT * FROM SDE.sde_xml_doc2
END OF STMT
PARSE #425905872:c=0,e=651,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,plh=3054090045,tim=1590924643
WAIT #425905872: nam='SQL*Net message to client' ela= 3 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1590924703
WAIT #425905872: nam='SQL*Net message from client' ela= 934 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1590925672
CLOSE #425905872:c=0,e=8,dep=0,type=0,tim=1590925717
=====================
PARSING IN CURSOR #425878616 len=283 dep=1 uid=0 oct=3 lid=0 tim=1590926313 hv=1612870922 ad='7ff643465b8' sqlid='gnkrt49h24x8a'
select pctfree_stg, pctused_stg, size_stg,initial_stg, next_stg, minext_stg, maxext_stg, maxsiz_stg, lobret_stg,mintim_stg, pctinc_stg, initra_stg, maxtra_stg, optimal_stg, maxins_stg,frlins_stg, flags_stg, bfp_stg, enc_stg, cmpflag_stg, cmplvl_stg from deferred_stg$ where obj# =:1
END OF STMT
PARSE #425878616:c=0,e=395,p=0,cr=0,cu=0,mis=1,r=0,dep=1,og=4,plh=0,tim=1590926312
BINDS #425878616:
Bind#0
oacdty=02 mxl=22(22) mxlc=00 mal=00 scl=00 pre=00
oacflg=00 fl2=0001 frm=00 csi=00 siz=24 off=0
kxsbbbfp=19644038 bln=22 avl=04 flg=05
value=74934
EXEC #425878616:c=0,e=816,p=0,cr=0,cu=0,mis=1,r=0,dep=1,og=4,plh=866645418,tim=1590927236
FETCH #425878616:c=0,e=10,p=0,cr=1,cu=0,mis=0,r=0,dep=1,og=4,plh=866645418,tim=1590927268
STAT #425878616 id=1 cnt=0 pid=0 pos=1 obj=97101 op='TABLE ACCESS BY INDEX ROWID DEFERRED_STG$ (cr=1 pr=0 pw=0 time=14 us cost=0 size=286 card=1)'
STAT #425878616 id=2 cnt=0 pid=1 pos=1 obj=97102 op='INDEX UNIQUE SCAN I_DEFERRED_STG1 (cr=1 pr=0 pw=0 time=7 us cost=0 size=0 card=1)'
CLOSE #425878616:c=0,e=3,dep=1,type=3,tim=1590927340
=====================
PARSE ERROR #425905872:len=30 dep=0 uid=91 oct=3 lid=91 tim=1591011466 err=600
SELECT * FROM SDE.sde_xml_doc3
WAIT #425905872: nam='SQL*Net break/reset to client' ela= 4 driver id=1413697536 break?=1 p3=0 obj#=-1 tim=1591011658
WAIT #425905872: nam='SQL*Net break/reset to client' ela= 1132 driver id=1413697536 break?=0 p3=0 obj#=-1 tim=1591012811
WAIT #425905872: nam='SQL*Net message to client' ela= 2 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591012838
WAIT #425905872: nam='SQL*Net message from client' ela= 8598 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591021476
CLOSE #425905872:c=0,e=12,dep=0,type=0,tim=1591021590
BINDS #425912928:
Bind#0
oacdty=01 mxl=32(06) mxlc=00 mal=00 scl=00 pre=00
oacflg=20 fl2=1000000 frm=01 csi=852 siz=64 off=0
kxsbbbfp=1962d228 bln=32 avl=03 flg=05
value="SDE"
Bind#1
oacdty=01 mxl=32(22) mxlc=00 mal=00 scl=00 pre=00
oacflg=20 fl2=1000000 frm=01 csi=852 siz=0 off=32
kxsbbbfp=1962d248 bln=32 avl=11 flg=01
value="GDB_RELEASE"
EXEC #425912928:c=0,e=251,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,plh=1467024140,tim=1591021945
FETCH #425912928:c=0,e=44,p=0,cr=2,cu=0,mis=0,r=0,dep=0,og=1,plh=1467024140,tim=1591022082
WAIT #425912928: nam='SQL*Net message to client' ela= 4 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591022177
WAIT #425912928: nam='SQL*Net message from client' ela= 1280 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591023500
BINDS #425912928:
Bind#0
oacdty=01 mxl=32(06) mxlc=00 mal=00 scl=00 pre=00
oacflg=20 fl2=1000000 frm=01 csi=852 siz=64 off=0
kxsbbbfp=1962d228 bln=32 avl=03 flg=05
value="SDE"
Bind#1
oacdty=01 mxl=32(22) mxlc=00 mal=00 scl=00 pre=00
oacflg=20 fl2=1000000 frm=01 csi=852 siz=0 off=32
kxsbbbfp=1962d248 bln=32 avl=11 flg=01
value="GDB_RELEASE"
EXEC #425912928:c=0,e=214,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,plh=1467024140,tim=1591023748
FETCH #425912928:c=0,e=29,p=0,cr=2,cu=0,mis=0,r=0,dep=0,og=1,plh=1467024140,tim=1591023847
WAIT #425912928: nam='SQL*Net message to client' ela= 4 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591023931
WAIT #425912928: nam='SQL*Net message from client' ela= 901 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591024974
BINDS #425912928:
Bind#0
oacdty=01 mxl=32(06) mxlc=00 mal=00 scl=00 pre=00
oacflg=20 fl2=1000000 frm=01 csi=852 siz=64 off=0
kxsbbbfp=1962d228 bln=32 avl=03 flg=05
value="SDE"
Bind#1
oacdty=01 mxl=32(22) mxlc=00 mal=00 scl=00 pre=00
oacflg=20 fl2=1000000 frm=01 csi=852 siz=0 off=32
kxsbbbfp=1962d248 bln=32 avl=11 flg=01
value="GDB_RELEASE"
EXEC #425912928:c=0,e=192,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,plh=1467024140,tim=1591025241
FETCH #425912928:c=0,e=29,p=0,cr=2,cu=0,mis=0,r=0,dep=0,og=1,plh=1467024140,tim=1591025357
WAIT #425912928: nam='SQL*Net message to client' ela= 2 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591025478
WAIT #425912928: nam='SQL*Net message from client' ela= 1341 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591026843
BINDS #425912928:
Bind#0
oacdty=01 mxl=32(06) mxlc=00 mal=00 scl=00 pre=00
oacflg=20 fl2=1000000 frm=01 csi=852 siz=64 off=0
kxsbbbfp=1962d228 bln=32 avl=03 flg=05
value="SDE"
Bind#1
oacdty=01 mxl=32(22) mxlc=00 mal=00 scl=00 pre=00
oacflg=20 fl2=1000000 frm=01 csi=852 siz=0 off=32
kxsbbbfp=1962d248 bln=32 avl=11 flg=01
value="GDB_RELEASE"
EXEC #425912928:c=0,e=203,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,plh=1467024140,tim=1591027119
FETCH #425912928:c=0,e=17,p=0,cr=2,cu=0,mis=0,r=0,dep=0,og=1,plh=1467024140,tim=1591027218
WAIT #425912928: nam='SQL*Net message to client' ela= 4 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591027294
WAIT #425912928: nam='SQL*Net message from client' ela= 550 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591027888
=====================
PARSE ERROR #425666352:len=45 dep=0 uid=91 oct=3 lid=91 tim=1591028475 err=942
SELECT GDB_RELEASE.* FROM SDE.GDB_RELEASE
WAIT #425666352: nam='SQL*Net break/reset to client' ela= 5 driver id=1413697536 break?=1 p3=0 obj#=-1 tim=1591028656
WAIT #425666352: nam='SQL*Net break/reset to client' ela= 726 driver id=1413697536 break?=0 p3=0 obj#=-1 tim=1591029423
WAIT #425666352: nam='SQL*Net message to client' ela= 2 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591029473
WAIT #425666352: nam='SQL*Net message from client' ela= 2727 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1591032226
CLOSE #425666352:c=0,e=8,dep=0,type=0,tim=1591032308
=====================最后执行的几个SQL语句，并无什么不对劲的地方。
此时真是。。。。。。。。。。。。。。。
仔细想想，这个库没有什么变动，只是上个周五，由于版本过低，执行GeoSQL总是报
ORA-28579(Oracle 11.2.0.1的bug)， 因此将其版本从11.2.0.1升级到了11.2.0.4。 升级过后数据库正常打开后，就下班闪人了。
突然想起来好像少点什么，是不是无效对象导致的？？？
SQL> select object_name,object_type from dba_objects where owner='SDE' and status='INVALID';
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A1_IX1 INDEX
XMLDOCIX4_TX INDEX
A16_IX1 INDEX
A13_IX1 INDEX
VERSION_UTIL PACKAGE BODY
ST_TYPE_EXPORT PACKAGE BODY
ST_DOMAIN_METHODS TYPE
ST_DOMAIN_METHODS TYPE BODY
ST_CONTAINS OPERATOR
ST_WITHIN OPERATOR
ST_INTERSECTS OPERATOR
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
ST_OVERLAPS OPERATOR
ST_TOUCHES OPERATOR
ST_CROSSES OPERATOR
ST_ORDERINGEQUALS OPERATOR
ST_EQUALS OPERATOR
ST_BUFFER_INTERSECTS OPERATOR
ST_RELATE OPERATOR
SDEXMLTOTEXT OPERATOR
ST_SPATIAL_INDEX INDEXTYPE
XMLDOCIX1_TX INDEX
XMLDOCIX2_TX INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
XMLDOCIX3_TX INDEX
GDB_ITEMS_VW VIEW
GDB_ITEMRELATIONSHIP VIEW
S_VW
A2_IX1 INDEX
A6_IX1 INDEX
A7_IX1 INDEX
A8_IX1 INDEX
A15_IX1 INDEX
A43_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A9_IX1 INDEX
A11_IX1 INDEX
A12_IX1 INDEX
A341_IX1 INDEX
A342_IX1 INDEX
A343_IX1 INDEX
A344_IX1 INDEX
A273_IX1 INDEX
A345_IX1 INDEX
A96_IX1 INDEX
A346_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A14_IX1 INDEX
A38_IX1 INDEX
A19_IX1 INDEX
GDB_ARCHIVE_TR33 TRIGGER
NVV33_INSERT TRIGGER
A20_IX1 INDEX
A41_IX1 INDEX
A23_IX1 INDEX
A26_IX1 INDEX
A33_IX1 INDEX
A89_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A90_IX1 INDEX
A91_IX1 INDEX
A92_IX1 INDEX
A87_IX1 INDEX
A114_IX1 INDEX
A223_IX1 INDEX
A225_IX1 INDEX
DDD_VIEW VIEW
A227_IX1 INDEX
A93_IX1 INDEX
A94_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A103_IX1 INDEX
A104_IX1 INDEX
A105_IX1 INDEX
A77_IX1 INDEX
A78_IX1 INDEX
A298_IX1 INDEX
A299_IX1 INDEX
A300_IX1 INDEX
A78_IX1_A INDEX
A8_IX1_A INDEX
A97_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A250_IX1 INDEX
A250_IX1_A INDEX
A88_IX1 INDEX
A84_IX1 INDEX
A85_IX1 INDEX
A86_IX1 INDEX
A261_IX1 INDEX
A262_IX1 INDEX
A266_IX1 INDEX
A267_IX1 INDEX
A268_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A203_IX1_A INDEX
A252_IX1 INDEX
A67_IX1 INDEX
A45_IX1 INDEX
A68_IX1 INDEX
A252_IX1_A INDEX
A73_IX1 INDEX
A143_IX1 INDEX
A100_IX1 INDEX
A75_IX1 INDEX
A75_IX1_A INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
V158_INSERT TRIGGER
V158_DELETE TRIGGER
V158_UPDATE TRIGGER
A76_IX1 INDEX
A76_IX1_A INDEX
V159_INSERT TRIGGER
V159_DELETE TRIGGER
V159_UPDATE TRIGGER
A253_IX1 INDEX
A231_IX1 INDEX
A106_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A107_IX1 INDEX
A137_IX1 INDEX
A138_IX1 INDEX
A139_IX1 INDEX
A140_IX1 INDEX
A109_IX1 INDEX
A232_IX1 INDEX
A110_IX1 INDEX
A111_IX1 INDEX
A112_IX1 INDEX
A187_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A130_IX1 INDEX
A110_IX1_A INDEX
V197_INSERT TRIGGER
V197_DELETE TRIGGER
V197_UPDATE TRIGGER
A130_IX1_A INDEX
V234_INSERT TRIGGER
V234_DELETE TRIGGER
V234_UPDATE TRIGGER
A131_IX1 INDEX
A131_IX1_A INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
V235_INSERT TRIGGER
V235_DELETE TRIGGER
V235_UPDATE TRIGGER
A133_IX1 INDEX
A134_IX1 INDEX
A135_IX1 INDEX
A136_IX1 INDEX
A405_IX1 INDEX
TESTDDD_IDX INDEX
TESTDDD1_IDX INDEX
A178_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A220_IX1 INDEX
A335_IX1 INDEX
A221_IX1 INDEX
A222_IX1 INDEX
A189_IX1 INDEX
A336_IX1 INDEX
A337_IX1 INDEX
A338_IX1 INDEX
A339_IX1 INDEX
A340_IX1 INDEX
A177_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A188_IX1 INDEX
A233_IX1 INDEX
A233_IX1_A INDEX
A172_IX1 INDEX
A176_IX1 INDEX
A97_IX1_A INDEX
A96_IX1_A INDEX
A254_IX1 INDEX
A256_IX1 INDEX
A257_IX1 INDEX
A258_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A259_IX1 INDEX
A260_IX1 INDEX
A179_IX1 INDEX
A190_IX1 INDEX
A215_IX1 INDEX
A205_IX1 INDEX
A209_IX1 INDEX
A322_IX1 INDEX
A270_IX1 INDEX
A272_IX1 INDEX
A196_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A199_IX1 INDEX
A361_IX1 INDEX
A362_IX1 INDEX
A201_IX1 INDEX
A203_IX1 INDEX
A277_IX1 INDEX
A278_IX1 INDEX
A378_IX1 INDEX
GDB_ARCHIVE_TR1463 TRIGGER
A307_IX1 INDEX
A282_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A283_IX1 INDEX
A284_IX1 INDEX
A279_IX1 INDEX
A286_IX1 INDEX
A308_IX1 INDEX
A290_IX1 INDEX
A309_IX1 INDEX
GDB_ARCHIVE_TR619 TRIGGER
A311_IX1 INDEX
A312_IX1 INDEX
A313_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A314_IX1 INDEX
A291_IX1 INDEX
A292_IX1 INDEX
A293_IX1 INDEX
A294_IX1 INDEX
A315_IX1 INDEX
A295_IX1 INDEX
A323_IX1 INDEX
A316_IX1 INDEX
A296_IX1 INDEX
A297_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A317_IX1 INDEX
A318_IX1 INDEX
A319_IX1 INDEX
A347_IX1 INDEX
A196_IX1_A INDEX
A348_IX1 INDEX
A349_IX1 INDEX
A350_IX1 INDEX
A351_IX1 INDEX
A352_IX1 INDEX
A353_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A354_IX1 INDEX
A326_IX1 INDEX
A355_IX1 INDEX
A356_IX1 INDEX
A357_IX1 INDEX
A358_IX1 INDEX
A359_IX1 INDEX
A360_IX1 INDEX
A103_IX1_A INDEX
A327_IX1 INDEX
A329_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A331_IX1 INDEX
A332_IX1 INDEX
A333_IX1 INDEX
A334_IX1 INDEX
A363_IX1 INDEX
A255_IX1 INDEX
A364_IX1 INDEX
A366_IX1 INDEX
A364_IX1_A INDEX
A366_IX1_A INDEX
A365_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A365_IX1_A INDEX
A367_IX1 INDEX
A380_IX1 INDEX
A383_IX1 INDEX
A384_IX1 INDEX
A369_IX1 INDEX
A9_IX1_A INDEX
A370_IX1 INDEX
A386_IX1 INDEX
A387_IX1 INDEX
A388_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A371_IX1 INDEX
A372_IX1 INDEX
A372_IX1_A INDEX
A373_IX1 INDEX
A374_IX1 INDEX
A392_IX1 INDEX
A393_IX1 INDEX
A394_IX1 INDEX
A395_IX1 INDEX
A375_IX1 INDEX
A376_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A396_IX1 INDEX
A397_IX1 INDEX
A398_IX1 INDEX
A399_IX1 INDEX
A400_IX1 INDEX
A114_IX1_A INDEX
A416_IX1 INDEX
A417_IX1 INDEX
A418_IX1 INDEX
A401_IX1 INDEX
A402_IX1 INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A403_IX1 INDEX
A409_IX1 INDEX
A410_IX1 INDEX
A411_IX1 INDEX
A413_IX1 INDEX
A414_IX1 INDEX
A415_IX1 INDEX
GDB_ARCHIVE_TR1737 TRIGGER
A416_IX1_A INDEX
A113_IX1 INDEX
A113_IX1_A INDEX
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
A419_IX1 INDEX
A423_IX1 INDEX
A424_IX1 INDEX
A426_IX1 INDEX
A427_IX1 INDEX
已选择289行。
SQL> spool off
果然接近300个无效对象，最主要的VERSION_UTIL这个包体也无效，这个包就是用来获取Geodatabase版本信息的。
重新编译一下无效对象
SQL> exec dbms_utility.compile_schema('SDE');
PL/SQL 过程已成功完成。重新使用Desktop连接，发现错误依旧。
继续
SQL> select object_name,object_type from dba_objects where owner='SDE' and status='INVALID';
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
DDD_VIEW VIEW
DEMO_EVW VIEW
V161_INSERT TRIGGER
V161_DELETE TRIGGER
V161_UPDATE TRIGGER
DWP_27200_EVW VIEW
V391_INSERT TRIGGER
V391_DELETE TRIGGER
V391_UPDATE TRIGGER
HURI_EVW VIEW
V395_INSERT TRIGGER
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
V395_DELETE TRIGGER
V395_UPDATE TRIGGER
AAB_VW VIEW
V333_INSERT TRIGGER
V333_DELETE TRIGGER
V333_UPDATE TRIGGER
TESTVERSION_EVW VIEW
V399_INSERT TRIGGER
V399_DELETE TRIGGER
V399_UPDATE TRIGGER
SHIYUTEST_EVW VIEW
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
V159_INSERT TRIGGER
V159_DELETE TRIGGER
V159_UPDATE TRIGGER
JZWP_26320_EVW VIEW
V387_INSERT TRIGGER
V387_DELETE TRIGGER
V387_UPDATE TRIGGER
JZWL_26410_EVW VIEW
V388_INSERT TRIGGER
V388_DELETE TRIGGER
V388_UPDATE TRIGGER
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
POINTSOFINTEREST_VW VIEW
V197_INSERT TRIGGER
V197_DELETE TRIGGER
V197_UPDATE TRIGGER
AAAAAAA_VW VIEW
V235_INSERT TRIGGER
V235_DELETE TRIGGER
V235_UPDATE TRIGGER
DWP_27500_EVW VIEW
V394_INSERT TRIGGER
V394_DELETE TRIGGER
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
V394_UPDATE TRIGGER
DWP_27100_EVW VIEW
V390_INSERT TRIGGER
V390_DELETE TRIGGER
V390_UPDATE TRIGGER
JZWP_26100_EVW VIEW
V381_INSERT TRIGGER
V381_DELETE TRIGGER
V381_UPDATE TRIGGER
JZWP_26240_EVW VIEW
V385_INSERT TRIGGER
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
V385_DELETE TRIGGER
V385_UPDATE TRIGGER
JZWP_26230_EVW VIEW
V384_INSERT TRIGGER
V384_DELETE TRIGGER
V384_UPDATE TRIGGER
JZWL_26420_EVW VIEW
V389_INSERT TRIGGER
V389_DELETE TRIGGER
V389_UPDATE TRIGGER
DWP_27400_EVW VIEW
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
V393_INSERT TRIGGER
V393_DELETE TRIGGER
V393_UPDATE TRIGGER
JZWP_26310_EVW VIEW
V386_INSERT TRIGGER
V386_DELETE TRIGGER
V386_UPDATE TRIGGER
DWP_27300_EVW VIEW
V392_INSERT TRIGGER
V392_DELETE TRIGGER
V392_UPDATE TRIGGER
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
JZWP_26210_EVW VIEW
V382_INSERT TRIGGER
V382_DELETE TRIGGER
V382_UPDATE TRIGGER
JZWP_26220_EVW VIEW
V383_INSERT TRIGGER
V383_DELETE TRIGGER
V383_UPDATE TRIGGER
TEST4FEATURESERVICE_ VIEW
EVW
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
V377_INSERT TRIGGER
V377_DELETE TRIGGER
V377_UPDATE TRIGGER
CHINAPINT_EVW VIEW
V182_INSERT TRIGGER
V182_DELETE TRIGGER
V182_UPDATE TRIGGER
CHINAPOINT2_EVW VIEW
V181_INSERT TRIGGER
V181_DELETE TRIGGER
V181_UPDATE TRIGGER
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
ZXYTEST_EVW VIEW
V190_INSERT TRIGGER
V190_DELETE TRIGGER
V190_UPDATE TRIGGER
NETLINE_VW VIEW
V1293_INSERT TRIGGER
V1293_DELETE TRIGGER
V1293_UPDATE TRIGGER
GEONET_NET_JUNCTIONS VIEW
_VW
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
V1305_INSERT TRIGGER
V1305_DELETE TRIGGER
V1305_UPDATE TRIGGER
JMBDDD_EVW VIEW
V14_INSERT TRIGGER
V14_DELETE TRIGGER
V14_UPDATE TRIGGER
TEST2_EVW VIEW
V1375_INSERT TRIGGER
V1375_DELETE TRIGGER
V1375_UPDATE TRIGGER
OBJECT_NAME OBJECT_TYPE
-------------------- -------------------
PO_EVW VIEW
V201_INSERT TRIGGER
V201_DELETE TRIGGER
V201_UPDATE TRIGGER
P_EVW VIEW
V202_INSERT TRIGGER
V202_DELETE TRIGGER
V202_UPDATE TRIGGER
已选择125行。
SQL> spool off
还是有很多的无效对象，但是对象都是trigger和view，随便找一个view重新编译一下。
SQL> alter view sde.p_evw compile ;
alter view sde.p_evw compile
*
第 1 行出现错误:
ORA-00600: 内部错误代码, 参数: [kkpo_rcinfo_defstg:objnotfound], [96314], [],
[], [], [], [], [], [], [], [], []Oracle的内部错误，查询google发现该错误是11g的defer_segment_creation特性导致的，也旧就是这些视图后面的表都是没有记录的，从输出列表中可以看到很多都是图层的多版本视图以及其上面的trigger是无效的，这些视图都是在使用SQL直接编辑版本数据时候使用的，桌面是不会使用的。因此Desktop连接Geodatabase过程中不会判断这些视图的有效性。
仔细查看列表，竟然发现gdb_items_vw也是无效的，这个视图是可以重建的，那试着重建一下。
SQL> drop view gdb_items_vw;
View dropped
SQL> create or replace view gdb_items_vw as
2 select objectid,uuid,type,name,physicalname,path,url,properties, defaults,datasetsubtype1,datasetsubtype2,datasetinfo1,datasetinfo2, sde.sdexmltotext(d1.xml_doc) as definition, sde.sdexmltotext(d2.xml_doc) as documentation, sde.sdexmltotext(d3.xml_doc) as iteminfo, shape FROM GDB_ITEMS LEFT OUTER JOIN sde_xml_doc1 d1 on gdb_items.definition = d1.sde_xml_id LEFT OUTER JOIN sde_xml_doc2 d2 on gdb_items.documentation = d2.sde_xml_id LEFT OUTER JOIN sde_xml_doc3 d3 on gdb_items.iteminfo = d3.sde_xml_id;
ORA-00600: internal error code, arguments: [kkpo_rcinfo_defstg:objnotfound], [74934], [], [], [], [], [], [], [], [], [], []从整个SQL语句可以看到该视图主要联合了GDB_ITEMS,SDE_XML_DOC1,SDE_XML_DOC2,SDE_XML_DOC3表
我们对这几张表查询，发现
select * from sde_xml_doc3
ORA-00600: internal error code, arguments: [kkpo_rcinfo_defstg:objnotfound], [74934], [], [], [], [], [], [], [], [], [], []
SQL> select count(*) from sde_xml_doc3;
select count(*) from sde_xml_doc3
ORA-00600: internal error code, arguments: [kkpo_rcinfo_defstg:objnotfound], [74934], [], [], [], [], [], [], [], [], [], []果然是sde_xml_doc3这种表出问题了（跟10046 trace的结果一致了，只不过trace没有报ora-00600错误），
由于sde_xml_doc3表中没有记录，因此可以重建，查看别的库上该表的定义并重建之。
SQL> drop table sde_xml_doc3 cascade constraints;
表已删除。
SQL> CREATE TABLE "SDE"."SDE_XML_DOC3"
2 ( "SDE_XML_ID" NUMBER(*,0) NOT NULL ENABLE,
3 "DOC_PROPERTY" NUMBER(*,0),
4 "XML_DOC" BLOB NOT NULL ENABLE,
5 "XML_DOC_VAL" CLOB,
6 CONSTRAINT "XML_DOC3_PK" PRIMARY KEY ("SDE_XML_ID"));
表已创建。
SQL> CREATE INDEX "SDE"."XML_DOC3_IX" ON "SDE"."SDE_XML_DOC3" ("DOC_PROPERTY");
索引已创建。重建后问题Desktop可以正常连接。
扫一扫
3192
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
