Spotlight re-indexes with each startup

Each time I startup my PowerBook, Spotlight spends a good 15-20 mins indexing. It does eventually stop and is then fully functional, but I wonder if anyone has experienced something similar and found a fix.

I wish I was posting a solution rather than a "me too." I believe this happened after I went from 10.4.3 to 10.4.4, but my memory could be failing me. Either way, I also experience Spotlight re-indexing at each startup. It is somewhat annoying, but not overly so. Any help or insight would be appreciated.
I did update to 10.4.5, and it still re-indexes at startup.

Similar Messages

Spotlight always indexes mac on startup

I've read several reports on Spotlight rebuilding indexes on startup. I found this issue on both my macs (with TIme Machine either on or off).
Here's what I've done trying to solve the problem:
1) I removed all of the spotlight indexes from all the disks and forced a re-index;
2) Removed all the *.mdimporter files from /Library/Spotlight
3) Erased all the system and application's caches with Onyx.
Are there any other solutions?

I don't mean to presume that all your guys' issues are related to this, but I am having this problem as well, and am quite sure it's due to a faulty logic board, and/or the inability of the machine to properly access RAM and other key components. My MBP 2.16, 1 GB constantly makes helicopter sounds that are emitted from the right speaker area. Apple replaced the first logic board in this machine while it was under warranty, and apparently put another defective one in. Overall, Apple hasn't been to helpful since.

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

Spotlight not indexing after hard drive replaced

Hi all
Just wondering if anyone knows how to encourage Spotlight to re-index? Just had my hard drive replaced as part of the recall, and now Spotlight wont index anything.
I've tried previous suggestions (adding and removing hard drive to privacy list, commands through terminal etc), but it's still not working. All the software is up to date (10.7.5).
Any ideas? It's incredibly annoying, and making working on this computer virtually impossible at the moment.
Cheers

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console 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. Click Utilities, then Console in the icon grid.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
Enter "mdworker" (without the quotes) in the Filter text field. Post the most recent 50 or so messages that appear in the Console window — the text, please, not a screenshot.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into a message.
Some personal information, such as the names of your files, may be included — edit that out, too, but don’t remove the context.
Step 2
Do the same with the search string "mds".

IPhoto/Spotlight not indexing SOLUTION

For those iPhoto 6 users whoose comments and keywords not being indexed by Spotlight, here is the solution to your problem!
If you are getting * Parsing file: '~/Pictures/iPhoto Library/AlbumData.xml'
ERROR: syntax error (<key>PhotoCount</key>) when you try to manually index your iPhoto library with mdimport, this will solve your problem!
You can only have single-line comments on your photos:
- Create a smart album: "Comments... contains... [option][return]"
Note: press option+return with your keyboard... the box will appear blank
- The smart album should become populated with photos where you entered a comment containing a character return
- Click the ( i ) in the bottom left-hand corner to draw up the info for each file, and manually remove the character break until your smart alum is empty OR go to Photos -> Batch Change and enter a new comment. Make sure that "append" is UNCHECKED -- This will overwrite all of the comments.
Now, you must also make sure you only have single-line comments on your rolls:
- From the iPhoto Library, go to View -> Sort Photos -> By Film Roll
- Hold the Apple (command) key, and click the drop down triangle once or twice (until all are collapsed)
- Manually examine each roll and make sure that the comments (if any) are all on one line.
Note: If the comments are all on one line, the whole line will be visible in the collapsed view under the Film Roll name
Quit iPhoto
Open Terminal (in the Utilities folder)
- Type mdimport -f ~/Pictures and hit return
- After some time, a message should come up saying:
* Parsing file: '~/Pictures/iPhoto Library/AlbumData.xml'
As long as there is not an error message underneath, this is good!
- When the command has finished running and you're at a blank prompt again, quit Terminal
Open iPhoto
- Click iPhoto in the menu bar, and go to Preferences
- Click the Keywords tab
- Click the "+" and create a new keyword called Spotlight
- Close out of iPhoto preferences
- From the iPhoto Library, select all of the photos (Edit -> Select All)
- Get info on the files (Photos -> Get Info)
- Select the Keywords tab
- CHECK the box that says [Spotlight] *THIS MIGHT TAKE A WHILE
- UNCHECK the box that says [Spotlight] * THIS MIGHT TAKE A WHILE
Note: This forces all of the pictures to be updated in the database
- Quit iPhoto
Search for your comments and keywords with Spotlight

