SDO_AGGR_UNION function reverses linestrings !?

Hi,
When I use the SDO_AGGR_UNION function, the geometry objects (linestrings) get reversed
by changing the order of the vertex
Here's a SQL sample code that illustrates this issue :
Code :
DROP TABLE tmp;
commit;
CREATE TABLE tmp
("ID" NUMBER,
"GEOM" SDO_GEOMETRY);
commit;
INSERT INTO TMP VALUES (
1,
SDO_GEOMETRY(2002, NULL, NULL, sdo_elem_info_array (1,2,1), SDO_ORDINATE_ARRAY(1,1, 2,2))
commit;
INSERT INTO TMP VALUES (
1,
SDO_GEOMETRY(2002, NULL, NULL, sdo_elem_info_array (1,2,1), SDO_ORDINATE_ARRAY(1,1, 2,2))
commit;
INSERT INTO TMP VALUES (
2,
SDO_GEOMETRY(2002, NULL, NULL, sdo_elem_info_array (1,2,1), SDO_ORDINATE_ARRAY(2,2, 1,1))
commit;
INSERT INTO TMP VALUES (
2,
SDO_GEOMETRY(2002, NULL, NULL, sdo_elem_info_array (1,2,1), SDO_ORDINATE_ARRAY(2,2, 1,1))
commit;
SELECT id, SDO_AGGR_UNION(SDOAGGRTYPE(a.geom,0.005))
FROM tmp a
GROUP BY id;
Output :
ID SDO_AGGR_UNION(SDOAGGRTYPE(A.GEOM,0.005))
1 MDSYS.SDO_GEOMETRY(2002,NULL,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,2,1),MDSYS.SDO_ORDINATE_ARRAY(1,1,2,2))
2 MDSYS.SDO_GEOMETRY(2002,NULL,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,2,1),MDSYS.SDO_ORDINATE_ARRAY(1,1,2,2))
1 SDO_ORDINATE_ARRAY(1,1,2,2)
2 SDO_ORDINATE_ARRAY(1,1,2,2)
The linear geometry from record 2 got reversed by the SDO_AGGR_UNION function but not the one from record 1.
Is this a normal feature ? Is there a workaround ?
Thanks for your help

update :
if a SRId is provided (8307 for instance), the geometries get reversed but in another order !
drop table tmp;
commit;
create table tmp
("ID" NUMBER,
"GEOM" SDO_GEOMETRY);
commit;
INSERT INTO TMP VALUES (
1,
SDO_GEOMETRY(2002, 8307, null, sdo_elem_info_array (1,2,1), SDO_ORDINATE_ARRAY(1,1, 2,2))
commit;
INSERT INTO TMP VALUES (
1,
SDO_GEOMETRY(2002, 8307, null, sdo_elem_info_array (1,2,1), SDO_ORDINATE_ARRAY(1,1, 2,2))
commit;
INSERT INTO TMP VALUES (
2,
SDO_GEOMETRY(2002, 8307, null, sdo_elem_info_array (1,2,1), SDO_ORDINATE_ARRAY(2,2, 1,1))
commit;
INSERT INTO TMP VALUES (
2,
SDO_GEOMETRY(2002, 8307, null, sdo_elem_info_array (1,2,1), SDO_ORDINATE_ARRAY(2,2, 1,1))
commit;
select id, SDO_AGGR_UNION(SDOAGGRTYPE(a.geom,0.005))
from tmp a
group by id;
ID SDO_AGGR_UNION(SDOAGGRTYPE(A.GEOM,0.005))
1 MDSYS.SDO_GEOMETRY(2002,8307,null,MDSYS.SDO_ELEM_INFO_ARRAY(1,2,1),MDSYS.SDO_ORDINATE_ARRAY(2,2,1,1))
2 MDSYS.SDO_GEOMETRY(2002,8307,null,MDSYS.SDO_ELEM_INFO_ARRAY(1,2,1),MDSYS.SDO_ORDINATE_ARRAY(2,2,1,1))
funny isn't it ?

Similar Messages

Keyword Lock function reversed

Not sure if I already posted this here or not, but I have sent a feedback for it.
Has anyone else noticed if the lock icon in the keyword panel works back to front (i.e. displays as locked, but is in fact unlocked, and vice versa).
I have also noticed that this can be random, as sometimes I display it, and find it's working the right way round.
Cheers.

Mine works (in both window and full-screen modes). The symbol on the button shows the current status. Clicking the bottom toggles the locked/unlocked status.

Reversing a document using the bapi 'BAPI_ACC_DOCUMENT_REV_POST'

Hi All,
I have posted a document using the FM 'BAPI_ACC_DOCUMENT_POST' and it is working fine .
How can I reverse the same posted document using the FM
'BAPI_ACC_DOCUMENT_REV_POST'?
What are the mandatory parameters to be filled?
Can anyone explain me with a example
Thanks in Advance.

Hi Siva,
The bapi you have mentioned is the correct one.
Look at the BAPI documentation which is pretty informative.
In case you don't have it, i'm just copy pasting it.
Functionality
Reversing an external document in Accounting. (negative posting)
The method "Reverse" can be used to reverse the relevant document in the accounting components.
Parameters
REVERSAL
Reference information for reversal in Accounting
Description
Parameter for transferring a reversal document. The reversal document for the source document is not transferred - the reversal documents are generated in the individual components from the documents to be reversed. This is only possible however, if the corresponding documents are available, meaning that line item update is active in all components and no documents have been archived. If this is not the case, an appropriate error message is issued in the return parameter. If this happens, the document can only be reset by means of a corresponding inverse posting by the sender.
You must make entries in the following fields
Reversal document number:
OBJ_TYPE     Sender ID
OBJ_KEY     Reference number of the reversal document (source document)
OBJ_SYS     Logical system
OBJ_KEY_R     Reference number of the document to be reversed.
Default
All other fields are transferred from the FI document to be reversed.
BUS_ACT
Business Transaction
Description
To reverse the document, the same business transaction must be entered that was used for the posting.
OBJ_TYPE
Reference procedure
Source document
Description
When a business transaction is updated in Accounting, it may be that several documents are updated at the same time (FI document, CO document, etc). If the business transaction is not initiated in Accounting, a source document must exist outside Accounting. The information from this document must be transferred when the FI/CO interface is called up. The source information is updated in all accounting documents, and is made up of the following fields:
AWTYP (OBJ_TYPE) Reference transaction
Sender ID
AWKEY (OBJ_KEY) Reference key
Source document number
The reference key is made up of:
AWREF Reference document number (10 digits)
Source document number
AWORG Reference organizational unit (10 digits)
Number range ID (if required)
AWSYS (OBJ_SYS) Logical system
Logical system of source document
When the document is being processed, the system checks whether a reference document number (first part of the reference key) has been transferred.
Notes
Use a separate value in the OBJ_TYPE field (reference transaction). You must maintain an entry for this value in table TTYP, which could be a function module that is called when the user wants to branch back to the source/sender document from an accounting document. This makes it possible for documents updated using BAPIs to be included in the document navigation (revision). If you use SAP defined characters in the field OBJ_TYPE, errors can occur in the navigation.
The FI and CO line item suppression is defined separately for each reference transaction.
It is not necessary to separate the reference key into reference document number and reference organizational unit. This means that reference document numbers that are longer than 10 digits can be transferred into the reference key.
OBJ_KEY
Reference Key
Source document
Description
When a business transaction is updated in Accounting, it may be that several documents are updated at the same time (FI document, CO document, etc). If the business transaction is not initiated in Accounting, a source document must exist outside Accounting. The information from this document must be transferred when the FI/CO interface is called up. The source information is updated in all accounting documents, and is made up of the following fields:
OBJ_SYS
Logical system of source document
Source document
Description
When a business transaction is updated in Accounting, it may be that several documents are updated at the same time (FI document, CO document, etc). If the business transaction is not initiated in Accounting, a source document must exist outside Accounting. The information from this document must be transferred when the FI/CO interface is called up. The source information is updated in all accounting documents, and is made up of the following fields:
AWTYP (OBJ_TYPE) Reference transaction
RETURN
Return Parameter
Description
This table contains the return messages from the method call.
Value range
The first message contains the general status of processing:
Type ID Number Message
S RW 605 Document posted successfully
S RW 614 Document check without errors
A RW 609 Error in document
The fields MESSAGE_V1, MESSAGE_V2 and MESSAGE_V3 contain the following information:
Reference transaction ( OBJ_TYPE)
Reference key ( OBJ_KEY)
Logical system of source document ( OBJ_SYS)
Additional messages are transferred with the following information:
Parameter ( PARAMETER)
Row ( ROW)
Field ( FIELD)
in which the error occurred.
REgards.
Ravi

A problem about SDO_AGGR_UNION

I have a problem with the SDO_AGGR_UNION function.
In the first step, I calculate the areas of the intersection between each polygon in dataset aus_veg_test A and the polygon 8 in dataset LAND_USE_DSE_TEST B. As the result shown below, some of the polygons in dataset A do intersect with polygon 8 in dataset B, such as 12, 13, 14, etc.
In step 2, all the polygons in dataset A are aggregated into a single polygon 100 by SDO_AGGR_UNION function.
In step 3, the area of the intersection between 100 (in table TEST_100) and 8 (dataset B) is calculated. But the result is 0.
It seems to be a contradiction. Do you have some ideas about this? Thank you!
-- STEP 1;
SQL> SELECT a.gid, b.gid, SDO_GEOM.SDO_AREA(SDO_GEOM.SDO_INTERSECTION(a.geometry, b.geometry, 0.000000005), 0.000000005) AREA
2 FROM aus_veg_test a, LAND_USE_DSE_TEST b
3 WHERE B.GID = 8;
GID GID AREA
1 8
2 8
3 8
4 8
5 8
6 8
7 8
8 8
9 8
10 8
11 8
GID GID AREA
12 8 2.1580E-07
13 8 8.2592E-07
14 8 .00012801
15 8
16 8
17 8
18 8
19 8
20 8 .000042058
21 8
22 8
GID GID AREA
23 8
24 8
25 8
26 8
27 8
28 8
29 8
30 8
31 8
32 8
33 8 .000027234
GID GID AREA
34 8 0
34 rows selected.
-- STEP 2;
SQL> CREATE TABLE TEST_100 AS
2 SELECT 100 GRIDCODE, SDO_AGGR_UNION(MDSYS.SDOAGGRTYPE(GEOMETRY,0.0000005)) GEOMETRY
3 FROM (SELECT 100 GRIDCODE, GEOMETRY FROM aus_veg_test) GROUP BY GRIDCODE;
Table created.
-- STEP 3;
SQL> SELECT A.GRIDCODE, B.GID, SDO_GEOM.SDO_AREA(SDO_GEOM.SDO_INTERSECTION(A.geometry, B.geometry, 0.000000005), 0.000000005) AREA
2 FROM TEST_100 A, LAND_USE_DSE_TEST B
3 WHERE B.GID = 8;
GRIDCODE GID AREA
100 8 0

I have the same problem with sdo_aggr_concat_line function
create table uma_1(id number, geom mdsys.sdo_geometry);
alter table uma_1 parallel;
insert into uma_1
values (1,SDO_GEOMETRY(2002,null,null,SDO_ELEM_INFO_ARRAY(1,2,1),SDO_ORDINATE_ARRAY(50,0,60,0)));
insert into uma_1
values
(2,SDO_GEOMETRY(2002,null,null,SDO_ELEM_INFO_ARRAY(1,2,1),SDO_ORDINATE_ARRAY(20,0,30,0)));
commit;
SELECT SDO_AGGR_CONCAT_LINES(a.geom) FROM uma_1 a;
:Returns no value or Oracle Error
ORA-29400: data cartridge error
ORA-00600: internal error code, arguments: [kohfrm771], [], [], [], [], [], [],[]
alter table uma_1 noparallel;
:Returns valid Line
I wondering if you answer or replay on your problem?

SDO_AGGR_UNION very slow

Hello friends,
I'm having problems with SDO_AGGR_UNION function in Oracle 11.2.0.3. The performance is very bad.
I need to aggregate several polygons (645) using SDO_AGGR_UNION.
My table is:
SQL> DESC GC_MUNICIPALITY;
Nome Nulo Tipo
STATE_ID NOT NULL NUMBER(5)
GEOLOC SDO_GEOMETRY()
First I ran the following query:
SELECT SDO_AGGR_UNION(SDOAGGRTYPE(geoloc, 0.5)) geoloc
FROM GC_MUNICIPALITY
WHERE STATE_ID = 35
Execution time: 57 minutes
Then, I ran then aggregate union with groupings:
SELECT SDO_AGGR_UNION(SDOAGGRTYPE(geoloc,0.5)) geoloc
FROM
(SELECT SDO_AGGR_UNION(SDOAGGRTYPE(geoloc,0.5)) geoloc
FROM
(SELECT SDO_AGGR_UNION(SDOAGGRTYPE(geoloc,0.5)) geoloc
FROM
(SELECT SDO_AGGR_UNION(SDOAGGRTYPE(geoloc, 0.5)) geoloc
FROM GC_MUNICIPALITY
WHERE STATE_ID = 35
GROUP BY MOD(ROWNUM, 15))
GROUP BY MOD (ROWNUM, 7))
GROUP BY MOD (ROWNUM, 2)
Execution time: 15 minutes
The second execution was faster than the first, but still very slow.
If I use ArcGis, PostGis or JTS, the same aggregation is executed in few seconds.
Why is this function so slow in Oracle?
Is there another way to accomplish this aggregation with better performance?
I read in another forum that if I convert from SDO_GEOMETRY to SDO_TOPO_GEOMETRY the aggregation is faster. However, the SDO_AGGR_UNION works only with SDO_GEOMETRY type. Is there any way to aggregate SDO_TOPO_GEOMETRY?
Thanks!
Edited by: user12000327 on 03/04/2012 09:30
Edited by: user12000327 on 03/04/2012 09:33

Siva,
This group by won't work as you hit that internal limit in the server.Patently! I provided this example because this is what people want in an aggregate and it is the way most people think of it.
So try the other approach described in the user guide using a function that creates a geometry array and passes it to the union function.OK, two more assertions:
1. Working with users over the years I have discovered they can use SQL reasonably well but I am surprised how many simply don't want to go down a PL/SQL function route!
2.The example given is very opaque as to how to do a SELECT ... GROUP BY aggregation using sdo_aggr_set_union.
Personally, I would prefer to expose the grouping value....
CREATE OR REPLACE FUNCTION Set_Geometry(p_value in varchar2)
RETURN SDO_GEOMETRY_ARRAY
deterministic
AS
c_query   SYS_REFCURSOR;
v_g       sdo_geometry;
v_GeomArr sdo_geometry_array;
BEGIN
v_GeomArr := SDO_GEOMETRY_ARRAY();
OPEN c_query FOR 'select a.geometry from admin a where a.blockcode = :1'
             USING p_value;
   LOOP
    FETCH c_query into v_g;
     EXIT when c_query%NOTFOUND ;
     v_GeomArr.extend;
     v_GeomArr(v_GeomArr.count) := v_g;
   END LOOP;
   RETURN v_GeomArr;
END;
-- Which is called like so:
select a.group_code, count(*) as aggrCount, sdo_aggr_set_union(set_geometry(a.group_code),0.005) as geoms
from admin a
where a.hierarchy_code = 'WA'
group by a.group_code;But this is quite inflexible because it really isn't a generic function but rather a function for a specific piece of SQL.
Because of this I prefer something more generic:
CREATE OR REPLACE FUNCTION Set_Geometry(p_cursor in SYS_REFCURSOR)
RETURN SDO_GEOMETRY_ARRAY
DETERMINISTIC
AS
   v_geom    sdo_geometry;
   v_GeomArr sdo_geometry_array;
BEGIN
   v_GeomArr := SDO_GEOMETRY_ARRAY();
   LOOP
    FETCH p_cursor INTO v_geom;
     EXIT when p_cursor%NOTFOUND ;
     v_GeomArr.extend;
     v_GeomArr(v_GeomArr.count) := v_geom;
   END LOOP;
   RETURN v_GeomArr;
END;
-- Results
FUNCTION Set_Geometry compiled
-- Now here's how to use it in a SELECT .... GROUP BY ...
select group_code,
       count(*) as aggrCount,
       sdo_aggr_set_union(set_geometry(CURSOR(SELECT b.geometry FROM test_table b WHERE b.group_code= a.group_code)),0.005) as geoms
from test_table a
where a.hierarchy_code = 'WA'
group by a.group_code;Now I agree SDO_AGGR_SET_UNION is much faster and, with my function, more flexible but it is still ugly.
I am not an expert on this issue of that system limit of 30k sort area. When we talk to internal groups about it, they always
ask us to show the customer filed ER. So it will really help if customers like you file an official ER for this.Surely someone in the spatial team is an expert!
I can't file an ER because my Oracle use is under an OTN license for development purposes. I have asked complaining customers to do so over the years but for some reason they don't so I am left to make a fool of myself on their behalf.
Having said that, the main problem with this approach is still the multiple copies of the data which tends to take up
most of the time. So we are coming up with a better way to call sdo_aggr_set_union that avoid this multiple copies of the data.In your UC presentation? It is good for the public to know that the OS team is always trying to make things better and faster.
regards
Simon

How to reverse the cash journal posted entries in FBCJ

Hi All
In Cash journal (FBCJ) user has posted the document by mistakenly two times, is it possible to reverse the cash journal posted document. Please advise how to reverse the posted cash journal entries.
Regards
K.Gunasekar

Hi,
For reversing, select the line and then go to "Edit > Delete Entry (Shift+F2)" or "Delete Row" button at the bottom part of screen. (Deletion function reverse the document in FBCJ)
However in case you are trying to reverse the entry after printing a receipt if you must implement OSS Note 359656 first:-
[https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=359656]
Regards,
Gaurav

SDO_AGGR_UNION crashes the session

Hi!
I am developing a PL/SQL overlay module to overlay two polygon layers (+ some additional logic). I also use SDO_AGGR_UNION function, which aggregates polygons previously created by SDO_INTERSECTION function.
At this point session crashes with "end-of-file on communication chanel". When debugging, I realised, that SDO_INTERSECTION produced invalid polygon from valid input polygons. In some case,s playing with tolerances, helps that crash does not occur. But produces crashes at other cases.
I have Oracle Database 10g Enterprise Edition Release 10.1.0.4.0.
Any idea, what is wrong or how to handle "end-of-file on communication chanel" as exception?
Regards, Saso

Saso,
I'd bet real money that this is related to the issue we've been having, and working with Oracle to resolve, on SDO_UNION:
SDO_UNION EOF on communications channel
No, you cannot do anything to trap this problem in the database as the database session has crashed (core dumped).
Bryan

Reverse Cobol Copy Book - default directory

Hi,
We use the functionality "Reverse COBOL Copy Book" quite often to import metadata for flat files.
When you have to select the .cbb file the default path to select the file is c:
Is there a possibility to set the default path to any other directory (where for instance all .cbb files are stored)?
Thanks in advance!
Best regards,
H.

Hi H,
Yeah its possible to set for a directory and even for folder also.Follow these steps:
1.In topology manager under file technology duplicate any dataserver which is working eg: FILE_GENERIC.
2.Change the name of the dataserver,and apply changes.i.e click on yes..
3.Under physical schema fill the directory(Schema) as ur wish for default directory.
Eg: for directory c:/
If u need folder then c:/TEMP
4.copy same path for work schema
5.provide appropriate context
6.Now reverse from model it will point to default path which u have menttiioned in topology
Thanks,
katukota

Workspace Reverse Proxy

Hello all,
I am not sure if this is the correct location for this but will give it a try.
Last week my organization setup a reverse proxy to our internal workspace so our external users would be able to login and use LC. The proxy gets external users to the login screen but after typing in the username/password and clicking login we get the spinning circle for about three seconds and then an error message that reads "An error occurred while initializing Workspace.".
Any ideas on why this is happening or if you have a functioning reverse proxy did you have to do anything special on the LC install?
Thanks,
~Josh

I am not the one that setup the reverse proxy so I will have someone look into the logs for me.
I read your first blog entry you posted and noticed something in the server.xml that I am missing.
proxyName="apache.company.com" proxyPort="80"
Not having this line in the server.xml file could that be the possible explaination? Also, if I add this file will I only be able to use the proxy address or will the internal url still work?
~Josh

Reverse Track

I am trying to reverse a guitar solo track. The manual indicates either Functions>Reverse or, Shift-Control-R. Seems simple however; do I select the track first and then press Shift-Control-R? Also, silly question but where is Functions located?

Select your guitar solo region and open the Sample Editor. When in the Sample Editor hit Command+A to select the entire region, then ControlShiftR and click "process" in the pop-up window to reverse your solo. Another way to do it is to go to "Functions" in the Sample Editor menu bar and select "reverse" in the drop-down menu.
I guess you just found out on your own.
Message was edited by: Guitartist

Rebuilding spatial indexing fail after patch 9.2.0.8.0

Hi!
I did apply patchset, and after i did try to
set NLS_LANG=American_America.CL8MSWIN1251
sqlplusw ......
SQL> alter index XXXX.YYYYYYYY_g_idx rebuild; -- <- Russian name
alter index XXXX.YYYYYYYY_g_idx rebuild
ERROR at line 1:
ORA-29858: error occurred in the execution of ODCIINDEXALTER routine
ORA-29400: data cartridge error
¡a¤
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13205: internal error while parsing spatial parameters
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 259
ORA-06512: at line 1
As you can see, rebuilding was failed.
Before upgrade all did work fine.
If i will create table WITH_ENGLISH_NAME as SELECT from my table all working fine ;(
I DID apply all *.sql from patchset.
Any idea, gurus ?
P.S.
I did use script from metalink
verify_spatial_installation.sql :
SQL>
SQL> prompt Verify version and status
Verify version and status
SQL> select COMP_NAME, SCHEMA, VERSION, STATUS
2 from dba_registry where comp_id='SDO';
COMP_NAME SCHEMA VERSION STATUS
Spatial MDSYS 9.2.0.8.0 VALID
SQL>
SQL> prompt Number of objects
Number of objects
SQL> select count(*)
2 from dba_objects where owner='MDSYS';
COUNT(*)
250
SQL>
SQL> prompt Summary count of objects
Summary count of objects
SQL> select object_type, count(*)
2 from dba_objects where owner='MDSYS'
3 group by object_type;
OBJECT_TYPE COUNT(*)
FUNCTION 47
INDEX 17
INDEXTYPE 2
LIBRARY 12
LOB 12
OPERATOR 14
PACKAGE 25
PACKAGE BODY 25
SEQUENCE 2
TABLE 18
TRIGGER 7
TYPE 34
TYPE BODY 10
VIEW 25
14 rows selected.
SQL>
SQL> prompt Any invalid objects ?
Any invalid objects ?
SQL> select object_name, object_type, status
2 from dba_objects
3 where owner='MDSYS'
4 and status <> 'VALID'
5 order by object_name;
OBJECT_NAME OBJECT_TYPE STATUS
SDO_MIGRATE PACKAGE BODY INVALID
SQL>
SQL> prompt List of all spatial objects ordered by object_name
List of all spatial objects ordered by object_name
SQL> select object_name, object_type, status
2 from dba_objects where owner='MDSYS'
3 order by object_name;
OBJECT_NAME OBJECT_TYPE STATUS
AGGRCENTROID TYPE VALID
AGGRCENTROID TYPE BODY VALID
AGGRCONVEXHULL TYPE VALID
AGGRCONVEXHULL TYPE BODY VALID
AGGRLRSCONCAT TYPE VALID
AGGRLRSCONCAT TYPE BODY VALID
AGGRLRSCONCAT3D TYPE VALID
AGGRLRSCONCAT3D TYPE BODY VALID
AGGRMBR TYPE VALID
AGGRMBR TYPE BODY VALID
AGGRUNION TYPE VALID
AGGRUNION TYPE BODY VALID
ALL_GEOMETRY_COLUMNS VIEW VALID
ALL_SDO_GEOM_METADATA VIEW VALID
ALL_SDO_INDEX_INFO VIEW VALID
ALL_SDO_INDEX_METADATA VIEW VALID
ALL_SDO_LRS_METADATA VIEW VALID
ALL_SDO_MAPS VIEW VALID
ALL_SDO_STYLES VIEW VALID
ALL_SDO_THEMES VIEW VALID
CS_SRS TABLE VALID
DBA_GEOMETRY_COLUMNS VIEW VALID
DBA_SDO_INDEX_INFO VIEW VALID
DBA_SDO_INDEX_METADATA VIEW VALID
DBA_SDO_LRS_METADATA VIEW VALID
DBA_SDO_MAPS VIEW VALID
DBA_SDO_STYLES VIEW VALID
DBA_SDO_THEMES VIEW VALID
F81_INDEX_OBJECT TYPE VALID
F81_INDEX_OBJ_ARRAY TYPE VALID
F81_NT_IND_TYPE TYPE VALID
GEOCODER_HTTP PACKAGE VALID
GEOCODER_HTTP PACKAGE BODY VALID
GEOCODE_RESULT TYPE VALID
GEODETIC_SRIDS VIEW VALID
H81_INDEX_OBJECT TYPE VALID
H81_INDEX_OBJ_ARRAY TYPE VALID
H81_NT_IND_TYPE TYPE VALID
HHAND FUNCTION VALID
HHBYTELEN FUNCTION VALID
HHCBIT FUNCTION VALID
HHCELLBNDRY FUNCTION VALID
HHCELLSIZE FUNCTION VALID
HHCLDATE FUNCTION VALID
HHCOLLAPSE FUNCTION VALID
HHCOMMONCODE FUNCTION VALID
HHCOMPARE FUNCTION VALID
HHCOMPOSE FUNCTION VALID
HHDECODE FUNCTION VALID
HHDISTANCE FUNCTION VALID
HHENCODE FUNCTION VALID
HHENCODE_BYLEVEL FUNCTION VALID
HHGBIT FUNCTION VALID
HHGETCID FUNCTION VALID
HHGROUP FUNCTION VALID
HHGTBIT FUNCTION VALID
HHGTYPE FUNCTION VALID
HHIDLPART FUNCTION VALID
HHIDPART FUNCTION VALID
HHINCRLEV FUNCTION VALID
HHJLDATE FUNCTION VALID
HHLENGTH FUNCTION VALID
HHLEVELS FUNCTION VALID
HHMATCH FUNCTION VALID
HHMAXCODE FUNCTION VALID
HHNCOMPARE FUNCTION VALID
HHNDIM FUNCTION VALID
HHOR FUNCTION VALID
HHORDER FUNCTION VALID
HHPRECISION FUNCTION VALID
HHSBIT FUNCTION VALID
HHSETCID FUNCTION VALID
HHSTBIT FUNCTION VALID
HHSTYPE FUNCTION VALID
HHSUBDIVIDE FUNCTION VALID
HHSUBSTR FUNCTION VALID
HHXOR FUNCTION VALID
LOCATOR_WITHIN_DISTANCE OPERATOR VALID
MD PACKAGE VALID
MD PACKAGE BODY VALID
MD$RELATE TABLE VALID
MD1 PACKAGE VALID
MD1 PACKAGE BODY VALID
MD2 PACKAGE VALID
MD2 PACKAGE BODY VALID
MDERR PACKAGE VALID
MDERR PACKAGE BODY VALID
MDPRVT_IDX PACKAGE VALID
MDPRVT_IDX PACKAGE BODY VALID
MD_LRS PACKAGE VALID
MD_LRS PACKAGE BODY VALID
OGIS_GEOMETRY_COLUMNS TABLE VALID
OGIS_SPATIAL_REFERENCE_SYSTEMS TABLE VALID
ORDMD_AG_LIBS LIBRARY VALID
ORDMD_CS_LIBS LIBRARY VALID
ORDMD_IDX_LIBS LIBRARY VALID
ORDMD_LRS_LIBS LIBRARY VALID
ORDMD_MBR_LIBS LIBRARY VALID
ORDMD_MIG_LIBS LIBRARY VALID
ORDMD_PRIDX_LIBS LIBRARY VALID
ORDMD_REL_LIBS LIBRARY VALID
ORDMD_RTREE_LIBS LIBRARY VALID
ORDMD_UDT_LIBS LIBRARY VALID
ORDMD_UTL_LIBS LIBRARY VALID
ORDMD_WD_LIBS LIBRARY VALID
PK_SDO_MASK INDEX VALID
PK_SRID INDEX VALID
PRVT_IDX PACKAGE VALID
PRVT_IDX PACKAGE BODY VALID
RTREE_FILTER OPERATOR VALID
RTREE_IDX PACKAGE VALID
RTREE_IDX PACKAGE BODY VALID
RTREE_INDEX INDEXTYPE VALID
RTREE_INDEX_METHOD TYPE VALID
RTREE_INDEX_METHOD TYPE BODY VALID
RTREE_NN OPERATOR VALID
SAMPLE_SEQ SEQUENCE VALID
SDO PACKAGE VALID
SDO PACKAGE BODY VALID
SDOAGGR TYPE VALID
SDOAGGR TYPE BODY VALID
SDOAGGRTYPE TYPE VALID
SDO_3GL PACKAGE VALID
SDO_3GL PACKAGE BODY VALID
SDO_ADMIN PACKAGE VALID
SDO_ADMIN PACKAGE BODY VALID
SDO_AGGR_CENTROID FUNCTION VALID
SDO_AGGR_CONVEXHULL FUNCTION VALID
SDO_AGGR_LRS_CONCAT FUNCTION VALID
SDO_AGGR_LRS_CONCAT_3D FUNCTION VALID
SDO_AGGR_MBR FUNCTION VALID
SDO_AGGR_UNION FUNCTION VALID
SDO_ANGLE_UNITS TABLE VALID
SDO_AREA_UNITS TABLE VALID
SDO_CATALOG PACKAGE VALID
SDO_CATALOG PACKAGE BODY VALID
SDO_CONSTRUCT_DIM_ARRAY FUNCTION VALID
SDO_CS PACKAGE VALID
SDO_CS PACKAGE BODY VALID
SDO_DATUMS TABLE VALID
SDO_DIM_ARRAY TYPE VALID
SDO_DIM_ELEMENT TYPE VALID
SDO_DIST_UNITS TABLE VALID
SDO_DROP_USER TRIGGER VALID
SDO_ELEM_INFO_ARRAY TYPE VALID
SDO_ELLIPSOIDS TABLE VALID
SDO_FILTER OPERATOR VALID
SDO_GEOM PACKAGE VALID
SDO_GEOM PACKAGE BODY VALID
SDO_GEOMETRY TYPE VALID
SDO_GEOMETRY TYPE BODY VALID
SDO_GEOM_IDX INDEX VALID
SDO_GEOM_METADATA_TABLE TABLE VALID
SDO_GEOM_TRIG_DEL1 TRIGGER VALID
SDO_GEOM_TRIG_INS1 TRIGGER VALID
SDO_GEOM_TRIG_UPD1 TRIGGER VALID
SDO_IDX PACKAGE VALID
SDO_IDX PACKAGE BODY VALID
SDO_IDX_MDATA_IDX INDEX VALID
SDO_IDX_TAB_SEQUENCE SEQUENCE VALID
SDO_INDEX_METADATA_TABLE TABLE VALID
SDO_INDEX_METHOD_9I TYPE VALID
SDO_INDEX_METHOD_9I TYPE BODY VALID
SDO_INT2_FILTER OPERATOR VALID
SDO_INT2_RELATE OPERATOR VALID
SDO_INT_FILTER OPERATOR VALID
SDO_INT_RELATE OPERATOR VALID
SDO_LRS PACKAGE VALID
SDO_LRS PACKAGE BODY VALID
SDO_LRS_METADATA_TABLE TABLE VALID
SDO_LRS_META_IDX INDEX VALID
SDO_LRS_TRIG_DEL TRIGGER VALID
SDO_LRS_TRIG_INS TRIGGER VALID
SDO_LRS_TRIG_UPD TRIGGER VALID
SDO_MAPS_TABLE TABLE VALID
SDO_MBR TYPE VALID
SDO_META PACKAGE VALID
SDO_META PACKAGE BODY VALID
SDO_MIGRATE PACKAGE VALID
SDO_MIGRATE PACKAGE BODY INVALID
SDO_NN OPERATOR VALID
SDO_NN_DISTANCE OPERATOR VALID
SDO_NUMTAB TYPE VALID
SDO_ORDINATE_ARRAY TYPE VALID
SDO_POINT_TYPE TYPE VALID
SDO_PRIDX PACKAGE VALID
SDO_PRIDX PACKAGE BODY VALID
SDO_PROJECTIONS TABLE VALID
SDO_RELATE OPERATOR VALID
SDO_RELATEMASK_TABLE VIEW VALID
SDO_RELATE_MASK PACKAGE VALID
SDO_RELATE_MASK PACKAGE BODY VALID
SDO_RID_ARRAY TYPE VALID
SDO_RTREE_ADMIN PACKAGE VALID
SDO_RTREE_ADMIN PACKAGE BODY VALID
SDO_RTREE_FILTER OPERATOR VALID
SDO_RTREE_RELATE OPERATOR VALID
SDO_STAT TYPE VALID
SDO_STATTAB TYPE VALID
SDO_STYLES_TABLE TABLE VALID
SDO_THEMES_IDX INDEX VALID
SDO_THEMES_TABLE TABLE VALID
SDO_TUNE PACKAGE VALID
SDO_TUNE PACKAGE BODY VALID
SDO_UTIL PACKAGE VALID
SDO_UTIL PACKAGE BODY VALID
SDO_VERSION FUNCTION VALID
SDO_VPOINT_TYPE TYPE VALID
SDO_WITHIN_DISTANCE OPERATOR VALID
SPATIAL_INDEX INDEXTYPE VALID
SYS_C001565 INDEX VALID
SYS_C001571 INDEX VALID
SYS_C001706 INDEX VALID
SYS_LOB0000027008C00040$$ LOB VALID
SYS_LOB0000027008C00041$$ LOB VALID
SYS_LOB0000027053C00012$$ LOB VALID
SYS_LOB0000027053C00013$$ LOB VALID
SYS_LOB0000027209C00004$$ LOB VALID
SYS_LOB0000027216C00005$$ LOB VALID
SYS_LOB0000027216C00006$$ LOB VALID
SYS_LOB0000027216C00013$$ LOB VALID
SYS_LOB0000027216C00014$$ LOB VALID
SYS_LOB0000027229C00006$$ LOB VALID
SYS_LOB0000028651C00012$$ LOB VALID
SYS_LOB0000028651C00013$$ LOB VALID
TRANSFORM_MAP PACKAGE VALID
TRANSFORM_MAP PACKAGE BODY VALID
UNIQUE_ANGLE_UNITS INDEX VALID
UNIQUE_AREA_UNITS INDEX VALID
UNIQUE_DIST_UNITS INDEX VALID
UNIQUE_LAYERS INDEX VALID
UNIQUE_MAPS INDEX VALID
UNIQUE_STYLES INDEX VALID
UNIQUE_TABLES INDEX VALID
UNIQUE_THEMES INDEX VALID
USER_CS_SRS TABLE VALID
USER_GEOMETRY_COLUMNS VIEW VALID
USER_SDO_GEOM_METADATA VIEW VALID
USER_SDO_INDEX_INFO VIEW VALID
USER_SDO_INDEX_METADATA VIEW VALID
USER_SDO_LRS_METADATA VIEW VALID
USER_SDO_MAPS VIEW VALID
USER_SDO_STYLES VIEW VALID
USER_SDO_THEMES VIEW VALID
USER_TRANSFORM_MAP TABLE VALID
V81_INDEX_OBJECT TYPE VALID
V81_INDEX_OBJ_ARRAY TYPE VALID
V81_NT_IND_TYPE TYPE VALID
VERTEX_SET_TYPE TYPE VALID
VERTEX_TYPE TYPE VALID
250 rows selected.
SQL>
SQL> spool off

Sir! No Sir! :)
I will try to explain.
If I do have table with russian letter, than creating index creation will fail, no matter name of index :(
But if I will prepare copy of my table with english name (including meta-data) - index creations is succesfull.

9.2.0.6 Intersection Error

Weve recently upgraded to 9.2.0.6 as part of a major release and were seeing the following spatial error intermittently in our Production system which is causing us major problems. When we get this problem the whole GIS application grinds to a halt.
*** SESSION ID:(173.10) 2006-05-03 09:51:33.390
*** 2006-05-03 09:51:33.390
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kohdtf048], [], [], [], [], [], [], []
Current SQL statement for this session:
SELECT COUNT(*) , SDO_AGGR_UNION(MDSYS.SDOAGGRTYPE(TBLINPROCESSPBLPLY.GEOM, 0.001)) FROM TBLINPROCESSPBLPLY WHERE CRN = :B3 AND SDO_RELATE(TBLINPROCESSPBLPLY.GEOM,:B2 , 'mask=ANYINTERACT querytype=WINDOW')='TRUE' AND SDO_GEOM.SDO_AREA(SDO_GEOM.SDO_INTERSECTION(TBLINPROCESSPBLPLY.GEOM ,
:B4 ,:B2 ,:B4 ),:B4 ) > 10 AND CREATEDBY = :B1 AND OBJLOCKED = 2
----- PL/SQL Call Stack -----
object line object
handle number name
43143e930 25 MDSYS.AGGRUNION
43143e930 25 MDSYS.AGGRUNION
430296160 1 anonymous block
4314eb9d8 485 RLR.TBLINPROCESSPBLPLY
The current code looks as follows, based on a trigger:-
SELECT COUNT(*) , SDO_AGGR_UNION(MDSYS.SDOAGGRTYPE(TBLINPROCESSPBLPLY.GEOM, 0.001)) INTO nPBLPolys , nUnionElem FROM TBLINPROCESSPBLPLY
WHERE CRN = :NEW.CRN
AND SDO_RELATE
(TBLINPROCESSPBLPLY.GEOM,:NEW.GEOM , 'mask=ANYINTERACT querytype=WINDOW')='TRUE'
AND SDO_GEOM.SDO_AREA(SDO_GEOM.SDO_INTERSECTION(TBLINPROCESSPBLPLY.GEOM , dim_array ,:NEW.GEOM ,dim_array),dim_array) > 10
AND CREATEDBY = :NEW.CREATEDBY
AND OBJLOCKED = 2
I have looked on the Oracle forums and it looks like the SDO_INTERSECTION call is causing the exception. Ive changed the above to the following to remove this call and also added an exception block.
BEGIN
SELECT COUNT (*),
sdo_aggr_union
(MDSYS.sdoaggrtype
(tblinprocesspblply.geom,
0.001
INTO npblpolys,
nunionelem
FROM tblinprocesspblply
WHERE crn = :NEW.crn
AND sdo_relate
(tblinprocesspblply.geom,
:NEW.geom,
'mask=OVERLAPBDYINTERSECT+CONTAINS+INSIDE+COVERS+COVEREDBY+EQUAL querytype=WINDOW'
) = 'TRUE'
AND createdby = :NEW.createdby
AND objlocked = 2;
EXCEPTION
WHEN OTHERS
THEN
BEGIN
INSERT INTO tbltrigger_log
(lineno, varname, VALUE
VALUES (2, :NEW.crn, :NEW.createdby
RAISE;
END;
END;
Hopefully this will solve the problem but I was wondering if anyone had seen this problem before and how you got around it. And also if the second piece of SQL would mimic the first?

This looks like a known memory leak issue with sdo_aggr_union which
is fixed in 9207.
Do you know how many rows are going into the sdo_aggr_union function ?
siva

Delete exposure in THMEX and FTREX12 - error "Transaction does not exist"

I have transferred by error an exposure (using TFREX12) to HM. In THMEX I have deleted the newly created exposure that has a transaction Nber. Then in TFREX12 I try to reverse this transfer by using in the menu Position the function "Reverse transfer" but get an error message "Transaction xxx does not exist". How can it be deleted so that I can transfer the exposure to the appropriate Hedge Plan??
Thanks
G.

Hi,
correct procedure is to reverse transfer in FTREX12 without deleting the exposure in THMEX. If you deleted it in THMEX first, then the error is justified. To solve the problem, you can manually create an exposure with the same transaction directly in THMEX, then transfer reversal should be possible.
Rgds,
Tomislav

In Finder , why i can't go back and forward using the trackpad in Mountain Lion?

In Finder , why i can't go back and forward using the trackpad in Mountain Lion?

Hi. I also got the same problem but just learnt a way to resolve it. No need for 3rd party software.
If you don't care much about the Three finger drag gesture, and just want to swipe between pages in Finder and web browsers, please follow these:
System Preferences/Trackpad/More gestures/Swipe between pages/Scroll left or right with 2 fingers. This option works solely for web browsers.
In order to swipe between pages in Finder, web browsers and other apps as well,change the option to Swipe with two or three fingers. (3 for Finder and apps, 2 for web pages)
If you also want to use Three-finger drag to move windows and drag-select:
The problem occurs once you change to "Swipe with 2 or three fingers", Lion will automatically disable/uncheck the Three finger drag function in Trackpad/Point&Click. Or the other way around, you tick Three Finger drag, Swipe between pages automatically switches to Scroll with two fingers because these 2 functions are overlapped.
My solution is:
stick with initial option Scroll with two fingers for navigating between web pages.
Re-tick Three finger drag in Point&Click.
Use combination: Option+Swipe 4 fingers for Finder and other apps (although it functions reversely, Swiping left to go backward, swipe right to go forward)
My current gesture routine:
- Swipe between web pages: Scroll with two fingers.
- Swipe between pages in Finder and other apps: Combination Option+swipe 4 fingers
- Swipe between full-screen apps (desktops): Swipe left or right with 4 fingers
- Drag select and navigate windows: Three finger drag
- Mission Control - Swipe up with 4 fingers. (avoid conflict with three finger drag)
* You can actually use combination Option+Swipe 4 fingers for everything (apps, finder, web pages) but I personally prefer swipe 2 fingers for web browsing. It's just easier and quicker and avoid conflicts with other gestures.
Hope this help.

What's the deal with iCal and DNS?

So according to the documents, you need a domain name and fully functional reverse DNS, to use the caldav server? What's that all about? Do you really need all that? Why can't you just type in the IP of the server, and connect to the server? Just like connecting to a web server, nice and simple? Most ISP's won't give you custom reverse DNS. My collocation data center does, bust all the calendar servers i've set up, were in small office networks with small mac mini servers. I feel like I'm missing some part of this equation?

Why? Modern IP network security and user authentication is based on forward DNS, and particularly on matching forward and reverse DNS.
More than iCal Server here, Mac OS X Server itself expects functional DNS.
If you're running privately, the easiest approach is the obvious one: [set up your DNS|http://labs.hoffmanlabs.com/node/1436] and be done with it.
Mac OS X Server can get wonky with no DNS and can get particularly wonky with bad DNS. And the authentication services can get particularly cranky in the absence of DNS. (That's why SLS sets up its own very private rDNS environment for itself during the installation, when installed in the absence of local DNS.)
nb: iCal doesn't need the SRV records if you're on the default ports.
Or for running your iCal publicly? You're in a slightly tough spot with your ISP. Try it. Like with the mail server and other services, I'd tend to have issues with mismatching reverse DNS. Or connect into and use a tunnel, as that reduces the "fun factor" with network security and dealing with the yutzes that attack everybody's servers, in addition masking to the rDNS aspects.

SDO_AGGR_UNION function reverses linestrings !?

Similar Messages

Maybe you are looking for