Rebuild the Index

Hello
the following query takes more than 3 hours.

the wait event is a clue: PSCRECV_HDR. Should rebuild us this index? Or problem is something else?
How can I check the health of the index?
show parameter optimizer
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------
optimizer_capture_sql_plan_baselines boolean     FALSE
optimizer_dynamic_sampling           integer     2
optimizer_features_enable            string      11.2.0.3
optimizer_index_caching              integer     0
optimizer_index_cost_adj             integer     100
optimizer_mode                       string      ALL_ROWS
optimizer_secure_view_merging        boolean     TRUE
optimizer_use_invisible_indexes      boolean     FALSE
optimizer_use_pending_statistics     boolean     FALSE
optimizer_use_sql_plan_baselines     boolean     TRUE

Explain plan for
SELECT A.BUSINESS_UNIT, D.DESCR FROM PS_SP_RECV1_NONVW A, PS_SP_RCV1_NONVWLN D WHERE D.BUSINESS_UNIT LIKE 'I%' AND D.BUSINESS_UNIT=A.BUSINESS_UNIT AND D.LANGUAGE_CD='FRA' UNION SELECT  BUSINESS_UNIT, DESCR FROM PS_SP_RECV1_NONVW A WHERE BUSINESS_UNIT LIKE 'IF%' AND NOT EXISTS (SELECT 'X' FROM PS_SP_RCV1_NONVWLN D WHERE  D.BUSINESS_UNIT=A.BUSINESS_UNIT AND 

explain plan succeeded.
159 ms 
PLAN_TABLE_OUTPUT                                                                                                                                                                                                                                                                                            
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ 
                                                                                                                                                                                                                                                                                                             
-----------------------------------------------------------------------------------------------------                                                                                                                                                                                                        
| Id  | Operation                         | Name               | Rows  | Bytes |TempSpc| Cost (%CPU)|                                                                                                                                                                                                        
-----------------------------------------------------------------------------------------------------                                                                                                                                                                                                        
|   0 | SELECT STATEMENT                  |                    |  9960M|   538G|       |   313M  (1)|                                                                                                                                                                                                        
|   1 |  SORT ORDER BY                    |                    |  9960M|   538G|   410G|   313M  (1)|                                                                                                                                                                                                        
|   2 |   SORT UNIQUE                     |                    |  9960M|   538G|   633G|   188M  (1)|                                                                                                                                                                                                        
|   3 |    UNION-ALL                      |                    |       |       |       |            |                                                                                                                                                                                                        
|*  4 |     HASH JOIN                     |                    |  9960M|   538G|  3944K| 31301  (98)|                                                                                                                                                                                                        
|*  5 |      INDEX FAST FULL SCAN         | PSCRECV_HDR        |   201K|  1577K|       |   187   (2)|                                                                                                                                                                                                        
|*  6 |      HASH JOIN                    |                    | 98659 |  4817K|       |   191   (2)|                                                                                                                                                                                                        
|   7 |       NESTED LOOPS                |                    |       |       |       |            |                                                                                                                                                                                                        
|   8 |        NESTED LOOPS               |                    |     1 |    42 |       |     3   (0)|                                                                                                                                                                                                        
|   9 |         MERGE JOIN CARTESIAN      |                    |     1 |    12 |       |     2   (0)|                                                                                                                                                                                                        
|* 10 |          INDEX RANGE SCAN         | PS_BUS_UNIT_TBL_FS |     1 |     6 |       |     1   (0)|                                                                                                                                                                                                        
|  11 |          BUFFER SORT              |                    |     1 |     6 |       |     1   (0)|                                                                                                                                                                                                        
|* 12 |           INDEX RANGE SCAN        | PS_BUS_UNIT_TBL_FS |     1 |     6 |       |     1   (0)|                                                                                                                                                                                                        
|* 13 |         INDEX UNIQUE SCAN         | PS_BUS_UNIT_LANG   |     1 |       |       |     0   (0)|                                                                                                                                                                                                        
|  14 |        TABLE ACCESS BY INDEX ROWID| PS_BUS_UNIT_LANG   |     1 |    30 |       |     1   (0)|                                                                                                                                                                                                        
|* 15 |       INDEX FAST FULL SCAN        | PSCRECV_HDR        |   201K|  1577K|       |   187   (2)|                                                                                                                                                                                                        
|* 16 |     FILTER                        |                    |       |       |       |            |                                                                                                                                                                                                        
|* 17 |      HASH JOIN                    |                    |   100K|  3450K|       |   190   (2)|                                                                                                                                                                                                        
|  18 |       TABLE ACCESS BY INDEX ROWID | PS_BUS_UNIT_TBL_FS |     1 |    27 |       |     2   (0)|                                                                                                                                                                                                        
|* 19 |        INDEX RANGE SCAN           | PS_BUS_UNIT_TBL_FS |     1 |       |       |     1   (0)|                                                                                                                                                                                                        
|* 20 |       INDEX FAST FULL SCAN        | PSCRECV_HDR        |   201K|  1577K|       |   187   (2)|                                                                                                                                                                                                        
|  21 |      NESTED LOOPS                 |                    |  9178 |   215K|       |   681   (1)|                                                                                                                                                                                                        
|  22 |       NESTED LOOPS                |                    |     1 |    16 |       |     0   (0)|                                                                                                                                                                                                        
|* 23 |        INDEX UNIQUE SCAN          | PS_BUS_UNIT_LANG   |     1 |    10 |       |     0   (0)|                                                                                                                                                                                                        
|* 24 |        INDEX UNIQUE SCAN          | PS_BUS_UNIT_TBL_FS |     1 |     6 |       |     0   (0)|                                                                                                                                                                                                        
|* 25 |       INDEX RANGE SCAN            | PSCRECV_HDR        |  9178 | 73424 |       |   681   (1)|                                                                                                                                                                                                        
-----------------------------------------------------------------------------------------------------                                                                                                                                                                                                        
                                                                                                                                                                                                                                                                                                             
Predicate Information (identified by operation id):                                                                                                                                                                                                                                                          
---------------------------------------------------                                                                                                                                                                                                                                                          
                                                                                                                                                                                                                                                                                                             
   4 - access("A"."BUSINESS_UNIT"="A"."BUSINESS_UNIT" AND                                                                                                                                                                                                                                                    
              "A"."BUSINESS_UNIT"="B"."BUSINESS_UNIT")                                                                                                                                                                                                                                                       
   5 - filter("A"."RECV_STATUS"<>'C' AND "A"."BUSINESS_UNIT" LIKE 'I%')                                                                                                                                                                                                                                      
   6 - access("A"."BUSINESS_UNIT"="B"."BUSINESS_UNIT")                                                                                                                                                                                                                                                       
  10 - access("B"."BUSINESS_UNIT" LIKE 'I%')                                                                                                                                                                                                                                                                 
       filter("B"."BUSINESS_UNIT" LIKE 'I%')                                                                                                                                                                                                                                                                 
  12 - access("B"."BUSINESS_UNIT" LIKE 'I%')                                                                                                                                                                                                                                                                 
       filter("B"."BUSINESS_UNIT" LIKE 'I%')                                                                                                                                                                                                                                                                 
  13 - access("B"."BUSINESS_UNIT"="C"."BUSINESS_UNIT" AND "C"."LANGUAGE_CD"='FRA')                                                                                                                                                                                                                           
       filter("C"."BUSINESS_UNIT" LIKE 'I%')                                                                                                                                                                                                                                                                 
  15 - filter("A"."RECV_STATUS"<>'C' AND "A"."BUSINESS_UNIT" LIKE 'I%')                                                                                                                                                                                                                                      
  16 - filter( NOT EXISTS (SELECT 0 FROM SYSADM."PS_BUS_UNIT_LANG"                                                                                                                                                                                                                                           
              "C",SYSADM."PS_BUS_UNIT_TBL_FS" "B",SYSADM."PS_RECV_HDR" "A" WHERE                                                                                                                                                                                                                             
              "A"."BUSINESS_UNIT"="B"."BUSINESS_UNIT" AND "A"."RECV_STATUS"<>'C' AND                                                                                                                                                                                                                         
              "A"."BUSINESS_UNIT"=:B1 AND "B"."BUSINESS_UNIT"=:B2 AND                                                                                                                                                                                                                                        
              "B"."BUSINESS_UNIT"="C"."BUSINESS_UNIT" AND "C"."LANGUAGE_CD"='FRA' AND                                                                                                                                                                                                                        
              "C"."BUSINESS_UNIT"=:B3))                                                                                                                                                                                                                                                                      
  17 - access("A"."BUSINESS_UNIT"="B"."BUSINESS_UNIT")                                                                                                                                                                                                                                                       
  19 - access("B"."BUSINESS_UNIT" LIKE 'IF%')                                                                                                                                                                                                                                                                
       filter("B"."BUSINESS_UNIT" LIKE 'IF%')                                                                                                                                                                                                                                                                
  20 - filter("A"."RECV_STATUS"<>'C' AND "A"."BUSINESS_UNIT" LIKE 'IF%')                                                                                                                                                                                                                                     
  23 - access("C"."BUSINESS_UNIT"=:B1 AND "C"."LANGUAGE_CD"='FRA')                                                                                                                                                                                                                                           
  24 - access("B"."BUSINESS_UNIT"=:B1)                                                                                                                                                                                                                                                                       
       filter("B"."BUSINESS_UNIT"="C"."BUSINESS_UNIT")                                                                                                                                                                                                                                                       
  25 - access("A"."BUSINESS_UNIT"="B"."BUSINESS_UNIT")                                                                                                                                                                                                                                                       
       filter("A"."RECV_STATUS"<>'C' AND "A"."BUSINESS_UNIT"=:B1)                                                                                                                                                                                                                                            
                                                                                                                                                                                                                                                                                                             
Note                                                                                                                                                                                                                                                                                                         
-----                                                                                                                                                                                                                                                                                                        
   - 'PLAN_TABLE' is old version                                                                                                                                                                                                                                                                             

65 rows selected

1 273 ms écoulées

==============================================================================================
SQL> select sid, osuser,row_wait_obj#,program,event from v$session where program like '%Dev%' and osuser='myuser';

       SID OSUSER          ROW_WAIT_OBJ# PROGRAM         EVENT
---------- --------------- ------------- --------------- ---------------
        29 myuser                51715 SQL Developer   SQL*Net message
                                                          from client

SQL> select  object_type, object_name, data_object_id
  2  from dba_objects
  3  where object_id = 51715;

OBJECT_TYPE         OBJECT_NAME     DATA_OBJECT_ID
------------------- --------------- --------------
INDEX               PSCRECV_HDR              51715
Thank you.

Are accurate statistics, the query returns about 10 billion lines, and if so how long you expect to take?
Can send you a SQL trace with details of actual file?

Tags: Database

Similar Questions

  • I followed these steps several times, but he still has to work to rebuild the index.  Is there something else in the way of this work?

    Have you tried to rebuild the index spotlight several times, but it didn't work. I followed the steps through the system preferences, but there is no result for the rebuilding of the index.  Is there another way to do it, or is there another problem preventing it from working?

    Do you mean the following steps:

    Rebuild the index on your Mac - Apple Support Spotlight

  • How to stop automatically rebuild the index

    How to stop windows from automatically rebuild the index; I am running vista sp2?  it restarts just as soon as he completed which makes my ability to get something useless

    Hi deblee99,

    -How long have you had this problem?

    -What software changes you did on the computer before the show?

    Follow these steps:

    Method 1:

     

    Follow these steps:

    Step 1:

    Create a new user account and see if the problem persists.

    Step 2:

    If the problem does not persist in the new user account, it could indicate that your old user account is corrupted.

    Follow the steps in the following article to repair the damaged user profile:

    Difficulty of a corrupted user profile

    Method 2: Perform an auditor of file system (CFS) scan in safe mode

     

    SFC tool scans system files and replaces incorrect versions of system files by using the correct versions.

    For instructions, see How to use the tool File Checker system to troubleshoot missing or corrupted system files on Windows Vista or Windows 7 .

  • Shrink the table, rebuild the index?

    I need to reduce some very large tables after the removal of lines and I want to validate the script to run. I was thinking something like this:
    run_deleting_process;
    change the movement line of table my_tableI enable;
    ALTER table my_table retractable space WATERFALL;
    change the movement line of table my_tableI disable;
    I need to rebuild the index after that?, or if I rebuild the markings, can I delete clause CASCADE of the command? It is recommended to run utltrp.sql after shrink the table?, maybe some dependent object needs to be recompiled after the reduction of a table?
    The database version is 11.1.0.7 and documentation does not specify that the index rebuild is required, but I realized it is a desition normall when the narrowing of the tables.
    Thank you

    No there is no rebuild the index after shrinkage. And if you use "cascade", your index will be supported. You do very well.

    Visit this link as well.

    http://www.orafaq.com/Forum/t/137522/2/

  • ORA-14456: can not rebuild the index on a temporary table

    change the IND_DEBITDOCUMENT TABLESPACE INDEXDATA index rebuild
    *
    ERROR on line 1:
    ORA-14456: can not rebuild the index on a temporary table


    why it is given such error?

    Thanks in advance.

    This information is always kept to user_ | all_ | dba_ tables, in this case in the temporary column.

    Obvious, isn't it?

    ---------
    Sybrand Bakker
    Senior Oracle DBA

  • rebuild the index partition

    Hello
    I have unusable a clue. Now I want to rebuild the index for this I have to rebuild the partition and the tablespace in two different command as

    Index_name ALTER INDEX REBUILD PARTITION p1;
    Index_name ALTER INDEX REBUILD PARTITION p1 TABLESPACE INDX_TS;
    now my question is when I run first command and check the index of fof status it shows not usable. In the same way when I ran only 2nd order also rebuild successfully. If I ran only 2nd command works fine?
    why it displays usable after only rebuild partition?


    I have script for all indexes on user like this

    Select 'ALTER INDEX' | index_name |' rebuild partition '. Nom_partition | ';' in USER_IND_PARTITIONS
    Select 'ALTER INDEX' | index_name |' rebuild partition '. NOM_PARTITION | 'SPACE '. nom_tablespace | ';' in USER_IND_PARTITIONS

    Why you set all the indexes to be UNUSABLE?

    (Please don't keep saying "unuse index", do you mean "occupies an unusable index"!)

    The instance / session SKIP_UNUSABLE_INDEXES setting determines the behavior of DML. In 9i, it is false by default. In 10g, it is by default true. Thus, in the 10g (unless you have changed it back to FALSE), INSERT/DELETE operations can succeed even if an Index is UNUSABLE. However, indexes to enforce PRIMARY KEY constraints or unique indexes (index created in CREATE a UNIQUE or apply INDEX of UNIQUE constraints) cannot be ignored by normal DML.

    (Direct path operations automatically update the index and, therefore, can leave clues in an unusable state temporary.) These look like actually to DDL operations and lock the partition table/preventing simultaneous updates).

  • Rebuild the indexes in Win Explorer: old folder back.

    I rebuild my index every month. When I do, I get an old folder in the My Documents folder. It appears once I do the reconstruction.

    Here's what I do:

    Control-> system and Maintenance-> Indexing Options Control Panel

    Click on the Advanced button

    Re-index selected location: click the Refresh button

    Places that have always been selected for reconstruction are:

    OneNote

    IE

    Start menu

    Users

    The old folder that keeps appearing once completed the reconstruction process is not among the users of--> username--> Documents folder under the location list.

    It is not a big problem for me to remove this old issue of each month. But I would like to know what is happening here in case there is something wrong with my system.

    I discovered what was going on. I hope it's useful to someone.
    I use a software CoffeeCup HTML editor. In the window of the preferences of this application, I had the path to the 'default Web site project folder"pointing to the folder that kept reappearing. When I changed the path to an existing folder, I got is no longer this mysterious folder reappears.
    It is logical. The application was create the folder whenever I opened it because he needed new projects.
    I also tested this theory by creating a new default folder, delete and then opening the application. He kept creating the folder.
    A big "thank you" to all of you who have looked at this and I tried to understand.

  • Rebuild the indexes to search for Windows 7 via command line

    My search index is constantly becomes corrupted and will have problems, looking for things in Outlook. The only way I can make it work temporarily is rebuilt the index and it goes for a week or two before she starts to have problems again.

    Is it possible that I can have research rebuilt via command line so that I can put in a batch file and schedule it to run?

    off @echo
    net stop wsearch
    del "% programdata%\microsoft\search\data\applications\windows\Windows.edb.bak".
    move "% programdata%\microsoft\search\data\applications\windows\Windows.edb" "% programdata%\microsoft\search\data\applications\windows\Windows.edb.bak".
    net start wsearch

  • Capture the Index Rebuild process time in a table

    Dear Experts,

    I have a stored procedure to rebuild the indexes. I would like to capture reconstruction of start and end time for a table. I created the table with structure below: I am writing an insert statement in the procedure that captures rebuild timings, might well want to suggest how to implement this?


    MAINT DESC

    Name Null? Type
    ------------------------------------------- ------------------------------------
    OWNER VARCHAR2 (30)
    TABLE-NAME VARCHAR2 (30)
    START_TIME DATE
    END_TIME DATE
    VARCHAR2 (200) COMMENTS


    CODE PLEASE
    =======

    CREATE OR REPLACE PROCEDURE "USER1". "" ONLINE_REORG ".
    (v_owner IN varchar2, v_tablename IN varchar2) AS
    v_rebuild_statement VARCHAR2 (1000);
    v_rebuild_statement1 VARCHAR2 (1000);
    err_msg VARCHAR2 (100);
    v_cdc number (6);
    cursor c1 is select master index_name table_name, nom_tablespace
    of dba_indexes
    where table_owner = upper (v_owner) and
    nom_tablespace is not null and
    index_type = 'NORMAL' and
    table_name = Upper (v_tablename);

    BEGIN
    DBMS_OUTPUT. Put_line ('Rebuild Index procedure begins execution At' | to_char (sysdate, ' DD-MM-YYYY HH24:MI:SS'));))

    FOR c1_rec IN c1 LOOP
    Start
    v_rebuild_statement: = 'edit index' | c1_rec. Owner: '.' | c1_rec.index_name |' REBUILD PARALLEL 6 LOGGING COMPRESS TABLESPACE ' | c1_rec.tablespace_name;
    DBMS_OUTPUT. Put_line(v_rebuild_statement||';');
    EXECUTE IMMEDIATE v_rebuild_statement;
    exception when others then
    null;
    end;
    Start
    v_rebuild_statement: = 'edit index' | c1_rec. Owner: '.' | c1_rec.index_name |' NOPARALLEL ';
    DBMS_OUTPUT. Put_line(v_rebuild_statement||';');
    EXECUTE IMMEDIATE v_rebuild_statement;
    exception when others then
    null;
    end;
    END LOOP;
    DBMS_OUTPUT. Put_line ("Rebuild Index procedure completes execution to ' |") TO_CHAR
    (sysdate, ' DD-MM-YYYY HH24:MI:SS'))) ;
    EXCEPTION
    WHILE OTHERS THEN
    DBMS_OUTPUT. Put_line ("Rebuild Index ended execution without success to")
    ' || TO_CHAR (sysdate, ' DD-MM-YYYY HH24:MI:SS'));)
    err_msg: = SUBSTR (SQLERRM, 1, 100);
    raise_application_error(-20001,err_msg);
    END;

  • schedule the index rebuild online

    Hello

    I need to schedule a task at the level of the database to rebuild the index online each month. all script exist? as the procedure to call on every month to rebuild indexes for the 5 tables identified in our project?

    It is in production

    We run in oracle 10g in the solaris platform.

    Dear Raman,

    I have no why yon need this.

    Try this, you can change next_date and interval you condition

    declare
  VJOBNUMBER BINARY_INTEGER;
