MacOSX SL constantly indexing or similar

Hi everyone.
I´ve already been through a couple of threads covering "Constantly indexing" but could´t find a simililar situation as I´m not sure if really Spotlight is the issue here. I know I know: Snow Leopard might be old school but so am I.
My iMac-late2011/MayOSX-SL is running this now the third day:
/System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
/System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings
/private/var/folders/jZ/jZ2KTuydFVa+tlzLQGml1++++TI/-Caches-/com.apple.IntlDataC ache.le.sbdl
/System/Library/ColorSync/Profiles/sRGB Profile.icc
/System/Library/Fonts/Keyboard.ttf
/System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat .bundle/GLRendererFloat
/System/Library/Caches/com.apple.IntlDataCache.le.kbdx
/usr/share/icu/icudt40l.dat
/System/Library/Fonts/LucidaGrande.ttc
/System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/Resources/SArtFile .bin
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fram ework/Versions/A/Resources/Extras2.rsrc
/System/Library/Fonts/Helvetica.dfont
/System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/Resources/ArtFile. bin
/System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle /GLEngine
/System/Library/Extensions/ATIRadeonX3000GLDriver.bundle/Contents/MacOS/ATIRadeo nX3000GLDriver
/System/Library/Keyboard Layouts/AppleKeyboardLayouts.bundle/Contents/Resources/AppleKeyboardLayouts-L.d at
/private/var/folders/jZ/jZ2KTuydFVa+tlzLQGml1++++TI/-Caches-/com.apple.LaunchSer vices-025501.csstore
/usr/lib/dyld
/private/var/db/dyld/dyld_shared_cache_x86_64
/dev/null
->0xffffff80147c5840
->0xffffff80147c5840
/private/etc/security/audit_control
count=1, state=0x2
at this line it goes: Users/me/ all kind of files scattered over my system like Downloads/iTunes/Documents etc etc
->0xffffff80147c3380
->0xffffff80147c2f00
->0xffffff80147c2180
->0xffffff80147c3b00
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fram ework/Versions/A/Resources/Extras2.rsrc
/private/etc/security/audit_class
and I have no clue what it´s doing, if it´s a failure, if it ever will stop or what it is at all. All I can say it´s so annoying that I stay away from my iMac, because the process steals up to 100% CPU capacity, so working on that machine is hard to do.
Is there anybody who can tell me more about - or if and how I can stop this, because I need to do some jobs now.
Any help is much appreciated. Thanks in advance and have a nice day.
Cheers
F.

You can also try going to your user library folder in your user/home folder. Select Preferences/
com.apple.finder.plist. Move the .plist to your desktop.
Re-launch Finder by logging out/in and test. If it works okay, delete the plist from the desktop.
If the same, return the .plist to where you got it from, overwriting the newer ones.

Similar Messages

Mail constantly indexing Gmail account.

Ever since I upgraded to Snow Leopard, and now Lion, Mail constantly indexes my Gmail IMAP account which causes me to get locked out of Gmail for a day. I don't know why this is happening. I've tried to delete the index file, delete and re-add the account, nothing works.
Any ideas?

Did you find a solution for your issue? It sounds like an issue with the SMTP server settings for that email account. If you still haven't resolved this issue, feel free to look at the directions I wrote for another post:
https://discussions.apple.com/message/20345791#20345791
Good luck!

Spotlight constantly indexing and Time Machine endlessly preparing backup

Hi,
I have a Macbook Pro 5,5 and Mac OS X 10.8.4
Lately I noticed that Spotlight was pretty much constantly indexing, so I went to "System Preferences/Spotlight/Privacy" and I dragged my HD there to prevent Spotlight from indexing it. Then rebooted my laptop and removed my HD again, which caused my Spolight to start indexing again.
After a night of indexing, everything seemed to be working fine. Nevertheless, today Spotlight is once again constantly indexing my computer, and the bar just won't go beyond "Estimating Indexing Time". What could I do to solve this issue?
Related to this, I assume, is my inability to backup through Time Machine. I feel like Time Machine is waiting for Spotlight to complete its indexing in order to start its backup-job, is that correct?
Thanks for your help,
Sander

If you have more than one user account, these instructions must be carried out as an administrator.
Triple-click anywhere in the line below on this page to select it:
syslog -k Sender mdworker -o -k Sender mds | grep -v boxd | tail | open -f -a TextEdit
Copy the selected text to the Clipboard (command-C).
Launch the 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. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V).
The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. The title of the window doesn't matter, and you don't need to post that.