Can I ask, does this need to be done every time you add photos to iPhoto, or is this a one-off trick to get Spotlight to look at iPhoto keywords in the first place?
My first experience with iPhoto is iPhoto6 so I don't have any baggage that I am bringing from earlier copies of iPhoto. I've imported in 1500 photos and am working my way through tagging them with keywords and am hoping that spotlight will index them. Is this bug related to keywords applied in older versions of iPhoto, or does the issue manifest itself even on a brand new library? Are Apple looking to patch iPhoto / Spotlight to resolve this?
Thanks.
Graham

IPhoto/Spotlight not indexing SOLUTION *edit

For those iPhoto 6 users whoose comments and keywords not being indexed by Spotlight, here is the solution to your problem!
If you are getting * Parsing file: '~/Pictures/iPhoto Library/AlbumData.xml'
ERROR: syntax error (<key>PhotoCount</key>) when you try to manually index your iPhoto library with mdimport, this will solve your problem!
You can only have single-line comments on your photos:
- Create a smart album: "Comments... contains... [option][return]"
Note: press option+return with your keyboard... the box will appear blank
- The smart album should become populated with photos where you entered a comment containing a character return
- Click the ( i ) in the bottom left-hand corner to draw up the info for each file, and manually remove the character break until your smart alum is empty OR go to Photos -> Batch Change and enter a new comment. Make sure that "append" is UNCHECKED -- This will overwrite all of the comments.
Now, you must also make sure you only have single-line comments on your rolls:
- From the iPhoto Library, go to View -> Sort Photos -> By Film Roll
- Hold the Apple (command) key, and click the drop down triangle once or twice (until all are collapsed)
- Manually examine each roll and make sure that the comments (if any) are all on one line.
Note: If the comments are all on one line, the whole line will be visible in the collapsed view under the Film Roll name
Quit iPhoto
Open Terminal (in the Utilities folder)
- Type mdimport -f ~/Pictures and hit return
- After some time, a message should come up saying:
* Parsing file: '~/Pictures/iPhoto Library/AlbumData.xml'
As long as there is not an error message underneath, this is good!
- When the command has finished running and you're at a blank prompt again, quit Terminal
Open iPhoto
- Click iPhoto in the menu bar, and go to Preferences
- Click the Keywords tab
- Click the "+" and create a new keyword called Spotlight
- Close out of iPhoto preferences
- From the iPhoto Library, select all of the photos (Edit -> Select All)
- Get info on the files (Photos -> Get Info)
- Select the Keywords tab
- CHECK the box that says [Spotlight] *THIS MIGHT TAKE A WHILE
- UNCHECK the box that says [Spotlight] * THIS MIGHT TAKE A WHILE
Note: This forces all of the pictures to be updated in the database
- Quit iPhoto
Search for your comments and keywords with Spotlight

Can I ask, does this need to be done every time you add photos to iPhoto, or is this a one-off trick to get Spotlight to look at iPhoto keywords in the first place?
My first experience with iPhoto is iPhoto6 so I don't have any baggage that I am bringing from earlier copies of iPhoto. I've imported in 1500 photos and am working my way through tagging them with keywords and am hoping that spotlight will index them. Is this bug related to keywords applied in older versions of iPhoto, or does the issue manifest itself even on a brand new library? Are Apple looking to patch iPhoto / Spotlight to resolve this?
Thanks.
Graham

How I solved my Spotlight+ Mail indexing problem

