java.security.PrivilegedActionException: weblogic.common.ResourceException Oracle SOA

java.security.PrivilegedActionException: weblogic.common.ResourceException: java.security.PrivilegedActionException: weblogic.common.ResourceException: No credential mapper entry found for password indirection user=apps for data source DataSourceName While creating a war file and then deploying on weblogic we get this error. To get ride of this error in Jdeveloper go to application properties and then deployments and then uncheck "Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment" then create WAR file again...

Read More

Error(1,1)mdssys/mdx/componentType.rdf: XML-20108: (Fatal Error) Start of root element expected.

 Error(1,1)mdssys/mdx/componentType.rdf<Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected. Sometimes when we build Oracle SOA project we get the above error. To resolve this issue just go to those file where this error is coming you can see this from compiler and remove those file or add following in those files  <xml version="1.0" encoding="UTF-8"/>  Save it and rebuild the code again and this error will be no more...

Read More

rul-05720 datatype mismatch for test jaxbelement >int Oracle SOA business rule

rul-05720 datatype mismatch for test jaxbelement >int Sometime we face this error while creating business rule. I was facing the same issue with variable that I was using in business rule by removing minOccurs="0" in my schema element. Like below  <xs:element name="netAmount" type="xs:decimal" minOccurs="0" nillable="true"/> just remove the highlighted area and try to create your business rule with newly updated schema. <xs:element name="netAmount" type="xs:decimal"  nillable="true"/> ...

Read More

Oracle SOA Business rule Fact not found in the rule engine working memory

The following error comes sometimes in Oracle SOA suite business rule. Fact not found in the rule engine working memory, rule session execution failed. This is most likely a rule modeling error. I was facing the same issue while working on business rule. The error was coming due to schema issues or namespace issues in schema. If you create a separate application and test this using the same schema the chances of error would be very less. I just created a new XSD with new target namespace and copy pasted the existing elements/complex elements...

Read More