Spotlight constantly indexing (mds Abort Trap)

A couple days ago I noticed in top that mds kept cycling through pids, getting into the 2000-3000 range within an hour of bootup. I checked the system log and noticed this message occuring prior to the problem:
Nov 18 12:03:00 Optimus-Prime launchd: Server 0 in bootstrap 1103 uid 0: "/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framewor k/Versions/A/Support/mds"[4806]: exited abnormally: Abort trap
As a result of this Abort trap, spotlight indexes constantly, prohibiting me from searching for anything.
I tried deleting the .Spotlight-V100 directories for my drives and rebooting, and that seemed to solve the problem until about 4 am today, when the symptoms showed up again.
Has anyone else noticed this occuring with their systems? Or maybe know of a solution short of deleting the directories and rebooting?

After being directed to the spotlight subforum, R C-R's post in http://discussions.apple.com/thread.jspa?threadID=234031&tstart=0
seems to have fixed the issue.

Spotlight constantly indexing in a never ending loop

I've upgraded my older Aluminium iMac Early 2008 model from Tiger to Snow Leopard to Lion and then Mountain Lion.
Since Mountain Lion, I've been having indexing problems. The mds process just doesn't want to stop. I have tried all the solutions.
Turn off mds from launchtl and then delete the /.Spotlight.V100/ folder, relaunch via launchctl again, then stopping indexing using, mdutil deleting via mdutil. Reboot, then also trying the recommended Machintosh HD drag into privacy and out again. I've done them all. I've added bootcamp to my privacy and also sugarsync drive and also my incomplete torrent folder.
I've re-indexed my drive, it's just no longer funny anymore. The problem is that the indexing process is running away. I check it via fs_usage for mds, and I can see the files it's opening and writing. This is not mdworker which matched my manual activity, e.g. if I make a numbers worksheet background, then of course it saves the file automatically and I can see in mdworker that it quickly indexes that file and stops.
The culprit is mds. It just continually indexes certain folders and files, which are just normal files and folders which I work on, e.g. my business documents, mail download mailboxes, iphoto library, etc. There doesn't seem to be a pattern to what it's doing. The files and folders run so fast over the terminal screen when I use fs_usage, that I know it's mds, because I can tell the activitiy matches the lines written to the terminal screen.
The problem is that this mds and HDD activity is NOT accompanied by any message in the little blue spotlight window, that is is currently indexing the drive. although it sounds exactly like it IS indexing the drive. Surely it doesn't have to reindex portions of the drive again and again. Shouldn't there come a point when it completely stops?
Normally, I have a silent computer after some indexing completes, but mostly it lasts only a day and then it starts chugging again.
Apart from re-installing, which I really don't want to do. What else is there I can try.

If you have more than one user account, these instructions must be carried out as an administrator.
Triple-click anywhere in the line below to select it:
syslog -k Sender mdworker -o -k Sender mds | grep -v boxd | tail
Copy the selected text to the Clipboard (command-C).
Launch the 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. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V).
The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
A TextEdit window will open with the output of the command. Post the contents of that window (not the Terminal window), if any — the text, please, not a screenshot. The title of the window doesn't matter, and you don't need to post that.
If any personal information appears in the output, anonymize before posting, but don’t remove the context.

Spotlight is CONSTANTLY indexing my hard drive

Mavericks Server 10.9.5.
Whenever I use Spotlight, I virtually always get "Indexing <my hard drive name>", and "Estimating indexing time".
If I put in a search term, it often works, but still with the "Estimating indexing time" barber pole at the bottom of the results window.
I have tried all the known solutions with no effect. The problem has persisted through multiple OS updates.
Possible clue: I notice a LOT (like about 5 every second) of lines like this in the System Log:
7:49:533 AM mdworker: (Warning) Import: Bad path:
(other than the timestamp, they are all exactly like this).

Safari Web Content can build up over time. You could try doing Safari>Reset Safari. I check every item in the list except "Saved names and Passwords" which would otherwise be a pain to re-enter for everything.
Note also that unlike SL, Lion does not quit the app when you click on the x, so maybe you have very many lingering in memory. This should not make a difference as normally the memory manager copes with it, but just maybe a third party app is not letting go as it should.

