Aperture 10.8.3 library upgrade database inconsistency?

After updating to Aperture 3.4.4, I am unable to update vaults from either of my two Aperture libraries.  A warning reads "An inconsistency in your database has been detected.  The application will now quit, relaunch, and restore your database to a consistent state.  This may take some time."  In fact, that does not happen (waited 12 hours).  I have gone through all three levels of Library first aid with no joy.  Libraries are 288 GB and 128 GB.  Is there a fix?  Should I delete the vaults and set up new ones, or is the problem with my Aperture libraries themselves?

  I had always been reluctant to "Repair Database". fearing it might screw something up and will do that in the future prior to upgrades.
Bill
Bill,
"repair database" and "repair permissions" are routine maintainance operations, perfectly safe to use.
They will check the permissions and the integrity of the internal databases and fix minor glitches. Only it may take some time, if your library is large.
I use these tools routinely to ensure my library is in perfect working condition before any major operations, like updating the library to a new Aperture version or moving it to a new location.
The third fix "rebuild library" will do a major reconstruction of the library, and if the library is already badly damaged it might make matters worse. It is highly recommended to check the backup of the library, if it is up to date, before rebuilding.
I could not do a restore from my SuperDuper Clone because it runs nightly and had already cloned the problematic libraries before I realized there was a problem.
I second Kirby's advice to use clones instead of the vault.
Just one more thing to add: Clones and vaults are only snapshots of one moment in time, and if you update your clone or vault you cannot go back in time. I include my Aperture library into my regular TimeMachine backup, so I can go back to previous versions, if need be, in addition to the clone.
In total I have three backups of every library.
If you do not have at least two backups, go for it. Your system may fail, when you are backing up, and both the backup and the computer may be damaged. This happened to me during a bad thunderstorm, when a lightning stroke close to our house and caused a power failure. I was very happy to have a second backup, on a drive that had not been turned on at that time.

