Create Location in owb 10.2.0.4.

My repository is in version 10.2.0.4 and I want to connect to a sorce in version 11.1, is giving the following message:
rct-5318 invalid location type pair for name oracle database and version

I think 11g was certified in 10.2.0.5...
When you define the location which version did you select?
Cheers
David

Similar Messages

How to use OEM location in OWB?

What is a purpose of oem location in owb 9.2 (9.0.4)?
This location doesn't use in any module and integration with oem realize through oem_exec_template.sql script that manually register in oem.
How to use this location?

Dmitry,
This location would be used in the process flow configuration of an individual activity. The location enables you to perform remote node execution. For example, if you wanted to execute SQL loader on a remote node (not the actual target machine) then this would happen via the OEM location. The use of the OEM location would require an Oracle Management Server (OMS) set up and OEM agents locally.
Mark.

TCA API create_location creates locations irrespective of the address style

Hi All,
We are using Trading Community Architecture API for customer conversion. We have address styles setup for Canada and US and we have attached these address styles to the respective countries in the territories window.
But when we use create_location API for creating location and then a party site for it, it allows us to create the locations even when we dont pass in a value for the REQUIRED fields setup at the address style. We expected it to error out.
Does anyone have idea about how this works. We want the API to validate the addresses we enter for locations with the address styles we set up.
ketha

You can create a wrapper package on top of the API (hr_location_api.create_location)
In the wrapper package you set all the values dynamically based on your requirements(say the style and add_line columns are populated on your conditions) and then you call the API.
Does that not work ?

Creating locations for the assets in Asset accounting

Hi,
Can anyone please let me know how to create locations for the existing assets in AA module? We need to create locations and assign the assets so as to track the assets location wise.
Thanks,

Goto
SPRO-->Enterprise structure->Definition-->Logistic General->Define Location
there you can create location

How to create Location using tcode BBPMAININT

Hi,
I wanted to create local plants in EBP/SRM. I was using tcode BBPMAININT to create Location but facing problem.
Can any one please list steps to follow to create local plant? Is there any other tcode we can use?
Regards,
SAP Guy.

Hi,
What error message are you getting?
Generally LOCAL plants are created using the tracn BBPMAININT.You can also try using the FM "BBP_LOCATION_CREATE" to create the plant in SRM system.
BR,
Disha.
Do reward points for useful answers.

Calendar is automatically creating Location points - Why?

I'm using Calendar version 6.0 running on Mountain Lion 10.8.4 on an iMac. For some reason when I make a diary entry a location point is automatically created.As you can see on the above example Calendar has automatically created "The Day" as the location which is nonsense. I never type anything into this box. I simply leave it as None. Most of the automatically created locations do not make any sense. I'm at a loss as to how to turn this extremely annoying function off.
Your help would be appreciated.
Thanks,
Dave

I am having the exact same problem.
very annoying.
Anyone with an idea how to fix this?

Issue while creating location with database link

