Running catalog and catproc

Hi all,
If I run catalog.sql and catproc.sql in a production database (when application is not accessing db), they will recreate data dictionary, views and recompile packages. But, wiil my data be affected by this?
Regards,
Saikat

If I run catalog.sql and catproc.sql in a production database (when application is not accessing db), they will recreate data dictionary, views and recompile packages. But, wiil my data be affected by this?Refer the foll link:
https://forums.oracle.com/forums/thread.jspa?threadID=2410592
Refer Metalink Doc Id:
*Why do I have to run the CATPROC.SQL PUPBLD.SQL Oracle Scripts ? [ID 1033107.1]*
*Best Practices for running catalog, catproc and utlrp script [ID 863312.1]*
Edited by: Vedant.. on Dec 11, 2012 4:10 PM

Similar Messages

  • Need of catalog and catproc

    Hi is it compulsory that we will run catalog.sql or catproc.sql scripts after installing database?or is there any procedure that we can run automatically?
    please explain me for 10g version also (if there is any difference in 10g)
    thanks in advance.

    catalog.sql created all the DBA_, ALL_ and USER_ views that make up the data dictionary. Without them, you'd be stuffed. You wouldn't be able to manage a thing. So, whilst the database is mostly functional without running the script, it's completely unmanageable, which amounts to being totally non-functional, really.
    Catproc.sql creates all the packages and procedures that the database needs to be fully functional. Schedule a job with DBMS_JOB or DBMS_SCHEDULER? Well, how do you think DBMS_JOB or DBMS_SCHEDULER got there in the first place? Catproc.sql is how, along with a bazillion other DBMS_this, that or the other. So no, without catproc, you wouldn't have a useful or usable database.
    This hasn't changed one bit in 10g. It's been like this for versions going back to at least version 7, and quite possibly long before that.
    You don't need to run them yourself, however, if you use the Database Configuration Assistant which has been Oracle's preferred way of creating databases since about version 8.0. The DBCA runs both scripts (and a few others) for you. The progress display reads something like 'Creating Data Dictionary Views' when it's doing it. You can check this for yourself by asking DBCA not to actually create a database but merely to create the scripts which it would normally use to create a database. Those scripts are merely text files, so you can open them up and have a look... and you'll see catalog and catproc both make an appearance there.

  • Catalog and Catproc

    Hello Everybody
    I am new to Oracle. I have few queries related to Catalog and Catproc.
    1)What happens if we run CATALOG and CATAPROC as non SYS user?
    2) Can we run CATPROC first then CATALOG? If not then why?
    3) What happens if I rerun CATALOG.SQL & CATPROC.SQL?
    With Regards

    947797 wrote:
    Hello Everybody
    I am new to Oracle. I have few queries related to Catalog and Catproc.
    1)What happens if we run CATALOG and CATAPROC as non SYS user? errors
    >
    2) Can we run CATPROC first then CATALOG? If not then why?
    I give up.
    Can you?
    3) What happens if I rerun CATALOG.SQL & CATPROC.SQL?
    Nothing special.

  • Several errors after running catalog.sql

    I did a fresh installation of oracle apps EBS 11.5.10.2 on Linux OEL and was trying to do an import/export and it was not working as expected. So after i looked at Oracle's documentation it said catalog.sql has to be run before using the import/export. So i ran catalog.sql first but i did not run it with SYSDBA but ran it as SYSTEM and i saw several errors like access denied etcv. after i ran the catalog.sql i was not able to login via apps or any other user except SYSTEM and was giving me erros like ORA-04065:not executed,altered or dropped stored procedure "SYS.DBMS_SESSION"
    After this to fix the issue i ran @?/rdbms/admin/catpatch.sql and @?/rdbms/admin/utlrp as SYSDBA but both executed a lot of grants etc but are haging at some point and not finishing.
    The current state of the database is that im not able to login via any user except SYSTEM and i think i corrupted the db dictionary as everywhere i see they say running catalog.sql on an existing database is a bad idea. Can anyone help?

    Hi Dheeraj,
    My db version is 9.2.0.5.0 and OS is OEL 5.7.
    The doc where it was mentioned to run catalog.sql before using import/export is below:
    http://docs.oracle.com/cd/B10501_01/server.920/a96652/ch01.htm
    Please do not follow the steps in this link and instead follow the steps in (9i Export/Import Process for Oracle Applications Release 11i [ID 230627.1]).
    Currently when im trying to login using apps or any other user below are errors i get.
    ERROR:
    ORA-00604: error occurred at recursive SQL level1
    ORA-04068: existing state of packages has been discarded
    ORA-04065: not executed, altered or dropped stored procedure "SYS.DBMS_SESSION"
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512:at "SYS.OWA_VPD_CTX", line 5
    ORA-06512:at "SYS.PORTAL_LOGIN", line 3
    ORA-06512:at line 2
    Can you pls help me to fix this.The status of the package is invalid and you need to validate it. Connect as sysdba and issue:
    SQL> select owner, object_type, status
    from dba_objects
    where object_name = 'DBMS_SESSION';
    SQL> alter package DBMS_SESSION compile body;
    SQL> show error
    SQL> alter package DBMS_SESSION compile;
    SQL> show errorPlease also see:
    Data Dictionary Objects Invalid after Running catalog.sql, catproc.sql, utlrp.sql or catpatch.sql [ID 752783.1]
    Debug and Validate Invalid Objects [ID 300056.1]
    How to Diagnose Invalid or Missing Data Dictionary (SYS) Objects [ID 554520.1]
    Thanks,
    Hussein

  • Run catalog.sql and catproc.sql?

    Hi,
    Does the install procedure for Oracle 9i Release 2 run catalog.sql and catproc.sql? Or should they be run manually after install? Thanks for the help.
    rmc.

    If I run catalog.sql and catproc.sql in a production database (when application is not accessing db), they will recreate data dictionary, views and recompile packages. But, wiil my data be affected by this?Refer the foll link:
    https://forums.oracle.com/forums/thread.jspa?threadID=2410592
    Refer Metalink Doc Id:
    *Why do I have to run the CATPROC.SQL PUPBLD.SQL Oracle Scripts ? [ID 1033107.1]*
    *Best Practices for running catalog, catproc and utlrp script [ID 863312.1]*
    Edited by: Vedant.. on Dec 11, 2012 4:10 PM

  • Creating database without running the catalog.sql and  catproc.sql script

    Hi
    I created tow databse without running catalog.sql and catproc.sql. Any one knows what is the drawback of not running them?
    BR.

    I created tow databse without running catalog.sql and catproc.sql. Any one knows what is the drawback of not running them?Functionality & capabilities will be severely limited.

  • Invalid objects after running catalog.sql and catproc.sql

    I have a db 10.1.0.3.0. standard edition with the 10.1.0.4.0 patch installed.
    After executing catalog.sql and catproc.sql the database contains lots of invalid objects in the public, olapsys and xdb schemas.
    I have executed utlrp.sql, the script completes successfully, but lots of invalid objects remain.
    Does anyone know how to fix this?
    Thanks in advance.
    Below is the output of
    select owner, object_name, object_type from dba_objects where status like 'INVALID';
    OWNER OBJECT_NAME OBJECT_TYPE
    XDB DBMS_XDBUTIL_INT PACKAGE
    XDB SETMODFLG PROCEDURE
    XDB DBMS_XDBZ0 PACKAGE BODY
    XDB DBMS_XDBUTIL_INT PACKAGE BODY
    PUBLIC DBMS_XDBUTIL_INT SYNONYM
    XDB XDB$PATCHUPSCHEMA PROCEDURE
    OLAPSYS ALL$OLAP2_AW_CATALOGS VIEW
    PUBLIC ALL_OLAP2_AW_CATALOGS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CATALOG_MEASURES VIEW
    PUBLIC ALL_OLAP2_AW_CATALOG_MEASURES SYNONYM
    OLAPSYS ALL$OLAP2_AW_PHYS_OBJ VIEW
    PUBLIC ALL_OLAP2_AW_PHYS_OBJ SYNONYM
    OLAPSYS ALL$OLAP2_AW_PHYS_OBJ_PROP VIEW
    PUBLIC ALL_OLAP2_AW_PHYS_OBJ_PROP SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIMENSIONS VIEW
    PUBLIC ALL_OLAP2_AW_DIMENSIONS SYNONYM
    OLAPSYS ALL$OLAP2_AW_ATTRIBUTES VIEW
    PUBLIC ALL_OLAP2_AW_ATTRIBUTES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBES VIEW
    PUBLIC ALL_OLAP2_AW_CUBES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_DIM_USES VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_DIM_USES SYNONYM
    OLAPSYS ALL$AW_DIM_ENABLED_VIEWS VIEW
    PUBLIC ALL_AW_DIM_ENABLED_VIEWS SYNONYM
    OLAPSYS ALL$AW_CUBE_ENABLED_VIEWS VIEW
    PUBLIC ALL_AW_CUBE_ENABLED_VIEWS SYNONYM
    OLAPSYS ALL$AW_CUBE_ENABLED_HIERCOMBO VIEW
    PUBLIC ALL_AW_CUBE_ENABLED_HIERCOMBO SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIM_LEVELS VIEW
    PUBLIC ALL_OLAP2_AW_DIM_LEVELS SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIM_HIER_LVL_ORD VIEW
    PUBLIC ALL_OLAP2_AW_DIM_HIER_LVL_ORD SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_MEASURES VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_MEASURES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_SPECS VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_SPECS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_MEAS VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_MEAS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_LVL VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_LVL SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_OP VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_OP SYNONYM
    OLAPSYS MRAC_OLAP2_AW_DIMENSIONS_V VIEW
    OLAPSYS MRAC_OLAP2_AW_CUBES_V VIEW
    OLAPSYS MRAC_OLAP2_AW_CUBE_MEASURES_V VIEW
    PUBLIC MRV_OLAP2_AW_DIMENSIONS SYNONYM
    PUBLIC MRV_OLAP2_AW_CUBES SYNONYM
    PUBLIC MRV_OLAP2_AW_CUBE_MEASURES SYNONYM
    OLAPSYS CWM2_OLAP_METADATA_REFRESH PACKAGE BODY
    OLAPSYS OLAP_SYS_AW_ACCESS_DIM_VIEW VIEW
    OLAPSYS OLAP_SYS_AW_ACCESS_CUBE_VIEW VIEW
    OLAPSYS OLAP_SYS_AW_ENABLE_ACCESS_VIEW VIEW
    PUBLIC OLAP_SYS_AW_ACCESS_CUBE_VIEW SYNONYM
    PUBLIC OLAP_SYS_AW_ACCESS_DIM_VIEW SYNONYM
    PUBLIC OLAP_SYS_AW_ENABLE_ACCESS_VIEW SYNONYM
    OLAPSYS CWM2_OLAP_OLAPAPI_ENABLE PACKAGE BODY
    OLAPSYS DBMS_AWM PACKAGE BODY
    OLAPSYS CWM2_OLAP_CUBE PACKAGE BODY

    This note explains 80% of the problem: 42 invalid objects are normal, I have 52 invalid objects.
    I have re-executed the catpatch.sql script, I couldn't find any errors in the output. At the end Oracle Intermedia and Oracle Expression Filter remain invalid.
    last lines of catpatch.sql output:
    COMP_NAME STATUS VERSION
    OLAP Analytic Workspace OPTION OFF 10.1.0.3.0
    Oracle OLAP API OPTION OFF 10.1.0.3.0
    Oracle Database Catalog Views VALID 10.1.0.4.0
    Oracle Database Packages and Types VALID 10.1.0.4.0
    JServer JAVA Virtual Machine VALID 10.1.0.4.0
    Oracle XDK VALID 10.1.0.4.0
    Oracle Database Java Packages VALID 10.1.0.4.0
    Oracle XML Database VALID 10.1.0.4.0
    Oracle interMedia INVALID 10.1.0.4.0
    Oracle Text VALID 10.1.0.4.0
    Oracle Ultra Search VALID 10.1.0.4.0
    Oracle Expression Filter INVALID 10.1.0.4.0
    Oracle Enterprise Manager VALID 10.1.0.4.0
    Oracle Workspace Manager VALID 10.1.0.2.0
    Oracle Data Mining OPTION OFF 10.1.0.3.0
    OLAP Catalog OPTION OFF 10.1.0.3.0
    Spatial OPTION OFF 10.1.0.3.0
    SQL> select owner, object_name, object_type from dba_objects where status like 'INVALID';
    OWNER OBJECT_NAME OBJECT_TYPE
    WK_TEST BIN$9oUB6zbaOP/gMCzPA4J5+w==$0 TRIGGER
    OLAPSYS ALL$OLAP2_AW_CATALOGS VIEW
    PUBLIC ALL_OLAP2_AW_CATALOGS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CATALOG_MEASURES VIEW
    PUBLIC ALL_OLAP2_AW_CATALOG_MEASURES SYNONYM
    OLAPSYS ALL$OLAP2_AW_PHYS_OBJ VIEW
    PUBLIC ALL_OLAP2_AW_PHYS_OBJ SYNONYM
    OLAPSYS ALL$OLAP2_AW_PHYS_OBJ_PROP VIEW
    PUBLIC ALL_OLAP2_AW_PHYS_OBJ_PROP SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIMENSIONS VIEW
    PUBLIC ALL_OLAP2_AW_DIMENSIONS SYNONYM
    OLAPSYS ALL$OLAP2_AW_ATTRIBUTES VIEW
    PUBLIC ALL_OLAP2_AW_ATTRIBUTES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBES VIEW
    PUBLIC ALL_OLAP2_AW_CUBES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_DIM_USES VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_DIM_USES SYNONYM
    OLAPSYS ALL$AW_DIM_ENABLED_VIEWS VIEW
    PUBLIC ALL_AW_DIM_ENABLED_VIEWS SYNONYM
    OLAPSYS ALL$AW_CUBE_ENABLED_VIEWS VIEW
    PUBLIC ALL_AW_CUBE_ENABLED_VIEWS SYNONYM
    OLAPSYS ALL$AW_CUBE_ENABLED_HIERCOMBO VIEW
    PUBLIC ALL_AW_CUBE_ENABLED_HIERCOMBO SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIM_LEVELS VIEW
    PUBLIC ALL_OLAP2_AW_DIM_LEVELS SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIM_HIER_LVL_ORD VIEW
    PUBLIC ALL_OLAP2_AW_DIM_HIER_LVL_ORD SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_MEASURES VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_MEASURES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_SPECS VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_SPECS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_MEAS VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_MEAS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_LVL VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_LVL SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_OP VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_OP SYNONYM
    OLAPSYS MRAC_OLAP2_AW_DIMENSIONS_V VIEW
    OLAPSYS MRAC_OLAP2_AW_CUBES_V VIEW
    OLAPSYS MRAC_OLAP2_AW_CUBE_MEASURES_V VIEW
    PUBLIC MRV_OLAP2_AW_DIMENSIONS SYNONYM
    PUBLIC MRV_OLAP2_AW_CUBES SYNONYM
    PUBLIC MRV_OLAP2_AW_CUBE_MEASURES SYNONYM
    OLAPSYS CWM2_OLAP_METADATA_REFRESH PACKAGE BODY
    OLAPSYS OLAP_SYS_AW_ACCESS_DIM_VIEW VIEW
    OLAPSYS OLAP_SYS_AW_ACCESS_CUBE_VIEW VIEW
    OLAPSYS OLAP_SYS_AW_ENABLE_ACCESS_VIEW VIEW
    PUBLIC OLAP_SYS_AW_ACCESS_CUBE_VIEW SYNONYM
    PUBLIC OLAP_SYS_AW_ACCESS_DIM_VIEW SYNONYM
    PUBLIC OLAP_SYS_AW_ENABLE_ACCESS_VIEW SYNONYM
    OLAPSYS CWM2_OLAP_OLAPAPI_ENABLE PACKAGE BODY
    OLAPSYS DBMS_AWM PACKAGE BODY
    OLAPSYS CWM2_OLAP_CUBE PACKAGE BODY
    53 rows selected.

  • Reexecuting the catalog.sql and catproc.sql

    what will happened if we re execute the catalog.sql and catproc.sql on existing running oracle database ? is some thing is distructive or what ?

    what will happened if we re execute the catalog.sql and catproc.sql on existing running oracle database ? is some thing is distructive or what ?what's the reason to re-running them? Any errors?
    Catalog - creates data dictionary views.
    Catproc - create in built PL/SQL Procedures, Packages etc
    Dictionary objects might go INVALID and you need to run utlrp.sql to validate them.
    No harm in running. But, its time consuming and resource consuming.
    HTH
    -Anantha

  • Help!!!: catalog.sql and catproc.sql damage my db

    after running the file my.sql (see below), i encounter some error:
    when i try to edit the table data, the following error displayed:
    ORA-04045 ... SYS.DBMS_OUTPUT
    ORA-06508 ...
    ORA-06512 ...
    ORA-06508 ...
    ORA-06512 ...
    then i go to the package SYS.DBMS_OUTPUT, the status is "invalid", i try to recompile it, the following error displayed:
    ORA-04045 ... SYS.CDC_ALTER_CTABLE_BEFORE
    ORA-06508 ...
    ORA-06512 ...
    ORA-06508 ...
    ORA-06512 ...
    my db works well before running the file my.sql. it seems the execution of catalog.sql and catproc.sql cause the error. i am using 9i, and the document histories show that the catalog.sql and catproc.sql are last updated in Apr,2001.
    my questions are:
    1.with 9i db, do i need to run the two files?
    2.how can i recover my db?(i don't have backup, can i use redoXX.log?)
    ***my.sql***
    connect sys/change_on_install@orcl as sysdba
    @/opt/oracle/rdbms/admin/catalog.sql
    connect sys/change_on_install@orcl as sysdba
    CREATE database mydb
    @/opt/oracle/rdbms/admin/catproc.sql
    ***my.sql***

    how can i get my db work properly just as it was?
    what do you mean by "create database script"?
    Database configuration assistant allows you to create the database template and then save it as a set of scripts that you
    can later customize and run to create the database. If you created your "create database scripts" using this option then
    these scripts automatically run the catproc.sql and catalog.sql scripts along with several other scripts.
    If you use Database configuration assistant to create such a set of DB creation scripts, than look at the
    CreateDBCatalog.sql script, as you can see it runs both the scripts. so, if you do it this way, you do not need to do any
    extra steps (apart from your custom scripts that may be part of your post install steps).
    A sample of such DB creation script will be as below (for your reference):
    ===================================================================
    connect SYS/change_on_install as SYSDBA
    set echo on
    spool /home/oracle/Ora9i/assistants/dbca/logs/CreateDBCatalog.log
    @/home/oracle/Ora9i/rdbms/admin/catalog.sql;
    @/home/oracle/Ora9i/rdbms/admin/catexp7.sql;
    @/home/oracle/Ora9i/rdbms/admin/catblock.sql;
    @/home/oracle/Ora9i/rdbms/admin/catproc.sql;
    @/home/oracle/Ora9i/rdbms/admin/catoctk.sql;
    @/home/oracle/Ora9i/rdbms/admin/owminst.plb;
    connect SYSTEM/manager
    @/home/oracle/Ora9i/sqlplus/admin/pupbld.sql;
    connect SYSTEM/manager
    set echo on
    spool /home/oracle/Ora9i/assistants/dbca/logs/sqlPlusHelp.log
    @/home/oracle/Ora9i/sqlplus/admin/help/hlpbld.sql helpus.sql;
    spool off
    spool off
    exit;
    ===========================================================================

  • I'm using LR5.7 on a Mac Mini running Mavericks and when I attempt to import a folder of new RAW photos from my external drive into my catalog instead of seeing a preview of each thumbnail photo I see the following message displayed: "Preview Unavailable

    I'm using LR5.7 on a Mac Mini running Mavericks and when I attempt to import a folder of new RAW photos from my external drive into my catalog instead of seeing a preview of each thumbnail photo I see the following message displayed: "Preview Unavailable for this file." If I highlight any other folder of photos the previews are all there. What is the likely reason for these previews being unavailable? JohnnyCam

    What camera took these RAW photos?
    Did you use any Nikon software to transfer the photos to your computer's hard disk?

  • I have just reformatted my drive and reinstalled creative cloud and lightroom. When i open it, it says there is another version running the catalog and i have to switch to it to fix the problem, but there is no other version on my computer. Does anyone kn

    I have just reformatted my drive and reinstalled creative cloud and lightroom. When i open it, it says there is another version running the catalog and i have to switch to it to fix the problem, but there is no other version on my computer. Does anyone know how to fix this?

    Where did you put the LR catalog?
    Did you install the same version of LR, which one?
    OS and version?
    Open the folder where the catalog (*.lrcat) is located. If you see a file with lock in it while LR is not running, delete it.
    Now try to start LR again.

  • Catalog.sql, catproc.sql

    Hi,
    I created a database manually. Then I run the scripts catproc.sql, catalog.sql and I obtained some errors ORA-01432 - public synonym to be dropped and then drop public synonym. To be ok? To pass with courage at the next step importing the full database exported from another computer?
    Thank you,
    Mihaela

    Well, I don't have an 8.1.7.4 DB on hands to try it :-)
    SQL> select version from v$instance;
    VERSION
    8.1.7.0.1
    SQL> create or replace synonym emp for scott.emp;
    create or replace synonym emp for scott.emp
    ERROR at line 1:
    ORA-00922: missing or invalid option
    SQL>                                                                           

  • **urgent- impact of rerunning catlog.sql and catproc.sql

    Hi ,
    We are in middle of troubleshooting an export issue where it gives error on exporting some of the packages that starts with DBMS_ .
    After doing metalink search it appears that some of the objects may be invalid and the suggestion is to run utlrp.sql which did not solve the problem.
    The other suggestion is to rerun catlog.sql and catproc.sql as sys user
    My question is, if we re run the the scripts, will it overwrite any v$ or dba_ views ?
    ps. this is a prodn db

    What's Oracle version?
    As said, it generally safe to run catalog.sql and catproc.sql but better do it at quiet time of your production DB.
    also you might want to investigate why these packages were broken in the first place. Someone temper with your database dictionary?

  • Images (w/correct meta data) are in catalog and on disk, but LR 5.7 considers them new on Import

    For reasons explained below, I want to try to re-import all my images into LR and hope that none/few are in fact considered new and are imported.  Yet, for some folders, LR is apparently unable to detect that my source images are already in the catalog, and are on disk, and that the source file meta data matches what LR knows about the images.  When I click an image in LR and Show in Finder, I do see the imported image on disk.  I can edit the image in the Develop module.  So, it seems good, but all is not well.   Sorry for the long post here, but I wanted to provide as much info as I could, as I am really seeking your help, which I'd very much appreciate.
    Here are some screen shots that illustrate the problem:
    Finder contents of the original images
    LR folder hierarchy
    an image as seen in LR
    Finder content of external LR copy of images
    import showing 10 "new" photos
    The original images ... (I'm not sure why the file date is April 2001 but the actual image date is January 2011; I may have just used the wrong date on the folder name?)
    The LR folder hierarchy ...
    An image as seen in LR ...
    The external folder containing the images in the LR library
    But on import of the original source folder, LR sees 10 "new" photos ...
    I tried "Synchronize Folder ..." on this particular folder, and it simply hangs half-way through as seen in the screen shot below.   IS THIS AN LR BUG?   This is really odd, since "Synchronize Folder ..." on the top-level folder completes quickly.
    I have a spreadsheet of of the EXIF data for the original files and those created by LR.  (I extracted this info using the excellent and free pyExifToolGui graphical frontend for the command line tool ExifTool by Phil Harvey.)   Almost all of the Exif data is the same, but LR has added some additional info to the files after import, including (of course) keywords.  However, I would not have expected the differences I found to enter into the duplicate detection scheme.  (I didn't see a way to attach the spreadsheet to this posting as it's not an "image".)
    I'm running LR 5.7 on a 27" iMac with Yosemite 10.10.2, having used LR since LR2.  I have all my original images (.JPEGs and RAWs of various flavors) on my internal drive on the Mac.   To me this is like saving all my memory cards and never re-using them.   Fortunately, these files are backed up several ways.   I import these images (copying RAWs as DNG) into LR with a renaming scheme that includes the import number, original file creation date and original file name.   There should be one LR folder for each original source file folder, with the identical folder name (usually a place and date).  I store the LR catalog and imported images on an external drive.  Amazingly and unfortunately my external drive failed as did it's twin, same make/size drive that I used as a backup with Carbon Copy Cloner.   I used Data Rescue 4 to recover to a new disk what I thought was almost all of the files on the external drive.
    So, I thought all would be well, but, when I tried "Synchronize Folder" using the top-level folder of my catalog, the dialog box appeared saying there were over 1000 "New" photos that had not been imported.  This made be suspicious that I had failed to recover everything.   But actually things are much worse than I thought..   I have these counts of images:
    80,0061 files in 217 folders for my original source files (some of these may be (temporary?) copies that I actually don't want to import into LR)
    51,780 files in 187 folders on my external drive containing the LR photo library
    49,254 images in the top-level folder in the LR catalog (why different from the external file count?)
    35,332 images found during import of the top-level folder containing original images
    22,560 images found as "new" by LR during import
    1,074 "new" images reported by Synchronize Folder ... on the top-level folder in the catalog; different from import count
    Clearly things are badly out of sync.   I'd like to be sure I have all my images in LR, but none duplicated.   Thus, I want to try to import the entire library and have LR tell me which photos are new.  I have over 200 folders in LR.  I am now proceeding to try importing each folder, one at a time, to try to reconcile the differences and import the truly missing images.  This will be painful.  And it may not be enough to fully resolve the above discrepancies.
    Does anyone have any ideas or suggestions?  I'd really appreciate your help!
    Ken

    Thanks for being on the case, dj!   As you'll see below, YOU WERE RIGHT!      But I am confused.
        1. Does the same problem exist if you try to import (not synchronize) from that folder? In other words, does import improperly think these are not duplic
    YES.  Import improperly thinks they are NOT duplicates, but they are in fact the same image (but apparently not the EXACT SAME bytes on disk!)
        2. According to the documentation, a photo is considered a duplicate "if it has the same, original filename; the same Exif capture date and time; and the same file size."
    This is my understanding too.
        3. Can you manually confirm that, for an example photo, that by examining the photo in Lightroom and the photo you are trying to synchronize/import, that these three items are identical?
    NO, I CAN'T!  The ORIGINAL file name (in the source folder) is the SAME as it was when I first imported that folder.  That name is used as part of the renaming process using a custom template. However, the file SIZES are different.    Here is the Finder Get Info for both files.  Initially, they appeared to be the same SIZE, 253KB, looking at the summary. But, if you look at the exact byte count, however, the file sizes are DIFFERENT: 252,632 for the original file and 2252,883 for the already-imported file:
    This difference alone is enough to indicate why LR does not consider the file a duplicate.
    Furthermore, there IS one small difference in the EXIF data regarding dates ... the DateTimeOriginal:
                                                                                                     CreateDate              DateTimeDigitized                    DateTimeOriginal              FileModifyDate                              ModifyDate
    ORIGINAL name: P5110178.JPG                                     2001:05:11 15:27:18    2001:05:11 15:27:18-07:00        2001:01:17 11:29:00        2011:01:17 11:29:00-07:00       2005:04:24 14:41:05  
    After LR rename:  KRJ_0002_010511_P5110178.JPG    2001:05:11 15:27:18    2001:05:11 15:27:18-07:00        2001:05:11 15:27:18        2011:01:17 11:29:02-07:00       2005:04:24 14:41:05
    So ... now I see TWO reasons why LR doesn't consider these duplicates.   Though the file NAME is the same (as original), the file sizes ARE slightly different.  The EXIF "DateTimeOriginal" is DIFFERENT.   Therefore, LR considers them NOT duplicates.
         4a. With regards to the screen captures of your images and operating system folder, I do not see that the filename is the same; I see the file names are different. Is that because you renamed the photos in Lightroom (either during import or afterwards)?
    I renamed the file on import using a custom template ...
            4b. Can you show a screen capture of this image that shows the original file name in the Lightroom metadata panel (it appears when the dropdown is set to EXIF and IPTC)?
    SO ....
    The METADATA shown by LR does NOT include the ORIGINAL file name (but I think I have seen it displayed for other files?).  The File SIZE in the LR metadata panel (246.96 KB) is different from what Finder reports (254 KB).  There are three "date" fields in the LR metadata, and five that I've extracted from the EXIF data.   I'm not sure which EXIF date corresponds to the "Data Time" shown in the LR metadata.
    I don't understand how these differences arose.   I did not touch the original file outside LR.   LR is the only program that touches the file it has copied to my external drive during import.  (though it was RECOVERED from a failed disk by Data Rescue 4),
    NOW ...
    I understand WHY LR considers the files different (but not how they came to be so).  The question now is WHAT DO I DO ABOUT IT?   Is there any tool I can use to adjust the original (or imported) file's SIZE and EXIF data to match the file LR has?  Any way to override or change how LR does duplicate detection?
    Thanks so very much, dj.   Any ideas on how to get LR to ignore these (minor) differences would be hugely helpful.

  • Moved catalog and now LR won't open it by default. Help?

    I'm running LR2 (I know, first step, UPGRADE!), but in the meantime, I had to move my catalog because my drive got full. Under the Backup dialog box I chose the new location. But when I just click on the LR icon to open the program it opens with the default C: drive catalog location that it first installed with. Then I open the specific catalog from in the program and relaunch it. I have LR set to bring the dialog box everytime I start LR since I don't use it everyday. So I back it up when the dialog comes up and when it's done it goes right back to the default catalog with none of my library in there.  Why do I have to keep opening the catalog manually?? It's driving me insane at this point. Can someone provide some tips please?? Thanks.

    Double-click the moved catalog and Lr will open with it.
    But in fact, you did not move the catalog at all. you made a backup of your catalog, and that is what you should do.
    But making a backup catalog does not mean that Lr now opens with the backup catalog.
    Having a backup means that there are now 2 catalogs: the "working" catalog and the backup catalog. If you had only one (1) catalog, you wouldn't have a backup.
    Lr still opens and works with your "working" catalog. That is normal and expected.
    If you want to move your "working" catalog do this:
    Close Lr. In your OS (Mac Finder / Win Explorer) move (not copy!) the catalog to a different location. Then double-click the moved catalog and Lr will open with it and will use the new location as "working" catalog. But I recommend that you do not put your "working" catalog on the same drive as the "backup" catalog. If that drive fails, you have neither a "working" nor a "backup" catalog. Not good!
    But I wonder why you would say your drive got full. Usually the catalog doesn't fill a drive, but your photos are.
    Moving the catalog doesn't move your photos.
    What you don't know, maybe, is that the catalog and the photos don't have to be on the same drive. So you can leave your catalog on the C-drive and have your photos somewhere else.
    If you want to move your photos, you best do this in Lr. If you do it in your OS, you will have to re-link the photos and image folders.
    See here on how to do the re-linking:
    http://tv.adobe.com/watch/creative-suite-podcast-photographers/lightroom-dude-where-are-my -photos/
    http://www.computer-darkroom.com/lr2_find_folder/find-folder.htm

Maybe you are looking for