Delays on updating large vault in A3

After updating A2>A3 I've successfully converted my several libraries, ranging in size from ~9>561 GB. The latter conversion took an overnight swath of time. Then I started on updating the backup vaults. Usually two per library, each located on a differing HD. Each successful, but slow. Waited with the big one until last. It was nearly midnight last night when I began, and I thought the timing would be similar. No way! According to the progress bar, it was ~65% after 10 hours, ~95% at 13 hours and now at almost 18 hours it looks like ~97%. Showing hardly any progress in the last 5 hours. Over time, I've watched the updated vault grow in size (in the HD location) to slightly larger than its non-updated pair. So, at the ~95% barrier and it has only added 1.2 GB in size over the last 5 hours. No spinning beach balls. Only a lack of real progress near the end. Why the terminal delay in vault update progress?

i am seeing the same problem. updating the vault seems to take forever, it has been running for several days now and the Activity Monitor says Aperture is not responding, but it also shows data writes the the vault at about 4 MB/sec and the vault is growing, but very slowly. i am now trying it for the third time, it keeps crashing at different points in the creation of the Vault. I have tried all three repairs, repair permissions, repair database and rebuild database. the original conversion of my Aperture Library from V2 to V3 took close to 30 hours (175,000 images). i have a fast machine and fast disks attached via FW800.
while some of the new features are nice the problems are staggering, did any of this stuff get tested?
glenn

Similar Messages

Mail freezes when updating large RSS feed boxes

This is something I encountered and how I have formulated a work around. I have discovered that Mail will freeze when updating large RSS feed boxes.
A little history. After discovery RSS and how they work, I began building a collection of feeds. They included feeds from many major news providers. Over the years, the number articles form some of these sources went into the thousands.
As my database of articles grew, I encountered more severe and more frequent freezes of the application Mail. I began to take the computer off-line in order to work in these files. But inevitably, a situation would arise that would lead to the Mail application freezing.
Isolation of the issue with Mail and to the RSS boxes within Mail. The freeze would not occur when RSS feeds boxes where collapsed. Also, the freeze only affected the Mail application. Mac OS was not affected and I was able to alway close Mail from with in the Force Quit menu. Also, the Force Quit menu affirmed that Mail was indeed frozen by listing it as also "not responding."
Work around. To resolve this issue, I first choose to remove the number of RSS feed that I had subscribed to but used very infrequently. Second, I choose to delete old feeds from "never" to "every two weeks" from within the Mail preference menu (RSS sub-menu).
I think it took a while for Mail to fully delete messages older than two weeks. In fact, when I began deleting whole feeds, it took some time for those feeds to be removed from my mail box tree. Within the Activity Monitor application, I could see that a lot of disk use was occurring, even though the OS was allowing me to continue to use Mail and other applications.
To assist this process, I took my computer off-line and stepped away from it. Upon my return, the disk use was down to normal, the number of article in many RSS boxes where greatly reduced, and my disk had recovered over a GB of space. Also, Mail seems to be behaving properly, with smooth and quick performance.
If you found this article, I hope the information provided has been helpful! After a quick search in to previous posts, an entirely similar post was not found. However, others are finding the Mail application will freeze, but not necessary for the same reason.

Since I don't want to download any attachments from RSS feeds in Mail.app, is there any way to turn off the attachment download once and for all? I also get the beach ball for minutes when an item has a big attachment, and I fear my HD is cluttered with files I don't use.

Why am I suddenly getting error messages when updating the vault?

Hi, I would greatly appreciate any advice anyone here can offer of how to correct a problem that started recently.
I've updated the vault for Aperture successfully many times before, but now, when I attempt to update the vault I've started receiving error messages. Everything seems to proceed normally at first, a progress bar opens showing "Comparing library to vault", then when that is done, another opens showing "updating vault 'photograph lockbox' from library". But after that I now get an error message which reads:
"Update Vault Error:
13345 errors occurred. The first 5 are:
Error creating a directory in vault ‘Photograph Lockbox‘.
Error creating a directory in vault ‘Photograph Lockbox‘.
Error creating a directory in vault ‘Photograph Lockbox‘.
Error creating a directory in vault ‘Photograph Lockbox‘.
Error creating a directory in vault ‘Photograph Lockbox‘."
I have a Mac Pro running 10.4.11, my version of Aperture is 1.5.6. I haven't updated either of those for financial reasons and because I have no pressing need to. And everything seemed to be working fine until a couple of weeks ago when the updating errors started.
My vault is in a Seagate portable hard drive.
Does anyone have any ideas about how to fix this?
Also, does this mean that none of my new photographs are being backed up in the vault? That would be scary!
Thanks for any advice offered.
Rick

