Mapping problem with XML scheme

Hi All,
I have a scenario which I am trying to send a XML file through SFTP (Advanco) to a Z RFC.
I created the message mapping, but I am dealing with a issue that I would like to see if it already happened with someone else and which is the best way to solve it.
In the message mapping - test tab - source view we can find this xml tag regarding the messagetype (see that my MT is called ROOT)
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ROOT xmlns:ns0="http://www.post.ch/schemas/dfu/2006/20/Report6">
the problem is, when I am testing the interface the original file comes like this below
<?xml version="1.0" encoding="UTF-8"?>
<ROOT xmlns="http://www.post.ch/schemas/dfu/2006/20/Report6">
without ns0:
And if I test in message mapping without ns0: I have the problem.
Shouldnt it be equivalent ? I mean, as far as I know the ns0: shouldnt be a problem
Does someone have any suggestion regarding my issue above ?
Thank you
Regards
Diego
Edited by: Diego Crespo on Feb 10, 2011 10:01 AM

Shouldnt it be equivalent ? I mean, as far as I know the ns0: shouldnt be a problem
when you have a namespace in the message then you need to associate it with some prefix....since ns0 (or any other prefix) is not present you are getting the error....having the namespace but not ns0 is the problem.
XMLAnonymizer bean may help you to add the namespace prefix...

Similar Messages

I am facing a new problem with xml schema, plz help me

