Tune a mapping in ODI
How to tune a mapping in ODI ?
What is low level ELT and high level ELT in ODI?
What is Data migration in ODI ?
Thanks
How to tune a mapping in ODI ?
Choose between various knowledge modules (KMs) for loading and integration. Each one performs differently based on the source/target technology and the type of data that you're dealing with. Some perform better than others depending on the situation. Some KMs use set-based transactions, others use PL/SQL blocks to commit data in small batches.
Choose where ODI should execute each join/filter/transform. You can usually choose between the source, target or a separate staging area. What you choose here can influence how much source data you will extract and process.
The ODI KMs utilize temporary tables to perform the loading, checking and transform operations and will create the necessary indexes for performance. It will also analyse these tables as part of the flow to enable the DB engine to generate accurate execution plans.
Similar Messages
-
What is use of Active mapping in ODi interfaces?
hi,
What is use of active mapping in ODI interfaces ?
What are the advantages of using active mapping?
If active mapping is not used in ODI ,would it affect ODI code in some sense?
Thanks,
MaheshMaheshGx wrote:
hi,
What is use of active mapping in ODI interfaces ?This ask ODI to generate for for the mapped column . Other wise no code will be generated .
What are the advantages of using active mapping?If you want to generate code use active mapping .
If active mapping is not used in ODI ,would it affect ODI code in some sense?
It will not generate the code
Thanks,
Mahesh -
Hi guys!
I was wondering if ODI has a similar functionality to OWB pluggable mapping? If yes please tell me how ;)
With regards,
PsmakRHi,
You can find a great blog post about ODI User Functions @ http://blogs.oracle.com/dataintegration/2009/09/odi_user_functions_a_case_stud.html.
It should give you enough details, the User Functions are also covered in the ODI documentation.
Thanks,
Julien -
Regarding Performance Tunning of Mapping & Process Flow
Hi,
i have around 60-70 GB data in Target database.
i need do improve the performance of Mapping and Process flow.
i have used lookup transformation in mapping.
Plz give me some tips for improving performance of Process.
Thanks,Please go through a Performance Tuning Book for Oracle 10gR2.
Most importantly remember that in Oracle 10g, your performace of mappings can be increased manifold by following these steps:
1. Do not design a mapping wherein you load a table and then select from that table to load another table and so on. This is a bad design.
2. Keep mappings as simple as possible. In other words if a mapping is complicated in terms of joins or other operators then split the mapping into more than one parts.
3. Also check that all your source tables should be analyzed using DBMS_STATS. Ensuring this one single step can make your work very easy.
4. Put indexes where you find your predicate has a very high selectivity. Also keep in mind the column ordering of the index.
5. Use Set Based operation, since it is always a good idea to achieve the result by running one single query rather than a loop and multiple inserts.
6. Use APPEND PARALLEL hint while loading the target tables. This will not generate wny redo and save time
7. Please have a recheck while usng some performance intensive operators like UNION, DISTINCT and AGGREGATION
8. When using a sequence operator to load a large table, check that the sequence should be cached with some values.
9. When loading large data HASH JOINS are the most appropriate more often than not. So you can use USE_HASH as the hint for selecting from large tables.
10. Filter out as much unrequired data from a table as soon as possible in the mapping before doing multiple joins.
I am sure there are many more ... the above is just a random list that I could remember now. Please go through Oracle Performance Tuning Guide, Tom Kyte's Oracle Expert One on One. Knowledge of performance tuning will grow with experience. I am also learning each day !!!
Regards
AP -
How to use Variable in interface for Mapping in ODI 11g
Hi,
I want to use Variable 'Year' in interface mapping. how i can do that? I define a variable YEAR1 = '2001' and in interface i put #YEAR1 but it didn't work for me. is there any other way?
Example.
I m using 'Year' column in mapping and it is having different 3 constant values so i was think to define 3 variable Year1= '2001' & Year2= '2005' & Year3= '2010'.
In interface i just want to put variable name insted giving fix value.
regards
SherThank u
I m trying with all the options & when i create Variable i and set Default value to ''2001'
'#YEAR'
#YEAR
'#PROJECT_NAME.YEAR'
#PROJECT_NAM.YEAR
#PROJECT_NAME.'YEAR'
and setting to Stagging Area
But still it is not working out.
I m suing ODI11.1.1.3
is it any issue? -
How to create mapping diagrams in ODI?
Is there anything in ODI similar to informatica stencil for visio to create the mapping design diagrams to show the data flow and transformations in a visio schematic diagram?
Thanks for your feedback.thanks for your reply.
I am not looking to find where to design/create the map in ODI.
This is for a schematic representation of the mapping for design documentation to show how the map is going to look like with icons of various transformations involved in the map and connecting arrows to show the data flow in the map.
Something similar to this for informatica:
https://community.informatica.com/mpresources/screenshots/Replication.png -
Hi experts
i am new to ODI can anybody give explanation on what are the tunning methods for mapping in ODI?
thanks in advanceIt's a quite generic question.
Under my opinion you have 3 points of tuning.
1 - Source,staging, Target: decide where execute each mapping/filter/join and which is staging. This could make a speed up (less data, less time)
2 - Choose right KM and its option: If you are using an Oracle there are many KM, which is the correct for your need? Insert update, delete all, merge..
3 - Modify your KM: standard KM is a good start point. Personally i ALWAYS modify my KM, it's usefull, performing and quite funny.
Let me know -
DATE Format Error in ODI-11g(11.1.1.3)
I am using ETL transformations in ODI-11g. There's a dominant issue regarding date formattings when I map an ODI variable (storing date) with a TGT column(datatype=date) mappings.
In all the src-tgt mappings I am formatting the date by using TO_DATE() functions. But still getting the error:
"ORA-01830: date format picture ends before converting entire input string".
A point to Note: The same ETL in other env are ruuning fine but in my new dev env it's giving this date error.
I had checked with the DBA folks and they confirmed they set equal DATE settings in all the env.
The ODI Variable is defined as an "Alphanumeric".
Tx Used: #BUSINESS_CURRENT_DT=TO_DATE('Date','YYYY-MM-DD')
Require some urgent advice...Please let me knowHi,
W store name-value pair in the Control table from where we exctract our data. Both (param name and param value) are varchars.
Well this looks pretty strange in 11g! Here's what we found out...
If you are trying to retrieve a date variable by using TO_DATE() in the refresh query the ODI Java driver (JDK 1.6) would call java.sql.timestamp and gracefully attach HH:MI:SS.NS along with the date (YYYY-MM-DD HH:MI:SS.NS). My target ia a date always..!
So, when I do: TO_DATE('20101010','YYYY-MM-DD) in the refresh query ODI stores it as '2010-10-10 00:00:00.0'
For this the Load always fails as Oracle would not be able to interpret a timestamp by suing TO_DATE()
The Java driver does this damage. However, it may be wise to store as a timestamp rather as a date if in case u do a Data capture and want the exact time credentials.
Unfortunately not a req, as of now for us so I had to chop-off the timestamp..!
Let me know if you find any other details...
Thanks.! -
Need Help on complex XML loading into ODI
Hi,
I have a requirement in which i have to create xml mapping in ODI which should load 30 to 40 million message per day with file size of 30 MB. I have created xml connection in topology manager and have provided xsd path of unix server and it's working but when I try to reverse xml structure into Designer model then it gave me error " java.sql.SQLException: No DTD found and no XML file provided: the XML schema cannot be created". I have used below xml connection detail in topology manager.
JDBC Driver: com.sunopsis.jdbc.driver.xml.SnpsXmlDriver
jdbc:snps:xml?f=/odi_rep/sita_meg_bi/etl_metadata/&stypex.xsd&re=TYPEX&ro=true&case_sens=true
We are using 10.1.3.6 ODI version in this project.I have given below xsd and xml file format. FYI...we recevie multiple message with same strucutre in xml source file.
XSD File:
XML File :
<tns1:MessageTraceEvent xmlns_tns1="http://www.sita.aero/csbu/tools/v1/namespace" timeStamp="2011-07-13T00:01:09Z" priority="3" envelopeMessageID="xs-atl-xs2011-07-13t00:01:09.525:519160" mes
sageType="TYPEX" messageTotalSize="6506" systemID="bgtxjao">
<tns1:SitaIdentifiers>
<tns1:sitaUID>xPreg1D3RF2tGbF9iUPReA</tns1:sitaUID>
<tns1:TransactionID>dzA5Arb0QZyOOq9NqgrQ2Q</tns1:TransactionID>
</tns1:SitaIdentifiers>
<tns1:previousSitaIdentifiers>
<tns1:sitaUID>xPreg1D3RF2tGbF9iUPReA</tns1:sitaUID>
<tns1:TransactionID>zrL7EtGpTVSYeLpb+2W1NQ</tns1:TransactionID>
</tns1:previousSitaIdentifiers>
<tns1:Addresses>
<tns1:Originator>XS-ATL-XS</tns1:Originator>
<tns1:Recipient>AF-QVI-BP</tns1:Recipient>
<tns1:Recipient>AF-QVI-BP</tns1:Recipient>
</tns1:Addresses>
<tns1:RemoteSystem>
<tns1:Source>
<tns1:NodeID>AF-QVI-BP</tns1:NodeID>
<tns1:MiscData>BadgerID: XS-ATL-XS-1310515269-9.1</tns1:MiscData>
<tns1:isCustomer>false</tns1:isCustomer>
</tns1:Source>
</tns1:RemoteSystem>
<tns1:AdditionalData>
<tns1:TypeXData subject="No message"/>
</tns1:AdditionalData>
<tns1:Payload payloadType="MessageData">PHR4bWU6VFhNX0VudmVsb3BlIHhtbG5zOnR4bWU9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL2VudmVsb3BlIiB4bWxuczp0eG1zPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9zZXNzaW9
uIiB4bWxuczp0eG1tPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9tc2doZWFkZXIiIHhtbG5zOnR4bWM9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL2NvbW1hbmQiIHhtbG5zOnR4bXg9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL3hhdGFwIiB4bWxucz
p0eG1mPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9mYXVsdCIgeG1sbnM6dHhtcj0iaHR0cDovL3d3dy5pYXRhLm9yZy90eG0vcmVwb3J0IiB4bWxuczp0eG11PSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9hdXRoIiB4bWxuczp0eG1hPSJodHRwOi8vd
3d3LmlhdGEub3JnL3R4bS9hdHRh
pc3Rvcnk+PC93dHI6QklSX0RlbGF5ZWRCYWdSZWNvcmQ+CgkJPC90eG1lOlRYTV9QYXlsb2FkPgoJPC90eG1lOlRYTV9Cb2R5Pgo8L3R4bWU6VFhNX0VudmVsb3BlPgo=</tns1:Payload>
</tns1:MessageTraceEvent>
Edited by: user13544580 on Jul 18, 2011 6:27 AM<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2010 rel. 3 sp1 (http://www.altova.com) by SITA (SITA) -->
XSD File :
<xs:schema xmlns:tns1="http://www.sita.aero/csbu/tools/v1/namespace" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.sita.aero/csbu/tools/v1" targetNamespace="http://www.sita.aero/csbu/tools/v1/namespace" elementFormDefault="qualified" attributeFormDefault="unqualified" version="version 1.0">
<xs:element name="MessageTraceEvent">
<xs:annotation>
<xs:documentation>version 1.0</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="SitaIdentifiers" type="tns1:SitaIdType">
<xs:annotation>
<xs:documentation>Container for Sita Unique ID and Transaction ID</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="previousSitaIdentifiers" type="tns1:SitaIdType" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>Container for previous Sita Unique IDs and Transaction IDs</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="relatedSitaIdentifiers" type="tns1:SitaIdType" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>Container for related Sita Unique IDs and Transaction IDs which a delivery report is reporting</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Addresses">
<xs:annotation>
<xs:documentation>Container for Sender and Recipient addresses</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="Originator" type="tns1:AddressType" minOccurs="0"/>
<xs:element name="Recipient" type="tns1:AddressType" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="RemoteSystem">
<xs:annotation>
<xs:documentation>Container for Source or Destination system information</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:choice>
<xs:element name="Source" type="tns1:HostType"/>
<xs:element name="Destination" type="tns1:HostType"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="AdditionalData" minOccurs="0">
<xs:annotation>
<xs:documentation>Service or Billing specific information</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:choice>
<xs:element name="AFTNData" type="tns1:AFTNDataType" minOccurs="0">
<xs:annotation>
<xs:documentation>Addintinal data gathered on NTS </xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TypeBData" type="tns1:TypeBDataType" minOccurs="0">
<xs:annotation>
<xs:documentation>Additional data gathered on MegaSwitch, Sitex or Badgers</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TypeXData" type="tns1:TypeXDataType" minOccurs="0">
<xs:annotation>
<xs:documentation>Additional data gathered on Badgers</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="SMTPData" type="tns1:SMTPDataType" minOccurs="0">
<xs:annotation>
<xs:documentation>Additional data gathered on SMTP systems</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="FAXData" type="tns1:FAXDataType" minOccurs="0">
<xs:annotation>
<xs:documentation>Additional data gathered on Fax systems</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="OmhData" type="tns1:OmhDataType" minOccurs="0">
<xs:annotation>
<xs:documentation>Additional data gathered on OmhData systems</xs:documentation>
</xs:annotation>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="Payload" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>Used to save the full message as received from customer, it can help us avoid re-transforming it back to original message or be used for debugging</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:base64Binary">
<xs:attribute name="payloadType">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="MessageData"/>
<xs:enumeration value="EnvelopeData"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="timeStamp" type="xs:dateTime" use="required"/>
<xs:attribute name="priority" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>Priority defines precedence in sending the messages through to destination</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="bodyMessageID" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The Message ID in the body, as received from or sent to the customer.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="envelopeMessageID" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The Message ID in the envelope, as received from or sent to the customer.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="isReport" type="xs:boolean" use="optional" default="false">
<xs:annotation>
<xs:documentation>Is it a delivery or acknowledge report? If so, set it true</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="messageType" type="tns1:MessageType" use="required">
<xs:annotation>
<xs:documentation>The type of message, e.g. TYPEB, TYPEX, SMS, etc.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="previousMessageType" type="tns1:MessageType" use="optional">
<xs:annotation>
<xs:documentation>The logical message type, where this is different from the physical type. For example a TYPEB message sent to SMTP would have a messageType of SMTP, but previousMessageType of TYPEB.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="messageBodySize" type="xs:string" use="optional"/>
<xs:attribute name="messageHeadSize" type="xs:string" use="optional"/>
<xs:attribute name="messageTotalSize" type="xs:string" use="optional"/>
<xs:attribute name="PDM" type="xs:boolean" use="optional">
<xs:annotation>
<xs:documentation>True if it is a PDM message.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="messsageArchive" type="xs:boolean" use="optional">
<xs:annotation>
<xs:documentation>True if the message has been flagged for archiving.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="messageArchiveDays" type="xs:int" use="optional">
<xs:annotation>
<xs:documentation>The number of days to archive, if known.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="systemID" type="xs:string" use="required">
<xs:annotation>
<xs:documentation>The unique identifier for the system executing the transaction, e.g. BADGERX, JAOMSW, etc.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:simpleType name="MessageType">
<xs:restriction base="xs:string">
<xs:enumeration value="AFTN"/>
<xs:enumeration value="FAX"/>
<xs:enumeration value="SMTP"/>
<xs:enumeration value="TYPEC"/>
<xs:enumeration value="TYPEB"/>
<xs:enumeration value="TYPEX"/>
<xs:enumeration value="SMS"/>
<xs:enumeration value="X400"/>
<xs:enumeration value="SKYFAX"/>
<xs:enumeration value="OTHER"/>
<xs:enumeration value="TELEX"/>
<xs:enumeration value="URI"/>
<xs:enumeration value="EDI"/>
<xs:enumeration value="EDI-X12"/>
<xs:enumeration value="EDI-EDIFACT"/>
<xs:enumeration value="EDI-BINARY"/>
<xs:enumeration value="EDI-XML"/>
<xs:enumeration value="SPEC2000"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="EventType">
<xs:restriction base="xs:string">
<xs:enumeration value="MessageAccepted"/>
<xs:enumeration value="MessageDispatched"/>
<xs:enumeration value="MessageRejected"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="TypeBPriority">
<xs:restriction base="xs:string">
<xs:enumeration value="AF"/>
<xs:enumeration value="NO"/>
<xs:enumeration value="OK"/>
<xs:enumeration value="QA"/>
<xs:enumeration value="QB"/>
<xs:enumeration value="QC"/>
<xs:enumeration value="QD"/>
<xs:enumeration value="QK"/>
<xs:enumeration value="QN"/>
<xs:enumeration value="QP"/>
<xs:enumeration value="QQ"/>
<xs:enumeration value="QU"/>
<xs:enumeration value="QX"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="FaxServiceName">
<xs:restriction base="xs:string">
<xs:enumeration value="IPFax"/>
<xs:enumeration value="BFax"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="MessageStatusType">
<xs:restriction base="xs:string">
<xs:enumeration value="failed"/>
<xs:enumeration value="relayed"/>
<xs:enumeration value="received"/>
<xs:enumeration value="delivered"/>
<xs:enumeration value="rejected"/>
<xs:enumeration value="re-injected"/>
<xs:enumeration value="intercepted"/>
<xs:enumeration value="drained"/>
<xs:enumeration value="op-dropped">
<xs:annotation>
<xs:documentation>message dropped by an operator</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="sys-dropped">
<xs:annotation>
<xs:documentation>message dropped by the messaging system</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="odmci">
<xs:annotation>
<xs:documentation>out of date message cancellation input</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="odmco">
<xs:annotation>
<xs:documentation>out of date message cancellation output</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="other"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="AFTNDataType">
<xs:attribute name="isDataCollect" type="xs:boolean" use="optional">
<xs:annotation>
<xs:documentation>To determine a Type B traffic chargeable</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="messageIdentifier" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="SMI" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>Standard message identifier for Type B messages</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="doubleSignature" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="BATAPSN" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The BATAPSN number of a message</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="ISN" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The ISN number of a message</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="TypeBDataType">
<xs:attribute name="isDataCollect" type="xs:boolean" use="optional">
<xs:annotation>
<xs:documentation>To determine a Type B traffic chargeable</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="messageIdentifier" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="SMI" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>Standard message identifier for Type B messages</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="doubleSignature" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="eopt" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>eopt is 10 numeric characters long and the value is always 0000000000, Eric indicated his team does not populate any value in this field. </xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="documentConversion" type="xs:boolean" use="optional"/>
<xs:attribute name="subject" type="xs:string" use="optional"/>
<xs:attribute name="charSet" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The character set of a message body</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="BATAPSN" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The BATAPSN number of a message</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="ISN" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The ISN number of a message</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="cnxType" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The connection Type of a message</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="Location" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The location of a connection coming from</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="SMTPDataType">
<xs:attribute name="subject" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="doubleSignature" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="rule" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="resend" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="TypeXDataType">
<xs:attribute name="messageIdentifier" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="doubleSignature" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="documentConversion" type="xs:boolean" use="optional"/>
<xs:attribute name="subject" type="xs:string" use="optional"/>
<xs:attribute name="XATAPSN" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The XATAPSN number of a message</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="BadgerId" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The BadgerId to a Type X message is what ISN to a Type B message</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="FAXDataType">
<xs:attribute name="errorCode" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>Error code for the request. 0=success.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="errorString" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The error message, if any.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="serviceName" type="tns1:FaxServiceName" use="optional">
<xs:annotation>
<xs:documentation>Enum value in FaxServiceType</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="channelNumber" type="xs:int" use="optional">
<xs:annotation>
<xs:documentation>The fax channel on the server.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="receivedSize" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The size of the received message, including headers.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="convertedSize" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The size of the message after conversion for fax.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="totalSentSize" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The sum of the bytes sent, including cover pages and retries.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="totalConnectTime" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The sum of time connected to a fax receiver for all attempts.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="totalDuration" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The sum of the off-hook, or network time, for all attempts.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="nbrFaxPages" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The number of pages in the message, including the cover sheet.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="totalPages" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The sum of the pages sent for all attempts.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="recvCSID" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The CSID received from the remote fax system.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="tries" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The number of fax attmpts.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="subject" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="acknow" type="xs:string" use="optional"/>
<xs:attribute name="cod" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="referenceNumber" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The UFAX MSG_ID for the message.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="distID" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The UFAX MSG_RQ_ID for the message.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="fineResolution" type="xs:boolean" use="optional">
<xs:annotation>
<xs:documentation>True for Fine resolution, false for Coarse resolution.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="baudRate" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The connection speed for the fax.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="sitaReceiveTime" type="xs:dateTime" use="optional">
<xs:annotation>
<xs:documentation>The time when the message is received into SITA's network.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="ufaxReceiveTime" type="xs:dateTime" use="optional">
<xs:annotation>
<xs:documentation>The time when UFAX receives the message, when it is delivered to the UFAX inbox.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="startConversionTime" type="xs:dateTime" use="optional">
<xs:annotation>
<xs:documentation>The time when the Converter starts processing a message. If it takes more than one attempt to convert the message, this will be the time of the first attempt.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="endConversionTime" type="xs:dateTime" use="optional">
<xs:annotation>
<xs:documentation>The time when the Converter completes the conversion process. If it takes more than one attempt to convert the message, this will be the time of the last attempt.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="tfaTime" type="xs:dateTime" use="optional">
<xs:annotation>
<xs:documentation>The time of the first call attempt for the message. If UFAX is already calling the fax number for a different message, then this will be the time the message was queued for calling.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="completionTime" type="xs:dateTime" use="optional">
<xs:annotation>
<xs:documentation>The time when the fax has been completed, either because the fax was delivered or it reached the maximum error threshold.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="reportTime" type="xs:dateTime" use="optional">
<xs:annotation>
<xs:documentation>The time when the delivery report is sent. Not used if a report isn't sent.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="doubleSignature" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>For BFax, the Double Signature for the message if any.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="userConfigType" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>Legacy bit-mapped field for BFax.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="networkAccessPoint" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>The network access point where the channel was connected.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="OmhDataType">
<xs:attribute name="msgIdent" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="sysMsgIdent" type="xs:string" use="required">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="inMsgFmt" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="outMsgFmt" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="toDirection" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="fromDirection" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="inMsgSize" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="outMsgSize" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="compCode" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
<xs:attribute name="applicationId" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="AddressType">
<xs:annotation>
<xs:documentation>This is a generic address object</xs:documentation>
</xs:annotation>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="responsible" type="xs:boolean" use="optional" default="false">
<xs:annotation>
<xs:documentation>Used to denote whether the address should be delivered or not, is the node responsible for delivery of this address</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="typeOfAddress" type="tns1:MessageType" use="optional">
<xs:annotation>
<xs:documentation>Type of the address we are given</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="mapped" type="xs:boolean" use="optional" default="false">
<xs:annotation>
<xs:documentation>Used to denote whether the address is mapped or not</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="masqueraded" type="xs:boolean" use="optional" default="false">
<xs:annotation>
<xs:documentation>used to denote if the address is masqueraded, this happens often when messages are pushed through gateways.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="masqueradedID" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>If the address is masqueraded than this is the place where I can carry the original address</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="HostType">
<xs:annotation>
<xs:documentation>This is a generic host object</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="HostName" minOccurs="0">
<xs:annotation>
<xs:documentation>Hostname of the server</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="hostType" type="tns1:MessageType" use="optional">
<xs:annotation>
<xs:documentation>Type of the host such as MQ, JMS, SMTP etc</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="NodeID" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Optional NODE ID goes here</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="HostIP" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Service or host IP address of the service</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="HostPort" type="xs:integer" minOccurs="0">
<xs:annotation>
<xs:documentation>Port address of the service</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="url" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>URL address of the service</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="HostChannel" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Channel name of the service</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ConnectionNumber" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>the connection number that host is connecttng to.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="CircuitNumber" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>This is SITA's CNR</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="DestinationNumber" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>This is SITA's DNR</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="X25DNA" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>This is SITA's X25 dan numbers</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:positiveInteger"/>
</xs:simpleType>
</xs:element>
<xs:element name="MessageStatus" type="tns1:MessageStatusType" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>Users can put anything they want here</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="MiscData" type="xs:string" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>Users can put anything they want here</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="isCustomer" type="xs:boolean">
<xs:annotation>
<xs:documentation>False if the sender/receiver is a SITA system</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="SitaIdType">
<xs:sequence>
<xs:element name="sitaUID" type="xs:string">
<xs:annotation>
<xs:documentation>The unique ID assigned to the message by the first receiving system. This ID must be contained in the message.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TransactionID" type="xs:string">
<xs:annotation>
<xs:documentation>An identifier assigned or created for this event. This must be a unique identifier for this message, i.e. the combination of the SitaUID and transaction ID must be unique. This ID must be contained in the message.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema> -
Expression Tranformation in ODI
Hi,
I am trying to develop an existing informatica mapping in ODI.
my informatica ETL mapping design is like this:
Source Qualifier ----------->1st Exp Tranformation ---------------->2nd exp trnsf --------> lookup ------> insert/update
in the above design how can i implement 1st exp and 2nd exp transformations in ODI.
ThanksHi,
Thanks for the reply.
Yes,i used expression editor in one of my mappings.
in my question you can see 2 expression tranfrmations.
when i open target table expression editor i can apply the 1st exp transformations then how about 2nd exp tranformation which uses calculations from 1st.
Thanks -
Data Loss in DB to DB Transformation in ODI
Hi,
I am facing data loss when I am trying a transformation for a DB to DB mapping in ODI.
I have two tables in two different schemas with the following specifications. In ODI designer model of i have put the type of place as number in target and place as varchar2 for source and accordingly done the mapping.It works successfully when i am putting the data as ('12', 'ani', '12000', '55').
Now for testing I am giving the datas as ('1', 'ani', '12000', '55') and ('2', 'priya', '15000', '65t') and when I am executing it is giving the error as expected(ORA-01722: invalid number) in the task (Insert flow into I$ table). My C$ table is populated with the datas from source. But E$,I$ and target tables are not populated with the data.
Now when I am puttting data in source as ('3', 'shubham', '12000', '56') and ('4', 'shan', '12000', '59') it is getting completed successfully , datas from C$ tables are deleted and data is inserted into the target table.
Now my question is where are the datas ('1', 'ani', '12000', '55') and ('2', 'priya', '15000', '65t') gone. If they are lost what is the recoverable table so that no data loss takes place.
The codes for source and target tables are as follows:
source table code:
CREATE TABLE "DEF"."SOURCE_TEST"
"EMP_ID" NUMBER(9,0),
"EMP_NAME" VARCHAR2(20 BYTE),
"SAL" NUMBER(9,0),
"PLACE" VARCHAR2(10 BYTE),
PRIMARY KEY ("EMP_ID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) TABLESPACE "USERS" ENABLE
inserted data:
INSERT INTO "DEF"."SOURCE_TEST" (EMP_ID, EMP_NAME, SAL, PLACE) VALUES ('1', 'ani', '12000', '55')
INSERT INTO "DEF"."SOURCE_TEST" (EMP_ID, EMP_NAME, SAL, PLACE) VALUES ('2', 'priya', '15000', '65t')
Target table code:
CREATE TABLE "ABC"."TARGET_TEST"
"EMP_ID" NUMBER(9,0),
"EMP_NAME" VARCHAR2(20 BYTE),
"YEARLY_SAL" NUMBER(9,0),
"BONUS" NUMBER(9,0),
"PLACE" NUMBER(9,0),
PRIMARY KEY ("EMP_ID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) TABLESPACE "USERS" ENABLE
Thanks.So, first you have data in "DEF"."SOURCE_TEST".
You then run your interface, and the data is moved into "ABC"."TARGET_TEST" if the interface executes successfully with no errors.
Correct? - no data loss
But if you're saying that you need to handle records which are going to cause the "invalid number" error, then you should read up on 'flow' and 'static' control and how to flag errors before loading them. Flow and Static Control allows ODI to identify erroneous records prior to loading - they'll be put in the E$ table for you to deal with later.
If you haven't already, I'd encourage you to take a look at the documentation on this:
Implementing Data Quality Control -
Missing IN or OUT parameter at index in ODI
HI All,
I am using ODI 11.6
I am facing the below error while working on sequence generator in ODI.I have pass the sequence as (:SP_OFFER_OFFER_ID_SEQ.NEXTVAL)
Its a Table to Table mapping.
ODI-1217: Session INT_TEMP_TO_OFFER (757011) fails with return code 17041.
ODI-1226: Step INT_TEMP_TO_OFFER fails after 1 attempt(s).
ODI-1240: Flow INT_TEMP_TO_OFFER fails while performing a Integration operation. This flow loads target table SP_OFFER.
ODI-1228: Task INT_TO_OFFER (Integration) fails on the target ORACLE connection OWNER.
Caused By: java.sql.SQLException: Missing IN or OUT parameter at index:: 1
The code is
/* DETECTION_STRATEGY = NOT_EXISTS */
insert into OWNER.SP_OFFER T
CAMPGN_NO,
CAMP_OFF
, OFFER_ID
select CAMPGN_NO,
CAMP_OFF
, :SP_OFFER_OFFER_ID_SEQ.NEXTVAL
from OWNER.I$_SP_OFFER S
where IND_UPDATE = 'I'
Please let me know how to resolve this
Thanks,
LonyIs this Database Sequence ? If yes , check the execution area. If everything looks fine and you are still getting error , try to execute this query directly in the Backend. This will make sure if this is a DB related issue or something is missing
-
Hi,
I am doing my first interface/mapping in ODI.
After creation of the datastore (via standard reverse engg) ,I have added a condition/constraint of not null to a column.
When i right click the data store control > check
I get error " CKM not selected ".
Is anyting to do with Agent selection/setting ?
Thanks
SIt's nothing to do with agent. The constarint checking functionality is performed via a Check Knowledge Module i.e. CKM. You will have to aselct a CKM relevant to the technology of your Data Store e.g. Oracle SQL Server etc. You will probably not have the CKM imported into your project so your first step will be to go to Knowledge modules in your Project and import the appropriate CKM. It will then be available in the Knowledge Module dropdown selection on the Check Tab.
-
How to generate documentation for ODI 12c?
Hi,
How to generate documentation of maps for ODI 12c?
Hugs,
RafaelHi,
Please go through the below links
Oracle Data Integrator Solutions: Generating Documentation from Oracle Data Integrator (ODI)
http://docs.oracle.com/cd/E28280_01/integrate.1111/e12643/organizing_documenting.htm#ODIDG517
Thanks,
Pratik -
Error for datatype mismatch or wrong data in XML to database ODI interface
Hello All,
I am doing XML to DB mapping in ODI. but when there is any mismatch in the datatype between source and target or any data issue, ODI is not showing any error for that. it is just inserting the data in the DB from XML up to that erroneous record without any error message.Could anybody please help, how can I get the error message for the same, from ODI when I execute that interface?
Thanks in Advance!no I could not find any records in the error table i.e E$_X table.
Maybe you are looking for
-
I'm trying to find more information on using the . I brought this with the intent of using it as both MP3 player and portable HD, and I heard from a friend that it isn't compatiable on a Mac as a portable HD. Is this true? I thought it would be like
-
Catalog or file problem Lightroom 4
I had to reload my entire system from a backup image. Now my catalog is cutting off at the date of the backup image and many of the files show a question mark. The disk I use to store my images is intact but Lightroom is not getting to them. I can't
-
Next exam after 'Introduction to Oracle9i SQL (1Z0-007)' ?
HI, I have completed IZ0-007 before 2 years please let me know what is the next exam i can go for.I have 6 years epx in SQL/PL SQL.
-
Hi, I want to change to lacation of my mails. Currently the database and the users account are on one Firewire drive (external). I want to create a new database on another disk. I don't care about moving the old one. Just want to create a new one. I
-
Hello all, I'm having audio problems with my FiOS set top box. When I start to change channels I lose audio and can't get it back unless I turn the TV off/on or I change the HDMI source on my TV . Seems after changing a couple of channels the problem