Import WB_RT_GET_JOB_METRICS procedure into OWB

How do I import this procedure WB_RT_GET_JOB_METRICS into my mapping.

You can get the public transformations. After you have opened your map, you can follow this path to get to the procedure: explorer in upper left pannel --> Pulic transformation --> Pre-defined --> control_center --> WB_RT_GET_JOB_METRICS . Then you can drap it to your map.

Similar Messages

  • Importing packages/procedures into OWB

    Is it possible to import packages or procedures into OWB that are stored on a different database?
    I want to call a procedure in a mapping that is stored on a different database. I can only import tables and views (as data source ) from other databases.
    I can only import PL/SQL packages into OWB if they're stored in the current database.
    Does anybody have a solution?
    Regards,
    Maurice

    Maurice,
    Essentially the import uses a dblink, so you have the option to specify the dblink to another place and you should be able to see/import that pl/sql.
    The most elegant and prefered way however is to import the pl/sql into the public transformations node (I'm using OWB 9.0.4). This is a bucket that holds sharable pl/sql and seems to address the need for you.
    Here again you create the dblink and point at the remote db schema that owns the pl/sql.
    Hope this helps,
    Jean-Pierre

  • Importing a package into OWB repository.

    Hi,
    there is a package existing in my OWB repository.
    Package ABC
    Procedure PQR(pram1 varchar2,param2 varchar2)
    now i have modified this package in my target schema, an extra parameter is added to the procedure PQR.
    Procedure PQR(pram1 varchar2,param2 varchar2,param3 number).
    now when I re import this package to my OWB repository module. it shows both versions of the procedures.
    Package ABC
    PQR(pram1 varchar2,param2 varchar2)
    PQR(pram1 varchar2,param2 varchar2,param3 number)
    PQR(pram1 varchar2,param2 varchar2) is still vsible in OWB repository though it is replaced with PQR(pram1 varchar2,param2 varchar2,param3 number) in target schema.
    Is there any way I can replace the old version of procedure with the new version in OWB repository.
    Regards
    RD_RBS

    Hi
    Standard approach to be followed for any object modification
    1. If you have created your package from OWB and deployed it into your DB, always do it that way i.e. Design center -->DB . Do not make any modifications on DB level and import in back to your Design center. OWB manages Ids for all objects on the repository and this will confuse it. That is why you see two versions of the same package . Any modifications should be done on Design center level and then do a replace on the package from control center
    2. If an object (package or procedure) is created on DB directly and is imported into design center, follow the same norm everytime you make any changes to that object. The status of that object will appear as "New" or "Not deployed" on control center but that is fine because OWB has no ID on its repository to maintain this information.
    3. If you need to rename any object already deployed from OWB, always drop it first, then rename it and then deploy it. That way OWB will maintain the name and ID on its end and not get confused.
    4. For your case, you can drop the older version of the package from OWB, delete the one imported from Database into OWB, make the changes on OWB level (adding parameter etc) and then redeploy the same package as replace from control center.
    Hope these tips help
    birdy

  • Importing Database Package into OWB changes position of parameters .. Nasty

    Hi all,
    Anyone else having the same problem ? Any solutions ? Or is this a bug.
    When a package is imported from a DB schema, OWB kindly changes the order in which the parameters are listed.
    The effect is that any mapping using the procedure or function will not have the correct parameters passed to.
    For example.
    DB_Test_proc
    io_name_in in out varhar2,
    o_clean_name_out out varchar2
    After importing in OWB the parameter positions are reversed .... very nasty.
    Anyone can help or do I raise a bug ?
    Regards
    Nick

    Hi Borkur,
    Dropping and re-importing the package would work well (works for another module) but this is a package whose procedures and functions are heavily referenced in several mappings and process flows (supports the custom job management). So, I would be forced to re-synchronize them all which I want to avoid. The other way would be to modify the package manually (only the signature is needed not the code since I will not deploy it from OWB, in fact, I deployed it from Oracle Designer !!!). But OWB Paris doesn't allow this. Once imported, always imported. You can modify imported tables, procedures, functions but not packages. Or is there a way ???
    regards
    Thomas

  • Import excel file into owb automatically, is it possible?

    Is it possible to load several excel files in owb automatically?
    I want to avoid the follow situation...
    I have like 100 excel files I have to create 100 system dsn each pointing to one excel file.
    Is it possible?
    Thanks

    The forum is how to integrate foreign databases into an oracle database using gateway. From the provided description you're trying to import an Excel file directly into OWB. OWB has its own mechanism to import these files , so better post your issue in the OWB forum:
    Warehouse Builder

  • Importing existing dimensions into OWB

    Does any body know how to import an existing Dimension, created in an Oracle database into OWB so that the dimension definition appears under the dimension tab.

    Hi,
    I think you can't import a dimension from data base.you have to create throught OWB.
    Regards
    naren

  • Importing Stored procedures into pre-made report

    <p>Hello all,</p><p>i&#39;v got some trouble with some pre-made reports that we wish to start using with embedded java engine.</p><p>Reports are stored procedure based and the built-in connection is ODBC.</p><p>What I&#39;d like to do is to change the datasource to JDBC datasource and run all queryes through there. Is is possible with CR4E ? </p><p> </p><p>Best regards,</p><p>Henrix</p>

    Hi Henrix,
    This is possible, however there is a known issue with the Database Explorer that ships with CR4E in that Stored Procs are not displayed. You can check out the following forum thread if you want more information on this specific issue:
    *http://diamond.businessobjects.com/node/520*
    This issue generally affects creating new reports against Stored Procedures, but it will affect you as well as it will prevent you from using the UI to switch from one database driver to another, Primarily because the Stored Procs won't be displayed in the destination table that you wish to switch to.
    To get around this we will need to create a simple java routine to switch the tables via code. The attached code below will go through all of the tables in the main report and the subreport and assign the new JDBC connection information:
    package com.businessobjects.samples;
    import java.io.IOException;
    import com.crystaldecisions.sdk.occa.report.application.OpenReportOptions;
    import com.crystaldecisions.sdk.occa.report.application.ReportClientDocument;
    import com.crystaldecisions.sdk.occa.report.data.IConnectionInfo;
    import com.crystaldecisions.sdk.occa.report.data.ITable;
    import com.crystaldecisions.sdk.occa.report.data.Tables;
    import com.crystaldecisions.sdk.occa.report.lib.IStrings;
    import com.crystaldecisions.sdk.occa.report.lib.PropertyBag;
    import com.crystaldecisions.sdk.occa.report.lib.ReportSDKException;
    public class ChangeDatasource {
    Â Â Â /**
    Â Â Â * @param args
    Â Â Â * @throws ReportSDKException
    Â Â Â * @throws IOException
    Â Â Â */
    Â Â Â public static void main(String[] args) throws ReportSDKException, IOException {
    Â Â Â Â Â Â //change the next set of variables to match your requirements
    Â Â Â Â Â Â String connectionURL = "jdbc:derby:classpath:/Xtreme";
    Â Â Â Â Â Â String driverName = "org.apache.derby.jdbc.EmbeddedDriver";
    Â Â Â Â Â Â String DB_USER_NAME="bobj";
    Â Â Â Â Â Â String DB_PASSWORD = "bobj";
    Â Â Â Â Â Â String reportName = "MyODBCReport.rpt";
    Â Â Â Â Â Â
    Â Â Â Â Â Â //the next few variables should not need to be changed for JDBC connections
    Â Â Â Â Â Â String SERVER_TYPE = "JDBC (JNDI)";
    Â Â Â Â Â Â String USE_JDBC = "true";
    Â Â Â Â Â Â String DATABASE_DLL = "crdb_jdbc.dll";
    Â Â Â Â Â Â String CONNECTION_URL = connectionURL;
    Â Â Â Â Â Â String DATABASE_CLASS_NAME = driverName;
    Â Â Â Â Â Â
    Â Â Â Â Â Â ReportClientDocument clientDoc = new ReportClientDocument();
    Â Â Â Â Â Â clientDoc.setReportAppServer("inproc:jrc");
    Â Â Â Â Â Â
    Â Â Â Â Â Â // Open report
    Â Â Â Â Â Â clientDoc.open(reportName, OpenReportOptions._openAsReadOnly);
    Â Â Â Â Â Â
    Â Â Â Â Â Â PropertyBag propertyBag = null;
    Â Â Â Â Â Â IConnectionInfo connectionInfo = null;
    Â Â Â Â Â Â ITable origTable = null;
    Â Â Â Â Â Â ITable newTable = null;
    Â Â Â Â Â Â Tables tables = null;
    Â Â Â Â Â Â
    Â Â Â Â Â Â //this next routine iterates through all the tables in the main report
    Â Â Â Â Â Â //if you need to make specific changes to an individual table you can
    Â Â Â Â Â Â //evaluate the name of the current table and change the code accordingly
    Â Â Â Â Â Â tables = clientDoc.getDatabaseController().getDatabase().getTables();
            for(int i = 0;i < tables.size();i+){<br />            origTable = tables.getTable(i);<br />            newTable = (ITable)origTable.clone(true);<br />            newTable.setQualifiedName(origTable.getAlias());<br />            connectionInfo = newTable.getConnectionInfo();<br />            <br />            // Set new table connection property attributes<br />            propertyBag = new PropertyBag();<br /><br />            // Overwrite any existing properties with updated values<br />            propertyBag.put("Server Type", SERVER_TYPE);<br />            propertyBag.put("Use JDBC", USE_JDBC);<br />            propertyBag.put("Database DLL",DATABASE_DLL );<br />            propertyBag.put("Connection URL", CONNECTION_URL);<br />            propertyBag.put("Database Class Name", DATABASE_CLASS_NAME);<br />            connectionInfo.setAttributes(propertyBag);<br /><br />            connectionInfo.setUserName(DB_USER_NAME);<br />            connectionInfo.setPassword(DB_PASSWORD);<br /><br />            // Update the table information<br />            clientDoc.getDatabaseController().setTableLocation(origTable, newTable);            <br />        }<br />    <br />    // Next loop through all the subreports and pass in the same<br />    // information. You may consider creating a separate method which accepts different settings<br />        IStrings subNames = clientDoc.getSubreportController().getSubreportNames();<br />        for (int subNum=0;subNum<subNames.size();subNum) {<br />            tables = clientDoc.getSubreportController().getSubreport(subNames.getString(subNum)).getDatabaseController().getDatabase().getTables();<br />            for(int i = 0;i < tables.size();i+){
    Â Â Â Â Â Â Â Â Â Â Â Â origTable = tables.getTable(i);
    Â Â Â Â Â Â Â Â Â Â Â Â newTable = (ITable)origTable.clone(true);
    Â Â Â Â Â Â Â Â Â Â Â Â newTable.setQualifiedName(origTable.getAlias());
    Â Â Â Â Â Â Â Â Â Â Â Â connectionInfo = newTable.getConnectionInfo();
    Â Â Â Â Â Â Â Â Â Â Â Â // Set new table connection property attributes
    Â Â Â Â Â Â Â Â Â Â Â Â propertyBag = new PropertyBag();
    Â Â Â Â Â Â Â Â Â Â Â Â // Overwrite any existing properties with updated values
    Â Â Â Â Â Â Â Â Â Â Â Â propertyBag.put("Server Type", SERVER_TYPE);
    Â Â Â Â Â Â Â Â Â Â Â Â propertyBag.put("Use JDBC", USE_JDBC);
    Â Â Â Â Â
    Â Â Â Â Â Â Â propertyBag.put("Database DLL",DATABASE_DLL );
    Â Â Â Â Â Â Â Â Â Â Â Â propertyBag.put("Connection URL", CONNECTION_URL);
    Â Â Â Â Â Â Â Â Â Â Â Â propertyBag.put("Database Class Name", DATABASE_CLASS_NAME);
    Â Â Â Â Â Â Â Â Â Â Â Â connectionInfo.setAttributes(propertyBag);
    Â Â Â Â Â Â Â Â Â Â Â Â connectionInfo.setUserName(DB_USER_NAME);
    Â Â Â Â Â Â Â Â Â Â Â Â connectionInfo.setPassword(DB_PASSWORD);
    Â Â Â Â Â Â Â Â Â Â Â Â // Update the table information
    Â Â Â Â Â Â Â Â Â Â Â Â clientDoc.getSubreportController().getSubreport(subNames.getString(subNum)).getDatabaseController().setTableLocation(origTable, newTable);
    Â Â Â Â Â Â Â Â Â Â Â Â }
    Â Â Â Â Â Â Â Â Â }
    Â Â Â Â Â Â
    Â Â Â Â Â Â //save the report with the changes
    Â Â Â Â Â Â clientDoc.save();
    Â Â Â
    Â Â Â }
    Â Â Â
    Â This code is pretty generic, however you can modify it to be specific for each report if necessary.
    Regards,
    Sean Johnson (CR4E Product Manager)
    Rate this plugin @ Eclipse Plugin Central          </p>

  • Import PLSQL procedure or package into OWB

    Here's a simple question. In schema X, I created a procedure and a package. If I try to import them into OWB (10g R2), connecting to schema X and clicking on transformations and "import" doesn't show the newly created objects for import. I tried granting execute to OWB10GR2, but no luck. Closed and re-started design center with no luck.
    Creating a procedure in Design Center and then deploying it to schema X works and is a workaround, but it's awkward to write code there (compile is deploy, which takes a lot longer than normal compile).
    What am I missing so that I can't import a procedure into design center?

    OK, so I'm going to answer my own question. Maybe someone else can use the info...
    The problem is that I have development and production configurations.
    Procedure or package defined only in one (dev or prod) schema won't show up on the import list. Apparently, in order to import the object into OWB you need to define it in all environments. Otherwise it doesn't show up on the import list.

  • Argument Order Reversed Importing Package into OWB

    I'm having a problem importing Packages into OWB. It recognizes the Functions contained in the Package, however the order of the arguments for each Function are reversed after I complete the import into OWB. This causes execution of the mapping to fail... Additionally, after importing into OWB, OWB doesn't seem to recognize any optional parameters or default values in the signature of the Function. I must be doing something wrong... Can anyone help...
    Thanks
    Alan

    Hi
    Standard approach to be followed for any object modification
    1. If you have created your package from OWB and deployed it into your DB, always do it that way i.e. Design center -->DB . Do not make any modifications on DB level and import in back to your Design center. OWB manages Ids for all objects on the repository and this will confuse it. That is why you see two versions of the same package . Any modifications should be done on Design center level and then do a replace on the package from control center
    2. If an object (package or procedure) is created on DB directly and is imported into design center, follow the same norm everytime you make any changes to that object. The status of that object will appear as "New" or "Not deployed" on control center but that is fine because OWB has no ID on its repository to maintain this information.
    3. If you need to rename any object already deployed from OWB, always drop it first, then rename it and then deploy it. That way OWB will maintain the name and ID on its end and not get confused.
    4. For your case, you can drop the older version of the package from OWB, delete the one imported from Database into OWB, make the changes on OWB level (adding parameter etc) and then redeploy the same package as replace from control center.
    Hope these tips help
    birdy

  • Geting an error trying to import a data file into OWB repository

    Hi,
    We're using OWB 11.1.0.7.0
    I'm trying to import a new data file and I'm getting an error.
    When I go to The Project/Files/ I right click on the module I want to add the files to,
    I get a 'Wizard' titled 'Welcome to the Import Metadata Wizard'.
    I click next.
    I get the 'Filter Information' screen that asks if I want to select 'All Data Files' or a specific file.
    I pick 'All Data Files' and click 'next'.
    I get the 'Object Selection' screen that has a left and right panel. The left side is titled 'Available' and the right side is titled Selected.
    The 'Available' panel had the directory in Linux (/etl/datafeeds/dev) where our data files are stored with a plus sign next to it.
    When I click the plus sign, I get an error message that says:
    API2836: Directory
    /etl/datafeeds/dev does not exist.Has anyone seen this? What is the work around? Is it a bug? How do I import a data file into OWB if this isn't the way to do it?
    Thanks,

    Hi, is there any obligation to use import wizard?
    can you use right click and import view/table?
    Ugur MIHCI
    www.ifslibrary.com

  • Dynamic import of metadata in owb?

    hello,
    I have to create a data warehouse in an Oracle database 11gR1, the production system is based on Oracle 9.2.0.1, to capture data changes I have to use synchronous cdc because the asynchronous mode requires at least version 9.2.0.6
    in synchronous mode I must generate views each time I want to capture the changes but in owb 11gR1 I can not import views in dynamic mode
    what can you suggest to me in this case?
    thank you
    tarek

    That's unfortunate.
    You'll probably have to write some PL/SQL that does one of two things. First, you could us a synonym to pull the view into OWB. You'll have to use some PL/SQL that drops and recreates the synonym every time you extend the window, to have the synonym point to the new name of the change view. You could do the same thing with a view if you are more comfortable with using a view. One of the parameters passed to the procedure would be the dynamic change view.
    The other thing you could do is have a PL/SQL procedure that selects all the rows out of the change view and inserts them to a regular staging table. Similar to the procedure above, you could pass the dynamic name of the change view but the staging table would always be constant. That way it could be brought into OWB and used successfully.
    Stewart Bryson

  • Error API0259 while Importing Processflow in to owb 11g

    Hi All,
    I am using owb 11.1.0.7.0. I am getting the following error while importing the process flow into owb (the mdl dump was taken from owb 10gR2)
    error: API0259: The object cannot be edited in Read-Only mode.
    Can any body please tell me the solution. Its urgent.
    Thanks in advance,
    Siva

    Hi Sutirtha,
    Thanks for u r reply, the problem was solved. What I was doing is , trying to import only one process flow which is using as sub process in other process flow.thats giving me the error.
    So, I have deleted all the process flows and imported whole process flow package in one go. That solved the problem.
    Regards,
    Siva

  • Error while importing MS project into cProject

    Hi
    I am getting the below error while importing MS project client file or XML file into cProjects.
    dpr_shared087
    Logon language becomes original language
    Message no. DPR_SHARED087
    Diagnosis
    The logon language is defined as a possible text language in Customizing for Collaboration Projects under Specify Text Languages. Therefore, it is valid.
    System Response
    The logon language becomes the original language of the new object that was created.
    Kindly suggest what configuration data if any is missing.
    Regards
    Srikrishna

    Hi
    I am getting the below error while importing MS project into cProject.
    Error occurred when importing from Microsoft Project
    Message no. DPR_UI_BSP116
    Diagnosis
    When a project is imported from Microsoft Project, the system generates an XML string during internal processing. A project is then created in cProjects from this string.
    The XML string contains errors because the values from Microsoft Project were transferred without verification.
    Procedure for System Administration
    Notify SAP or call the cProjects application with the "DebugMode=X" query string and carry out the import again.
    The XML string that was generated temporarily is then validated against the cProjects XML schema. The error message from the XML parser is then displayed in the popup.
    Kindly suggest, if the below steps for importing MS project is ok or not?
    step 1: Create project in MS project with tasks.
    step 2: Maintain maping fields of MSP in cProject configurat
    step 3: Import MPP file into cProject using "Import" button.
    step 4: I am getting the above error while importing the MPP file.
    Regards
    Srikrishna

  • Error While Importing Process Flow in OWB Repository.

    Hi All,
    OWB Config Details is as follows:
    Oracle 9i Warehouse Builder Client: 9.2.0.2.8
    Oracle 9i Warehouse Builder Repository: 9.2.0.2.0
    Following Error Message is displayed when i tried to import process flow from one OWB Repositoty to another OWB Repository.
    Warning at line 23: MDL1312: Referenced logical location with name <PF_STG_INC_LOC> and UOID <F3940F1D5EB84985E0340003BA0AF737> not found for PROCESSMODULE <SALES_INC>. Logical location not set for this module.
    Warning at line 28: MDL1320: PROCESS PF_C_C_CALLS_INC in STG_INC.SALES_INC.SAL_INC cannot be imported because referenced STANDALONEPROCEDURE
    FLSTG.PROC_GET_ETL_DATA_DATE does not exist.
    Warning at line 28: MDL1320: PROCESS PF_STG_CALL_CENTER_CALLS_INC in FLSTG_INC.SALES_INC.SAL_INC cannot be imported because referenced STANDALONEPROCEDURE
    FL_TRG_FLSTG.PROC_UPDATE_RECO_CTL does not exist.
    Informational: MDL1134: COMMIT issued at end of import data file.

    Hello, all the errors you've been given are related to missing objects.
    You should re-create/import the location for you process flows before importing the process flows themselves.
    Also verify that you have imported the procedures FLSTG.PROC_GET_ETL_DATA_DATE and FL_TRG_FLSTG.PROC_UPDATE_RECO_CTL because you use them in your process flows so you need them: OWB refuses to import a process flows if some objects are missing because it would break some links.
    In general process flows should be imported where you have all the other objects in the repository because they are the final step and they reference many other objects.
    Hope this helps - Antonio

  • Cannot import 2000 chars in OWB 9.0.4.

    I'm trying to import a flat file in EBCDIC format into OWB 904. It fails with the following message:
    "API2839 - The field definitions exceed the length of a fixed length record."
    The record length is 4050, with fixed length fields. When I enter the field lengths and then click Next, the error message appears.
    How can I get around this?
    Thanks,
    Carey

    Carey,
    It sounds like the length of each field when added together exceeds the value of the record length value. To confirm this, look at the field property sheet and the file property sheet to cross check that this is
    true.
    JP

Maybe you are looking for