Problem In Index Creation

Gurus,
I am creating an index as indextype CTXSYS. But it is taking more than 6-7 hrs and still it is running.
Is there any way to see what is happening or i am doing any wrong?
below is the syntax:
CREATE INDEX <INDEX_NAME>
ON table_name(column_name) INDEXTYPE IS
CTXSYS.CONTEXT PARAMETERS
3 (' DATASTORE CONTENT_DIR
4 5 FILTER CTXSYS.INSO_FILTER
6 STORAGE STORAGE_INDX
7 LEXER GLOBAL_LEXER
8 LANGUAGE COLUMN INTERMEDIA_LANGUAGE_COLUMN
9 STOPLIST GLOBAL_STOPLIST
10 SECTION GROUP CTXSYS.AUTO_SECTION_GROUP
11 FORMAT COLUMN FORMAT_TYPE');
Oracle Version:10.2.0.1.0
OS: SunOS 5.10

can you output the content of v$session_longops ? this is a view which gives you all long running sql.
yang

Similar Messages

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.

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

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

Relation between temp tablespace and index creation

Hi,
I have my Oracle database (11gR1) on windows 2008 server R1 64 bit..
This is my development database. i have one table which has more than 2 billion rows , the problem i m facing here is while creating the index on this table i m getting temp segment error , while my temp tablespace size is 32 gb.
Here my doubt is :
1.What will happen in temp tablespace when index is created ? Relation between temp and index creation ?
2. how to create the index on a huge table?
3. What is the meaning og logging and no logging in INDEX creation .
4. how can we over come for these kind of problem and manage the temp TS..
Thanks & Regards,
Vikash Chauradia

add another tempfile?
1.What will happen in temp tablespace when index is created ? Relation between temp and index creation ?
index creation needs sort. how much depends on the size of the index.
2. how to create the index on a huge table?
create an interim (temporary? :)) huge temporary space for the very purpose.
http://docs.oracle.com/cd/B28359_01/server.111/b28310/indexes003.htm#i1006643
3. What is the meaning og logging and no logging in INDEX creation .
nologging means you the creation isnt in the logs so if you need to recover you cant get back to it. when using nologging in a prod env you might do it for performance during a period of heavy dml such as a large index creation and then backup afterwards. common enough.
4. how can we over come for these kind of problem and manage the temp TS..
current tempspace size =X
is X big enough? if yes, cup of tea, if no, make X bigger.
It doesnt matter what X is.

Systemcopy using R3load - Index creation VERY slow

We exported a BW 7.0 system using R3load (newest tools and SMIGR_CREATE_DDL) and now importing it into the target system.
Source database size is ~ 800 GB.
The export was running a bit more than 20 hours using 16 parallel processes. The import is still running with the last R3load process. Checking the logs I found out that it's creating indexes on various tables:
(DB) INFO: /BI0/F0TCT_C02~150 created#20100423052851
(DB) INFO: /BIC/B0000530000KE created#20100423071501
(DB) INFO: /BI0/F0COPC_C08~01 created#20100423072742
(DB) INFO: /BI0/F0COPC_C08~04 created#20100423073954
(DB) INFO: /BI0/F0COPC_C08~05 created#20100423075156
(DB) INFO: /BI0/F0COPC_C08~06 created#20100423080436
(DB) INFO: /BI0/F0COPC_C08~07 created#20100423081948
(DB) INFO: /BI0/F0COPC_C08~08 created#20100423083258
(DB) INFO: /BIC/B0000533000KE created#20100423101009
(DB) INFO: /BIC/AODS_FA00~010 created#20100423121754
As one can see on the timestamps the creation of one index can take an hour or more.
x_cons is showing constant CrIndex reading in parallel, however, the througput is not more than 1 - 2 MB/sec. Those index creation processes are running now since over two days (> 48 hours) and since the .TSK files don't mentioned those indexes any more I wonder how many of them are to be created and how long this will take.
The whole import was started at "2010-04-20 12:19:08" (according to import_monitor.log) so running now since more than three days with four parallel processes. Target machine has 4 CPUs and 16 GB RAM (CACHE_SIZE is 10 GB). The machine is idling though with 98 - 99 %.
I have three questions:
- why does index creation take such a long time? I'm aware of the fact, that the cache may not be big enough to take all the data but that speed is far from being acceptable. Doing a Unicode migration, even in parallel, will lead to a downtime that may not be acceptable by the business.
- why are the indexes not created first and then filled with the data? Each savepoint may take longer but I don't think that it will take that long.
- how to find out which indexes are still to be created and how to estimate the avg. runtime of that?
Markus