Hi all,
I am using OWB 10.2.0.4.0 (same Oracle DB version). I am trying to create a location using a database link.
When I select the location which the database link is located (From location drop-down list), I face the following error.
>
ENV0036: The selected location is not valid.
ENV0036: The selected location is not valid.
     at oracle.wh.service.sdk.integrator.RepositoryUtils.createDBLinkWithLocation(RepositoryUtils.java:156)
     at oracle.wh.ui.environment.wizards.DatabaseLinkComponent.init(DatabaseLinkComponent.java:61)
     at oracle.wh.ui.environment.wizards.DatabaseLinkComponent.reload(DatabaseLinkComponent.java:204)
     at oracle.wh.ui.environment.wizards.FromLocationComponent.itemStateChanged(FromLocationComponent.java:111)
     at javax.swing.JComboBox.fireItemStateChanged(JComboBox.java:1162)
     at javax.swing.JComboBox.selectedItemChanged(JComboBox.java:1219)
     at javax.swing.JComboBox.contentsChanged(JComboBox.java:1266)
     at javax.swing.AbstractListModel.fireContentsChanged(AbstractListModel.java:100)
     at javax.swing.DefaultComboBoxModel.setSelectedItem(DefaultComboBoxModel.java:88)
     at javax.swing.JComboBox.setSelectedItem(JComboBox.java:551)
     at javax.swing.JComboBox.setSelectedIndex(JComboBox.java:597)
     at javax.swing.plaf.basic.BasicComboPopup$ListMouseHandler.mouseReleased(BasicComboPopup.java:749)
     at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:232)
     at java.awt.Component.processMouseEvent(Component.java:5100)
     at javax.swing.plaf.basic.BasicComboPopup$2.processMouseEvent(BasicComboPopup.java:452)
     at java.awt.Component.processEvent(Component.java:4897)
     at java.awt.Container.processEvent(Container.java:1569)
     at java.awt.Component.dispatchEventImpl(Component.java:3615)
     at java.awt.Container.dispatchEventImpl(Container.java:1627)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
     at java.awt.Container.dispatchEventImpl(Container.java:1613)
     at java.awt.Window.dispatchEventImpl(Window.java:1606)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:480)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:141)
     at java.awt.Dialog$1.run(Dialog.java:542)
     at java.awt.Dialog$3.run(Dialog.java:569)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.awt.Dialog.show(Dialog.java:567)
     at java.awt.Component.show(Component.java:1133)
     at java.awt.Component.setVisible(Component.java:1088)
     at oracle.bali.ewt.wizard.WizardDialog.runDialog(Unknown Source)
     at oracle.bali.ewt.wizard.WizardDialog.runDialog(Unknown Source)
     at oracle.wh.ui.owbcommon.OWBWizard.initialize(OWBWizard.java:815)
     at oracle.wh.ui.owbcommon.OWBWizard.<init>(OWBWizard.java:168)
     at oracle.wh.ui.owbcommon.OWBWizard.<init>(OWBWizard.java:147)
     at oracle.wh.ui.owbcommon.IdeUtils._doLaunchDefinition(IdeUtils.java:1188)
     at oracle.wh.ui.owbcommon.IdeUtils.showWizard(IdeUtils.java:471)
     at oracle.wh.ui.owbcommon.IdeUtils.showWizard(IdeUtils.java:427)
     at oracle.wh.ui.jcommon.tree.WBRepositoryObjectTree.launchWizard(WBRepositoryObjectTree.java:502)
     at oracle.wh.ui.console.commands.CreateByWizardCmd.showUI(CreateByWizardCmd.java:33)
     at oracle.wh.ui.console.commands.CreateCmd.performAction(CreateCmd.java:76)
     at oracle.wh.ui.console.commands.TreeMenuHandler$1.run(TreeMenuHandler.java:188)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:189)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:478)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
>
Could you please let me know how to solve this and how to create such location with OMB*Plus?
Thanks,
Sebastian

Hi David,
Thanks a lot for the tip. Now I was able to use this and using a registered location.
OMBCREATE LOCATION 'X' SET PROPERTIES (TYPE,VERSION,CONNECTION_TYPE, SCHEMA) VALUES ('ORACLE_DATABASE','11.1','DATABASE_LINK','MY_SCHEMA')
OMBCREATE CONNECTOR 'REGISTERED_LOC/X SET PROPERTIES (DATABASE_LINK_NAME) VALUES ('MY_DBLINK') SET REF LOCATION 'X'
OMBCOMMIT
OMBCC '/MY_PROJECT'
OMBCAC 'DEFAULT_CONFIGURATION'
OMBCONNECT CONTROL_CENTER USE 'owb_user/owb_user'
OMBREGISTER LOCATION 'X' REUSE
OMBCOMMITBut now my question is the following.
I am having problems to import the metadata from X.
When create a module (source), I am able to make "data location" from location 'X' but when I want to import a table from location 'X' is not possible, because it shows as a plausible metadata location as "REGISTERED_LOC"
Could you please let me know how to use 'X' as metadata location?
Thanks!
Sebastián

