Skip to content

Archive for

java.sql.SQLException: invalid name pattern

We are trying to push the data to Oracle EBS via SOAP But We’re getting the below errors

Errors in log file

oracle.apps.fnd.soa.util.SOAException: ServiceProcessingError: Exception returned from JCA Service Runtime. file:/u01/…….soa/PLSQL/4457/XXACE_XXXXXXXX_LOAD.wsdl [ XXACE_XXXXXXXXXLOAD_ptt::XXACE_XXXXXXXXX_LOAD(InputParameters,OutputParameters) ] – WSIF JCA Execute of operation ‘XXACE_XXXXXXXXX_LOAD’ failed due to: Error while converting to a Java array object. Unable to convert the XSD element P_INVOICE_REC whose collection type is APPS.XXACE_XXXXXXXXX_SOA_PKG_XX_6. Cause: java.sql.SQLException: invalid name pattern: APPS.XXACE_XXXXXXX_SOA_PKG_XX_6 [Caused by: invalid name pattern: APPS.XXACE_XXXXXXX_SOA_PKG_XX_6] ; nested exception is: ORABPEL-11801 Error while converting to a Java array object. Unable to convert the XSD element P_INVOICE_REC whose collection type is APPS.XXACE_XXXXXXXXX_SOA_PKG_XX_6. Cause: java.sql.SQLException: invalid name pattern: APPS.XXACE_XXXXXXXXX_SOA_PKG_XX_6 [Caused by: invalid name pattern: APPS.XXACE_XXXXXXXXX_SOA_PKG_XX_6] Check to ensure that the XML data describing the collection matches the definition of the array in the XSD. Contact oracle support if error is not fixable. at oracle.apps.fnd.soa.provider.services.jca.JCAHandler.invoke(JCAHandler.java:173) at oracle.apps.fnd.soa.provider.services.jca.JCAHandler.handleRequest(JCAHandler.java:120) at oracle.apps.fnd.soa.provider.SOAProvider.processMessage(SOAProvider.java:342) at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:958) at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:388) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:396) at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:385) at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:481) at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114) at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96) at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:200) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:734) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:391) at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:908) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:458) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199) at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303) at java.lang.Thread.run(Thread.java:662) org.collaxa.thirdparty.apache.wsif.WSIFException:

Solution :Regenerate the WSDL and deploy

We push the data, its successful.

Please be note : We cloned the data only not entire application files, so that reason the above error occurred.

mailx sender address picks the OS user account instead of sender address

We’re trying to send email from redhat 7 terminal using with below command,

mailx -s “Test mail” mazar@xxxx.com -r ezylebdb@alerts.xxxx.net

But its sender by OS hostname

Solution :

Send by like below

mailx -r ezylebdb@alerts.xxxx.net -s “Test mail” mazar@xxxx.com

 

EBS 12.2.6 Generate Automatically and Enter Manually Options Are Missing In User Management

When you try to reset password for asadmin and other users in User management, Its invisible.

Solution :

 

12.2.6 Reset Password Options: Generate Automatically and Enter Manually Options Are Missing In User Management > Users Page (Doc ID 2260179.1)