i Peter,
I would suggest creating an SAP ticket for this, because these kind of problems are quite difficult to analyze.
But let me describe the index creation within MaxDB. If only one index creation process is active, MaxDB can use multiple Server Tasks (one for each Data Volume) to possibly increase the I/O throughput. This means the more Data Volumes you have configured, the faster the parallel index creation process should be. However, this hugely depends on your I/O system being able to handle an increasing amount of read/write requests in parallel. If one index creation process is running using parallel Server tasks, all further indexes to be created at that time can only utilize one single User Task for the I/O.
The R3load import process assumes that the indexes can be created fast, if all necessary base table data is still present in the Data Cache. This mostly applies to small tables up to table sizes that take up a certain amount of the Data Cache. All indexes for these tables are created right after the table has been imported to make use of the fact, that all the needed data for index creation is still in the cache. Many idexes may be created simultaneously here, but only one index at a time can use parallel Server Tasks.
If a table is too large in relation to the total database size, then its indexes are being queued for serial index creation to be started when all tables were imported. The idea is that the needed base table data would likely have been flushed out of the Data Cache already and so there is additional I/O necessary rereading that table for index creation. And this additional I/O would greatly benefit from parallel Server Tasks accessing the Data Volumes. For this reason, the indexes that are to be created at the end are queued and serialized to ensure that only one index creation process is active at a time.
Now you mentioned that the index creation process takes a lot of time. I would suggest (besides opening an OSS ticket) to start the MaxDB tool 'Database Analyzer' with an interval of 60 seconds configured during the whole import. In addition, you should activate the 'time measurement' to get a reading on the I/O times. Plus, ensure that you have many Data Volumes configured and that your I/O system can handle that additional loag. E.g. it would make no sense to have 25 Server Tasks all writing to a single local disk, I would assume that the disk would become a bottle neck...
Hope my reply was not too confusing,
Thorsten

After index creation infocube is very slow! (don't produce result)

Hello all,
       I have the following problem, on a single cube ZWLPIANIF, after the index creation from manage of cube, the query on this cube is totally unusable because during a lot of time (it's necessary stop the execution) I whait over 30 minutes. When I delete the index the query work fine a little bit slow compared to another cube that have index.
ZWLPIANIF have 1,200,000 record loaded in FULL
from RSPC we made the following step:
deletion index
loading
creation index, the job of creation is completed successfully (in SM21 no log, in ST22 no dump, in SM37 is ok).
This is the details of our system SAP NetWeaver 2004s:
SAP_ABA     700     0016     SAPKA70016
SAP_BASIS     700     0016     SAPKB70016
ST-PI     2008_1_700     0000          -
PI_BASIS     2006_1_700     0006     SAPKIPYM06
SAP_BW     700     0018     SAPKW70018
FINBASIS     600     0013     SAPK-60013INFINBASIS
SEM-BW     600     0013     SAPKGS6013
BI_CONT     703     0011     SAPKIBIIQ1
ST-A/PI     01L_BCO700     0000          -
everyone have some ideas?
REGARDS
Gianvito

Hi,
You can analyse/debug the query through RSRT in execute+debug mode and please check wether the database optimiser chooses the right index that means wether statistics are updated or not.
You can do a reorganise of indexes as well.
Thank you,
Tilak

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

BIA Index creation error due to invalid characters

Hi All,
While creating BIA index on an Infocube the index creation process fails with the following message.
Index for table '/BIC/SSPSEGTXT' is being processed
A character set conversion is not possible.
Parallel indexing process terminated (Task: '4')
Turns out this field is a text field and has characters such as * and + in the description,which is causing this problem.
How do I proceed with the index creation.
Options I have are:
a) Get rid of this field.. Impossible since there are a few queries that require this information.
b) Run the Database scan tool RSI18N_Search to eliminate foreign characters ....but this does not work for me.
Can anyone suggest some other option or a resolution to this problem. Or If anyone has prior experience of working with the program RSI18N_Search please let me know.
Regards
VK