How to set directory to file locations in OWB 904

Where I can to define a default directory for SQL* Loader control files and other data flat files?
Any attributes in configure of mapping about location is only combo box with locations list, BUT locations doesn't allow to set any default dirrectories, because it did not have this attribute!!

Hi Dmitry,
I'm assuming you are trying to determine the directory that you will need to load data from.
In this case, you pick a location, let's name it FF_DIR. You create as many locations in the FF module as required, however let's start with one.
Then you will deploy the mapping to the database (or better the runtime platform) and register a location. This will be your default directory and all mappings that use this location will now use this directory.
For an external table you will then create a directory with OWB that points to this location/directory by deploying the connector.
Hope this helps,
Jean-Pierre

Using locations in OWB

hi,
i have problem deploying the target module created in OWB 10g release 1. I have created the location and its connector but in the database location for that connector it does not show its own location name. so what does it exactly mean. how do we use this connector ?
The deploy results are all 'success' but after deploying it, it displays 'failed'.
is the above connector problem the reason i am getting the ORA:12541 TNS no listener ???

Do you have registered your locations?.
Mehdi

Creating Configuration in OWB 11gR2 using OMB+ Scripts

Hi All,
Please help how to create a configuration pointing to another OWB Repository using OMB+ scripts.Also how to change the Active Deployment Location for a module using OMB+ Script.

