Creating Index Spatial problems (Beginner)

I get the below error:

CREATE INDEXES HHLT. BUILDING_SPATIAL_IDX
*
ERROR on line 1:
ORA-29855: an error has occurred in the execution of routine ODCIINDEXCREATE
ORA-13203: cannot read the notice USER_SDO_GEOM_METADATA
ORA-13203: cannot read the notice USER_SDO_GEOM_METADATA
ORA-06512: at the 'MDSYS. SDO_INDEX_METHOD_10I', line 10


When I select run the following, I get:
Select * from mdsys.sdo_geom_metadata_table;

SDO_OWNER SDO_TABLE_NAME
-------------------------------- --------------------------------
SDO_COLUMN_NAME
--------------------------------------------------------------------------------

SDO_DIMINFO (SDO_LB, SDO_UB, SDO_DIMNAME, SDO_TOLERANCE)
--------------------------------------------------------------------------------

SDO_SRID
----------
BUILDING SYS
BUILDING_POLYGON
SDO_DIM_ARRAY (SDO_DIM_ELEMENT ('X', 0,.005, 820), SDO_DIM_ELEMENT ('Y', 0, 580,.)

005))



This is my script:
=========================
create user HHLT identified by HHLT;
grant all privileges on HHLT;

ALTER session set current_schema = HHLT;

CREATE THE TABLE HHLT. BUILDING
(
BUILDING_ID VARCHAR2 (3),
BUILDING_NAME VARCHAR2 (50).
VERTICES_COUNT INT,
MDSYS BUILDING_POLYGON. SDO_GEOMETRY,
CONSTRAINT BUILDING_PK PRIMARY KEY (BUILDING_ID)
);

INSERT IN USER_SDO_GEOM_METADATA
VALUES ('CONSTRUCTION', 'BUILDING_POLYGON',
SDO_DIM_ARRAY (SDO_DIM_ELEMENT ('X', 0, 820, 0.005),
SDO_DIM_ELEMENT ('Y', 0, 580, 0.005)), NULL);

COMMIT;

CREATE INDEXES ELKORDY. BUILDING_SPATIAL_IDX
ON ELKORDY. BUILDING (BUILDING_POLYGON)
INDEXTYPE IS MDSYS. SPATIAL_INDEX;
==================================

What Miss me? Windows 7 installation work.

Dear nobody without a name...

It looks like the cross-schema issues for me.

You do all your work in the HHLT schema and then, at the end of your script, you do this:

CREATE INDEX ELKORDY.BUILDING_SPATIAL_IDX
 ON ELKORDY.BUILDING(BUILDING_POLYGON)
 INDEXTYPE IS MDSYS.SPATIAL_INDEX;

You are still in your message:

CREATE INDEXES HHLT. BUILDING_SPATIAL_IDX

Sorry, who is?

In addition, when you select in the metadata table it tells you that the table of the BUILDING is in the SYS schema (SYS is the owner), but not in HHLT or ELKORDY!

I think that:

ALTER session set current_schema = HHLT;

Do not connect you expect - you are still the user SYS - so that when you did:

INSERT INTO USER_SDO_GEOM_METADATA
 VALUES ('BUILDING', 'BUILDING_POLYGON',
 SDO_DIM_ARRAY( SDO_DIM_ELEMENT('X', 0, 820, 0.005),
 SDO_DIM_ELEMENT('Y', 0, 580, 0.005)), NULL);

It combined the metadata with the SYS owner and not the owner of HHLT where the error during the creation of the index.

I would recommend you.

1. connect as the SYS schema.
2. remove metadata objects.
3. plug into a new session on the schema HHLT as user HHLT.
5. create a new metadata entry in user_sdo_geom_metadata when in the HHLT schema.
6 create the index (drop all existing broken index first).

concerning
SImon

Tags: Database