Hi
Exactly the same problem started for me a little while ago.
Firstly, you are correct in assuming that subsequent backups are not taking place. This can easily be confirmed by looking at the colour of the synchronization button. Red circular arrows indicate that there are Digital Masters in your library that have not been backed up in a vault. What colour are yours?
The problem is either a program error or hardware or both.
I suggest that you create another vault, this time on your desktop. Backup to it. If this is successful the problem is not with the Aperture program.
I was advised to format my hard drive as "Mac OS Extended (journaled)" before attempting to backup.

Why does it keep telling me that my photos are referenced when I update my vault?

I recently imported all of my photos into Aperture and immediately set up a Vault to back them up. (I lost 4 years worth of photos so I've become a little paranoid about losing any more photos).
I've also imported some additional photos directly from my camera.
As I go through and edit the pictures in my projects I occasionally update my Vault. A couple of times now it warns me that referenced photos will not be backed up. I set all of the photos to managed and I have no idea what photos it thinks are referenced.
Is it the stuff I am importing? Or the originals that I am editing?
If I select the entire library and convert to managed, it tells me that none of the photos are referenced.
I'm very confused (and suitably nervous about the potential for losing more photos).
Thanks,
Jaime

I do actually....that would make sense....
Thanks!
Jaime

Update of vault goes through entire library and get error message

When I try and update my vault it seems to try and update the entire vault and not just the new pictures. Also I get and error message at the end
/Users/tblack114/Desktop/Picture 1.png

Hasn't anyone had a problem like this. Any help would be greatly appreciated.

Aperture crashes when I attempt to update a vault

recently, when I have attempted to update a vault I get the spinning wheel and Force Quit informs me that Aperture is not responding. I have rebuilt the library, attempted the action on two different Macs (both latest operating systems), used different external vault drives. Same thing: crash. Any advice how to fix this?

What you describe is not actually a crash and while it might seem the same it is different and requires a different method to troubleshoot.
An application reported as not responding does not necessarily mean the application is hung. So as phosgraphis asked how long did you let the vault operation run before you forced quit Aperture?
Also what is your OS and Aperture versions? What type of drive is the vault(s) on? Have you recently update Aperture and/or the OS?

How can delayed delivery update be configured for Inbound delivery ?

Hi All,
How can delayed delivery update be configured for Inbound delivery ?
There is setting for Outbound delivery delayed delivery update but how the same functionality be used for Inbound delivery?
Regards
Jimmi

Hello Jimmi,
Unfortunately I must confirm that the Delayed delivery update is only available for outbound deliveries. Please see below note for further details
664316 Tips for the delayed delivery update for TO
I hope this information helps!
Martin

Delay in updating table

Most of the time, it takes 1 ms to update myTbl using the sql "where myPrimaryKey = 'A123'".
But, on 2 occasions this week, it took 522 ms and 242 ms.
Below is the index fragmentation on myTbl on the 2 days that the delay occurred.
In other days, I see avg_fragmentation_in_percent of PK__myTbl reached 96.969, but I don't see the delay in updating myTbl.
If the avg_fragmentation_in_percent is high (like > 90%), will I see delay in all update, or just occassionally ?
Thank you
index_id name              avg_fragmentation_in_percent    fragment_count   avg_fragment_size_in_pages
1            IX_myTbl       17.960088691796                       121
3.72727272727273
2            PK__myTbl     97.1428571428571                     35
1
index_id name             avg_fragmentation_in_percent      fragment_count   avg_fragment_size_in_pages
1            IX_myTbl       41.0281280310378                     485                     2.12577319587629
2            PK__myTbl     96.7741935483871                     62                      1

Thank you for your reply.
My sql statement is something like
Update myTbl SET col1 = '', col2 = ''...WHERE myPrimaryKey = 'A123'"
Below are the page count.
Are these numbers considered less page counts ?
index_id name         avg_fragmentation_in_percent   fragment_count    avg_fragment_size_in_pages   page_count
1           IX_myTbl    17.960088691796                    121
3.72727272727273                451
2           PK__myTbl 97.1428571428571                  35
1                                          35
index_id name          avg_fragmentation_in_percent   fragment_count   avg_fragment_size_in_pages   page_count
1           IX_myTbl    41.0281280310378                   485                     2.12577319587629
1031
2           PK__myTbl 96.7741935483871                   62
1                                            62
The primary is Non Clustered indexed, but it is a varchar(50) column.
When I perform the Update statement, this is the logical and physical read on the 2 databases that had the delay:
Table 'myTbl'. Scan count 0, logical reads 12, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Table 'myTbl'. Scan count 0, logical reads 5, physical reads 1, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Table 'myTbl'. Scan count 0, logical reads 14, physical reads 2, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.

Delay when applying large, hierarchical type definitions

Hello,
I searched around using various terms, but couldn't readily find posts on what I'm experiencing.
Has anyone else noticed huge delays when applying large, hierarchical type definitions? I've got about a dozen nested type definitions of clusters, each containing anywhere from 10 to 100 controls, and they're used throughout a large application. When I open any member of that hierarchy, make a small change, and hit apply, I see the hourglass (spinning ring of death in Vista/7) for a good two to five minutes.
A short term workaround has been to close all dependent VIs and typedefs, and then make an isolated edit. Then, if I open the whole application again, I see some compiling taking place, but it seems to take a lot less time than when the whole application is open.
I could have sworn that I read a discussion by some others commiserating about this at some point, but now I can't find it.
Has this been addressed, and has anyone heard if there's any development effort to improve this?
Thanks,
Jim

Hi Fred,
Thanks for getting back to me on this.
> You could use more specific typedefs and not a massive one to pass data through VIs.
It's funny, I've actually adopted using larger typdefs in the last year or two for architectural simplicity, and that's when I've noticed this becoming a problem. In fact, for what it's worth, right now I'm using a data reference to store the "data dictionary" (large typedef) but that doesn't really help the issue.
From an architectural sense, it makes things easier for me because I have much fewer wires to pass around most of my data is in one place.
> Or you could pass a queue reference to the subVIs and have the queue be made of of elements that are the large type definition.
Actually, I'm using a data reference right now, which is somewhat analogous to what you're suggesting. (Maybe not? I also use queues and notifiers depending on the situation.) I haven't really seen this technique help the issue; I'm still noticing the large delays, but only when editing the typedefs.
The only way I've really found relief is to separate the large typedef into smaller ones and pass them around separately. This is kind of a pain because it means I have many more references to data structures to keep track of.
> If this is causing major problems, let me know, and I'll pass along your concerns to R&D.
Actually, if I'm to be honest, it really is starting to become a hassle. I hit apply and end up working on something else for a few minutes while the compiler chugs away. I'd be really interested in an improvement in this area. If it makes things easier, I can discuss this via email and upload an application I'm working on as an example. (Multiple large apps I'm working on exhibit this behavior)
Thanks again for your help.
Regards,
Jim