Hi
Here is how you can add a new location to a module and set its configuration setting to this location (ADC);
OMBALTER ORACLE_MODULE 'TGT_MOD' ADD REF LOCATION 'ADC'
OMBALTER ORACLE_MODULE 'TGT_MOD' SET PROPERTIES (DB_LOCATION) VALUES ('ADC')
http://download.oracle.com/docs/cd/E11882_01/owb.112/e14406/chap3015.htm#DADFHBGE
Not sure if this is what you are after? To create a new configuration pointing to your own control center;
OMBCREATE CONTROL_CENTER 'MYCC' SET PROPERTIES ( etc...
OMBCREATE CONFIGURATION 'MYCONFIG'
OMBCC 'MYCONFIG'
OMBCREATE DEPLOYMENT 'MYCONFIGDEPLOY' SET REF CONTROL_CENTER 'MYCC'
Cheers
David

Error creating location

HI ALL,
I am using OWB 11g r2 ,
Location for my project is not showing in location navigator under oracledatabase tab. When i am trying to create a new location its showing connection is successful but unable to retrive workflow version . Can anyone help me regarding this.

Hi
Sounds like you are trying to create a workflow location using a database schema that does not have workflow installed. If so you need to install workflow into that database schema if that is what you are trying, if not then create a regular Oracle database location (and not a workflow one).
Cheers
David

Need TCL for the "Use Global Names" checkbox when creating Location(s)

We have a TCL script that creates OWB locations as part of our automated install and build process. Recently we switched to using GLOBAL NAME = TRUE on our databases (to implement Oracle Streams). In order to create a location and successfully register the location in the GUI, we need to manually check the "Use Global Names" checkbox and then enter the fully qualified name to successfully connect and register. We need to be able to code this into our TCL scripts to get this location creation and registration done programmatically, but we've reviewed the API coding guide and found nothing. So far, our SR on Oracle support hasn't turned up much either.
Just wondering if anyone else out there has had any success with locations with Global Names enabled, using TCL...?
And it's: OWB 10gR2.
Thanks,
Jim

From my installation script which deals with databases with both global names settings:
       if [string match TRUE $dbGlobalNames] {
           OMBCREATE LOCATION '$DATA_LOCATION_NAME' SET PROPERTIES (TYPE, VERSION, DESCRIPTION, BUSINESS_NAME, HOST, PORT, SERVICE, CONNECT_AS_USER, PASSWORD, DATABASE_NAME) VALUES ('ORACLE_DATABASE','$DATA_LOCATION_VERS','ERS Datamart Code User','$DATA_LOCATION_NAME', '$DATA_LOCATION_HOST','$DATA_LOCATION_PORT','$DATA_LOCATION_SRVC', '$DATA_LOCATION_USER','$DATA_LOCATION_PASS','$DATA_LOCATION_SRVC' )
       } else {
           OMBCREATE LOCATION '$DATA_LOCATION_NAME' SET PROPERTIES (TYPE, VERSION, DESCRIPTION, BUSINESS_NAME, HOST, PORT, SERVICE, CONNECT_AS_USER, PASSWORD) VALUES ('ORACLE_DATABASE','$DATA_LOCATION_VERS','ERS Datamart Code User','$DATA_LOCATION_NAME', '$DATA_LOCATION_HOST','$DATA_LOCATION_PORT','$DATA_LOCATION_SRVC', '$DATA_LOCATION_USER','$DATA_LOCATION_PASS')
       }Addding a value to the DATABASE_NAME property lets OWB know that this a case where GLOBAL_NAMES=TRUE as you wouldn't populate that value otherwise. OWB then will check that checkbox for you.
Cheers,
Mike

OMB plus Creating Locations Modules And Importing the Metadata?

Hi All,
First of all I would like to thank you all of you in advance for all your time and concern. I have serious of questions and I will ask them in 3 different portions as they are slightly different.
How can I implement the steps below using OMB plus? If you could provided sample script and notation it will be highly appreciated.
-- Creating an Oracle Location for a Schema and Registering it
-- Creating an Module and relating it to the location that was created.
-- Importing the metadata for all the objects in this Schema in to this module.
For example,
You have a schema called ORACLE_SRC. I need to create the location and module for this schema and tie them each other. Then I need to import all the metadata for all the objects in this ORACLE_SRC schema. During this import all the preserve statements should be unchecked. And I need to accomplish all these using OMB plus and TCL scripting.
-- Creating an Non Oracle (SQL server 2005) Location for a database and Registering it
-- Creating an Module and relating it to the location that was created.
-- Importing the metadata for all the objects in this Schema in to this module.
For example,
You have a schema called SQLSERVER_SRC. I need to create the location and module for this schema and tie them each other. Then I need to import all the metadata for all the objects in this SQLSERVER_SRC schema. During this import all the preserve statements should be unchecked. And I need to accomplish all these using OMB plus and TCL scripting.
-- Creating an Flat File Location for a folder structure and Registering it
-- Creating an Module and relating it to the location that was created.
For example,
You have a schema called FLATFILE_SRC. I need to create the location and module for this schema and tie them each other.
Thanks again for all your help and concern!
Kind Regards,
Mike

In addition to the performance issue above I have faced an extremely more important problem. When I have used the same logic for importing Materialized views I am getting an error at the last step of the script. It is exactly the same case also for EXTERNAL_TABLE objects. TABLE and VIEW objects are fine. OMBIMPORT command throw the error message below.
PUB04201: Encountered an internal fatal error during processing of oracle module XXX_DMY_DWPROD_TST: unsupported obj type.
I would like to mention that MATERIALIZED_VIEW is the object name I took from OWB scripting Reference guide. I have tried couple other naming conventions too but it didn't work.
Strange thing is If I were to change MATERIALIZED_VIEW to TABLE it works but the materialized view gets imported into 'Tables' folder under the module.
Please help?
     #IMPORT FOR MATERIALIZED VIEWS STARTS
#pull the names of the object inthe schema
     set MVIEWLIST {}
     set sqlStr "select distinct Mview_Name from all_mviews where owner = upper('$DbNm') order by Mview_Name"
     #execute the query
     set oraRs [oracleQuery $oraConn $sqlStr]
     #Loop through the list of objects
     while {[$oraRs next]} {
          set mvwName [$oraRs getString Mview_Name]
          lappend MVIEWLIST $mvwName
     #and close the query
     $oraRs close
     set listCntr 0
     set listTotal [llength $MVIEWLIST]
     set mviewName [lindex $MVIEWLIST $listCntr]
     #First object
     OMBALTER IMPORT_ACTION_PLAN 'IMPORT_ALL' ADD ACTION 'MAT_VIEWS' SET REF SOURCE MATERIALIZED_VIEW '$mviewName' SET REF TARGET ORACLE_MODULE '$ModNm'
     OMBCOMMIT
     puts "$mviewName is being imported"
     incr listCntr
     while {$listCntr<$listTotal} {
          #Rest of the objects
          set mviewName [lindex $MVIEWLIST $listCntr]
          incr listCntr
          OMBALTER IMPORT_ACTION_PLAN 'IMPORT_ALL' MODIFY ACTION 'MAT_VIEWS' SET REF SOURCE MATERIALIZED_VIEW '$mviewName' SET REF TARGET ORACLE_MODULE '$ModNm'
          OMBCOMMIT
          puts "$mviewName is being imported"
     set listCntr 0
     set listTotal 0
     #IMPORT FOR MATERIALIZED VIEWS ENDS
          OMBIMPORT FROM METADATA_LOCATION FOR IMPORT_ACTION_PLAN 'IMPORT_ALL'
          OMBDROP IMPORT_ACTION_PLAN 'IMPORT_ALL'

How to Create/Locate Offline Photographs, Revisited

I hope this updated procedure may be useful to others: I believe that I have evolved a viable scheme (in Lightroom 2.4 under Windows XP), both for importing old photographs that had been burned onto CD/DVD, and for burning and moving offline new photographs that have been imported directly from a camera onto the hard drive in LR. The goal is to get ALL photos into the online LR catalog while keeping the most recent image files online only until enough inactive ones have accumulated to fill a new CD/DVD. If anyone still archiving to CD/DVD has the patience to read through this long post, any corrections or improvements would be greatly appreciated! (In any case, it's been helpful to me to write it up.)
0) Background: My old photo CDs (ISO 9669 Mode 1 Level II) each contain a parent directory named according camera/photographer (e.g., "MY_CANON_PHOTOGRAPHS") and numerous sub-directories named either by capture date or by import date, according to the proprietary software that was originally used to import them. These CDs also have hand-written disk names (e.g., "My Canon Photographs III") by which they can be manually identified. (I didn't bother giving the CDs unique electronic names, nor does it appear that it would have helped much if I had. Am I wrong here?) One of my goals is to keep this disk labeling and directory structure as consistent as possible going forward, burning new disks with third-party software that features a verify-after-burn cycle (and using high-quality media, of course) for data security. Minor differences in date format of the old, proprietarily generated folder names also makes it convenient to keep them segregated under separate parent directories in LR, as on the CDs themselves (see section 2 below).
1) To import pre-existing photographs from CD/DVD into a LR catalog WITHOUT moving the image files to the HD (the easy part): Insert the CD and click "File/Import Photos from Disk..." Select the parent directory on the CD. (This parent should be reflected in a parent folder within the LR catalog. If not, right-click on any of the new dated sub-folders and select "Add Parent Folder.") Click "Import All Photos in Selected Folder," and wait for "Computing dates..." to complete. Under File Handling select "Add photos to catalog without moving." Under Keywords, add the name written on the CD/DVD (e.g., "CD-My_Canon_Photographs_III"), along with any other desired keywords. (This keywording is the step that allows the offline source of individual catalogued photos to be manually identified.) Click Import. Note that keywords should not contain spaces; substitute hyphens, underscores, or similar. The LR Text filter -- the only facility that allows a "Don't Contain," or logical NOT, option -- does not currently allow searches on phrases containing spaces. (The familiar Windows quote marks don't work.)
2) To import new photos from a camera to HD in LR (also easy): Connect the camera and click "File/Import Photos from Device..." Under File Handling retain "Copy photos to a new location and add to catalog." Under Copy to, choose an exsiting, or create a new, parent directory, as appropriate (e.g., "...\My Pictures\Lightroom\MY_CANON_PHOTOGRAPHS" -- this to maintain consistency with existing CD structure). Under Organize choose "By date: YYYY-MM-DD" (according to your preference), and leave File Naming as "Filename" or change as desired. (Note that in my case there are slight differences in date format in LR as compared to the old proprietary software used for earlier CDs, e.g., hypens in place of underscores. If these will create folder-sequencing problems in the catalog later on, it is best to use a different parent directory for the LR-imported pictures -- e.g., "LR_CANON_PHOTOGRAPHS.") Under Keywords, add something like "NOT_YET_ARCHIVED" (as a reminder) along with any other desired keywords. Click Import. If at the end of the process you don't see the parent folder in the LR catalog, right-click on any of the new dated sub-folders and select "Add Parent Folder."
3) To burn new photos to CD/DVD and delete them from the HD (the tricky part):
      a) First, use LR's "Library/New Folder" to create a unique new parent directory on the HD (e.g., "Photo DVD II" -- this may as well become the name hand-written on the optical disk for later manual identification), in my case under "...\My Pictures\Lightroom\," to contain the entire directory structure that you want to burn to a SINGLE optical disk. In my case this structure consists of a sequence of dated subdirectories under one or more existing parent directories like "LR_CANON_PHOTOGRAPHS." Then, still in LR, drag and drop these existing parent directories onto the new parent, one by one. These steps are important, as they will greatly simplify the process of redirecting the LR catalog to point to the new offline files -- see step 3.c below. Finally, select all of the photos in this directory structure and (in the Grid view!) add a keyword (e.g., "DVD-Photo_DVD_II"), to be sure that you will know which offline media to load when you want access to these photographs in the future.
      b) It may be wise at this point to select the relevant directory structure and click "Metadata/Save Metadata to Files," to make sure that all of your metadata work will be saved in the image files on CD/DVD. Then close LR and use third-party burning software (with verify!) to burn the above directory structure, INCLUDING the newly created parent directory, onto the CD/DVD. Don't forget to hand-write a name on the disk (in this case, "Photo DVD II") by which it can be manually identified later.
      c) Restart LR, right-click on the newly created parent folder (in this example, "Photo DVD II"), and select "Update Folder Location..." Navigate to the corresponding parent (now root) directory on the new CD/DVD, and click OK. This procedure should re-link all the sub-folders and photographs in the newly burned part of the LR catalog to the corresponding directories/image files on the optical disk. You will see these sub-folders disappear from under the HD heading and re-appear in the newly created parent folder under the optical-drive heading. (Again, if you don't see this parent folder in the LR catalog, right-click on any of the newly burned, second-level folders and select "Add Parent Folder.")
      d) Only after you are completely satisfied that the CD/DVD burn was successful and your photographs are safe, close LR and (using the Windows Explorer, or whatever) delete the newly burned directory structure from the HD. Back in LR, the thumbnails and metadata for the now-moved photographs will still be accessible in the appropriate folders under the optical drive. If the CD/DVD is removed, the directory structure will be "grayed out," with question marks to indicate "missing" folders; but browsing, keywording, etc. can still be done. If you want to "Develop" or otherwise work with the actual images, you have only to identify the correct optical media and re-insert it into the drive. If you want to do extensive work on, or otherwise re-catalog, these photographs, however, you can always (outside LR) copy the entire directory tree from the optical drive back onto the HD and then reverse the process described in 3.c above to re-link the catalog to the on-line copy.
      e) Finally, delete the "NOT YET ARCHIVED" keyword on all of the burned photographs, now in the CD/DVD folder. (Don't forget to Select All in the Grid view!)
      f) Just one more thought. Some evidently feel that DVDs are not reliable long-term storage. My current solution to this potential problem is to burn the original photographs onto CD-R's, structured similarly to the old CDs described in Section 0 above, as soon as they are imported, before any work is done on them in LR. These CDs can be stored offsite, just in case the DVDs fail. Personally, however, I don't want to maintain a RAID system of external hard drives, and I trust DVD+R's more than I trust the HD in my laptop.
