SDO_3GL error
Hi,
I'm using Oracle spatial (Oracle Database 10g Release 10.2.0.4.0 - 64bit Production) and GeoServer for a mapping application. GeoServer makes the following request as part of its geom boundary calculations:
select sdo_aggr_mbr(geom) from table;
but it's failing with the error:
ORA-04063: package body "MDSYS.SDO_3GL" has errors
ORA-06508: PL/SQL: could not find program unit being called: "MDSYS.SDO_3GL"
ORA-06512: at "MDSYS.SDO_GEOM", line 3398
ORA-06512: at "MDSYS.SDO_GEOM", line 3507
ORA-06512: at "MDSYS.SDOAGGR", line 41
ORA-06512: at "MDSYS.AGGRMBR", line 14
I get the same error even if I just run the select in an Oracle command window.
Does anyone understand the problem here or know of a fix?
Any help appreciated,
Dave
Did you included the interMedia Component or the Spatial component during the creation of your database? If so, are they valid? Check the results of this query, they should show either SDO/Spatial or ORDIM/interMedia as installed and VALID:
col comp_name format a35
col comp_id format a15
select comp_id, comp_name, status from dba_registry;
COMP_ID COMP_NAME STATUS
APEX Oracle Application Express VALID
CONTEXT Oracle Text VALID
EM Oracle Enterprise Manager VALID
ORDIM Oracle interMedia VALID
XDB Oracle XML Database VALID
EXF Oracle Expression Filter VALID
RUL Oracle Rules Manager VALID
OWM Oracle Workspace Manager VALID
CATALOG Oracle Database Catalog Views VALID
CATPROC Oracle Database Packages and Types VALID
JAVAVM JServer JAVA Virtual Machine VALID
XML Oracle XDK VALID
CATJAVA Oracle Database Java Packages VALID
13 rows selected.
Cheers,
Tino
Similar Messages
-
Validate_layer_with_context error
BEGIN sdo_geom.validate_layer_with_context('COPPER', 'GEOM', 'VAL_RESULTS', 100); END;
ERROR at line 1:
ORA-04030: out of process memory when trying to allocate 16408 bytes (koh-kghu sessi,mdvgrr elmbr)
ORA-06512: at "MDSYS.SDO_3GL", line 439
ORA-06512: at "MDSYS.SDO_GEOM", line 3848
ORA-06512: at line 1
Is this a known bug in Oracle 9.2.0.2? Will I need to got to 9.2.0.3 to get this to work?
R Clement
Alaska DNRHi Richard,
This is reported in bug 2698729, and I don't see any info about it being fixed as of today.
Sorry,
Dan -
ORA-13199 Error on a spatial query
Hi,
I am getting following Error on a spatial query (on version 11.1.0.7)
"ORA-13199: Dimensionalities of geometry (GTYPE 3003) and diminfo (2) do not match.
ORA-06512: at "MDSYS.MD", line 1723
ORA-06512: at "MDSYS.MDERR", line 17
ORA-06512: at "MDSYS.SDO_CS", line 2809
ORA-06512: at "MDSYS.SDO_3GL", line 182 "
The same query used to work fine on 10.2.
My query looks like
Select Sfilt.GEOMETRY FROM
(Select TA.GEOMETRY FROM LANDPLAN.TOPOAREA TA, TEST.PLAN PL
WHERE PL.PLAN_ID = 12345 AND TA.LOC_CODE = 7
AND SDO_FILTER(TA.GEOMETRY,PL.GEOMETRY) = 'TRUE'
) Sfilt
,TEST.PLAN PL2 WHERE
PL2.PLAN_ID = 12345 AND
SDO_RELATE(PL2.GEOMETRY, sfilt.GEOMETRY, 'mask=anyinteract') = 'TRUE';
in the above data TEST.PLAN table is 2D table and LANDPLAN.TOPOAREA is 3D table and both are indexed.
Any help appriciated..Siva,
Thank you for your response. Now I have tried by increasing the DIMINFO (rebuiding the index) to three.
Now it shows below error..
ORA-29902: error in executing ODCIIndexStart() routine
ORA-13243: specified operator is not supported for 3- or higher-dimensional R-tree
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 416
I didn't reason now...for clarity
Can I have 3d layer with 2d index's ?
If Yes, can Spatial query work using these 2d index's against other 2d layer and 3d layers ? -
ORA-21779: duration not active error line 25 of MDSYS.AGGRUNION
I execute the following pl/sql (line 56/57 in
a procedure called RebuildSMZLabels)....
v_query := 'SELECT /*+ INDEX ( A BASE_SMZ_A_SHAPE ) NO_INDEX ( A BASE_SMZ_A_RETIREDATE ) */ MDSYS.SDO_AGGR_UNION(MDSYS.SDOAGGRTYPE(a.s
hape,:1)) FROM &owner.base_smz_a A WHERE MDSYS.SDO_RELATE(a.shape,:2,''mask=ANYINTERACT querytype=window'') = ''TRUE'' and retiredate is
null';
EXECUTE IMMEDIATE v_query INTO v_union_shape USING v_diminfo(1).sdo_tolerance, v_trans_shape ;
And I get...
Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
DECLARE
ERROR at line 1:
ORA-21779: duration not active
ORA-06512: at "MDSYS.AGGRUNION", line 25
ORA-06512: at "MDSYS.AGGRUNION", line 25
ORA-06512: at line 1
ORA-06512: at "MDCADM.REBUILDSMZLABELS", line 57
ORA-06512: at line 5
Got me beat... anyone got any ideas?
Simon Greener
GIS Manager
Forestry TasmaniaDan
I reverted to the old 8i code (with individual
UNIONS) and it still fails:
DECLARE
ERROR at line 1:
ORA-21779: duration not active
ORA-06512: at "MDSYS.SDO_3GL", line 439
ORA-06512: at "MDSYS.SDO_GEOM", line 3096
ORA-06512: at "MDCADM.REBUILDSMZLABELS", line 74
ORA-06512: at line 5
Line 74 is:
v_union_shape := MDSYS.SDO_GEOM.SDO_UNION(v_union_shape,v_diminfo,v_shape,v_diminfo);
Any ideas as I need this to work in 9i ASAP (as it
doesn't work in 8i)?
PS Dan, it is the same database/code problem I sent
to you earlier this year. It is getting to the point
that I am going to have to rebuild all this database
centric code (which is where it needs to be in the
business process) within our GIS (ArcInfo) which is going
to be far more complex and not sustainable in the medium
term.
regards
Simon -
I get this error on this statement:
if SDO_GEOM.RELATE(Pic1,'anyinteract',Pic2,0.0000005)='TRUE'
then
The error i get is the following:
ORA-13050: unable to construct spatial object
ORA-06512: at MDSYS.SDO_3GL
ORA-06512: at MDSYS.MD2
Where can i do?The most likely cause is that an instance of Pic1 or Pic2 is invalid. Run sdo_geom.validate_geometry_with_context() and if any geometries are invalid, fix or delte them.
Jayant -
Any suggestions on what could be going wrong here?
SQL> Select t1.* from t1, t2
2 where (sdo_relate(t1.geoloc, t2.geoloc, 'mask=ANYINTERACT querytype=JOIN') = 'TRUE');
where (sdo_relate(t1.geoloc, t2.geoloc, 'mask=ANYINTERACT querytype=JOIN') = 'TRUE')
ERROR at line 2:
ORA-13285: Geometry coordinate transformation error
ORA-29400: data cartridge error
ORA-22060: argument [2] is an invalid or uninitialized number
ORA-06512: at "MDSYS.SDO_3GL", line 41
ORA-06512: at "MDSYS.MD2", line 722
ORA-06512: at line 1
nullHi,
This is probably related to coordinate systems.
There are two layers specified. One of them probably has
coordinate systems information specified (SDO_SRID), the other
probably doesn't. When using spatial operators Oracle Spatial
implicitly tries to convert the coordinate system of the query
window (the second geometry) to that of the first geometry.
In this case the implicit transformation is failing, hence the
error.
It is not legal in Oracle Spatial to have coordinate system
information specified for one layer and NULL for another
layer.
Hope this helps.
dan -
Get the following error exporting a schema from Oracle XE Universal edition on Windows XP
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
EXP-00056: ORACLE error 932 encountered
ORA-00932: inconsistent datatypes: expected BLOB, CLOB got CHAR
EXP-00000: Export terminated unsuccessfully
Any idea how to remedy this?For the SQL statement I get around 187 rows:
10111 OPERATOR CTXSYS.CONTAINS
10116 INDEXTYPE CTXSYS.CONTEXT
10134 INDEXTYPE CTXSYS.CTXXPATH
10110 PACKAGE CTXSYS.CTX_CONTAINS
10132 PACKAGE CTXSYS.CTX_XPCONTAINS
10083 TYPE BODY CTXSYS.DR$OPTTF_IMPL_T
10007 PACKAGE BODY CTXSYS.DRIACC
10019 PACKAGE BODY CTXSYS.DRIDML
10023 PACKAGE BODY CTXSYS.DRIERR
9941 PACKAGE CTXSYS.DRIPARX
10066 PACKAGE BODY CTXSYS.DRIPARX
10113 PACKAGE CTXSYS.DRISCORE
10055 PACKAGE BODY CTXSYS.DRVDDL
10062 PACKAGE BODY CTXSYS.DRVDML
10073 PACKAGE BODY CTXSYS.DRVPARX
10114 OPERATOR CTXSYS.SCORE
10104 TYPE BODY CTXSYS.TEXTINDEXMETHODS
10133 OPERATOR CTXSYS.XPCONTAINS
9620 PACKAGE BODY DBSNMP.MGMT_BSLN
9611 PACKAGE DBSNMP.MGMT_BSLN_INTERNAL
9613 PACKAGE BODY DBSNMP.MGMT_BSLN_INTERNAL
13497 PACKAGE BODY FLOWS_020100.WWV_FLOW_DATALOAD_XML
13368 PACKAGE BODY FLOWS_020100.WWV_FLOW_ELEMENT
13463 PACKAGE BODY FLOWS_020100.WWV_FLOW_HELP
13395 PACKAGE BODY FLOWS_020100.WWV_FLOW_PLSQL_JOB
13390 PACKAGE BODY FLOWS_020100.WWV_FLOW_PROVISION
13473 PACKAGE BODY FLOWS_020100.WWV_FLOW_SW_SCRIPT
13462 PACKAGE BODY FLOWS_020100.WWV_FLOW_THEME_FILES
13408 PACKAGE BODY FLOWS_020100.WWV_FLOW_UPGRADE_REPORT
13220 PACKAGE FLOWS_020100.WWV_FLOW_WEB_SERVICES
13442 PACKAGE BODY FLOWS_020100.WWV_FLOW_WEB_SERVICES
13398 PACKAGE BODY FLOWS_020100.WWV_FLOW_WIZARD_API
13434 PACKAGE BODY FLOWS_020100.WWV_FLOW_XLIFF
11547 PACKAGE BODY MDSYS.SDO_3GL
11707 TRIGGER MDSYS.SDO_CRS_INSERT_TRIGGER
11433 PACKAGE MDSYS.SDO_CS
11661 PACKAGE BODY MDSYS.SDO_CS
11383 FUNCTION MDSYS.SDO_VERSION
10924 SYNONYM PUBLIC.ABSPATH
11050 SYNONYM PUBLIC.ALL_PATH
11253 SYNONYM PUBLIC.ALL_XML_INDEXES
11246 SYNONYM PUBLIC.ALL_XML_SCHEMAS
10112 SYNONYM PUBLIC.CONTAINS
10934 SYNONYM PUBLIC.CONTENTSCHEMAIS
10117 SYNONYM PUBLIC.CONTEXT
10135 SYNONYM PUBLIC.CTXXPATH
9404 SYNONYM PUBLIC.DBA_HIST_ACTIVE_SESS_HISTORY
9332 SYNONYM PUBLIC.DBA_HIST_DB_CACHE_ADVICE
9288 SYNONYM PUBLIC.DBA_HIST_FILESTATXS
9322 SYNONYM PUBLIC.DBA_HIST_LATCH
9328 SYNONYM PUBLIC.DBA_HIST_LATCH_MISSES_SUMMARY
9372 SYNONYM PUBLIC.DBA_HIST_OSSTAT
9376 SYNONYM PUBLIC.DBA_HIST_PARAMETER
9336 SYNONYM PUBLIC.DBA_HIST_ROWCACHE_SUMMARY
9380 SYNONYM PUBLIC.DBA_HIST_SEG_STAT
9416 SYNONYM PUBLIC.DBA_HIST_SERVICE_STAT
9418 SYNONYM PUBLIC.DBA_HIST_SERVICE_WAIT_CLASS
9340 SYNONYM PUBLIC.DBA_HIST_SGASTAT
9306 SYNONYM PUBLIC.DBA_HIST_SQLBIND
9296 SYNONYM PUBLIC.DBA_HIST_SQLSTAT
9366 SYNONYM PUBLIC.DBA_HIST_SYSSTAT
9312 SYNONYM PUBLIC.DBA_HIST_SYSTEM_EVENT
9368 SYNONYM PUBLIC.DBA_HIST_SYS_TIME_MODEL
9406 SYNONYM PUBLIC.DBA_HIST_TABLESPACE_STAT
9316 SYNONYM PUBLIC.DBA_HIST_WAITSTAT
11251 SYNONYM PUBLIC.DBA_XML_INDEXES
11245 SYNONYM PUBLIC.DBA_XML_SCHEMAS
12128 SYNONYM PUBLIC.DBMS_CLR
10889 SYNONYM PUBLIC.DBMS_XDBUTIL_INT
11048 SYNONYM PUBLIC.DBMS_XDB_VERSION
10849 SYNONYM PUBLIC.DBMS_XMLDOM
10853 SYNONYM PUBLIC.DBMS_XMLPARSER
10819 SYNONYM PUBLIC.DBMS_XMLSCHEMA
10858 SYNONYM PUBLIC.DBMS_XSLPROCESSOR
10923 SYNONYM PUBLIC.DEPTH
10918 SYNONYM PUBLIC.EQUALS_PATH
7334 SYNONYM PUBLIC.OLAPRC_TABLE
7333 SYNONYM PUBLIC.OLAP_TABLE
10922 SYNONYM PUBLIC.PATH
11052 SYNONYM PUBLIC.PATH_VIEW
10928 SYNONYM PUBLIC.RESOURCE_VIEW
10115 SYNONYM PUBLIC.SCORE
11658 SYNONYM PUBLIC.SDO_CS
11385 SYNONYM PUBLIC.SDO_VERSION
10917 SYNONYM PUBLIC.UNDER_PATH
11255 SYNONYM PUBLIC.USER_XML_INDEXES
11249 SYNONYM PUBLIC.USER_XML_SCHEMAS
13295 SYNONYM PUBLIC.WWV_FLOW_WEB_SERVICES
11054 SYNONYM PUBLIC.XDB_PVTRIG_PKG
10930 SYNONYM PUBLIC.XDB_RVTRIG_PKG
10850 SYNONYM PUBLIC.XMLDOM
10854 SYNONYM PUBLIC.XMLPARSER
10859 SYNONYM PUBLIC.XSLPROCESSOR
11252 VIEW SYS.ALL_XML_INDEXES
2218 VIEW SYS.ALL_XML_SCHEMAS
8760 VIEW SYS.AQ$ALERT_QT_R
4786 VIEW SYS.AQ$AQ_SRVNTFN_TABLE
5160 VIEW SYS.AQ$SCHEDULER$_EVENT_QTAB_R
5068 VIEW SYS.AQ$SCHEDULER$_JOBQTAB
5074 VIEW SYS.AQ$SCHEDULER$_JOBQTAB_R
9890 VIEW SYS.AQ$SYS$SERVICE_METRICS_TAB_R
8755 VIEW SYS.AQ$_ALERT_QT_F
8645 VIEW SYS.AQ$_AQ$_MEM_MC_F
4774 VIEW SYS.AQ$_AQ_EVENT_TABLE_F
4787 VIEW SYS.AQ$_AQ_SRVNTFN_TABLE_F
5155 VIEW SYS.AQ$_SCHEDULER$_EVENT_QTAB_F
5069 VIEW SYS.AQ$_SCHEDULER$_JOBQTAB_F
9885 VIEW SYS.AQ$_SYS$SERVICE_METRICS_TAB_F
11250 VIEW SYS.DBA_XML_INDEXES
11244 VIEW SYS.DBA_XML_SCHEMAS
12126 PACKAGE SYS.DBMS_CLR
12127 PACKAGE BODY SYS.DBMS_CLR
13618 TYPE SYS.DBMS_CLRPARAMTABLE
13616 TYPE SYS.DBMS_CLRTYPE
13617 TYPE BODY SYS.DBMS_CLRTYPE
11209 PACKAGE BODY SYS.DBMS_EPG
7328 TYPE SYS.OLAPIMPL_T
7329 TYPE BODY SYS.OLAPIMPL_T
7330 TYPE SYS.OLAPRANCURIMPL_T
7332 FUNCTION SYS.OLAPRC_TABLE
7331 FUNCTION SYS.OLAP_TABLE
10875 PROCEDURE SYS.SET_TABLESPACE
11254 VIEW SYS.USER_XML_INDEXES
11248 VIEW SYS.USER_XML_SCHEMAS
10851 SYNONYM SYS.XMLDOM
10855 SYNONYM SYS.XMLPARSER
10860 SYNONYM SYS.XSLPROCESSOR
4852 VIEW SYSTEM.AQ$_DEF$_AQCALL_F
4863 VIEW SYSTEM.AQ$_DEF$_AQERROR_F
10921 OPERATOR XDB.ABSPATH
11049 OPERATOR XDB.ALL_PATH
10933 FUNCTION XDB.CONTENTSCHEMAIS
11261 PACKAGE BODY XDB.DBMS_XDBT
10833 PACKAGE XDB.DBMS_XDBUTIL_INT
10887 PACKAGE BODY XDB.DBMS_XDBUTIL_INT
10839 PACKAGE BODY XDB.DBMS_XDBZ0
11045 PACKAGE XDB.DBMS_XDB_VERSION
11047 PACKAGE BODY XDB.DBMS_XDB_VERSION
10862 PACKAGE BODY XDB.DBMS_XMLDOM
11272 PACKAGE BODY XDB.DBMS_XMLINDEX
10852 PACKAGE XDB.DBMS_XMLPARSER
10865 PACKAGE BODY XDB.DBMS_XMLPARSER
10816 PACKAGE XDB.DBMS_XMLSCHEMA
10903 PACKAGE BODY XDB.DBMS_XMLSCHEMA
10901 PACKAGE XDB.DBMS_XMLSCHEMA_INT
10902 PACKAGE BODY XDB.DBMS_XMLSCHEMA_INT
10856 PACKAGE XDB.DBMS_XSLPROCESSOR
10868 PACKAGE BODY XDB.DBMS_XSLPROCESSOR
10920 OPERATOR XDB.DEPTH
10916 OPERATOR XDB.EQUALS_PATH
11077 TYPE XDB.FUNCSTATS
11078 TYPE BODY XDB.FUNCSTATS
10919 OPERATOR XDB.PATH
11051 VIEW XDB.PATH_VIEW
10927 VIEW XDB.RESOURCE_VIEW
10915 OPERATOR XDB.UNDER_PATH
10935 FUNCTION XDB.UNDER_PATH_FUNC
10905 PROCEDURE XDB.XDB$PATCHUPSCHEMA
11206 TRIGGER XDB.XDBCONFIG_VALIDATE
10925 INDEXTYPE XDB.XDBHI_IDXTYP
10911 TYPE XDB.XDBHI_IM
10912 TYPE BODY XDB.XDBHI_IM
10831 PACKAGE XDB.XDBPI_FUNCIMPL
10832 PACKAGE BODY XDB.XDBPI_FUNCIMPL
10828 TYPE XDB.XDBPI_IM
10829 TYPE BODY XDB.XDBPI_IM
10914 PACKAGE XDB.XDB_ANCOP
10937 PACKAGE BODY XDB.XDB_ANCOP
10913 PACKAGE XDB.XDB_FUNCIMPL
10932 PACKAGE BODY XDB.XDB_FUNCIMPL
11053 PACKAGE XDB.XDB_PVTRIG_PKG
11055 TRIGGER XDB.XDB_PV_TRIG
10929 PACKAGE XDB.XDB_RVTRIG_PKG
10938 PACKAGE BODY XDB.XDB_RVTRIG_PKG
10931 TRIGGER XDB.XDB_RV_TRIG
11073 INDEXTYPE XDB.XMLINDEX
11062 TYPE XDB.XMLINDEXMETHODS
11063 TYPE BODY XDB.XMLINDEXMETHODS
11070 PACKAGE XDB.XMLINDEX_FUNCIMPL
11071 OPERATOR XDB.XMLINDEX_GETNODES
Cheers.
11072 OPERATOR XDB.XMLINDEX_ISATTRIBUTE -
Sdo_filter error while trying to do results paging
This is a continuation of the problem found at: Re: Problem with SDO_FILTER combined with Timestamp and Order By using JDBC
It seems that the index hint fixed most of the problems where the spatial index wasn't getting used, but it fails in the case when I try to do results paging. It seems as if the order by and sdo_filter cause problems. I've simplified the offending query down to the following below.
select ROWNUM rowcount, a.* from
(select /*+ INDEX (TRACK_SEGMENTS TRACK_SEGMENTS_SPATIAL_IDX) */ * from TRACK_SEGMENTS
where ( ( sdo_filter(GEOM, sdo_geometry(2003, 8307, null, sdo_elem_info_array(1, 1003, 3), sdo_ordinate_array(?, ?, ?, ?) ), 'MASK=ANYINTERACT') = 'TRUE' and
END_DATE >= ? and START_DATE < ?)) and (
(START_DATATYPE = 'maritime_dense'))
ORDER BY ID
) a
I've tried adding a global hint such as INDEX (a.TRACK_SEGMENTS TRACK_SEGMENTS_SPATIAL_IDX) and I've also tried joining the spatial index and the primary key "ID" index. But no matter what I've tried, the spatial index is not used and it results in the following error:
java.sql.SQLException: ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "MDSYS.SDO_3GL", line 1320
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1062)
at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:839)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1132)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3390)
at QueryTester.main(QueryTester.java:61)
As an extra wrinkle, if I take that exact same query and run it from sql developer rather a java class and jdbc, it runs just fine.
Thanks in advance for your help,
Jim1. Oracle optimizer is cost-based, so sometime it may think other non-spatial predicates
are more selective or give more performance.
2. I don't know. Are you sure that it is the same query, and the same-sized table?
Maybe some optimizer parameters are different in the two environments.
3. I think that the real problem is with the order by clause. If the optimizer chooses
a non-spatial index for the order by clause, it may not choose the spatial index.
For other indexes (say a index on START_DATE), you don't have to specify the
NO_INDEX hint.
Another way to avoid specifying the NO_INDEX hint:
select /*+ NO_MERGE(a) */
ROWNUM rowcount, a.* from
(select /*+ INDEX (TRACK_SEGMENTS TRACK_SEGMENTS_SPATIAL_IDX) */ * from TRACK_SEGMENTS
where ( ( sdo_filter(GEOM, sdo_geometry(2003, 8307, null, sdo_elem_info_array(1, 1003, 3), sdo_ordinate_array(?, ?, ?, ?) ), 'MASK=ANYINTERACT') = 'TRUE' and
END_DATE >= ? and START_DATE < ?)) and (
(START_DATATYPE = 'maritime_dense'))) a
ORDER BY a.ID -
Error with : SDO_RELATE(.........) = 'FALSE'
When i use the operator SDO_RELATE and i try to evaluate it with "= 'FALSE'" or with "!= 'TRUE'" instead of "= 'TRUE'", a receive some errors. The same query works fine when i use "= 'TRUE'",
Is it possible to evaluate the SDO_RELATE operator with "= 'FALSE'" or with "!= 'TRUE'" ?
Example with "= 'FALSE'"
SELECT IDE_TEST
FROM TEST
WHERE (sdo_relate (TEST.GEO_TEST, mdsys.sdo_geometry(2003, 1557057, NULL, mdsys.sdo_elem_info_array(1,1003,1), mdsys.sdo_ordinate_array (994431.1035,519763.6176,995340.97698,518071.25296,995944.125,518928.5,994431.1035,519763.6176)),'mask=anyinteract querytype=WINDOW') = 'FALSE');
ERROR at line 1:
ORA-29902: error in executing ODCIIndexStart() routine
ORA-13207: incorrect use of the [SDO_RELATE] operator
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 368
ORA-06512: at line 1
Example with "!= 'TRUE'"
SELECT IDE_TEST
FROM TEST
WHERE (sdo_relate (TEST.GEO_TEST, mdsys.sdo_geometry(2003, 1557057, NULL, mdsys.sdo_elem_info_array(1,1003,1), mdsys.sdo_ordinate_array (994431.1035,519763.6176,995340.97698,518071.25296,995944.125,518928.5,994431.1035,519763.6176)),'mask=anyinteract querytype=WINDOW') != 'TRUE');
ERROR at line 1:
ORA-13268: error obtaining dimension from USER_SDO_GEOM_METADATA
ORA-06512: at "MDSYS.MD", line 1723
ORA-06512: at "MDSYS.MDERR", line 8
ORA-06512: at "MDSYS.SDO_3GL", line 89What you want to do is a little tricky. When you use an operator, the first thing spatial does is use the index to try to narrow the search field to geometries that are likely to interact. If you then use disjoint as a mask, what you will return is all of the geometries that are likely to interact, but don't.
Instead, you might want to try something like this:
select IDE_TEST
FROM TEST
MINUS
SELECT IDE_TEST
FROM TEST
WHERE sdo_relate (TEST.GEO_TEST, mdsys.sdo_geometry(2003, 1557057, NULL, mdsys.sdo_elem_info_array(1,1003,1), mdsys.sdo_ordinate_array (994431.1035,519763.6176,995340.97698,518071.25296,995944.125,518928.5,994431.1035,519763.6176)),'mask=anyinteract querytype=WINDOW') = 'TRUE'); -
Simple geometry gets ORA-29532 error on all SDO_GEOM calls
Hi all,
I have a single point in a table such that the query:
select SDO_GEOM.VALIDATE_GEOMETRY(geomObj, 0.05) from testvalid;
/* Returns */
SDO_GEOM.VALIDATE_GEOMETRY(GEOMOBJ,0.05)
'TRUE'However the query:
select SDO_GEOM.VALIDATE_GEOMETRY_with_context(geomObj, 0.05) from testvalid;Receives the following error:
ORA-29532: Java call terminated by uncaught Java exception: java.lang.NumberFormatException: empty String
ORA-06512: at "MDSYS.SDO_3GL", line 658
ORA-06512: at "MDSYS.SDO_GEOM", line 519
ORA-06512: at "MDSYS.SDO_GEOM", line 558
ORA-06512: at line 1The data itself is a single sdo_point:
select GEOMOBJ from testvalid;
/* Returns: */
GEOMOBJ
'(3001, , (174.092329032787, 129.420551704918, -71.2857142857142), , )'I think that the problem is something to do with the precision of the stored X, Y and Z values in the point because if I run the following:
update TESTVALID set GEOMOBJ.sdo_point.x = cast(GEOMOBJ.sdo_point.x as number(8,3));
select SDO_GEOM.VALIDATE_GEOMETRY_with_context(geomObj, 0.05) from testvalid;
/* Returns: */
SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(GEOMOBJ,0.05)
'TRUE'Similarly, running a direct comparison from an object made on the fly from the point's text representation works fine:
select SDO_GEOM.VALIDATE_GEOMETRY_with_context("MDSYS"."SDO_GEOMETRY"(3001,NULL, "MDSYS"."SDO_POINT_TYPE"(174.092329032787,129.420551704918,-71.2857142857142),NULL,NULL), 0.005) from dual;
/* Returns */
SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT("MDSYS"."SDO_GEOMETRY"(3001,NULL,"MDSYS"."SDO_POINT_TYPE"(174.092329032787,129.420551704918,-71.2857142857142),NULL,NULL),0.005)
'TRUE'Note that I only noticed this problem after upgrading from v11 to v11 R2. Also, the same ORA-29532 error comes up when running any of the SDO_GEOM.[x] function calls such as SDO_GEOM.DISTANCE(). The problem is not limited to SDO_POINT type geometries, yet the problem occurs only on some geometry entries in my database. It is repeatable in that the same geometry will continue to fail and the only solution I've found is to try to round down its precision in x, y, and/or z. I only know how to easily round down the precision for SDO_POINT types, so one of my problems is that I'm left with a whole scattering of other geometries that I can no longer spatially query.
The datas themselves were inserted from MATLAB (which connects using v11 Oracle ODBC Java drivers) which converts my coordinates to java.math.BigDecimal and binds them to an oracle prepared statement.
One possibility that I'm considering is that the insertion is done from various computers, some of which are 64-bit machines. Maybe somehow those machines are pumping in coordinates to a precision too great for oracle geometry?
Any help would be fantastic as I'm pretty lost here.
If the precision is indeed the problem, does anyone know how I can trim off those excess values after the decimal point for all geometry types?
Thanks,
Sven.The problem is with the way the ordiantes are created via java programs pre 11.2.
There was a bit alignment problem in the internal representation of the number when these numbers are created from a java program.
In 11.2 this corruption is fixed, but as a result the data that is already corrupted gives this "empty string" error.
It is very easy to fix. Follow the steps in the script below.
create or replace function id_geom ( g in sdo_geometry)
return sdo_geometry deterministic as
g1 sdo_geometry ;
idx number;
ords sdo_ordinate_array;
x number;
y number;
z number;
point_t sdo_point_type;
begin
if (g.sdo_point is not NULL) then
x := NULL; y := NULL; z := NULL;
if (g.sdo_point.x is not NULL) then
x := g.sdo_point.x * 10;
x := x / 10;
end if;
if (g.sdo_point.y is not NULL) then
y := g.sdo_point.y * 10;
y := y / 10;
end if;
if (g.sdo_point.z is not NULL) then
z := g.sdo_point.z * 10;
z := z / 10;
end if;
point_t := SDO_POINT_TYPE(x,y,z);
else
point_t := NULL;
end if;
if (g.sdo_ordinates is not NULL) then
ords := sdo_ordinate_array();
ords.extend(g.sdo_ordinates.count);
for idx in 1 .. ords.count loop
x := g.sdo_ordinates(idx);
x := (x*10.0);
x := x/10.0;
ords(idx) := x;
end loop;
g1 := sdo_geometry(g.sdo_gtype, g.sdo_srid,point_t,g.sdo_elem_info,ords);
else
g1 := sdo_geometry(g.sdo_gtype, g.sdo_srid,point_t,g.sdo_elem_info, NULL);
end if;
return g1;
end;
And then update the rows with geometry data with SQL like this:
update geom_table set geom = id_geom(geom); -
Error reading User_SDO_Geom_Metadata when validating geometry
Hello,
I am having an error when running SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT on an Oracle 10.2.0.4 DB running on Windows. Below is a code snippet and response with errors. (I think during the investigation of this problem that I saw similar errors when attempting to build a spatial index but not with this example)
There is the correct entry into ALL_SDO_GEOM_METADATA also.
If anyone can offer any suggestions?
Thanks!
CODE
CREATE TABLE "TABLE1"
( "COL" VARCHAR2(20 BYTE),
"GEOM" "MDSYS"."SDO_GEOMETRY"
DELETE FROM USER_SDO_GEOM_METADATA
WHERE TABLE_NAME = 'TABLE1' AND COLUMN_NAME = 'GEOM' ;
INSERT INTO USER_SDO_GEOM_METADATA (TABLE_NAME, COLUMN_NAME, DIMINFO, SRID)
VALUES
('TABLE1', 'GEOM',
MDSYS.SDO_DIM_ARRAY
(MDSYS.SDO_DIM_ELEMENT('X', 100000, 200000, 0.005000000),
MDSYS.SDO_DIM_ELEMENT('Y', 100000, 200000, 0.005000000)
), null
COMMIT;
SELECT * FROM USER_SDO_GEOM_METADATA;
INSERT INTO TABLE1 VALUES('TEST',SDO_GEOMETRY
(2003,null,null,SDO_ELEM_INFO_ARRAY(1, 1003, 1),
SDO_ORDINATE_ARRAY
(180000.00,120000.00,
185000.00,120000.00,
185000.01,125000.00,
180000.00,125000.00,
180000.00,120000.00)));
COMMIT;
CREATE INDEX TABLE1_SX ON TABLE1 ( GEOM ) INDEXTYPE IS MDSYS.SPATIAL_INDEX;
CREATE TABLE VALIDATION_RESULTS (
SDO_ROWID ROWID,
STATUS VARCHAR2(2000)
PROMPT #############################
CALL SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT('TABLE1','GEOM','VALIDATION_RESULTS');
RESULTS
CREATE TABLE succeeded.
0 rows deleted
1 rows inserted
COMMIT succeeded.
TABLE_NAME COLUMN_NAME DIMINFO SRID
TABLE1 GEOM MDSYS.SDO_DIM_ELEMENT(MDSYS.SDO_DIM_ELEMENT(X,100000,200000,0.005),MDSYS.SDO_DIM_ELEMENT(Y,100000,200000,0.005))
1 rows selected
1 rows inserted
COMMIT succeeded.
CREATE INDEX succeeded.
CREATE TABLE succeeded.
Error starting at line 36 in command:
CALL SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT('TABLE1','GEOM','VALIDATION_RESULTS')
Error report:
SQL Error: ORA-13203: failed to read USER_SDO_GEOM_METADATA view
ORA-13205: internal error while parsing spatial parameters
ORA-13249: Stmt-Execute Failure: SELECT DBMS_ASSERT.SCHEMA_NAME( :1 ) FROM DUAL
ORA-29400: data cartridge error
ORA-44001: invalid schema
ORA-06512: at "SYS.DBMS_ASSERT", line 243
ORA-06512: at "MDSYS.SDO_3GL", line 665
ORA-06512: at "MDSYS.SDO_GEOM", line 3770
ORA-06512: at line 1
13203. 00000 - "failed to read USER_SDO_GEOM_METADATA view"
*Cause: An error encountered while trying to read the USER_SDO_GEOM_METADATA
view.
*Action: Check that USER_SDO_GEOM_METADATA has an
entry for the current geometry table.Works for me on Windows XP 11.1.0.7
You should contact Oracle support about this type of error.
SQL> CALL SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT('TABLE1','GEOM','VALIDATION_RESULTS');
Call completed.
SQL> select * from VALIDATION_RESULTS;
SDO_ROWID STATUS
Rows Processed <1>
1 row selected. -
Error ORA-13364: layer... using /*+ ORDERED */
We develop a spatial application using ORACLE 10.1.0.4 Spatial.
While testing the application we found a very strange behavior:
If we use the /*+ ORDERED */ hint we get an error:
ORA-13364: layer dimensionality does not match geometry dimensions
Here is the query and the results:
SQL> set echo on
SQL> set timing on
SQL> -- omitting "+" this is only a comment
SQL> select /* ORDERED */ GEM.PGNAME from
2 bas.pol_gemeinde GEM, wlk.wb_einzugsgebiet_geo GEO
3 where SDO_ANYINTERACT(gem.geometry,geo.geometry)='TRUE'
4 and GEO.objectid=24481 and geo.geometry is not null and
5 gem.geometry is not null;
PGNAME
Innsbruck
Götzens
Mutters
Elapsed: 00:00:00.07
SQL>
SQL> select /*+ ORDERED */ GEM.PGNAME from
2 bas.pol_gemeinde GEM, wlk.wb_einzugsgebiet_geo GEO
3 where SDO_ANYINTERACT(gem.geometry,geo.geometry)='TRUE'
4 and GEO.objectid=24481 and geo.geometry is not null and
5 gem.geometry is not null;
select /*+ ORDERED */ GEM.PGNAME from
ERROR at line 1:
ORA-13364: layer dimensionality does not match geometry dimensions
ORA-06512: at "MDSYS.SDO_3GL", line 4
ORA-06512: at "MDSYS.MD2", line 726
ORA-06512: at "MDSYS.SDO_3GL", line 115
ORA-06512: at "MDSYS.SDO_3GL", line 142
Elapsed: 00:00:00.04
SQL>
SQL> select /*+ ORDERED */ GEM.PGNAME from
2 wlk.wb_einzugsgebiet_geo GEO , bas.pol_gemeinde GEM
3 where SDO_ANYINTERACT(gem.geometry,geo.geometry)='TRUE'
4 and GEO.objectid=24481 and geo.geometry is not null and
5 gem.geometry is not null;
PGNAME
Innsbruck
Götzens
Mutters
Elapsed: 00:00:00.12
SQL>
The geometry-fields of both tables were checked by sdo_geom.validate_geometry_with_context. There were no errors.
We tested these queries with 10.2.0.1 and got no error.Hi,
Some spatial operators have function-based implementations, so if the Oracle optimizer decides not to use the spatial index, the operator can complete successfully using the function-based implementation (which is usually very slow).
In this case, because of the order of the tables in the from clause (reverse of what they should be), you've told Oracle not to use the spatial index, and since there is a function-based implementation, Oracle will use it.
It looks like the function-based implementation won't let you join a 3d geometry with a 2d geometry. -
Internal error for SDO_INTERSECTION
Hi guys,
I wrote a procedure to create intsection line between a polyline table and a polygon table. The SQL statement is like this:
<code>
CREATE TABLE intersect_line_polygon AS
(SELECT B.polygon_id, A.line_id, SDO_GEOM.SDO_INTERSECTION(A.GEOM, B.GEOM, 0.005) AS INTERSECT_LINE
FROM LINE_INVENTORY A, POLYGON_INVENTORY B
WHERE SDO_RELATE(A.GEOM, B.GEOM, 'MASK=ANYINTERACT QUERYTYPE=WINDOW') = 'TRUE' AND A.TYPE IN ('1', '2'));
</code>
The oracle server turned to be very slow and returned the following error.
ORA-13050: unable to construct spatial object
Then I increased the tolerance to 0.5 to make the performance better. The server was still very slow, but returned a different error.
ORA-00600: internal error code, arguments: [kohdtf048], [], [], [], [], [], [],[]
ORA-06512: at "MDSYS.SDO_3GL", line 439
ORA-06512: at "MDSYS.SDO_GEOM", line 3145
ORA-06512: at "MDSYS.SDO_GEOM", line 3194
I don't know what the problem is. I guess there should be some other factors other than tolerance that caused these two errors. I can't increase the tolerance higher further. Can anyone give me a clue how to solve this problem? Thank you!
ChenI've seen the same error in an intersection operation. One of the geometries was invalid. In my case, it was compounded by the fact that the geometry validation routine did NOT detect the fact that the geometry was invalid. There were duplicate vertices that were not detected when the tolerance was 1 meter, but were detected when the tolerance was 100 meters. Strange thing was that the duplicate vertices WERE within 1 meter of each other. Oracle has opened a bug on the issue.
- David -
Hello,
We are using Oracle Spatial and MapGuide.
Since a few days, we are encountered the following errors and we don't know the workflow behind:
An exception occurred in FDO component.
ORA-29925: cannot execute MDSYS.SDO_3GL.RELATE
ORA-21780: Maximum number of object durations exceeded.
An exception occurred in FDO component.
ORA-29900: operator binding does not exist
ORA-21780: Maximum number of object durations exceeded.
Have you already seen this and have you an idea what is the problem?
Thanks in advance.
Damien.I haven't seen that error before. I suspect that MDSYS.SDO_3GL.RELATE is called from SDO_GEOM.RELATE, but I'm not 100% sure. I'm not sure why FDO would be calling SDO_GEOM.RELATE. I'd expect it to use SDO_RELATE, but not SDO_GEOM.RELATE.
Anyway, I'd suggest you trace the FDO session to try to get the exact SQL it is running. Then try to run that in SQL*Plus to reproduce it. If you can reproduce in SQL*Plus and take FDO out of the equation, then you'll have a much better chance of finding the problem.
Run a 10046 level 4 trace to get the bind variables too.
See: http://psoug.org/reference/trace_tkprof.html
Also, ensure the geometries you're querying are valid. Run sdo_geom.validate_geometry_with_context to check that.
The GeoRaptor (http://sourceforge.net/projects/georaptor/) plugin for SQLDeveloper is very useful for validating data. You can validate the data using its interface and then use it to zoom to the the exact point of the error.
John -
I am getting an error on a query retrieving the
SDO_GEOM.SDO_INTERSECTION() which uses SDO_RELATE()
in the WHERE clause.
Any information and/or suggestions would be appreciated.The sdo_version is 9.2.0
I've pasted the part of the .trc file below - including the query. Let me know if you want the binary stack
trace.
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
ORACLE_HOME = /u01/home/oracle/product/9.2.0
System name: SunOS
Node name: atathrd01
Release: 5.9
Version: Generic_112233-07
Machine: sun4u
Instance name: ATATHRD1
Redo thread mounted by this instance: 1
Oracle process number: 13
Unix process pid: 9843, image: oracle@atathrd01 (TNS V1-V3)
*** SESSION ID:(81.7065) 2004-02-04 10:17:07.179
*** 2004-02-04 10:17:07.179
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kohdtf048], [], [], [], [], [], [], []
Current SQL statement for this session:
SELECT m.module, m.minalt, m.maxalt, SDO_GEOM.SDO_INTERSECTION(m.module_geom, :SegmGeom, .5) FROM TEST_GEOM_ADD m WHERE module in ( 'ZME0101M1', 'ZME6701M1' ) AND SDO_RELATE(module_geom, :SegmGeom, 'mask=ANYINTERACT querytype=WINDOW')='TRUE'
----- PL/SQL Call Stack -----
object line object
handle number name
30c17630 439 package body MDSYS.SDO_3GL
3581c720 3144 package body MDSYS.SDO_GEOM
3581c720 3193 package body MDSYS.SDO_GEOM
346b3290 262 anonymous block
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
ksedmp()+248 CALL ksedst()+0 2C7FF4C ? 2C7FF28 ? C ? 0 ?
FFBF4FF4 ? 2C7FC00 ?
kgerinv()+160 PTR_CALL 00000000 3 ? 3 ? 258 ? 2E776C8 ? 0 ?
FFBF567C ?
kgesinv()+20 CALL kgerinv()+0 2F5CE10 ? 30070EC ? 2E776C8 ?
0 ? FFBF567C ? 0 ?
kgesin()+28 CALL kgesinv()+0 2F5CE10 ? 30070EC ? 2E776C8 ?
0 ? FFBF567C ? 96B7EC ?
kohdtf()+164 CALL kgesin()+0 2F5CE10 ? 30070EC ? 2E776C8 ?
0 ? D494D300 ? FF0C65C8 ?
kohbgud()+124 CALL kohdtf()+0 2F5CE10 ? FEB611C8 ?
30289EC ? 1 ? E4 ? 2000 ?
kohbgu()+56 CALL kohbgud()+0 2F5CE10 ? C ? 0 ? C ? 0 ?
2F14280 ?
mdirisct()+176 CALL kohbgu()+0 2F5CE10 ? C ? 0 ? 2 ?
FFBF5A28 ? FFBF5A10 ?
mdorelun()+604 CALL mdirisct()+0 FFBF5A28 ? 2F5CCD4 ?
2FEDF84 ? FFBF5A30 ?
FFBF5958 ? FFBF5A30 ?
mdorel_geom_op()+69 CALL mdorelun()+0 FFBF6C50 ? FFFFFFFF ?
6 FFBF5AB4 ? FFBF78A8 ?
FFBF6BDC ? 251CD80 ?
OCI_geom_op()+100 CALL mdorel_geom_op()+0 FFBF5A30 ? FFBF6CD0 ?
3031574 ? 3031620 ? 3 ?
FFBF6C50 ?
spefcpfa()+560 PTR_CALL 00000000 FFBF78A8 ? 3027B90 ? 0 ?
3031574 ? 3031620 ? 3 ?
spefmccallstd()+916 CALL spefcpfa()+0 FFBF7664 ? B ? 300FCD0 ?
FFBF700C ? FFBF7024 ? 0 ?
peftrusted()+176 CALL pextproc()+0 FFBF78E0 ? FFBF7644 ?
FFBF76D0 ? FFBF7664 ? 0 ? 2 ?
psdexsp()+44 PTR_CALL 00000000 FFBF78E0 ? FFBF73C4 ? 0 ?
3581C720 ? 2 ? 2 ?
rpiswu2()+328 PTR_CALL 00000000 FFBF7564 ? 8B9460 ? 0 ?
30C17630 ? 300FCA4 ?
300FC2C ?
psdextp()+388 CALL rpiswu2()+0 2E30DAB4 ? 48 ? 2E30DAD8 ?
2 ? FFBF7504 ? 48 ?
pefccal()+440 PTR_CALL 00000000 FEA902C4 ? FFBF7644 ?
FFBF76D0 ? 0 ? 20003 ?
FFBF78E0 ?
pefcal()+36 CALL pefccal()+0 0 ? 37F02828 ? FFBF78E0 ? 0 ?
FFBF78E8 ? FFBF78EC ?
pevm_FCAL()+200 CALL pefcal()+0 FFBF78E0 ? 300D87C ?
FEA902C4 ? FFBF78DC ? D83 ?
FFBF7950 ?
pfrrun()+51116 CALL pevm_FCAL()+0 FEA903AC ? 37F02828 ? 78 ?
FFBF7F34 ? 37F01C08 ? 0 ?
peidxr_run()+172 CALL pfrrun()+0 58 ? 0 ? 4 ? 0 ? 53444F5F ?
5354414E ?
peidxexe()+136 CALL peidxr_run()+0 FE9A03D8 ? 1D ? FEB67994 ?
4 ? 8 ? FE9A03F0 ?
kkxdexe()+716 CALL peidxexe()+0 FE9A03D8 ? FEB67838 ?
FF000000 ? FC00 ? 1 ? 1 ?
kkxmpexe()+396 CALL kkxdexe()+0 FE9100C0 ? FEB67838 ?
FE9A0578 ? FE9A030C ? 0 ?
FEB679D8 ?
kgmexwi()+1428 PTR_CALL 00000000 2F5CE10 ? 0 ? 0 ? 0 ? 0 ?
FE9A030C ?
kgmexec()+316 CALL kgmexwi()+0 FE9A030C ? 0 ? 0 ? 0 ? 0 ?
FE7B6248 ?
evapls()+952 CALL kgmexec()+0 1 ? 0 ? 1D ? FFBF91DE ? 0 ?
FE9A0418 ?
evaopn2()+392 PTR_CALL 00000000 FE9A0308 ? 2F5CC00 ?
2F62800 ? 337E3FA8 ? 0 ? 3 ?
opifcr()+1500 CALL evaopn2()+0 337E3FA8 ? FEB5FF9C ? 2 ?
28615DC ? FE920074 ?
285F8D0 ?
qertbFetchByRowID() PTR_CALL 00000000 4000 ? 22181EE7 ? 3009254 ?
+1344 FE920074 ? FFBF9FE8 ? 58 ?
opifch2()+1440 PTR_CALL 00000000 38714094 ? 8C67FC ?
FFBF9FE8 ? 1 ? 0 ? 2F7CF9F8 ?
opifch()+56 CALL opifch2()+0 2F62800 ? 20011800 ?
2000BC00 ? 2000BC00 ?
2000BC00 ? 0 ?
opipls()+5172 CALL opifch()+0 5 ? 2 ? FFBFA2FC ? FEB60014 ?
0 ? 0 ?
opiodr()+1104 PTR_CALL 00000000 2F5CEEC ? 6 ? FFBFB188 ?
FEB5FA3C ? 346B3290 ?
FEB5FA3C ?
rpidrus()+112 CALL opiodr()+0 66 ? 0 ? FFBFB188 ? 8 ?
301A390 ? 10 ?
skgmstack()+152 PTR_CALL 00000000 FFBFAB90 ? 2F5CC58 ? 1 ? 0 ?
0 ? 0 ?
rpidru()+124 CALL skgmstack()+0 FFBFAB74 ? 2F5CC58 ? F618 ?
8B9900 ? FFBFAB90 ? 0 ?
rpiswu2()+328 PTR_CALL 00000000 FFBFB038 ? 8B9460 ? 0 ?
302563C ? 0 ? 28C ?
rpidrv()+1380 CALL rpiswu2()+0 2E30DAB4 ? 48 ? 2E30DAD8 ?
10 ? 300D64C ? 48 ?
psddr0()+124 CALL rpidrv()+0 2E30DAB4 ? 2E30DAD8 ?
2F5CC00 ? 10 ? 2E9CFA4 ?
FFBFB150 ?
psdnal()+176 CALL psddr0()+0 8 ? 66 ? FFBFB188 ? 71 ?
276A800 ? 0 ?
pevm_BFTCHC()+372 PTR_CALL 00000000 FFBFC650 ? FFBFC71C ?
2F63480 ? FEB5FA3C ?
346B3290 ? 346B3290 ?
pfrrun()+11304 CALL pevm_BFTCHC()+0 FEB6F19C ? 301A534 ? 0 ?
301A100 ? 301A390 ? 10 ?
peicnt()+232 CALL pfrrun()+0 48 ? 0 ? 372C9874 ? 0 ? 0 ?
0 ?
kkxexe()+524 CALL peicnt()+0 FFBFC650 ? FEB6F19C ?
372C9874 ? 0 ? 0 ? 0 ?
opiexe()+7460 CALL kkxexe()+0 FEB6D068 ? FFBFCD28 ?
2F62800 ? 2 ? 0 ? 0 ?
opiall0()+1180 CALL opiexe()+0 0 ? 0 ? 0 ? 2F5E800 ?
FFBFCD28 ? 2F5CC00 ?
kpoal8()+1004 CALL opiall0()+0 5E ? 22 ? FFBFD2E0 ? 0 ?
FFBFD290 ? 2FEA45C ?
opiodr()+1104 PTR_CALL 00000000 0 ? 135CD0 ? 40000 ? 1 ? 0 ?
0 ?
ttcpip()+900 PTR_CALL 00000000 5E ? 0 ? FFBFEFE0 ? 0 ? 4 ?
0 ?
opitsk()+768 CALL ttcpip()+0 FFBFE5BC ? 0 ? 2FB7D78 ?
184D0 ? 18400 ? 2F426C8 ?
opiino()+1328 CALL opitsk()+0 0 ? 0 ? 0 ? 0 ? 0 ? FF0000 ?
opiodr()+1104 PTR_CALL 00000000 3C ? 4 ? FFBFF7EC ? 0 ? 0 ?
0 ?
opidrv()+492 CALL opiodr()+0 3C ? 0 ? FFBFF7EC ? 0 ? 0 ?
0 ?
sou2o()+16 CALL opidrv()+0 3C ? 4 ? FFBFF7EC ?
2F6C6F67 ? FFBFF9C7 ? 0 ?
main()+236 CALL sou2o()+0 FFBFF7FC ? 3C ? 4 ?
FFBFF7EC ? 2FE89E8 ?
29F6C00 ?
_start()+264 CALL main()+0 2 ? FFBFF8C4 ? FFBFF8D0 ?
2F5CC00 ? 0 ? 0 ?
Maybe you are looking for
-
Does anyone know if it is possible to connect a laptop through the Mobile Hotspot application using the USB cable instead of WiFi - I have a very old laptop that I would like to occassionally use but it does not have WiFi capabilities.
-
PDF and MSWord links don't work once published
Help, I have created a four module course and published it using aggregate, it looks great except none of the links to the pdf or msword docs work. I have tried several suggestions, but nothing works when the course is launched on another computer.
-
My iphone 4S wont stop "talking." everthing i touch is repeated back to me. How can I fix?
My iphone 4S won't stop "talking" to me. Everytime I press something the SIRI voice repeats the action I just took. When I go to access something, I have to press 2x. I think something got inadvertently changed in settings. To me, what's going on
-
Adobe was working and then stopped.
I wanted to watch something on CBS.com (The big brother live feeds). I watch it fine for 2 days and on the 3rd day it worked fine. I paused the player and 15 mins went back and it said I needed to update flash to adobe 10. But the thing is, I was
-
Keep getting ".kext" errors during software installation or updates
This has been going on for a while now, though presently I am finally getting a pattern in terms of incedent times. Previosly, I was getting ".kext" error messages all the time. Then I tried re-installing Snow Leopard and that redueced the number of