ENQ: TM - claim when creating index

Similar Questions

• 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

• When creating index table lock?

  Hello
  
  My db is oracle10g. My database is OLTP system. I wanted to create the index on one of the table. The table has 200 million recordings.
  
  It locks the whole when table I create index? I think, its impact on the regular operations of the database when creating the index?
  
  Any help is appreciated...

  Hello

  You have Enterprise Edition? If so, the online option is available.

  So you can do:

  create index my_new_index on my_tab(col1,col2) online;
  

  or:

  alter index my_existing_index rebuild online;
  

  If you are not using the online option, then Yes, the table will be locked for updates, all traffic OLTP will serialize buttocks the index maintenance operation.

  Hope that helps,

  -Mark

• 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.

• Change the order of selection when the index is created

  I run the query as
  
  Select emp.ename, dept.dname from emp, dept
  where emp.deptno = dept.deptno;
  
  The result is like
  
  ENAME DNAME
  ---------- --------------
  SEARCH FOR SMITH
  SALES OF ALLEN
  SALES OF WARD
  SEARCH FOR JONES
  SALES OF MARTIN
  SALES OF BLAKE
  CLARK ACCOUNTING
  SEARCH FOR SCOTT
  ACCOUNTING OF KING
  SALES OF TURNER
  SEARCH FOR ADAMS
  
  ENAME DNAME
  ---------- --------------
  JAMES SALES
  SEARCH FORD
  MILLER ACCOUNTING
  
  14 selected lines.
  
  But now, I create an index on the deptno column in the emp table as - create index emp_ie1 on emp (deptno); Now, when I run the query even the result is like
  
  ENAME DNAME
  ---------- --------------
  CLARK ACCOUNTING
  ACCOUNTING OF KING
  MILLER ACCOUNTING
  SEARCH FOR SMITH
  SEARCH FOR JONES
  SEARCH FOR SCOTT
  SEARCH FOR ADAMS
  SEARCH FORD
  SALES OF ALLEN
  SALES OF WARD
  SALES OF MARTIN
  
  ENAME DNAME
  ---------- --------------
  SALES OF BLAKE
  SALES OF TURNER
  JAMES SALES
  
  14 selected lines.
  
  Please, note that, once the index is created the default order is on the deptno. Whereas, in the former case, there is no default order. Any who, can explain this behavior? Thank you

  Just read this

  http://www.DBA-Oracle.com/concepts/index_administration.htm

• 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/

• CHKDSK in windows xp hangs at 0% when the index checking, but eventually ends. Why it suddenly runs so much slower than before? Thank you.

  Once I got this error message after 3-4 were revealed when checking indexes scene: "an unexpected error has occurred...". ». At that time there chkdsk stopped and I had to close the window.

  Test the hard drive with a diagnostic utility downloaded from site of the disc mftr. or use SeaTools for BACK of Seagate. You create a bootable CD with the files you download. You will need a third party burning software to do as the free ImgBurn, Nero or Roxio. Burn as an image, not in the form of data.

  http://www.ImgBurn.com

  http://www.Seagate.com/www/en-us/support/downloads/SeaTools/seatooldreg
  http://Seagate.custkb.com/Seagate/CRM/selfservice/search.jsp?docid=201271 (how-to)

  Boot with the CD that you have done and do a full test of the reader. The physical tests fail, replace it. MS - MVP - Elephant Boy computers - don't panic!