Thanks in advance for any comments. -- JClarkW

I hope this updated procedure may be useful to others: I believe that I have evolved a viable scheme (in Lightroom 2.4 under Windows XP), both for importing old photographs that had been burned onto CD/DVD, and for burning and moving offline new photographs that have been imported directly from a camera onto the hard drive in LR. The goal is to get ALL photos into the online LR catalog while keeping the most recent image files online only until enough inactive ones have accumulated to fill a new CD/DVD. If anyone still archiving to CD/DVD has the patience to read through this long post, any corrections or improvements would be greatly appreciated! (In any case, it's been helpful to me to write it up.)
0) Background: My old photo CDs (ISO 9669 Mode 1 Level II) each contain a parent directory named according camera/photographer (e.g., "MY_CANON_PHOTOGRAPHS") and numerous sub-directories named either by capture date or by import date, according to the proprietary software that was originally used to import them. These CDs also have hand-written disk names (e.g., "My Canon Photographs III") by which they can be manually identified. (I didn't bother giving the CDs unique electronic names, nor does it appear that it would have helped much if I had. Am I wrong here?) One of my goals is to keep this disk labeling and directory structure as consistent as possible going forward, burning new disks with third-party software that features a verify-after-burn cycle (and using high-quality media, of course) for data security. Minor differences in date format of the old, proprietarily generated folder names also makes it convenient to keep them segregated under separate parent directories in LR, as on the CDs themselves (see section 2 below).
1) To import pre-existing photographs from CD/DVD into a LR catalog WITHOUT moving the image files to the HD (the easy part): Insert the CD and click "File/Import Photos from Disk..." Select the parent directory on the CD. (This parent should be reflected in a parent folder within the LR catalog. If not, right-click on any of the new dated sub-folders and select "Add Parent Folder.") Click "Import All Photos in Selected Folder," and wait for "Computing dates..." to complete. Under File Handling select "Add photos to catalog without moving." Under Keywords, add the name written on the CD/DVD (e.g., "CD-My_Canon_Photographs_III"), along with any other desired keywords. (This keywording is the step that allows the offline source of individual catalogued photos to be manually identified.) Click Import. Note that keywords should not contain spaces; substitute hyphens, underscores, or similar. The LR Text filter -- the only facility that allows a "Don't Contain," or logical NOT, option -- does not currently allow searches on phrases containing spaces. (The familiar Windows quote marks don't work.)
2) To import new photos from a camera to HD in LR (also easy): Connect the camera and click "File/Import Photos from Device..." Under File Handling retain "Copy photos to a new location and add to catalog." Under Copy to, choose an exsiting, or create a new, parent directory, as appropriate (e.g., "...\My Pictures\Lightroom\MY_CANON_PHOTOGRAPHS" -- this to maintain consistency with existing CD structure). Under Organize choose "By date: YYYY-MM-DD" (according to your preference), and leave File Naming as "Filename" or change as desired. (Note that in my case there are slight differences in date format in LR as compared to the old proprietary software used for earlier CDs, e.g., hypens in place of underscores. If these will create folder-sequencing problems in the catalog later on, it is best to use a different parent directory for the LR-imported pictures -- e.g., "LR_CANON_PHOTOGRAPHS.") Under Keywords, add something like "NOT_YET_ARCHIVED" (as a reminder) along with any other desired keywords. Click Import. If at the end of the process you don't see the parent folder in the LR catalog, right-click on any of the new dated sub-folders and select "Add Parent Folder."
3) To burn new photos to CD/DVD and delete them from the HD (the tricky part):
      a) First, use LR's "Library/New Folder" to create a unique new parent directory on the HD (e.g., "Photo DVD II" -- this may as well become the name hand-written on the optical disk for later manual identification), in my case under "...\My Pictures\Lightroom\," to contain the entire directory structure that you want to burn to a SINGLE optical disk. In my case this structure consists of a sequence of dated subdirectories under one or more existing parent directories like "LR_CANON_PHOTOGRAPHS." Then, still in LR, drag and drop these existing parent directories onto the new parent, one by one. These steps are important, as they will greatly simplify the process of redirecting the LR catalog to point to the new offline files -- see step 3.c below. Finally, select all of the photos in this directory structure and (in the Grid view!) add a keyword (e.g., "DVD-Photo_DVD_II"), to be sure that you will know which offline media to load when you want access to these photographs in the future.
      b) It may be wise at this point to select the relevant directory structure and click "Metadata/Save Metadata to Files," to make sure that all of your metadata work will be saved in the image files on CD/DVD. Then close LR and use third-party burning software (with verify!) to burn the above directory structure, INCLUDING the newly created parent directory, onto the CD/DVD. Don't forget to hand-write a name on the disk (in this case, "Photo DVD II") by which it can be manually identified later.
      c) Restart LR, right-click on the newly created parent folder (in this example, "Photo DVD II"), and select "Update Folder Location..." Navigate to the corresponding parent (now root) directory on the new CD/DVD, and click OK. This procedure should re-link all the sub-folders and photographs in the newly burned part of the LR catalog to the corresponding directories/image files on the optical disk. You will see these sub-folders disappear from under the HD heading and re-appear in the newly created parent folder under the optical-drive heading. (Again, if you don't see this parent folder in the LR catalog, right-click on any of the newly burned, second-level folders and select "Add Parent Folder.")
      d) Only after you are completely satisfied that the CD/DVD burn was successful and your photographs are safe, close LR and (using the Windows Explorer, or whatever) delete the newly burned directory structure from the HD. Back in LR, the thumbnails and metadata for the now-moved photographs will still be accessible in the appropriate folders under the optical drive. If the CD/DVD is removed, the directory structure will be "grayed out," with question marks to indicate "missing" folders; but browsing, keywording, etc. can still be done. If you want to "Develop" or otherwise work with the actual images, you have only to identify the correct optical media and re-insert it into the drive. If you want to do extensive work on, or otherwise re-catalog, these photographs, however, you can always (outside LR) copy the entire directory tree from the optical drive back onto the HD and then reverse the process described in 3.c above to re-link the catalog to the on-line copy.
      e) Finally, delete the "NOT YET ARCHIVED" keyword on all of the burned photographs, now in the CD/DVD folder. (Don't forget to Select All in the Grid view!)
      f) Just one more thought. Some evidently feel that DVDs are not reliable long-term storage. My current solution to this potential problem is to burn the original photographs onto CD-R's, structured similarly to the old CDs described in Section 0 above, as soon as they are imported, before any work is done on them in LR. These CDs can be stored offsite, just in case the DVDs fail. Personally, however, I don't want to maintain a RAID system of external hard drives, and I trust DVD+R's more than I trust the HD in my laptop.
Thanks in advance for any comments. -- JClarkW

Strategy to create projects in OWB

Hi Fellows
We are starting using OWB and I like to know your expertise how to structure our projects in OWB
We want to use OWB for Data warehouse projects.
We have different layers in our architecture and each layer has its own schemas
for example, we have a data load layer, an integration layer, a start schema layer and a reporting layer.
Each have their own schemas.
We have development projects that many developers can work on the project.
My question comes when you do recommend to create project.
Do we create one project for all layers?
Do we create oner project for each layer(schema)?
Do we create project for every development project?
or any other criteria to consider to help us decide when we create projects.
Sincerely

Hey,
please create one project for all layers and for each layer one module.
For each development project create one collection.
All answers are valid if your development is made on site.
BR

Create Location in owb 10.2.0.4.

Similar Messages

Maybe you are looking for