Aperture database corruption

I have just started with Aperture and am using version 1.5.2 on a powerbook with 200G Firewire and 500G USB2 HD.
Have been testing the setup for my long term usage and have managed to corrupt the database/library.
Powerbook went into sleep mode as it was running on battery. It was not processing as far as I am aware. Drives were disconnected and powerbook used elsewhere with Aperture left open.
On reconnecting message to say drives not properly shut down. they weren't but i have done this many times before with other programs and just relink. Can't remember if I shut Aperture anyhow now get the 'Library Alert' message to rebuild. All 200 pictures are reference files but versions are in the library (I did not realise this).
This is the interesting bit; Aperture has lost track of the refernce files and all the metadata/keyword associated. The rebuild stops immediately does not process so I have found by quiting and resarting the process for each project I can get back up and then Apreture recovers the variations in the library.
All metadata rankings and keywords lost.
This worries me as I was intending to make the powerbook the core of my workflow, taking it on location and using it with the portable drives. Yes I will be using vaults in the future but shutting down the system on a shoot, we can all make mistakes; just pulling the plug or battery out.
It's the reference files that do not seem to rebuild maybe Apple needs to look at this.
Steve

Go into the Aperture library (Right-click in Finder and seelct "Show Package Contents". That opens a window in your library, try copying projects out from there and importing them into a fresh library. You can also right click on the project files and "Show Package Contents" as well, inside the "import" directory there are subdirectories that hold version information. All the aperture library is basically a bunch of directories with files.
What I am worried about is that your disk was corrupted somehow - you may need to run a program like Disk Warrior to repair damage and recover the files that represent your versions.

Similar Messages

Aperture Library corrupted

I have my 2007-08 Aperture Library on a external drive (2nd gen DROBO) with essentially all of my pictures as referenced files. A couple of days ago, I got a warning that said there was an inconsistency in the library and that I should do a consistency check. I did that, and after about 2 hours of VACUUM everything seemed to come back and was working fine. Yesterday, after exporting 600 images in three file formats to the Drobo, I got another inconsistency warning. I have started aperture with the command-option key down again and it still running VACUUM. Using Activity Monitor, Aperture seems to be doing something with Mach Messages Out, Mach System Calls, and Context Switches changing..going up.
QUESTION: Is Aperture hung and not really do anything or is it still working away at a very nasty database corruption?
If I get my database back, I will move it off the Drobo as I suspect (no proof) that there is something strange going on between their RAID structure and the continual updating of Aperture Library.

OK...this is a remarkable story and I post it in case anyone else does a search on VACUUM, the software that seems to run when one does a consistency check.
So I let the consistency check run overnight (CPU time was 13 hrs in Activity Monitor, but total elapsed time was about 24 hours. It was still running this morning so I decided to do a forced quit. Opened the Library on the Drobo drive and much to my amazement, it opened without difficulty and all the pictures were visible and it seemed fine.
Having been spooked about what was happening to the AP Library (size 60 GB) on the Drobo when I exported files, under the Finder did a drag and drop of the Library over to my internal drive. Opened the Library on my internal drive and it successfully found all of my referenced pictures on the Drobo and seemed to function fine. Checked several of the projects and the few seemed ok.
Have now done a SuperDuper backup of my internal drive to an external FW drive (part of the routine)
Don't know whether the next time I do a large export to the Drobo whether I will have problems again with the Library, but I will provide an update to these notes in the future.

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)

Aperture Database Restore

Hi All,
Would James or one of the gurus mind walking me through restoring an Aperture database that I may have done something stupid to as I cram to organize images for my big opportunity presentation?
I am trying to see if I need to get back to 30 minutes or an hour ago or otherwise lose about 2 days or work with no time to recreate.
Anything available that is a step by step that a dumb monkey (that I am) could follow?
Thanks very much.

Here are the steps that have worked for me (note – to date; I have always run a managed library with all files inside the Aperture library package):
1 – Quit Aperture
2 – Open the location of the current Aperture library package (for this purpose we will use the default location of the‘Home/Pictures’ folder).
3 – Move the current Aperture library to the desktop.
4 – From the ‘Home/Pictures’ folder (which used to hold the Aperture library), enter Time Machine.
5 – Go back to the date and / or time you want to restore the library from and then select the Aperture library in Time Machine.
6 – Click the ‘Restore’ button at bottom of Time Machine interface to copy that version of the library to the ‘Home/Pictures’ folder.
7 – Once the restore is complete, close Time Machine as needed and double-click the restored Aperture library icon to start Aperture and load that library.
Note – I have always held down the ‘Option + Command’ keys while double-clicking the library the first time and running the ‘Repair Database’ option from the First Aid dialog to ‘theoretically’ remove any corruption in the restored library before it loads that first time.
If you have stored your Aperture library in a location other than the default ‘Home/Pictures’ folder, then insert that location in place of ‘Home/Pictures’ folder in steps #2, #4 and #6.
Once you have verified that all is well with the restored library, simply delete the old library from the desktop.
Proviso – since I have not done this with a Referenced library, I do not know what issues you may have with Master files that have been added or removed from finder folders after the restore date.
Good luck.

Convert RAW Files in Your Aperture Database to Adobe DNG Files

The following describes how to convert all the RAW images in your Aperture database from manufacturer formats, such as Sony's ARW and Canon's CR2, to Adobe's DNG while retaining all the Adjustments already applied to your RAW files. In the example below I am assuming that your Aperture Library has ARW and CR2 files. These steps work with the latest version of Aperture, being Version 3.3, and have not been tested with earlier versions (in fact, it probably will not work because the database structure changed in 3.3 - however, this means that the steps below can also be applied to your iPhoto library). The steps are:
1. Within Finder select the Aperture Library and Secondary Click to bring up the Shortcut Menu. From this select "Show Package Contents"; this will open a Window showing all the files/directories contained within your Aperture Library.
2. Drag the "Masters" folder out of the Package and place it on your Desktop. The purpose of this step is so that Applications, such as Adobe DNG Converter, can "see" the "Masters" folder, which they cannot do if it is located within the Aperture Library Package.
3. Run the Adobe DNG Converter, select the above "Masters" folder with the "Select Folder" button, make sure you have selected the option "Save in the Same Location", it is also a good idea to select the option "Skip source image if the destination already exists", check your Preferences then select the "Convert" button.
4. Adobe DNG Converter will now convert all the RAW files to Adobe DNG files and save them in the same location as your existing RAW files. Once complete, take a note of (a) the number of files converted and (b) the types of files converted, such as if the conversion includes ARW, CR2, NEF files etc. In this example I will assume that the converter only found ARW and CR2 files; if your system is different then modify the steps below to make sure it covers all the RAW file types converted in your particular system.
5. Select the "Masters" folder and in the Finder Window Search Field search for all the files that end in .ARW and .CR2 (this filename search list should match the types of files found by the Adobe DNG Converter in step (4)(b) above). The number of files returned by the search must match the number of files recorded by the Adobe DNG Converter in step (4)(a) above. Do NOT put the .DNG files in your search criteria. Select all the files found in the search and move them to the Trash. This will delete all the original manufacturer's RAW files from your Aperture Library leaving behind all the new DNG files.
6. Move the "Masters" folder on your Desktop back to the root directory of the Aperture Library Package Content directory.
7. Select the Finder Window containing the Aperture Library Package Contents.
8. If there is a file called "ApertureData.xml" then open it with a text editor. Search and Replace ".arw" with ".dng", ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (note, do not use the " marks in your search). Make sure you cover all the file types incorporated in your particular system. Save the "ApertureData.xml" file.
9. Traverse to the Database/apdb directory. Select the "BigBlobs.apdb" file and open it with a Hex editor. In this example I will use Hex Fiend by Ridiculous Fish (see http://ridiculousfish.com/hexfiend/). Once the file is open perform a Find and Replace ensuring you are finding and replacing Text and not Hex. In Hex Fiend this means selecting Edit/Find from the menu and then selecting the "Text" button to the top/left of the window. In your Find/Replace field you will need to find ".arw" and replace it with ".dng", make sure you select "Replace All" (note, do not use the " marks in your search). Do exactly the same for ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (and whatever particular RAW files were in your system).
10. Perform exactly the same steps in (9) for the files "History.apdb", "ImageProxies.apdb", "Library.apdb" and "Properties.apdb".
That is it, your Aperture Library now contains DNG files instead of your original manufacturer files while still retaining all the Adjustments originally made in Aperture to those manufacturer files. Of course, you can repeat the same step and replace your DNG files with the original RAW manufacturer files if you wish. This process works because:
1. Aperture does not store the Adjustments in the RAW files, it keeps these in its internal SQLite database.
2. By using a Hex Editor you (a) don't have to play with SQLite to gain access to Aperture's data and (b) because you are replacing text that has exactly the same number of characters you are not invalidating the format of the underlying data file - this is why you use a Hex Editor instead of a simple text editor.
Think of Aperture as being a repository that holds Adjustments which then link to the original RAW source. Therefore, the above process simply replaces your RAW source and therefore all the Aperture Adjustments are still valid; same Adjustments, new source. In case you ask, no, you cannot transfer Adjustments in and out of Aperture because there is no standard to transform adjustments between different photographic applications.

A rather involved method, David.
I am sure it works, and compliments for figuring it out, but I think one critical step is missing in your workflow: Before you begin - backup, backup, backup!
And I think, all the edits in your database that you are doing so diligently, is what you bought Aperture for to do for you, why do it yourself?
I convert selected raw files this way - without manually patching the Aperture Library:
Export the originals of the raw images that I want to convert.
Run dng-converter.
Import the converted originals back, flag them, and move them to the project they came from.
Sort the project by capture date, so that identical images are show side by side.
Then I use the Lift&Stamp tool to transfer all adjustments and tags from the original raw to the dng copy. I check, if some edits are left to do, then delete the original.
It may take a little longer than your method, but this way all edits in the library are done by Aperture, and I am protected from accidental slips when editing the property list files. That requires a very careful work.
Patching the database files inside the library may be justified as a last ressort, when you need to fix and recue a broken Aperture library, and none of the provided tools is working, but not as a routine operation to do batch conversion of image files. It is very error prone. One wrong entry in the library files and your Aperture Library may be unreadable.
Regards
Léonie

Trying to install Photo Shop CS3 Extended on Windows 8 and keep getting database corrupted

Hi, I am trying to install my Adobe Photoshop CS3 Extended on my new Windows 8 OS 64 Bit computer. The CD does not have a scratch on it, it is like new. I get the error database is corrupted. Contact Adobe Support.
I went to the Adobe website and downloaded the updated installer, same error. I tried running the installer in Windows XP compatibility mode, it looks like it installed, but when I run I get database corrupted.
I could really use some help.

Error "...Installer Database is Corrupt..." when you install Adobe Creative Suite 3 products

Can I synchronize my iDevice with Aperture database on external volume?

Hi everyone,
I'm a photography enthusiast and I would always take photos.
Recently, my built-in harddisk was full and I transferred my photos to an USB-connected 2.5" external harddisk. That's not the problem - I can browse and edit the photo freely whenever I plug in my external harddisk.
But when I tried to synchronize my iPad with a database on the external volume, the problem comes. iTunes told that it cannot find the aperture database (in local drive) and I have no idea to match it with my current database.
Who can give me a solution? Thanks!
ALC
(Sorry for my poor English as I'm not an English native speaker)

Hi Ap Lei Chau,
Your English is fine.
Though I do not have a iPad, I do have an iPhone. With my iPhone plugged in, open iTunes, under Devices click my phone, then Photos tab mine reads Aperture. Clicking that drop down I have a option to choose Folder. From there I can walk the path to an Aperture library.
It is my hope it appears the same in an iPad.
Cordially,
RicD

Zenworksd Database Corrupt

A while back I had a problem with the Zenworks database starting on a NW6
SP5 server running Zen 6.5 SP2. I was told to copy the database off to a
PC and then back to the sever. This worked great and I was able to
restart the database and continue on. Since then I have had this happen
twice more on the same server. Completing the above process appears to
fix the problem but it continues to come back. Yesterday I had the same
problem on another server. I might add that these server are at
different schools and have no phyicial connection to each other.
How can I resolve this permanetly?
Thanks,
Coy

All,
I followed the TID Shaun listed and copied the Zenworks folder off and
then pasted it back. I when through each database files and right
clicked and checked do not compress. The error occurred again. This
time I went in through NRM and set the Don't Compress setting for each
files including the NAL.DB file. In the 2 days since I did that I
haven't received a database corruption error.
I am not sure if I am doing this correctly, is there another place to set
do not compress?
Thanks for your help,
Coy
> ensure that the database does not get compressed is one option
> http://www.novell.com/support/search.do?
cmd=displayKC&docType=kc&externalId=10075966&slice Id=&dialogID=8172969&sta
teId=0%200%208180432
>
> --
>
> Shaun Pond
>
>

Logical names lost after database corruption removal

Hi,
I am working on a PXI based project using NI 5663 and NI 5673. The MAX database in system got corrupted recently due to power cut.
I did a database corruption removal and the only issue I face now is that there are no logical names for the devices. I am following the steps from the site below to create the same –
http://www.ni.com/white-paper/4594/en
But after I create a new logical name say for the LO 5652 (associated with 5663), I do not know which driver session to associate with it.
There are driver sessions for niFGen, ni5450 in the list but no session for 5663 or 5673.
Could someone please help me out with creating logical names and associating them to the devices?
Thanks so much,
Sharmi

Hello,
To configure your 5663, you can refer to the RF Vector Signal Analyizer Getting Started Guide pages 37 - 39.
You should open Measurement & Automation Explorer and rename the devices such as VSA_LO, VSA_DC, VSA_DIG for the local oscillator, downconverter and digitzer respectively. Next you will need to associate the downconverter with the local oscillator and digitizer by right clicking the downconverter and selecting properties
To configure the 5673 the steps will be fairly identical, rename the devices if you wish and then associate the upconverter (IQ Vector Modulator) with the arbitrary waveform generator and the local oscillator. You can also refer to the RF Signal Generator Getting Started Guide on pages 23 - 24.
Which programming language are you using the VSA and VSG with? You normally wouldn't need to configure any IVI sessions the the devices. The only configuration normally is just associating the upconverter or downconverting with the LO or digitizer/AWG module.
Anthony F.
Product Marketing Engineer
National Instruments

Simulating Database Corruption

Any one have any reliable methods of simulating database corruption? (I know, use SQL Server.) I want to test various methods of monitoring for both physical and logical corruption.
I have used tried using dd but I can't see a way to just corrupt a specific block without truncating the file so I end up overwriting most of the data file which has its uses, but isn't a good test.
Logical corruption is more tricky. Any one know any good tricks that would let end up with a mismatch between index and table rows etc.
Thanks in advance.

There are so many websites/blogs that share similar informations.
Then you don't need mine and you (i.e., one) needn't keep linking to them.
I don't know why its only you who has problems.
I suspect you don't have much of an idea of what is going on in regards to my material and its accessibility. We'll leave it there, then, with me pausing just long enough to point out that it is not my problem if I choose to remove all access to my material. The problem is rather with those who think linking to it is a particularly useful or sensible thing to do.

CS4 Web Premium Installation "Installer Database Corrupt. Contact Adobe Customer Service."

I need help.
I just purchased a HP Envy 23 running Windows 8. It came with Adobe Premiere and Elements 11 already installed.
I own Lightroom 3, which I installed very quickly and easily.
I own CS4 Web Premium with the serial number at hand. I insert the disk 1 to install and the error message appears: "Installer Database Corrupt. Contact Adobe Customer Service." After serveral attempts, I resort to researching on this forum.
In the forum, found here: http://forums.adobe.com/thread/1238032 I was asked to go the linked website and download and specifically follow the instructions to install CS4 from the internet. I did what I was told as closely as possible.
I received the same error message: "Installer Database Corrupt."
I asked if I needed to uninstall Elements 11 before trying to install CS4 but haven't received a response. Actually, now Adobe won't let me sign on with my password and when I request for a new one it doesn't send me a confirmation email so I have resorted to making a new username.
I called Adobe about the issue with the error and was directed back here to the forum because they do not have phone service support for CS2, CS3, CS4, or CS5 because it is "old" technology. I am loosing lots of work time because I can't seem to get a quick response to my questions here on the forum.
I found another forum saying that I need to rename the file "caps.db." to "xcaps.db" and it will install just fine. I did what it said, looking for any and every folder in both premiere and elements to rename anything that began with "caps" After doing so, I still got the error message.
What I need to know is:
1. How can I install CS4 Web Premium either by disk or internet without getting an error.
2. Must I totally uninstall Elements and Premiere to get CS4 installed? I really don't want to do that since I paid for them with the purchase of my computer.
I'd really like some answers. Thanks.

You're going to need to be more specific about what I am supposed to do because I'm very unfamiliar with computer lingo. I don't know what an OEM is and I am unsure about these backup disks you are referring to. The expertise on this forum is the only lifeline I have to fixing this Adobe issue so I really want to try my best here to get things resolved. I've not heard of deleting caps.db and haven't heard of anything to do with medai.db files before. I'm supposed to delete these instead of renaming caps?

Moved to Server 2012 getting Access Database Corruption

We moved our company file shares to a new Windows 2012 server and are now having issues with Access databases becoming corrupted when accessed by multiple clients at the same time. Does anyone have any ideas on what could be causing this? We
were not having any issues with this on the 2008 or 2003 servers these were on previously.

We migrated from a Windows 2008 file server cluster with four nodes to a Windows 2012 R2 file cluster with two nodes.
After the migration to the new file server cluster our customers running Windows 7 SP1 started reporting Access Database corruption and slow file access.
However, if the SAME Access Database file was hosted on a Windows 2012 R2 file server NOT in a cluster there was no corruption.
I will not bore you with all the tests we ran while trying to determine the cause but here is what we did to fix the issue.
The solution was provided via an open case with Microsoft.
1. Create the following registry entries on all Windows 2012 R2 Servers in the new file server CLUSTER and reboot.
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
Value: DisableLeasing
Type: DWORD
Data: 0x1

Foolproofing database corruption

Hi All,
How do we fool proof database corruption from happening. Does Essbase have any real time hot backups that can be implemented? What can be done here to get some real time backups?
I am more interested in prevention as well as immediate restore features.
I am aware that database corruption could be due to many reasons a few common ones are Memory read error, Disk space Shortage, out of memory and crash, locked file interference, broken sectors on the disk, last but not least software defects and we cannot be ascertained to one entity.
Thanks

Hot backups - not natively (see below).
Backups in general - although a level 0 backup will do for many people, I much prefer to do a full image backup on any relatively small databases (less than 10 Gigs). The reasons are several and vary, here are two of the more prominent ones (there are a few more subtle ones):
1) It's not about the disk/tape space, it's about the recovery time in an emergency. A full image database restores in minutes for whatever reason.
2) Some times, a level 0 export is not enough (think of: restated history issues where the totals are not to be recalculated after the reporting period).
Prevention - Here are a few guidelines, which may each trigger others:
- Separate your OS, Backup, and Essbase drives
- Don't let the tape backup software anywhere near your essbase app directory (goes with above)
- Insist on dedicated I/O (don't let IS/IT sell you on a shared NAS solution)
- Don't give calculate rights to the users blindly
- If your server uses a dual/redundant power supply, hook ONE of them into a good UPS (the other to a different/independent UPS or to grid power)
- (Windows specific): Run essbase as a service instead of using a user account
If you want to set up a fairly decent disk recovery process, consider the use of a VM/VHD for the essbase data, they can be configured to generate real time disk images fairly easy without extreme expense. If you want to go about this the "correct" way, ensure you use a good RAID configuration -- the more spindles in use, the more efficient it will be over all for a specific RAID configuration (i.e. RAID 5 beats RAID 1 for performance on more than 6 drives or so, with "realistic" redundancy/reliability).

E63 Media Database corruption

On opening Media->Gallery, I always get a annoying message that "Database corrupted: Some data might have been lost".
I don't store any songs/video there. Only once used camera.
Will camera corrupts media database while storing images ?
I use latest firmware 200.21.012. I have installed following applications Nokia maps, Google Search and Google maps. When those applications where installed in memory card, I used to get error like "Memory card corrupted". Now, I reinstalled them into phone memory.
Anyone knows solution for this ? I am planning to try soft reset after backing data.

Just don't install programs or applications on the memorycard. Insert the card IN the phone and NOT on a PC or Mac to format. Remove the card by pressing the red button and choose remove card from the dialog option. If you insert the card later you should hear a short bleep.
‡Thank you for hitting the Blue/Green Star button‡
N8-00 RM 596 V:111.030.0609; E71-1(05) RM 346 V: 500.21.009

Moving selected portions of aperture database from old powerpc to bookpro

I have a 2005 ish powerpc G5 that I still use. It is a fine computer, getting a bit bogged down as no further updates for products on the G5 architecture.
I finally broke down and got the i7 macbook pro.
it only has a 500 gig hard drive.
my aperture database is 333.5 GB in size. Seeing as I don't want to use the computer for pics only, I'm wondering if I can move just selected portions of the Aperture database over to the laptop.
For example, there are only certain projects I'm working on. I'd like to (finally) get Aperture 3 (cant get for powermac) and continue with the current projects.
I have the aperture database backups and such.
How can I transfer over only certain raw files and certain projects without transferring over the entire database?
Is this possible?
Thanks

I have a 2005 ish powerpc G5 that I still use. It is a fine computer, getting a bit bogged down as no further updates for products on the G5 architecture.
I finally broke down and got the i7 macbook pro.
it only has a 500 gig hard drive.
my aperture database is 333.5 GB in size. Seeing as I don't want to use the computer for pics only, I'm wondering if I can move just selected portions of the Aperture database over to the laptop.
For example, there are only certain projects I'm working on. I'd like to (finally) get Aperture 3 (cant get for powermac) and continue with the current projects.
I have the aperture database backups and such.
How can I transfer over only certain raw files and certain projects without transferring over the entire database?
Is this possible?
Thanks

Aperture database corruption

Similar Messages

Maybe you are looking for