Spotlight constantly indexing

Struggling with my new MacBook.
When I try to install some of my software (Macromedia Dreamweaver & Kaleidagraph), programs work but Spotlight never completes indexing.
I could live without it (spotlight), but I am worried it is a symptom of a larger problem. I have done erase/install several times, but every time I reload the programs the problem arises again.
Any thoughts?

Hi Miriam, thanks for responding!
I have a couple folders in the privacy area, but it's all documents and the like, no applications or programs.
In the Search Results I don't know if I ever really did anything to it, but it has the following: Applications, System Preferences, Documents, Folders, Mail Messages, Contacts, Events & To Do Items, Images, PDF Documents, Webpages, Music, Movies, Fonts, and Presentations. They are all checked.

Mds constantly indexing the same folder

Every few days, mds will continuously index the Archive Utility.app folder (I monitored it with Instruments). I've tried to let this run its course for several hours but it never finishes. I used both mdutil and Onyx to delete the Spotlight cache and let Spotlight rebuild the indexes but the problem comes back after several days. I've currently added Core Utilities to Spotlight's privacy preferences, but this isn't a desirable solution.
Has anyone encountered and fixed this problem?

This is happening to me. plus CPU usage at 98%.
All this began when I installed Windows and VMware Fusion.
mysqld is also using a tone of vertural memory.
I suspect some type of corruption or a virus that came with using windows

Visual Similarity Index Error

I've had PS Elements 7 for a while now, but a couple of months ago I started getting a dialog box that says, "The visual similarity index must be rebuilt or your visually similar photos will not be ordered properly." I get this dialog box when uploading pictures from my D80. Of course I click OK, the index rebuilds, and I proceed. I'm sure it's related to the Auto Suggest Photo Stacks option I use to group the JPG and NEF files together, but I've always used this option and never received the warning dialog box before, even when I was using Elements 5. Has anyone else run into this, and if so, have you been able to correct it?
Thanks,
Gary

1. Try File > Catalog > Repair. When it says "No Errors Were Found", check Re-Index Visual Similarity Data and click Repair Anyway.
2. If that doesn't help, try deleting the thumbnail cache and then repeating step 1. See this FAQ for deleting the cache:
http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Recreate_Organizer_thum bnails
Note that PSE generates about 5 to 10,000 thumbnails per hour, so it could take a while.
To help others here, let us know if this works.

Spotlight Indexing, Systemstats, Missing File, All After Mavericks Upgrade

Dear Mac Support Communities,
The upgrade to OS X 10.9.4 has crippled my computer.
My main question is: should I reformat, or should I wait for a patch to come out to solve whatever is wrong with Mavericks? I explain below.
Spotlight is constantly indexing. The mdworker is all over the place on the Activity Monitor—4% and then it explodes to 85% of CPU usage. Systemstats kicks in randomly (connected to spotlight perhaps?) and eats up 90% of my CPU and 3gigs of RAM. Time Machine takes AGES to backup.
I have not been able to stop Spotlight's endless indexing. I have moved my hard drive and my Time Machine backup into the 'private' filter in 'Spotlight Preferences.' I have also tried the "sudo mdutil -a -i off" trick to stop indexing altogether. But Spotlight Indexing goes "off" and then automatically turns "on" in Terminal. Spotlight carries on, and the computer performance is choppy.
I've run disk repair. First, I repaired permissions. Then I verified and attempted to repair the the hard drive. There is a missing file apparently, and I therefore must reformat. This is very first issue I've ever had with the hard drive since I bought the computer. Considering how awful Mavericks has been—I have been reading other Support Communities posts—I'm nervous about something going wrong, or that all these problems will persist after the reformat.
All of this has occurred three days after my upgrade to to OS X 10.9.4. I have heard of numerous people having problems with Mavericks. All similar problems concerning missing files, haywire spotlight, systemstats devouring any remaining CPU power and memory space, and slow Time Machine back-ups.
Anyone with the same problems? Care to theorize some solutions?
I have a late 2008, 15inch MacBook Pro., 2.53 GHz Intel Core 2 Duo, 8 GB 1067 MHz DDR3, running OS X 10.9.4 (13E28).
Cheers! I appreciate the help.

