Mat views

what does the term materialized views implies in oracle database.what is the purpose of using them in the oracle database.please explain me
Regards
Aram

Hi ,
Can you please go through the below link to get complete dtls.
http://download.oracle.com/docs/cd/B10500_01/server.920/a96567/repmview.htm
Thanks,
Rafi

Similar Messages

  • Creating a Mat View having the same name with that of the table name

    Hi everyone,
    After dropping the mat view name "QQ.TRDLN_DIM_MV", I'm trying to re-create it by having the same name as that of the table but I got an error stating that "name is already used by an existing object". How can create a mat view to look like the object owned by schema "GQ", having a name that is the same as that of the table name, without dropping the table?
    OWNER_O OBJECT_TYPE CREATED LAST_DDL_ TIMESTAMP STATUS OBJECT_NAME
    ===
    GQ MATERIALIZED VIEW 05-NOV-08 13-DEC-08 2008-11-05:06:31:46 VALID TRDLN_DIM_MV
    GQ TABLE 05-NOV-08 15-DEC-08 2008-11-05:06:31:00 VALID TRDLN_DIM_MV
    QQ TABLE 17-AUG-07 16-MAR-09 2007-08-17:17:05:21 VALID TRDLN_DIM_MV
    SQL>CREATE MATERIALIZED VIEW QQ.TRDLN_DIM_MV
    2 TABLESPACE FPLC01S
    3 NOCACHE
    4 NOLOGGING
    5 COMPRESS
    6 PARALLEL ( DEGREE 2 INSTANCES 1 )
    7 BUILD IMMEDIATE
    8 REFRESH FORCE ON DEMAND
    9 WITH PRIMARY KEY
    10 AS
    11 select /*+ NO_REWRITE */ trdln_id,
    12 trdln_skid,
    13 trdln_end_date,
    14 first_value(trdln_end_date) over (partition by trdln_id order by trdln_end_date DESC) as MaxDate
    15 from QQ.trdln_dim;
    from QQ.trdln_dim
    ERROR at line 15:
    ORA-00955: name is already used by an existing object
    I appreciate your help. Many thanks in advance!
    Regards,
    Radic

    You'd have to rename the table (using ALTER TABLE tablename RENAME TO othername; ) before you create the MV.
    You can't have both existing with the same name in the same schema.
    What you see in the GQ schema is that the "table" is the underlying table for the Materialized View.
    When you do a CREATE MATERIALIZED VIEW MY_MV AS ...
    Oracle creates two objects with the same name, one being the Materialized View MY_MV and the other being the table MY_MV which is the physical storage. {Remember that a Materialized View is a means of getting a physical representation of a View}.
    In the QQ schema what you have is either
    a. a real Table
    or
    b. an improperly dropped MV, resulting in the underlying Table still present.

  • Need Help in Mat View Creation

    I have the following query to create a mat view
    CREATE MATERIALIZED VIEW IB_CONT1
    REFRESH FAST ON DEMAND WITH ROWID
    AS
      SELECT
            CUST,
            CONSEQ,
            STD,
            ENDD,
            ADD     
    FROM
         ADMIN.CONTACT@IB_DBLINK;But it displays an error as
            ADMIN.CONTACT@IB_DBLINK
    ERROR at line 11:
    ORA-12018: following error encountered during code generation for
    "OWNER"."IB_CONT1"
    ORA-00942: table or view does not existBut when i query the table i displays data.
    SQL> select count(*) from admin.contact@ib_dblink;
      COUNT(*)
          100what could be the reason?
    Any help will be highly appreciated.
    Thanks in advance.

    Try without ROWID option.
    Regards
    RK

  • Error in MAT View Creation

    I am getting an error in creating a mat view.
    SQL> CREATE MATERIALIZED VIEW
    2 MV1
    3 as
    4 select integration_id
    5 from sbolap.w_org_d;
    from zeus.w_org_d
    ERROR at line 5:
    ORA-00942: table or view does not exist
    Here the zeus is the schema i am accessing. At present i am operating in Aegis schema. I have privileges to create Mat Views in my schema and Select privileges in zeus schema.
    Am i missing some thing? Kindly Help.

    I soved it. Actually we didnt have select privileges on proper and required objects.

  • MAT View Creation Performance Issue

    Hello Experts,
    Below query is executing approximately in 1-3 sec.
    select
    COMMITMENT_ID,
    FUNDING_RULE_ID,
    reporting_year||'-'||reporting_period as RepPeriod,
    GET_START_DAY_OF_PERIOD (FUNDING_RULE_ID, reporting_year, reporting_period) START_DAY_OF_PERIODt,
    GET_END_DAY_OF_PERIOD(FUNDING_RULE_ID, reporting_year, reporting_period) END_DAY_OF_PERIOD
    from
      (select
      COMMITMENT_ID,
      FR_ID as FUNDING_RULE_ID,
      COMT_START_DATE,
      --COMT_TERMINATION_DATE,
      GETREPYEARFROMDATE(COMT_START_DATE,FR_ID) as reporting_year,
      GETREPORTINGPERIOD(to_char(COMT_START_DATE, 'mm') ,FR_ID) as  reporting_period
      from
        select
        COMMITMENT_ID,
        COMT_START_DATE,
        --COMT_TERMINATION_DATE,
        COALESCE(CB_FUNDING_RULE_ID,NC_FUNDING_RULE_ID) FR_ID
        from
        (COMMITMENT_TABLE left outer join (CHILD_BENEFICIARY_TABLE left outer join FUNDING_RULE_TABLE a on
        a.FUNDING_RULE_ID = CB_FUNDING_RULE_ID )
        on COMT_BENEFICIARY_REF = CB_BENEFICIARY_REF
        left outer join (NON_CHILD_BENEFICIARY_TABLE left outer join FUNDING_RULE_TABLE b on
        b.FUNDING_RULE_ID = NC_FUNDING_RULE_ID)
        on
         COMT_BENEFICIARY_REF = NC_BENEFICIARY_REF)
    The query is returning 4.5 lacks of rows.
    I want to create a MAT view by using above query and refresh this on daily basis.
    But the MAT view creation is taking more time near about 401sec (6.68min).
    Why the MAT view is taking more time?
    MAT_VIEW
    CREATE MATERIALIZED VIEW "REP_PERIOD_START_END_DATE"
    AS select
    COMMITMENT_ID,
    FUNDING_RULE_ID,
    reporting_year||'-'||reporting_period as RepPeriod,
    GET_START_DAY_OF_PERIOD (FUNDING_RULE_ID, reporting_year, reporting_period) START_DAY_OF_PERIODt,
    GET_END_DAY_OF_PERIOD(FUNDING_RULE_ID, reporting_year, reporting_period) END_DAY_OF_PERIOD
    from
      (select
      COMMITMENT_ID,
      FR_ID as FUNDING_RULE_ID,
      COMT_START_DATE,
      --COMT_TERMINATION_DATE,
      GETREPYEARFROMDATE(COMT_START_DATE,FR_ID) as reporting_year,
      GETREPORTINGPERIOD(to_char(COMT_START_DATE, 'mm') ,FR_ID) as  reporting_period
      from
        select
        COMMITMENT_ID,
        COMT_START_DATE,
        --COMT_TERMINATION_DATE,
        COALESCE(CB_FUNDING_RULE_ID,NC_FUNDING_RULE_ID) FR_ID
        from
        (COMMITMENT_TABLE left outer join (CHILD_BENEFICIARY_TABLE left outer join FUNDING_RULE_TABLE a on
        a.FUNDING_RULE_ID = CB_FUNDING_RULE_ID )
        on COMT_BENEFICIARY_REF = CB_BENEFICIARY_REF
        left outer join (NON_CHILD_BENEFICIARY_TABLE left outer join FUNDING_RULE_TABLE b on
        b.FUNDING_RULE_ID = NC_FUNDING_RULE_ID)
        on
         COMT_BENEFICIARY_REF = NC_BENEFICIARY_REF)
    Is there any way to make the MAT view creation within 3 minutes?

    CREATE MATERIALIZED VIEW "REP_PERIOD_START_END_DATE"
    AS
    with tab as
    select /*+ materialize */ commitment_id,
                           comt_start_date,
                           --COMT_TERMINATION_DATE,
                           coalesce (cb_funding_rule_id, nc_funding_rule_id)
                              fr_id
                      from (      commitment_table
                               left outer join
                                  (   child_beneficiary_table
                                   left outer join
                                      funding_rule_table a
                                   on a.funding_rule_id = cb_funding_rule_id)
                               on comt_beneficiary_ref = cb_beneficiary_ref
                            left outer join
                               (   non_child_beneficiary_table
                                left outer join
                                   funding_rule_table b
                                on b.funding_rule_id = nc_funding_rule_id)
                            on comt_beneficiary_ref = nc_beneficiary_ref)
    select commitment_id,
           funding_rule_id,
           reporting_year || '-' || reporting_period as repperiod,
           get_start_day_of_period (funding_rule_id,
                                    reporting_year,
                                    reporting_period)
              start_day_of_periodt,
           get_end_day_of_period (funding_rule_id,
                                  reporting_year,
                                  reporting_period)
              end_day_of_period
      from (select commitment_id,
                   fr_id as funding_rule_id,
                   comt_start_date,
                   --COMT_TERMINATION_DATE,
                   getrepyearfromdate (comt_start_date, fr_id) as reporting_year,
                   getreportingperiod (to_char (comt_start_date, 'mm'), fr_id)
                      as reporting_period
              from tab);

  • Unable to refresh Mat View

    BANNER (ADB)
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    BANNER (MDB)
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    Hello everyone,
    I'm unable to refresh a mat view in MDB which is based on ADB. Even just after creating it everytime the refresh fails.
    Currently I'm re-creating the mat view daily and then point the synonym to new one.
    There are no errors thrown in session. It just times out.
    Below is the script for the same.
    CREATE MATERIALIZED VIEW MDB.MV_APRP_DTL_JUN02
    TABLESPACE MCCI_DATA
    BUILD IMMEDIATE
    USING INDEX
    REFRESH FAST START WITH SYSDATE+12/24 NEXT SYSDATE+1
    WITH ROWID
    AS
    SELECT /*+ PARALLEL (APREP_DTL,6) */ * FROM prp.aprep_dtl@mdb_adb prep_del_dtl;
    Can anybody tell me how can I atleast find what and where the problem is ?
    Thanks
    Jitu J K

    If you currently are dropping and recreating the MV, you don't need the MV Log.
    Drop and recreate the MV Log before you recreate the MV and then retest performance of FAST refresh's. A 600MB MV Log does mean that something has gone wrong. Do you / Did you have other MVs that were also extracting data from the same base table(s) ? If those MVs have stopped refreshing but did not unregister, the MV Log will continue to grow and your current MV's FAST refresh performance will suffer.
    See Oracle Support Note#1031924.6 and
    http://hemantoracledba.blogspot.com/2007/01/large-growing-snapshot-logs-indicate.html
    Note : Before you drop the MV log confirm that there are no other MVs (in the same database or a remote database) that are built on the same base table(s).
    Hemant K Chitale

  • Which sys view has whether a mat. view is logging or nologging

    I am looking for the view that contains information about whether a materialized view is set as logging or nologging. I would like most replication to bypass redo logs.

    If you are on 9i onwards you can use DBMS_METADATA. Here an example :
    SCOTT@db102 SQL> select dbms_metadata.get_ddl('MATERIALIZED_VIEW','TEST_EMP','SCOTT') from dual;
    DBMS_METADATA.GET_DDL('MATERIALIZED_VIEW','TEST_EMP','SCOTT')
      CREATE MATERIALIZED VIEW "SCOTT"."TEST_EMP"
      ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOG
    GING
      STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
      PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
      TABLESPACE "USERS"
      BUILD IMMEDIATE
      USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255
      STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
      PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
      TABLESPACE "USERS"
      REFRESH FORCE ON DEMAND
      WITH ROWID USING DEFAULT LOCAL ROLLBACK SEGMENT
      DISABLE QUERY REWRITE
      AS SELECT "NEWEMP"."EMPNO" "EMPNO","NEWEMP"."ENAME" "ENAME","NEWEMP"."JOB" "JO
    B","NEWEMP"."MGR" "MGR","NEWEMP"."HIREDATE" "HIREDATE","NEWEMP"."SAL" "SAL","NEW
    EMP"."COMM" "COMM","NEWEMP"."DEPTNO" "DEPTNO" FROM "NEWEMP"@ORCL "NEWEMP"
    SCOTT@db102 SQL>                                                                                     

  • EXPort (without Mat view logs)

    Hi
    Oracle10g, Win2003
    Is there a way to take EXPort without "materialized view logs", as these logs cause error in IMPort and some time even terminate IMPort.
    It will be equally well for me if i got a way to completely exclude "materialized view & materialized view logs" from EXPort.
    Some one please guide me the way to exclude them from IMP or EXP?
    Wishes

    Additionally when ever I IMPort a user some objects appear in non-compiled state, I compile them with my client tool, but I have to drop and recreate materialized view every time.
    Can come one have an improved way to get IMPort with materialized view?
    Wisehs

  • Problem in Mat view execution through dblinks

    HI Experts,
    I am refreshing MAT_VIEW's via dblinks. But during refresh i am getting below error.
    I tried both with Complete and Fast. Both are getting errors.
    Seems i missed some privilages.
    Please assist me here..
    With Fast option
    *===========*
    SQL> exec dbms_mview.refresh('CDS_BANK_BRANCH_NLD',*'F'*);
    BEGIN dbms_mview.refresh('CDS_BANK_BRANCH_NLD','F'); END;
    ERROR at line 1:
    ORA-12018: following error encountered during code generation for
    "ACCOUNTINFO"."CDS_BANK_BRANCH_NLD"
    ORA-00942: table or view does not exist
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2256
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2462
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2431
    ORA-06512: at line 1
    With Complete Option
    SQL> exec dbms_mview.refresh('CDS_BANK_BRANCH_NLD',*'C'*);
    BEGIN dbms_mview.refresh('CDS_BANK_BRANCH_NLD','C'); END;
    ERROR at line 1:
    ORA-12018: following error encountered during code generation for "ACCOUNTINFO"."CDS_BANK_BRANCH_NLD"
    ORA-00942: table or view does not exist
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2256
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2462
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2431
    ORA-06512: at line 1

    Fran wrote:
    You are calling materialized view at local DB where the m_view doesn't exists. To refer another database through dblink you must use m_view@remote_databaseyou are right , i just notice this :)

  • Create mat view

    Database version = 10.2
    I have a materialized view called BENEFIT_MAT_VIEW. All I have is sqlplus. How do I find out the CREATE MATERIALIZED VIEW DDL statement that was used to create this view ?

    Example :
    TEST@db102 SQL> set long 100000
    TEST@db102 SQL> select dbms_metadata.get_ddl('MATERIALIZED_VIEW','MV_EMP','TEST')
      2  from dual;
    DBMS_METADATA.GET_DDL('MATERIALIZED_VIEW','MV_EMP','TEST')
      CREATE MATERIALIZED VIEW "TEST"."MV_EMP"
      ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOG
    GING
      STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
      PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
      TABLESPACE "USERS"
      BUILD IMMEDIATE
      USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255
      STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
      PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
      TABLESPACE "USERS"
      REFRESH FORCE ON COMMIT
      WITH PRIMARY KEY USING DEFAULT LOCAL ROLLBACK SEGMENT
      DISABLE QUERY REWRITE
      AS SELECT empno,ename
    from emp
    TEST@db102 SQL>                                                                                

  • Best Strategy for Oracle Replication Dataguard/Streams/Mat Views...

    We have a database in Atlanta and a Nat. Office DB in DC. The primary workhorse is the ATL db. The DC office needs to be able to review the most current ATL database data and make small changes to status codes and comment fields (not necessarily on the database but can be if that is the best way). The DC database in the case of network failure/Loss of communication with ATL wants to be able to continue to work on the most current data as of the network failure and resync/or send those changes back to ATL db when the network is restored.
    Iam interested in startegies you would take to accomplish these goals.
    We will be using Oracle 10.2
    Thanks in Advance

    Sounds like a typical Replication Streams use case. DataGuard is not quite in the picture.
    If your remote office only need to replication few tables from ATL, setup Mview based replication seems a good idea.
    Check more information here,
    Oracle® Database Advanced Replication

  • Refresh/Update data in a materialized view

    Hi,
    I have question about the data in a materialized view and how it is refreshed. My mat view has all my dimension-ids and my (for my specialize needs) aggregated measures from my fact table. I used the mat view wizard to create my view - which works perfectly. But now I wonder if I have to create some sort of mapping(?) or some sort of trigger to refresh the data in the mat view. Or is the data automatically refreshed when I start my fact table mappings. I use OWB 11gR2
    thx

    MVs have properties for refresh - you an refresh based on schedules or when dependent data is committed or manually.
    Cheers
    David

  • Exporting data from a materialized view in Oracle 10g

    Can anybody tell me how to export data to a remote server and import data in that remote server without using ftp utility. Actually I want to export the data from a materialized view to the remote server and import the same in the remote server.
    If everything works well, I'll put the exporting and importing in a cronjob.
    Please let me know how can I do that if that's possible .
    Any reply would be appreciated.
    Thanks.

    Here is what I'm trying to do.
    I created materialized views using multiple base tables in my local server and the base tables got populated using a long process.
    Now I want to copy those data alone to some remote server since it doesn't have any base tables in it. For now, the remote server should depends on the localserver's data. I'm going to use the remote server's data for some testing purposes.
    I know it is easy to create mat.views in the remote server but it doesn't have I don't want to do that now. I just want to copy the snapshots from my local server to the remote server.
    Please let me know how to do that.
    Thanks.

  • Altering a table in a materialized view environment

    Hello everybody!.
    My question is as simple as this:
    When I have a single master - multiple materialized views environment , and I want to alter the master table (usually adding a column) , how do I propagate the change to the materialized view sites ?
    In Oracle's documentation manuals it is written the process ONLY for the master sites.If I manually just alter the materialized views to the mat.views sites , the new columns DON'T take data from the master table!
    It would be very nice if someone could help me.
    Thanks everybody on advance!.
    Thanasis Avdis

    Hi,
    you must dorp and recreate materialized view.

  • Issue with fast refresh on a materialized view

    Hi,
    Oracle DB version is 10.2.0.3
    We have a matierialized view created using this script. We have materialized view logs on these six tables.
    By default, it is set to ON COMMIT .
    When a batch job is run every morning (usually 100-200 records) we set it to ON DEMAND and then bring it back to ON COMMIT. It takes around 1-2 minutes.
    If the batch is unusually big, like say 100,000 it takes more than 5 hours to put it back on ON COMMIT. (We analyze the schema (GATHER STALE) before refreshing the MV.) Trace shows deletes taking a long time.
    When I see a big batch, I usually drop the view and recreate it with indexes (there is also a context index). Takes 30 mins to do the whole thing.
    I tried refreshing it COMPLETE when the num of rows is high but it still takes more than 2 hours..(I killed it)
    Is there any way to speed things up without dropping and recreating the MV ?
    thanks
    Mat view creation script:
    CREATE MATERIALIZED VIEW WCC_INTERNAL_SEARCH_M
    TABLESPACE ICV_TS_WCC_DATA
    NOCACHE
    LOGGING
    NOCOMPRESS
    NOPARALLEL
    BUILD IMMEDIATE
    REFRESH FAST ON COMMIT
    WITH ROWID
    AS
    SELECT orgname.ROWID orgname_rowid,
    cnt.ROWID cnt_rowid,
    locgrp.ROWID locgrp_rowid,
    cntry.ROWID cdcntry_rowid,
    addrgrp.ROWID addrgrp_rowid,
    addr.ROWID addr_rowid,
    cnt.cont_id cont_id,
    decode(cntry.name,'US',substr(addr.postal_code,1,5),addr.postal_code) postal_code,
    cntry.name country,
    UPPER(addr.addr_line_one) addr_line_one,
    UPPER(addr.addr_line_two) addr_line_two,
    UPPER(addr.addr_line_three) addr_line_three,
    UPPER(addr.CITY_NAME) city_name,
    UPPER(cnt.CONTACT_NAME) display_name,
    UPPER(orgname.ORG_NAME) org_name,
    addr.prov_state_tp_cd
    FROM orgname,
    contact cnt,
    locationgroup locgrp,
    cdcountrytp cntry,
    addressgroup addrgrp,
    address addr
    WHERE locgrp.cont_id = orgname.cont_id
    AND locgrp.cont_id = cnt.cont_id
    AND addrgrp.location_group_id = locgrp.location_group_id
    AND addr.country_tp_cd = cntry.country_tp_cd
    AND addr.address_id = addrgrp.address_id
    AND cnt.INACTIVATED_DT is null
    AND locgrp.END_DT is null
    AND orgname.END_DT is null
    AND cnt.person_org_code = 'O'
    AND cntry.lang_tp_cd = 100
    AND locgrp.member_ind = 'Y'
    AND locgrp.loc_group_tp_code = 'A'
    ORDER by org_name,city_name,postal_code,country;

    This is the script that creates the preferences and then the context index.
    exec ctx_ddl.create_preference('STEM_FUZZY_PREF', 'BASIC_WORDLIST');
    exec ctx_ddl.set_attribute('STEM_FUZZY_PREF','FUZZY_MATCH','AUTO');
    exec ctx_ddl.set_attribute('STEM_FUZZY_PREF','FUZZY_SCORE','60');
    exec ctx_ddl.set_attribute('STEM_FUZZY_PREF','FUZZY_NUMRESULTS','100');
    exec ctx_ddl.set_attribute('STEM_FUZZY_PREF','STEMMER','AUTO');
    exec ctx_ddl.set_attribute('STEM_FUZZY_PREF', 'wildcard_maxterms',15000) ;
    exec ctx_ddl.create_preference('LEXTER_PREF', 'BASIC_LEXER');
    exec ctx_ddl.set_attribute('LEXTER_PREF','index_stems', 'ENGLISH');
    exec ctx_ddl.set_attribute('LEXTER_PREF','skipjoins',',''."+/-&');
    exec ctx_ddl.create_preference('ICV_WCC_INT_SEARCH_CTX_PREF', 'BASIC_STORAGE');
    exec ctx_ddl.set_attribute('ICV_WCC_INT_SEARCH_CTX_PREF', 'I_TABLE_CLAUSE','tablespace ICV_TS_CTX_IDX');
    exec ctx_ddl.set_attribute('ICV_WCC_INT_SEARCH_CTX_PREF', 'K_TABLE_CLAUSE','tablespace ICV_TS_CTX_IDX');
    exec ctx_ddl.set_attribute('ICV_WCC_INT_SEARCH_CTX_PREF', 'N_TABLE_CLAUSE','tablespace ICV_TS_CTX_IDX');
    exec ctx_ddl.set_attribute('ICV_WCC_INT_SEARCH_CTX_PREF', 'I_INDEX_CLAUSE','tablespace ICV_TS_CTX_IDX compress 2');
    exec ctx_ddl.set_attribute('ICV_WCC_INT_SEARCH_CTX_PREF', 'P_TABLE_CLAUSE','tablespace ICV_TS_CTX_IDX');
    exec ctx_ddl.set_attribute('ICV_WCC_INT_SEARCH_CTX_PREF', 'R_TABLE_CLAUSE','tablespace ICV_TS_CTX_IDX');
    CREATE INDEX WCC_INT_SEARCH_CTX_I1 ON WCC_INTERNAL_SEARCH_M
    (ORG_NAME)
    INDEXTYPE IS CTXSYS.CTXCAT
    PARAMETERS('Wordlist STEM_FUZZY_PREF
    LEXER LEXTER_PREF
    STORAGE ICV_WCC_INT_SEARCH_CTX_PREF');
    DB is 10.2.0.3

Maybe you are looking for