Multiple Runtime Repositories

First let me explain my situation.
I have several projects and they all have similar sources and targets.
1) It appears I cannot use the same schema to hold runtime repository user for two different OWB Projects -- TRUE or FALSE?
2) I created another Runtime User for the new project, but have only one Runtime Repository Owner. This also appears to impossible as for some reason I'm unable to connect and run on this runtime. TRUE of FALSE?
3) DOes this mean I need a separate Runtime Repository Owner and Runtime User for every Project?
Thanks
Sridhar

Hey Sridhar, I love this True/False format but I will add some explanations for the extra credit ;-)
1. FALSE. Projects are just a grouping convenience at the design time. Projects have a many to many relationship to runtime repository, i.e. many projects can be deployed into the same runtime repository and the same project can be deployed into many runtime repositories. What is the symptom that make you think otherwise?
2. FALSE. Multiple Runtime Users can belong to the single Runtime Owner. The reason to have a Runtime User is security, it has very limited database privileges.
3. NO, as per above.
Nikolai Rochnik

Similar Messages

  • Multiple runtime users for the same runtime

    Hi,
    Is there any GUI method to create multiple runtime users to access the same runtime repository ? Currently, we are running this script:
    =============
    grant WB_U_UII_OWB_REP9204 to &&rep_user;
    grant WB_R_UII_OWB_REP9204 to &&rep_user;
    grant WB_D_UII_OWB_REP9204 to &&rep_user;
    grant WB_A_UII_OWB_REP9204 to &&rep_user;
    ==============
    Is this the correct way of doing it ?
    Thanks and regards,
    Biswa.

    Biswa,
    No way to do this in UI other than the first time the runtime repository is created by the Runtime Assistant. However, as you correctly point out, granting the following 4 roles to any user is all it takes: WB_RT_X, where RT is the name of your Runtime Repository and X is A, D, R or U:
    - The User role (U) gives select access to the public views in the runtime repository.
    - The Developer role (D) gives execute access to the PL/SQL packages in the runtime repository required to perform deployment operations.
    - The Runtime role (R) gives execute access to the PL/SQL packages in the runtime repository required to perform execution operations.
    - The Admin role (A) gives execute access to the PL/SQL packages in the runtime repository required to perform administrative operations.
    So you actually have some flexibility as to what exactly you want to allow the user to do.
    Nikolai Rochnik

  • Creating multiple runtime access users in OWB

    Hi,
    Can anyone tell me how to create multiple runtime access users in OWB. Using Runtime Repository Assistant everytime i may have to create Runtime Repository schema for creating Runtime Access user.
    Regards,
    Kunal

    We have 1 runtime repository and many runtime access users.
    Please change the repository user and rauser
    CREATE USER PMIRA
    IDENTIFIED BY 'PASSWORD'
    DEFAULT TABLESPACE TOOLS
    TEMPORARY TABLESPACE TEMP
    PROFILE DEFAULT
    ACCOUNT UNLOCK;
    GRANT CONNECT TO PMIRA;
    GRANT WB_A_OWB101RR TO PMIRA;
    GRANT WB_D_OWB101RR TO PMIRA;
    GRANT WB_R_OWB101RR TO PMIRA;
    GRANT WB_U_OWB101RR TO PMIRA;
    ALTER USER PMIRA DEFAULT ROLE CONNECT;
    ALTER USER PMIRA
    QUOTA UNLIMITED ON TD10_WHS_SMALL_I01
    QUOTA UNLIMITED ON TD10_WHS_SMALL_D01
    QUOTA UNLIMITED ON TD10_ODS_SMALL_I01
    QUOTA UNLIMITED ON TD10_ODS_SMALL_D01
    QUOTA UNLIMITED ON TD10_STG_SMALL
    QUOTA UNLIMITED ON CONVERSIE;

  • Multiple runtime configurations

    Hi,
    I'd like to set up multiple runtime configurations on a project. i.e. I want to be able to run the same java class with multiple program arguments or virtual machines. Is there any way I can do this without creating a separate project or using <target> in an ant file?
    Thanks in advance for any help,
    Venura

    Hi Venura,
    You can do this in Project Properties. On the Profiles page, click New... to create a new profile. You can change many of the runtime settings associated with the project for each individual profile.
    Thanks,
    Brian
    JDev Team

  • How to Configure ODI Console to Connect Multiple Master Repositories

    Hi,
    Can anybody help me in following,
    1. How to configure ODI Console to access Multiple Master Repositories and its corresponding Work Repository?
    2. Solutions are not supported by ODI Console? Is it possible to import scenarios as solutions in ODI Console?
    Thanks
    MT

    MT,
    1. I can only speak on my own experience in setting up the ODI console, but my understanding is that the console is configured against a single master repository - the connection details are picked up when the WebLogic server starts.  If I'm wrong, I'm sure one of the gurus will correct me.
    2. I haven't come across a way to do this - I'm using 11.1.1.5.  Aside from my initial go-live, I tend to only promote individual scenarios across environments.  For the rare occasion when I need to do a larger bulk import I'll just use ODI Studio.

  • Multiple Calendar Repositories?

    Is it possible to create multiple calendar repositories.
    one for Lotus and one for Exchange?

    Hi,
    If tried that. But every time I try to add new Calendar repository it gives and error:
    Configuration framework system error: "The prefix /calendar of repository lotus is already in use for repository davxchg"
    No is it possible to have Lotus and Exchnge integrated with the room calendar?
    We have to groupware systems in place Lotus and Exchange.
    Regards
    Richard

  • How  to reuse common code across multiple work repositories

    Hi Experts,
    I have a ruqirements from our customer side. we have a one master repository attached with three work repositories(wk1,wk2,2k3). Customer want to place some common code into wk1 workrepository and want to reuse across multiple workrepositories(wk2,wk3).
    Generally we can reuse code in same work repositories like knowmodules and interfaces.
    Is it possible to use across mutiple workrepositories?
    Thanks in Advance
    Siri

    You can't hare the same instance of the code across multiple work repositories. You have to have a seperate instance in each work repository. However you can manage it as if it was shared through ODI's versioning capability i.e. all changes to the common code are only ever made in one work repository i.e. Wk1 and then deployed to the other 2 which is as simple as getting the latest version from the Master repository. You could even set up security in Wk2 and Wk3 to make sure that your developers/users do not have permission to edit the common code in those repositories.

  • Installing and configuring Warehouse design and runtime repositories

    Hi,
    My topology is this:
    machine 1: Oracle database 9i (source data): instance: dbprod
    machine 2: Oracle database 10gR2: instances: owbdes and owbrun
    I have installed Oracle Warehouse builder 10.2 on machine 2. The implementation is as follows:
    I want to create a design repository on instance owbdes and a runtime repository on owbrun.
    The design repository on owbdes will contain the metadata from source dbprod and the metadata is intended to be deployed on owbrun.
    I am confused about the creation of repositories. Could someone send me detailed information about this?
    I know I have to run the OWB repository assistant on both owbdes and owbrun, but I don't know how to configured them in order to be the design and runtime repositories.
    For example when running the repository assistant I choose Advanced Setup, but do I have to create a new Repository owner for each database instance? Do I have to create the same target schemas on both instances?
    Please help me.
    Thanks in advance.

    I know I have to run the OWB repository assistant on both owbdes and owbrun, but I don't know how to configured them in order to be the design and runtime repositories.Yes, you should create OWB repository on the each server. During development you usually connect (with OWB Design Center) to design repository, but when you want to register new target schema you should connect with OWB client to runtime repository.
    Also you need to register Control Center (located on owbrun) in Design Center (when connected to design repository) from Connection Explorer, then you should modify Configuration for each of your OWB project - change Control Center from DEFAULT_CONTROL_CENTER to new.
    For example when running the repository assistant I choose Advanced Setup, but do I have to create a new Repository owner for each database instance?Yes, you need to create repositor owner on each DB instance.
    Do I have to create the same target schemas on both instances?No, you should create target schema only in target database instance
    Also read this threads, hope they will be helpful
    How to create a runtime repos in 10gR2
    OWB Standalone Target Schema - Split Architecture
    Regards,
    Oleg

  • Multiple Master Repositories

    Hi,
    Can we have multiple master repositories under single user i.e under  repository connection information dialog box we normally enter 'SUPERVISOR' and
    SUNOPSIS as password and under Database Connection(Master Repository) can we have 2 master repository users as part of two connections?
    i.e having two  master repository conections  under  one SUPERVISOR User pointing same URL i.e database.
    Cheers

    Hi,
    Yes you can create multiple master repository under SUPERVISOR user but different master repository schema in database.
    Thanks

  • Multiple development repositories issues

    We are going forward with multiple repositories for development. I would
    greatly appreciate any input from individuals who have implemented such a
    strategy or who have investigated it.
    Development would occur simultaneously in several repositories with one
    repository ultimately having all plans (projects) from all repositories.
    Other repositories would only have the projects that they are responsible
    for developing and read only copies of ones that they need as suppliers.
    The following are concerns
    * Keeping track of project versions and supplier plan dependencies
    * Propagating changes in one repository to another.
    * What is the definitive number of people in a repository for
    development/production. I have heard 10-12 and as many as 25 before
    performance degradation occurs.
    The solutions we have settled on (in the interim) are:
    * There will be no more than 10-12 developers per repository
    * Each development team will get their own repository
    * All project versions developed will be checked into a source code
    control (SCC) program
    * Anyone requiring a project as a supplier plan will pull them from
    SCC into a slave workspace of their repository, integrate it into the
    baseline and check it out (along with all supplier plans to that project
    with correct version).
    Does anyone else see the headache here?..... Bueller?
    BTW our version is Forte 3G2 on HPUX with NT4 clients.
    Len Lopez
    <http://www.carlsonwagonlit.com/> Carlson Wagonlit Travel, Inc.
    (612)594-2539
    [email protected] <mailto:[email protected]>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Sure.
    Only select the apps that you want to sync.
    It will only sync what you tell it to sync to each device.

  • One or more Runtime Repositories

    LS,
    I've been working with OWB903 for a while, but now we've migrated to 9.2, and I have a question about the best practice regarding the use of the Runtime Repository.
    Since multiple project are going to be defined in OWB, do I need only 1 general runtime repository for all projects that are going to be defined in OWB, or shoud I have one runtime repository per project (and therefore a RRU and a RAU per project)?
    Cheers, Patrick

    I would recommend to have one runtime repository per project (and one runtime schema per project too). The runtime repository contains metadata on the runtime operations (what objects were deployed and when, what was the deployment outcome etc., also, what mapping/process flow etc. was run and when, what was the outcome...). This kind of info is strictly related to a single project/runtime environment configuration.
    Regards:
    Igor

  • Multiple runtime systems

    Hello All,
    Is there a way to define two runtime production systems in NWDI for a track?
    Thanks,
    Kiran

    Hi Kiran,
    May be this thread will come in handy. I explained clearly the procedure to deploy to multiple systems
    transport to mulitple systems
    thanks

  • Control Center performance improvement for large (runtime) repositories

    Hi all,
    I'm currently working on a large OWB project. We have serious performance issues with the Control Center (version 10.2.0.3) I have investigated what happens when you start the Control Center (SQL traces) and have implemented the following:
    -- slow query 1
    -- also added parent_audit_object_id to this index to help with slow query 3
    CREATE INDEX colin_wb_rt_audit_objects_1 ON
      wb_rt_audit_objects(audit_object_id, parent_audit_object_id, audit_unit_id, number_of_script_errors, number_of_script_warnings);
    -- slow query 2
    CREATE INDEX colin_wb_rt_audit_scripts_1 ON
      wb_rt_audit_scripts(audit_object_id, audit_script_id);
    -- slow query 3
    CREATE INDEX colin_wb_rt_audit_objects_2 ON
      wb_rt_audit_objects(object_uoid, audit_object_id DESC, audit_unit_id);
    CREATE INDEX colin_wb_rt_audit_objects_3 ON
      wb_rt_audit_objects(parent_audit_object_id, audit_object_id);The reason this helps is that now the indexes contain all the data needed in the slow queries obviating the need to go to the tables, which in these cases are particularly expensive as the tables contain large LOB columns.
    It is very interesting to see that two of the indexes can replace existing indexes that were added in a recent patch!
    For the wb_rt_warehouse_objects table I've implemented an alternative solution, and that is to move the storage of 2 of the 3 CLOBs out-of-row:
    ALTER TABLE wb_rt_warehouse_objects MOVE
      TABLESPACE <xxx>
      LOB (creation_script)
      STORE AS (
        TABLESPACE <xxx>
        DISABLE STORAGE IN ROW
      LOB (client_info)
      STORE AS (
        TABLESPACE <xxx>
        DISABLE STORAGE IN ROW
    ;where you should replace <xxx> with the tablespaces of your choice.
    I hope this will help some of you with large repositories.
    Cheers,
    Colin

    Hi David,
    I hope these improvements can be implemented! ;-)
    We have a runtime repository with some 2300 deployed tables and an equivalent number of mappings.
    Total number of rows in wb_rt_warehouse_objects is more than 40,000
    I used an SQL trace and tkprof to identify some high cost queries -- individually these queries perform quite reasonably but when executed many times (as happens when starting the Control Center) these can cost many tens of extra seconds.
    If you're interested I can send you
    * traces
    * tkprofs
    * the slow queries
    and then you can see the before and after explain plans and why this works.
    Please contact me at colinthart at the Google mail service :-)
    Cheers,
    Colin

  • Multiple runtime armature scenes

    I am having multiple armatures that allow the user to interact with it. when I test the scene (2) with the armature it works fine but when i am in scene (1) and go to scene two it does not move? here is the following code for my scene 1 -
    stop();
    scene2_btn.addEventListener (MouseEvent.CLICK, onscene2_btnClick);
    function onscene2_btnClick (evtObject:MouseEvent) :void {
    gotoAndStop(1, "Scene 2");
    and here is my code for scene 2 -
    import fl.ik.*;
    var elephant:IKArmature=IKManager.getArmatureByName("elephant");
    var foot:IKBone=elephant.getBoneByName("foot");
    var footEffector:IKJoint=foot.tailJoint;
    var elephantPos:Point=footEffector.position;
    var elephantMover:IKMover=new IKMover(footEffector,elephantPos);
    home_btn.addEventListener (MouseEvent.CLICK, onhome_btnClick);
    function onhome_btnClick (evtObject:MouseEvent) :void {
    gotoAndStop(1, "Scene 1");
    stop() ;
    Any suggestions?

    You must wait between the 2 executions:Process p = Runtime.getRuntime().exec(
              "cmd /c copy \"" +path2 + "\" \""+ path +"\\\" /Y");
    p.waitFor();
    Runtime.getRuntime().exec("cmd /c attrib "+path+"\\* +R");Regards

  • Policy Enforcement issues in AM 7.1 with multiple user repositories

    Hello,
    We have a scenario where we need to authenticate and authorize both ADAM and Sun Directory Server users into a web application through the same realm. The realm is setup with 2 identity repositories - one for ADAM and one for DS - both of type LDAP v3 Repo. Authentication into AM console through the ?realm=name parameter works fine in this setup for users from both repositories.
    However, when we try to authenticate users into the protected web application as an AD/DS user, policy enforcement is not deterministic. Policy Agent starts allowing URL access to DENIED users also. Is this a known issue/bug with Sun Access Manager 7.1?
    The policy agents in our setup are Apache, Tomcat and IIS 6.
    Thanks,
    Srinivas

    Please provide more information. If I understand you correctly, you have a realm with 2 LDAP Auth modules configured. Are these part of an Auth Chain? What does that Chain look like? Both Required? Sufficient?
    What does your URL policy look like?
    Have you made sure AM Agent is not set to SSO_ONLY?
    What do you mean by "Policy Agent starts allowing URL access to DENIED users also"? You see "DENIED" in a log file but the user gets through, or you are just reporting the behavior?
    Thanks,
    Eric

Maybe you are looking for