Older Macs have more troubles under Mavericks. Considering the age of your Mac, it's not uncommon to start have hardware issues like drive failure.
To repair the drive you must boot from the Recovery Drive.
Boot into the Recovery Drive by holding down Command R when restarting.
Run Repair Drive and Repair Permissions using Disk Utility in Recovery.***
Next Reset Home Directory Permissions and ACLs following directions here This will serve two purposes. It will reset YOUR permissions. Not the same as Disk Utility reset permissions and it will cause Spotlight to re-index your drive when restarting.
Restart
Download and run the combo updater to refresh your OS X files.
OS X Mavericks 10.9.4 Update (Combo)
http://support.apple.com/kb/DL1755
MORE INFO ON WHY RUNNING COMBO FIXES ISSUES
Apple updates available from the Software Update application are incremental updates. Delta updates are also incremental updates and are available from Apple Downloads (software updates are generally smaller than delta updates). The Combo updates contain all incremental updates and will update files that could have become corrupted.
Combo updaters will install on the same version as they're applying--no need to roll back or do a clean install.
"Delta" updaters can only take you from one version to the next. For example: 10.9.3 to 10.9.4. If somehow the 10.9.3 is missing something it should have, and that something isn't changed between 10.9.3 and 10.9.4 it will still be stale after the delta update.
***If Disk Utility is unable to repair you will have to copy your data to an external drive first. Reformatting will erase the drive. You should have a backup regardless, if your data is important to you. Just like a seat belt and an air bag protect you in different ways when driving, you need both Time Machine and a clone for full protection. If you don't have an external drive for backup, I can give you some suggestions to get you started.
Both of these applications can be used to create a clone.
SuperDuper! http://www.shirt-pocket.com/
CCC http://www.bombich.com/download.html

Multi-column BITMAP index vs. multiple BITMAP indices?

Given the table (simple, made-up example):
CREATE TABLE applicant_diversity_info (
applicant_diversity_id NUMBER(12), PRIMARY KEY(applicant_diversity_id),
apply_date DATE,
ssn_salted_md5 RAW(16),
gender CHAR(1), CHECK ( (gender IS NULL OR gender IN ('M','F')) ),
racial_continent VARCHAR2(30), CHECK ( (racial_continent IS NULL
OR racial_continent IN ('Europe','Africa','America','Asia_Pacific')) ),
ethnic_supergroup VARCHAR2(30), CHECK ( (ethnic_supergroup IS NULL OR ethnic_supergroup IN ('Latin American','Other')) ),
hire_salary NUMBER(11,2),
hire_month DATE,
termination_salary NUMBER(11,2),
termination_month DATE,
termination_cause VARCHAR2(30), CHECK ( (termination_cause IS NULL
OR termination_cause IN ('Resigned','Leave of Absence','Laid Off','Performance','Cause')) )
Oracle (syntactically) allows me to create either one BITMAP index over all four small-cardinality columns
CREATE BITMAP INDEX applicant_diversity_diversity_idx ON applicant_diversity_info (
gender, racial_continent, ethnic_supergroup, termination_reason );
or four independent indexes
CREATE BITMAP INDEX applicant_diversity_gender_idx ON applicant_diversity_info ( gender );
CREATE BITMAP INDEX applicant_diversity_race_idx ON applicant_diversity_info ( raceial_continent );
etc.
What is the difference between the two approaches; is there any meaningful difference in disk-space between the one multi-colum index and the four single-column indexes? Does it make a difference in what the query-planner will consider?
And, if I define one multi-column BITMAP index, does the order of columns matter?

>
What is the difference between the two approaches; is there any meaningful difference in disk-space between the one multi-colum index and the four single-column indexes? Does it make a difference in what the query-planner will consider?
And, if I define one multi-column BITMAP index, does the order of columns matter?
>
You may want to read this two-part blog, that answers that exact question, by recognized expert Richard Foote
http://richardfoote.wordpress.com/2010/05/06/concatenated-bitmap-indexes-part-i-two-of-us/
http://richardfoote.wordpress.com/2010/05/12/concatenated-bitmap-indexes-part-ii-everybodys-got-to-learn-sometime/
As with many things Oracle the answer is 'it depends'.
In short the same considerations apply for a concatenated index whether it is bitmap or b-tree: 1) will the leading column usually be in the predicate and 2) will most or all of the index columns be specified in the queries.
Here are some quotes from part 1
>
Many of the same issues and factors in deciding to create a single, multi-column index vs. several, single column indexes apply to Bitmap indexes as they do with B-Tree indexes, although there are a number of key differences to consider as well.
Another thing to note regarding a concatenated Bitmap index is that the potential number of index entries is a product of distinct combinations of data of the indexed columns.
A concatenated Bitmap index can potentially use less or more space than corresponding single column indexes, it depends on the number of index entries that are derived and the distribution of the data with the table.
>
Here is the lead quote from part 2
>
The issues regarding whether to go for single column indexes vs. concatenated indexes are similar for Bitmap indexes as they are for B-Tree indexes.
It’s generally more efficient to access a concatenated index as it’s only the one index with less processing and less throwaway rowids/rows to contend with. However it’s more flexible to have single column indexes, especially for Bitmap indexes that are kinda designed to be used concurrently, as concatenated indexes are heavily dependant on the leading column being known in queries.

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.

