Is this in PowerCenter or IDQ?
In PowerCenter that's "normal" behaviour; you cannot use local namespaces in PowerCenter, that's an old problem.
About IDQ I can't tell.
This is in powercenter. Are you referring to this problem in powercenter 113516 ? Does this still exist in 10.2 as well? We dont have XSD and only XML is there. As per this KB, we tried to define the namespaces in the beginning of the XML file, aliased it with a prefix and tried using the prefixes for elements and attributes in XML. However, it did not work. Will this approach work fine with XSD only?
Please provide your inputs on this.
That's exactly what I meant.
To be honest I don't know for sure whether this applies to XSD files only or to XML files as well, but as the solution given clearly indicates the use of a XSD, I fear that indeed this can be done only if you do have a XSD file and not only a XML.
If I understand you correctly, you don't have a XSD and can't get one as well. So in your case I fear that the only way to deal with this problem is to get rid of this local namespace completely in the XML file.
Does anyone else have a better approach?
An alternative would be to use B2B Data Transformation; it can handle (almost) arbitrarily large and complex XML files and can be embedded in PowerCenter mappings via the so-called Unstructured Data Object, UDO (or Unstructured Data Transformation, UDT, both terms can be used interchangeably). But of course that means extra license costs.
We created the XSD for the XML using XMLSPY tool. Imported the XSD into informatica and it worked fine. We were able to read the data in XML successfully.
Thanks for your help.