• Why I can't create indexes on the table of RDF data

  When I tried to create indexes on the table of RDF data, it always say the table or view does not exist. I created the RDF model using java codes:

  Oracle Oracle = new Oracle ("jdbc:oracle:thin:@localhost:1521:orcl", "system", "123");

  Chart GraphOracleSem = new GraphOracleSem (oracle, "test2");

  
  

  And used the following commands in sqlplus to create indexes:

  SQL >

  SELECT THE SEPARATE OWNER, OBJECT_NAME

  FROM DBA_OBJECTS

  WHERE TYPE_OBJET = 'TABLE '.

  4. AND OBJECT_NAME like ' % TEST2;

  OWNER

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

  OBJECT_NAME

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

  SYSTEM

  TEST2_NS

  SYSTEM

  RDFB_TEST2

  SYSTEM

  TEST2_TPL

  OWNER

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

  OBJECT_NAME

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

  SYSTEM

  RDFC_TEST2

  
  

  SQL > connect as sysdba

  Enter the password:

  Connected.

  SQL >

  SQL >

  SQL > select * from TEST2_TPL;

  Select * from TEST2_TPL

  *

  ERROR on line 1:

  ORA-00942: table or view does not exist

  SQL > CREATE INDEX test2_sub_idx ON TEST2_TPL (triple. GET_SUBJECT());

  CREATE INDEX test2_sub_idx ON TEST2_TPL (triple. GET_SUBJECT())

  *

  ERROR on line 1:

  ORA-00942: table or view does not exist

  Hi Shifu,

  It is not recommended to use the SYS or SYSTEM to store/manage schema graph RDF data.

  Can you please try the following in a SQL * more terminal?

  SQL > conn system/eu1

  Connected.

  SQL >

  SQL >

  SQL > create user graphuser identified by graphuser;

  Created by the user.

  SQL > grant connect, resources, unlimited tablespace to graphuser;

  Grant succeeded.

  SQL > conn graphuser/graphuser

  Connected.

  SQL > create table graph_tpl (triple sdo_rdf_triple_s) compress;

  Table created.

  SQL > sem_apis.create_sem_model exec ('graphic', 'graph_tpl', 'three');

  PL/SQL procedure successfully completed.

  SQL > insert into graph_tpl values (sdo_rdf_triple_s ('graph', '', '', ''));

  1 line of creation.

  SQL > select count (1) in the mdsys.rdfm_graph;

  1

  You see the same result?

  Thank you

  Zhe Wu

• 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!

• The index used only when given Index indicator

  Hello

  Version of RDBMS - 11.2.0.3.0

  I have a situation where only when I use the Index indicator, index does is used.

  Use case: -.

  1. SELECT query on a table with about 100 KB of data.

  2. have the index on the column that is used in the WHERE clause of the SELECT query.

  CREATE TABLE him_entity (id NUMBER, him_val CHAR(1));
  
  
  INSERT INTO him_entity
  SELECT rownum,'1' FROM dual CONNECT BY level<=1000000;
  
  
  CREATE INDEX idx_him_val ON him_entity(him_val);
  
  
  
  
  
  

  Without using Index indicator, Explain plan: -.

  SELECT ID 
  FROM him_entity
  WHERE him_val='1';
  
  
  -----------------------------------------------------------------------------------
  | Id  | Operation         | Name          | Rows  | Bytes | Cost (%CPU)| Time     |
  -----------------------------------------------------------------------------------
  |   0 | SELECT STATEMENT  |               |  1000K|  4882K|   498   (5)| 00:00:06 |
  |*  1 |  TABLE ACCESS FULL| HIM_ENTITY    |  1000K|  4882K|   498   (5)| 00:00:06 |
  -----------------------------------------------------------------------------------
  
  
  Predicate Information (identified by operation id):
  ---------------------------------------------------
  
  
     1 - filter("HIM_VAL"='1')
  

  With the help of Index indicator, explain the plan: -.

  SELECT /*+ index(him_entity idx_him_val)*/ ID 
  FROM him_entity
  WHERE him_val='1';
  
  
  ---------------------------------------------------------------------------------------------
  | Id  | Operation                   | Name          | Rows  | Bytes | Cost (%CPU)| Time     |
  ---------------------------------------------------------------------------------------------
  |   0 | SELECT STATEMENT            |               |  1000K|  4882K|  3485   (1)| 00:00:42 |
  |   1 |  TABLE ACCESS BY INDEX ROWID| HIM_ENTITY    |  1000K|  4882K|  3485   (1)| 00:00:42 |
  |*  2 |   INDEX RANGE SCAN          | IDX_HIM_VAL   |  1000K|       |  1824   (1)| 00:00:22 |
  ---------------------------------------------------------------------------------------------
  
  
  Predicate Information (identified by operation id):
  ---------------------------------------------------
  
  
     2 - access("HIM_VAL"='1')
  

  (1) could you explain why Index was not be picked up without indicator Index for help?

  (2) I gathered statistics for the table before running the query.

  (3) is it fine / safe to use the FIRST_ROWS hint instead of Index indicator?

  Thank you...

  1. SELECT THE ID
  2. OF him_entity
  3. WHERE him_val = '1';

  You select all the rows in the table.

  As your query will extract all lines then the optimal trajectory IS FULL TABLE SCAN instead of using INDEXES

  If we let you use less than 5% of table rows, and then using index can be an optimal trajectory to go for the record.

  1. SELECT / * + index (him_entity idx_him_val) * / ID
  2. OF him_entity
  3. WHERE him_val = '1';

  Your strength of indicator Index to fetch the file by using the index of the query