Issue with Update All Vaults button

I am having a relatively strange issue with the latest version of Aperture (3.3.2).
After the upgrade, my "Update All Vaults" button behaves strangely. In the past, if you pressed it, it went through the process of updating the vaults and then it turned from yellow to black. With the new version, if Aperture is not the foreground application, the button stays yellow, even right after updating all vaults.
It's not a major issue, but it's quite frustrating because you are never sure if you had updated your vaults or not.
Any ideas will be greatly appreciated.

I have exactly the sane problem, even if Aperture is the foreground application.
According to the manual this means:
Yellow: All masters in the library have been backed up, but a change has occurred to at least one version (such as an adjustment) that has not been backed up. The vault should be updated to safeguard your work.
I have updated all 3 vaults multiple times and they remain yellow. Is there any way to correct this, or alternatively find out which picture creates this problem?
Thanks
Pim

Update all Vaults? (not all connected????) what is this?

Hello, I tried to update my Library Vault and I only have one. The message
"Some vaults are not connected. Do you wish to replace the contents of all connected vaults with the current contents of your library?
This cannot be undone."
Came up and offered me to "Update connected Vaults" or as I selected "do not update".
What should I do? How do I know if the Vault is connected? I updated it yesterday without a problem. Also I can see the Vault is in its usual place... Any ideas? Thanks!

