10.5.6 Results in "forever" indexing Spotlight and poor performance

Hi all,
I recently updated to 10.5.6 and have been struggling with a constantly indexing spotlight ever since. I have tried the following:
-- repairing the disk
-- repairing the disk permissions
-- deleting the spotlight index and re-indexing
-- use Onyx to clean up spotlight indexes
-- added various directories to "privacy" in spotlight preferences
Essentially, the computer becomes very laggy with TONS of I/O activity (180GB in data read overnight, 100GB of data on the disk). Even after it appears that Spotlight is done indexing, it does not provide any search results and will eventually start re-indexing all over again.
Here is the repeated lines I keep seeing in the system logs:
Dec 19 09:11:21 marzuki com.apple.metadata.mds[1970]: mds(1970,0xb071b000) malloc: * mmap(size=45056) failed (error code=12)
Dec 19 09:11:21 marzuki mds[1970]: mds(1970,0xb071b000) malloc: * mmap(size=45056) failed (error code=12)\n* error: can't allocate region\n* set a breakpoint in mallocerrorbreak to debug
Dec 19 09:11:21 marzuki com.apple.metadata.mds[1970]: * error: can't allocate region
Dec 19 09:11:21 marzuki com.apple.metadata.mds[1970]: * set a breakpoint in mallocerrorbreak to debug
Dec 19 09:11:27 marzuki com.apple.metadata.mds[1970]: terminate called after throwing an instance of 'std::bad_alloc'
Dec 19 09:11:27 marzuki com.apple.metadata.mds[1970]: what(): St9bad_alloc
Dec 19 09:11:28 marzuki /usr/sbin/spindump[2103]: process 1971 is being monitored
Dec 19 09:11:42 marzuki ReportCrash[2104]: Formulating crash report for process mds[1970]
Dec 19 09:11:42 marzuki com.apple.launchd[1] (0x10dfd0.mdworker[2097]): Exited: Terminated
Dec 19 09:11:42 marzuki com.apple.launchd[1] (0x10e6e0.mdworker[2093]): Exited: Terminated
Dec 19 09:11:43 marzuki com.apple.launchd[1] (com.apple.metadata.mds[1970]): Exited abnormally: Abort trap
Dec 19 09:11:44 marzuki /usr/sbin/spindump[2103]: process 1971 is being no longer being monitored
Dec 19 09:11:48 marzuki ReportCrash[2104]: Saved crashreport to /Library/Logs/CrashReporter/mds2008-12-19-091128marzuki.crash using uid: 0 gid: 0, euid: 0 egid: 0
Dec 19 09:11:55 marzuki mds[2105]: (Error) Server: Client checkin failed: (ipc/send) invalid destination port
Dec 19 09:11:55 marzuki mds[2105]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"
Dec 19 09:11:56 marzuki /usr/sbin/spindump[2103]: process 1971 is being monitored
Dec 19 09:12:22 marzuki /usr/sbin/spindump[2103]: process 1971 is being no longer being monitored
The only solution I have found is to disable Spotlight completely.
Any help would be appreciated.
Thanks.

Thanks for all the replies. Unfortunately, none of them solved my problem. I tried:
1) restarting in safe-mode
2) repairing permissions
3) restarting in safe-mode
4) installing the combo update
5) restarting normally
My machine has been indexing for about 9 hours now and Spotlight status still says, "Estimating Indexing Time".
I am seeing this over and over again in my system log:
Jan 5 08:37:13 marzuki mds[2984]: mds(2984,0xb081f000) malloc: * mmap(size=45056) failed (error code=12)\n* error: can't allocate region\n* set a breakpoint in mallocerrorbreak to debug
Jan 5 08:37:13 marzuki com.apple.metadata.mds[2984]: mds(2984,0xb081f000) malloc: * mmap(size=45056) failed (error code=12)
Jan 5 08:37:13 marzuki com.apple.metadata.mds[2984]: * error: can't allocate region
Jan 5 08:37:13 marzuki com.apple.metadata.mds[2984]: * set a breakpoint in mallocerrorbreak to debug
Jan 5 08:37:13 marzuki com.apple.metadata.mds[2984]: terminate called after throwing an instance of 'std::bad_alloc'
Jan 5 08:37:13 marzuki com.apple.metadata.mds[2984]: what(): St9bad_alloc
Jan 5 08:37:14 marzuki ReportCrash[2988]: Formulating crash report for process mds[2984]
Jan 5 08:37:14 marzuki com.apple.launchd[1] (0x10d370.mdworker[2987]): Exited: Terminated
Jan 5 08:37:15 marzuki ReportCrash[2988]: Saved crashreport to /Library/Logs/CrashReporter/mds2009-01-05-083713marzuki.crash using uid: 0 gid: 0, euid: 0 egid: 0
Jan 5 08:37:15 marzuki com.apple.launchd[1] (0x10d160.mdworker[2986]): Exited: Terminated
Jan 5 08:37:15 marzuki com.apple.launchd[1] (com.apple.metadata.mds[2984]): Exited abnormally: Abort trap
Jan 5 08:38:14 marzuki mds[2989]: mds(2989,0xb081f000) malloc: * mmap(size=45056) failed (error code=12)\n* error: can't allocate region\n* set a breakpoint in mallocerrorbreak to debug
Jan 5 08:38:14 marzuki com.apple.metadata.mds[2989]: mds(2989,0xb081f000) malloc: * mmap(size=45056) failed (error code=12)
Jan 5 08:38:14 marzuki com.apple.metadata.mds[2989]: * error: can't allocate region
Jan 5 08:38:14 marzuki com.apple.metadata.mds[2989]: * set a breakpoint in mallocerrorbreak to debug
Jan 5 08:38:14 marzuki com.apple.metadata.mds[2989]: terminate called after throwing an instance of 'std::bad_alloc'
Jan 5 08:38:14 marzuki com.apple.metadata.mds[2989]: what(): St9bad_alloc
Jan 5 08:38:15 marzuki ReportCrash[2995]: Formulating crash report for process mds[2989]
Jan 5 08:38:15 marzuki mdworker[2992]: (Fatal) Import: Importer mach message failure on request work: (-308) (ipc/mig) server died
Jan 5 08:38:15 marzuki mdworker[2991]: (Fatal) Import: Importer mach message failure on request work: (-308) (ipc/mig) server died
Jan 5 08:38:15 marzuki ReportCrash[2995]: Saved crashreport to /Library/Logs/CrashReporter/mds2009-01-05-083814marzuki.crash using uid: 0 gid: 0, euid: 0 egid: 0
Jan 5 08:38:16 marzuki com.apple.launchd[1] (com.apple.metadata.mds[2989]): Exited abnormally: Abort trap
Any other ideas?
Thanks.