Venkat, Andres,
You can try several things here;
1) This is pretty ugly but in case you need a quick way around. Create another cube w/o that char, load all the data to that cube from the first cube, and start sending daily deltas to both cubes. Of course put the second cube to BWA
2) Delete the master data! When you try deleting the master data (a particular record or records that you identified), mostly you will find out that it's used in a transactional data(in ODS or Cube) therefore it will not allow you to delete those records, unless you delete the records from the cubes first, then try it again. OR you might be lucky that it's not stored in anycube and it will delete it right away!
The right way is the second option, however when you delete data from cubes, ods, it will lock the cube + invalidate aggregates if you have + BWA indexes etc. You need to recreate them again. So try doing it in non-business hours or in your maintenance window.
Cheers
Tansu

Faster Context index creation!!

Hi Experts,
I am new to the concept of CONTEXT in Oracle and I havent worked on it. My problem is that we have monthly process of rebuilding the context index on a table ( varchar column). This process takes about 8hrs. When I created it the last time I increased the sort_area_size parameter for the session to 500M,increased sort_multiblock_read_count and db_file_multiblock_read_count depending upon the OS limitations,and the index was created in 4 hrs. But this is just DBA trick to do things faster and i beleive it can be done more faster.
Can anyone suggest me what are the ways of speeding up the index creation process from the CONTEXT perspective
,like increasing default memory with Ctx_Adm.Set_Parameter ( 'DEFAULT_INDEX_MEMORY', '500M'); .
Also having default_index_memory and sort_area_size as 500, will this take 1000M of memory during the index creation?
Also i read somewhere that before creating index truncating the table DR$INDEX_ERROR will help speeding index creation. Is this right? I think it should not make a difference .
Any suggestion on speeding up the index creation would be helpful. i cannot create the index in parallel as I am running Oracle 8.1.6 and base table is not partitioned.
Thanks.
Ankur

Sorry for posting this question here. I have put in on TEXT forum.

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

INDEX CREATION ERROR IN iFS

Hello i took an export of iFS schema "ifssys" and tried to import into another database with same set of tablespaces. the tables got created but index creation failed with following error msg.
Oracle error 6510 encountered.
Pl/Sql: unhandled user-defined exception
at CTXSYS.DRIUTL
no data found
at CTXSYS.DRIIMP
problem importing metadata for index
INDEXBLOB_I. index creation will be skipped.
Please note i had given connect, resource,dba and ctxapp role to ifssys user.
Kindly suggest.
Manish Jain.
null

Please see response at: http://technet.oracle.com:89/ubb/Forum36/HTML/000661.html

Index creation error while importing

Hello i took an export of iFS schema "ifssys" and tried to import into another database with sample set of tablespaces. the tables got created but index creation failed with following error msg.
Oracle error 6510 encountered.
Pl/Sql: unhandled user-defined exception
at CTXSYS.DRIUTL
no data found
at CTXSYS.DRIIMP
problem importing metadata for index
INDEXBLOB_I. index creation will be skipped.
Please note i had give connect, resource,dba and ctxapp role to ifssys user.
Kindly suggest.
Manish Jain.

Please see reply at:
http://technet.oracle.com:89/ubb/Forum36/HTML/000661.html

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.

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

Problem In Index Creation

Similar Messages

Maybe you are looking for