Similar Messages

  • Trying to open old iPhoto library on osx 10.9.5 with iPhoto 9.5.1.  iPhoto says I must upgrade but upgrade eventually hangs.  Tried to rebuild/repair database but it always says you have to upgrade database first and eventually hangs

    Trying to open old iPhoto library on osx 10.9.5 with iPhoto 9.5.1.  iPhoto says I must upgrade but upgrade eventually hangs.  Tried to rebuild/repair database but it always says you have to upgrade database first and eventually hangs

    What version was the old library made with?
    What is the exact message? when it hangs does it crash or do you have to force quit?
    LN

  • After upgrading to Aperture 3 I had to 'upgrade' all files. When this was done, there was an Aperture 3 library and the original Aperture 2 library. Are the two libraries identical and can I safely trash the Aperture 2 library?

    After upgrading to Aperture 3 I had to 'upgrade' all files. When this was done, there was an Aperture 3 library and the original Aperture 2 library. Are the two libraries identical and can I safely trash the Aperture 2 library?

    If the upgrade completed successfully and you are running Aperture 3 on the converted library and you're sure all the images that were in the old library are in the new library then you could delete the Aperture 2 library.
    However I'm the paranoid type and when it comes to deleting images I'm always hesitant. If you can fine a place to archive the old library that  would be your a better option.
    At a minimum I would keep the old library around for a month or so after switching to Aperture 3 just to make sure in case something pops up.
    regards

  • Aperture Library.aplibrary/Database/History/Changes/

    Hello everyone, i've recently had some trouble with corrupted Aperture library. This has all been fixed now however in the process of trying to fix things up I stumbled accross Aperture Library.aplibrary/Database/History/Changes/ folder - I've been trying to clear some space from my HDD and notice that this folder is enourmous. Almost as large as the preview, master or thumbnail folders.
    It measures over 40gb which accounts for over 20 per cent of my library size. What excectly does this folder do (Aperture Library.aplibrary/Database/History/Changes). There a hundreds of plist files measuring several 100mb each.
    I know I can safely delete things like preview and thumbnail and rebuilt the database however have been hestitant to touch this folder as I don't know what it does. Can someone shed some light on the purpose of this folder. Google searches have just come up with threads about disk warrior reporting the folder as having errors but doesn't say what the folder does. Can I delete to save space? I'm concerned this folder contains the changes made to masters meaning i can't revered changes in the versions.

    Just as a test I took one of my libraries that I do this sort of thing to and removed the Changes folder and ran Aperture on the library. Aperture worked fine. The library behaved just as expected.
    I've never paid much attention to this folder before and it's not clear just what 'changes' they are referring to but I wouldn;t get to worked up about it. Just make sure you have good working backups (as you should have anyway) and remember the next time you run DiskWarrior you'll probably see these errors.
    regards

  • Upgrade Aperture 3.2.4 Library to 3.5.1

    Hi,
    I just upgraded from a MBP 1.83 GHz to a new iMac.
    I am trying to open or import my MBP Aperture Library (3.2.4) in my iMac Library (3.5.1), but Aperture tells me:
    The library could not be imported because it is from an out of date version of Aperture 3. Please upgrade the library to the latest version of Aperture 3 and try again.
    When I go to File > Switch to Library > Other / New and select the MBP Library, Aperture tells me:
    The selected library is from an older version of Aperture and requires a relaunch to switch.
    Choose “Relaunch” to relaunch Aperture with the new library.
    But then nothing happens, and Aperture reopens the current library.
    Problem is that I cannot upgrade from my MBP as I cannot upgrade to the latest version of macos.
    Therefore, I wonder how to proceed.
    Any advice will be welcome!
    Thanks
    Hugo

    Hello, I thought I'd chime in on this too, because I have had a lot of trouble getting this to work as well.
    I followed lots of post around the internet and found nothing worked.
    I did the usual upgrade thing that most people have done, and upgraded from Snow Leopard to Mavericks, only I had this exact problem, and I got stuck in the endless loop too. I tried clearing out the user preferences and restarting the computer, only to have it still not work.
    Fortunately for me, when I installed Mavericks, I did it on to a fresh SSD drive, and left my Snow Leopard "Macintosh HD" still bootable.
    I booted in to SL, and I then ran Apeture, 3.2.4. I did a repair of the DB. (hold down OPTION and COMMAND when starting to get the repair message) at the start.
    When it was complete, I restarted the computer back in to Mavericks and then tried loading the Library the same way as before. Eg. File, Switch to Library, Import/Open etc. Still nothing.
    I then just did as the above posts suggested. I found the library, and double clicked it, and it said, Do you wish to upgrade to 3.5.1. YES. It seems to be working so far.
    Thanks. Just thought I'd share, in case any more information for others was key as well.

  • Database Inconsistency Nightmare

    As an avid user and supporter of Aperture since it's release, I now have an new issue. I am a pro photojournalist using Aperture every day for all my magazine assignment work and I feel like I know the program very well after 2+ years of heavy daily use.
    I have never had any serious problems with the program at all, until one week ago.
    The problems started when I launched aperture and got a database inconsistency dialog box. I was not too worried as I have had this once or twice in the past and I just relaunched the app with apple and option keys down and rebuilt the database. Everything seemed ok but then I noticed that 2,400 of my 12,000 referenced images were tagged as missing. I thought this was strange, and I used "Manage Referenced Files" to see what was going on and reconnect the missing files. I also noticed that 2 subjects had a second version not in a stack that contained the thumbnail for each image without metadata, while the normal version and stack with metadata had no thumbnail! On my FireWire drive 1 which holds a first copy of all referenced files in my library, each subject has a corresponding folder and I started to reconnect the offline and missing files. For most of the subjects everything went fine, but then there were 4 subjects where I encountered very unexpected problems. Firstly the names of the Master images for some subjects had been changed more that one year earlier, but the reconnect dialog box showed the original filename from the camera as the master filename. It did not want to "Reconnect All" so the only way is one by one!
    Then I notice that the smart folders set to show "Offline" and "Missing" masters are inaccurate for some reason.
    I even have a few "Managed" masters that will not export because the dialog box comes up to tell me that the image is "Offline" or "Unavailable". What? Ok so at this point I decide that since I have everything backed up on two separate Firewire drives and a server in California, that it may just be cleaner to reinstall Aperture and revert to a recent Vault. I did this and guess what, same problems plus a few more headaches reconnecting masters!
    The biggest problem at this point is that for two subjects, the captions and adjustments are in a version that has no thumbnail, shows the "Missing" tag in the Metadata panel listing the original filename from the camera as the Master Filename, while there is a new mysterious version 2 which has a thumbnail, no caption, the offline tag and and shows the correct Master Filename. If I reconnect the masters for these images it still shows as missing for the normal version which has the captions, keywords and adjustments.
    At this point I have decided that for two of the subjects One is Versailles 600 images and the other Cyprus 700 images, that I will probably end up having to just reimport these two subjects and manually move the caption for each image.
    This is all starting to make me call into question the stability of this type of system for archiving large amounts of images. True that with all the backups and the normal robustness of Aperture you should not loose images. But if the Masters get unlinked in a corrupt way from the database you CAN loose a large part of your post processing work. And the worst seams to be that this can happen even if you DO know what you are doing.
    This does not at all mean I am going to stop using Aperture, but it does make me feel a little more weary from an archival standpoint about keeping all metadata and adjustments separate from master images.

    Thanks for all your replies. And yes the Project container is a fantastic way to back things up. It is especially useful for moving a project from one Library to another without risk of overwriting files.
    Naturally if I could get my corrupt projects in order I would export the projects, including the masters and then reimport them. But Aperture is not going to let me do that with these corrupt Projects, as the masters are not be properly linked. I have tried everything I could think of.
    There are still some really weird things going on with the database in my library. One really strange thing is that some referenced images that DO have the master linked and show the normal reference tag, but will not Consolidate as the dialog comes up "The selection does not contain any referenced files".
    But then for the same image you can choose "Show in finder" and it goes straight to the master on it's external drive! How strange is that. For that matter it will also not "Relocate Master" for the image because it says that the master is "Offline or cannot be found". OK then here comes the weirdest part: It will export the image without a hitch! Managed referenced files shows these images as connected and black.
    Then the other really bad thing is that some of the managed images will not export or relocate as the dialog comes up "Offline or cannot be found". I have rebuilt the library and everything else to no avail.
    The thing that bothers me about this is that if this can happen to me, who spends untold hours on Aperture and on the computer in general and I believe I do know quite a lot about the program, what is going to happen to the many photographers who do not fully grasp the abstract file management of Aperture?
    Maybe it is more stable to run your Library as Managed, but for working photographers who are usually laptop users it is almost essential to keep the masters on an external Ruggged drive. If you put the Library on the external drive the performance which is already sometimes sluggish when you need to work very quickly (even with the most powerful MacBook Pro) becomes too beach ball when on an external drive.
    In any event I think that if I can ever get my Library back in order, in addition to the many backups of masters and vaults, I am going to export each project including masters and back that up too on a regular basis. Seems like a lot of work backing up to maintain the integrity of a database!
    Cheers

  • Upgrading database nev completes

    I have just upgraded iphoto to the latest version via the App Store.
    As part of the installatin process it says it needd to upgrde the iphoto database. After a coouple of quick checking screens it begins the updating database process.  the progress bar completes 95% of it journey and but then frezes at the last 2 millmetres. The first tie I waited 8 hours for the process to complete but it never did.  I had to force quit iphoto.
    I then trashed the iphoto application and downloaded a fresh copy.  In case the iphoto library has been corrupted by the failed installation process, I went into the timemachine and restored the iphoto library to a a copy before the instalatin process had been underaken.  the same thing happened again a freeze 2 mm boe thened.  What now?

    After "Force Quitting" try to repair the aperture Libray before trying to upgrade:
    Launch Aperture with the cmd-options-key combination (⌘⌥) firmly held down, then select "Repair Library" from the "Aperture 3 Library First Aid" panel; if "Repair" does not suffice, try "Rebuild Database".
    Good Luck
    Léonie

  • TS2518 Library upgrade stuck at 99%

    The 3.2.4 Aperture library upgrade is getting stuck at 99% and maxing one of my CPUs seemingly indefinitely. I've force quit and restarted the process, but it's stuck again at 99%. I have a decent sized library, but not insanely huge or anything.
    Anybody else experiencing this? Does it just take a really long time?

    So I force quit Aperture, and did a "Repair Database" http://documentation.apple.com/en/aperture/usermanual/index.html#chapter=27%26se ction=10%26tasks=true
    Less than five minutes later Aperture was open upgraded to 3.3.
    So there you go.
    P.S. Aperture is now maxing all 4 cores of my CPU, I assume, processing all the previews.

  • IPhoto library upgrade failed, one third of the photos lost, but the library works as normal. No corruption.

    Hello! I recently replaced my tragically crashed Macbook Pro 2008 with a newer model and transferred my volumous iphoto library of 20 000+ photos to my new machine. To be able to use my iphoto '08 library with Aperture I had to upgrade the library in the iphoto '11 version. I left the computer on during the day, and when I got back it seemed to work fine. I browsed my library in Aperture and could see all the thumbnails, but looking closer I noticed a small yellow warning triangle with an arrow in the corner of some pictures. Turns out all pictures from before ~2010 are lost! When I wiev the photos I see nothing but the infinite black of the data void.
    Here's how I've tried to fix the problem:
    1. Opening the iPhoto Library package in Finder. All the folders for the earlier dates are there, but they are empty. I notice no incorrect or impossible dating, which seemed to be a common problem among users who's libraries where corrupted during the upgrade process.
    2. Rebuilding the iphoto library in iphoto. No effect.
    3. Recovering the iphoto library from my Time Machine Backup. SInce my old hard drive was just 200 GB, I stored all pictures older than one year on my external hard drive (note that about half of those pictures were successfully imported/upgraded). Both the internal and the external hard drive where backed up using Time Machine on a NAS from Seagate (Black Armor 110, 3TB). I was able to access backed up files on my external drive through Time Machine on my old computer, but since it is now rendered unbootable I tried using Migration Assistant to let my new computer inherit the old backup. However, I could not find the backup of the external drive in Migration Assistant, just my old internal drive. When I tried to access the backup volume on my NAS through Finder it didn't show up (I could find it that way on my old computer).
    4. Googling "iPhoto library upgrade failed", or "Inheriting Time Machine backup of external drive", and similarily desperately specific phrases - Nothing useful. Other people seems to have had problems with corrupt Libraries, but I'm not sure that's the case here.
    My pictures must exist somewhere on my computer and in a backup on my NAS. I just can't find them! Do anyone have a clue to what may have gone wrong? I'm afraid the computer might have gone to sleep during the upgrade, because I didn't thinkabout adjusting the power saving settings before starting it. But since pictures 1-8000-something are missing, it doesn't seem to have worked properly during the whole beginning of the upgrade, not just during the middle. As I knew I had a backup of the library I didn't worry about upgrading the single functional copy. From now on I will think thrice before doing anything as serious as this.
    I am eternally grateful for any answers that might help me recovering my photos!
    //Teodor Nilson

      b) I split up my photo collection into two iphoto libraries. One for the new photos stored on my internal HD            and one for photos older than one year stored on my external HD
    And exactly How did you Split up your iPhoto library?
    c) I used Migration Assistant in an attempt to access the Time Machine backup of my old MBP from my new      MBP (by inheriting the backup). When I made my backups, I made sure Time Machine included the external      HD. But Migration Assistant could only find the backup of my Internal HD with the library of new photos!
    And again
    You should not use Migration assistant on an iPhoto library - it generally does not work
    and
         d)   When signing in and mounting the NAS in Finder, I used to be able to see a Time Machine backup      folder/icon. Now I was unable to locate it.
    I believe you are using your NAS for your Time Machine backup. If your Time Machine backup and/or your iPhoto library is on a NAS you will have problems - both need to be on Mac formatted volumes - the least troublsome is a volume formatted Mac OS extended (journaled)
    http://support.apple.com/kb/HT1427?viewlocale=en_US&locale=en_US
    Manually preparing a new disk for Time Machine
    If you want to erase a disk before using it with Time Machine, follow these steps:
    Open Disk Utility (located in the Utilities folder).
    Connect the disk if it isn't already attached.
    In the left side of the Disk Utility window, select the disk you want to use with Time Machine.
    Optional: If you want to partition the disk, click the Partition tab and select a layout. Make sure "Mac OS Extended (Journaled)" is selected in the Format menu for the partition that will be used for backups. Click Apply.
    Click the Erase tab.
    Optional: If you want to securely erase the disk, click Security Options to configure, then click OK.
    Click Erase.
    After erasing, open Time Machine preferences in System Preferences and configure as described in the section above.
    Are the iPhoto libraries kept on an external drive formated Mac OS extended (journaled)? Or are they on the NAS? - If you are using the NAS for iPhoto and/or Time Machine that is the source of your problems
    LN

  • HT5037 The iPhoto Library Upgrader tool doesn't work. I've downloaded it, and follow the directions, but iPhoto still won't open.

    The iPhoto Library Upgrader tool doesn't work. I've downloaded it, and follow the directions, but iPhoto still won't open.

    Your Library is damaged.
    Option 1
    Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Repair Database. If that doesn't help, then try again, this time using Rebuild Database.
    If that fails:
    Option 2
    Download iPhoto Library Manager and use its rebuild function. (In early versions of Library Manager it's the File -> Rebuild command. In later versions it's under the Library menu.)
    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.  
    As for goign back: do you have an undamaged library?
    Regards
    TD

  • Aperture 2.1 to 3 upgrade

    Can I use the Aperture 3 trial to upgrade my 2.1 copy until the new version arrives in the mail? I received the following a message stating:
    "A licensed copy of Aperture has already been installed in the Applications folder. To install the Aperture 3 Trial, rename your existing copy of Aperture, then run this installer again."

    Well, first, you have to rename your old Aperture in order to do this. Just rename it Aperture2 in the Finder.
    Then you can install the Aperture 3 Trial.
    Note, Aperture 3 Trial will NOT upgrade your Aperture 2 library. Or, at least, it won't do it automatically. Some have said if you try after launching the application it will do it, but in general it's not supposed to work, to keep you from boxing yourself into Aperture 3 if you decide not to purchase.
    You can export all your projects from Aperture 2 and then import them into Aperture 3; this will work and is supported.

  • Next Number Maintenance - Database inconsistency

    Hi ,
    I did basic configurations in SAP ME. I also did Next number maintenance as a part of configuration. I have created few shop orders and completed successfully  with NC .
    Recently we have upgraded to SAP ME 5.2.4.3 from 5.2.4.1
    Now I have added some more materials to the same plant  and trying to create inventory for those materials in Inventory Receipt.
    I am getting the following message.
    Database inconsistency: "Invalid Next Number return" (Message 1006)
    I am able to create inventory for  the old materials even now.But not for the newly added materials.
    Did I miss something after patch upgrade? or is it  configuration problem?
    Regards,
    Guru.

    Hi,
    it looks weird. Could you look at the default trace? What is the stack trace behind the exception you get?
    What if you try just to copy old material under a new name? Does it work?
    Regards,
    Anton

  • Library Upgrade in Progress...

    I upgraded from Beta 4 to LR 1 and was not really intimidated when LR told me that this might take "a few minutes".
    Twelve hours later, with LR using up 2/3 of my RAM and up to 98 of my CPU, I stopped this via the task manager.
    I then rebooted my PC and tried to open Lightroom again. Now "Library upgrade is in progress" again...
    This was about 8 hours ago.
    Admittedly, the photographs indexed (many are high resolution scans of slides) take about a terabyte disk storage, but the database itself should be much smaller.
    Anything, I can do to speed up the process?
    Or will the new lightroom just not run on my system?
    Laurenz

    OK, I just returned to my PC after a good night's sleep.
    Library Upgrade is still "in Progress", about 1 % of the progress bar is blue.
    To me this looks as though LR was really having a problem with the library Beta 4 created.
    If there is no other way then re-importing everything, I'd even do that, but there's no way I could do anything like this from within the application (as it won't open).
    Is there anyway, I could do this from outside?
    One thing: I did not install Lightroom at the default location - I have a special drive for all programmes and used the option to install it there.
    Worked fine with beta 4 - might this be part of the problem, or is it just the number of pictures referenced?

  • What can I do? Every "iPhoto Library Upgrader" I've downloaded fails to prepare the my iPhoto Library, so I can't open iPhoto any more.

    What can I do? Every time I download & run "iPhoto Library Upgrader" it fails to "prepare" the my iPhoto Library, so I can't open iPhoto any more. 
    (My MacOS & iPhoto are the latest versions.) 
    Ever since my last upgrades, every time I try to open iPhoto, a Alert box pops up saying, "To open your library with this version of iPhoto, it first needs to be prepared. To prepare the library, use the iPhoto Library Upgrader", and it gives 2 options: a "Learn More" button or "Quit" (iPhoto) button. The "Learn More" button links to Apple's "iPhoto '11: About the Library Upgrader" page (http://support.apple.com/kb/HT5037), but whenever I then download and run that page's linked app, the same thing happens all over again. 
    It does no good to rebuild the iPhoto Library (holding down the command & option keys while reopening iPhoto): the same thing happens. 
    It does no good to use iPhoto Library Manager (http://www.fatcatsoftware.com/iplm/) to rebuild the iPhoto Library, as was suggested elsewhere: the same thing happens.

    Option 1
    Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Repair Database. If that doesn't help, then try again, this time using Rebuild Database.
    If that fails:
    Option 2
    Download iPhoto Library Manager and use its rebuild function. (In early versions of Library Manager it's the File -> Rebuild command. In later versions it's under the Library menu.)
    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.  
    Regards
    TD

  • (DBUA) New upgraded database from 10.2.0.4 to 11.2.0.3 adconfig fails

    OS: OEL5x86
    DB :11.2.0.3
    Good Day,
    I am trying to create the environment for my new upgraded database but I am getting an error..
    /ora/oracle/proddb/11.2.0/appsutil/install/PROD_mobay/adcrobj.sh and /ora/oracle/proddb/11.2.0/appsutil/install/PROD_mobay/txkcreateACL.sh
    subsequently failed stating the same error ORA-12705: Cannot access NLS data files or invalid environment specified.
    ---extract from autoconfig log-------
    AutoConfig Profile Phase
    Running Profile Process 1 of 1 for AppsUtil
    Executing script in InstantiateFile:
    /ora/oracle/proddb/11.2.0/appsutil/install/PROD_mobay/afdbprf.sh
    script returned:
    afdbprf.sh started at Thu Jan 23 12:14:45 EST 2014
    The environment settings are as follows ...
           ORACLE_HOME : /ora/oracle/proddb/11.2.0
            ORACLE_SID : PROD
                  PATH : /ora/oracle/proddb/11.2.0/perl/bin:/ora/oracle/proddb/11.2.0/bin:/ora/oracle/proddb/11.2.0/perl/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin:.
          Library Path : /ora/oracle/proddb/11.2.0/lib:/usr/X11R6/lib:/usr/openwin/lib:/ora/oracle/proddb/11.2.0/ctx/lib
    Executable : /ora/oracle/proddb/11.2.0/bin/sqlplus
    SQL*Plus: Release 11.2.0.3.0 Production on Thu Jan 23 12:14:45 2014
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    Enter value for 1: Enter value for 2: Enter value for 3: ERROR:
    ORA-12705: Cannot access NLS data files or invalid environment specified
    ERRORCODE = 1 ERRORCODE_END
    .end std out.
    .end err out.
    Any Suggestions?
    Regards,
    Shridath.

    Please see:
    AutoConfig is Failing with status 4 for a New Database with NLS Environment Error ORA-12705 (Doc ID 1612017.1)
    DatabaseTier Autoconfig Errors ORA-12705: Cannot Access NLS Data Files Or Invalid Environment Specified (Doc ID 548916.1)
    AutoConfig is Failing with status 4 for a New Database with NLS Environment Error ORA-12705 (Doc ID 1612017.1)
    Thanks,
    Hussein

Maybe you are looking for