ORA-01480 aborts index creation/syncronization

I have a intermedia index and I have got an error creating the
index.
I you run this script, you will see the problem:
drop table test_ferran;
create table test_ferran (id number primary key, txt clob);
create index ctx_test_ferran
on test_ferran(txt) indextype is ctxsys.context
parameters ('nopopulate section group
ctxsys.auto_section_group');
insert into test_ferran values(1,
'<bbb
b<ccccccccccccccccccccccccccccccccc<ddddddddddddddddddddddddd
<e>'
commit;
begin
ctx_ddl.sync_index('CTX_TEST_FERRAN');
end;
ORA-20000: Error d'interMedia Text:
DRG-50857: oracle error in dreii0fsh
ORA-01480: manca el carScter nul a la cua de la cadena STR
ORA-06512: a "CTXSYS.DRUE", line 126
ORA-06512: a "CTXSYS.CTX_DDL", line 1298
ORA-06512: a line 2
In this other case (just adding a space) there is no problem:
drop table test_ferran;
create table test_ferran (id number primary key, txt clob);
create index ctx_test_ferran
on test_ferran(txt) indextype is ctxsys.context
parameters ('nopopulate section group
ctxsys.auto_section_group');
insert into test_ferran values(1,
'<bbb b<cc
ccccccccccccccccccccccccccccccc<ddddddddddddddddddddddddd <e>'
commit;
begin
ctx_ddl.sync_index('CTX_TEST_FERRAN');
end;
The error is not reported in ctx_errors. Oracle just abort the
index creation,
why?
.

Just tried your test on 9i and works. Which db/platform are you
using?
SQL> create index ctx_test_ferran
on test_ferran(txt) indextype is ctxsys.context 2
3 parameters ('nopopulate section group
ctxsys.auto_section_group');
Index created.
SQL> insert into test_ferran values(1,
'<bbb 2
3
b<ccccccccccccccccccccccccccccccccc<ddddddddddddddddddddddddd
4 <e>');
1 row created.
SQL> commit;
Commit complete.
SQL> exec ctx_ddl.sync_index('CTX_TEST_FERRAN');
PL/SQL procedure successfully completed.

Similar Messages

  • ORA-1652: Index creation error

    At the time of table re-organisation, Index creation got aborted for the secondary index creation. then we have continued our activity leaving the index creation due to short of System downtime.
    Again we have run the sql statment when the sap system is up, then it has thrown an error:
    ORA-1652 unable to extend temp segment by 128 in tablespace PSAPTEMP.
    In the current system, we are not ready to increase the size of datafile or resizing.where it leads to the increase the size of database.
    Here we have option to create a new temp tablespace, will delete after index creation, but while doing this how do we point the new tablespace which is created for this activity.
    SAP 4.6c oracle 9 sun solaris.
    Kindly advise what can be done. reply ASAP

    Martin,
    We have discussed with the team like,
    1. Create new temporary tablespace with desired Size which should be minimum 25GB
                CREATE temporary tablespace PSAPTEMP1......
        2. If the original tablespace is a default temporary tablespace, set the new tablespace as default temporary tablespace in the database.
                 SQL> alter database default temporary tablespace PSAPTEMP1;
        3. Perform the index creation
        4. Make the old tablespace PSAPTEMP as the default temporary tablespace.
                 SQL> alter database default temporary tablespace PSAPTEMP
       5. Drop the new tablespace.
                 SQL> drop tablespace temp including contents.
    Here I have a question, while switching the default temporary tablespace from PSAPTEMP to the much bigger new PSAPTEMP1Tablespace whether this will affect the running transaction.
    Any impact on switching the tablespace online..?
    We are performing this activity in the online system(running sap system)
    Thanks,

  • Spatial query index creation fails with ORA-13282: failure on initializatio

    Hi,
    I have an Oracle 10g 10.2.0.5.0 database newly installed. Spatial index creation fails:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-13282: failure on initialization of coordinate transformation
    ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
    The script I am trying to run is:
    Insert into USER_SDO_GEOM_METADATA
    (TABLE_NAME, COLUMN_NAME, DIMINFO, SRID)
    Values
    ('SOME_TABLE', 'geo',
    "SDO_DIM_ARRAY"(
    "SDO_DIM_ELEMENT"('X',600000,900000,0.001),
    "SDO_DIM_ELEMENT"('Y',150000,400000,0.001)), 23700);
    CREATE INDEX IX_GEO_SOME_TABLE ON SOME_TABLE (GEO) INDEXTYPE IS MDSYS.SPATIAL_INDEX ;
    Earlier I had some issues with NLS settings in relation to Spatial, but in this particular case setting the NLS_LANG for AMERICAN_AMERICA does not help. I found this comment http://www.orafaq.com/forum/t/127312/2/ but would not like to hack around with MDSYS table content. Any help is highly appreciated.
    Regards, Tamas

    Tamas,
    1 . . .Are you indexing a table that already has geometries or an empty table?
    . . . .If the former, do all the geometries in that table have the same (not NULL) SRID (23700)?
    2 . .The link you posted suggests a parsing problem since in Hungarian (23700), the decimal seperator is a comma (not a period). Accordingly, I believe the edit to mdsys.sdo_cs_srs.WKTEXT would be:
    PROJCS["HD72 / EOV", GEOGCS [ "HD72", DATUM ["Hungarian Datum 1972 (EPSG ID 6237)", SPHEROID ["GRS 1967 (EPSG ID 7036)", 6378160, 298,247167427]], PRIMEM [ "Greenwich", 0,000000 ], UNIT ["Decimal Degree", 0,01745329251994328]], PROJECTION ["Egyseges Orszagos Vetuleti (EPSG OP 19931)"], UNIT ["Meter", 1]]
                                                                                                                                         ^                                    ^                                   ^                                                                                                  Regards,
    Noel

  • Error while running index creation

    Hi All ,
    I am running index creation step like below .
    alter session enable parallel DDL;
    alter session set workarea_size_policy=manual;
    alter session set sort_area_size=250000000;
    alter session set db_file_multiblock_read_count=128;
    CREATE INDEX "CUST_ROUTE_IDX" ON "CUST_2_K2K" ("PP2S", "KK2S")
    PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING
    STORAGE( INITIAL 5M
    NEXT 16777216
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    PCTINCREASE 0
    FREELISTS 1
    FREELIST GROUPS 1
    BUFFER_POOL DEFAULT)
    TABLESPACE "INDX" PARALLEL 2;
    when i am running like above i am getting following error..
    CREATE INDEX "CUST_ROUTE_IDX" ON "CUST_ROUTE_IDX" ("PP2S", "KK2S")
    **ERROR at line 1:**
    **ORA-00604: error occurred at recursive SQL level 1**
    **ORA-04031: unable to allocate 38410272 bytes of shared memory ("large**
    **pool","SEQ$","QERHJ hash-joi","kllcqc:kllcqslt")**
    DB is ORA 10gR2 installed on 8 cpu machine with 32 GB of RAM . From Unix Top command i can understand that 18GB of RAM is free.
    When i remove "alter session set sort_area_size=250000000;" and run above script no error is coming .
    But enough memory is availabe to the machine as per UNIX . Can any one help me out why this err is coming .
    Also when I do " show parameter sort_area_size " in any new sqlplus session it displays 65536
    This value is in bytes/KB/MB ...pls advice
    Thanks in Advance

    Please read any error message carefully, prior to posting.
    **ORA-04031: unable to allocate 38410272 bytes of shared memory (*"large**
    **pool"*,"SEQ$","QERHJ hash-joi","kllcqc:kllcqslt")**
    Oracle is trying to allocate memory in the large pool, and the large pool is too small.
    The sort_area_size has nothing to do with it.
    Also there is no gain in setting the work_policy to manual, as Oracle will allocate memory beyond pga_aggregate_target automagically.
    There is also no gain in setting db_file_multiblock_read_count, as Oracle will adjust that automagically.
    Sort_area_size is in bytes, as documented, and it is your value in the spfile/init.ora which is the default or which you have set.
    You can read about this in the documentation which is online at http://tahiti.oracle.com
    Sybrand Bakker
    Senior Oracle DBA

  • Strange: Conditional Error in Intermedia Text Index Creation

    Hi All,
    I am facing a strange error while creating the Intermedia Text index on 8.1.6 release for NT 4.0.
    I have one database instance installed on the server. When i connect to Oracle through SQL plus as: connect username/password;
    The index creation works fine!
    But, if i connect using: username/password@servicename;
    The index creation does not work!
    The following error occurs.
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000:intermedia Text error:
    ORA-50704:Net8 listener is not running or cannot start external procedures
    ORA-28575:unable to open RPC connection to external procedure agent
    ORA-12154:TNS:could not resolve service name
    ORA-06512:at "CTXSYS.DRUE", line 126
    ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 54
    ORA-06512:at line 1
    Could anyone please help as to why it works without when connected without the service name but not otherwise?
    Thanking you in advance!
    Thanks and Regards
    Anurag Agarwal

    Hi All,
    I am facing a strange error while creating the Intermedia Text index on 8.1.6 release for NT 4.0.
    I have one database instance installed on the server. When i connect to Oracle through SQL plus as: connect username/password;
    The index creation works fine!
    But, if i connect using: username/password@servicename;
    The index creation does not work!
    The following error occurs.
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000:intermedia Text error:
    ORA-50704:Net8 listener is not running or cannot start external procedures
    ORA-28575:unable to open RPC connection to external procedure agent
    ORA-12154:TNS:could not resolve service name
    ORA-06512:at "CTXSYS.DRUE", line 126
    ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 54
    ORA-06512:at line 1
    Could anyone please help as to why it works without when connected without the service name but not otherwise?
    Thanking you in advance!
    Thanks and Regards
    Anurag Agarwal

  • Parallel Index creation takes more time...!!

    OS - Windows 2008 Server R2
    Oracle - 10.2.0.3.0
    My table size is - 400gb
    Number of records - 657,45,95,123
    my column definition first_col varchar2(22) ; -> I am creating index on this column
    first_col -> actual average size of column value is 10
    I started to create index on this column by following command
    CREATE INDEX CALL_GROUP1_ANO ON CALL_GROUP1(A_NO) LOCAL PARALLEL 8 NOLOGGING COMPRESS ;
    -> In my first attempt after three hours I got an error :
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
    So I increased the size of temp tablespace to 380GB ,Because i expect the size of first_col index this much.
    -> In my second attempt Index creation is keep going even after 17 hours...!!
    Now the usage of temp space is 162 GB ... still it is growing..
    -> I checked EM Advisor Central ADDM :
    it says - The PGA was inadequately sized, causing additional I/O to temporary tablespaces to consume significant database time.
    1. why this takes this much of Temp space..?
    2. It is required this much of time to CREATE INDEX in parallel processing...? more than 17 hrs
    3. How to calculate and set the size of PGA..?

    OraFighter wrote:
    Oracle - 10.2.0.3.0
    My table size is - 400gb
    Number of records - 657,45,95,123
    my column definition first_col varchar2(22) ; -> I am creating index on this column
    first_col -> actual average size of column value is 10
    I started to create index on this column by following command
    CREATE INDEX CALL_GROUP1_ANO ON CALL_GROUP1(A_NO) LOCAL PARALLEL 8 NOLOGGING COMPRESS ;
    Now the usage of temp space is 162 GB ... still it is growing..The entire data set has to be sorted - and the space needed doesn't really vary with degree of parallelism.
    6,574,595,123 index entries with a key size of 10 bytes each (assuming that in your choice of character set one character = one byte) requires per row approximately
    4 bytes row overhead 10 bytes data, 2 bytes column overhead for data, 6 bytes rowid, 2 bytes column overhead for rowid = 24 bytes.
    For the sorting overheads, using the version 2 sort, you need approximately 1 pointer per row, which is 8 bytes (I assumed you're on 64 bit Oracle on this platform) - giving a total of 32 bytes per row.
    32 * 6,574,595,123 / 1073741824 = 196 GB
    You haven't said how many partitions you have, but you might want to consider creating the index unusable, then issuing a rebuild command on each partition in turn. From "Practical Oracle 8i":
    <blockquote>
    In the absence of partitioned tables, what would you do if you needed to create a new index on a massive data set to address a new user requirement? Can you imagine the time it would take to create an index on a 450M row table, not to mention the amount of space needed in the temporary segment. It's the sort of job that you schedule for Christmas or Easter and buy a couple of extra discs to add to the temporary tablespace.
    With suitably partitioned tables, and perhaps a suitably friendly application, the scale of the problems isn't really that great, because you can build the index on each partition in turn. This trick depends on a little SQL feature that appears to be legal even though I haven't managed to find it in the SQL reference manual:
         create index big_new_index on partitioned_table (colX)
         local
         UNUSABLE
         tablespace scratchpad
    The key word is UNUSABLE. Although the manual states that you can 'alter' an index to be unusable, it does not suggest that you can create it as initially unusable, nevertheless this statement works. The effect is to put the definition of the index into the data dictionary, and allocate all the necessary segments and partitions for the index - but it does not do any of the real work that would normally be involved in building an index on 450M rows.
    </blockquote>
    (The trick was eventually documented a couple of years after I wrote the book.)
    Regards
    Jonathan Lewis

  • Error in index creation: null

    Hi,
    I have a problem when I try to create an index.
    The message I get is: Could not create the index: null
    But apparently the index is created. I try to add data sources but then i get portal runtime error.
    Looking in TREX monitor the Queue is created (obviously without any entries).
    And finally when I try to create a taxonomy (after choosing Trex Search and Classification service in index creation) the new button doesn't appear!
    Could anyone give a clue?
    Thanks in advance.
    Guillermo.

    Please visit Google and issue
    ora-29833 site:oracle.com
    Kindly do this with every error you get.
    Sybrand Bakker
    Senior Oracle DBA

  • R-tree index creation error

    I'm getting the following error when trying to create an r-tree index:
    create index new_gps_idx on gis.new_gps (geometry) indextype is mdsys.spatial_index PARAMETERS('TABLESPACE=INDX')
    ERROR at line 1:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-06512: at line 1
    I get the error regardless of which tablespace I specify.
    I can however create fixed quad-tree indexes with the following command, in the same tablespace:
    create index new_gps_idx on gis.new_gps (geometry) indextype is mdsys.spatial_index PARAMETERS('SDO_LEVEL=4');
    The error is defined as:
    ORA-29855 error occurred in the execution of ODCIINDEXCREATE routine
    Cause: Failed to successfully execute the ODCIIndexCreate routine.
    Action: Check to see if the routine has been coded correctly.
    I have created one r-tree index on a large spatial table, 5633 geometries, in the INDX tablespace. I am not able to create another one.
    The INDX tablespace is only 2% used and its size is 200MB.
    Any help would be greatly appreciated.
    Dave
    null

    Hi David,
    Can you try applying the patch (if you haven't already)? Unfortunately I can't rememeber the details of what the symptoms were, and although the patch kit describes a fix there is no corresponding bug in Oracle's bug database. If I remember correctly there was a bug in the values the r-tree code was using for intermediate (temporary) tables created during r-tree index creation.
    Sorry I can't pin this down for you.
    dan

  • Intermedia text index creation error

    My intermedia text was working fine, but now when create one index, it failed and it gave me the following error message:
    ERROR at line 1:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: ConText error:
    ORA-06520: PL/SQL: Error loading external library
    ORA-06522: ld.so.1: extprocPLSExtProc: fatal: libskgxp8.so: open failed: No such file or directory
    ORA-06512: at "CTXSYS.DRUE", line 122
    ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 34
    ORA-06512: at line 1
    The listener itself is fine, is it because some library need to be re-created?
    null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Alexander Bogomolov ([email protected]):
    I've installed Intermedia text. During sample index creation i've get following error messages:
    ORA-06520: PL/SQL: Error loading external library
    ORA-06522: Unable to load DLL
    ORA-06512: at "CTXSYS.DRUE", line 126
    ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 54
    ORA-06512: at line 1...
    seems to be incorrect NET8 settings. How can I solve this problem?
    thanks.
    Sorry for bad English. regards!<HR></BLOCKQUOTE>
    *** check your listener.ora file
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = oracle_home)
    (PROGRAM = extproc)
    (SID_DESC =
    (GLOBAL_DBNAME = global dbname)
    (ORACLE_HOME = oracle_home)
    (SID_NAME = sidname)
    for the correct location of extproc
    null

  • XML DB Index creation problem

    We are facing issues in creating index on XMLTYPE elements. In the below example, when we try to create index on "/PurchaseOrder/LineItems/LineItem/Description" element, its throwing "ORA-29036: This feature is not supported" error. It is allowing us to create index on Description element if we remove "maxOccurs="unbounded" attribute either in "LineItem" element or "Part" element. Please provide pointers on this issue. Below are the sample code for schema, table and index creation.
    DECLARE
    XMLSCHEMADOC VARCHAR2(32767);
    BEGIN
    XMLSCHEMADOC := '
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb"
    version="1.0" xdb:storeVarrayAsTable="true">
    <xs:element name="PurchaseOrder" type="PurchaseOrderType"/>
    <xs:complexType name="PurchaseOrderType">
    <xs:sequence>
    <xs:element name="Reference" type="ReferenceType"/>
    <xs:element name="Actions" type="ActionsType"/>
    <xs:element name="Reject" type="RejectionType" minOccurs="0"/>
    <xs:element name="Requestor" type="RequestorType"/>
    <xs:element name="User" type="UserType"/>
    <xs:element name="CostCenter" type="CostCenterType"/>
    <xs:element name="ShippingInstructions" type="ShippingInstructionsType"/>
    <xs:element name="SpecialInstructions" type="SpecialInstructionsType"/>
    <xs:element name="LineItems" type="LineItemsType"/>
    </xs:sequence>
    </xs:complexType>
    <xs:complexType name="LineItemsType">
    <xs:sequence>
    <xs:element name="LineItem" type="LineItemType" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    <xs:complexType name="LineItemType">
    <xs:sequence>
    <xs:element name="Description" type="DescriptionType"/>
    <xs:element name="Part" type="PartType" maxOccurs="unbounded"/>
    </xs:sequence>
    <xs:attribute name="ItemNumber" type="xs:integer"/>
    </xs:complexType>
    <xs:complexType name="PartType">
    <xs:attribute name="Id">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:minLength value="10"/>
    <xs:maxLength value="14"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="Quantity" type="moneyType"/>
    <xs:attribute name="UnitPrice" type="quantityType"/>
    </xs:complexType>
    <xs:simpleType name="ReferenceType">
    <xs:restriction base="xs:string">
    <xs:minLength value="18"/>
    <xs:maxLength value="30"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:complexType name="ActionsType">
    <xs:sequence>
    <xs:element name="Action" maxOccurs="4">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="User" type="UserType"/>
    <xs:element name="Date" type="DateType" minOccurs="0"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    <xs:complexType name="RejectionType">
    <xs:all>
    <xs:element name="User" type="UserType" minOccurs="0"/>
    <xs:element name="Date" type="DateType" minOccurs="0"/>
    <xs:element name="Comments" type="CommentsType" minOccurs="0"/>
    </xs:all>
    </xs:complexType>
    <xs:complexType name="ShippingInstructionsType">
    <xs:sequence>
    <xs:element name="name" type="NameType" minOccurs="0"/>
    <xs:element name="address" type="AddressType" minOccurs="0"/>
    <xs:element name="telephone" type="TelephoneType" minOccurs="0"/>
    </xs:sequence>
    </xs:complexType>
    <xs:simpleType name="moneyType">
    <xs:restriction base="xs:decimal">
    <xs:fractionDigits value="2"/>
    <xs:totalDigits value="12"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="quantityType">
    <xs:restriction base="xs:decimal">
    <xs:fractionDigits value="4"/>
    <xs:totalDigits value="8"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="UserType">
    <xs:restriction base="xs:string">
    <xs:minLength value="1"/>
    <xs:maxLength value="10"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="RequestorType">
    <xs:restriction base="xs:string">
    <xs:minLength value="0"/>
    <xs:maxLength value="128"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="CostCenterType">
    <xs:restriction base="xs:string">
    <xs:minLength value="1"/>
    <xs:maxLength value="4"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="VendorType">
    <xs:restriction base="xs:string">
    <xs:minLength value="0"/>
    <xs:maxLength value="20"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="PurchaseOrderNumberType">
    <xs:restriction base="xs:integer"/>
    </xs:simpleType>
    <xs:simpleType name="SpecialInstructionsType">
    <xs:restriction base="xs:string">
    <xs:minLength value="0"/>
    <xs:maxLength value="2048"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="NameType">
    <xs:restriction base="xs:string">
    <xs:minLength value="1"/>
    <xs:maxLength value="20"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="AddressType">
    <xs:restriction base="xs:string">
    <xs:minLength value="1"/>
    <xs:maxLength value="256"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="TelephoneType">
    <xs:restriction base="xs:string">
    <xs:minLength value="1"/>
    <xs:maxLength value="24"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="DateType">
    <xs:restriction base="xs:date"/>
    </xs:simpleType>
    <xs:simpleType name="CommentsType">
    <xs:restriction base="xs:string">
    <xs:minLength value="1"/>
    <xs:maxLength value="2048"/>
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="DescriptionType">
    <xs:restriction base="xs:string">
    <xs:minLength value="1"/>
    <xs:maxLength value="256"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:schema>
    DBMS_XMLSCHEMA.registerSchema(
         SCHEMAURL => 'purchaseorder1.xsd',
         SCHEMADOC => XMLSCHEMADOC,
              LOCAL => TRUE,
              GENTYPES => TRUE,
              GENTABLES => TRUE,
              genbean => FALSE,
              enablehierarchy => 1,
              force => FALSE);
    END;
    CREATE TABLE PURCHASEORDER (
    PURCHASE_ORDER_ID NUMBER PRIMARY KEY,
    PURCHASE_ORDER_CONTENTS XMLType
    XMLTYPE COLUMN PURCHASE_ORDER_CONTENTS
    XMLSCHEMA "purchaseorder1.xsd"
    ELEMENT "PurchaseOrder"
    VARRAY PURCHASE_ORDER_CONTENTS."XMLDATA"."LineItems"."LineItem"
    STORE AS table ACTION_TABLE
    ((primary key (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$))
    organization index overflow);
    create index po_lineitem_org_idx on PURCHASEORDER(extractValue(PURCHASE_ORDER_CONTENTS,'/PurchaseOrder/LineItems/LineItem/Description'));

    Hi,
    Thanks for your reply. Please find below my issues
    issue 1 : (index creation using extractvalue)
    I am able to create index on Description element if I remove maxoccurs="unbounded" from Part element. I am not able to understand, how i am able to create index if I remove maxoccurs="unbounded" from its sibiling.
    issue 2 : (Creating an Index for Direct Access to an Ordered Collection Table)
    When i tried to create table i am getting the following error.
    SQL> CREATE TABLE PURCHASEORDER (
    2 PURCHASE_ORDER_ID NUMBER PRIMARY KEY,
    3 PURCHASE_ORDER_CONTENTS XMLType
    4 )
    5 XMLTYPE COLUMN PURCHASE_ORDER_CONTENTS
    6 XMLSCHEMA "purchaseorder1.xsd"
    7 ELEMENT "PurchaseOrder"
    8 VARRAY PURCHASE_ORDER_CONTENTS."XMLDATA"."LineItems"."LineItem"
    9 STORE AS table LINEITEM_TABLE
    10 ((primary key (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$)))
    11 VARRAY PURCHASE_ORDER_CONTENTS."XMLDATA"."LineItems"."LineItem"."Part"
    12 STORE AS table PART_TABLE
    13 ((primary key (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$)));
    VARRAY PURCHASE_ORDER_CONTENTS."XMLDATA"."LineItems"."LineItem"."Part"
    ERROR at line 11:
    ORA-22809: nonexistent attribute
    Please provide pointers.

  • Errors in index creation

    Hi,
    I'm using Oracle Intermedia on Oracle 8.1.7.0.0 to index some columns of type LONG.
    During the index creation I'm having some errors with some tables:
    [type 1 error]
    ERROR at line 1:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: interMedia Text error:
    DRG-50857: oracle error in drekalc startid
    DRG-50858: OCI error: OCI_NO_DATA
    ORA-06512: at "CTXSYS.DRUE", line 126
    ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 78
    ORA-06512: at line 1
    [type 2 error]
    ERROR at line 1:
    ORA-03113: end-of-file on communication channel
    In this second case the result is also that I'm no longer connected to Oracle.
    Do you have some hints?
    Patchset 2 can solve these problems?
    Best Regards. Riccardo Girardi

    There has been some bugs with LONG so try to get the latest patchset. I suggest going to 8.1.7.4

  • Help needed in index creation and its impact on insertion of records

    Hi All,
    I have a situation like this, and the process involves 4 tables.
    Among the 4 tables, 2 tables have around 30 columns each, and the other 2 has 15 columns each.
    This process contains validation and insert procedure.
    I have already created some 8 index for one table, and an average of around 3 index on other tables.
    Now the situation is like, i have a select statement in validation procedure, which involves select statement based on all the 4 tables.
    When i try to run that select statement, it takes around 30 secs, and when checked for plan, it takes around 21k memory.
    Now, i am in a situation to create new index for all the table for the purpose of this select statement.
    The no.of times this select statement executes, is like, for around 1000 times of insert into table, 200 times this select statement gets executed, and the record count of these tables would be around one crore.
    Will the no.of index created in a table impacts insert statement performace, or can we create as many index as we want in a table ? Which is the best practise ?
    Please guide me in this !!!
    Regards,
    Shivakumar A

    Hi,
    index creation will most definitely impact your DML performance because when inserting into the table you'll have to update index entries as well. Typically it's a small overhead that is acceptable in most situations, but the only way to say definitively whether or not it is acceptable to you is by testing. Set up some tests, measure performance of some typical selects, updates and inserts with and without an index, and you will have some data to base your decision on.
    Best regards,
    Nikolay

  • Fast index creation suggestions wanted

    Hi:
    I've loaded a table with a little over 100,000,000 records. The table has several indexes which I must now create. Need to do this as fast as possible.
    I've read the excellent article by Don Burleson (http://www.dba-oracle.com/oracle_tips_index_speed.htm) but still have a few questions.
    1) If the table is not partitioned, does it still make sense to use "parallel"?
    2) The digit(s) following "compress" indicate the number of consective columns at the head of the index that have duplicates. True?
    3) How will the compressed index effect query performance (vs not compressed) down the line?
    4) In the future I will be doing lots and lots of updates on the indexed columns of the records as well as lots of record deletes and inserts into/out-of the table. Will these updates/inserts/deletes run faster or slower given that the indexes are compressed vs if they were not?
    5) In order to speed up the sorting, is it better to add datafiles to the TEMP table or create more TEMP tables (remember, running "parallel")
    Thanks in Advance

    There are people who would argue that excellent and Mr. Burleson do not belong in the same sentence.
    1) Yes, you can still use parallel (and nologging) to create the index, but don't expect 20 - 30 times faster index creation.
    2) It is the number of columns to compress by, they may not neccesarily have duplicates. For a unique index the default is number of columns - 1, for a non-unique index the default is the number of columns.
    3) If you do a lot of range scans or fast full index scans on that index, then you may see some performance benefit from reading fewer blocks. If the index is mostly used in equality predicates, then the performance benefit will likely be minimal.
    4) It really depends on too many factors to predict. The performance of inserts, updates and deletes will be either
    A) Slower
    B) The same
    C) Faster
    5) If you are on 10G, then I would look at temporary tablespace groups which can be beneficial for parallel operations. If not, then allocate as much memory as possible to sort_area_size to minimize disk sorts, and add space to your temporary tablespace to avoid unable to extend. Adding additional temporary tablespaces will not help because a user can only use one temporary tablespace at a time, and parallel index creation is only one user.
    You might want to do some searching at Tom Kyte's site http://asktom.oracle.com for some more responsible answers. Tom and Don have had their disagreements in the past, and in most of them, my money would be on Tom to be corerct.
    HTH
    John

  • Party Merge ORA-29861: domain index is marked LOADING/FAILED/UNUSABLE

    Hi gurus,
    i am using 11.5.10.2 on linux.
    while running the party merge concurrent program , we are getting below error, please help.
    Errors in Merge :
    Application: Receivables_
    Error: Merge failed in Receivables (HZ_STAGED_PARTY_SITES ) with the following error message:
    This unexpected SQL error occurred during the merge process :
    ORA-29861: domain index is marked LOADING/FAILED/UNUSABLE
    The following record was being handled when the error occurred :
    Thanks
    RB

    Thanks Hussain, this is similer to the error i got, i will run the steps and get back to you, once again thanks for your prompt responce.
    Thx
    RB
    Edited by: R12DBA on Jul 23, 2010 4:36 PM
    Edited by: R12DBA on Jul 23, 2010 4:50 PM

  • Index creation failed in Business Objects Explorer

    Hi,
    I installed the Business Objects Explorer ...
    But I can not index anything.
    When I try to index the following message appears:
    "Server, DRWBI001.PolestarIndexing, generated messages The Following:
    Index creation failed. File system Polestar exceptions occurred on the server. Search for Polestar ERROR Within the servers log file for more details. (Can not create directory C: \ Program Files \ Business Objects \ BusinessObjects Enterprise 12.0 \ win32_x86 \ \ Index \ DRWBI001.PolestarIndexing \ InProgress \ ExplorationIndexes \ 35e98114-4831-A254-8dad-497fd3d4bb26 \-30_10.09.41 2010-06. 564) "
    What should I do? help me please

    I do not have UNIVERSE.
    I'm trying to index files like Microsoft excel.
    I have to do some configuration in the CMC to be able to crawl in Business Objects Explorer?
    What should I do to crawl in Business Objects Explorer?

Maybe you are looking for