OK, so I thought I would post my solution to a stubborn indexing problem, for people who may have the same issue (and it does seem many people do).
Problem: Spotlight index was unreliable. In particular, Spotlight was terrible at indexing mail. It could not find the messages by content that it would find by searching the "from" field, nor could it find those reliably. Unusable.
What DID NOT work:
-- adding and removing any folder whatsoever in the Privacy preferences of Spotlight. The index would rebuild, but with the same problems.
-- doing this via terminal (e.g, using sudo mdutil -E /Volumes/MyHardDisk)
-- using Onyx
-- using Spotless
-- simply reinstalling the system
-- manually modifying the plist files inside the .spotlight folder to add and remove the folders that would not get indexed.
What DID work:
-- first, I reinstalled the system. That's not such a big deal. Upgrade up to 10.4.6
-- then, I authorized the root user (that's probably not necessary) (this, you do by using Netinfo manager)
-- Then, I deactivated the index (via terminal:
sudo mdutil -i off /Volumes/MyHardDisk
-- now the tricky part. This concerns Mail, in particular.
I have a very complex mail folder (tens of thousands of messages). I noticed that inside each mail folder, I had two things that were not supposed to be there
1. a copy of each folder.mbox which was empty, but with the same name without the extension .mbox. This is probably something that was created while importing mail from Panther to Tiger, for what I can tell.
2. Most importantly, a file named ".index.ready". This also, apparently, was an old legacy coming from Panther. I suspect this was the main problem for the lack of indexing in Mail.
Ok, so... I deleted these folders and files. If you have a complex structure of subfolders, you can delete the files with an Unix command by first cd to your mail folder, and then use
find . -name \.index.r* -ok rm {} \;
which will ask you confirmation before deleting each file.
It was faster to remove the empty subfolders by hand, as they all had different names.
-- Ok, at this point, I erased entirely the .Spotlight-V100 directory which stays at the root of your computer. You can do it with a rmdir command from the terminal or, as I did, you can login as root (remember, we activated root), use a utility that allows you to see hidden files (e.g., Tinkertool), and move it manually to the trash folder.
Then I emptied the trash. For superstition, I restarted, and let the index be built again (that took about 5 hours in my computer, for an HD with about 60 gb occupied on it).
Now everything seems to work perfectly fine. I don't know whether this procedure can be shortened, but I do know that nothing else worked for me. I thought I would post it here as I spent sooo much time to solve this problem, and furthermore, I found that none of the suggested solutions would work.
OK, your responsibility to do it, if you want to do it. Hope nobody needs to!
Best to you all,
l.
Mac OS X (10.4.6)

Thank you, thank you, thank you, Lucabo! Using ideas from your post, I also (at least for now) solved my Mail indexing problem. One day (not even after an upgrade) Mail just quit finding messages by content, even when I had open a message with that content!
What I did:
-- In System Preferences, told Spotlight to index only Mail (I just use grep from a Terminal window for everything else!)
-- Ensured Mail app wasn't running
-- Backed up my Library/Mail folder to an external disk
-- Turned off indexing via Terminal (after sudo sh), with
mdutil -i off /Volumes/MyHardDisk
-- Deleted old files in my mailboxes (inside the whatever.mbox folders):
.index.ready
mbox
tableofcontents
content_index
It was clear that mbox, tableofcontents, and content_index were left over from a previous version of mail - they hadn't been accessed since I upgraded.
Note that I didn't delete the whatever.mbox folders (just the plain mbox file inside)!
-- Deleted (in Terminal) the .Spotlight-V100 in the root directory
-- Restarted my Mac. The indexing started itself. Since I had it set up to index only Mail, it took about 3-ish hours to finish (I have 100s of 1000s of emails in thousands of folders).
After the indexing finished, all the test searches that I tried worked. From now on I will always be suspicious if search doesn't find anything!
Also, I just checked - using the Spotlight field on the menu bar now works better too. When the Mail search problem showed up, I tried using the Spotlight field and the Spotlight window, but they would just flash up a few items, remove the list, over and over, sometimes with the beachball, then finally settle to an empty list. Now the Spotlight field seems to work.
I infer that the Spotlight index gets corrupted, and that the Spotlight code doesn't notice that it's reading junk from the index...
BTW, about the same time that search quit working, some emails in my Inboxes got highlighted with a dark brown background color. Have no idea why. They aren't marked as Junk (the junk messages have the text in the usual lighter brown). But, when I select a message with the dark brown highlight, mark it as junk, then mark it as not junk, the dark brown highlight goes away. On some occasions, just quitting Mail and restarting makes the dark brown highlights go away - but not always. Sigh... at least it's not a show stopper, even if it is ugly!
Thanks again, Lucabo, for your post!
Mac OS X (10.4.6)

Multi-column Index vs One index for each column

Hello everyone,
i have one table about 20 000 000 rows, some developers have to generate reports on it and i want to create indexes on this table.
The table has 34 columns, no primary key, no unique keys.
The "where..." clause of the reports usually use 8 columns but some reports uses 8 + some other columns.
can any one help me on what kind of indexes do i have to create?
1. one index for each column used in "where clause"
2. one index for 8 columns and some other indexes for other used columns
3. one index for all columns
or something else etc...
br flag

i have one table about 20 000 000 rows, some developers have to generate reports on it and i want to create indexes on this table.
The table has 34 columns, no primary key, no unique keys.
The "where..." clause of the reports usually use 8 columns but some reports uses 8 + some other columns.
can any one help me on what kind of indexes do i have to create?
1. one index for each column used in "where clause"
2. one index for 8 columns and some other indexes for other used columns
3. one index for all columns
or something else etc...What's the version of your data base? what kind of database you have, DWH or OTLP? The answer might depend on the type of database as far as bitmap indexes might suit or might not depending if you are runing DWH or OLTP kind of database
Let me suppose that you are runing OLTP database and you have a where clause with 8 columns.
1) are all those where clause equalities (where col1 = and col2 =) or there are inequalities?
2) could you evaluate the most repetitive columns?
3) could you know the column that could have the best clustering factor (the column which most follow a certain order in the table)
Based on that I would suggest to create one b-tree index having 8 columns (even though that it seems for me to high) this index should follow the following points:
1) put the most repetitive column at the leading edge (and compress the index if necessary)
2) put the columns that are used in equalitity predicate first
3) put the column having the best clustering factor first
The most precise index you have the best access you could gain.
Of course that you have to know that an index access is not always good and a FULL table scan is not always bad.
Best regards
Mohamed Houri
www.hourim.wordpress.com