Hi @,
I am facing a problem with xml schema validation. Below is my code.
public void initialize(String cfgFileName) {
try {
try {
DOMParserWrapper parser = (DOMParserWrapper)Class.forName("dom.wrappers.DOMParser").newInstance();
parser.setFeature( "http://apache.org/xml/features/dom/defer-node-expansion",true );
parser.setFeature( "http://xml.org/sax/features/validation",true);
parser.setFeature( "http://xml.org/sax/features/namespaces",true );
parser.setFeature( "http://apache.org/xml/features/validation/schema",true );
parser.setFeature( "http://apache.org/xml/features/validation/schema-full-checking",true );
Document document = parser.parse(cfgFileName);
System.out.println("Vijay .. code .. damar\n");
}catch (org.xml.sax.SAXParseException spe) {
} catch (org.xml.sax.SAXNotRecognizedException ex ){
} catch (org.xml.sax.SAXNotSupportedException ex ){
} catch (org.xml.sax.SAXException se) {
if (se.getException() != null)
se.getException().printStackTrace(System.err);
else
se.printStackTrace(System.err);
}catch (Exception e) {
System.out.println("Caught unknown exception : \n");
e.printStackTrace(System.err);
System.out.println("Vijay .. code .. success\n");
DocumentBuilderFactory docBuilderFactory = DocumentBuilderFactory.newInstance();
DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
//docBuilder.setErrorHandler(myErrorHandler);
cfg = docBuilder.parse(new File(cfgFileName));
cfg .getDocumentElement ().normalize ();
} catch (Exception e) {
e.printStackTrace();
In the above code I am parsing the xml file and i am doing schema validation. Schema validation is proper and it is validating correctly. Only problem is that, It is validating and showing error correctly correctly but it is not catching that error.
For clear understanding I am printing one statement before parsing and after parsing.
SYSTEM.OUT.PRINTLN("Vijay .. code .. damar\n") this is before parsing
SYSTEM.OUT.PRINTLN("Vijay .. code .. success\n") this is after parsing
Here what is happening means, It is validating correctly and showing error :
[Error] nw_layout-new.xml:800:97: Datatype error: Value 'y' does not match regular expression facet 'yes|no'..
Vijay .. code .. damar
Vijay .. code .. success
Here it is showing error and still continueing not catching.
Plz give solution for this.
Thanks
vijay K

Hello dipthebe,
Check out the articles below go through troubleshooting steps for your iPhone when the screen is unresponsive. You may want to try and restore your iPhone as a new device and then test out what happens when you miss a call to see if the issue is still present afterwards.
iPhone, iPad, iPod touch: Troubleshooting touchscreen response
http://support.apple.com/kb/ts1827
Use iTunes to restore your iOS device to factory settings
http://support.apple.com/kb/HT1414
Regards,
-Norm G.

BIZTALK bts action mapping problem with Message Schemas for the Composite Operation

Hi,
I have a message schema made with the composite operation.
now, I have re-deployed my biztalk project and in the send port for this Oracle composite message the SOAP action header hasn't updated the correct action.
now I tried several verations for this soap action mapping and this is what I got:
><BtsActionMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <Operation Name="Select" Action="http://Microsoft.LobServices.OracleDB/2007/03/CompositeOperation" />
> <Operation Name="SQLEXECUTE" Action="http://Microsoft.LobServices.OracleDB/2007/03/CompositeOperation" />
> </BtsActionMapping>
Now as you can see the Composite schema has 2 operations one is from an Oracle VIEW and the second one is an Oracle SQL querry.
please if someone could assist me with this issue?
Message Schemas for the Composite Operation
Message Schemas for the Composite Operation

For Composite Operations you don't use the Action Mapping Xml for both the SQL Server and Oracle bindings.
The Action for Oracle Composite Operations is:
http://Microsoft.LobServices.OracleDB/2007/03/CompositeOperation
by itself. No Xml or anything.

ExcelXML mapping---problem with XML maps in Excel sheet

Hi Friends,
I have one issue with ExcelXML mapping in Xcelsius.
The problem is I have designed one dashboard using ExcelXML mapping and everything is working fine but I was afraid that I could not able to find the mappings which were embedded in Excel.It happened many times.What I was doing is everytime Im re-mapping.I could be a big problem for me to do this procedire for everytime.How to recover my XML maps into excel sheet.Can anyone please provide the solution to achieve this.

Shouldnt it be equivalent ? I mean, as far as I know the ns0: shouldnt be a problem
when you have a namespace in the message then you need to associate it with some prefix....since ns0 (or any other prefix) is not present you are getting the error....having the namespace but not ns0 is the problem.
XMLAnonymizer bean may help you to add the namespace prefix...

Defining entities with XML schema

Hi,
I came across a problem with XML schema's apparent lack of support for entities. e.g. we define an entity like this:
<!ENTITY le "≤" >.
First off I was trying in my XML instance to include an external entity file like this:
<!DOCTYPE wpi [
<!ENTITY % DerwentXmlEntities PUBLIC "-//Derwent//Derwent XML General ENTITIES 20000214//EN"
"derwent-xml-entities.ent">
%DerwentXmlEntities;
]>
<WPI xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://www.derwent.co.uk/wpi.xsd">
but I am not clear on where I should place the file derwent-xml-entities.ent. Everything I tried ended up with:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00202: could not open file "derwent-xml-entities.ent"
Is it possible to include a file like this?
So I tried just defining an entity like this:
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE wpi [
<!ENTITY times "×">
<!ENTITY le "≤">
]>
The "times" seems OK, but for "le" I get:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00217: invalid character 8804 (\u2264)
What sort of encoding should I use?
Thanks
Pete

<xsd:element name="PsL">
<xsd:annotation>
<xsd:documentation>
**Pseudo List, required as in D-types, the editors often used the
{H control sequence to force an indent to make lists of compounds more
                legible. We can't be sure that they are always lists but there is
                useful mark-up there that we wouldn't want to lose**
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="PsE" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="PsE">
        <xsd:annotation>
            <xsd:documentation>
            Pseudo List Entry
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence minOccurs="1" maxOccurs="1">
                <xsd:element ref="PsP" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="PsS" minOccurs="1" maxOccurs="1"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="PsP">
        <xsd:annotation>
            <xsd:documentation>
            Pseudo List Prefix
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:choice minOccurs="0" maxOccurs="unbounded">
                <xsd:element name="PsP" type="xsd:string"/>
                <xsd:element ref="Sub" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="Sup" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="Em" minOccurs="1" maxOccurs="1"/>
            </xsd:choice>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="PsS">
        <xsd:annotation>
            <xsd:documentation>
            Pseudo List Suffix
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:choice minOccurs="0" maxOccurs="unbounded">
                <xsd:element name="PsS" type="xsd:string"/>
                <xsd:element ref="Sub" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="Sup" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="Em" minOccurs="1" maxOccurs="1"/>
            </xsd:choice>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="Prt">
        <xsd:annotation>
            <xsd:documentation>
            ************************ Part Container Element **************
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence minOccurs="1" maxOccurs="1">
                <xsd:element ref="PrtNo" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="PrtNm" minOccurs="1" maxOccurs="1"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="PrtNo">
        <xsd:annotation>
            <xsd:documentation>
            PartNo
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:choice minOccurs="0" maxOccurs="unbounded">
                <xsd:element name="PrtNo" type="xsd:string"/>
                <xsd:element ref="Sub" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="Sup" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="Em" minOccurs="1" maxOccurs="1"/>
            </xsd:choice>
        </xsd:complexType>
    </xsd:element>
xsd:element name="PrtNm">
        <xsd:annotation>
            <xsd:documentation>
            PartName
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:choice minOccurs="0" maxOccurs="unbounded">
                <xsd:element name="PrtNm" type="xsd:string"/>
                <xsd:element ref="Sub" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="Sup" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="Em" minOccurs="1" maxOccurs="1"/>
            </xsd:choice>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="L">
        <xsd:annotation>
            <xsd:documentation>
            ************************ List Container Element *************
        Attribute typ=used by the composition software to decide how to prefix
                                the list entries, e.g. (a), (A), (i), (1), etc.
                                AL for AlphaLower
                                AU for AlphaUpper
                                RL for RomanLower
                                RU for RomanUpper
                                No for Number
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence minOccurs="1" maxOccurs="unbounded">
                <xsd:element ref="LP" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="LS" minOccurs="0" maxOccurs="1"/>
            </xsd:sequence>
            <xsd:attribute name="typ" use="optional">
                <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                        <xsd:enumeration value="AL"/>
                        <xsd:enumeration value="AU"/>
                        <xsd:enumeration value="RL"/>
                        <xsd:enumeration value="RU"/>
                        <xsd:enumeration value="No"/>
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:attribute>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="LP">
        <xsd:annotation>
            <xsd:documentation>
            List Paragraph
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:choice minOccurs="0" maxOccurs="unbounded">
                <xsd:element name="LP" type="xsd:string"/>
                <xsd:element ref="Sub" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="Sup" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="Em" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="RefD" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="RefF" minOccurs="1" maxOccurs="1"/>
            </xsd:choice>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="LS">
        <xsd:annotation>
            <xsd:documentation>
            1st level sublist
        Attribute typ=used by the composition software to decide how to prefix
                                the list entries, e.g. (a), (A), (i), (1), etc.
                                AL for AlphaLower
                                AU for AlphaUpper
                                RL for RomanLower
                                RU for RomanUpper
                                No for Number
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence minOccurs="1" maxOccurs="unbounded">
                <xsd:element ref="LP" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="LSS" minOccurs="0" maxOccurs="1"/>
            </xsd:sequence>
            <xsd:attribute name="typ" use="optional">
                <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                        <xsd:enumeration value="AL"/>
                        <xsd:enumeration value="AU"/>
                       <xsd:enumeration value="RL"/>
                        <xsd:enumeration value="RU"/>
                        <xsd:enumeration value="No"/>
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:attribute>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="LSS">
        <xsd:annotation>
            <xsd:documentation>
            2nd level list
        Attribute typ=used by the composition software to decide how to prefix
                                the list entries, e.g. (a), (A), (i), (1), etc.
                                AL for AlphaLower
                                AU for AlphaUpper
                                RL for RomanLower
                                RU for RomanUpper
                                No for Number
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="LP" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
            <xsd:attribute name="typ" use="optional">
                <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                        <xsd:enumeration value="AL"/>
                        <xsd:enumeration value="AU"/>
                        <xsd:enumeration value="RL"/>
                        <xsd:enumeration value="RU"/>
                        <xsd:enumeration value="No"/>
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:attribute>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="IndexingCorePt">
        <xsd:annotation>
            <xsd:documentation>
            ******** ROOT ELEMENT for Core Patent Indexing   *********
            ** Indexing is composed of Derwent Classification (DC),IPCs,
                Fragmentation Coding (Frags), Polymer Indexing, Unlinked Registry numbers
                and Keyword Indexing (KI).
                Any combination is these three elements is allowed.
            Attribute vs        =Version number starting at 0
                Attribute co    =Patent country
                Attribute se    =Patent serial
                Attribute ki    =Patent Kind
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence minOccurs="1" maxOccurs="1">
                <xsd:element ref="DC" minOccurs="0" maxOccurs="1"/>
                <xsd:element ref="IPCs" minOccurs="0" maxOccurs="1"/>
                <xsd:element ref="Frag" minOccurs="0" maxOccurs="1"/>
                <xsd:element ref="Polymer" minOccurs="0" maxOccurs="1"/>
                <xsd:element ref="IdxU" minOccurs="0" maxOccurs="1"/>
                <xsd:element ref="KI" minOccurs="0" maxOccurs="1"/>
            </xsd:sequence>
            <xsd:attribute name="vs" type ="xsd:NMTOKEN" use="optional"/>
            <xsd:attribute name="co" type ="xsd:NMTOKEN" use="required"/>
            <xsd:attribute name="se" type ="xsd:NMTOKEN" use="required"/>
            <xsd:attribute name="ki" type ="xsd:NMTOKEN" use="required"/>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="DC">
        <xsd:annotation>
            <xsd:documentation>
            ************* DERWENT CLASSIFICATION *******************
            ** Derwent Classification is divided in 3 main areas:
                Chemical(CPI),General & Mechanical (EngPI),
                Electronic & Electronical (EPI)
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:choice minOccurs="1" maxOccurs="1">
                <xsd:sequence minOccurs="1" maxOccurs="1">
                    <xsd:element ref="CPIs" minOccurs="1" maxOccurs="1"/>
                    <xsd:element ref="EngPIs" minOccurs="0" maxOccurs="1"/>
                    <xsd:element ref="EPIs" minOccurs="0" maxOccurs="1"/>
                </xsd:sequence>
                <xsd:sequence minOccurs="1" maxOccurs="1">
                    <xsd:element ref="EngPIs" minOccurs="1" maxOccurs="1"/>
                    <xsd:element ref="EPIs" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
                <xsd:element ref="EPIs" minOccurs="1" maxOccurs="1"/>
            </xsd:choice>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="CPIs">
        <xsd:annotation>
            <xsd:documentation>
            UNIQUE ELEMENT DC
            ** Container element for CPI**
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="CPI" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="CPI">
        <xsd:annotation>
            <xsd:documentation>
            UNIQUE ELEMENT CPIs
            ** CPI is composed of sections A to N (no section I)
                Any combination is allowed, there has to be at least one section.
                No section can appear twice. The DTD does not enforce this.
                Section N can't be on his own. The DTD does not enforce this.
                Each single Chemical section is composed of one main class (DCCM)
                and zero to many secondary classes (DCCSs). One to many Manual
                code (MCCs) has to be applied to a given chemical section.
                Attribute section= an allowed Derwent CPI section    **
            Note that content MCCs is optional as its optional in the backfile
                before 19??
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:choice minOccurs="1" maxOccurs="1">
                <xsd:sequence minOccurs="1" maxOccurs="1">
                    <xsd:element ref="DCCM" minOccurs="1" maxOccurs="1"/>
                    <xsd:element ref="DCCSs" minOccurs="0" maxOccurs="1"/>
                    <xsd:element ref="MCCs" minOccurs="0" maxOccurs="1"/>
                </xsd:sequence>
                <xsd:element ref="MCCs" minOccurs="1" maxOccurs="1"/>
            </xsd:choice>
            <xsd:attribute name="sct" use="required">
                <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                        <xsd:enumeration value="A"/>
                        <xsd:enumeration value="B"/>
                        <xsd:enumeration value="C"/>
                        <xsd:enumeration value="D"/>
                        <xsd:enumeration value="E"/>
                        <xsd:enumeration value="F"/>
                        <xsd:enumeration value="G"/>
                        <xsd:enumeration value="H"/>
                        <xsd:enumeration value="J"/>
                        <xsd:enumeration value="K"/>
                        <xsd:enumeration value="L"/>
                        <xsd:enumeration value="M"/>
                        <xsd:enumeration value="N"/>
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:attribute>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="DCCM" type="xsd:string">
        <xsd:annotation>
            <xsd:documentation>
            ** Derwent Class Chemical Main element **
            </xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    <xsd:element name="DCCSs">
        <xsd:annotation>
            <xsd:documentation>
            ** Derwent Classes Chemical Secondary Container element**
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="DCCS" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
<xsd:element name="DCCS" type="xsd:string">
        <xsd:annotation>
            <xsd:documentation>
            ** A Derwent Class Chemical Secondary (DCCS) **
            </xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    <xsd:element name="MCCs">
        <xsd:annotation>
            <xsd:documentation>
            ** Manual Codes CPI Container Element **
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="MCC" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="MCC" type="xsd:string">
        <xsd:annotation>
            <xsd:documentation>
            ** A Manual Code CPI **
            </xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    <xsd:element name="EngPIs">
        <xsd:annotation>
            <xsd:documentation>
            **General & Mechanical Sections Container element**
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="EngPI" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="EngPI">
        <xsd:annotation>
            <xsd:documentation>
            UNIQUE ELEMENT EngPIs
            ** General & Mechanical Sections EngPI is composed of sections
                P and Q. Any combination is allowed, with at least one section.
                There are no manual codes for these sections.
                Each single EngPI section is composed of
                one or more Derwent Class Engineering (DCEng) elements.
                No section can appear twice. The DTD does not enforce this.
                Attribute section= an allowed Derwent EngPI section         **
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="DCEngs" minOccurs="1" maxOccurs="1"/>
            </xsd:sequence>
            <xsd:attribute name="sct" use="required">
                <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                        <xsd:enumeration value="P"/>
                        <xsd:enumeration value="Q"/>
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:attribute>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="DCEngs">
        <xsd:annotation>
            <xsd:documentation>
            ** Derwent Class Engineering Container eement **
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="DCEng" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
<xsd:element name="DCEng" type="xsd:string">
        <xsd:annotation>
            <xsd:documentation>
            ** Derwent Class Engineering **
            </xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    <xsd:element name="EPIs">
        <xsd:annotation>
            <xsd:documentation>
            ** Electronic & Electrical Sections EPI **
            Container element for EPI
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="EPI" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="EPI">
        <xsd:annotation>
            <xsd:documentation>
            UNIQUE ELEMENT EPIs
            ** EPI is composed of sections R to X. Any combination is allowed,
                  with at least one section.
                 Section R can't be on his own. The DTD does not enforce this.
                 Each single is composed of one or more Derwent Class Electronic
                 and Electrical (DCE) elements.
                 No section can appear twice. The DTD does not enforce this. **
     Attribute sct = an allowed Derwent EPI section
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="EPIgp" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
            <xsd:attribute name="sct" use="required">
                <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                        <xsd:enumeration value="R"/>
                        <xsd:enumeration value="S"/>
                        <xsd:enumeration value="T"/>
                        <xsd:enumeration value="U"/>
                        <xsd:enumeration value="V"/>
                        <xsd:enumeration value="W"/>
                        <xsd:enumeration value="X"/>
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:attribute>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="EPIgp">
        <xsd:annotation>
            <xsd:documentation>
            ** A Container element to group the related DCE & MCEs elements **
            Note that content MCEs is optional as its optional in the backfile
                 before 19??
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence minOccurs="1" maxOccurs="1">
                <xsd:element ref="DCE" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="MCEs" minOccurs="0" maxOccurs="1"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="DCE" type="xsd:string">
        <xsd:annotation>
            <xsd:documentation>
            ** Derwent Class Electronic & Electrical (DCE) contains
                 Manual Codes Electronic & Electrical (MCE)              **
            ** Derwent Class EPI **
            </xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    <xsd:element name="MCEs">
        <xsd:annotation>
            <xsd:documentation>
            ** Manual Codes EPI container element **
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="MCE" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="MCE" type="xsd:string">
        <xsd:annotation>
            <xsd:documentation>
            ** A Manual Code EPI **
            </xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    <xsd:element name="IPCs">
        <xsd:annotation>
            <xsd:documentation>
            ********************IPCs Container element *************
            ** The following xlink construct is a link to the IPC codes on
                 the WIPO site, this could be added to the DTD to provide the link
                 without adding any thing to the individual instances
                 xlink:type   (locator) #FIXED     "locator"
                 xlink:rl   NMTOKEN       #FIXED     "IPCs"
                 xlink:href CDATA #FIXED "http://classifications.wipo.int/fulltext/new_ipc/"
                 xlink:title CDATA       #FIXED     "IPC Codes"            **
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="IPC" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="IPC">
        <xsd:annotation>
            <xsd:documentation>
            UNIQUE ELEMENT IPCs
            ** An IPC Code **
            ** Attribute rnk= Derwent assigned character to indicate type
                 of IPC:
                      A= Main IPC
                      B= Other, unlinked IPCs
                      C to Y = Linked IPCs and Index Terms
                      Z= IPC Index Terms
                      -= Additional terms                       **
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
         <xsd:simpleContent>
          <xsd:extension base="xsd:string">
            <xsd:attribute name="rnk" use="required">
                <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                        <xsd:enumeration value="A"/>
                        <xsd:enumeration value="B"/>
                        <xsd:enumeration value="C"/>
                        <xsd:enumeration value="D"/>
                        <xsd:enumeration value="E"/>
                        <xsd:enumeration value="F"/>
                        <xsd:enumeration value="G"/>
                        <xsd:enumeration value="H"/>
                        <xsd:enumeration value="I"/>
                        <xsd:enumeration value="J"/>
                        <xsd:enumeration value="K"/>
                        <xsd:enumeration value="L"/>
                        <xsd:enumeration value="M"/>
                        <xsd:enumeration value="N"/>
                        <xsd:enumeration value="O"/>
                        <xsd:enumeration value="P"/>
                        <xsd:enumeration value="Q"/>
                        <xsd:enumeration value="R"/>
                        <xsd:enumeration value="S"/>
                        <xsd:enumeration value="T"/>
                        <xsd:enumeration value="U"/>
                        <xsd:enumeration value="V"/>
                        <xsd:enumeration value="W"/>
                        <xsd:enumeration value="X"/>
                        <xsd:enumeration value="Y"/>
                        <xsd:enumeration value="Z"/>
                        <xsd:enumeration value="-"/>
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:attribute>
           </xsd:extension>
         </xsd:simpleContent>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="Frag">
        <xsd:annotation>
            <xsd:documentation>
            ***************BCE INDEXING OR FRAGMENTATION ************
            ** Fragmentation Container element**
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="FragSub" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="FragSub">
        <xsd:annotation>
            <xsd:documentation>
            UNIQUE ELEMENT Frag
            ** Fragmentation Sub heading **
            ** Attribute sjct=The main BCE chemical subject categories
                 defined by Derwent as subsets. The subsets are designated by the
                 subheadings MO through M6:
                      MO Agricultural, pharmaceutical     1963-1969
                      M1 Agricultural, pharmaceutical natural products
                                     and polymers     1970 to present
                      M2 Agricultural, pharmaceutical         1970 to present
                      M3 General chemicals                    1970 to present
                      M4 Dyes                                 1970 to present
                      M5 Steroids                             1963 to present
                      M6 Galenicals                           1976 to present"**
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="CardRec" minOccurs="1" maxOccurs="unbounded"/>
            </xsd:sequence>
            <xsd:attribute name="sjct" use="required">
                <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                        <xsd:enumeration value="M0"/>
                        <xsd:enumeration value="M1"/>
                        <xsd:enumeration value="M2"/>
                        <xsd:enumeration value="M3"/>
                        <xsd:enumeration value="M4"/>
                        <xsd:enumeration value="M5"/>
                        <xsd:enumeration value="M6"/>
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:attribute>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="CardRec">
        <xsd:annotation>
            <xsd:documentation>
            ** Card Record **
                 Attribute no     =Derwent assigned record number
                 Attribute mc     = Markush DARC Control Code
                 Attribute trc     = Fragmentaion Control Time ranging codes:
                                M900     Pre-1970
                                M901     1970-1971
                                M902     1972-1981 (8126)
                                M903     1981 (8127) onward
                                M905
                 Attribute rn      = 910 Codes generated from registry numbers.
                                Only searchable from 1981
                 Attribute wd = 911 Wide Disclosure. Only searchable from 1981
            </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
            <xsd:sequence minOccurs="1" maxOccurs="1">
                <xsd:element ref="FCodes" minOccurs="1" maxOccurs="1"/>
                <xsd:element ref="RINs" minOccurs="0" maxOccurs="1"/>
                <xsd:element ref="SCNs" minOccurs="0" maxOccurs="1"/>
                <xsd:element ref="MCNs" minOccurs="0" maxOccurs="1"/>
                <xsd:element ref="DRNs" minOccurs="0" maxOccurs="1"/>
                <xsd:element ref="DCRs" minOccurs="0" maxOccurs="1"/>
            </xsd:sequence>

Mapping with xml-schema XML-data to relational tables

Hello,
is it possible to map data from xml documents to relational tables with xml-schema?
I mean not in nested tables but in relational tables with primary and foreign keys!
With SQL Server 2005 it is very easy, I dont believe that Oracle couldn't do this!
I searched but i cant find anything about that!
Thx
user445232

indeed, oracle does this for xml schema based xmltype data, however, these underlying tables are not accessable to the application. Maybe It should for next version, so folks who like to use relational model can use it without mapping it manually.
Actually, nested tables, are the same, their underlying tables (segments) are indeed relational tables, oracle manages them internally and not visiable to the application. You can find them in the user_segments, user_objects views though.

Problem with XML on Linux

hi everybody,
I've a big problem with XML on Linux, in details I see my program stopping on Linux at the instruction
XMLReader xr = XMLReaderFactory.createXMLReader("org.apache.crimson.parser.XMLReaderImpl");
and it's strange because on Windows it runs and there aren't problems about permissions on files, does anyone knows what to do?
thanks in advance!
Stefano

What happens on that line? I'm assuming you get some kind of error or exception.
Make sure the JAR file for Crimson is in your classpath.

Problem with XML in APEX ORA-06502

i, I have a problem with XML generation, I developed an application in APEX, and in a html page I have this process:
declare
l_XML varchar2(32767);
begin
select xmlElement
"iva",
xmlElement("numeroRuc",J.RUC),
xmlElement("razonSocial", J.RAZON_SOCIAL),
xmlElement("idRepre", J.ID_REPRE),
xmlElement("rucContador", J.RUC_CONTADOR),
xmlElement("anio", J.ANIO),
xmlElement("mes", J.MES),
xmlElement
"compras",
select xmlAgg
xmlElement
"detalleCompra",
--xmlAttributes(K.ID_COMPRA as "COMPRA"),
xmlForest
K.COD_SUSTENTO as "codSustento",
K.TPLD_PROV as "tpldProv",
K.ID_PROV as "idProv",
K.TIPO_COMPROBANTE as "tipoComprobante",
to_char(K.FECHA_REGISTRO, 'DD/MM/YYYY') as "fechaRegistro",
K.ESTABLECIMIENTO as "establecimiento",
K.PUNTO_EMISION as "puntoEmision",
K.SECUENCIAL as "secuencial",
to_char(K.FECHA_EMISION, 'DD/MM/YYYY') as "fechaEmision",
K.AUTORIZACION as "autorizacion",
to_char(K.BASE_NO_GRA_IVA, 9999999999.99) as "baseNoGraIva",
to_char(K.BASE_IMPONIBLE, 9999999999.99) as "baseImponible",
to_char(K.BASE_IMP_GRAV, 9999999999.99) as "baseImpGrav",
to_char(K.MONTO_ICE, 9999999999.99) as "montoIce",
to_char(K.MONTO_IVA, 9999999999.99) as "montoIva",
to_char(K.VALOR_RET_BIENES, 9999999999.99) as "valorRetBienes",
to_char(K.VALOR_RET_SERVICIOS, 9999999999.99) as "valorRetServicios",
to_char(K.VALOR_RET_SERV_100, 9999999999.99) as "valorRetServ100"
xmlElement
"air",
select xmlAgg
xmlElement
"detalleAir",
xmlForest
P.COD_RET_AIR as "codRetAir",
to_char(P.BASE_IMP_AIR, 9999999999.99) as "baseImpAir",
to_char(P.PORCENTAJE_AIR, 999.99) as "porcentajeAir",
to_char(P.VAL_RET_AIR, 9999999999.99) as "valRetAir"
from ANEXO_COMPRAS P
where P.ID_COMPRA = K.ID_COMPRA
AND P.ID_INFORMANTE_XML = K.ID_INFORMANTE_XML
xmlElement("estabRetencion1", K.ESTAB_RETENCION_1),
xmlElement("ptoEmiRetencion1", K.PTO_EMI_RETENCION_1),
xmlElement("secRetencion1", K.SEC_RETENCION_1),
xmlElement("autRetencion1", K.AUT_RETENCION_1),
xmlElement("fechaEmiRet1", to_char(K.FECHA_EMI_RET_1,'DD/MM/YYYY')),
xmlElement("docModificado", K.DOC_MODIFICADO),
xmlElement("estabModificado", K.ESTAB_MODIFICADO),
xmlElement("ptoEmiModificado", K.PTO_EMI_MODIFICADO),
xmlElement("secModificado", K.SEC_MODIFICADO),
xmlElement("autModificado", K.AUT_MODIFICADO)
from SRI_COMPRAS K
WHERE K.ID IS NOT NULL
AND K.ID_INFORMANTE_XML = J.ID_INFORMANTE
AND K.ID BETWEEN 1 AND 25
).getClobVal()
into l_XML
from ANEXO_INFORMANTE J
where J.ID_INFORMANTE =:P3_MES
and J.RUC =:P3_ID_RUC
and J.ANIO =:P3_ANIO
and J.MES =:P3_MES;
--HTML
sys.owa_util.mime_header('text/xml',FALSE);
sys.htp.p('Content-Length: ' || length(l_XML));
sys.owa_util.http_header_close;
sys.htp.print(l_XML);
end;
Now my table has more than 900 rows and only when I specifically selected 25 rows of the table "ANEXO_COMPRAS" in the where ( AND K.ID BETWEEN 1 AND 25) the XML is generated.+
I think that the problem may be the data type declared "varchar2", but I was trying with the data type "CLOB" and the error is the same.+
declare
l_XML CLOB;
begin
--Oculta XML
sys.htp.init;
wwv_flow.g_page_text_generated := true;
wwv_flow.g_unrecoverable_error := true;
--select XML
select xmlElement
from SRI_COMPRAS K
WHERE K.ID IS NOT NULL
AND K.ID_INFORMANTE_XML = J.ID_INFORMANTE
).getClobVal()
into l_XML
from ANEXO_INFORMANTE J
where J.ID_INFORMANTE =:P3_MES
and J.RUC =:P3_ID_RUC
and J.ANIO =:P3_ANIO
and J.MES =:P3_MES;
--HTML
sys.owa_util.mime_header('text/xml',FALSE);
sys.htp.p('Content-Length: ' || length(l_XML));
sys.owa_util.http_header_close;
sys.htp.print(l_XML);
end;
The error generated is ORA-06502: PL/SQL: numeric or value error+_
Please I need your help. I don`t know how to resolve this problem, how to use the data type "CLOB" for the XML can be generate+

JohannaCevallos07 wrote:
Now my table has more than 900 rows and only when I specifically selected 25 rows of the table "ANEXO_COMPRAS" in the where ( AND K.ID BETWEEN 1 AND 25) the XML is generated.+
I think that the problem may be the data type declared "varchar2", but I was trying with the data type "CLOB" and the error is the same.+
The error generated is ORA-06502: PL/SQL: numeric or value error+_
Please I need your help. I don`t know how to resolve this problem, how to use the data type "CLOB" for the XML can be generate+The likeliest explanation for this is that length of the XML exceeds 32K, which is the maximum size that <tt>htp.p</tt> can output. A CLOB can store much more than this, so it's necessary to buffer the output as shown in +{message:id=4497571}+
Help us to help you. When you have a problem include as much relevant information as possible upfront. This should include:
<li>Full APEX version
<li>Full DB/version/edition/host OS
<li>Web server architecture (EPG, OHS or APEX listener/host OS)
<li>Browser(s) and version(s) used
<li>Theme
<li>Template(s)
<li>Region/item type(s) (making particular distinction as to whether a "report" is a standard report, an interactive report, or in fact an "updateable report" (i.e. a tabular form)
And always post code wrapped in <tt>\...\</tt> tags, as described in the FAQ.
Thanks

Mapping problem with compressed key update record

Hi, could you please advise?
I'm getting the following problem:
About a week ago replicat abened with "Error in mapping" error. I found in discard file some record looking like:
filed1 = NULL
field2 =
field3 =
field4 =
field5 =
datefield = -04-09 00:00:00
field6 =
field8 =
field9 = NULL
field10 =
Where filed9 = @GETENV("GGHEADER", "COMMITTIMESTAM"), field10 = = @GETENV("GGHEADER", "COMMITTIMESTAM"), others are table fields mapped by USEDEFAULTS
So I got Mapping problem with compressed key update record at 2012-06-01 15:44
I guess I need to mention that extract failed in 5 minuts before it with: VAM function VAMRead returned unexpected result: error 600 - VAM Client Report <[CFileInfo::Read] Timeout expired after 10 retries with 1000 ms delay, waiting to read transaction log or backup files. To increase the number of retries, use SETENV (GGS_CacheRetryCount = n) in Extract parameter file. To control retry delay time, use SETENV (GGS_CacheRetryDelay = n). handle: 0000000000000398 ReadFile GetLastError:997 Wait GetLastError:997>.
I don't know if it has ther same source as data corruption, could you tell me if it is?
Well, I created new extract, starting 2012-06-01 15:30 to check if there was something with extract at the time, but got the same error.
If I run extract beging at 15:52 it starts and works.
But well, I got another one today. Data didn't look that bad, but yet one column came with null value:( And I'm using it as a key column, so I got Mapping problem with compressed key update record again:(
I'm replicating from SQL Server 2008 to Oracle 11g.
I'm actually using NOCOMPRESSUPDATES in Extract.
CDC is enabled for all tables replicated. The only thing is that it is enabled not by ADD TRANDATA command, but by SQL Server sys.sp_cdc_enable_table, does it matter?
Could you please advise why does it happen?

Well, the problem begins somewhere in extract or before extract, may be in transaction log, I don't know:(
Here are extract parameters:
EXTRACT ETCHECK
TRANLOGOPTIONS MANAGESECONDARYTRUNCATIONPOINT
SOURCEDB TEST, USERID **, PASSWORD *****
exttrail ./dirdat/ec
NOCOMPRESSUPDATES
NOCOMPRESSDELETES
TABLE tst.table1, COLS (field1, field2, field3, field4, field5, field6, field7, field8 );
TABLE tst.table2, COLS (field1, field2, field3, field4 );
Data pump:
EXTRACT DTCHECK
SOURCEDB TEST, USERID **, PASSWORD *****
RMTHOST ***, MGRPORT 7809
RMTTRAIL ./dirdat/dc
TABLE tst.table1;
TABLE tst.table2;
Replicat:
REPLICAT rtcheck
USERID tst, PASSWORD ***
DISCARDFILE ./dirrpt/rtcheck.txt, PURGE
SOURCEDEFS ./dirdef/sourcei.def
HANDLECOLLISIONS
UPDATEDELETES
MAP tst.table1, t.table1, COLMAP (USEDEFAULTS , filed9 = @GETENV("GGHEADER", "COMMITTIMESTAMP"), filed10= @CASE(@GETENV("GGHEADER", "OPTYPE"), "SQL COMPUPDATE", "U", "PK UPDATE", "U",@GETENV("GGHEADER", "OPTYPE")) ), KEYCOLS (field3);
MAP dbo.TPROCPERIODCONFIRMSTAV, TARGET R_019_000001.TPROCPERIODCONFIRMSTAV, COLMAP (USEDEFAULTS , field5 = @GETENV("GGHEADER", "COMMITTIMESTAMP"), filed6= @CASE(@GETENV("GGHEADER", "OPTYPE"), "SQL COMPUPDATE", "U", "PK UPDATE", "U",@GETENV("GGHEADER", "OPTYPE")) ), KEYCOLS (filed1, field2, field3);
Rpt file for replicat:
Oracle GoldenGate Delivery for Oracle
Version 11.1.1.1 OGGCORE_11.1.1_PLATFORMS_110421.2040
Windows x64 (optimized), Oracle 11g on Apr 22 2011 00:34:07
Copyright (C) 1995, 2011, Oracle and/or its affiliates. All rights reserved.
Starting at 2012-06-05 12:49:38
Operating System Version:
Microsoft Windows Server 2008 R2 , on x64
Version 6.1 (Build 7601: Service Pack 1)
Process id: 2264
Description:
** Running with the following parameters **
REPLICAT rtcheck
USERID tst, PASSWORD ***
DISCARDFILE ./dirrpt/rtcheck.txt, PURGE
SOURCEDEFS ./dirdef/sourcei.def
HANDLECOLLISIONS
UPDATEDELETES
MAP tst.table1, t.table1, COLMAP (USEDEFAULTS , filed9 = @GETENV("GGHEADER", "COMMITTIMESTAMP"), filed10= @CASE(@GETENV("GGHEADER", "OPTYPE"), "SQL COMPUPDATE", "U", "PK UPDATE", "U",@GETENV("GGHEADER", "OPTYPE")) ), KEYCOLS (field3);
MAP dbo.TPROCPERIODCONFIRMSTAV, TARGET R_019_000001.TPROCPERIODCONFIRMSTAV, COLMAP (USEDEFAULTS , field5 = @GETENV("GGHEADER", "COMMITTIMESTAMP"), filed6= @CASE(@GETENV("GGHEADER", "OPTYPE"), "SQL COMPUPDATE", "U", "PK UPDATE", "U",@GETENV("GGHEADER", "OPTYPE")) ), KEYCOLS (filed1, field2, field3);
CACHEMGR virtual memory values (may have been adjusted)
CACHEBUFFERSIZE: 64K
CACHESIZE: 512M
CACHEBUFFERSIZE (soft max): 4M
CACHEPAGEOUTSIZE (normal): 4M
PROCESS VM AVAIL FROM OS (min): 1G
CACHESIZEMAX (strict force to disk): 881M
Database Version:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for 64-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
Database Language and Character Set:
NLS_LANG = "AMERICAN_AMERICA.CL8MSWIN1251"
NLS_LANGUAGE = "AMERICAN"
NLS_TERRITORY = "AMERICA"
NLS_CHARACTERSET = "CL8MSWIN1251"
For further information on character set settings, please refer to user manual.
** Run Time Messages **
Opened trail file ./dirdat/dc000000 at 2012-06-05 12:49:39
2012-06-05 12:58:14 INFO OGG-01020 Processed extract process RESTART_ABEND record at seq 0, rba 925 (aborted 0 records).
MAP resolved (entry tst.table1):
MAP tst.table1, t.table1, COLMAP (USEDEFAULTS , filed9 = @GETENV("GGHEADER", "COMMITTIMESTAMP"), filed10= @CASE(@GETENV("GGHEADER", "OPTYPE"), "SQL COMPUPDATE", "U", "PK UPDATE", "U",@GETENV("GGHEADER", "OPTYPE")) ), KEYCOLS (field3);
2012-06-05 12:58:14 WARNING OGG-00869 No unique key is defined for table table1. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
Using the following default columns with matching names:
field1=field1, field2=field2, field3=field3, field4=field4, field5=field5, field6=field6, field7=field7, field8=field8
Using the following key columns for target table R_019_000001.TCALCULATE: field3.
2012-06-05 12:58:14 WARNING OGG-01431 Aborted grouped transaction on 'tst.table1', Mapping error.
2012-06-05 12:58:14 WARNING OGG-01003 Repositioning to rba 987 in seqno 0.
2012-06-05 12:58:14 WARNING OGG-01151 Error mapping from tst.table1 to tst.table1.
2012-06-05 12:58:14 WARNING OGG-01003 Repositioning to rba 987 in seqno 0.
Source Context :
SourceModule : [er.main]
SourceID : [er/rep.c]
SourceFunction : [take_rep_err_action]
SourceLine : [16064]
ThreadBacktrace : [8] elements
: [C:\App\OGG\replicat.exe(ERCALLBACK+0x143034) [0x00000001402192B4]]
: [C:\App\OGG\replicat.exe(ERCALLBACK+0x11dd44) [0x00000001401F3FC4]]
: [C:\App\OGG\replicat.exe(<RCALLBACK+0x11dd44) [0x000000014009F102]]
: [C:\App\OGG\replicat.exe(<RCALLBACK+0x11dd44) [0x00000001400B29CC]]
: [C:\App\OGG\replicat.exe(<RCALLBACK+0x11dd44) [0x00000001400B8887]]
: [C:\App\OGG\replicat.exe(releaseCProcessManagerInstance+0x25250) [0x000000014028F200]]
: [C:\Windows\system32\kernel32.dll(BaseThreadInitThunk+0xd) [0x000000007720652D]]
: [C:\Windows\SYSTEM32\ntdll.dll(RtlUserThreadStart+0x21) [0x000000007733C521]]
2012-06-05 12:58:14 ERROR OGG-01296 Error mapping from tst.table1 to tst.table1.
* ** Run Time Statistics ** *
Last record for the last committed transaction is the following:
Trail name : ./dirdat/dc000000
Hdr-Ind : E (x45) Partition : . (x04)
UndoFlag : . (x00) BeforeAfter: A (x41)
RecLength : 249 (x00f9) IO Time : 2012-06-01 15:48:56.285333
IOType : 115 (x73) OrigNode : 255 (xff)
TransInd : . (x03) FormatType : R (x52)
SyskeyLen : 0 (x00) Incomplete : . (x00)
AuditRBA : 44 AuditPos : 71176199289771
Continued : N (x00) RecCount : 1 (x01)
2012-06-01 15:48:56.285333 GGSKeyFieldComp Len 249 RBA 987
Name: DBO.TCALCULATE
Reading ./dirdat/dc000000, current RBA 987, 0 records
Report at 2012-06-05 12:58:14 (activity since 2012-06-05 12:58:14)
From Table tst.table1 to tst.table1:
# inserts: 0
# updates: 0
# deletes: 0
# discards: 1
Last log location read:
FILE: ./dirdat/dc000000
SEQNO: 0
RBA: 987
TIMESTAMP: 2012-06-01 15:48:56.285333
EOF: NO
READERR: 0
2012-06-05 12:58:14 ERROR OGG-01668 PROCESS ABENDING.
Discard file:
Oracle GoldenGate Delivery for Oracle process started, group RTCHECK discard file opened: 2012-06-05 12:49:39
Key column filed3 (0) is missing from update on table tst.table1
Missing 1 key columns in update for table tst.table1.
Current time: 2012-06-05 12:58:14
Discarded record from action ABEND on error 0
Aborting transaction on ./dirdat/dc beginning at seqno 0 rba 987
error at seqno 0 rba 987
Problem replicating tst.table1 to tst.table1
Mapping problem with compressed key update record (target format)...
filed1 = NULL
field2 =
field3 =
field4 =
field5 =
datefield = -04-09 00:00:00
field6 =
field8 =
field9 = NULL
field10 =
Process Abending : 2012-06-05 12:58:14

Mapping problem with compressed key update record (target format)...

Hi Guys,
Getting below error while replication from Source to target. Source table is having NOT NULL Column, but on target replicat process giving error about some NULL value ??
How to overcome this issue, any idea...
2011-08-04 10:35:04 INFO OGG-00995 Oracle GoldenGate Delivery for Oracle, rmastrk.prm: REPLICAT RMASTRK starting.
2011-08-04 10:35:05 INFO OGG-00996 Oracle GoldenGate Delivery for Oracle, rmastrk.prm: REPLICAT RMASTRK started.
2011-08-04 10:35:06 WARNING OGG-00869 Oracle GoldenGate Delivery for Oracle, rmastrk.prm: OCI Error ORA-01407: cannot update ("INFRA"."CUST"."CODE") to NULL (status = 1407), SQL <UPDATE "INFRA"."CUST" SET "ORD_ID" = :a2,"DP_ID" = :a3,"EXCHNG_CODE" = :a4,"ORD_QTY" = :a5,"ORD_PRICE" = :a6,"CODE" = :a7,"MKRT_CODE" = :a8,"CHANN>.
2011-08-04 10:35:06 WARNING OGG-01004 Oracle GoldenGate Delivery for Oracle, rmastrk.prm: Aborted grouped transaction on 'INFRA.CUST', Database error 1407 (ORA-01407: cannot update ("INFRA"."CUST"."SCRP_CODE") to NULL).
2011-08-04 10:35:06 WARNING OGG-01003 Oracle GoldenGate Delivery for Oracle, rmastrk.prm: Repositioning to rba 44132192 in seqno 68708.
2011-08-04 10:35:06 *WARNING OGG-01154 Oracle GoldenGate Delivery for Oracle, rmastrk.prm: SQL error 1407 mapping INFRA.CUST to INFRA.CUST OCI Error ORA-01407:* *cannot update ("INFRA"."CUST"."SCRP_CODE") to NULL (status = 1407), SQL <UPDATE "INFRA"."CUST" SET "ORD_ID" = :a2,"DP_ID" = :a3,"EXCHNG_CODE"=:a4,"ORD_QTY"*
*= :a5,"ORD_PRICE" = :a6,"SCRP_CODE" = :a7,"MKRT_CODE" = :a8,"CHANN>.*
2011-08-04 10:35:06 WARNING OGG-01003 Oracle GoldenGate Delivery for Oracle, rmastrk.prm: Repositioning to rba 44132192 in seqno 68708.
2011-08-04 10:35:06 ERROR OGG-01296 Oracle GoldenGate Delivery for Oracle, rmastrk.prm: Error mapping from INFRA.CUST to INFRA.CUST.
2011-08-04 10:35:06 ERROR OGG-01668 Oracle GoldenGate Delivery for Oracle, rmastrk.prm: PROCESS ABENDING.
Oracle GoldenGate Delivery for Oracle process started, group RMASTRK discard file opened: 2011-08-04 10:35:05
Current time: 2011-08-04 10:35:06
Discarded record from action ABEND on error 1407
OCI Error ORA-01407: cannot update ("INFRA"."CUST"."SCRP_CODE") to NULL
(status = 1407), SQL <UPDATE "INFRA"."CUST" SET "ORD_ID" = :a2,"MKRT_CODE" = :a8,"CHANN>
Aborting transaction on ./dirdat/pm beginning at seqno 68708 rba 44132192
error at seqno 68708 rba 44132192
Problem replicating INFRA.CUST to INFRA.CUST
*Mapping problem with compressed key update record (target format)...*
ORD_QTY = 500
ORD_PRICE = 37430
SCRP_CODE =
MKRT_CODE = N
Oracle GoldenGate Delivery for Oracle process started, group RMASTRK discard file opened: 2011-08-
04 10:35:05
Current time: 2011-08-04 10:35:06
Discarded record from action ABEND on error 1407
OCI Error ORA-01407: cannot update ("INFRA"."CUST"."SCRP_CODE") to NULL
(status = 1407), SQL <UPDATE "INFRA"."CUST" SET "ORD_ID" = :a2,"MKRT_CODE" = :a8,"CHANN>
Aborting transaction on ./dirdat/pm beginning at seqno 68708 rba 44132192
error at seqno 68708 rba 44132192
Problem replicating INFRA.CUST to INFRA.CUST
Mapping problem with compressed key update record (target format)...
ORD_QTY = 500
ORD_PRICE = 37430
SCRP_CODE =
MKRT_CODE = N
Any inputs / help would be appreciated.
Regards,
Manish

The SCRP_CODE column has a NOT NULL constraint. The ORA-01407 error is telling you that you cannot update or set a value for this column to null because of the constraint. This has absolutely nothing to do with an index. You can use a marker/sentinel value in lieu of using NULL. For a numeric field, where everything is positive, a negative value (-1) can be decoded as meaning null. For a character field, a code such as NA can represent NULL.
This also has nothing to do (directly) with GoldenGate failing because of this error. The underlying SQL statement will fail everywhere, regardless of the tool or application. It is not a case of failing only in GoldenGate.

Facing problem in xml schema xsd file registration

Hi,
i am facing problem in xml schema xsd file registration when
the number of column is more. It is showing persing error.
if i am deleting few column from xsd file . It is working otherwise
showing error. Is there any solution for that please suggest me.
The Error is
ORA-31011:XML parsing failed
ORA_19202: Error occurred in XML processing
LPX-00230 : (message vary time to time-like invalid tag ending etc.)
Regards
Manoranjan
and thanks in advance

Where is you XML coming from. Are you sure it's valid. If you are hard coding it as a SQL String constant are you hitting the 4k / 32K limit on the size of SQL / PL/SQL constant. Have you tried loading the content from a bfile..

Problem with database schema objects in the entity object wizard

Hi All,
When creating a new entity object, I am facing a problem with database schema objects in the entity object wizard, database schema objects (check boxes for tables,synonyms...) are disabled. Actually I am using a synonym but I am not able to select the synonym check box.
Can any of you folks tell me how to enable the database schema objects (check boxes for tables,synonyms...).
Thanks in Advance.
Raja.M

Make sure your using rite version of jdeveloper..
Make sure your using apps schema and check whether your able perform DML operations in the schema vis sql developer.
--Prasanna

Validation XML documnet with XML Schema in PL/SQL

Hello,
can someone please explain
How to validate an XML document with XML schema using PL/SQL code (with out writing Java code).
Thanks for your Help in Advance
Surendra.

see the posting: Schema validation routine?
regards, Bart

Dynamic Table with XML Schema

Hi, I am new to livecycle and wondering if there is any sample for setting up the dynamic table with XML schema so I can access the data through workbench's xpath. thanks.

Ivor,
Take a look at the samples shipped with Designer. For 8.2.1 release take a look at
C:\Program Files\Adobe\LiveCycle Designer ES\8.2\EN\Samples\Forms\Purchase Order\Schema\Schema\Purchase Order.xsd
and the form samples.
Otherwise, forward a request to [email protected] I would be happy to send you a sample XDP with a dynamic table and a schema.
Steve

Has anybody tried creating and validating a XML doc with XML Schema?

Hi,
Has anybody tried creating and validating a XML doc with XML Schema?

With XMLBeans, an XML document may be created from and validated with an XML schema.

Mapping problem with XML scheme

Similar Messages

Maybe you are looking for