Similar Messages

Finished indexing spotlight and still very slow, what else can be?

Any clue! Pleeeeeease! Thanks for any
Ight on it!
MACPRO INTEL LION RECENTLY INSTALLED 500hd WITH OVER 300 FREE 8GB RAM
THREE FIREWIRE EXTERNAL UNITS, ONE SEAGATE AND TWO WESTERN DIGITAL AND ANOTHER WESTERN DIGITAL USB UNIT
WACOM INTUOS TABLET
EXTERNAL APPLE KEYBOARD
SYNCMASTER 2370
APPLE MAGIC MOUSE

I set the phone up this morning as a new phone no back up.
Brightness set to full
No wifi
No bluetooth
No back ground programs running
Fetch every 15 minutes for emails for half the day and then went to manually for second half
3G for half day and 2g for second half
tethering off
thats all I can think of. My friend and I looked at all his setting and mine and they were both similar except he keeps his on wifi all day.
we put them to exact same spec when i got to his house at 3. I had close to 50% from a full overnight charge and when I left at 7:30 I left dead and His was at 17% left still from the previous day and when I left his was at 8%
I dont know

Optimizer=ALL_ROWS, PARTITION HASH, INDEX (RANGE SCAN) POOR PERFORMANCE?

Our os is;
SunOS 5.9
and database is;
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit
Our autotrace outputs are below also we have 10046 trace outputs;
08:41:04 tcell_dev@SCME > set timing on
08:41:19 tcell_dev@SCME > set autot on
08:41:21 tcell_dev@SCME > SELECT lnpessv.PROFILE_ID FROM SCME.LNK_PROFILEENTITY_SUBSSERVVAR lnpessv
08:41:25 2 WHERE lnpessv.SUBSCRIPTION_SERVICEVARIANT_ID = 1695083 ;
PROFILE_ID
1.400E+14
1.600E+14
Elapsed: 00:00:03.07
Execution Plan
0 SELECT STATEMENT Optimizer=ALL_ROWS (Cost=3 Card=3 Bytes=51)
1 0 PARTITION HASH (ALL) (Cost=3 Card=3 Bytes=51)
2 1 INDEX (RANGE SCAN) OF 'PK_PROFILEENTITY_SUBSSERVVAR' (INDEX (UNIQUE)) (Cost=
3 Card=3 Bytes=51)
Statistics
1 recursive calls
0 db block gets
1539 consistent gets
514 physical reads
0 redo size
258 bytes sent via SQL*Net to client
273 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
2 rows processed
08:41:32 tcell_dev@SCME > SELECT lnpessv.PROFILE_ID FROM SCME.LNK_PROFILEENTITY_SUBSSERVVAR lnpessv
08:41:43 2 WHERE lnpessv.SUBSCRIPTION_SERVICEVARIANT_ID = 169508 ;
PROFILE_ID
1.400E+14
1.600E+14
Elapsed: 00:00:04.01
Execution Plan
0 SELECT STATEMENT Optimizer=ALL_ROWS (Cost=3 Card=3 Bytes=51)
1 0 PARTITION HASH (ALL) (Cost=3 Card=3 Bytes=51)
2 1 INDEX (RANGE SCAN) OF 'PK_PROFILEENTITY_SUBSSERVVAR' (INDEX (UNIQUE)) (Cost=
3 Card=3 Bytes=51)
Statistics
1 recursive calls
0 db block gets
1537 consistent gets
512 physical reads
0 redo size
258 bytes sent via SQL*Net to client
273 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
2 rows processed
Here we see 97% wait time, and responce time is unexceptable; These are the waits from 10046 trace file;
WAIT #1: nam='gc cr grant 2-way' ela= 783 p1=341 p2=67065 p3=1 obj#=169530 tim=571610438395
WAIT #1: nam='db file sequential read' ela= 6924 file#=341 block#=67065 blocks=1 obj#=169530 tim=571610445466
WAIT #1: nam='gc cr grant 2-way' ela= 564 p1=294 p2=86263 p3=1 obj#=169531 tim=571610446493
WAIT #1: nam='db file sequential read' ela= 6629 file#=294 block#=86263 blocks=1 obj#=169531 tim=571610453158
INDEX RANGE SCAN PK_PROFILEENTITY_SUBSSERVVAR PARTITION: 1 512 (cr=1537 pr=512 pw=0 time=4272017 us)
This is the related tables properties;
OWNER     SCME
TABLE_NAME     LNK_PROFILEENTITY_SUBSSERVVAR
TABLESPACE_NAME     DATA01
STATUS     VALID
PCT_FREE     10
INI_TRANS     10
MAX_TRANS     255
INITIAL_EXTENT     65536
MIN_EXTENTS     1
MAX_EXTENTS     2147483645
LOGGING     NO
BACKED_UP     N
NUM_ROWS     239587420
BLOCKS     1587288
EMPTY_BLOCKS     0
AVG_SPACE     0
CHAIN_CNT     0
AVG_ROW_LEN     41
AVG_SPACE_FREELIST_BLOCKS     0
NUM_FREELIST_BLOCKS     0
DEGREE     1
INSTANCES     1
CACHE     N
TABLE_LOCK     ENABLED
SAMPLE_SIZE     71876226
LAST_ANALYZED     29.05.2006 23:21:24
PARTITIONED     NO
TEMPORARY     N
SECONDARY     N
NESTED     NO
BUFFER_POOL     DEFAULT
ROW_MOVEMENT     DISABLED
GLOBAL_STATS     YES
USER_STATS     NO
SKIP_CORRUPT     DISABLED
MONITORING     YES
DEPENDENCIES     DISABLED
COMPRESSION     DISABLED
DROPPED     NO
We are suspecting rac configuration and hash partition and index usage with rac.
Any comments will be welcomed,
Thank you.
Tonguç