Why to i have to plug in my mini display to vga monitor each startup

each startup my vga monitor will not come on unless I unplug and replug in my mini display adapter. then it comes on...does not happen in the sleep mode.

Jay Bullock wrote:
Has anyone else seen this/is it normal ?
No, and no. I would make an appointment at the Genius Bar and have it checked out. A full 30-second hang is also not normal. Five or six seconds, I have seen. Thirty? Never.
Easier said than done, nearest Genius Bar is an hour away, also machine is out of warranty. As I said it's been doing it forever, probably plugged it in 300 times. It only has the long hang once every so often. I'll live with it.

Spotlight is indexing but what? And why does it want access to the web?

I can see Spotlight is indexing, it spends several hours a day doing this, every day.
Where can i find more details like previous OS X versions? Which drive, how much time left etc.
Console was no help, any suggestions welcome.
Also, with "Spotlight Suggestions" and "Bing Web Searches" disabled in the Spotlight Search Results references, why is the process "Spotlight Web Content" still trying to access the web several times a day? I am not using Spotlight when this happens nor am i trying to preview any files that have web content in them. Most commonly it tries to connect to static.amazon.com on the http port.

In System Preferences > Spotlight > Search Results, if you have "Bookmarks and History" checked, then the "Spotlight Web Content" background process will crawl any web page that you recently visited to index its keywords. Uncheck that to turn it off.

Convincing spotlight to index other file types