begin
  DBMS_JOB.SUBMIT( job => VJOBNUMBER, NEXT_DATE => sysdate, interval => 'SYSDATE + 30', WHAT => 'BEGIN
FOR S IN (SELECT ''alter index'' || INDEX_NAME || '' rebuild;'' A FROM ALL_INDEXES)
LOOP
EXECUTE IMMEDIATE S.A;
END LOOP;
END;');
  DBMS_OUTPUT.PUT_LINE('Job number assigned: ' || TO_CHAR(VJOBNUMBER));
end;

  • Reduced index rebuild the size of

    Hi all

    I think that this topic was raised by several times up to now... But I would like to know as I'm very curious.

    An array of size 6 GB with index btree of 300 MB, the size very high CPU load in that server (I think because of I/O), after the reconstruction of this size of the index came up to 250 MB.

    Now all my seniors ordered me to rebuild all indexes in the database that are huge in size, so that the i/o and CPU will be back to normal.

    I had the argument with my elder for the reason why we need to rebuild the index?
    Answer: As Oracle has access to this index it a lot of scan crashes a lot because of fragmentation. Oracle also has to scan all the blocks below the high water mark, where some blocks have fewer lines.

    My doubt is: when index is fragmented (candidate means that after reconstruction, reduced its size) made Oracle scans unwanted blocks below let high water is wrong, because the INDEX and TABLE are two different concepts, INDEX maintains information on which all blocks, it would seek the required values. So Oracle will not scan the blocks unwanted in the INDEX.

    Do may doubt is good or bad?

    A few details:
    The indicator is in DMT tablespace.
    Oracle 8i version.
    Sun solaris with 5.8 version, with 8 CPUS and 6 GB of RAM
    None of the indices have a height more than two.

    Plz HELP me in this concept... I want to prove my elders.

    -Yasser

    Yasserracdba,

    People learn their theory IT more. The normal index is implemented as a B *-tree structure.
    This means

                                                                      1 

                                             2        3                              5            6

                                      7       8    9   10                    11     12    13     14

    This means: block 1 contains information on block 2, 3, 5, 6 (I forgot 4, does not renumber)
    Block 2 about 7 and 8
    Block 7, etc are the leaves blocks and contain the actual keys.
    The key consists of key values and a rowid.

    The index is balanced. For a single scan will always tell you the same number of blocks, in this case 4
    (3 blocks + block index 1 data).

    IF YOU DON'T HAVE A CLUE, YOU WILL BE FORCED TO READ THE ENTIRE TABLE, THE TABLE SCAN COMPLETE THIS CALLED (YOU CAN SHOUT, I CAN SHOUT TOO)

    TO ACCESS THE INDEX MEANS SELF-CONTAINED BED, FULL TABLE SCAN MEANS SCATTERED MULTI BLOCK READING (BLOCKS END UP NOT CONTIGUOUS CACHE)

    FOR RANGE SCANS IO CAN BE REDUCED. TO LOOK UP A KEY INDIVIDUAL IO WILL NOT, I REPEAT N O T, REDUCE.

    -----------------
    Sybrand Bakker
    Senior Oracle DBA

    Experts: those who don't read the documentation

    Published by: sybrand_b on May 28, 2009 11:04

  • the index rebuild process

    Hi master,

    It is 'NO' yet another thread on the rebuilding of the index.

    I have read all the threads on index rebuild on oracle forums. each thread is full load with arguments and significantly useful discussion.

    but hardly a thread to discuss the process of rebuilding the index!

    I would like to know what exactly the do oracle, to rebuild the index? It uses the existing as a source index and therefore require more space?

    or it generates repeat therefore requires more space?

    What oracle will do with the old index? It frees the space occupied by the old index?

    If someone has a link or a suggestion, I will be grateful. and the deep knowledge sharing is more appreciated.


    Thanks and greetings
    VD

    Published by: vikrant dixit on January 21, 2009 03:40

    Vikrant dixit says:
    Thanks Charles

    for your kind support. and yet I doubt how much performance gain should be expected by rebuilding the index. I think I have to read all this thread once more and find the cream of the subject.

    and all that said by experts is it not true that the performance gain is dependent on scenario?

    in any case thank you

    Thanks and greetings
    VD

    Vikrant,

    From what I've seen and read, what said you above is correct.

    I like your the thread topic to try to understand what is happening during an index rebuild and after an index rebuild. The subject of rebuild indexes or not has been discussed many, many times on this forum, in messages Usenet dating back to 1999, various threads on asktom.oracle.com, various Web sites and in various books. But, your topic of what happens during an index rebuild, and after an index rebuild is not discussed as often, then I hope the links I provided will help you.

    Charles Hooper
    IT Manager/Oracle DBA
    K & M-making Machine, Inc.

  • When I keyin information of track using Media Player, is this info inserted in the file itself, or only in the index Media Player?

    Original title: metadata key - music

    My question is actually very specific: when I keyin track using Media Player Info, is this info inserted in the file itself, or only in the index of Media Player? If I have to rebuild the indexes in the metadata file, the indexed fields are kept in?

    Only in the index of Media Player.  If you remove this file WMP (without actually deleting the computer/folder) and then read the file again, you would see that your changes have disappeared.

    To actually change the file, you will need a program known as ID3 Tag Editor.

  • How to check if the indexer works?

    The problem I have is that it generates a lot of disk activity.  If I do works that are heavy on the use of the disc, it becomes almost impossible to work.

    Is it possible to control when the indexer runs in the background?  I can work in two ways.

    1. If a process of a given name is in CPU, run no indexer

    2 in some window of time, don't throw an indexer (indexer or limited only to run in a window of time)

    Thank you

    Hello

    Thank you for your response.

    You can always return to your default configuration by disabling the additional folder that you added to the indexed location (-> Panel-> option change indexing) and rebuild the index (Control Panel-> option-> Advanced Indexing - > rebuild). Indexing of the entire system can lead to search huge index of data which may result from eating up your hard drive space and slow down your system.

    If the issue still persists I would say you are referring to the link below:

    See Mike Hall responded on 15 March 2012
    http://answers.Microsoft.com/en-us/Windows/Forum/Windows_7-files/does-Windows-search-indexing-really-slow-down-PC/1bd40e28-a1ef-486b-9246-867200139b81

    Hope this information helps and if you have other questions related to Windows do not hesitate to post on Microsoft Community, we will be happy to help you.

  • Analyze the index on the machine of Dataguard and redundancy of ASM disks

    Dear friends,

    I have two questions regarding disc Dataguard and ASM.

    (> > 1) for best performance, periodically, we rebuild the index index and analysis analyze table. What is the best periodic steps to do to get better performance?

    I mean, first of all is rebuilding of index, is second index analysis and so on......

    (> > 2) if I run analyze the index or the table on my PRODUCTION system he replicated this effect on statndby dataguard automatic system? If so, how it is replicated?

    (> > 3) my last question related with high redundancy of the ASM disk. I have some confusion on this area.

    Let's say I have 10 disks in a diskgroup '+ DATA' and I did 'HIGH' level redundancy, means 3 way redundancy. Here I know 3-way the redundancy, it writes data on 3 discs at a time. But what of the other 7 discs. In fact, I need to know the mechanism of writing?

    -Each disc is identical to the other drive?

    -For HIGH redundancy, how many disk failure can be tolerated for any loss of data?

    Waiting for your kind reply......

    "on my PRODUCTION'---> you mean"on my FIRST.

    Yes, the data dictionary is updated when you run dbms_stats.gather% and updates data dictionary are through recovery that applies to the WAITING for more.

    NOLOGGING surgery would not be applied to the expectation (the index would be marked corrupted to the standby) unless you have set on FORCELOGGING.

    Hemant K Collette

Maybe you are looking for