• How to create indexes on the ordered collection of XMLTYPE table?

  I use Oracle 11.2.0.2.

  Basically, my XML documents have a 3-level hierarchy:

  event

  + - action [1: n]

  + - param [1: n]

  I try to create indexes on the tables of the orderly collection, but cannot get the right syntax...

  I created a table with an XMLType object-relational column:

  CREATE TABLE T_C_RMP_MNTRNG_XML_FULL_IL4 (
    MESSAGE_ID NUMBER(22,0) NOT NULL ENABLE,
    XML_EVAL_ID NUMBER(22,0),
    VIN7 VARCHAR2(7 BYTE),
    FLEET_ID VARCHAR2(50 BYTE),
    CSC_SW_VERSION VARCHAR2(100 BYTE),
    RECEIVED DATE,
    XML_CONTENT SYS.XMLTYPE ,
    DWH_LM_TS_UTC DATE NOT NULL ENABLE,
    CONSTRAINT PK_C_RMP_MNTRNG_XML_FULL_IL4 PRIMARY KEY (MESSAGE_ID)
  ) NOLOGGING TABLESPACE CATALOG
  VARRAY "XML_CONTENT"."XMLDATA"."action" STORE AS TABLE "T_OR_MON_ACTION" (
    NOLOGGING TABLESPACE "CATALOG"
    VARRAY "param" STORE AS TABLE "T_OR_MON_ACTION_PARAM" (
    NOLOGGING TABLESPACE "CATALOG"
    ) RETURN AS LOCATOR
  ) RETURN AS LOCATOR
  XMLTYPE XML_CONTENT STORE AS OBJECT RELATIONAL XMLSCHEMA "http://mydomain.com/cs.xsd" ELEMENT "monitoring";
  
  
  
  
  

  I execute the SELECT statement:

  SELECT EVENT_ID, ACTION_SUB_ID, MESSAGE_ID, ACTION_TYPE, UNIXTS_TO_DATE(ACTION_TIMESTAMP) ACTION_TIMESTAMP
  FROM T_C_RMP_MNTRNG_XML_FULL_IL4, 
  XMLTABLE( 
    'for $i1 in /monitoring , 
    $i2 in $i1/action            
    return element r {              
    $i1/eventId,              
    $i2            
    }' 
    PASSING XML_CONTENT COLUMNS 
    EVENT_ID VARCHAR(40) PATH 'eventId', 
    ACTION_SUB_ID INTEGER PATH 'action/actionSubId', 
    ACTION_TYPE VARCHAR2(100) PATH 'action/type', 
    ACTION_TIMESTAMP NUMBER(13,0) PATH 'action/time' 
  ) T2 
  WHERE ( 
    EVENT_ID IS NOT NULL AND ACTION_SUB_ID IS NOT NULL 
  )
  
  
  
  
  

  The plan of the explain command looks like this (sorry, don't know how to get it formatted any 'eye-team'):

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

  | ID | Operation | Name                        | Lines | Bytes | TempSpc | Cost (% CPU). Time |

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

  |   0 | SELECT STATEMENT |                             |  1609K |  6316M |       |  6110K (1) | 20:22:11 |

  |*  1 |  HASH JOIN |                             |  1609K |  6316M |   111 M |  6110K (1) | 20:22:11 |

  |   2.   TABLE ACCESS FULL | T_C_RMP_MNTRNG_XML_FULL_IL4 |   582K |   104 M |       |  5241 (1) | 00:01:03 |

  |*  3 |   TABLE ACCESS FULL | T_OR_MON_ACTION |    32 M |   117G |       |   105K (2) | 00:21:08 |

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

  Information of predicates (identified by the operation identity card):

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

  1 - access ("NESTED_TABLE_ID"= "T_C_RMP_MNTRNG_XML_FULL_IL4"." ("SYS_NC0001300014$")

  filter (CAST (SYS_XQ_UPKXML2SQL (SYS_XQEXVAL (SYS_XQEXTRACT ((SYS_XMLGEN ("T_C_RMP_MNTRN XMLCONCAT

  G_XML_FULL_IL4 ". "" $ SYS_NC00017 ", NULL, SYS_XMLCONV ("T_C_RMP_MNTRNG_XML_FULL_IL4". "SYS_NC00012$", 0.32,

  (('EC1EEF23FD023A27E04032A06D930A8D', 3, 3783, 1)), SYS_MAKEXML ('EC1EEF23FD023A27E04032A06D930A8D', 3780,

  'T_C_RMP_MNTRNG_XML_FULL_IL4 '. "' SYS_NC00008$ ', 'SYS_ALIAS_0 '. ((("' SYS_NC_ROWINFO$ ')),'/ ID ', NULL), 0,.

  0,20971520,0), 50.1, 2) AS VARCHAR (40)) IS NOT NULL)

  3 filter (CAST (TO_NUMBER (TO_CHAR ("SYS_ALIAS_0". "actionSubId")) AS INTEGER) IS NOT NULL) "

  Note

  -----

  -dynamic sample used for this survey (level = 2)

  -Construction detected no optimized XML (activate XMLOptimizationCheck for more information)

  The XML schema looks like this:

  <?xml version="1.0" encoding="UTF-8"?>
  <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:oraxdb="http://xmlns.oracle.com/xdb" oraxdb:storeVarrayAsTable="true" oraxdb:flags="2105639" oraxdb:schemaURL="http://mydomain.com/cs.xsd" oraxdb:schemaOwner="MYUSER" oraxdb:numProps="23">
    <xs:element name="monitoring" oraxdb:propNumber="3785" oraxdb:global="true" oraxdb:SQLName="monitoring" oraxdb:SQLType="monitoring755_T" oraxdb:SQLSchema="MYUSER" oraxdb:memType="258" oraxdb:defaultTable="monitoring757_TAB" oraxdb:defaultTableSchema="MYUSER">
      <xs:complexType oraxdb:SQLType="monitoring755_T" oraxdb:SQLSchema="MYUSER">
        <xs:sequence>
          <xs:element maxOccurs="unbounded" ref="action" oraxdb:propNumber="3780" oraxdb:global="false" oraxdb:SQLName="action" oraxdb:SQLType="action752_T" oraxdb:SQLSchema="MYUSER" oraxdb:memType="258" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false" oraxdb:SQLCollType="action756_COLL" oraxdb:SQLCollSchema="MYUSER"/>
          <xs:element ref="reservationType" oraxdb:propNumber="3781" oraxdb:global="false" oraxdb:SQLName="reservationType" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false"/>
          <xs:element ref="softwareVersion" oraxdb:propNumber="3782" oraxdb:global="false" oraxdb:SQLName="softwareVersion" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false"/>
          <xs:element ref="eventId" oraxdb:propNumber="3783" oraxdb:global="false" oraxdb:SQLName="eventId" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false"/>
          <xs:element ref="vin" oraxdb:propNumber="3784" oraxdb:global="false" oraxdb:SQLName="vin" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="action" oraxdb:propNumber="3790" oraxdb:global="true" oraxdb:SQLName="action" oraxdb:SQLType="action752_T" oraxdb:SQLSchema="MYUSER" oraxdb:memType="258" oraxdb:defaultTable="action754_TAB" oraxdb:defaultTableSchema="MYUSER">
      <xs:complexType oraxdb:SQLType="action752_T" oraxdb:SQLSchema="MYUSER">
        <xs:sequence>
          <xs:element ref="type" oraxdb:propNumber="3786" oraxdb:global="false" oraxdb:SQLName="type" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false"/>
          <xs:element maxOccurs="unbounded" ref="param" oraxdb:propNumber="3787" oraxdb:global="false" oraxdb:SQLName="param" oraxdb:SQLType="param749_T" oraxdb:SQLSchema="MYUSER" oraxdb:memType="258" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false" oraxdb:SQLCollType="param753_COLL" oraxdb:SQLCollSchema="MYUSER"/>
          <xs:element ref="actionSubId" oraxdb:propNumber="3788" oraxdb:global="false" oraxdb:SQLName="actionSubId" oraxdb:SQLType="NUMBER" oraxdb:memType="2" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false"/>
          <xs:element ref="time" oraxdb:propNumber="3789" oraxdb:global="false" oraxdb:SQLName="time" oraxdb:SQLType="NUMBER" oraxdb:memType="2" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="type" type="xs:string" oraxdb:propNumber="3791" oraxdb:global="true" oraxdb:SQLName="type" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:defaultTable="type751_TAB" oraxdb:defaultTableSchema="MYUSER"/>
    <xs:element name="param" oraxdb:propNumber="3794" oraxdb:global="true" oraxdb:SQLName="param" oraxdb:SQLType="param749_T" oraxdb:SQLSchema="MYUSER" oraxdb:memType="258" oraxdb:defaultTable="param750_TAB" oraxdb:defaultTableSchema="MYUSER">
      <xs:complexType oraxdb:SQLType="param749_T" oraxdb:SQLSchema="MYUSER">
        <xs:sequence>
          <xs:element minOccurs="0" ref="value" oraxdb:propNumber="3792" oraxdb:global="false" oraxdb:SQLName="value" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false"/>
          <xs:element ref="key" oraxdb:propNumber="3793" oraxdb:global="false" oraxdb:SQLName="key" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="value" type="xs:string" oraxdb:propNumber="3795" oraxdb:global="true" oraxdb:SQLName="value" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:defaultTable="value748_TAB" oraxdb:defaultTableSchema="MYUSER"/>
    <xs:element name="key" type="xs:string" oraxdb:propNumber="3796" oraxdb:global="true" oraxdb:SQLName="key" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:defaultTable="key747_TAB" oraxdb:defaultTableSchema="MYUSER"/>
    <xs:element name="actionSubId" type="xs:integer" oraxdb:propNumber="3797" oraxdb:global="true" oraxdb:SQLName="actionSubId" oraxdb:SQLType="NUMBER" oraxdb:memType="2" oraxdb:defaultTable="actionSubId746_TAB" oraxdb:defaultTableSchema="MYUSER"/>
    <xs:element name="time" type="xs:integer" oraxdb:propNumber="3798" oraxdb:global="true" oraxdb:SQLName="time" oraxdb:SQLType="NUMBER" oraxdb:memType="2" oraxdb:defaultTable="time745_TAB" oraxdb:defaultTableSchema="MYUSER"/>
    <xs:element name="reservationType" type="xs:string" oraxdb:propNumber="3799" oraxdb:global="true" oraxdb:SQLName="reservationType" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:defaultTable="reservationType744_TAB" oraxdb:defaultTableSchema="MYUSER"/>
    <xs:element name="softwareVersion" type="xs:string" oraxdb:propNumber="3800" oraxdb:global="true" oraxdb:SQLName="softwareVersion" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:defaultTable="softwareVersion743_TAB" oraxdb:defaultTableSchema="MYUSER"/>
    <xs:element name="eventId" type="xs:string" oraxdb:propNumber="3801" oraxdb:global="true" oraxdb:SQLName="eventId" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:defaultTable="eventId742_TAB" oraxdb:defaultTableSchema="MYUSER"/>
    <xs:element name="vin" type="xs:string" oraxdb:propNumber="3802" oraxdb:global="true" oraxdb:SQLName="vin" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:defaultTable="vin741_TAB" oraxdb:defaultTableSchema="MYUSER"/>
  </xs:schema>
  
  
  
  
  

  How can I create an index on these tables of the ordered collection to improve performance?

  I found the example at http://docs.Oracle.com/CD/E11882_01/AppDev.112/e23094/xdb_rewrite.htm#ADXDB5859 but am not able to apply to this particular case...

  Thank you in advance...

  If the schema is not annotated and XS: Integer and XS: String are mapped to types of data NUMBER and VARCHAR2 (4000), so you must use in your query to avoid typecasting unnecessary operations.

  You must also use XMLTABLEs chained when accessing a parent/child instead of a FLWOR expression relationship, otherwise the CBO cannot rewrite the XQuery query correctly (maybe it's fixed in the latest version).

  If you make these changes, the plan should show the cleaner predicates:

  SQL > SELECT EVENT_ID, MESSAGE_ID, ACTION_TYPE, ACTION_SUB_ID, ACTION_TIMESTAMP

  2 FROM test_table

  3 XMLTABLE ('/ monitoring ')

  4 COLUMNS XML_CONTENT OF PASSAGE

  5 WAY of VARCHAR2 (4000) EVENT_ID "ID."

  6 actions for XMLTYPE PATH 'action '.

  (7) T1,

  8 XMLTABLE ('/ action')

  Shares of PASSAGE 9 COLUMNS

  NUMBER of ACTION_SUB_ID 10 PATH "actionSubId."

  11 PATH of VARCHAR2 (4000) ACTION_TYPE "type."

  12 WAY of NUMBER ACTION_TIMESTAMP 'time '.

  (13) T2

  14 WHERE EVENT_ID IS NOT NULL

  15 AND ACTION_SUB_ID IS NOT NULL

  16;

  Execution plan

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

  Hash value of plan: 1763884463

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

  | ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time |

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

  |   0 | SELECT STATEMENT |                 |   109.   220K |     6 (17). 00:00:01 |

  |   1.  THE MERGE JOIN.                 |   109.   220K |     6 (17). 00:00:01 |

  |*  2 |   TABLE ACCESS BY INDEX ROWID | TEST_TABLE |    11.   352.     2 (0) | 00:00:01 |

  |   3.    INDEX SCAN FULL | SYS_C007567 |    11.       |     1 (0) | 00:00:01 |

  |*  4 |   JOIN TYPE.                 |   109.   216K |     4 (25) | 00:00:01 |

  |*  5 |    TABLE ACCESS FULL | T_OR_MON_ACTION |   106 S 216K |     3 (0) | 00:00:01 |

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

  Information of predicates (identified by the operation identity card):

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

  2 - filter("TEST_TABLE".") (' SYS_NC00012$ ' IS NOT NULL)

  4 - access("SYS_ALIAS_0".") NESTED_TABLE_ID "=" TABLE_TEST. " ("' SYS_NC0000800009$ ')

  filter ("SYS_ALIAS_0". "NESTED_TABLE_ID"="TABLE_TEST" "." " ("SYS_NC0000800009$")

  5 - filter("SYS_ALIAS_0"." actionSubId» IS NOT NULL)

  Note

  -----

  -dynamic sample used for this survey (level = 2)

  Now, if it is still necessary, everything boils down to choosing a technique for index NULL values:

  -composite index with a column not zero or constant

  -FBI

  -bitmap image

  Choose the one that best fits your data, the selectivity and activity on the tables.

• Creating INDEX on a BLOB column in a separate tablespace

  Hello

  
  

  Our database contains 2 storage spaces :

  -Tablespace DATA : is reserved to hold the data.

  -Tablespace INDX: is reserved to hold the index.

  
  

  For some reason, that we must create the indexes on columns of type blob and the pending order are:

  SQL > CREATE INDEX my_index ON DOC_CONTENTS (doc_content) INDEXTYPE IS CTXSYS. CONTEXT;  / / doc_content a blob type.

  SQL> index created
  

  Now, all indexes are created in the tablespace for DATA that is not good, they should be created in the tablespace INDX (now is empty)

  For this reason, and after a search, I specified the tablespace INDX , which will contain the index, and the used command is:
  

  SQL > CREATE INDEX my_index ON DOC_CONTENTS (doc_content) INDEXTYPE IS CTXSYS. CONTEXT TABLESPACE INDX;

  *

  ERROR on line 1:

  ORA-29850: invalid option for creating domain index

  NB: also, when I try to use the same command with varchar column, it works.

  SQL > CREATE INDEX my_index ON DOC_CONTENTS (doc_name) TABLESPACE INDX;  / / doc_content a type VARCHAR2.

  SQL> index created

  
  

  Do you have an idea on how to create indexes on a blob column in a different tablespace?

  This question has nothing to do with the Oracle objects, but is related to Oracle Text, then perhaps that some moderator moves text objects.

  To specify a storage space for a ctxsys.context Oracle Text index domain index tables, you must create a storage preference, specify storage spaces in attributes of this preference, then use this preference in settings of creating index.  Please see the example below which shows first create domain index tables in the default users tablespace, then the creation of the field tables to be indexed in the example tablespace.

  Scott@orcl_11gR2 >-test environment:

  Scott@orcl_11gR2 > doc_contents CREATE TABLE

  2 (doc_content BLOB)

  3.

  Table created.

  Scott@orcl_11gR2 > INSERT INTO doc_contents VALUES

  2 (UTL_RAW. CAST_TO_RAW ("test data"))

  3.

  1 line of creation.

  Scott@orcl_11gR2 >-create domain index tables in default users tablespace:

  Scott@orcl_11gR2 > my_index CREATE INDEX

  2 doc_contents (doc_content)

  3 INDEXTYPE IS CTXSYS. FRAMEWORK

  4.

  The index is created.

  Scott@orcl_11gR2 > SELECT index_name, nom_tablespace

  2 FROM user_indexes

  3. WHERE index-name LIKE '% MY_INDEX % '.

  4.

  INDEX_NAME TABLESPACE_NAME

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

  MY_INDEX

  DR.$ MY_INDEX$ X USERS

  2 selected lines.

  Scott@orcl_11gR2 > SELECT table_name, nom_tablespace

  2 FROM user_tables

  3 WHERE table_name LIKE '% MY_INDEX % '.

  4.

  TABLE_NAME, TABLESPACE_NAME

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

  DR. MY_INDEX$ I HAVE USERS

  USERS R DR$ MY_INDEX$

  DR.$ MY_INDEX$ N

  DR.$ MY_INDEX$ K

  4 selected lines.

  Scott@orcl_11gR2 >-creating the tables index field in example of tablespace:

  Scott@orcl_11gR2 > my_index DROP INDEX

  2.

  The index is deleted.

  Scott@orcl_11gR2 > start

  2 ctx_ddl.create_preference ("mystore', 'BASIC_STORAGE'");

  3 ctx_ddl.set_attribute ("mystore', 'I_TABLE_CLAUSE',")

  4 "tablespace storage example (original 1 K) ');

  5 ctx_ddl.set_attribute ("mystore', 'K_TABLE_CLAUSE',")

  6 "tablespace storage example (original 1 K) ');

  7 ctx_ddl.set_attribute ("mystore', 'R_TABLE_CLAUSE',")

  8 ' lob tablespace storage example (original 1 K)

  9 (data) store as (storage off in row cache)');

  10 ctx_ddl.set_attribute ("mystore', 'N_TABLE_CLAUSE',")

  11 "tablespace storage example (original 1 K) ');

  12 ctx_ddl.set_attribute ("mystore', 'I_INDEX_CLAUSE',")

  13 ' example of tablespace storage (initial 1 K) compress 2 ');

  14 ctx_ddl.set_attribute ("mystore', 'P_TABLE_CLAUSE',")

  15 "tablespace storage example (original 1 K) ');

  16 ctx_ddl.set_attribute ("mystore', 'S_TABLE_CLAUSE',")

  17 "tablespace storage example (original 1 K) ');

  18 end;

  19.

  PL/SQL procedure successfully completed.

  Scott@orcl_11gR2 > my_index CREATE INDEX

  2 doc_contents (doc_content)

  3 INDEXTYPE IS CTXSYS. FRAMEWORK

  4 PARAMETERS ('STORAGE mystore')

  5.

  The index is created.

  Scott@orcl_11gR2 > SELECT index_name, nom_tablespace

  2 FROM user_indexes

  3. WHERE index-name LIKE '% MY_INDEX % '.

  4.

  INDEX_NAME TABLESPACE_NAME

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

  MY_INDEX

  DR.$ MY_INDEX$ X FOR EXAMPLE

  2 selected lines.

  Scott@orcl_11gR2 > SELECT table_name, nom_tablespace

  2 FROM user_tables

  3 WHERE table_name LIKE '% MY_INDEX % '.

  4.

  TABLE_NAME, TABLESPACE_NAME

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

  DR. MY_INDEX$ I EXAMPLE

  DR.$ MY_INDEX$ R EXAMPLE

  DR.$ MY_INDEX$ N

  DR.$ MY_INDEX$ K

  4 selected lines.

  Post edited by: BarbaraBoehmer (corrected for error due to the already existing preference)

• 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

• alternative to delete and re-create indexes

  Hi all
  
  We use Oracle 11.2.0.2. We have a script where we fall before the full update of a table, the indexes and re-create indexes to improve performance.
  
  Rather than a drop and recreate indexes, I wanted to know if there's another approach better to achieve performance gains.
  
  I thought make unusable index and rebuild later. Would it not be better to drop and re-create the index.
  
  Thanks for your time.

  >
  I thought make unusable index and rebuild later. Would it not be better to drop and re-create the index.
  >
  This is exactly the right strategy to use. He does need to get the benefit of the performance, and there is no danger of inadvertently re-create the index with the wrong settings or in the wrong table space.

  See understanding when to use unusable index or Invisible in the DBA Guide
  http://docs.Oracle.com/CD/E11882_01/server.112/e25494/indexes002.htm#CIHJIDJG
  >
  Unusable index

  An unusable index is ignored by the optimizer, and is not maintained by DML. One of the reasons to make an unusable index are to improve the performance of loading in bulk. (Loads in bulk, go faster if the database is not required to manage the index when inserting rows.) Instead of letting fall the index and later re-creation, requiring you to remember the exact parameters of the CREATE INDEX statement, you can make the index unusable and then rebuild.

• Strange behavior when creating a composite with ' without validating key. '

  Hi all
  
  It's very strange for me. Can you please tell me where I am wrong.
  
  I want to create a composite key for the combination "INT_ID" and "STO_ID" columns in the table "act_ord". because this table contains already more entries in double for this combination, I decided to use 'enable novalidate' to skip validation for records duplicate already existing while creating constraints. But I get the following error "ORA-02260: table can have only one primary key" executing the below statement 1.1. If I create a 1 column with option novalidate constraint means, its working fine.
  

  1.1 Not working:- Giving error ORA-02260: table can have only one primary key
  ALTER TABLE ACT_ORD ADD CONSTRAINT PK_INT_ORD
   PRIMARY KEY   (INT_ID,STO_ID) enable novalidate 

  1.2 Working without any error:
  ALTER TABLE SPL_VAS.ACT_ORDER ADD CONSTRAINT PK_INT_STO_ORD
   PRIMARY KEY   (INT_ID) enable novalidate

  Is there a limitation of use 'enable novalidate' with the creation of composite primary key?
  
  Please take the necessary steps and make your suggestions.
  
  Kind regards
  Jame

  It is clear to me why you get this error. Here's a unit test where I get a different error (more logical).

  Note: to do this, you must first create a NON-unique index on the columns that you want to be in the primary key. Then use the clause for INDEXING to HELP when you add the primary key.

  SQL> create table test (i number not null, j number not null);
  
  Table created.
  
  SQL> insert into test values(0,0);
  
  1 row created.
  
  SQL> insert into test values(0,0);
  
  1 row created.
  
  SQL> commit;
  
  Commit complete.
  
  SQL> select *  from test;
  More...
  
           I          J
  ---------- ----------
           0          0
           0          0
  
  2 rows selected.
  
  SQL> alter table test add primary key (i,j) enable novalidate;
  alter table test add primary key (i,j) enable novalidate
  *
  ERROR at line 1:
  ORA-02437: cannot validate (TOON.SYS_C0028830) - primary key violated
  
  SQL> create index my_pk_index on test(i,j);
  
  Index created.
  
  SQL> alter table test add primary key (i,j) using index my_pk_index enable novalidate;
  
  Table altered.
  
  SQL> insert into test values(1,1);
  
  1 row created.
  
  SQL> insert into test values(1,1);
  insert into test values(1,1)
  *
  ERROR at line 1:
  ORA-00001: unique constraint (TOON.SYS_C0028831) violated
  
  SQL>