Mail search not working + Spotlight keeps indexing

I have an old problem that has resurfaced after creating a new user on my Mac. Mail search brings no results and Spotlight is constantly indexing - day in, day out. It never seems to get there. I tried turning my hard drive to private in Spotlight settings and then taking it out. Previously Spotlight seemed to get bogged down with external drives now it's stuck indexing my Mac.
Any advice? Is there a way I get unstick this?

I can't believe that Apple have STILL not sorted this out. I haven't created a new user (so it's nothing to do with that), but Mail.app won't find anything when searching "Entire Message" in the current Mailbox or in "All Mailboxes". This has been ongoing since Leopard was first released, and we are now up to 10.5.8 without this being fixed.
Here are some of the reports:
Topic : Spotlight does not search Mail messages
http://discussions.apple.com/thread.jspa?threadID=1366101
Topic : Search "Entire Message" returns "0 Found" in mailboxes
http://discussions.apple.com/thread.jspa?threadID=1341832
Topic : Spotlight died on me
http://discussions.apple.com/thread.jspa?threadID=1226645
Topic : I can't search through my inbox!
http://discussions.apple.com/thread.jspa?threadID=1387827
Topic : Leopard's Spotlight doesn't search Mail messages
http://discussions.apple.com/thread.jspa?threadID=1219030
Topic : Mail Search
http://discussions.apple.com/thread.jspa?threadID=1347387
Topic : Mail Won't Search
http://discussions.apple.com/thread.jspa?threadID=1204827
Topic : Search does not work
http://discussions.apple.com/thread.jspa?threadID=1254966
Topic : Mail search not working
http://discussions.apple.com/thread.jspa?threadID=1289253
Topic : Unable to Search Mailbox
http://discussions.apple.com/thread.jspa?threadID=1232504
Topic : Why is Search in Mail.app busted?
http://discussions.apple.com/thread.jspa?threadID=1403758
Topic : Mail Search comes up empty
http://discussions.apple.com/thread.jspa?threadID=1378473
Topic : Search "Entire Message" not working with Smart Mailboxes?
http://discussions.apple.com/thread.jspa?messageID=6548355&#6548355
Topic : Mail searches yield no results! Smart mailboxes also yield no results!
http://discussions.apple.com/thread.jspa?threadID=1395508
Topic : 10.5.2 Mail.app search still not working (Entire Message)
http://discussions.apple.com/thread.jspa?threadID=1389466

SP with input parameters to disable and enable indexes

I need to build a stored proc script with input paramters to disable indexes and enable indexes of specific tables.
Parameter would be tablename,schemaname,a value input which will determine if it is for disabling index or enabling index
I will have a reference table which would hold the specific tables
Below is the ddl script and sample data for reference
USE [test]
GO
/****** Object: Table [dbo].[TestingIndex] DDL Script Date: 01/27/2014 22:38:39 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
CREATE TABLE [dbo].[TestingIndex](
[tablename] [varchar](30) NULL,
[schemaname] [varchar](10) NULL,
[Flag] [varchar](1) NULL
) ON [PRIMARY]
GO
SET ANSI_PADDING OFF
GO
sample data
tablename
schemaname
Flag
tableabc
abc
y
tabledef
def
y
tableghi
ghi
y
All I want to do is disable all the indexes of the tables which are present in my reference table by looping through the reference tables.
Similarly I want to do enable all the indexes of the diabled table using the reference table
Any help would be appreciated and best way to do it thinking all pros n cons.
Mudassar

New code with changes
USE [TEST]
GO
/****** Object: StoredProcedure [dbo].[usp_indexes] Script Date: 1/28/2014 10:11:55 AM ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE PROCEDURE [dbo].[usp_indexes1]
@ref reftable READONLY,
@input int
AS
BEGIN
---Declare variables
DECLARE @tblnm VARCHAR(30), @schnm VARCHAR(10), @flag BIT, @sql VARCHAR(MAX)
---Declare cursor
DECLARE cursor_index CURSOR
FOR SELECT tablename, schemaname, flag FROM @ref
--Open cursor
OPEN cursor_index
FETCH NEXT FROM cursor_index INTO @tblnm, @schnm, @flag
WHILE @@FETCH_STATUS = 0
BEGIN
if @input =1
BEGIN
SET @sql = 'ALTER INDEX ALL ON '+@schnm+'.'+@tblnm+' DISABLE '
print @sql
EXEC sp_execute @sql;
END
else
BEGIN
SET @sql = 'ALTER INDEX ALL ON '+@schnm+'.'+@tblnm+' REBUILD '
print @sql
EXEC sp_execute @sql;
ALTER INDEX ALL ON dbo.Test1 DISABLE
END
FETCH NEXT FROM cursor_index INTO @tblnm, @schnm, @flag
END
CLOSE cursor_index
DEALLOCATE cursor_index
END
GO
result when I execute it gives below message
(3 row(s) affected)
ALTER INDEX ALL ONdbo.Test1DISABLE
Msg 214, Level 16, State 2, Procedure sp_execute, Line 1
Procedure expects parameter '@handle' of type 'int'.
ALTER INDEX ALL ONdbo.Test3DISABLE
Msg 214, Level 16, State 2, Procedure sp_execute, Line 1
Procedure expects parameter '@handle' of type 'int'.
ALTER INDEX ALL ONdbo.Test4DISABLE
Msg 214, Level 16, State 2, Procedure sp_execute, Line 1
Procedure expects parameter '@handle' of type 'int'.
DECLARE @ref reftable
INSERT INTO @ref
SELECT * FROM testingindex
EXEC usp_indexes1 @ref,1
but when I go n check indexing status no tables have been disabled using the below query it shows still enabled
select sys.objects.name as 'table',
sys.indexes.name as 'index',
is_disabled = case is_disabled
when '1' then 'disabled'
when '0' then 'enabled'
end
from sys.objects join sys.indexes
on sys.objects.object_id = sys.indexes.object_id
where sys.objects.name in('Test1','Test3','Test4' )
below are my table schema and index script (similar for 3 tables i m using for testing)
CREATE TABLE [dbo].[Test1](
[YEAR] [varchar](10) NULL,
[MONTH] [varchar](10) NULL,
[MONTH_VAL] [varchar](10) NULL
) ON [PRIMARY]
GO
SET ANSI_PADDING OFF
GO
USE [TEST]
GO
/****** Object: Index [NonClusteredIndex-20140128-112203] Script Date: 1/28/2014 11:23:48 AM ******/
CREATE NONCLUSTERED INDEX [NonClusteredIndex-20140128-112203] ON [dbo].[Test1]
[YEAR] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
GO
Mudassar

Index order in Oracle 10g

Hi
I have a query:
I have a table having date and status as fields. Date is indexed.
Now i want to know whether the performance will hit if i make the query as:
where status = 'A' and date >= sysdate-100 and date <= sysdate
Does it matter that the where clause ordering should be as per ordering of indexes?
Similarly the same thing for partition. If date field is partitioned, will the partitioning advantage is there if we put status condition first.
Regards

The optimizer will choose the order of operations that it believes will cause your query to run the most quickly regardless of the order you specify conditions in your WHERE clause. The optimizer's decision will be driven by a number of factors-- optimizer parameters, database version, system statistics, table statistics, index statistics, histograms, the selectivity of your conditions, etc. No one can say with any level of certainty what the optimizer in your particular database with your particular tables and indexes with your particular statistics would generate for a query plan.
If you as a human have reason to believe that the date condition is sufficiently selective that the optimizer should use that to do an index range scan as the first step, the optimizer should come up with that plan assuming your statistics back up your intuition.
Justin

MacOSX SL constantly indexing or similar

Similar Messages

Maybe you are looking for