Rebuilding database in Aperture

Rebuilding database in Aperture causes "Recovered Folder" to appear in project, even with Aperture & Mac trashes empty. Tried deleting "recovered" images and emptying trashes then rebuilding but it has the same effect, another Recovered Folder.

Kirby Krieger wrote:
Mark Alan Thomas wrote:
Don't rebuild the database unless absolutely necessary. Much better to repair. Rebuilding should be a last resort.
While I agree "repair" should -- as Apple recommends -- precede "rebuild", I have not in my experience found any reason to not run "rebuild" when needed, and have never seen an ill effects. Have you?
I have. It was related to a bug I'd discovered a few years ago. Rebuilding the database made it worse, and afterward I was warned that rebuilding could be destructive, and that it should only be done as a last resort. So be careful.
Here's the thread:
https://discussions.apple.com/message/15334014#15334014

Similar Messages

Rebuild Database did not reduce the database size

I just completed a rebuild database. The rebuild completed much quicker than anticipated and in the end the did not reduce in size.
This is my first rebuild and since original installation I have deleted a number of masters. From my understanding thumbnails and previews are not deleted when the master is deleted. In order to delete the thumbnails and previews the db must be rebuilt. Is this correct?
The db is over 31.1gb. The rebuild took approx 10 minutes and when completed the db size was still 31.1gb. There was a message during the rebuild that read "Recovering projects". I was expecting to see stats showing previews and thumbnails being generated in the activity window but don't see it. Has the db been rebuilt?
Thanks for any assistance.