Sorry VAN D,, still no joy; though I note the increasing number of (various) enquiries about people having problems with this topic;
Vaults not being recognised seems to be getting quite common !!!
- will let you know if I get any suitable responses (none as yet)

Updating Aperture vault will not complete, Aperture quits unexpectedly.

I have a continuing and recurring problem updating Aperture vault after the current Aperture update. The problem also occured after the last update.
Updating the vault does not complete and Aperture quits unexpectedly. This frequently leads to repair to the Aperture library being required. The only solution i have found is to create a new vault. Time consuming and a frustrating waste. I have reloaded Aperture and made updates. This has not solved the problem. I have checked permissions. Nothing wrong there.
My vault and Aperture library are on seperate external drives.

i am experiencing the very same problem updating my vault. Have tried about a half dozen times, creating new vaults (some work some dont) and updating existing vaults (never works). My managed library is 418GB on an external raid array. I have previously created a vault successfully on an external La Cie drive, but then the update failed. After repeated attempts I can not create a new one without Aperture crashing -- which leads to a multi hour repair session. Very very frustraing.
Can someone from Apple comment on whether this is a known bug? What is the work around? Smaller libraries?

Getting Error messages when updating my vaults.

I got about 26 of these error messages when I am trying to update my Vault! I have no clue why I am getting them.
ERROR MESSAGE:
Couldn't create /Volumes/MASTERS/Chuck's Photography Vault 1.apvault/Library/Nature.approject/2010-04-10 @ 09:38:50 PM - 3.apimportgroup/DSC_1509/Info.apmaster

Anybody ever get an error message like this when trying to update your vault?

Delay in update

Greetings,
My problem is that there seem to be a delay the updating of my entries when I call an RFC, I would submit data but would be able to see my updates right away until I wait for a couple of seconds and sometimes it takes longer than 5 seconds. Does anyone have a solution. Please advise.
Much thanks in advance,
Cory

Hi Cory,
Just check in your RFC there must be somewhere the command COMMIT WORK and WAIT FOR n SECONDS.
or the FM BAPI_TRANSACTION_COMMIT..having some value for waiting time..
And this time is actually require for the COMMIT WORK to update all the changes in the DB, so there is no solution for this.
Regards,
Atish

Cannot successfully update any vaults

I just upgraded to Aperture 3 and since then have not been able to successfully update any of my vaults. The library became too large for the external drive that housed my A Vault so I added a new vault on a separate drive that has ample room. When I clicked the update vault icon, aperture said it was calculating disk space and then said it was updating vault. When the update vault scrollbar reached about halfway it stopped moving. I left it run overnight and no change. I was able to then just click on any image and the update bar disappeared as if nothing ever happened. I checked the external drive to see if anything was there and a vault existed, but is much smaller in size than my actual library.
I then went and picked up my offsite drive and brought it back to the office to back up. It did the same thing as above.
I'm confused. I tried to go through the steps to repair my library, but each time I command, option click on the library it just opens Aperture instead of the repair dialogue. Is there another way to repair the library and does anyone have any other suggestions?
Thanks!

I too am experiencing vault issues, although not exactly the same as what you describe. My issues were posted to this discussion thread (see http://discussions.apple.com/thread.jspa?threadID=2631926&tstart=250) on Oct 30, and no one has provided their ideas or solutions in reply. The point I wish to make is that colleagues who regularly follow and post suggestions and answer questions seem to ignore issues with vaults. After I posted my question I searched all posts in this this thread where the word "vault" is used in the subject, and most if not all have zero responses and I can only conclude by the general absence of responses to vault issues that this feature of Aperture is not well known. In the last 90 days I encountered some 20 users with vault issues.
If there are people out there who know how to update, reconnect, migrate, etc vaults - particularly when going from AP2 --> AP3, there are a number of us users who sure would appreciate their insights.
Perhaps there are some Apple personnel on the Aperture Software Team who monitor this thread....if you are out there, then please chime in.

Delays on updating large vault in A3

Similar Messages

Maybe you are looking for