Creating Index Failing

When i try to create a complex FBI it throws me everytime same error , how can i achieve it please.
SQL> create index sr_merged_data_new_FBI_REC on SR_MERGED_DATA_NEW DECODE(SOURCE_SYSTEM,'S', CAST( FROM_TZ( CAST(SR_DATE_RECD AS TIMESTAMP) , 'GMT') AT TIME ZONE sessiontimezone AS DATE), 'Q', SR_DATE_RECD)
  2  /
create index sr_merged_data_new_FBI_REC on SR_MERGED_DATA_NEW DECODE(SOURCE_SYSTEM,'S', CAST( FROM_T
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Awais

>on SR_MERGED_DATA_NEW DECODE
Shouldn't the DECODE be preceded by an open bracket  (and a corresponding close bracket at the end) ?
Hemant K Chitale

Similar Messages

  • Create Index fail in process chain

    Hi Friends,
    I have a process chain in production system which loads inventory data everyday at 6:00Am.
    2 days back R3 production system failed and the data is not loaded into BI.  It was stopped at Delete Index step. I have started again by selecting Repeat then it worked and the infopackage is also executed successfully.
    After that it is failed at Create index step and giving message " Job cancelled after system exception ERROR_MESSAGE". Till then it is giving same problem everyday.
    Could you guys help me how to solve this and execute the chain successfully.
    Thanks & Regards

    Hi,
    Try to create index for the cube manually i.e got info cube , Right Click -> manage->performance-> perform check index - if red do repair index, if it will not help then create index. After that run it though process chain
    Hope it will resolve your problem.
    Sangita

  • CREATE INDEX fails with "insufficient privilege"

    Hello. I've never used TEXT before and frankly my first experience isn't going well. The long and the short of it is that when I ask 11g to make an index (authenticated to the schema) I get an error stack suggesting privilege problems:
    ORA-20000: Oracle Text error:
    DRG-50857: oracle error in drvxtabc.create_indexes:TC
    ORA-01031: insufficient privileges
    ORA-06512: at "CTXSYS.DRUE", line 160
    ORA-06512: at "CTXSYS.CATINDEXMETHODS", line 97
    I've concocted this simple case so you can see my work:
    create table a_ctxtest
         mykey int not null,
         mytext varchar2(200),     
         constraint px_testkey primary key ( mykey )
    create index itx_test on a_ctxtest( mytext ) indextype is ctxsys.ctxcat PARAMETERS ('STORAGE mystore');
    This code, found in this forum, had been run earlier in the session:
    begin
    ctx_ddl.create_preference('mystore', 'BASIC_STORAGE');
    ctx_ddl.set_attribute('mystore', 'I_TABLE_CLAUSE', 'tablespace users storage (initial 32k)');
    ctx_ddl.set_attribute('mystore', 'K_TABLE_CLAUSE', 'tablespace users storage (initial 32k)');
    ctx_ddl.set_attribute('mystore', 'R_TABLE_CLAUSE', 'tablespace users storage (initial 32k) lob (data) store as (disable storage in row cache)');
    ctx_ddl.set_attribute('mystore', 'N_TABLE_CLAUSE', 'tablespace users storage (initial 32k)');
    ctx_ddl.set_attribute('mystore', 'I_INDEX_CLAUSE', 'tablespace users storage (initial 32k) compress 2');
    ctx_ddl.set_attribute('mystore', 'P_TABLE_CLAUSE', 'tablespace users storage (initial 32k)');
    ctx_ddl.set_attribute('mystore', 'S_TABLE_CLAUSE', 'tablespace users storage (initial 32k)');
    end;
    Hints or even outright commands back toward something that works as expected would certainly be welcome.

    I am going to guess that you are probably missing the create trigger privilege. I have provided a reproduction of your error, followed by granting of create trigger, followed by successful creation of the index. The required privileges can either be granted individually or through roles such as resource and ctxapp.
    SCOTT@orcl_11g> create user test identified by test
      2  /
    User created.
    SCOTT@orcl_11g> alter user test quota 100m on users
      2  /
    User altered.
    SCOTT@orcl_11g> grant connect to test
      2  /
    Grant succeeded.
    SCOTT@orcl_11g> grant create table to test
      2  /
    Grant succeeded.
    SCOTT@orcl_11g> grant execute on ctx_ddl to test
      2  /
    Grant succeeded.
    SCOTT@orcl_11g> connect test/test
    Connected.
    TEST@orcl_11g>
    TEST@orcl_11g> create table a_ctxtest
      2  (
      3  mykey int not null,
      4  mytext varchar2(200),
      5  constraint px_testkey primary key ( mykey )
      6  )
      7  /
    Table created.
    TEST@orcl_11g> begin
      2  ctx_ddl.create_preference('mystore', 'BASIC_STORAGE');
      3  ctx_ddl.set_attribute('mystore', 'I_TABLE_CLAUSE', 'tablespace users storage (initial 32k)');
      4  ctx_ddl.set_attribute('mystore', 'K_TABLE_CLAUSE', 'tablespace users storage (initial 32k)');
      5  ctx_ddl.set_attribute('mystore', 'R_TABLE_CLAUSE', 'tablespace users storage (initial 32k) lob (data) store as (disable storage in row cache)');
      6  ctx_ddl.set_attribute('mystore', 'N_TABLE_CLAUSE', 'tablespace users storage (initial 32k)');
      7  ctx_ddl.set_attribute('mystore', 'I_INDEX_CLAUSE', 'tablespace users storage (initial 32k) compress 2');
      8  ctx_ddl.set_attribute('mystore', 'P_TABLE_CLAUSE', 'tablespace users storage (initial 32k)');
      9  ctx_ddl.set_attribute('mystore', 'S_TABLE_CLAUSE', 'tablespace users storage (initial 32k)');
    10  end;
    11  /
    PL/SQL procedure successfully completed.
    TEST@orcl_11g> create index itx_test on a_ctxtest( mytext ) indextype is ctxsys.ctxcat PARAMETERS ('STORAGE mystore')
      2  /
    create index itx_test on a_ctxtest( mytext ) indextype is ctxsys.ctxcat PARAMETERS ('STORAGE mystore')
    ERROR at line 1:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: Oracle Text error:
    DRG-50857: oracle error in drvxtabc.create_indexes:TC
    ORA-01031: insufficient privileges
    ORA-06512: at "CTXSYS.DRUE", line 160
    ORA-06512: at "CTXSYS.CATINDEXMETHODS", line 97
    TEST@orcl_11g> drop index itx_test
      2  /
    Index dropped.
    TEST@orcl_11g> connect scott/tiger
    Connected.
    SCOTT@orcl_11g>
    SCOTT@orcl_11g> grant create trigger to test
      2  /
    Grant succeeded.
    SCOTT@orcl_11g> connect test/test
    Connected.
    TEST@orcl_11g>
    TEST@orcl_11g> create index itx_test on a_ctxtest( mytext ) indextype is ctxsys.ctxcat PARAMETERS ('STORAGE mystore')
      2  /
    Index created.
    TEST@orcl_11g>

  • Create index fails (but worked previously)

    oracle 8.1.6 / solaris 7
    I installed InterMedia a few weeks ago (after many problems with configuring
    the listener and tnsnames) and created 3 text indexes on 2 tables(one column
    being a CLOB). The searches worked great (using "contains"). Next I tried to
    create a preference using ctx_ddl.create_preference andctx_ddl.set_attribute
    to allow for streaming of docs on the server. When Itried to create the index
    on the docs, it failed, giving me the
    ORA - 29885 error.
    Today, I needed to truncate the tables I created with the 3 indexes; in order
    to do so, I had to drop the index (FORCE) and when trying to recreatethem, it
    failed, giving me the error below. IT WAS WORKING 2 WEEKS AGO! WHAT
    HAPPENED??? The metalink site does not have good info and is TOO slow.
    null

    here's the error message:
    ORA-29855:error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000:interMedia Text error: DRG-50704: Net8 listener is not running or
    cannot start external procedures ORA-28575: unable to open RPC connection to
    externalprocedure agent ORA-06512: at "CTXSYS.DRUE", line 126 ORA-06512: at
    "CTXSYS.TEXTINDEXMETHODS", line 54 ORA-06512: at line 1
    oracle 8.1.6 / solaris 7
    I installed InterMedia a few weeks ago (after many problems with configuring
    the listener and tnsnames) and created 3 text indexes on 2 tables(one column
    being a CLOB). The searches worked great (using "contains"). Next I tried to
    create a preference using ctx_ddl.create_preference andctx_ddl.set_attribute
    to allow for streaming of docs on the server. When Itried to create the index
    on the docs, it failed, giving me the
    ORA - 29885 error.
    Today, I needed to truncate the tables I created with the 3 indexes; in order
    to do so, I had to drop the index (FORCE) and when trying to recreatethem, it
    failed, giving me the error below. IT WAS WORKING 2 WEEKS AGO! WHAT
    HAPPENED??? The metalink site does not have good info and is TOO slow.
    null

  • Error while creating index on  ep 6.0 9 sr1   (trex 6.1).

    Hell o all,
        I am getting following error while creating index on  ep 6.0 9 sr1   (trex 6.1).
    Index could not be created; creating index failed: general configuration error (Errorcode 2030)
    can any on ehelp.
    thanks and regards
    Rajendra

    Hi,
    We are running TREX 6.1.09.00 on EP6.0.9.0.0 and KMC6.0.9.0.0.
    We are experiencing the same problems, even after changing the value in the .ini file as specified in NOTE 766197.
    After doing changes, I restarted the server after doing the changes.
    Alessandro, have you got any ideas for fixing this?
    Message was edited by: Bjorn Bjornstad

  • Configuration error while creating index in KM

    Hi KM Expets,
    I am getting the following error while creating a new index via System Adminstration > System Configuration > Knowledge Management > Index Adminstration.
    Index could not be created; creating index failed: Invalid entry in configuration: section nameserver, key address, value tcpip://<nameserverhost>:<nameserverport> is invalid (Errorcode 7213)
    I guess all the field values filled by me are correct, so not able to get the problem.
    Any suggestions/help ?
    Regards,
    Saurabh

    HI
    check this links:
    https://www.sdn.sap.com/irj/sdn/thread?messageID=551325
    https://forums.sdn.sap.com/thread.jspa?threadID=953575&messageID=5752406#5752406
    Hope this may help you.
    Thanks
    Hussain.

  • Error while creating index

    hi all,
    i got this error while creating index in portal.
    <b>Index could not be created; creating index failed: Invalid entry in configuration: section nameserver, key address, value tcpip://<nameserverhost>:<nameserverport> is invalid (Errorcode 7213)</b>
    it a little urgent any will be appreciated.
    thanks in advance
    Ranga

    Hi Ranga,
    Please follow http://help.sap.com/saphelp_nw04s/helpdata/en/c7/e0d13f7fb44c21e10000000a1550b0/frameset.htm
    Hope it helps
    Detlev
    PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!

  • Couldn't create index errorcode 0

    Hi Expert,
    I would like to create index for web repository.
    1. create HTTP system
    2. create web site
    3. create web repository
    4. create crawler parameter
    and tried to create index by select TREX Search service and crawler in step4.
    but found this msg. " Index could not be created; creating index failed: no error (Errorcode 0) "
    (also TREX Search and Classification and TREX Classification service)
    before I tried to create web index, I created PCD content successfully!.
    I checked TREX monitor,HTTP Server and Name Server is Green.
    How can I check the crawler status, does it collect data successfully?
    Please kindly suggest me.
    Regards,
    Kanok-on K.

    The URL of the TREXWebServer wasn't correct

  • What resources are used for "create index" ?

    In the context of creating an index on a heavily loaded table....
    What Oracle resources are consumed>? Any caches or buffers? Sort files? Temp Tables?
    (trying to speed up an index create)

    Like any other read/write database activities, CREATE INDEX uses blocks in the buffer cache. If your table is large, I would recommend increase your buffer cache.
    No temporary tables is used as far as I know. There are no sort files in Oracle. Temporary tablespace may be used because sorting is generally needed when creating an index, but I am not sure about that.
    When creating a index, Oracle creates a temporary segment in your permanent tablespace: if the CREATE INDEX fails, the temporary segment is removed. If the CREATE INDEX succeeds, the temporary segment is made permanent.
    Message was edited by:
    Pierre Forstmann

  • BUG ? Create index on a partitioned table drops the complete table !

    Hi ...
    now i had twice the problem when i tried to create a local index (with 2 fields) on a partitioned table .
    I set initrans to 1 and maxtrans to 255 (i know - initrans has to be at least 2).
    I got an error - and the table (including the data) was gone ... :-((
    Has anybody the same behavior and is it a bug ??
    Christian

    See 1.5 Bad bug when creating index fails.
    Have fun,
    K.

  • Creating index ,im getting this error

    hi ,
    while  im creating index ,im getting this error:
    Index could not be created; creating index failed: Invalid entry in configuration: section nameserver, key address, value tcpip://<nameserverhost>:<nameserverport> is invalid (Errorcode 7213)
    can you pls help me ?
    Regard,
    prasad D.

    Hi Prasad,
       Please see the TREX Configuration doc  [TREX Configuration|http://help.sap.com/saphelp_nw70/helpdata/en/a9/4a6642161d0f53e10000000a155106/frameset.htm]
    you can check the all the TREX server status in System Administration ->Monitoring ->TREX Monitor .
    Naga

  • Errorcode 2030 while creating Index

    Hi,
    I am try to create an index for the first time and am not able to, because of the following error:
    Index could not be created; creating index failed: general configuration error (Errorcode 2030)
    Can you tell me if there is any place where I can lookup errorcodes and their descriptions?
    Thanks
    Raj Balakrishnan

    Error codes and messages of TREX 6.0
    OSS Note 649574 you can find a attach file in which explain you these message error.
    Patricio.
    List of TREX 6.0 Error Codes and Messages
    (including hints for solving some common problems)
    0000 no error No errors occurred. The process was completed successfully
    0001 multiple operations failed detail provided in a list This problem is mostly caused by HTTP problems when indexing or synchronizing. You must check whether the documents processed are actually available
    0004 Document to delete/update was not found The document that was prepared for deindexing or an incorrect document ID or document name. You must check whether there is a document in the index or on the harddisk (as URL) with the corresponding ID. For non Portal scenarios this error means: "document can not be found". If you use Content Server please check this document for consistency.
    0008 index is corrupted. Must be deleted/repaired by hand An error occurred when the system tried to delete the index. The corresponding entry was deleted from bartho.ini, but the index still exists. Solution: 1. Stop the TREXServices. 2. Delete the index directory and the entries in bartho.ini, TREXIndexServer.ini and TREXTcpipClient.ini manually. 3. Start the TREXServices 4. if necessary delete index in R/3 system (for non Portal scenarios) and clean tables. 
    0010 not enough space available for index creation There is no disk space available for creating a new index. You must chose another disk for the index. (The trace files might be occupying to much diskspace. If so, they have to be deleted.) 
    0011 specified language is unknown or not supported You must check whether the chosen language is supported by TREX and whether the language ID has been entered correctly. You must check also if these languages have been chosen correctly during the TREX installation. 
    0012 directory creation failed An index with the same name has already been created, and an error occurred when the index with the same ID was created again. The old index was not correct deleted :empty index directory still exists. Solution: 1. Stop the TREX Services. 2. Delete the index directory manually. 3. Start TREX Services again. 
    0013 directory removal failed The index directory could not be deleted correctly. This may be because there is a file missing from the index directory, or the index might be locked by another process. Solution: 1. Stop the TREX Services. 2. Delete the index directory and the entry in bartho.ini, in TREXIndexServer.ini and in TREXTcpipClient.ini manually. 3. Start the TREX Services 4. if necessary delete index in R/3 system (for non Portal scenarios) and clean tables. 
    0014 unknown or unsupported data type This may be because the document contains a data type that is not supported.
    0016 an operation has failed on a file (create, delete, copy, move...) This error occurs when the system tries to delete an index that is locked by another process. Solution: 1. Stop the TREX Services. 2. Delete the index directory and the entry in bartho.ini,TREXIndexServer.ini and in TREXTcpipClient.ini manually. 3. Start the TREX Services 
    0018 a received argument has an invalid value This problem can be occurred for example if Search Request is not correct.
    0020 unspecified win32/unix system error The error occurs when the system tries to index an index that has already been partially deleted. Solution: 1. Stop the TREX Services. 2. Delete the index directory and the entry in bartho.ini,TREXIndexServer.ini and in TREXTcpipClient.ini manually. 3. Start the TREX Services 
    0022 automatic index optimization failed This error can occur when another document is indexed by a URL in an index for an existing document. Afterwards the index is no longer available. Solution: 1. Stop the TREX Services. 2. Delete the index directory and the entry in bartho.ini,TREXIndexServer.ini and in TREXTcpipClient.ini manually. 3. Start the TREX Services 
    2001 Multiple operation failed, detail is provided in a list This problem is mostly caused by HTTP problems when indexing or synchronizing. You must check whether the documents processed are actually available. 
    2003  The error normally occurs when you try to create a new index with the same index ID as that of an existing index. If the index is not available in SAP_RETRIEVAL_PATH \Index, you must check whether there is an entry for a corresponding index in bartho.ini, TREXIndexServer.ini 
    2004 Document to delete/update was not found The document that was prepared for deindexing or an incorrect document ID or document name. You must check whether there is a document in the index or on the harddisk (as URL) with the corresponding ID. For non Portal scenarios this error means: "document can not be found". If you use Content Server please check this document for consistency.
    2007 index does not exist This error occurs when you try to delete an index that does not exist (or (de-) index some document in this index). The following points must be checked: Is the name of the index correct? Is there a subdirectory with the same name in SAP_RETRIEVAL_PATH\Index? Is there a matching entry in bartho.ini, TREXIndexserver.ini and in TREXTcpipClient.ini? 
    2011 Document language is unknown or not specified Check whether the chosen language is supported by TREX and whether the language ID has been entered correctly. (You also need to check that the language in question was selected when TREX was installed). 
    2503 Direct load, no queue server existing It should be checked , if the TREXIndexServer.ini has the proper entry for the Index Server, Queue Server and the IndexId. If it is necessary, this entries have to be added manually or from the backup version. 
    2960 The index server (for the specified indexes) cannot be determined check if TREXNameServer should be used, properly configured and run.
    2982 A communication error occured, with the TREX TcpIp Server Check if TREXIndexServer is running.
    2988 Missing argument Possible reason: search query is not correct
    2990 codepage error Possible reason: Codepage is not supported. 
    2998 dll can not be loaded Possible reason: in R/3 system check if in Transaction SRMO during the creation of SSR was selected DRFUZZY as searchengine. 
    6001 QS error: index not found Possible reasons: Index was deleted not complete (queue is still exist), or queue was created from TREXQueueClient. Solution: delete Queue through TREXQueueClient 
    6002 QS error: queue not found The queue has been deleted manually or was never created.
    6009 QS error: no connection to QueueServer The queue server did not start. Also check whether the TREXIndexServer.ini file has appropriate entries for the index server, queue server, and index id. If necessary, enhanced these entries manually or using the back-up version. 
    6017 QS error: queue not deleted The queue can not be deleted. The TREX index server, preprocessor, and queue server must be stopped and the queue index must then be deleted manually. 
    6021 QS error: queue exists The queue wasn't deleted when you deleted the index. This error occurred when you tried to create an index with the same ID. You have to delete the entries from this index from TREXTcpipClient.ini. 
    6401 HTTP Status Code 401 : Unauthorized Possible reason: TREX-user has no permissions for this document
    6403 HTTP Status Code 403 : Forbidden Possible reason: TREX-user has no permissions for this document
    6404 HTTP Status Code 404 : Not Found Possible reason: the document is not available
    6806 Preprocessor: filter error check if the document has correct mime-type and if necessary test with the filter.exe
    6906 Attribute engine index not found Subfolder attribute for index was not created with the index. Solution: 1. Stop the TREXServices. 2. Delete the index directory and the entries in bartho.ini, TREXIndexServer.ini and TREXTcpipClient.ini manually. 3. Start the TREXServices 4. if necessary delete index in R/3 system (for non Portal scenarios) and clean tables. 
    6915 UNKNOWN_ATTRIBUTE (AttributeEngine) check the search query. Requested attribute is not available in the index.
    Message was edited by: Patricio Garcia

  • Creating Index in KM

    Hi,
    I'm trying to create Index from Index Administration but its giving me the following error:
    Index could not be created; creating index failed: Invalid entry in configuration: section nameserver, key address, value tcpip://<nameserverhost>:<nameserverport> is invalid (Errorcode 7213)
    Where I should configure this setting?
    Thanks,
    Priya

    Hi Priya,
    you can configure this setting in the config tool under Global Serever Configuration --> services --> trex.service --> nameserver.address
    Best Regards
    Frank

  • INDEX failed to create while  Import using datapump

    Hi DBA's
    database 11.2.01
    OS : Solaris 10
    I am trying to Import the data using the following command.
    impdp system/******* SCHEMAS=EIMS DIRECTORY=expdp_dir DUMPFILE=eimsexp.dmp*
    but it fails import index and error out, but the tables and data imported.
    I checked in the metalink and followed the Note id (During Data Pump Import Index Creation Fails With: ORA-39083 and ORA-14102 errors OR ORA-39083 ORA-02158 and ORA-39112 errors [ID 1066635.1]) , but no luck.
    Kindly advice me.
    ERROR
    ORA-39083: Object type INDEX failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    Failing sql is:
    CREATE UNIQUE INDEX "EIMS"."PK_MDS_PSTN_LEVEL" ON "EIMS"."MDS_PSTN_LEVEL" ("REGION_CODE", "AREA_CODE", "LEVEL_NO", "EXCHANGE_CODE") PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" PARALLEL 1
    ORA-39083: Object type INDEX failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    Best Regards,
    SG

    Dear Hussein,
    Yes i applied the patch, still i am getting the same error and again i followed one more note (Impdp Failed With Error Ora-39083, 0ra-01403 On Index_statistics (Doc ID 755253.1))
    in that note i given option "exclude=index", then i got in different error.
    We are in the process of doing testing on Tablespace Encryption.
    We are having two instances one is dev and uat instance.
    we are creating Encryption tablespace on uat instance and trying to import the data from dev instance only from particular user.
    We completed the followings.
    1. Created tablespace Encryption.
    2. Created user and assigned the tablespace to the user EIMS1.
    3. Took export from the dev instance using the following command.
    expdp system/******** SCHEMAS=EIMS DIRECTORY=expdp_dir DUMPFILE=eimsexp.dmp
    4. Importing data from
    impdp system/******** REMAP_SCHEMA=EIMS:EIMS1 DIRECTORY=expdp_dir exclude=index DUMPFILE=eimsexp.dmp
    Error
    ====
    ORA-39083: Object type CONSTRAINT failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    Failing sql is:
    ALTER TABLE "EIMS1"."DOCS" ADD PRIMARY KEY ("ID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" ENABLE
    ORA-39083: Object type CONSTRAINT failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    before i used to get the bellow errors
    ==========================
    ALTER TABLE "EIMS1"."TST1" ADD CONSTRAINT "ADMACHINEDEPLOYMENTSTATUS_PK" PRIMARY KEY ("MID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" ENABLE
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    ORA-39083: Object type INDEX_STATISTICS failed to create with error:
    ORA-01403: no data found
    ORA-01403: no data found
    Failing sql is:
    DECLARE I_N VARCHAR2(60); I_O VARCHAR2(60); c DBMS_METADATA.T_VAR_COLL; df varchar2(21) := 'YYYY-MM-DD:HH24:MI:SS'; BEGIN DELETE FROM "SYS"."IMPDP_STATS"; c(1) := 'ID'; DBMS_METADATA.GET_STAT_INDNAME('EIMS1','DOCS',c,1,i_o,i_n); INSERT INTO "SYS"."IMPDP_STATS" (type,version,flags,c1,c2,c3,c5,n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,d1,cl1) VALUES ('I',5,0,I_N,NUL
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MDS_PSTN_LEVEL" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_AMT_REQUEST_PRIORITY" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_AMT_REQUEST_QUEUE" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH02_REQUEST_PRIORITY" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH03_REQUEST_PRIORITY" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH03_REQUEST_QUEUE" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH04_REQUEST_PRIORITY" creation failed
    Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 1049 error(s) at 20:43:02
    Thanks
    SG

  • Process chain failed on creating Indexes

    Hello All,
    Since a few days our process chains have failed because of an impossibility to create Indexes.
    Job BI_PROCESS_INDEX can run for 3 days without any result. Usually it runs during 4 seconds.
    When we stop this job, the next day the process chain fails to delete indexes.
    If we run RSRV for our infocube we get the following error :
    ORACLE: The status of index /BI0/E0PA_C01~040 is INVALID
    Our DBA says it's a BW issue.
    Any idea to solve this issue ?
    Thanks &
    Regards
    Catherine

    If we run RSRV for our infocube we get the following error :
    ORACLE: The status of index /BI0/E0PA_C01~040 is INVALID
    I hope u followed the below to check cube.
    RSRV -> Tests in Transaction RSRV -> All Elementary Tests -> Database -> Database Statistics for an InfoCube and its Aggregates
    In that case, did u execute "Correct Error" (button in toolbar) to fix that error ?
    If that does not fix the issue,
    cannot u delete (button in toolbar) and reschedule Process chain (delete index -> DTP load to Cube -> create index) to create index ??

Maybe you are looking for