Rebuilding the database is for disaster-recovery, not file maintenance. I certainly wouldn't do it unless something was fundamentally broken and the application didn't run.
"rebuilding" the database seems to do the following:
(1) remove the database file completely (not even to the trash, it destroys the database utterly)
(2) run through the plist files and reconstruct a brand-new database from them all
I checked this (on an empty library) using hard-links from the commandline, and step (1) above scared me sufficiently that I'd only rebuild the database as an absolute last resort.
Now, 31GB seems a lot for a database that only took 10 minutes to rebuild - are you sure you're not telling us the size of the library (to find the database size, right-click on the library and select view-package-contents, then open the 'Aperture.aplib' folder and find the size of the 'Library.apdb' file. That's the file you're changing when you 'rebuild database'.)
If you're telling us the size of the entire aperture library instead, then that size will be completely dominated by the master RAW files you've imported. I'd guess your library will be less than 10MB.
My understanding is that previews are deleted (since they're stored as separate files alongside the master image, if you look in the folder hierarchy), but thumbnails aren't. The thumbnails are aggregated together into one-file-per-project (presumably for speed of access), and I'd guess the space is reclaimed for future use, but the file doesn't get any smaller. That's a classic trade-off for speed-of-access, and users like us are normally very keen on things being fast
-=C=-

Rebuild database 2005q4

Hi,
I'm in trouble with csdb rebuild. I have a copy of the *.db in other directory and run csdb rebuild [dbdir] [rebuild_dir]. the output is:
Building calprops based on component information.
Please be patient, this may take a while...
Scanning events database...
41134 events scanned
41134 events copied
Scanning todos database...
828 todos scanned
828 todos copied
Scanning deletelog database...
42430 deletelog entries scanned
Scanning gse database...
1864 gse entries scanned
Scanning recurring database...
498 recurring entries scanned
Successful components db scan
Calendar database has been rebuilt
Building components based on calprops information.
Please be patient, this may take a while...
Scanning calprops database to uncover events...
After that it takes a looooooong time doing nothing. I think I'm patient but one night at 0,02% of CPU is so much.
A truss of the process say :
lwp_park(0xF6A37E98, 0) Err#62 ETIME
/4: lwp_park(0xF6A37E98, 0) Err#62 ETIME
/4: lwp_park(0xF6A37E98, 0) Err#62 ETIME
/4: lwp_park(0xF6A37E98, 0) Err#62 ETIME
/4: lwp_park(0xF6A37E98, 0) Err#62 ETIME
/4: lwp_park(0xF6A37E98, 0) Err#62 ETIME
/4: lwp_park(0xF6A37E98, 0) Err#62 ETIME
/4: lwp_park(0xF6A37E98, 0) Err#62 ETIME
/4: lwp_park(0xF6A37E98, 0) Err#62 ETIME
/4: lwp_park(0xF6A37E98, 0) Err#62 ETIME
/5: lwp_park(0xF6937A88, 0) Err#62 ETIME
/5: time() = 1163152714
/4: lwp_park(0xF6A37E98, 0) Err#62 ETIME
every 60 seconds it gets:
/5: time() = 1163152780
/5: time() = 1163152780
/5: time() = 1163152780
/5: stat64("/var/tmp/restoredb.1.rebuild/log.0000000001", 0xF6937448) = 0
/5: open64("/var/tmp/restoredb.1.rebuild/log.0000000001", O_RDONLY) = 23
/5: fcntl(23, F_SETFD, 0x00000001) = 0
/5: fstat64(23, 0xF69374E0) = 0
/5: llseek(23, 0x05EE0FDF, SEEK_SET) = 0x05EE0FDF
/5: read(23, "840FEE05 4\0\0\0 MA6B6 a", 12) = 12
/5: close(23) = 0
/5: stat64("/var/tmp/restoredb.1.rebuild/log.0000000001", 0xF6937448) = 0
/5: open64("/var/tmp/restoredb.1.rebuild/log.0000000001", O_RDONLY) = 23
/5: fcntl(23, F_SETFD, 0x00000001) = 0
/5: fstat64(23, 0xF69374E0) = 0
/5: llseek(23, 0x05ED9013, SEEK_SET) = 0x05ED9013
/5: read(23, "\0\0\0\0\0 ' MC2AA J o".., 32768) = 32768
/5: close(23) = 0
Thanks in advance.

Rebuilding the database is for disaster-recovery, not file maintenance. I certainly wouldn't do it unless something was fundamentally broken and the application didn't run.
"rebuilding" the database seems to do the following:
(1) remove the database file completely (not even to the trash, it destroys the database utterly)
(2) run through the plist files and reconstruct a brand-new database from them all
I checked this (on an empty library) using hard-links from the commandline, and step (1) above scared me sufficiently that I'd only rebuild the database as an absolute last resort.
Now, 31GB seems a lot for a database that only took 10 minutes to rebuild - are you sure you're not telling us the size of the library (to find the database size, right-click on the library and select view-package-contents, then open the 'Aperture.aplib' folder and find the size of the 'Library.apdb' file. That's the file you're changing when you 'rebuild database'.)
If you're telling us the size of the entire aperture library instead, then that size will be completely dominated by the master RAW files you've imported. I'd guess your library will be less than 10MB.
My understanding is that previews are deleted (since they're stored as separate files alongside the master image, if you look in the folder hierarchy), but thumbnails aren't. The thumbnails are aggregated together into one-file-per-project (presumably for speed of access), and I'd guess the space is reclaimed for future use, but the file doesn't get any smaller. That's a classic trade-off for speed-of-access, and users like us are normally very keen on things being fast
-=C=-

Rebuilding Databases for indexing

Hi,
The question below is on rebuilding databases.
I have the intermedia to index xml documents .The encoding of the xml documents is UTF-8.
The Oracle database has a character set as "WE8ISO8859P1".
The tokens do not get indexed for 2-byte characters like i, g, etc.
Oracle support has suggested that the Database itself be rebuilt as UTF-8 to enable the encoding.
Can anyone please tell me if it is possible to rebuild the database Iam working on, without affecting the other applications running on ORACLE. Note that my application has a seperate schema.
In other words, can the rebuilding to UTF-8 be done on Database level for a specific schema or does it have to be universal.
Thanks
Syed

It is entirely your choice is you want to use one schema or multiple schemas, personally I prefer using multiple schemas as it makes life easier for recovery and problem solving.
Cheers
John
http://john-goodwin.blogspot.com/

Rebuilding databases

Hi,
The question below is on rebuilding databases.
I have the intermedia to index xml documents .The encoding of the xml documents is UTF-8.
The Oracle database has a character set as "WE8ISO8859P1".
The tokens do not get indexed for 2-byte characters like i, g, etc.
Oracle support has suggested that the Database itself be rebuilt as UTF-8 to enable the encoding.
Can anyone please tell me if it is possible to rebuild the database Iam working on, without affecting the other applications running on ORACLE. Note that my application has a seperate schema.
In other words, can the rebuilding to UTF-8 be done on Database level for a specific schema or does it have to be universal.
Thanks
Syed

Try the following:
1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your
User/Home/Library/ Preferences folder.
2 - delete iPhoto's cache file, Cache.db, that is located in your
User/Home/Library/Caches/com.apple.iPhoto folder (Snow Leopard and Earlier).
or with Lion and Mt. Lion delete the contents the User/Library/Containers/com.apple.iPhoto/
Data/Library/Caches/com.apple.iPhoto folder.
3 - reboot, launch iPhoto, reset the iPhoto preferences and try dragging again.
NOTE: In Lion and Mountain Lion the Home/Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and press the Return key - 10.7: Un-hide the User Library folder.
If you're running Mavericks, 10.9, go to your Home folder and use the View ➙ Show View Options menu to bring the this window:
where you can check the Show Library Folder checkbox.

After using migration assistant to a new Mac 10.9.5, Outlook failed to open...mssge "Could not rebuild database -18000"

After using migration assistant to my new MacBook Retina 10.9.5, Outlook failed to open...mssge "Could not rebuild database -18000"

See if this previous discussion/link to microsoft support helps
Re: There is a problem with the Outlook database. Your database could not be rebuilt. [-18000]

Rescuing and/or Accessing Images From Aperture Database Without Aperture

Early reviews of Aperture mentioned that Aperture created a closed, inaccessible database of all the images contained therein. This apparently means that these images cannot be accessed unless you have Aperture. Does anyone else feel nervous about this? What happens if the Aperture database is corrupted and won't open? As far as I can see, you would be toast because you couldn't reach your images. I would appreciate hearing from someone who can address these concerns. How stable is the Aperture database? Is there a chance it could be corrupted and refuse to open? And if so, how would you go about rebuilding it and/or rescuing your images? It also appears that the only way you can move images is by exporting them (which requires a working program).
Any thoughts?

No problem! Trying to answer these questions is a very helpful way to learn the app by looking at aspects of it I have not encountered yet.
Yes, you can rebuild the Aperture database in a similar way to Entourage (and iPhoto). Holding down command-option after launching Aperture will make a Rebuild Library dialog appear. HOWEVER, don't do this unless you really want to see it work, because there seems to be no way to cancel the process. You can choose Rebuild Now or Don't Rebuild. If you choose Don't Rebuild, your Projects will nonetheless need to be recovered before use. The dialog mentions a Rebuild Later button, but there is no such button available.
I have done this a few times both ways in the course of writing this, and there does not seem to be any negatives to rebuilding other than the time rebuilding takes, so if your projects aren't large it may be worth doing now to get comfortable with the process.
G5 Dual 2.7 Mac OS X (10.4.3)

Office 2011 for Mac - Error rebuilding database following full restore from Time machine

This is my first time on here, so will try to be brief and specific.
I have been using Outlook without issues. I had a logic board failure and had to replace my logic board on my Macbook pro.
After repair, I then restored the entire computer from my Time machine backup
Everything worked perfectly until I tried to use Outlook, when I was given an error message saying "Your Office database index is missing and needs to be rebuilt. This is usually caused by restoring an identity with Time Machine." It then offers
me a chance to rebuild using the Database Utility.
I went ahead and tried to rebuild, but after running through the 5 steps, the task failed and I was given another error msg: :Your database could not be rebuilt [-18000]
I did some research online and found an article which suggested I go back in time on my Time machine and find an old version of my 'Main Identity' folder from when Outlook was working. Then to copy that folder,
rename it 'Restored Main Identity' and paste it into the 'Office 2011 Identities' folder on my HD.
I have done that, so it now appears with the other identities in the Microsoft Database Utility, and then tried to rebuild again, but still no luck.
Any ideas on how I can get around this issue…. don't really understand how Outlook is the only thing that I can't get working after restoring my old data.
Tried to get some help from Microsoft, but they pointed me to this forum or wanted to charge me for advice…
Any help would be much appreciated,
Paul

Hi,
We mainly support Office problems on Windows, since you are using Office for Mac, I suggest you post the question to Office for Mac forum:
http://answers.microsoft.com/en-us/mac
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank
you for your understanding.
Regards,
Melon Chen
TechNet Community Support

Help, everytime I try to rebuild my library, aperture crashes (was my aperture library won't open)

I have tried to recover my aperture library through all methods specified by apple. Rebuild was my last option. Is this library lost for good? It is with all my masters and organized painstakingly over the last year.
I am running osx v10.6.7 on an intel 17" macbook pro. The library is 250GB on an external 5ooGB Harddrive. Aperture 3 with the latest version.
Any suggestions?

It is possible that there is a problem with the files sessionstore.js and sessionstore.bak in the Firefox Profile Folder.
Delete the sessionstore.js [2] file and possible sessionstore-##.js [3] files with a number and sessionstore.bak in the Firefox Profile Folder.
* Help > Troubleshooting Information > Profile Directory: Open Containing Folder
* http://kb.mozillazine.org/Profile_folder_-_Firefox
Deleting sessionstore.js will cause App Tabs and Tab Groups and open and closed (undo) tabs to get lost, so you will have to create them again (make a note or bookmark them).
See also:
* [1] http://kb.mozillazine.org/Session_Restore
* [2] http://kb.mozillazine.org/sessionstore.js
* [3] http://kb.mozillazine.org/Multiple_profile_files_created

IPhoto 11 issues syncing via itunes and rebuilding database

Hopefully someone can help here. I originally had an issue where some photos in an event would not sync. They are viewable OK in iPhoto, ut will not sync, even if they are renamed or editted. Based on some research I deleted the iPod photo cache to rebuild the Phone and iPad optimised versions. Now I can sync the event I had an issue with, but have another issue. Now I cannot sync all photos, events, etc.. I get "The iPhone cannot be synced. An unknonw error occured (-50). I can sync a subset, but seem to have an issue with 3 "Faces". If I go into iPhoto and look at all the photos that contain those Faces it all looks OK.
My assumption is that this is some kind of corruption in the iPhoto database, So I have tried to use the tools to fix it. A reapir of the permissions works OK, but when I try to repair the library database it flies along to 69% and then gets stuck.
I have put a lot of work into the faces and locations sections, so I would really like to fix this instead creating a new library.
Any ideas?

OK, some progress, btu not out of the woods yet.
THrough trial and error I found that by deleting the 3 of my 'faces' that would not sync I can now sync all photos again. i have since recreated then and can still sync it all. it seems that I still have an issue with the iPhoto database though as a repair sticks at 69%
I could live with this as it does not seem to be having an effect, but I am worried what it may mean in future.

IPhoto 11 (9.4.2) rebuilding database file

Hi All
iPhoto 11 keeps corrupting the database file resulting in the following:
•     deletion of video and photo particulaly those that were imported from my iPhone 5.
•     when recent photos and video are deleted as a result of the system recommending rebuilding the databse file there is no way to recover lost video and photos.
•     rearranging of the album list on the left hand side al;so ocours
•     after the system rebulsd the database file the photos are all duplicated (I have over (3,000 original files) I now have over 6,000.
The itunes libery is now extreamly unreliable. To try to resolve the problem I have moved the photos out of another library then created a new account. I then imported the library into the new account. This was fine for a few days then the problem of a corrupt database file came up again.
• I will try creating a new libraty again but this time import he photos manually and see how this goes.
If anyone has knowledge of the situation and can offer a better and or permanent fix please ket me know.
Kind regards
Tony

Moving a Library from account to account will not fix it.
Download iPhoto Library Manager and use its rebuild function. (In Library Manager it's the FIle -> Rebuild command)
This will create an entirely new library. It will then copy (or try to) your photos and all the associated metadata and versions to this new Library, and arrange it as close as it can to what you had in the damaged Library. It does this based on information it finds in the iPhoto sharing mechanism - but that means that things not shared won't be there, so no slideshows, books or calendars, for instance - but it should get all your events, albums and keywords, faces and places back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.

Rebuild database hanging at 100%

I'm using a 17" macbook pro that's about 18 months old and I'm running Snow Leopard.
I've updated Aperture to 3.1.1 but I'm having an odd problem.
As of last night, when I attempt to access a library I get a message saying that the library should be rebuilt. I accept that option, a progress bar appears and after about ten minutes reaches 100%. At that point nothing at all happens, I even left it in that state over night only to find nothing changed this morning.
The only way to finish the process is to force quit Aperture and when it relaunches the process begins again with the 'you should rebuild' message.
What concerns me even more is that I get exactly the same message even when I attempt to launch a Vault backup instead, even though that Vault was created when everything was working properly. The Vault is stored on an external HDD.
I've tried deleting the Aperture preferences and then tried deleting Aperture and reinstalling (then updated to 3.1.1). I've repaired permissions and repaired the HDD without any issues arising.
Does anyone have any tips?

kevlar35 wrote:
I'm using a 17" macbook pro that's about 18 months old and I'm running Snow Leopard.
I've updated Aperture to 3.1.1 but I'm having an odd problem.
The only way to finish the process is to force quit Aperture and when it relaunches the process begins again with the 'you should rebuild' message.
How did you determine that force-quitting was "the only way to finish the process"?
Does anyone have any tips?
Let Aperture run longer. Close all apps, be sure to set your laptop to not turn off/go to sleep/shut down the drives, connect it to a power source, and try the rebuild option again.
I recently rebuilt a (very large) Library -- it took about 24 hr. During much of this time Aperture was reported as using c. 90% of the processors' capacity (and the CPU temp soared).
IME, force-quitting Aperture is never a good step.

Constatly having to rebuild thumbnails in Aperture 2.1.4. Huge Library

I have over 62,000 images in one Aperture Library contained in several projects. One main project is over 48,000 images and requires me to rebuild the thumbnails almost weekly. It takes 12 hours to rebuild. What is wrong? What am I doing wrong. This is the main library that I use and don't know how to stop this. Is there something corrupt? Aperture Library is over 1.5TB

Forgot to mention the Aperture Library is over 1.5TB

Error opening database in aperture

Made a back up of aperture lib using time machine and now the lib will not open with error:
"There was an error opening the database for the library "~/Destop/Aperture Library.aplibrary".
I restored the file and still have the problem. Ran disk util and other checks of the machine and no joy!
Tried command-option without luck. Any other suggestions?

"Made a back up of aperture lib using time machine". What does that mean exactly? Time Machine should not be affecting your library unless you are trying to recover something from a time machine backup. But that is the opposite of what I think you are saying.
One thing to try is create a new fresh library and then try importing from your old library into the new library (File->Import->Library/Project...). If your library is large, this could take a long time.

Rebuild database, ran out of space on /var

Hi all,
while Syu-ing today I ran out of space on the /var directory. Now some updates are not complete, the applications won't launch, but pacman says everything is up to date. How do I rebuild the package database so I can complete the update?

You might decide backing up /etc and /home and then reinstalling is easiest.
This thread from the mailing lists may help you decide: http://www.mail-archive.com/arch@archli … 09351.html.

Rebuilding database in Aperture

Similar Messages

Maybe you are looking for