IKM and staging area

Hi,
I'm exstracting data from a sybase table and I need to store these data in a temporary table in an oracle db. The ODI is installed on the oracle db.
So I imported the source table from sybase datasources, I created the temporary table but in the flow tab I can't select the IKM module (my integration modules are IKM SQL to File Append and IKM SQL to SQL Append). Can someone help me?
Thanks
Giovanni

Giovanni
I think you need to import some KMs into your project. For moving data from Sybase to Oracle, there are a number of KMs which may be suitable, LKM SQL to Oracle, and IKM Oracle Incremental Update or IKM SQL Control Append, depending on your preferences.
To import KMs into a project, right mouse button on the project Import->Knowledge Modules, and navigate to the <ODI_HOME>/oracledi/impexp directory.
Depending on the volumes of data, I might suggest that you might want to transfer bulk, using an LKM which extracts using BCP and loads into Oracle with External Tables or SQL*LOader.

Similar Messages

  • Door and staging area not determined automaticaly in IBD

    Dear All ,
    Kindly guide as Door, staging area  determination is not happening automatically after inbound delivery creation.
    currently assignment is being carried out manually , Attached screen shots for your kind perusal.
    Thanks
    Jinoy

    Please do the following
    Define Staging Area and Door Determination Groups
    SPRO ® EWM ® Master Data ® Staging Areas ® Define Staging Area and Door Determination Groups
    SPRO ® EWM ® Master Data ® Warehouse Door ® Assign Staging Area/Door Determination Group to Door
    SPRO ® EWM ® Master Data ® Warehouse Door ® Assign Staging Area to Warehouse Door
    SAP menuà EWMà Settingsà Shipping and Receivingà Access Sequence to Staging Areas and Door Determination)
    SAP menuà EWMà Settingsà Shipping and Receivingà Staging Area and Door Determination (Inbound)

  • Setting staging area in VA01

    Hello,
    I would like to set an indication to the sales order in ERP for the purpose to determine the right staging area in EWM:
    [EWM] Storage control by alternative staging area according to sales order
    But I dont found the field "staging area/door determination group" in the sales order: VA01->TA
    Features
    In order that the system can perform staging area and door determination in the background, you must define determination rules. When doing this, you first specify which values the system is to compare with the values in the delivery:
    ●      Inbound delivery process: Warehouse process type and staging area/door determination groups
    ●      Outbound delivery process: Routes, departure calendar, staging area/door determination groups, and destination sequence numbers
    You then define which of the values named under u201CUseu201D are to be determined by the system.
    http://help.sap.com/saphelp_scm70/helpdata/EN/52/08b240ac052817e10000000a1550b0/frameset.htm
    Thanks in advance!
    Best regards,
    Laura

    Hi Laura,
    In order that the system can perform staging area and door determination in the background,
    Regards
    Seegal

  • Work Schema Vs Staging Area

    Can anybody explain what's the difference between Work Schema and Staging Area in ODI.
    Work schema we specify while creating Physical schema in Topology manager.
    Is Staging area same as work schema?
    Thanks

    Hi,
    you have 3 step
    1-source
    2-staging area
    3-target
    in any mapping (designer9 you may choose in which step execute the operation (according to step technology). The work schema is the place in which you execute operation of this step. So, if you say to
    LOGICAL : MY_SRC_DB
    schema: ora_schema
    work_schema: ora_w_schema
    LOGICAL : MY_TARGET_DB
    schema: ora_t_schema
    work_schema: ora_wt_schema
    you could say to odi having staging area different from target (for example SUNOPSIS MEMORY ENGINE)
    the operation on source would be executed on ora_w_schema
    the operation on staging would be executed on SUNOPSIS_MEMORY ENGINE's work
    the operation on target would be executed on ora_wt_schema
    At Oracle University teacher said me to put work=schema. You may fill in them different only for security issue (or performance)
    i hope to be usefull, my english is not so good;P
    Decaxd

  • How to print staging areas and doors on the pick doc. ?

    Dear experts!
    Thank you for your attention!
    In our system, we use Lean WM.
    We know staging areas and doors can aslo be printed on the pick doc.  How to do that?
    Best regard!
    Tangdark

    I'm not a WM expert, but am pretty sure nothing special is required for that. If the fields, where this information is stored, are used by the output processing program and the data is passed to the form and then printed by the form, there should be no problem. If data is there, but it's not printed, then you might need to adjust the output program and/or form.
    You might want at least to try it first and use Search whenever possible, then come back with more specific questions, if necessary.

  • Staging area error and universal installer does not run

    Everything was ok. I installed Oracle 9i r 2, AS 9.0.2, iFS 9.0.2.
    Then I uninstall AS and iFS. But AS folder remains there (with inventory,contentsXML.. folder inside), even if I deleted it, when I tried to install AS again I get the error staging area error, and the folder appears again.
    Another thing is that in oracle universal installer the installed and deinstall products options do not do anything. I only can select the install option
    Did I do something wrong during the AS uninstall?
    What Can I do now?
    Thanks for your help,

    Try looking here:
    http://www.thomasfly.com/Oranux/#Step-by-step
    follow these steps/configs and the install will go quite nice!

  • Staging area and target area

    hi..friends.
    should staging area and target area be same or different???
    if same what are the advantages and dis-advantages???
    and if not same what are the advantages and dis-advantages????
    I want your help..
    Thanks.

    Staging area is the place where transformation takes place.
    Basically c$,I$ tables gets created at this place and once processing is done , the same gets dropped .
    By defalut staging area and traget area are the same . But most of the DBA does not like to have the temp tables created at the target as this cause dbms performance, maintance issue in long term.
    Instead you can have a dedicated schema created just for staging and use the same in your interface.
    Plus when your target is non dbms then you need to go for a dedicated staging area which can be a separate schema in your database or it could be in memory schema. You will find performance issue if you are using in memory schema as your staging area in case the data volume increase.
    Thanks,
    Sutirtha

  • Staging area and base are in different schema/tablespace

    Please can someone give me some advantages and disadvantages to keep staging tables and base tables in same schema. For eg we have staging area where we daily truncate staging table, load in the stg table and do transformation process. Once done we will move the staging table data to base tables. Base tables sizes are huge volume like 6 to 8 million rows as there is no purging done.
    I want to suggest to my team that we should keep them in separate schemas as I understand it will be good from I/O point.
    Is there any other reason to keep staging and base tables in separate schema/tablespace.

    Hi,
    Definitely I agree with previous answers. You wrote that staging area, transformation etc.. So I think it's a datawarehouse. Staging and base tables should be stored in different data files also in different harddrives. During the ETL task there can be high load on the Disk subsystem. Storing them in different schemas is another subject which is not related with the disk performance.
    When it comes to blocksize of the datafile, there is a approach like this:
    If the database is used for OLTP systems, it would be good idea to setup smaller size blocks. But when we're talking about a datawarehouse, it's highly recommended to use larger block sizes like 16KB or 32KB. This setting has an advantage related to reading, accessing data blocks.
    Regards,
    Cuneyt

  • Staging area and Target area in ODI

    Hii...experts.
    How Staging area is different from target area and same as target area?? what are their benefits and drawbacks in both??
    Please suggest me with some pictorial representation..
    Thanks

    Hi SRK
    I think you'll find your answer in this old white paper from oracle. The new version of the best practices are much smaller :/.
    http://www.oracle.com/technetwork/middleware/data-integrator/overview/odi-bestpractices-datawarehouse-whi-129686.pdf
    Page 87-95.
    Hope it helps.
    Regards,
    Jerome
    ps : p79-84 are interesting too

  • Automatically determine the staging area and door

    Hello Gurus,
            How to automatically determine the staging area and door ? and where to configure it?
    thanks very much!

    Hi zhang
    Material staging areas and doors are related to Warehouse management.
    First of all assign WM to your storage location
    Doors
    This is the place where the goods come to the warehouse  or  leave  from the warehouse
    The use of doors is to pick and  putaway  process in the warehouse.
    You can also assign the doors to the staging areas as goods receiving and shipping points
    Material staging areas
    This is an organizational unit that is assigned to the warehouse number. It is used to organize the goods flow in the warehouse
    The use of the material staging areas is that , they are used for interim storage of goods in the warehouse
    Staging areas can be defined for other purposes like goods receipt and goods issues
    Regards
    Srinath

  • Maintaining the structure of a SQL Server staging area and dwh aligned with the Oracle data source

    Hi,
    I'm working in a context where the data source system, in Oracle, is a continuos work in progress. Each 1-2-3 weeks the data source system in the prod environment is updated with new tables or updated table (with new columns or altered columns). So, it is
    important to apply in a rapid manner the related changes in the data structure of the SQL Server staging area and dwh.
    The issues to solve are:
    a. maintaining SQL Server data structure of the staging area aligned with the data structure of the Oracle data source;
    b. maintaing SQL Server data structure of the staging area aligned with the data structure of the SQL Server staging area.
    In order to solve these issues it could be useful to think to an authomatic manner to alert when a data structure change occurs and a simple manner to apply the changes on SQL Server data structure.
    Any suggests, please? Many thanks

    We use Oracle CDC service in SQLServer. It has a flag to indicate the schema changes happening at the Oracle end. We track the schema changes using it and then apply changes to sqlserver side. And regarding automation you can use Biml as suggested or .NET
    scripts inside script task.
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Staging area different from target - which KM???

    Hi,
    I need to transfer data from CSV to DB (only new inserts operation)
    I am working the following KM's
    LKM File to SQL
    IKM SQL Control Append
    It's working fine. However now i need to keep the staging area (where C$, I$ etc table are created) in a separate schema.
    I have created a diff schema for staging area and selected in the interface "Staging area different from target"
    However not sure of which KM's to use.
    Please let me know how to achieve this.
    Thanks,
    Rosh

    Hi
    1st thing you have to give the workschema for temp tables when creating physical schema in dataserver for target.
    Then you have to select the workschema in overview of interface as "staging different from target".
    After doing this when you will use predefined KM for the interface it will create temp tables in workschema.
    Now suppose you are not giving the workschma at the time of creating physical schema and you have selected "staging different than target" in interface.Here your C$ table will be created in your workschema but I$ table that is used by IKM is going to be created on target schema.So for this again you have change the IKM KM i.e. where to create I$ table (wokrschema) by selecting the corresponding logical schema.
    So its better you give the workschema at the time of creating physical schema.
    Here is the query to give privilege by the sys_dba
    Grant create any table to ODI_TEMP.
    Hope you got it
    (Please mark the answer as correct or helpful and close the thread)
    Thanks

  • Staging Area Schema

    My source and target table is same and I am trying to update certain column in table XXX, I have set staging area different then target and specify the staging schema where I do have the create table prevelige but when I run this interface its trying to create temp table in target schema where I do not have preveilege to create table.Any clue ...?
    In the interface I have checked all my mapping process is in staging area not source or target.
    Any clue ...?
    Thanks

    HI,
    It depends on the KM that you are using... If you are using a IKM Incremental Update then the process will create a temp table at target because it needs it to make the PK comparation.
    My suggestions to work around it:
    1) if your ETL allows, work with the IKM Control Append
    2) If you need of a Incremental Update ELT just point the "Work Area" at the target Physical Schema to the "Staging Area" Schema, change the Database connection user to the user of Staging Area and give him the necessary grants at the tables of the target schema (insert and update i imagine),
    Just to be sure, are you using Oracle DB as source, staging and target?

  • Lookup issue when staging area diff from target

    Hi,
    I am using staging area different from target (csv file to database)
    Everything is working fine the source data is moved to target. The interface runs suiceessfuly.
    Now i want to add a lookup during transformation using a lookup table.
    When i do that using lookups in quick edit section, i am getting an error.
    When i run the interface, the C$ gets created in staging area - that is correct.
    However when inserting from staging to target, now the ODI searches for the C$ table in target area instead of the staging..
    Please help.
    Thanks,
    Rosh

    Hi
    1st thing you have to give the workschema for temp tables when creating physical schema in dataserver for target.
    Then you have to select the workschema in overview of interface as "staging different from target".
    After doing this when you will use predefined KM for the interface it will create temp tables in workschema.
    Now suppose you are not giving the workschma at the time of creating physical schema and you have selected "staging different than target" in interface.Here your C$ table will be created in your workschema but I$ table that is used by IKM is going to be created on target schema.So for this again you have change the IKM KM i.e. where to create I$ table (wokrschema) by selecting the corresponding logical schema.
    So its better you give the workschema at the time of creating physical schema.
    Here is the query to give privilege by the sys_dba
    Grant create any table to ODI_TEMP.
    Hope you got it
    (Please mark the answer as correct or helpful and close the thread)
    Thanks

  • Staging area on source in Oracle

    Hi,
    My source and target, both are Oracle DBs.
    a) I created one interface with STAGING AREA ON TARGET. For this I used LKM SQL to SQL and IKM SQL Incremental Update.
    Its working fine and all the work tables, flow table etc are gettting created in the
    Work Schema (ie. ODI_TRG) I have given while defining physical schema of my target.
    I want to try with staging area on source....
    b) I checked the "Staging area different from Target" option and selected the logical schema of the source in the Definitions tab of my interface.
    In the corresponding physical schema, Work Schema I gave is ODI_SRC.
    Now I expected all the work tables, flow tables etc to be created ODI_SRC. But still they are getting created in ODI_TRG!!! Why???
    But finally to insert/update the target table, its trying to read the flow table from ODI_SRC, even though it created the flow table in ODI_TRG!!!!
    And as a result its failing with this error code...
    942 : 42000 : java.sql.SQLException: ORA-00942: table or view does not exist
    Please clarify.

    I think you didn't change your KM.
    Step1: import the "IKM SQL to SQL Append" into your project
    Step2: In your interface, on the definition table, select the "Staging Area Different From Target" checkbox, and select the schema of your source data in the drop-down list box.
    Step3: go to the flow tab, and select the target, and select the IKM SQL to SQL Append.
    Step4: Execute.
    Refer this thread what KM to change.
    Optimizing the KM

Maybe you are looking for