ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Poitras Christian" <Christian.Poit...@ircm.qc.ca>
Subject RE: URGENT Cause: java.sql.SQLException: invalid name pattern: LXDV.T_FIN_DETAILS_TYPE
Date Thu, 13 Jul 2006 12:53:46 GMT
Can you post your sqlmap file?
 
If your type is userdefine, then you should (maybe must) define a
TypeHandler for your type. Do you use one?
 
Chris

________________________________

From: chaithanya ibatis [mailto:chaithanya.ibatis@gmail.com] 
Sent: Thursday, 13 July 2006 08:01
To: user-java@ibatis.apache.org
Subject: URGENT Cause: java.sql.SQLException: invalid name pattern:
LXDV.T_FIN_DETAILS_TYPE


HI,

        when i use a Type (userdefined) in oracle as OUT parmaters in
procedure. i have got this problem. can any one tell me what is the
exact cause for these.
i have these type defined outside the package. and procedure is also in
outside package. what is the reason for this error..and how can we solve
it? 


The error occurred in orderProcessingSqlMap.xml.  
--- The error occurred while executing query procedure.  
--- Check the {  call LVL$ECOM_SERVICE_PACK.get_financial_details_proc(
?,?,?,?,?,?,? ) }.  
--- Check the output parameters (register output parameters failed).  
--- Cause: java.sql.SQLException: invalid name pattern:
LXDV.T_FIN_DETAILS_TYPE; nested exception is
com.ibatis.common.jdbc.exception.NestedSQLException :   
--- The error occurred in orderProcessingSqlMap.xml.  
--- The error occurred while executing query procedure.  
--- Check the {  call LVL$ECOM_SERVICE_PACK.get_financial_details_proc(
?,?,?,?,?,?,? ) }.  
--- Check the output parameters (register output parameters failed).  
--- Cause: java.sql.SQLException: invalid name pattern:
LXDV.T_FIN_DETAILS_TYPE
    at org.jboss.ejb.plugins.LogInterceptor.handleException(
LogInterceptor.java:386)
    at
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196)
    at
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryF
inderInterceptor.java:122)
    at
org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
    at org.jboss.ejb.Container.invoke(Container.java:873)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:245)
    at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
    at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JR
MPInvoker.java:805)
    at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:406
)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a :39)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java
:261)
    at sun.rmi.transport.Transport$1.run(Transport.java:148)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages
(TCPTransport.java:460)
    at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.ja
va:701)
    at java.lang.Thread.run(Thread.java:534)



Regards,
Chaithanya


Mime
View raw message