this is the output of dbms_metadata.get_ddl for the table;
CREATE TABLE "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR"
(     "SUBSCRIPTION_SERVICEVARIANT_ID" NUMBER NOT NULL ENABLE NOVALIDATE,
     "PROFILE_ID" NUMBER NOT NULL ENABLE NOVALIDATE,
     "CREATED_BY_ID" NUMBER,
     "CREATED_DATE" DATE DEFAULT SYSDATE,
     "UPDATED_BY_ID" NUMBER,
     "UPDATED_DATE" DATE,
     CONSTRAINT "PK_PROFILEENTITY_SUBSSERVVAR" PRIMARY KEY ("SUBSCRIPTION_SERVICEVARIANT_ID", "PROFILE_ID")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING
STORAGE(INITIAL 4194304
BUFFER_POOL DEFAULT)
TABLESPACE "INDX02" GLOBAL PARTITION BY HASH ("SUBSCRIPTION_SERVICEVARIANT_ID","PROFILE_ID")
(PARTITION "SYS_P52989"
TABLESPACE "INDX02",
PARTITION "SYS_P52990"
TABLESPACE "INDX02",
PARTITION "SYS_P54010"
TABLESPACE "INDX02",
PARTITION "SYS_P54011"
TABLESPACE "INDX02",
PARTITION "SYS_P54012"
TABLESPACE "INDX02") ;
CREATE UNIQUE INDEX "SCME"."PK_PROFILEENTITY_SUBSSERVVAR" ON "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" ("SUBSCRIPTION_SERVICEVARIANT_ID", "PROFILE_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING
STORAGE(INITIAL 4194304
BUFFER_POOL DEFAULT)
TABLESPACE "INDX02" GLOBAL PARTITION BY HASH ("SUBSCRIPTION_SERVICEVARIANT_ID","PROFILE_ID")
(PARTITION "SYS_P52989"
TABLESPACE "INDX02",
PARTITION "SYS_P52990"
TABLESPACE "INDX02",
PARTITION "SYS_P53499"
TABLESPACE "INDX02",
PARTITION "SYS_P53500"
TABLESPACE "INDX02") ENABLE NOVALIDATE,
     CONSTRAINT "FK_LNK_PROF_REFERENCE_SDP_SUBS" FOREIGN KEY ("SUBSCRIPTION_SERVICEVARIANT_ID")
     REFERENCES "SCME"."SDP_SUBSCRIPTIONSERVICEVARIANT" ("SUBSCRIPTION_SERVICEVARIANT_ID") DEFERRABLE INITIALLY DEFERRED ENABLE NOVALIDATE
) PCTFREE 10 PCTUSED 40 INITRANS 10 MAXTRANS 255 NOCOMPRESS NOLOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "DATA01" ;
CREATE INDEX "SCME"."LNK_PROFILEENTITY_SUB_HNDX3" ON "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" ("SUBSCRIPTION_SERVICEVARIANT_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING
STORAGE(INITIAL 2097152
BUFFER_POOL DEFAULT)
TABLESPACE "INDX02" GLOBAL PARTITION BY HASH ("SUBSCRIPTION_SERVICEVARIANT_ID")
(PARTITION "SYS_P53501"
TABLESPACE "INDX02",
PARTITION "SYS_P53502"
TABLESPACE "INDX02",
PARTITION "SYS_P53499"
TABLESPACE "INDX02",
PARTITION "SYS_P53500"
TABLESPACE "INDX02") ;
CREATE INDEX "SCME"."PROFILE_ID_NDX43" ON "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" ("PROFILE_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "INDX03" ;
ALTER TABLE "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" ADD CONSTRAINT "PK_PROFILEENTITY_SUBSSERVVAR" PRIMARY KEY ("SUBSCRIPTION_SERVICEVARIANT_ID", "PROFILE_ID")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING
STORAGE(INITIAL 4194304
BUFFER_POOL DEFAULT)
TABLESPACE "INDX02" GLOBAL PARTITION BY HASH ("SUBSCRIPTION_SERVICEVARIANT_ID","PROFILE_ID")
(PARTITION "SYS_P52989"
TABLESPACE "INDX02",
PARTITION "SYS_P52990"
PARTITION "SYS_P53498"
TABLESPACE "INDX02",
PARTITION "SYS_P53499"
TABLESPACE "INDX02",
PARTITION "SYS_P53500"
TABLESPACE "INDX02") ENABLE NOVALIDATE;
ALTER TABLE "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" MODIFY ("SUBSCRIPTION_SERVICEVARIANT_ID" NOT NULL ENABLE NOVALIDATE);
ALTER TABLE "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" MODIFY ("PROFILE_ID" NOT NULL ENABLE NOVALIDATE);

Non-indexing of word files in spotlight and error message

Spotlight on my macbookpro seems not to index any of msword files (including those with .doc in the name), and so I tried going into the terminal and typing "mdimport -f directoryname. The result was an endless flood of error messages like those below. I'm clueless, but it seems like it's saying the appropriate plugin is not loading. Anybody understand what's really going on?
Thanks,
Tom
2006-04-01 20:32:26.541 mdimport[1488] CFLog (21): dyld returns 2 when trying to load /Library/Spotlight/Microsoft Office.mdimporter/Contents/MacOS/Microsoft Office
2006-04-01 20:32:26.543 mdimport[1488] CFLog (22): Cannot find function pointer OfficeImporterPluginFactory for factory BFA4E323-1889-11D9-82C8-000A959816BE in CFBundle/CFPlugIn 0x328170 </Library/Spotlight/Microsoft Office.mdimporter> (bundle, not loaded)
2006-04-01 20:32:26.575 mdimport[1488] CFLog (21): dyld returns 2 when trying to load /Library/Spotlight/Microsoft Office.mdimporter/Contents/MacOS/Microsoft Office
2006-04-01 20:32:26.577 mdimport[1488] CFLog (22): Cannot find function pointer OfficeImporterPluginFactory for factory BFA4E323-1889-11D9-82C8-000A959816BE in CFBundle/CFPlugIn 0x328170 </Library/Spotlight/Microsoft Office.mdimporter> (bundle, not loaded)
macbookpro 1.83 Mac OS X (10.4.5)
powerbook g4 667 Mac OS X (10.3.9)

I noticed that the update info showed that it was supposed to improve things. My experience was that when it came to content indexing Spotlight seemed to take its own sweet time about getting that done--it seemed like it continued to add content indexes long after it finished its regular index run. So that might be a factor. Also, it is my understanding that it does not index everything in very long files, only the first so many pages (don't remember just how many and am not sure that is correct info, Doc Smoke would know), and if that is true length could be a factor. I just re-indexed a folder full of MSWord docs, and Spotlight does seem to be finding the content now, however the files are all short, one to two pages. I did a search in another folder, which contains a few MSWord docs and which I had not re-indexed, and Spotlight did find one file that had a unique word but not another (in a longer file). So it looks like the situation may be improved, but you will have to re-index to see any of the improvement.
Francine
Francine
Schwieder

Indexing Spotlight

Then I start my IMac (I have Yosemite 10.10.2) Spotlight then spends about about a hour re-indexing, During this re-indexing period I can use Spotlight and look for the items (indexed items) but afterwards (after that the indexing ends) it is still not able to locate any of the files on the disk.

Step 1
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Triple-click anywhere in the line below on this page to select it:
syslog -F '$Time $Message' -k Sender mdworker -o -k Message Rne Norm -k Sender mds | tail | pbcopy
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Paste into the Terminal window by pressing the key combination command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign ($) to appear.
The output of the command will be automatically copied to the Clipboard. If the command produced no output, the Clipboard will be empty. Paste into a reply to this message.
The Terminal window doesn't show the output. Please don't copy anything from there.
If any personal information appears in the output, anonymize before posting, but don’t remove the context.
Step 2
Enter the following command as in Step 1 and post the output:
mdutil -as 2>&- | pbcopy
You can then quit Terminal.
Step 3
Launch the Console application in the same way you launched Terminal. In the Console window, look under the heading DIAGNOSTIC AND USAGE INFORMATION on the left for crash reports related to Spotlight. If you don't see that heading, select
View ▹ Show Log List
from the menu bar. A Spotlight crash report has a name beginning in "mds" or "mdworker" and ending in ".crash". Select the most recent such report, if any, from the System and User subcategories and post the entire contents—the text, please, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post any other kind of diagnostic report, such as hang logs—they're very long and not helpful.

Weird result of oracle query before and after function base index creation

Hi All,
Here is the unique situation we are facing after creating just an index.
The query result before the index and the query result after the index do not match.
This is very illogical situation. Shidhar and me have done lot of R&D, also tried to get lots info from Google but we couldn't decipher the reason for that.
I am giving you all the details about the query, index and tables with following steps.
Please let us know if anything is going wrong from our side or is it a bug at oracle level which is a rarest possibility but a possibility.
Step 1 :- Create table
create table TEMP_COMP
ID VARCHAR2(10),
GROUP_ID VARCHAR2(10),
TRAN_DATE DATE,
AMT_1 NUMBER,
AMT_2 NUMBER,
AMT_3 NUMBER
Step 2 :- Insert Sample data
set feedback off
set define off
prompt Deleting TEMP_COMP...
delete from TEMP_COMP;
commit;
prompt Loading TEMP_COMP...
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('01', 'G01', to_date('01-03-2007', 'dd-mm-yyyy'), 1, 11, 111);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('02', 'G01', to_date('02-03-2007', 'dd-mm-yyyy'), 2, 22, 222);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('03', 'G01', to_date('03-03-2007', 'dd-mm-yyyy'), 3, 33, 333);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('04', 'G01', to_date('04-03-2007', 'dd-mm-yyyy'), 4, 44, 444);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('05', 'G01', to_date('05-03-2007', 'dd-mm-yyyy'), 5, 55, 555);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('06', 'G01', to_date('01-03-2008', 'dd-mm-yyyy'), 6, 66, 666);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('07', 'G01', to_date('02-03-2008', 'dd-mm-yyyy'), 7, 77, 777);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('08', 'G01', to_date('03-03-2008', 'dd-mm-yyyy'), 8, 88, 888);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('09', 'G01', to_date('04-03-2008', 'dd-mm-yyyy'), 9, 99, 999);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('10', 'G01', to_date('05-03-2008', 'dd-mm-yyyy'), 10, 100, 1000);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('01', 'G01', to_date('01-03-2007', 'dd-mm-yyyy'), 1, 11, 111);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('02', 'G01', to_date('02-03-2007', 'dd-mm-yyyy'), 2, 22, 222);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('03', 'G01', to_date('03-03-2007', 'dd-mm-yyyy'), 3, 33, 333);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('04', 'G01', to_date('04-03-2007', 'dd-mm-yyyy'), 4, 44, 444);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('05', 'G01', to_date('05-03-2007', 'dd-mm-yyyy'), 5, 55, 555);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('06', 'G01', to_date('01-03-2008', 'dd-mm-yyyy'), 6, 66, 666);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('07', 'G01', to_date('02-03-2008', 'dd-mm-yyyy'), 7, 77, 777);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('08', 'G01', to_date('03-03-2008', 'dd-mm-yyyy'), 8, 88, 888);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('09', 'G01', to_date('04-03-2008', 'dd-mm-yyyy'), 9, 99, 999);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('10', 'G01', to_date('05-03-2008', 'dd-mm-yyyy'), 10, 100, 1000);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('01', 'G02', to_date('01-03-2007', 'dd-mm-yyyy'), 1, 11, 111);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('02', 'G02', to_date('02-03-2007', 'dd-mm-yyyy'), 2, 22, 222);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('03', 'G02', to_date('03-03-2007', 'dd-mm-yyyy'), 3, 33, 333);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('04', 'G02', to_date('04-03-2007', 'dd-mm-yyyy'), 4, 44, 444);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('05', 'G02', to_date('05-03-2007', 'dd-mm-yyyy'), 5, 55, 555);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('06', 'G02', to_date('01-03-2008', 'dd-mm-yyyy'), 6, 66, 666);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('07', 'G02', to_date('02-03-2008', 'dd-mm-yyyy'), 7, 77, 777);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('08', 'G02', to_date('03-03-2008', 'dd-mm-yyyy'), 8, 88, 888);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('09', 'G02', to_date('04-03-2008', 'dd-mm-yyyy'), 9, 99, 999);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('10', 'G02', to_date('05-03-2008', 'dd-mm-yyyy'), 10, 100, 1000);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('01', 'G03', to_date('01-03-2007', 'dd-mm-yyyy'), 1, 11, 111);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('02', 'G03', to_date('02-03-2007', 'dd-mm-yyyy'), 2, 22, 222);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('03', 'G03', to_date('03-03-2007', 'dd-mm-yyyy'), 3, 33, 333);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('04', 'G03', to_date('04-03-2007', 'dd-mm-yyyy'), 4, 44, 444);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('05', 'G03', to_date('05-03-2007', 'dd-mm-yyyy'), 5, 55, 555);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('06', 'G03', to_date('01-03-2008', 'dd-mm-yyyy'), 6, 66, 666);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('07', 'G03', to_date('02-03-2008', 'dd-mm-yyyy'), 7, 77, 777);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('08', 'G03', to_date('03-03-2008', 'dd-mm-yyyy'), 8, 88, 888);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('09', 'G03', to_date('04-03-2008', 'dd-mm-yyyy'), 9, 99, 999);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('10', 'G03', to_date('05-03-2008', 'dd-mm-yyyy'), 10, 100, 1000);
insert into TEMP_COMP (ID, GROUP_ID, TRAN_DATE, AMT_1, AMT_2, AMT_3)
values ('11', 'G01', to_date('03-03-2008', 'dd-mm-yyyy'), 100, 200, 300);
commit;
prompt 41 records loaded
set feedback on
set define on
prompt Done.
Step 3 :- Execute the query.
SELECT GROUP_ID
, SUM(LAST_YR_REV) as "Year_2007_Amt"
, SUM(CURR_YR_REV) as "Year_2008_Amt"
FROM (
SELECT GROUP_ID,
CASE WHEN TO_CHAR(TRAN_DATE,'YYYYMM') BETWEEN'200701'AND'200712'THEN SUM(AMT_1) ELSE 0 END AS LAST_YR_REV ,
CASE WHEN TO_CHAR(TRAN_DATE,'YYYYMM') BETWEEN'200801'AND'200812'THEN SUM(AMT_1) ELSE 0 END AS CURR_YR_REV
FROM TEMP_COMP t
WHERE GROUP_ID ='G01'
AND TO_CHAR(TRAN_DATE,'YYYYMM') BETWEEN'200601'AND'200912'
GROUP BY GROUP_ID, TRAN_DATE
GROUP BY GROUP_ID
The result of above query
GROUP_ID Year_2007_Amt Year_2008_Amt
G01 30 180
Step 4 : Create composite index
create index GROUP_ID_TRAN_DATE_IDX on TEMP_COMP (GROUP_ID, TO_CHAR(TRAN_DATE,'YYYYMM'))
Step 5 : Execute once again query from step 3.
SELECT GROUP_ID
, SUM(LAST_YR_REV) as "Year_2007_Amt"
, SUM(CURR_YR_REV) as "Year_2008_Amt"
FROM (
SELECT GROUP_ID,
CASE WHEN TO_CHAR(TRAN_DATE,'YYYYMM') BETWEEN'200701'AND'200712'THEN SUM(AMT_1) ELSE 0 END AS LAST_YR_REV ,
CASE WHEN TO_CHAR(TRAN_DATE,'YYYYMM') BETWEEN'200801'AND'200812'THEN SUM(AMT_1) ELSE 0 END AS CURR_YR_REV
FROM TEMP_COMP t
WHERE GROUP_ID ='G01'
AND TO_CHAR(TRAN_DATE,'YYYYMM') BETWEEN'200601'AND'200912'
GROUP BY GROUP_ID, TRAN_DATE
GROUP BY GROUP_ID
The result of above query
GROUP_ID Year_2007_Amt Year_2008_Amt
G01 0 210
Thanks
Sunil

I just wanted to make a comment. The predicates in both your queries are flawed I believe. You convert a date column to a character and then you say only pick the converted result between two sets of characters.
TO_CHAR(TRAN_DATE,'YYYYMM') BETWEEN'200601'AND'200912'It should be coded like this for a proper date range comparison:
TRAN_DATE BETWEEN TO_DATE('200601','YYYYMM') AND TO_DATE('200912','YYYYMM')That will eliminate the need for you to create FBI that you created. You should now be able to create a regular (B*Tree) index on the TRAN_DATE column.
Also, now that we have the structure of your tables and sample data, what business question are you trying to answer? I think there is a better query that can be written if we know the requirements.
Hope this helps!

Spotlight and indexing of other disk partitions

Hi,
I have the internal drive of my 12" PowerBook formatted into two partitions, a small maintenance partition that's running 10.4.8, and a main partition, that's running 10.5.2. While I don't have a problem with upgrading the maintenance partition to Leopard, after seeing this report, I'm wondering if it's not a good idea to have Tiger and Leopard installed on separate partitions of the same internal drive. This leads to my questions:
Question 1:
Is it true that booting into a Tiger installation will cause Spotlight to overwrite the index files that Leopard created on either (or both) partitions? If this is true, then it would seem that I should really upgrade the maintenance partition to Leopard to prevent complete reindexing whenever I switch startup drives from one partition to the other.
Question 2:
Is there any way that I can tell Spotlight on the maintenance partition to not index the main partition? I only boot into the maintenance partition to run tools to maintain the main partition, so I have no need for Spotlight when booted into the maintenance partition.
Question 3:
Even if I upgrade the maintenance partition to Leopard, is there any way that I can prevent each partition's installation from indexing the other?
Thanks,
Ken

I want to make sure that I have each partition's installation set up so Spotlight won't corrupt or redo what the other partition's Spotlight has already done.
You can't do that, which is why I ended up with the less than satisfactory solution I have. When you boot up Spotlight begins to run as part of the system activities. It then looks at every mounted drive. Each and every drive has an invisible Spotlight folder. In that folder are the instructions to Spotlight about whether the drive or any directories on the drive have been excluded from Spotlight, and also, if the drive is supposed to be indexed, then the indexes themselves are in that folder. Thus the command line instruction to turn Spotlight status on or off specifies the path to the particular drive. There is no way to "quarantine" the Tiger or Leopard Spotlight. Whichever version is running looks to see if any given drive is supposed to be indexed, and, if it is, indexes it. The two versions can read each others general instruction about whether or not something is supposed to BE indexed, but can't read each others actual indexes. So if the instruction is for indexing to be on, then the version of Spotlight running looks at the index, can't read the index from the other version, and so proceeds to create a new index.
You can either have Spotlight on or off for a particular drive, that information will be read by both versions of Spotlight and acted on accordingly. Thus I booted in Leopard, ran the command line to turn the status off on my Tiger drive, preventing the drive from being indexed in Leopard, and edited the /etc/hostconfig file for Tiger to disable the Tiger Spotlight. When I booted in Tiger Spotlight didn't run AT ALL, so it didn't re-do the indexing for either the Tiger or Leopard drive. As far as I've been able to figure out this is the best solution, since I am generally booted in Leopard.
If all I had done was to add the Tiger drive to the Leopard Privacy pane, when I booted in Tiger its Spotlight would run, consult the preference for its drive, see it wasn't supposed to index its own startup drive, look at the information on the Leopard drive, see that that drive was supposed to be indexed, be unable to read the index and create a new one. When I next booted into Leopard it would have to re-index its own drive because its index would have been over-written.
Hope that makes a nasty situation clearer. I pondered the conundrum for some time before coming up with a solution. When I am booted in Tiger (which is rarely) I have to remember to use EasyFind when I want to find something, and when I am in Leopard a search of the Tiger drive is "brute force" only, but it can be searched.
Francine
Francine
Schwieder

Facing the issue Incomplete results (due to index-reload or timeout). Query will be resubmitted in 0 ms. 0 tries left. in FAST ESP 5.3

Hi ,
I am getting the following problem in my FAST ESP 5.3 , after recently updating the new Index profile. It was a Hot Update. Have already reset the index, but still this message keeps coming every 6 hrs. Please suggest.
Its a 2 node setup with 5 active partitions.
Thanks in Advance
[2014-08-25 11:59:53]
WARNING
qrserver
Server1
15100
systemmsg
Error received while searching tcp/manufsis1.manu:15150. Error: [18] No engine available for partition 3
[2014-08-25 11:59:52]
WARNING
qrserver
  Server2
15100
systemmsg
Error received while searching tcp/manufsis2.manu:15150. Error: [18] No engine available for partition 3
[2014-08-25 11:59:52]
WARNING
qrserver
  Server1
15100
systemmsg
Error received while searching tcp/manufsis1.manu:15150. Error: [18] No engine available for partition 3
[2014-08-25 11:59:52]
WARNING
qrserver
  Server2
15100
systemmsg
Incomplete results (due to index-reload or timeout). Query will be resubmitted in 0 ms. 0 tries left.

If there was an index profile update, could you try to clear qrserver cache and redeploy views:
- stop the qrserver,
-delete the qrserver cache ($FASTSEARCH/var/qrserver),
-start qrserver and run the following two commands from bin:
view-admin -m deploy -a
view-admin -m refresh –a
You might want to do this during off peak hours.
Also, from the server(s) running topfdispatcher can you check if you have duplicate entries in the enginerc-tld_0 file(located in %FASTSEARCH/var/searchctrl/etc)

AUTO_FILTER in 10g results in NO indexes

I have a MULTI_COLUMN_DATASTORE associated with my index. One of the columns is a BLOB. I have tested with Word, XML and PPT documents and embedded text in those docs is searchable without me specifying any FILTER parameter during index creation.
When I test with PDF docs I don't find anything on my searches. I have tried INSO_FILTER and AUTO_FILTER during index creation and every time I get NO hits on any searches anymore. I rebuild my datastore with the new FILTER clause, specify Y for my BLOB column and N for the others. Again, I get NO hits for any searches. Rebuild datastore specifying N for the BLOB column and all indexes (except PDFs) get generated fine again.
I assume use of AUTO_FILTER requires something that I don't have configured.
Any ideas appreciated.

Hi,
I am also planning to use Oracle text for our document and database searching (Oracle 10g (10.2.0)). I have saved 2 files (.DOC and .PDF) as blobs in the database. I used the following script for creating index on the blob type:
create index testindex on doc_prototype1(text) indextype is ctxsys.context
parameters ('filter ctxsys.inso_filter');
I also tried using auto_filter as well but it didn’t work.
I got the following error when I viewed the error log and the index tables were blank.
DRG-11207: user filter command exited with status 1 - DRG-11222: Third-party filter does not support this known document format.
Can anyone please help me out to resolve this problem and also to analyze the exact reason and the solution for the same.
Regards
Inderjeet

Spotlight and iCal search not working after upgrade to Leopard

I recently upgraded my MBP to Leopard (10.5.7), and everything seemed fine. Except search in iCal wasn't working. I looked in forums and found a suggestion - renaming Calendar Cache in Home>>Library>>Calendars, then restarting iCal. iCal rebuilt the Calendar Cache (or looked like it was, progress bar and all), but search still wasn't working, failing to bring up events I was looking right at.
Then I tried to use Spotlight, and it didn't seem to be working either. I tried searching for Safari, and after a brief pause, Spotlight said "No Result Found." I confirmed Safari is in fact still on my MBP and working (opened from applications folder). After some more hunting on forums, I found a thread talking about how to force Spotlight to re-index, figuring that was at least Spotlight's problem. Here's the thread - http://forums.macrumors.com/showthread.php?t=381832
I tried what it suggested, using the command line in Terminal, but Terminal just spat back "No Index." So now I'm stumped. Any ideas? I've already tried rebooting, to no effect, though I'll try it again tonight.

Well, thanks again for all the suggestions, but I sort of stumbled on the fix - which turned out to be upgrading MacFUSE. I had forgotten I installed that so I could read/write to my BootCamp Windows partition under Tiger, and a couple times when I would restart my computer I'd get an error message about MacFUSE (ironically, the error claimed my OS was out of date, but it was really MacFUSE that was out of date).
After I updated to the latest version of MacFUSE and restarted, Spotlight started indexing. Now it works just fine. Not sure if this is a known issue, but it seems that was most likely the problem.
Now I just have to figure out why the search feature in Calendar doesn't work... already tried rebuilding the Calendar Cache multiple times. Any ideas for that one?

So now spotlight and finder in coloum view crash/not working

So now my spotlight never searches for everything (I tried restarting, then logging off and logging back again, reindexing, delted plist) nothing works
and finder in colum veiw crashes

unfortunately I this is still not working, thanks for the link Eric i tried those options, but still the problem remains.
I can clear the cache and re index my mac, and while the system is re indexing spotlight works and I can find material during the reindex. This is obviously limited to the files that have been indexed at the point of using spotlight.
Once indexing has finished if I go to spotlight and try to search for anything, there are no results only the dictionary appears.
At the moment I have to delete the index cache every morning to trigger a re index so I can work, this is terrible and the worst upgrade experience I have had with any OS mac or windows

Spotlight and finder not working after Yosemite upgrade

Hi,
I just upgrade to 10.10.1 from 10.8 on a Mid 2012 Retina macbook pro, 2.7Ghz i7, 16GB RAM, 750GB SSD drive.
Since upgrading spotlight and finder have stopped working. When I first upgraded I noticed it worked very briefly and found some of my applications, but now nothing. The only thing it does is find the definition of the word I am searching for,
I have
gone in to sys pref > spotlight added and remove all folders and rebooted the machine
gone in to sys pref > spotlight > privacy tab and ensured no folders are in that pane
gone in to sys pref > spotlight > privacy tab and added "documents folder" closed sys prefs rebooted and then removed "documents" folder to try and trigger a re index
gone to terminal and typed "sudo mdutil -E /" which should erase and rebuild the index but i get the error back "Error: Index is already changing state. Please try again in a moment"
gone to terminal and typed "sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist" and then typed "sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist"
go to disk utility and verified my disk which comes back as showing no errors
logged in as another user but spotlight and finder still not working
Any other ideas my laptop is useless for work if I can't find anything,
Thanks

unfortunately I this is still not working, thanks for the link Eric i tried those options, but still the problem remains.
I can clear the cache and re index my mac, and while the system is re indexing spotlight works and I can find material during the reindex. This is obviously limited to the files that have been indexed at the point of using spotlight.
Once indexing has finished if I go to spotlight and try to search for anything, there are no results only the dictionary appears.
At the moment I have to delete the index cache every morning to trigger a re index so I can work, this is terrible and the worst upgrade experience I have had with any OS mac or windows

Spotlight and Mail searches

I have just replaced my 2007 MP with a shiny new one, (garbage can someone described it to me) !
The computer is responding a bit slowly entering text into Safari fields, i.e. logging into sites, username & passwords - I type out a word and it takes seconds to appear in the box.
Also searches in Mail & Spotlight do not yield any results and judging by other posts on the subject, is probably down to Spotlight indexing the 3TB of data on the Pegasus drive.
I did not migrate any files over from my old MP as I wanted to keep a clean new drive.(I did this initially but ended up in a mess so had to erase the disk and reinstall Yosemite) I have reinstalled the majority of my apps that were on the old machine from the app store and note a significant difference in the sizes of the Libraries :
                    Old MP          New MP
Library          88gb                 6 gb
User library   33gb               11 gb
So some questions arising that hopefully someone will answer :-
Doing a spotlight search of the Pegasus drive - there is no progress bar (as noted in other posts) - there is a message that just says "Searching Promise". So presumably it is indexing the drive. Not sure how long it will take to do 3TB of data (a lot of video)
Mail - doing a search in Mail does not do anything, no dropdown etc. I presume that this is using Spotlight and once that is indexed then a Mail search should work?
Is there a way to migrate specific apps from my old MP?
I am wondering why such a big difference between the libraries on the 2 machines.
Thanks & regards

The warranty entitles you to complimentary phone support for the first 90 days of ownership.

Spotlight and Time Machine

According to my console log file, Spotlight is having trouble with my Time Machine volume
Jul 1 18:48:25 StevesiMac mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8)(E rror) IndexCI in openindexfile:ftruncate error: 22, size: 32768, live.0.indexIds
Jul 1 18:48:25 StevesiMac mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8)(E rror) IndexCI in ContentIndexOpenBulk:Could not open /Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8/li ve.0.; needs recovery
Jul 1 18:48:25 StevesiMac mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8)(E rror) IndexCI in copyFileOrFd:error (22) opening 0.indexGroups
Jul 1 18:48:25 StevesiMac mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8)(E rror) IndexCI in recoverIndex:Unrecoverable error: could not recover groups file (0.)
Jul 1 18:48:25 StevesiMac mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8)(E rror) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8
The net result is that the drive always shows as busy. I can't eject it and I get the "Failed to create backup index" error message.
Does anyone know of a fix for this. If I used a utility such as Spotless to turn indexing off on the TM volume, will it also disable my ability to use TM to restore a file since the drive is no longer indexed?
Thanks
BTW, just happened in 10.5.4, but first noticed the symptoms is 10.5.3.
Thanks
Steve

there is no need to have TM drive indexed. it will only confuse both TM and spotlight and is likely to cause problems of the kind you are having. add it to spotlight's privacy pane. that will have no effect on using spotlight from inside TM interface to search backups.

Spotlight and Time Machine broken after restore/upgrade

I've found a few similar threads to this but none of those solutions has worked for me.
Two things happened at nearly the same time, so I don't exactly know the source of my problem:
I upgraded my old MacBook Pro (approx. Oct 2010, 2.66GHz I think, 300GB-ish HD) from Lion to Mountain Lion
The hard drive on my old MacBook Pro developed a terminal fault, so I had to buy a new one (8GB, 750GB HD) and restore a month-old Time Machine backup from my external drive.
I can't remember whether my last Time Machine backup to my external drive was before or after I upgraded to Mountain Lion.
Now I'm on OS X 10.8.2 on this new machine and I have two problems that seem to co-exist for a lot of other people too:
Spotlight won't index: this is f***ing infuriating, I love spotlight and I use it all the time. When I first restored from the TM backup I think the old index restored with the backup as I did get a decent number of search results (both in spotlight and in MS Outlook), but new files didn't seem to get recognised. I tried adding my hard drive to the exclusion list and removing it again in an attempt to get it to rebuild the index, but all that did was wipe the old index without building a new one, so now I get no spotlight results whatsoever. I tried this solution and sadly it hasn't worked either. Basically I can't search for anything. Even applications (which I like to launch from spotlight) don't appear. All I get is "estimating indexing time", and it never gets any further.
Time Machine won't back up: the first time I tried to backup my new machine it got a few hundred megabytes in before stalling; then a few hundred kilobytes in the next time I tried; and now it just doesn't get anywhere at all. The external drive I'm trying to backup to is recognised fine, I can see all the other files on it, and Time Machine seems to know that it's there, but the backup gets nowhere.
There are reports of this kinds of crap all over the Apple Support forums, but no definitive answer, especially for 10.8.2.
I could really do with some help on this. I need a backup before I screw another laptop, and I need spotlight to survive day-to-day life.
Thanks,
Craig

Hi Craig - I had the exact same problem - I'm using an old early 2009 MacBook Pro upgraded to 8 Gb Ram, 1 TB internal Hitachi HD, 10.8.2 - tried the fixes suggested - got it to work with these steps- everybodies mileage is different but hopefully it works for you as well.
a) I repaired disk permissions with Onyx (free utility) and then started up with Command-R using Disk Utility to repaired/check the Volume (harddisk checked out fine but the volume needed some minor repairs )- Onyx repair disk permission seems to go deeper -had to reinstall some apps - don't know if this solved it-seems to bring it back to the default state - you might get away with doing all from Disk Utility (but starting up with Command-R)
b) restart from my internal hd
c) downloaded the 10.8.2 combo update ( not the incremental shell update or whatever you call it which automatically gets installed with software update - combo update installs everything fresh from the .0 version)
d) with Onyx I deactivated spotlight and erased the spotlight index
d) restart
e) started TM backup - prep took pretty long 30 minutes but then 450 GB got backed up in 6 hours to my external HD which is fast enough for me
f) activated spotlight and 450 Gb were indexed in 9 hours or so
g) for 2 days everything runs fast and very responsive
best,
Franz

10.5.6 Results in "forever" indexing Spotlight and poor performance

Similar Messages

Maybe you are looking for