I have a large number of LaTeX documents on my computer, but Spotlight seems unwilling to index them. How can I convince spotlight to go ahead and index/search files with a .tex extension just like it would any other ASCII text file?
Details: LaTeX source code is standard ASCII text, but the files have a ".tex" extension. These files never seem to show up in Spotlight searches, even if I search for terms that I'm certain are included. I'm guessing that Spotlight sees the extension, says "I don't know how to index files of this type" and moves on. How can I tell it to index (and then subsequently search) these files just like normal .txt files? (I'd probably like to do the same with other "source code" file extensions too...) Thanks!

I found that Spotlight would index thousands of my old LaTeX files if I dragged them to another location and then dragged them back again. Unfortunately, I found that just moving the folders they were in was not sufficient.
This move added the metadata "public.plain-text" to all the .tex files, even though, since OS X 10.4, cp amd mv is supposed to preserving metadata and forks (according the man pages of CpMac and MvMac).
I did this after I had modified TeXShop's Info.plist by adding the public.plain-text string to the UTTypeConformsTo key. This is described in the Link: [macosxhints: Add Quick Look support for certain file formats|http://www.macosxhints.com/article.php?story=20071028184428583] and by Tristan Hubsch in the Link: [Apple Discussion Topic: How to Spotlight (and QuickView) Hidden and Programming Files?|http://discussions.apple.com/thread.jspa?messageID=6880380]. I don't know if this is necessary for the change.

Get Spotlight to index a NAS disk?

Is it possible to get Spotlight to index a NAS disk? (Or should it do this normally but it's not working properly?).
I have a NAS disk permanently connected to my Mac (LaCie Ethernet Disk Mini) & every time I do a search on there it will churn away searching but not return any results.
Actually it seems like it might be a bug because as well as not returning any results once I've closed the Finder window it will still continue churning away searching (I can hear the disk activity).
It will continue until I reboot the computer.

OK, the Terminal is a the way that you access UNIX shell commands (the Mac command line interface). Instead of clicking on things you have to type the actual command into the "prompt" hit return, and then the shell executes the command. So you go to the Utilities folder and double click Terminal to launch it. Exactly what you see when it finishes launching will depend on how you have configured it, so it won't be exactly what I see, but there will be some words of encouragement and then the prompt, where you will type things:
Last login: Tue Mar 20 14:06:01 on ttyp1
Welcome to Darwin!
-bash:~francine$
The "$" is where you start typing, or you can copy and paste things in also. You would then type:
sudo mdutil -i on /Volumes/YOURDRIVENAME/
You must make sure everything you type is exactly as given, thus you may want to simply copy and paste this:
sudo mdutil -i on /Volumes/
and, making sure there is no space after that final "/" character, type the name of your drive exactly as it appears in Finder. If the name has any spaces in it be sure to surround it with quotes:
sudo mdutil -i on /Volumes/"MY FAT DRIVE"/
Then hit the Return key. You will be asked for your admin password, and given a little lecture (this is only delivered the first time you use a sudo command). The password you type is not echoed to the screen in anyway whatsoever, so type very carefully and when you finish hit the Return key again. You'll then get the notice that indexing is enabled. Type the word exit, hit Return, and then quit Terminal.
Francine
Francine
Schwieder

Secondary Index with or without MANDT field

HI ABAP Guru's,
What is necessary to add field MANDT while creation of secodary index in DBS.
But i some body my superiors challanged to me with out using MANDT our secoday index won't works.
But i tested few scenarios i am not get differnce.
please advice me exactly which scenarios it is mandatory.
Below are the Time taken with deffrent scnarios i created one test program to get the time with secondary index with out secodary index secondary index with mndat fiels
**&with out creation of seconday index
*1st time -57,103,681
2nd Time-55,388,294
**before creation of seconday index with out mandt
I1st time execution-324,119
2nd time progrm execution--391,134
3rd time progrm execution-327,046
4th time progrm execution336,774
5th time progrm execution359,100
6t time progrm execution-328,027
*before creation of seconday index with mandtiI1st time execution-367,623
2nd time progrm execution365,139
3rd-352,328
4th-369,122
5th-352,236
6th380,590
7th466,810
Thanks In Advance,
Kandula.
Edited by: Thomas Zloch on Nov 18, 2011 1:08 PM

Vishnu Tallapragada wrote:
So if you are maintaining multiple client data on the same database, then not adding MANDT to index will have undesirable effects as any select based on secondary index may return records that are not belonging to this client and deletes and additions on the index from multiple clients will lead to data integrity issues.
Wrong!
WHERE clause decides about data being selected, deleted or what-ever.
Index decides only about HOW data is accessed (if used), not WHAT data is accessed.
If your database returns a different result depending on the indexdefinition,
you should log a call at your DB vendor immediately, because this is a bug.
In general, as the client has usually only a small number of distinct values, it is not a good field,
to convince the database, that this index is a good idea. But on high volume tables it can be very selective
as far as the number of result records is concerned (might cut down 50% when 2 clients!).
In addition it is a very short field, so it should not cost much storage (esp. when compressable).
Szenario:
MANDT+IDX-Field with two clients and lets say 5000 record per client (so that idx access will be interesting),
assuming a given IDX value will return 50 records (25 in each client).
So the select will be
... WHERE MANDT=sy-mandt AND IDX=value
Accesing the index with only IDX will result in stepping down the index-tree (say 3 blocks) and then reading leafblocks
to get the 50 hits for IDX-value (assuming 30 records per leafblock -> 2 leafblocks required to gret the 50 records)
Right now you have accessed 5 blocks to get the address of 50 records that still need to be checked against MANDT.
So there is need to get 50 blocks (may be less, depending on clustering) to do a filter on MANDT
and get the final 25 records for the result.
If you put the MANDT field into the index it might require more space, so that we assume 20 records per leaf block now.
But since you can now filter MANDT already on the index blocks, you will again only need to get 5 blocks and
have the adress of the required 25 target records.
So getting the result is 55 blockinspections without MANDT in index and 30 blockinspections with MANDT in index in this case.
Now you can start pushing around values and statistics an calculate at what amount of data and average
size of resultsets it becomes right or wrong to include MANDT. It may turn out both ways, allthough I think
with MANDT being small, it is usually loss of brain cycles to calculate around for this.
You simply include it, it will cost only little space and it will never be wrong.
You leave it out, you will gain little space, but might end up with performance loss.
If you have only one client in the system, you can safely go with the saving space strategie, as long as you do not need
a UNIQUE secondary index.
Volker

Spotlight not Indexing (or showing any results)

Spotlight isn't working at all for me in Leopard. I had just done a format and clean install of Leopard, all apps and fully updated OS and apps patches. It's been 2 days now so I'd expect Spotlight would have indexed everything. However Spotlight returns no results for anything typed in the search box. Nothing.
Could the following be related? When I open Spotlight preferences>privacy and try to add ANY of my drives to the prevent list, it returns this error for all drives: "Privacy List Error. the item couldn't be added or removed because of an unknown error."

I fixed it and want to post what worked for anyone else with this problem. Spotlight would not return ANY result after the clean Leopard install. I cleaned out ALL the caches with the program Cocktail Leopard edition. That did the trick. Instantly Spotlight began indexing my drives. While I've used Cocktail for years I also found a program called "MainMenu" which has an actual button for "Re-index Spotlight". I didn't need it because Cocktail worked. But should cocktail not work for you I would try MainMenu next.

How to know when spotlight is indexing

hi,
in previous OS versions you could tell when spotlight is indexing by clicking the spotlight icon in the toolbar and the dropdown would tell you. now in yosemite how can we tell when spotlight is indexing? because i use mail.app a lot and search won't work properly until the indexing is done. thanks!
rc

Same way.
Re-index Spotlight: Spotlight: How to re-index folders or volumes - Apple Support
If that doesn't work, force it with this command in Terminal:
sudo mdutil -E /

Spotlight re-indexes with each startup

Similar Messages

Maybe you are looking for