Similar Questions

  • Data Modeler - cannot create a spatial index

    Good day, colleagues!

    I have a version 584 of the Modeler of Dala.

    Here is her quote Guide of Modeler of Oracle SQL Developer data:

    "Properties of spatial definition 3.82.
    ...
    Benchmark ID: Value Oracle Spatial SRID. ...
    + Create Spatial Index: Determines if a spatial index is created. +
    Name of the spatial Index: name of the spatial index.
    ..."

    I have a SDO_GEOMETRY column in my table and want to create the spatial index.

    The problem is that there is no option "Create Spatial Index" in my space definition properties window. There is only 'The Spatial Index name' option. When I am creating the spatial index manually, I can't, because the option 'Space' for index creation is not active. I checked the table option 'Save as space Table', but it also did not help.

    So, I have no way to create a spatial index. How can I do?

    Hello usamytch,

    create spatial index is confusing. We will improve it in future releases. Here are the steps:
    (1) creation of index - no need to add columns
    (2) create the spatial column definition ('space properties' in the dialog table)
    (3) in the definition of the spatial column, you can select the size of the spatial column, coordinate ID system, and you can select one of the existing indexes to be used as a space.
    (4) after this index appear as space and you can define the spatial properties in the index dialog box
    (5) you must check 'Save as space Table' in order to get meta-space data generated by DDL

    There are additional space properties, that you can set in the physical model.

    Philippe

  • Problem with CREATE INDEX script

    Hello world!
    I want to create a 3D Spatial Index. So I added a few lines (PARAMETERS ('sdo_indx_dims = 3')) in the following script, I get the error

    PLS-00103: encountered the symbol "SETTINGS" then wait for the following :), * & = - + <>.
    PLS-00103: encountered the symbol "SDO_INDX_DIMS" then wait for the following :), * & = - + <>.

    Everything works well, if I remove the PARAMETERS ('sdo_index_dims = 3').
    I know that I need a few symbols, but I'm not good in programming
    Thanks for the tips!

    -create spatial indexes
    --
    procedure create_index
    newIndex user_indexes.index_name%type;
    Start

    list_spatial_indexed_tables;
    -Find all tables containing columns and a corresponding line in user_sdo_geom_metadata
    - and without a spatial index
    for rec in spatial_index_cursor
    loop
    newIndex: = rec.table_name | '_RTREE_IDX ';
    Execute ('create index' | newIndex |) "on" |
    Rec.table_name | ' (' | rec.column_name |)
    indextype') is mdsys.spatial_index ('sdo_indx_dims = 3') SETTINGS ');
    end loop;

    list_tables_missing_sdo_data ("spatial index cannot be created");

    end create_index;

    Hello

    in a string, you must make to a single quote, two quotes, then do this:

    -- create spatial indexes
    --
    procedure create_index is
    newIndex user_indexes.index_name%type;
    begin
    
    list_spatial_indexed_tables;
    -- Find all tables containing spatial columns and a corresponding row in user_sdo_geom_metadata
    -- and without a spatial index
    for rec in spatial_index_cursor
    loop
    newIndex := rec.table_name || '_RTREE_IDX';
    run ('create index ' || newIndex || ' on ' ||
    rec.table_name || '(' || rec.column_name ||
    ') indextype is mdsys.spatial_index PARAMETERS (''sdo_indx_dims=3'')');
    end loop;
    
    list_tables_missing_sdo_data ('spatial index can not be created');
    
    end create_index;
    

    If the quotes to the parameters clause must be doubled.

    Herald tiomela
    Superconsult.nl

  • CTXSYS. Problem creating index of type CONTEXT.

    Hi all

    I am trying to create an index of context as follows and it works well.

    CREATE INDEXES SMADMIN. ITX_DM_SYSOB_R_KYS ON SMADMIN. DM_SYSOBJECT_R (KEY WORDS)
    INDEXTYPE IS CTXSYS. CONTEXT;

    CREATE INDEX succeeded.

    But when I'm adding it setting paragraph as follows, I get the below error.


    CREATE INDEXES SMADMIN. ITX_DM_SYSOB_R_KYS ON SMADMIN. DM_SYSOBJECT_R (KEY WORDS)
    INDEXTYPE IS CTXSYS. CONTEXT parameters ('sync (each SYSDATE + 5/1440)');

    Error from the 1 in the command line:
    CREATE INDEXES SMADMIN. ITX_DM_SYSOB_R_KYS ON SMADMIN. DM_SYSOBJECT_R (KEY WORDS)
    INDEXTYPE IS CTXSYS. CONTEXT parameters ('sync (each SYSDATE + 5/1440)')
    Error in the command line: 1 column: 23
    Error report:
    SQL error: ORA-29855: error when executing routine ODCIINDEXCREATE
    ORA-20000: Oracle text error:
    DRG-50857: error oracle in drvddl. IndexCreate
    ORA-27486: insufficient privileges
    ORA-06512: AT CTXSYS. DRUE, line 160
    ORA-06512: AT CTXSYS. TEXTINDEXMETHODS, line 365
    29855 00000 - an error has occurred in the execution of routine ODCIINDEXCREATE
    * Cause: Cannot run the ODCIIndexCreate routine.
    * Action: Check if the routine was coded correctly.


    Please advise to solve the problem.

    Thank you
    -Samar-

    Hello

    the use of the synchronization setting, the user must be granted to run a job. Oracle is a job to do the synchronization. Then issue:

    GRANT CREATE JOB TO SMADMIN;

    SYS/system.

    Herald tiomela
    superconsult.nl

  • Cannot create the spatial index

    It's a little bit of the puzzle for me this one, I made this little time on different system and I do not understand why it's here

    Oracle 11.1.0.7 Windows 64-bit

    We have simple following table:

    CREATE TABLE DASHBOARD. DSGEOEXCEPTION
    (
    GEOIDE NUMBER NOT NULL,
    ZORDER INTEGER DEFAULT 0 NOT NULL.
    HOUSENO VARCHAR2 (100),
    STREET VARCHAR2 (100),
    VARCHAR2 (100) SUBURBAN,.
    CITY VARCHAR2 (100),
    COUNTY OF VARCHAR2 (100),
    DESCRIPTION VARCHAR2 (200),
    MDSYS FORM. SDO_GEOMETRY
    )
    LOGGING
    NOCOMPRESS
    NOCACHE
    NOPARALLEL
    NOMONITORING;

    ALTER TABLE DASH. (ADD) DSGEOEXCEPTION
    CONSTRAINT DSGEOEXCEPTION_PK
    KEY ELEMENTARY SCHOOL
    (GEOIDE)) ;



    Insert values (user_sdo_geom_metadata)
    "DASHBOARD. DSGEOEXCEPTION',.
    "FORM."
    MDSYS. () SDO_DIM_ARRAY
    MDSYS. SDO_DIM_ELEMENT ('LONGITUDE',-180, 180, 0.00005),
    MDSYS. SDO_DIM_ELEMENT ('LATITUDE',-90, 90, 0.00005)
    ),
    8307);

    until then, everything is good.

    I run the two sql suite to ensure that everything is fine

    Select * from USER_SDO_GEOM_METADATA;
    Dashboard. DSGEOEXCEPTION, shape, ((LONGITUDE,-180, 180, 5E-5), (LATITUDE, -90, 90, 5th-5),), 8307
    select * from mdsys.sdo_geom_metadata_table
    DASHBOARD, dashboard. DSGEOEXCEPTION, shape, ((LONGITUDE,-180, 180, 5E-5), (LATITUDE, -90, 90, 5th-5),), 8307
    select * from ALL_SDO_GEOM_METADATA;


    first 2 return one row as planned last returns nothing

    creating the index

    CREATE INDEXES DASH. DSGEOEXCEPTION_SIDX ON DASHBOARD. DSGEOEXCEPTION
    (FORM)
    INDEXTYPE IS MDSYS. SPATIAL_INDEX
    NOPARALLEL;

    or

    CREATE INDEXES DASH. DSGEOEXCEPTION_SIDX ON DASHBOARD. DSGEOEXCEPTION
    (FORM)
    INDEXTYPE IS MDSYS. SPATIAL_INDEX;


    fails with the error:

    ORA-29855: an error has occurred in the execution of routine ODCIINDEXCREATE
    ORA-13203: cannot read the notice USER_SDO_GEOM_METADATA
    ORA-13203: cannot read the notice USER_SDO_GEOM_METADATA
    ORA-06512: at the 'MDSYS. SDO_INDEX_METHOD_10I', line 10



    According to one of the posts, I run this

    ALTER session set current_schema = MDSYS;
    @$ORACLE_HOME/md/admin/prvtgmd.plb

    but no difference I can always create index


    Any suggestions?

    Please, try the following:

    Insert values (user_sdo_geom_metadata)
    "DSGEOEXCEPTION,"
    "FORM."
    MDSYS. () SDO_DIM_ARRAY
    MDSYS. SDO_DIM_ELEMENT ('LONGITUDE',-180, 180, 0.00005),
    MDSYS. SDO_DIM_ELEMENT ('LATITUDE',-90, 90, 0.00005)
    ),
    8307);

  • CREATE INDEXES online is waiting for the TX = 4 mode

    Hello

    I have a strange blocking problem where an INDEX CREATE LINE is waiting for a transaction that did only inserted a line in the parent table.

    Wait is mode TX = 4 (not TM locks) and I currently have it reproduced only on 11.2.0.3 and 11.2.0.4

    Easy to replicate the schema SCOTT:

    Session 1:

    SQL > set time on

    14:54:58 SQL > insert into SCOTT. Dept (DEPTNO, dname) values (50, 'test');

    1 line of creation.

    Session 2;

    14:55:24 SQL > create index test on SCOTT. EMP (ename) online;

    It's waiting ' enq: TX - line lock conflict ":"

    SQL > select sid, chain_signature from v$ wait_chains where blocker_is_valid = 'TRUE '.

    SID CHAIN_SIGNATURE

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

    603 ' SQL * Net client message' < ='enq: TX - line lock conflict '

    While waiting to acquire the lock of transaction in mode 4:

    SQL > select * lock gv$ where sid = 603

    INST_ID SELECT ADDR KADDR SID TYPE ID1 ID2 LMODE CTIME BLOCK REQUEST

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

    1 00000006CDA05EB8 00000006CDA05F10 603 352577 0 4 0 348 2 AE

    1 00000006CDA06078 00000006CDA060D0 603 DL 779505 0 3 0 308 2

    1 00000006CD9FABE0 00000006CD9FAC38 603 DL 779505 0 3 0 308 2

    1 00007F28001F5028 00007F28001F5088 603 779505 0 2 0 308 2 TM

    1 00007F28001F5028 00007F28001F5088 603 779510 0 4 0 308 2 TM

    1 00000006CD9FA240 00000006CD9FA298 603 779505 0 4 0 308 2 OD

    1 00000006B4F26790 00000006B4F26808 589847 711499 6 0 308 2 TX 603

    1 00000006CDA0ED68 00000006CDA0EDC0 655377 996169 0 4 308 TX 603 0

    I've traced 10046 and 10704:

    broadcast message = obj 29231196672 #= 779514 tim = 1447251053634045

    ksqgtl * mode TX-000f001e-000ad97c = 4 flags = 0 x 10001 timeout = 21474836 *.

    ksqgtl: xcb = 0x6bb322528, ktcdix = 2147483647, topxcb = 0x6bb322528

    ktcipt (topxcb) = 0 x 0

    ksucti: init logon has of txn DID:

    ksqgtl:

    ksqlkdid: 0001-003F-0000AFC4

    ksudidTrace: ksqgtl

    ktcmydid(): 0001-003F-0000AFC4

    ksusesdi: 0001-003F-0000AFC3

    ksusetxn: 0001-003F-0000AFC4

    ksqcmi: TX, f001e, ad97c mode = 4 timeout = 21474836

    2015-11-11 15:11:36.566

    WAITING #140700792578680: nam ='enq: TX - line lock conflict ' ela 42932082 name = | mode = 1415053316 usn < < 16 | location = sequence 983070 = obj 711036 #= 779514 tim = 1447251096566283

    And there is nothing in V$ SESSION leader/block/line current. class obj # is EMP. current sql_id is the CREATE INDEX.

    If anyone has an idea on:

    -Why creating an index in line must wait for transactions that modified only parent table

    -How to continue the investigation

    -can or cannot reproduce in other versions

    Thanks in advance,

    Franck.

    I guess you have a constraint foreign key between emp and Dept.

    It's expected behaviours: since 11.1 any DML at one end of a referential integrity constraint translates into a mode lock 3 taken at the other end, and your phenomenon resembles a side effect of this.

    When you try to create the index online that your session must assume that the other session (holding mode 3 on the emp and dept) may have changed the emp and dept, so it must wait for the session to the commit or rollback.

    (I guess that in principle, he could walk the cancellation of the transaction see if EMP had in fact been changed - but maybe who was considered too complicated to be worth the risk to implement)

    Concerning

    Jonathan Lewis

    Updated - I just did a quick check to reproduce the effect on 11.1.0.7

    For reference - here are a few notes on modes of locking and how the application has changed over time: https://jonathanlewis.wordpress.com/2010/06/21/locks/

  • create indexes on the upper part of the column - reminders function is not deterministic

    Hi all

    I'm having a problem on a database. When you create an index on an existing table on the upper part of a column, Oracle triggers an ORA-30553. I've done this 40 index other databases, with the same and different versions, without problem. When you create the index on a copy of the table, it is created with success...

    Here is the code:

    SQL > select * from v version $;

    BANNER

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

    Oracle Database 11 g Release 11.2.0.3.0 - 64 bit Production

    PL/SQL Release 11.2.0.3.0 - Production

    CORE Production 11.2.0.3.0

    AMT for 64-bit Windows: Version 11.2.0.3.0 - Production

    NLSRTL Version 11.2.0.3.0 - Production

    SQL > CREATE INDEX IDX_SRE_E_MAIL_UPPER on fsynrelatie (upper (sre_e_mail)) tablespace idx;

    CREATE the INDEX IDX_SRE_E_MAIL_UPPER on idx tablespace fsynrelatie (upper (sre_e_mail))

    *

    ERROR on line 1:

    ORA-30553: the function is not deterministic

    SQL > create table fsynrelatie2 in select * from fsynrelatie;

    Table created.

    SQL > CREATE INDEX IDX_SRE_E_MAIL_UPPER on fsynrelatie2 (upper (sre_e_mail)) tablespace idx;

    The index is created.

    SQL > drop table fsynrelatie2;

    Deleted table.

    SQL > show parameter query_rewrite_enabled

    VALUE OF TYPE NAME

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

    query_rewrite_enabled string TRUE

    Hi all

    Thank you for the answers. I found the problem:

    On the table, there are 54 index:

    Select index_type, uniqueness, count (*) from user_indexes where table_name = 'FSYNRELATIE '.

    Index_type group, uniqueness

    INDEX_TYPE SINGLE CHARACTER COUNT (*)
    FIELD ARE NOT UNIQUE 1
    BASED ON A NORMAL FUNCTION ARE NOT UNIQUE 4
    NORMAL UNIQUE 3
    NORMAL ARE NOT UNIQUE 46

    3 unique indexes are the primary key and 2 another witch number field contains unique identifiers for rows in other systems. The domain index is an index of Oracle text on a couple of fields. There are 3 indices of function based on a high on a field and 1 on an individual function. This last clue has caused the problem. Apparently, on the creation, this function is deterministic, but when rolling a new version of the software. It became a non-deterministic function. When I delete the index, my original index on upper (sre_e_mail) has been created successfully! Now, I did the deterministic function again and could recreate the function without problem.

    Thanks for your comments!

  • Cannot create indexes on the flow table

    Hello

    I'm new to ODI.

    The problem is that during the execution of an interface, I get the error of the "IKM Oracle Dimension to slow variation"

    The command in step "Create unique index on the flow table:

    creating index < % = odiRef.getTable ("L", "INT_NAME", "A") % > idx

    on < % = odiRef.getTable ("L", "INT_NAME", "A") % > (< % = odiRef.getColList ("", "[column]", ",", "", "SCD_NK") % >)

    < % = odiRef.getUserExit ("FLOW_TABLE_OPTIONS") % >

    generate the following statement which lacks the name of the column between the (_)

    Create index I$ _MYTABLE_idx

    I have $_MYTABLE)

    NOLOGGING

    The result is that the interface fails with the error 936: 42000: java.sql.SQLException: ORA-00936: lack of expression caused by the previous command wrong.

    Please, can you help me?

    Thank you very much

    Angelo

    Hello

    I'm really really sorry! I just realized that you are working on the SCD. Basically, you are looking for all the column mapped as SCD_NK (key to slowly change natural Dimensions) insofar as shown here

    Substitution QAnywhere

    IF you need to read this

    SCD Type 2 - ODIExperts.com

    Let me know.

  • Get the error when creating indexes in RAC environment in 11 g

    Hi all

    I'm new concept CARS when creating index get below error

    Error: AX_DISABLE_HIST - a SQL error. Position of the error: 0
    Return: 12801 - ORA-12801: error reported in the P146, proceeding parallel query server
    ORA-12853: insufficient memory for buffers PX: run 425904K,.
    Max needed 11105280 K ORA-04031: unable to allocate 32792 bytes of memory ('', 'unknow shared pool
    UNIQUE INDEX CREATE PS_AX_DISABLE_HIST WE PS_AX_DISABLE_HIST (EMPLID) TABLESPACE PSINDEX STORAGE
    (MAXEXTENTS THEN 65536 40000 INITIAL UNLIMITED PCTINCREASE 0) PCTFREE 10 NOLOGGING PARALLEL

    am not able to understand, it's this problem is related to the index or sga memory. can any time help me on that.

    Thanks in advance
    Prabhakar

    Published by: 889571 on May 16, 2013 07:41

    You probably need SGA more because you have a lot of Parallels/slave servers in your instance. I see that you have at least 146. How many processors do you have? Do you need so many parallel servers?

    Lordane Iotzov

  • Creating indexes in to_char

    Hello

    Try to create inxde on concatentated columns and it puts to_char default, trying to make column of numeric index but same to_number highlighting does not to_number on

    With the help of 11.2.03

    A tried

    create index MEDIA_PLIS_HANDLED_IDX on the MEDIA TO_NUMBER ((TO_CHAR (PLIS_HANDLED_YEAR) |)) LPAD (TO_CHAR (PLIS_HANDLED_WEEK), 2, '0')))
    tablespace BI_DW_DATA

    create index MEDIA_PLIS_HANDLED_IDX on MEDIA TO_NUMBER (PLIS_HANDLED_YEAR) | LPAD (PLIS_HANDLED_WEEK, 2, 0))
    tablespace BI_DW_DATA

    Any ideas how to avoid to_char leisure users seeking it has snumeric.

    Thank you

    The problem is with the function outside the parentheses - it is simply ignored.

    It's a quirk of known syntax that does not raise an error.

    SQL> create table t1
      2  (yr number
      3  ,wk number);
    
    Table created.
    
    SQL> create index i1 on t1 to_number(yr||lpad(wk,2,'0'));
    
    Index created.
    
    SQL> select column_expression from user_ind_expressions where index_name = 'I1';
    
    COLUMN_EXPRESSION
    --------------------------------------------------------------------------------
    TO_CHAR("YR")||LPAD(TO_CHAR("WK"),2,'0')
    
    SQL> drop index i1;
    
    Index dropped.
    
    SQL> create index i1 on t1 (to_number(yr||lpad(wk,2,'0')));
    
    Index created.
    
    SQL> select column_expression from user_ind_expressions where index_name = 'I1';
    
    COLUMN_EXPRESSION
    --------------------------------------------------------------------------------
    TO_NUMBER(TO_CHAR("YR")||LPAD(TO_CHAR("WK"),2,'0'))
    
    SQL>
    
  • ORA-00934: function of group not allowed error when creating index

    ORA-00934: Group feature is not allowed here
    create index idx_emp on emp(max(install_time))

    Hello

    Daniel wrote:
    ORA-00934: Group feature is not allowed here

    create index idx_emp on emp(max(install_time))
    

    It's true. It is documented in the Manual of the SQL language

    Restrictions on Function-based Indexes 
    
    Function-based indexes are subject to the following restrictions:
    ...
    The column_expression cannot contain any aggregate functions.
    

    MAX is an aggregate function.

    What problem are you trying to solve? If you could create an index like this, how would you use it?
    Explain what you need to do, and someone will help you find a good way to do it.

  • ENQ: TM - claim when creating index

    Hi all
    I'm trying to create an index on a table with 10 million documents. He got a primary key constraint, and there is no foreign key on all other tables.
    When I tried to create indexes, a few seconds, I am able to see below when asked...
    Select the SID, EVENT, TOTAL_WAITS, TOTAL_TIMEOUTS, TIME_WAITED FROM v$ session_evenement event WHERE ='enq: TM - claim ' and total_waits > 0;
    SID TOTAL_WAITS TOTAL_TIMEOUTS TIME_WAITED EVENT
    399 enq: TM - 101316 345 346 contention
    544 enq: TM - contention 39892 136 137
    862 enq: TM - 149 148 43485 contention
    968 enq: TM - 880 875 255780 contention
    985 enq: TM - 10 9 2842 contention
    999 enq: TM - 66662 227 228 contention

    I thought that these events have been waiting for some time... but the Dungeon number on the increase as the time increases
    I got to know that the creation of an index on the foreign key constraint would solve this... but unfortunately I don't see not all foreign keys...

    This will be solved if I wait for a long time?
    And the sql_text from v$ sqlarea is presented as "insert into table(col1,col2...)". values(:B1,:B2...); »
    Can someone please help me solve this problem...

    Thank you.

    so... is it OK to wait, even if I have 150 + "enq: TM - claim ' events pending on this table for several sid...?

    Depends on your application.

    See above mentioned online.

    http://richardfoote.WordPress.com/2008/02/11/index-create-and-rebuild-locking-improvements-in-11g-ch-ch-ch-changes/

  • Creating indexes in the XMLType column

    Hello

    I have the following for XML document stored as an XMLType column.

    < ocaStatus xmlns = "http://xmlbeans.apache.org/ocastatus" > < status > < > 934 statusCode < / statusCode > < statusDate > Wed Apr 07 16:05:53 GMT + 05:30 2010 < / statusDate > < userId > u0121845 < / userId > < comment > sent to FLC < / comment > < / status > < status > < statusCode > 934 < / statusCode > < statusDate > Wed Apr 07 15:58:25 GMT + 05:30 2010 < / statusDate > < userId > u0121845 < / username > < Comment > sent to FLC < / comment > < / status > < status > < statusCode > 934 < / statusCode > < statusDate > Wed Apr 07 15:54:02 GMT + 05:30 2010 < / statusDate > < userId u0121845 > < / userId > < comment > sent to FLC < / comment > < / status > < status > < statusCode > 750 < / statusCode > < statusDate > 2010 - 03 - 31 12:39:41.580 GMT + 05:30 < / statusDate > < u0121845 userId > < / userId > < comment > metadata of the Document is correct. < / comment > < / status > < status > < statusCode > 934 < / statusCode > < statusDate > 2010 - 03 - 31 12:39:41.580 GMT + 05:30 < / statusDate > < userId > u0121845 < / userId > < comment > sent to FLC < / comment > < / status > < status > < statusCode > 932 < / statusCode > < statusDate > 2010 - 03 - 31 12:39:41.580 GMT + 05:30 < / statusDate > < userId > u0121845 < / username > < comment > loaded Novus < /. comment > < / status > < status > < > 700 statusCode < / statusCode > < statusDate > 2010 - 03 - 31 12:39:41.580 GMT + 05:30 < / statusDate > < userId u0121845 > < / userId > < comment > Document is deleted from the OCA. < / comment > < / status > < / ocaStatus >

    I created as a result of the clues in the XML
    CREATING INDEX 'OCA_DEV '. "' OCA_STATUS_CODE_INDEX ' ON 'OCA_DEV '. "DOCUMENT_STATUS_XML"(EXTRACTVALUE('/ocaStatus/status/statusCode'));
    CREATING INDEX 'OCA_DEV '. "' OCA_STATUS_DATE_INDEX ' ON 'OCA_DEV '. "DOCUMENT_STATUS_XML"(EXTRACTVALUE('/ocaStatus/status/statusDate'));

    However, the problem is that I will be having several status within each XML that violates the indexing.
    Is there a way I can still create indexes for multiple State values in each XML file?

    Thanks in advance.

    Hello

    Take a look at the manual xdb (which version do you use?), for the 10.2 version, see: http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14259/xdb04cre.htm#sthref596
    It describes how you can index an XMLTYPE. Because you describe how you use, take a look at your needs.

    In 11G, you have the XMLINDEX to xmltypes indexing, you will find information here: http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10492/xdb_indexing.htm#CHDFCGGI

    Herald tiomela
    Superconsult.nl

  • a question about creating index on the view

    Hi all

    I had a problem on the creation of an index on the view

    create index sys_ixf_viewpnuc_03 on view_pnuc (ugcode | privatenum);

    It's the sql I've run pl/sql

    the result of the server is:
    SQL error: ORA-01702
    01702 00000 - "a view is not appropriate here.

    Thanks for giving me a helping hand

    TKS

    Hello

    You can not use the index on the view...

    better, you can create a view with the best of the select statement with the specified indexed column...

    Since then, the view is nothing other than a select statement. If any changes in the index, alter in the table and create a consequence of the view...

    canno't ' t you create an index on a view except the materialized view

    Kind regards
    Deepak

  • create indexes and internal error

    Hi, I run

    CREATE INDEX idx_nu_account_id_ ON archost
    (
    acc_id ASC
    )
    tablespace ts_idx
    /
    so happen "ORA-00600: internal error code, arguments: [ksuloget2], [0xFDD1F948], 'this message; '

    Also I during the exec select * archost then if record is going to get all the return even error why?

    What version of Oracle?
    What platform (OS)?

    I found two problem reports to Oracle on this error. The two refer to an LMS > 1 and are Windows specific. If you are under Windows see Oracle support documents: 564784.1 and 5935415.

    You can open a SR if the adjustment to see if there was a patch created. Otherwise, you can try using a smaller CMS framework.

    HTH - Mark D Powell.

Maybe you are looking for