Updating interMedia Index

Hi,
I need to know if there's an aitomated way of updating the interMedia index in Portal 3.0.9 (other than dropping the index and re-creating it from the UI). Is there any in-built program for performing the same action.
Thanks in advance.
Regards,
Jatinder

When you have created your Portal intermedia indexes and add a file item, this is not indexed automatically. You
cannot yet search on it. You have to recreate the Portal intermedia indexes, or you can schedule to synchronize
them.
You can download the file ctx_schedule from technet.
Step for automatic synchronization:
1. Install the package ctx_schedule (ctx_schedule.sql) in schema ctxsys.
2. Schedule to synchronize the Portal intermedia indexes every minute, and optimize them every 120 minutes.
Run script START_PORTAL_INDEX_REFRESH.SQL in ctxsys schema.
To stop the automatic synchronization run script STOP_PORTAL_INDEX_REFRESH.SQL.

Similar Messages

  • Auto sync is possible for intermedia indexes?

    HI gurus
    I understand that normally a database job or cron job has to be created to periodically sync the intermedia indexes.
    Is there a way to create indexes in intermedia so that the indexes updated automatically Just like normal index (without any job?)
    Regards
    Bhaskara

    Please ask questions about Oracle Text (formerly interMedia text) in the Oracle Text forum. You will get a quilcker, more expert answer there.

  • Intermedia index creation error

    Hi,
    I am getting the following error while importing a table with intermedia index on it.
    error occured in execution of ODCIINDEXCREATE routine.
    intermedia text error : Lost RPC connection to external procedure agent.
    at CTXSYS.DRUE
    at CTXSYS.TEXTINDEXMETHODS
    Any help is appreciated.
    thanks,
    Manish.

    We are encountering this error, too. On my local server, running 8.1.6 on Win2k on a laptop, I can create indexes successfully. We have a range of content, including Office 200 file types, html , text, etc.
    The column being indexed is LONG RAW. I believe we are using patch 8.1.6.3 already. We are eager to resolve this problem.

  • Error while rebuilding InterMedia index

    While executing "alter index ABC.SAMPLE_INTERMEDIA_INDEX rebuild online parameters( 'sync memory 45M' );", we encounter the following error:
    java.sql.SQLException: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: interMedia Text error:
    DRG-50857: oracle error in drekmap (execute insert)
    ORA-01562: failed to extend rollback segment number 6
    ORA-01650: unable to extend rollback segment RBS06 by 130 in tablespace RBS
    My configuration is as follows:
    Oracle 8i (8.1.7.3)
    SEGMENT TBLSPC INITIAL_EX NEXT_EX MIN_EX MAX_EX STATUS
    SYSTEM SYSTEM 57344 57344 2 505 ONLINE
    RBS01 RBS 1048576 1048576 40 32765 ONLINE
    RBS02 RBS 1048576 1048576 40 32765 ONLINE
    RBS03 RBS 1048576 1048576 40 32765 ONLINE
    RBS04 RBS 1048576 1048576 40 32765 ONLINE
    RBS05 RBS 1048576 1048576 40 32765 ONLINE
    RBS06 RBS 1048576 1048576 40 32765 ONLINE
    RBS07 RBS 1048576 1048576 40 32765 ONLINE
    TBLSPC INITIAL_EX NEXT_EX MIN_EX MAX_EX
    RBS 1048576 1048576 40 505
    Questions:
    1. What is the relationship between the RBS parameters and the operation to rebuild the intermedia index?
    2. How do we optimally set up our RBS parameters OR organize the "alter index rebuild" command to not run into such issues?
    Thanks in advance.

    I would set up a large rollback segment (eg "BIGROLL") and offline all but BIGROLL before doing the rebuild.
    Tom Best

  • Too many recursive statements in PRO*C in comparing to SQLPLUS for Intermedia Index.

    Hi,
    I hope someone can help about this Problem. I don't know ehther its Intermedia Index or Database Problem...
    The following Query;
    SELECT SCORE(1),D.DOCUMENT_ID,DOCU_DATE_NUM,DOC_TYPE_ID
    FROM
    DOCUMENT D WHERE CONTAINS(SEARCH_INDEX,:b1,1) > 0 ORDER BY SCORE(1) DESC,
    DOCU_DATE_NUM DESC
    takes approx 7 sec in SQLPLUS , but in PRO*C it takes approx 55 sec. They call the same PL/SQL Stored Proc including the SQL above returning REF Cursor.
    In PROC*C running Program the Trace file contains 139 Statements of:
    SELECT/*+INDEX(T "DR$DOCXML_IX$X")*/ DISTINCT TOKEN_TEXT FROM "GETINFO"."DR$DOCXML_IX$I" T WHERE TOKEN_TEXT LIKE :lkexpr and TOKEN_TYPE NOT IN (1, 2, 5)
    but in SQLPLUS generated Trace File it has only 18 of the Statement.
    The TKPROF Report for PRO*C is:
    SELECT SCORE(1),D.DOCUMENT_ID,DOCU_DATE_NUM,DOC_TYPE_ID
    FROM
    DOCUMENT D WHERE CONTAINS(SEARCH_INDEX,:b1,1) > 0 ORDER BY SCORE(1) DESC,
    DOCU_DATE_NUM DESC
    call count cpu elapsed disk query current rows
    Parse 1 0.00 0.00 0 0 0 0
    Execute 1 33.37 33.72 3 94 0 0
    Fetch 44 0.04 0.04 29 69 4 43
    total 46 33.41 33.76 32 163 4 43
    For SQLPLUS:
    SELECT SCORE(1),D.DOCUMENT_ID,DOCU_DATE_NUM,DOC_TYPE_ID
    FROM
    DOCUMENT D WHERE CONTAINS(SEARCH_INDEX,:b1,1) > 0 ORDER BY SCORE(1) DESC,
    DOCU_DATE_NUM DESC
    call count cpu elapsed disk query current rows
    Parse 1 0.01 0.01 0 0 0 0
    Execute 1 4.36 4.37 0 0 0 0
    Fetch 44 0.02 0.02 10 44 0 43
    total 46 4.39 4.40 10 44 0 43
    Why is there so much difference? Even if they both do HARD Parse for the SQL above or run the same Stored Proc many times with "ALTER SESSION SET SESSION_CACHED_CURSORS=10", the difference in Time is the same.
    Can someone help about this, I think it is an important Tuning Problem for Intermedia Index or ORACLE Bug maybe...

    Hi,
    Thanks for answering.
    Yes I'm sure , both of them are using the same bind variables and it is:
    (FUZZY($INTERNATIONAL) AND FUZZY($JOURNAL) AND FUZZY($ELECTRONICS) AND FUZZY($COMMUNICATIONS)) WITHIN SERIES_TITLE';
    The same Query takes too long in Unix SQL*PLUS (~ 54 secs) also, but in Windows SQL*PLUS its faster (~ 7 secs).
    Bu t if I chabe the Bind Variable as :
    STR := '(($INTERNATIONAL OR ?INTERNATIONAL) AND ($JOURNAL OR ?JOURNAL) AND ($ELECTRONICS OR ?ELECTRONICS) AND ($COMMUNICATIONS OR ?COMMUNICATIONS)) WITHIN SERIES_TITLE';
    then its in both Environment faster and nearly the same. But its not the same as the previous one.
    I think the problem is when using the search as ?$<Word> (Fuzzy Stem together). But not everytime. Do you think its a Bug?

  • JSF problem -  An internal error occurred during: "Updating JSP Index".

    Hello Friends,
    I am facing following problem in ecplise. Whenever I open JSP page or whenever I save my jsp page.
    !ENTRY org.eclipse.core.jobs 4 2 2008-06-14 13:54:24.151
    !MESSAGE An internal error occurred during: "Updating JSP Index".
    !STACK 0
    java.lang.NoClassDefFoundError: javax/servlet/jsp/tagext/TagLibraryInfo
         at org.eclipse.jst.jsp.core.internal.taglib.TaglibHelperCache.createNewHelper(TaglibHelperCache.java:112)
         at org.eclipse.jst.jsp.core.internal.taglib.TaglibHelperCache.getHelper(TaglibHelperCache.java:97)
         at org.eclipse.jst.jsp.core.internal.taglib.TaglibHelperManager.getHelperFromCache(TaglibHelperManager.java:43)
         at org.eclipse.jst.jsp.core.internal.taglib.TaglibHelperManager.getTaglibHelper(TaglibHelperManager.java:36)
         at org.eclipse.jst.jsp.core.internal.java.JSPTranslator.addTaglibVariables(JSPTranslator.java:684)
         at org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translateXMLNode(JSPTranslator.java:997)
         at org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translateRegionContainer(JSPTranslator.java:843)
         at org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translate(JSPTranslator.java:734)
         at org.eclipse.jst.jsp.core.internal.java.JSPTranslationAdapter.getJSPTranslation(JSPTranslationAdapter.java:131)
         at org.eclipse.jst.jsp.core.internal.java.search.JSPSearchDocument.getJSPTranslation(JSPSearchDocument.java:112)
         at org.eclipse.jst.jsp.core.internal.java.search.JSPSearchDocument.getPath(JSPSearchDocument.java:149)
         at org.eclipse.jst.jsp.core.internal.java.search.JavaSearchDocumentDelegate.<init>(JavaSearchDocumentDelegate.java:30)
         at org.eclipse.jst.jsp.core.internal.java.search.JSPSearchSupport.createSearchDocument(JSPSearchSupport.java:401)
         at org.eclipse.jst.jsp.core.internal.java.search.JSPSearchSupport.addJspFile(JSPSearchSupport.java:295)
         at org.eclipse.jst.jsp.core.internal.java.search.JSPIndexManager$ProcessFilesJob.run(JSPIndexManager.java:262)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
    I am using Ecplise 3.2.0
    JSF 1.1
    Tomcat 5.5
    JSP2.0
    Any solution for this?
    Thanks & regards
    Abhijai

    Abhijai wrote:
    java.lang.NoClassDefFoundError: javax/servlet/jsp/tagext/TagLibraryInfoThis exception is been thrown if the given class was available in classpath during compile time, but not during run time. The solution is obvious: make sure that the given class (or at least the JAR file with the given class) is available in the classpath during run time.
    By the way, why did you think that this problem is related to JSF?

  • ORA-28579 during Intermedia indexing

    The following error occured during the creation of an Intermedia
    index:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: interMedia Text error:
    ORA-28579: network error during callback from external procedure agent
    ORA-06512: at "CTXSYS.DRUE", line 126
    ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 54
    ORA-06512: at line 1
    Any idea what to do ? This error is reproducable.
    Andreas Jung

    We are encountering this error, too. On my local server, running 8.1.6 on Win2k on a laptop, I can create indexes successfully. We have a range of content, including Office 200 file types, html , text, etc.
    The column being indexed is LONG RAW. I believe we are using patch 8.1.6.3 already. We are eager to resolve this problem.

  • Errors while rebuilding InterMedia index

    While executing "alter index ABC.SAMPLE_INTERMEDIA_INDEX rebuild online parameters( 'sync memory 45M' );", we encounter the following error:
    java.sql.SQLException: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: interMedia Text error:
    DRG-50857: oracle error in drekmap (execute insert)
    ORA-01562: failed to extend rollback segment number 6
    ORA-01650: unable to extend rollback segment RBS06 by 130 in tablespace RBS
    My configuration is as follows:
    Oracle 8i (8.1.7.3)
    SEGMENT TBLSPC INITIAL_EX NEXT_EX MIN_EX MAX_EX STATUS
    SYSTEM SYSTEM 57344 57344     2      505 ONLINE
    RBS01     RBS 1048576 1048576 40 32765 ONLINE
    RBS02     RBS 1048576 1048576 40 32765 ONLINE
    RBS03     RBS 1048576 1048576 40 32765 ONLINE
    RBS04     RBS 1048576 1048576 40 32765 ONLINE
    RBS05 RBS 1048576 1048576 40 32765 ONLINE
    RBS06     RBS 1048576 1048576 40 32765 ONLINE
    RBS07     RBS 1048576 1048576 40 32765 ONLINE
    TBLSPC INITIAL_EX NEXT_EX MIN_EX MAX_EX
    RBS 1048576 1048576 40 505
    Questions:
    1. What is the relationship between the RBS parameters and the operation to rebuild the intermedia index?
    2. How do we optimally set up our RBS parameters OR organize the "alter index rebuild" command to not run into such issues?
    Thanks in advance.

    Please ask this question in the Oracle text (formerly interMedia text) forum.
    You will get a quicker, more expert answer there.

  • "UPDATE GLOBAL INDEXES"를 사용하여, DDL 처리와 동시에 GLOBAL INDEX를 자동 관리하는 방안

    제품 : ORACLE SERVER
    작성날짜 :
    "UPDATE GLOBAL INDEXES"를 사용하여, DDL 처리와 동시에 GLOBAL INDEX를 자동 관리하는 방안
    ==========================================================================================
    PURPOSE
    이 문서에서는 다음과 같은 사항을 기술한다.
    1. 새로 추가된 기능으로, 테이블 파티션에 대한 DDL 수행시
    지정 가능한 "UPDATE GLOBAL INDEXES" 절에 대한 설명
    2. UPDATE GLOBAL INDEXES를 사용하는 것 보다는 REBUILD INDEX를
    사용하여야 하는 성능상의 고려사항.
    SCOPE
    Oracle Partitioning Option은 8~10g Standard Edition에서는 지원하지
    않는다.
    Explanation
    테스트를 위해 먼저 4개의 테이블을 생성한다.
    1. RANGE partitioned table을 생성한 후 GLOBAL index를 만든다:
    SQL> create table orders (
    2 order_no number,
    3 part_no varchar2(40),
    4 ord_date date
    5 )
    6 partition by range (ord_date)
    7 (partition Q1 values less than (TO_DATE('01-APR-1999','DD-MON-YYYY')),
    8 partition Q2 values less than (TO_DATE('01-JUL-1999','DD-MON-YYYY')),
    9 partition Q3 values less than (TO_DATE('01-OCT-1999','DD-MON-YYYY')),
    10 partition Q4 values less than (TO_DATE('03-JAN-2000','DD-MON-YYYY'))
    11 );
    Table created.
    SQL> create index orders_global_idx
    2 on orders(ord_date)
    3 global partition by range (ord_date)
    4 (partition GLOBAL1 values less than (TO_DATE('01-APR-1999','DD-MON-YYYY')
    5 partition GLOBAL2 values less than (TO_DATE('01-SEP-1999','DD-MON-YYYY')
    6 partition GLOBAL3 values less than (TO_DATE('01-DEC-2000','DD-MON-YYYY')
    7 partition GLOBAL4 values less than (MAXVALUE)
    8 );
    Index created.
    SQL> select substr(index_name,1,20) index_name,
    2 substr(partition_name,1,20) part_name,
    3 status
    4 from dba_ind_partitions
    5 where index_name= 'ORDERS_GLOBAL_IDX' order by partition_name;
    INDEX_NAME PART_NAME STATUS
    ORDERS_GLOBAL_IDX GLOBAL1 USABLE
    ORDERS_GLOBAL_IDX GLOBAL2 USABLE
    ORDERS_GLOBAL_IDX GLOBAL3 USABLE
    ORDERS_GLOBAL_IDX GLOBAL4 USABLE
    SQL> insert into orders values (1,100,TO_DATE('02-FEB-1999','DD-MON-YYYY'));
    2. HASH partitioned table을 생성 한 후 GLOBAL index를 만든다:
    SQL> CREATE TABLE emp_hpart(
    2 empno NUMBER(4) NOT NULL,
    3 ename VARCHAR2(10),
    4 sal NUMBER(7,2))
    5 PARTITION BY HASH(sal)
    6 (PARTITION H1, PARTITION H2, PARTITION H3, PARTITION H4);
    Table created.
    SQL> CREATE INDEX emp_global_HASH_idx ON emp_hpart(ename)
    2 GLOBAL PARTITION BY RANGE (ename)
    3 (PARTITION p1 VALUES LESS THAN ('N') ,
    4 PARTITION p2 VALUES LESS THAN (MAXVALUE));
    Index created.
    SQL> select substr(index_name,1,20) index_name,
    2 substr(partition_name,1,20) part_name,status
    3 from dba_ind_partitions
    4 where index_name= 'EMP_GLOBAL_HASH_IDX' order by partition_name;
    INDEX_NAME PART_NAME STATUS
    EMP_GLOBAL_HASH_IDX P1 USABLE
    EMP_GLOBAL_HASH_IDX P2 USABLE
    SQL> insert into emp_hpart values (1,'AAA',100);
    3. COMPOSITE partitioned table을 생성한 후 GLOBAL index를 만든다:
    SQL> CREATE TABLE emp_composite(
    2 empno NUMBER(4) NOT NULL,
    3 ename VARCHAR2(10),
    4 sal NUMBER(6))
    5 PARTITION BY RANGE(empno)
    6 SUBPARTITION BY HASH(sal) SUBPARTITIONS 4
    7 (PARTITION p1 VALUES LESS THAN (50),
    8 PARTITION p2 VALUES LESS THAN (100),
    9 PARTITION p3 VALUES LESS THAN (150),
    10 PARTITION p4 VALUES LESS THAN (MAXVALUE));
    Table created.
    SQL> CREATE INDEX emp_global_composite_idx ON emp_composite(ename)
    2 GLOBAL PARTITION BY RANGE (ename)
    3 (PARTITION p1 VALUES LESS THAN ('N') ,
    4 PARTITION p2 VALUES LESS THAN (MAXVALUE));
    Index created.
    SQL> select substr(index_name,1,20) index_name,
    2 substr(partition_name,1,20) part_name,status
    3 from dba_ind_partitions
    4 where index_name= 'EMP_GLOBAL_COMPOSITE_IDX' order by
    partition_name;
    INDEX_NAME PART_NAME STATUS
    EMP_GLOBAL_COMPOSITE P1 USABLE
    EMP_GLOBAL_COMPOSITE P2 USABLE
    SQL> insert into emp_composite values (1,'AAA',100);
    4. LIST partitioned table을 생성 한 후 GLOBAL index를 만든다:
    SQL> CREATE TABLE locations (
    2 location_id NUMBER, street_address VARCHAR2(80), postal_code
    CHAR(12),
    3 city VARCHAR2(80), state_province CHAR(2), country_id
    VARCHAR2(20))
    4 PARTITION BY LIST (state_province)
    5 (PARTITION region_east
    6 VALUES ('MA','NY','CT','NH','ME','MD','VA','PA','NJ'),
    7 PARTITION region_west
    8 VALUES ('CA','AZ','NM','OR','WA','UT','NV','CO'),
    9 PARTITION region_south
    10 VALUES ('TX','KY','TN','LA','MS','AR','AL','GA'),
    11 PARTITION region_central
    12 VALUES ('OH','ND','SD','MO','IL','MI',NULL,'IA'));
    Table created.
    SQL> create index loc_global_idx
    2 on locations (state_province)
    3 global partition by range (state_province)
    4 (partition p1 values less than ('NV'),
    5 partition p2 values less than (maxvalue));
    Index created.
    SQL> INSERT INTO locations VALUES
    2 ( 1000,'1297 Via Cola di Rie','00989','Roma',NULL,'IT');
    1 row created.
    SQL> select substr(index_name,1,20) index_name,
    substr(partition_name,1,20)
    2 part_name , status
    3 from dba_ind_partitions
    4 where index_name= 'LOC_GLOBAL_IDX' order by partition_name;
    INDEX_NAME PART_NAME STATUS
    LOC_GLOBAL_IDX P1 USABLE
    LOC_GLOBAL_IDX P2 USABLE
    *** 오라클 8/8i : UPDATE GLOBAL INDEXES 절을 사용하지 않았을 때
    SQL> select substr(index_name,1,20) index_name,
    2 substr(partition_name,1,20) part_name,status
    3 from dba_ind_partitions
    4 where index_name= 'ORDERS_GLOBAL_IDX' order by partition_name;
    INDEX_NAME PART_NAME STATUS
    ORDERS_GLOBAL_IDX GLOBAL1 USABLE
    ORDERS_GLOBAL_IDX GLOBAL2 USABLE
    ORDERS_GLOBAL_IDX GLOBAL3 USABLE
    ORDERS_GLOBAL_IDX GLOBAL4 USABLE
    SQL> ALTER TABLE orders DROP PARTITION q2;
    Table altered.
    SQL> select substr(index_name,1,20) index_name,
    substr(partition_name,1,20)
    2 part_name, status
    3 from dba_ind_partitions
    4 where index_name= 'ORDERS_GLOBAL_IDX' order by partition_name;
    INDEX_NAME PART_NAME STATUS
    ORDERS_GLOBAL_IDX GLOBAL1 UNUSABLE
    ORDERS_GLOBAL_IDX GLOBAL2 UNUSABLE
    ORDERS_GLOBAL_IDX GLOBAL3 UNUSABLE
    ORDERS_GLOBAL_IDX GLOBAL4 UNUSABLE
    => Oracle 9i 이전 버젼에서는, partitioned table의 특정 파티션에 대해
    DDL을 수행하면, 해당 파티션이 비어있는 상태가 아니라면,
    GLOBAL index에 대한 상태를 invalidate 시킨다.
    => Oracle 9i에서 UPDATE GLOBAL INDEXES 절을 수행하면, 테이블의
    파티션에 대한 DDL 작업을 수행하는 동안 GLOBAL INDEX에
    대한 관리 작업을 자동으로 수행하게 된다.
    그러나 일부 작업에 대해서는, 위와 같은 작업이 허용되지
    않는다.
    *** UPDATE GLOBAL INDEXES 절과 ADD PARTITION 절의 동시 사용
    1. RANGE partitioned table:
    SQL> ALTER TABLE orders ADD PARTITION q5
    2 values less than (TO_DATE('03-JUN-2000','DD-MON-YYYY'))
    3 UPDATE GLOBAL INDEXES;
    ALTER TABLE orders ADD PARTITION q5
    ERROR at line 1:
    ORA-30564: Index maintainence clause not allowed for ADD partition to
    RANGE
    partitioned tables
    UPDATE GLOBAL INDEXES 절은 다음 경우에만 사용할 수 있다.
    => HASH partitioned table에 partition 추가
    => Composite partitioned table에 subpartition 추가
    | RANGE partitioned table에 일반적인 방식으로 작업 수행 |
    SQL> ALTER TABLE orders ADD PARTITION q5
    2 values less than (TO_DATE('03-JUN-2000','DD-MON-YYYY'));
    Table altered.
    SQL> @sel
    INDEX_NAME PART_NAME STATUS
    ORDERS_GLOBAL_IDX GLOBAL1 USABLE
    ORDERS_GLOBAL_IDX GLOBAL2 USABLE
    ORDERS_GLOBAL_IDX GLOBAL3 USABLE
    ORDERS_GLOBAL_IDX GLOBAL4 USABLE
    2. HASH partitioned table:
    | UPDATE GLOBAL INDEXES절을 HASH partitioned table 에서 사용 |
    | 하지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE emp_hpart ADD PARTITION q5
    2 UPDATE GLOBAL INDEXES;
    Table altered.
    SQL> @sel
    INDEX_NAME PART_NAME STATUS
    EMP_GLOBAL_HASH_IDX P1 USABLE
    EMP_GLOBAL_HASH_IDX P2 USABLE
    3. COMPOSITE partitioned table:
    | UPDATE GLOBAL INDEXES 절을 COMPOSITE partitioned table에서 사용 |
    | 하지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE emp_composite MODIFY PARTITION p1 add subpartition h5
    2 UPDATE GLOBAL INDEXES;
    Table altered.
    SQL> @sel
    INDEX_NAME PART_NAME STATUS
    EMP_GLOBAL_COMPOSITE P1 USABLE
    EMP_GLOBAL_COMPOSITE P2 USABLE
    4. LIST partitioned table
    | LIST partitioned table에 대해서는 일반적인 방법 사용 |
    SQL> alter table locations ADD
    2 partition nomansland values ('XX');
    Table altered.
    SQL> @sel
    INDEX_NAME PART_NAME STATUS
    LOC_GLOBAL_IDX P1 USABLE
    LOC_GLOBAL_IDX P2 USABLE
    *** UPDATE GLOBAL INDEXES 절과 DROP PARTITION절의 동시사용
    1. RANGE partitioned table:
    | UPDATE GLOBAL INDEXES를 RANGE partitioned table에서 사용 |
    | 하지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE orders DROP PARTITION q2 UPDATE GLOBAL INDEXES;
    Table altered.
    2. HASH partitioned table:
    HASH partitioned table에서는 DROP 명령을 수행할 수 없으며,
    COALESCE를 대신 사용함 (문서 마지막 부분을 참조)
    3. COMPOSITE partitioned table:
    | UPDATE GLOBAL INDEXES를 COMPOSITE partitioned table에서 사용하지|
    | 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE emp_composite DROP PARTITION p2
    2 UPDATE GLOBAL INDEXES;
    Table altered.
    4. LIST partitioned table:
    | UPDATE GLOBAL INDEXES를 LIST partitioned table에서 사용하지 |
    | 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> alter table locations DROP PARTITION
    2 region_south
    3 UPDATE GLOBAL INDEXES;
    Table altered.
    *** UPDATE GLOBAL INDEXES 절과 SPLIT PARTITION 절의 동시 사용
    1. RANGE partitioned table
    | UPDATE GLOBAL INDEXES를 RANGE partitioned table에서 사용 |
    | 하지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE orders SPLIT PARTITION q3 AT
    2 (TO_DATE('15-SEP-1999','DD-MON-YYYY'))
    3 INTO (PARTITION q3_1, PARTITION q3_2)
    4 UPDATE GLOBAL INDEXES;
    Table altered.
    2. HASH partitioned table
    HASH partitioned table에서는 SPLIT 명령을 수행할 수 없으며,
    ADD를 대신 사용함 (윗 부분에 기술하였음)
    3. COMPOSITE partitioned table
    | UPDATE GLOBAL INDEXES를 COMPOSITE partitioned table에서 사용하지|
    | 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE emp_composite SPLIT PARTITION p2 AT (80)
    2 INTO (PARTITION p2_1, PARTITION p2_2)
    3 UPDATE GLOBAL INDEXES;
    Table altered.
    4. LIST partitioned tables:
    | UPDATE GLOBAL INDEXES를 LIST partitioned table에서 사용하지 |
    | 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> alter table locations SPLIT PARTITION region_east
    2 VALUES ('MA','NJ')
    3 INTO (PARTITION region_east_1, PARTITION region_east_2)
    4 UPDATE GLOBAL INDEXES;
    Table altered.
    *** UPDATE GLOBAL INDEXES 절과 MERGE PARTITION 절의 동시 사용
    1. RANGE partitioned table
    | UPDATE GLOBAL INDEXES를 RANGE partitioned table에서 사용 |
    | 하지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE orders MERGE PARTITIONS q2, q3 INTO PARTITION q3
    2 UPDATE GLOBAL INDEXES;
    Table altered.
    2. HASH partitioned table
    HASH partitioned table에서는 MERGE 명령을 수행할 수 없으며,
    COALESCE를 대신 사용함 (문서 마지막 부분을 참조)
    3. COMPOSITE partitioned table
    | UPDATE GLOBAL INDEXES를 COMPOSITE partitioned table에서 사용하지|
    | 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE emp_composite MERGE PARTITIONS p1, p2
    2 INTO PARTITION p2
    3 UPDATE GLOBAL INDEXES;
    Table altered.
    4. LIST partitioned table:
    | UPDATE GLOBAL INDEXES를 LIST partitioned table에서 사용하지 |
    | 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> alter table locations MERGE PARTITIONS region_east,region_west
    2 INTO PARTITION region_north
    3 UPDATE GLOBAL INDEXES;
    Table altered.
    *** UPDATE GLOBAL INDEXES 절과 EXCHANGE PARTITION 절의 동시사용
    1. RANGE partitioned tables
    | UPDATE GLOBAL INDEXES를 RANGE partitioned table에서 사용 |
    | 하지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE orders EXCHANGE PARTITION q3 WITH TABLE t_orders
    2 UPDATE GLOBAL INDEXES;
    Table altered.
    If GLOBAL indexes exist on the TABLE of exchange, they are left UNUSABLE:
    SQL> create index t_orders_global_idx
    2 on t_orders(ord_date)
    3 global partition by range (ord_date)
    4 (partition GLOBAL1 values less than (TO_DATE('01-APR-1999','DD-MON-YYY
    Y')),
    5 partition GLOBAL2 values less than (TO_DATE('01-SEP-1999','DD-MON-YYY
    Y')),
    6 partition GLOBAL3 values less than (TO_DATE('01-DEC-1999','DD-MON-YYY
    Y')),
    7 partition GLOBAL4 values less than (MAXVALUE) );
    Index created.
    SQL> ALTER TABLE orders EXCHANGE PARTITION q3 WITH TABLE t_orders
    2 UPDATE GLOBAL INDEXES;
    Table altered.
    SQL> @sel
    INDEX_NAME PART_NAME STATUS
    T_ORDERS_GLOBAL_IDX GLOBAL1 UNUSABLE
    T_ORDERS_GLOBAL_IDX GLOBAL2 UNUSABLE
    T_ORDERS_GLOBAL_IDX GLOBAL3 UNUSABLE
    T_ORDERS_GLOBAL_IDX GLOBAL4 UNUSABLE
    ORDERS_GLOBAL_IDX GLOBAL1 USABLE
    ORDERS_GLOBAL_IDX GLOBAL2 USABLE
    ORDERS_GLOBAL_IDX GLOBAL3 USABLE
    ORDERS_GLOBAL_IDX GLOBAL4 USABLE
    2. HASH partitioned tables
    | UPDATE GLOBAL INDEXES를 HASH partitioned table에서 사용하 |
    | 지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE emp_hpart EXCHANGE PARTITION H1 WITH TABLE t_emp_hpart
    2 UPDATE GLOBAL INDEXES;
    Table altered.
    3. COMPOSITE partitioned tables
    SQL> ALTER TABLE emp_composite EXCHANGE PARTITION p1 WITH TABLE t_emp_composi
    te;
    ALTER TABLE emp_composite EXCHANGE PARTITION p1 WITH TABLE t_emp_composite
    ERROR at line 1:
    ORA-14291: cannot EXCHANGE a composite partition with a non-partitioned table
    | UPDATE GLOBAL INDEXES를 COMPOSITE partitioned table에서 사용하지|
    | 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE emp_composite EXCHANGE SUBPARTITION SYS_SUBP286
    2 WITH TABLE t_emp_composite
    3 UPDATE GLOBAL INDEXES;
    Table altered.
    4. LIST partitioned tables:
    | UPDATE GLOBAL INDEXES를 LIST partitioned table에서 사용하지 |
    | 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE locations EXCHANGE PARTITION region_east
    2 WITH TABLE t_locations
    3 UPDATE GLOBAL INDEXES;
    Table altered.
    *** UPDATE GLOBAL INDEXES절과 MOVE PARTITION 절의 동시사용
    1. RANGE partitioned table
    | UPDATE GLOBAL INDEXES를 RANGE partitioned table에서 사용 |
    | 하지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE orders MOVE PARTITION q3 TABLESPACE example
    2 UPDATE GLOBAL INDEXES;
    Table altered.
    2. HASH partitioned table
    | UPDATE GLOBAL INDEXES를 HASH partitioned table에서 사용 |
    | 하지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE emp_hpart MOVE PARTITION H1 TABLESPACE example
    2 UPDATE GLOBAL INDEXES;
    Table altered.
    3. COMPOSITE partitioned table
    SQL> ALTER TABLE emp_composite MOVE PARTITION p1 TABLESPACE example;
    ALTER TABLE emp_composite MOVE PARTITION p1 TABLESPACE example
    ERROR at line 1:
    ORA-14257: cannot move partition other than a Range or Hash partition
    SQL> ALTER TABLE emp_composite MOVE PARTITION p1 TABLESPACE example
    2 UPDATE GLOBAL INDEXES;
    ALTER TABLE emp_composite MOVE PARTITION p1 TABLESPACE example
    ERROR at line 1:
    ORA-14257: cannot move partition other than a Range or Hash partition
    4. LIST partitioned table
    | UPDATE GLOBAL INDEXES를 LIST partitioned table에서 사용하지 |
    | 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE locations MOVE PARTITION region_east
    2 TABLESPACE TS_DATA1
    3 UPDATE GLOBAL INDEXES;
    Table altered.
    *** UPDATE GLOBAL INDEXES 절과 TRUNCATE PARTITION 절의 동시 사용
    1. RANGE partitioned tables
    | UPDATE GLOBAL INDEXES를 RANGE partitioned table에서 사용 |
    | 하지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE orders TRUNCATE PARTITION q3
    2 UPDATE GLOBAL INDEXES;
    Table truncated.
    2. HASH partitioned tables
    | UPDATE GLOBAL INDEXES를 HASH partitioned table에서 사용 |
    | 하지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE emp_hpart TRUNCATE PARTITION H1
    2 UPDATE GLOBAL INDEXES;
    Table truncated.
    3. COMPOSITE partitioned table
    | UPDATE GLOBAL INDEXES를 COMPOSITE partitioned table에서 사용하지|
    | 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE emp_composite TRUNCATE PARTITION p1
    2 UPDATE GLOBAL INDEXES;
    Table truncated.
    4. LIST partitioned table
    | UPDATE GLOBAL INDEXES를 LIST partitioned table에서 사용하지 |
    | 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE locations TRUNCATE PARTITION region_east
    2 UPDATE GLOBAL INDEXES;
    Table truncated.
    *** UPDATE GLOBAL INDEXES 절과 COALESCE PARTITION 절의 동시사용
    1. RANGE partitioned table
    Range partitioned table에는 coalesce 기능이 지원되지 않음.
    2. HASH partitioned table
    | UPDATE GLOBAL INDEXES를 HASH partitioned table에서 사용 |
    | 하지 않을 경우 global index가 UNUSABLE 상태로 남음 |
    SQL> ALTER TABLE emp_hpart COALESCE PARTITION
    2 UPDATE GLOBAL INDEXES;
    Table altered.
    3. COMPOSITE partitioned table
    Composite partitioned table에 대해서는 coalesce 기능이 지원되지 않음.
    4. LIST partitioned table
    List partitioned table에 대해서는 coalesce 기능이 지원되지 않음.
    *** 성능상의 문제로 인해 UPDATE GLOBAL INDEXES 절을 사용하는 대신
    *** REBUILD INDEX를 사용하여야 할 경우
    UPDATE GLOBAL INDEXES절을 사용할 경우
    1 이전 버전에서는 단순히 invalid 상태로 표시하고 종료되었던 작업이
    인덱스 관리 작업까지 병행해 수행 되므로 partition DDL operation
    작업 수행 시간이 더 오래 걸린다.
    2 DROP, TRUNCATE, EXCHANGE 작업이 더 오래 걸린다. 이전에는 데이터
    딕셔너리상의 정보만을 갱신하는데 반해, UPDATE GLOBAL INDEXES절을
    사용할 경우, partition 내의 모든 row에 대한 scan 작업이 수행
    되기 때문이다.
    3 GLOBAL INDEX에 대한 갱신 작업을 통한 변경 사항이 redo log 및 rollback에
    남게 된다.
    4 row의 갯수가 작을 경우, update global index절을 사용하여 작업하는 것이
    편리하다.
    5 인덱스를 수동으로 rebuild 할 때 까지 애플리케이션 응답 속도가 현격
    하게 저하되는 것을 피할 수 있다.
    INDEX REBUILD를 사용할 경우
    1 전체 인덱스를 rebuild 하면, index가 좀더 효과적으로 구성된다.
    2 인덱스를 rebuild 하면, 사용자가 인덱스에 대한 구성을 수동으로
    변경할 수 있다.
    Example
    Reference Documents
    <Note:139707.1>

  • InterMedia indexing and searching of zipped files

    Hello, I have interMedia successfully configured to index and query a repository of files (MS Word, Excel, PPT, PDFs, txt files)which are located on a file system. My issue is with zip files. I cannot successfully index and search zip files. I've tried zips that contain both ascii(text) and formatted files (doc, ppt), but interMedia seems not to recognize this particular MIME type. Is there a way to have interMedia index and search zip files? Thanks in advance for any assistance.

    You will have more luck with this question if you post it in the Oracle Text forum. This forum is for interMedia (image, audio video).

  • Creating intermedia index is taking too long!!

    creating intermedia index is taking too long. then memory insufficient... system down.
    please help.
    platform: win2000 pro, oracle817
    linux redhat, oracle817

    Use CTX_OUTPUT_START_LOG() to begin logging index requests. Then create an index and see what's going on.
    o.

  • Intermedia indexes : "extproc_connection_data" error and ORA-28575

    1) I have migrated database from Rel2 to Rel3.,
    2) Migration of Db denied to migrate intermedia component,
    rest migration is successfull,
    3) With Rel2, intermedia indexes, lexer etc. were created
    and properly functioning with all default parameters,
    i do not remember any alteration, except the comment of
    mts entries in init.ora file,
    4) While creating intermedia indexes, it
    gives following errors :
    - ORA-20000
    - DRG-50704
    - ORA-28575
    - ORA-06512
    5) While issuing the following command, it returns error:
    > tnsping extproc_connection_data
    TNS-03505 : Failed to resolve name
    Furnishing the details of entries :-
    (A) TNSNAMES.ORA :
    EXTPROC_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)
    (KEY = EXTPROC0)))
    (CONNECT_DATA =
    (SID = PLSExtProc)
    (PRESENTATION = RO)))
    (B) LISTENER.ORA :
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)
    (KEY = EXTPROC0)))
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)
    (HOST = <host_name>)
    (PORT = 1521))))
    (DESCRIPTION =
    (PROTOCOL_STACK =
    (PRESENTATION = GIOP)
    (SESSION = RAW))
    (ADDRESS = (PROTOCOL = TCP)
    (HOST = <host_name>)
    (PORT = 2481))))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\Oracle\Ora81)
    (PROGRAM = extproc))
    (C) SQLNET.ORA :
    NAMES.DEFAULT_DOMAIN = <domain_name>
    SQLNET.AUTHENTICATION_SERVICES= (NTS)
    NAMES.DIRECTORY_PATH=(TNSNAMES, ONAMES, HOSTNAME)
    (D) SNMP_RO.ORA :
    snmp.SID.<sid_name>.matpl = <sid_name>
    snmp.oraclehome.<sid_name>.<domain_name> = d:\oracle\ora81
    snmp.address.<sid_name>.<domain_name> =
    (ADDRESS=(PROTOCOL=BEQ)(PROGRAM=ORACLE)
    (ARGV0=ORACLE<sid_name>)(ARGS='(DESCRIPTION=
    (LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))
    snmp.remoteaddress.<sid_name>.<domain_name> =
    (DESCRIPTION=(ADDRESS_LIST = (ADDRESS =
    (PROTOCOL = TCP)(HOST = <host_name>)
    (PORT =1521)))
    (CONNECT_DATA=(SID=<sid_name>)
    (SERVER=DEDICATED)))

    Thanks Omar, for proper diagnosis.
    Present Database Version in Oracle 8.1.7.0.0 and Oracle 9iAS 1.0.2.1 on Windows NT 4.0 platform.
    Regards,
    Ashwani
    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Omar Alonso:
    Please post db version and platform.<HR></BLOCKQUOTE>
    null

  • Drop Partition update Global Indexes

    hello Gurus,
    what will happen internally when issue a command
    alter table tab_name drop partition part_name update global indexes;
    why my insert statement waiting to complete this task on " cursor: pin S wait on X "
    thanks in advance ..

    Several times i also noticed that wait event for some jobs on 10 2 0 4 on hpux.
    I didn't found out what was the reason.
    It seems this wait event can be easly related to some bugs.
    http://karenmorton.blogspot.com/2008/08/strange-parsing-behavior.html
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm#sthref3012

  • Intermedia index creation error while taking import

    Hi,
    I tried taking an export dump from a intermedia text indexed schema , and re-importing into a new schema. All objects got created except intermedia indexes.
    Please suggest.
    IMP-00017: following statement failed with ORACLE error 6510:
    "BEGIN "
    "ctxsys.driimp.create_index('RESOURCE_SUMMARY_NDX','RESOURCES',USER,"
    "'RESOURCEID','2','RESOURCESUMMARYXML','1',"
    "'2000','48','8130','49',"
    "NULL, NULL, NULL );"
    regards,
    Manish Jain.

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

  • Error creating intermedia index in Portal

    We are running Portal 3.0.6 on Solaris 3.8.
    We are having trouble creating intermedia index. We get the "An unexpected error has occurred (WWS-32100)", when trying to create the index thru the UI.
    We tried metalink's suggestion and executed inctxgrn.sql. The error Persists on the UI, when you click create index.
    We tried to create the index from pl/sql, by executing ctxcrind.sql. we got the following error
    ERROR at line 1:
    ORA-06502: PL/SQL: numeric or value error
    ORA-06512: at "SYS.OWA_UTIL", line 323
    ORA-06512: at "SYS.HTP", line 859
    ORA-06512: at "SYS.HTP", line 974
    ORA-06512: at "SYS.HTP", line 992
    ORA-06512: at "SYS.HTP", line 40
    ORA-06512: at "PORTAL30.WWERR_API_ERROR_UI", line 109
    ORA-06512: at "PORTAL30.WWERR_API_ERROR_UI", line 57
    ORA-06512: at "PORTAL30.WWSBR_STDERR", line 350
    ORA-06512: at "PORTAL30.WWSBR_ERROR", line 8
    ORA-06512: at "PORTAL30.WWV_CONTEXT", line 377
    ORA-20100:
    ORA-06512: at "PORTAL30.WWSBR_STDERR", line 437
    ORA-06512: at "PORTAL30.WWV_CONTEXT", line 218
    ORA-20100:
    ORA-06512: at "PORTAL30.WWSBR_STDERR", line 437
    ORA-06512: at "PORTAL30.WWV_CONTEXT_UTIL", line 39
    ORA-20000: interMedia Text error:
    DRG-12603: CTXSYS does not own user datastore procedure: WWSBR_THING_CTX_41
    ORA-06512: at line 4
    null

    Seems like a package owenership problem.
    I suggest to post the same message in the Portal forum.

Maybe you are looking for

  • Scratch on screen - anybody know how to get rid of it?

    Hi, I have a deep, but superficial scratch on my Macbook air glossy screen. The scratch is only in the film on top of the LCD display and the hardware underneath is not affected. Does any one know of a polish I could use to get rid of the scratch? I

  • Issue regarding Select Query

    Hello experts, I want a join on table ekpo & mbew(for valuation class). But its not working. if valclass is initial. select  aebeln aebelp atxz01 amatnr abukrs awerks a~menge a~mtart b~bklas from  ekpo  as a inner join  mbew as b on bmatnr eq amatnr

  • RE: Payment method for Netting Process.

    Hi Gurus, My client want to activate Payment methods for netting process for their European company codes. Can anyone please help me on how to do customization for the netting process. Please input complete SAP Configuration required for Netting Proc

  • Captions in Lightbox Slideshow Widget

    The metadata in my files have both a Title and a Caption, yet when i Add Images to the Lightbox Slideshow Widget, I am stuck with Lorem Ipsum on every photo. Do I have to add the Captions manually for every image?!

  • Upgrading issues on 10.4.3

    Hi, I have just upgraded to 10.4.3 from the previous version (sorry cant remember the number). After updating, I noticed the following: 1. Verifying permissions-there seemed to be a lot of things to correct. I did it twice and same thing. 2. Running