Invalid Handle SQL Exception

Everytime I call this method from my JSP page, I get the error Invalid Handle. I changed my query statement at the most bottom part to a hard-coded update statement (this one update wirtech.orders_temp set BOOKCODE ='12345678', QUANTITY = '150', SUPPLIER = 'rain', STAT = 'pending', FULFILLED = '0', CONSOLIDATED = '1', CONSOLIDATEID ='1' where POID = '10003) but i still get that error. I traced my program and found out the error comes out at After System.out.println("hereba2"+query);. That's the line before stmt.executeupdate(query); at the bottom part of the consolidatePOS method.
Please help, we've been stuck here for one week already.
     public void consolidatePOS(Vector v, String code)
          try{
               String poidfinal = "";
               int y = 0;
               int qty = 0;
               Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
               con = DriverManager.getConnection(url, username, password);
            stmt = con.createStatement();
            System.out.println("before big while."+v.size());
               while(y<v.size())
            query = "select QUANTITY from wirtech.orders_temp where POID = '"+v.elementAt(y)+"'";
            System.out.println("first stmt.execute");
            rs=stmt.executeQuery(query);
            System.out.println("inside medium while.");
            while (rs.next())
                 System.out.println("inside small while.");
                 qty = qty + rs.getInt("QUANTITY");
            if(y == v.size()-1)
                 poidfinal = ""+v.elementAt(y);
            y++;
            rs.close();
            System.out.println("after big while.");
            int ea = getConsolidateID();
            System.out.println("ea"+ea);
            System.out.println("here ba/!?");
            query = "update wirtech.orders_temp set BOOKCODE ='12345678', QUANTITY = '150', SUPPLIER = 'rain', STAT = 'pending', FULFILLED = '0', CONSOLIDATED = '1', CONSOLIDATEID ='1' where POID = '10003'";
            System.out.println("here ba2"+query);
            stmt.executeUpdate(query);
            System.out.println("after big while. LASTT");
            stmt.close(); con.close();
            } catch(Exception ex) {
                 System.out.println("error in consolidatePOS()" + ex);     
          public int getConsolidateID()
          {int x =0;
               try {
            Class.forName(driver);
            con = DriverManager.getConnection(url, username, password);
            stmt = con.createStatement();
            query = "SELECT COUNT(DISTINCT CONSOLIDATEID) AS count FROM wirtech.orders_temp";
            rs = stmt.executeQuery(query);
            while (rs.next()) {
                x = rs.getInt("count");
            rs.close();
            stmt.close();
            con.close();
        } catch (Exception e) {
            System.out.println("getTransactionCount has an Exception: " + e);
        }

This is a complete guess! ... perhaps the
rs.close();also closes the Statement (or invalidates it) which you use later to execute the update. The API does not seem to indicate this though:
void close()
           throws SQLException
    Releases this ResultSet object's database and JDBC resources immediately instead of waiting for this to happen when it is automatically closed.
    Note: A ResultSet object is automatically closed by the Statement object that generated it when that Statement object is closed, re-executed, or is used to retrieve the next result from a sequence of multiple results. A ResultSet object is also automatically closed when it is garbage collected. But perhaps it may still be worthwhile seeing if removing that close will fix the problem.

Similar Messages

  • How to handle sql exceptions properly

    Hi,
    Using Jdev 11.1.1.1.0 and JPA/Toplink
    Our application is used to modify a number of different tables. The tables are mapped in EJB entities and are exposed in session beans which calls the proper methods from the DAOs. We use ADF Rich components in our view project and we have a lot of validation for preventing primary key violations etc. But obviously we can't control everything and we need some exception handling. As it is now, if e.g an sql exception occurs, it will pop up a huge error dialog with the stack trace and the page rendering will fail etc and sometimes needs to restart.
    So, I'm not sure how to approach this. How do we catch these exceptions, notify the user, and stop the page rendering so that it doesn't completely shut down...I've searched around and found some useful information, but since we've never done this before it's a little hard to put things together. Could you please give me some easy examples for this?
    Thank you!
    André

    Hi, thanks for your reply.
    Yes, I have tried to override both getDisplayMessage and reportException. I now used the exact same code as in the example you referred to, and still I get the same result.
    So just to make it clear... If do an insert that causes integrity constraint violation, I get in my console:
    Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint violated
    Error Code: 1
    Call: INSERT INTO etc etc... When this happens, a huge popup appears in my page:
    javax.ejb.EJBException: BEA1-002236FD9E083057A4BD: weblogic.transaction.internal.AppSetRollbackOnlyException
         at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:551)
         at weblogic.transaction.internal.TransactionManagerImpl.setRollbackOnly(TransactionManagerImpl.java:319)
         at weblogic.transaction.internal.TransactionManagerImpl.setRollbackOnly(TransactionManagerImpl.java:312)
         at org.eclipse.persistence.transaction.JTATransactionController.markTransactionForRollback_impl(JTATransactionController.java:145)
         at org.eclipse.persistence.transaction.AbstractTransactionController.markTransactionForRollback(AbstractTransactionController.java:196)
         at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.rollbackTransaction(UnitOfWorkImpl.java:4486)
         at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1351)
         at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitToDatabase(RepeatableWriteUnitOfWork.java:468)
         at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1398)
         at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.issueSQLbeforeCompletion(UnitOfWorkImpl.java:3022)
         at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.issueSQLbeforeCompletion(RepeatableWriteUnitOfWork.java:224)
         at ...................................etc etcThis is what I want to replace with an understandable message to the user. And this is what the custom error handler should do right?? There must be something I have misunderstood...

  • How To Handle SQL Exceptions in  Session EJB Bean

    Hi,
    we are working on toplink JPA. My use case is I have an emp table with columns as "empid" , "emp name" , "job" with "empid" as primary Key. Here I'm creating a record in the Database by using a jspx page. Here My problem is when I'm entering a duplicate value for the empid I'm getting "ORA-00001: unique constraint (constraint_name) violated" . I'm able to catch the exception in the jspx backing bean where I'm calling the JPA insert method, But i could not catch the exception in the sessionEJB Bean. Is there any way to catch such exception in the sessionEJB.
    could anyone help me out.
    Thanks in Advance.
    regards,
    PrapanSol

    You should be able to call flush on your EntityManager in your SessionBean to trigger the exception.
    Note that the transaction will still be rolled back even if you catch this exception.

  • How To Handle SQL Exceptions in JPA

    Hi,
    we are working on toplink JPA. My use case is I have an emp table with columns as "empid" , "emp name" , "job" with "empid" as primary Key. Here I'm creating a record in the Database by using a jspx page. Here My problem is when I'm entering a duplicate value for the empid I'm getting "ORA-00001: unique constraint (constraint_name) violated" . I'm able to catch the exception in the jspx backing bean where I'm calling the JPA insert method, But i could not catch the exception in the sessionEJB Bean. Is there any way to catch such exception in the sessionEJB.
    could anyone help me out.
    Thanks in Advance.
    regards,
    PrapanSol

    You should be able to call flush on your EntityManager in your SessionBean to trigger the exception.
    Note that the transaction will still be rolled back even if you catch this exception.

  • Invalid Descriptor Index (SQL exception)

    Hi Defts,
    im developing an application using swings, im getting an Invalid Descriptor Index (SQL exception). I have given my code below kindly help me out.
    private void formWindowActivated(java.awt.event.WindowEvent evt) {                                    
    // TODO add your handling code here:
    try
    Class.forName("sun.jdbc.odbc.JdbcOdbc");
    Connection con = DriverManager.getConnection("jdbc:odbc:tourismdatasource", "sa", "");
    String sel= "select * from tab_places where place_ID=?";
    PreparedStatement ps=con.prepareStatement(sel);
    ps.setString(1, jTextField4.getText().toString().trim());
    ResultSet rs=ps.executeQuery();
    if(rs.next())
    jTextField1.setText(rs.getString("place_name").toString());
    jTextField2.setText(rs.getString("state").toString());
    jTextField3.setText(rs.getString("category").toString());
    jTextArea1.setText(rs.getString("place_des").toString());
    catch(SQLException se){JOptionPane.showMessageDialog(null, se.getMessage());}
    catch(ClassNotFoundException ce){JOptionPane.showMessageDialog(null, ce.getMessage());}
    }

    It would help to know what statement is throwing the exception. The stack trace tells you that.
    As a guess the "select *" is returning the columns in a specific order. You are not calling getString() in that order though.
    Or one of the getString() values is wrong.
    And get rid of the ToString() calls on the getString() methods - they are already strings.

  • Invalid Handle Exception grr.

    I get this every time i try to update my database. not when i read from it, that goes error free but writing to it, ug. Here's whats goin on:
    the setup for the table is:
    Verb Type
    String Integer
    Con is the Connection that is always successful when used to read data
    the Method FindData returns "Yes" if the verb exists in the table and "No" if it doesn't and yes i have my reasons for making it return a string instead of a boolean
    Command is a Statement: Statement Command = Con.createStatement();
    Update is a String
    i is an int
    if (FindData(Con, Verb).compareTo("No") == 0)
         Update = "insert into [Sheet1$] (Verb, Type) values('"+Verb+"', "+Integer.parseInt(Data)+")";
         System.out.println("Update: "+Update);
         i = Command.executeUpdate(Update);
         if (i == 1) System.out.println("Success!!!"); else System.out.println("Failed");
         Command.close();
         Con.close();
         System.out.println("EXISTS:: "+FindData(Con, Verb));                    
    here's what i get as output:
    ----jGRASP exec: java UpdateData
    Update: insert into [Sheet1$] (Verb, Type) values('Mentir', 1)
    Invalid handle
    ----jGRASP: operation complete.
    Which means it throws an exception at the i = Command.executeUpdate(Update); line and doesn't go further than that.
    Does anyone know what this function even means?
    Does anyone know how to fix this?
    if you need more information pleas let me know
    Thanks, Lateralus

    yep it's an excel driver that allows you to connect to excel databases. here's my getConnection function:
    public static Connection getConnection(String FilePath, String FileName)
         String Driver = "";
         String Url = "";
         String Username = "";
         String Password = "";
         Connection Con = null;
         try
              Driver = "sun.jdbc.odbc.JdbcOdbcDriver";
              Url = "jdbc:odbc:Excel Files;DBQ=";
              Url += FilePath+"\\"+FileName;
              Username = "";
              Password = "";
              Class.forName(Driver); // load JDBC-ODBC driver
              return DriverManager.getConnection(Url, Username, Password);
         catch (Exception e) {System.out.println("getConnection:  "+e.getMessage());}
         return(Con);
    }

  • Invalid Handle Exception-What is the reason?

    I face with "Invalid Handle exception" (SQLException) while using the following code.
    Could anybody tell me the possible reasons/Situation the error rise?
    stmt = conn.createStatement();
    ResultSet rs = stmt.executeQuery(SQLStmt);
         if(rs!=null){
    ResultSetMetaData rsm = rs.getMetaData();
         int totalcols = rsm.getColumnCount();
         Vector temp;
         while (rs.next()) {
         Vector temp = new Vector();
         for (int i = 1; i <= totalcols; i++) {
              String value = rs.getString(i);
              if (value == null) {
              value = "";
         temp.addElement(value);
         }//for loop ends here
         valueVector.addElement(temp);
         rs.close();
         stmt.close();     
    Thank you all

    Vector temp;
    while (rs.next()) {
    Vector temp = new Vector();Are you sure that this is the code you are running? The reason I ask is that I'm pretty sure that it won't compile, at least under JDK1.4. You should get a compile error something like "temp is already defined".
    If thats not the problem you need to find out on which line the error actually occurs. You can get this from the exception by calling the printStackTrace() method.
    Col

  • Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.Invalid object name 'Webs'.

    SP 2013 Server + Dec 2013 CU. Upgrading from SharePoint 2010.
    We have a web application that is distributed over 7-8 content databases from SharePoint 2010. All but one database are upgradable. However, one database gives:
    Invalid object name 'Webs'.
    while running Test-SPContentDatabase or Mount-SPContentDatabase.
    EventViewer has the following reporting 5586 event Id:
    Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.Invalid object name 'Webs'.
    After searching a bit, these links do not help:
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/fd020a41-51e6-4a89-9d16-38bff9201241/invalid-object-name-webs?forum=sharepointadmin
    we are trying PowerShell only.
    http://blog.thefullcircle.com/2013/06/mount-spcontentdatabase-and-test-spcontentdatabase-fail-with-either-invalid-object-name-sites-or-webs/
    In our case, these are content databases. This is validated from Central Admin.
    http://sharepointjotter.blogspot.com/2012/08/sharepoint-2010-exception-invalid.html
    Our's is SharePoint 2013
    http://zimmergren.net/technical/findbestcontentdatabaseforsitecreation-problem-after-upgrading-to-sharepoint-2013-solution
    Does not seem like the same exact problem.
    Any additional input?
    Thanks, Soumya | MCITP, SharePoint 2010

    Hi,
    “All but one database are upgradable. However, one database gives:
    Invalid object name 'Webs'.”
    Did the sentence you mean only one database not upgrade to SharePoint 2013 and given the error?
    One or more of the following might be the cause:
    Insufficient SQL Server database permissions
    SQL Server database is full
    Incorrect MDAC version
    SQL Server database not found
    Incorrect version of SQL Server
    SQL Server collation is not supported
    Database is read-only
    To resolve the issue, you can refer to the following article which contains the causes and resolutions.
    http://technet.microsoft.com/en-us/library/ee513056(v=office.14).aspx
    Thanks,
    Jason
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Jason Guo
    TechNet Community Support

  • First Chance exception in build.exe(NTDLL.DLL);0xC0000008:Invalid Handle

    Hi Michael,
                               I am using WINDOWS XP with SP2 ; I am facing a problem after installing Sp6 for VC++
                 First Chance exception in build.exe(NTDLL.DLL);0xC0000008:Invalid Handle
         Please Help me out for this Michael.
    Thanks & Regards,
    Rakesh
    Rakesh

    Howdy Rakesh,
    I'm not sure who Michael is, but you might want to try the MSDN or the MSDN forum for general VC++ help.
    Warm regards,
    pBerg

  • Portlet Invalid handle exception -- URGENT PLEASE HELP

    I am deploying our Portal application and portlets in a clustered environment. We have three machines and following weblogic servers are started in each machine:
    Machine1 - Admin Server
    Machine2 - Portal1, Portlet1
    Machine3 - Portal2, Portlet2
    Portlets are deployed on portlet servers (portlet 1 and portlet 2). When I deployed the Portal application I intentionally registered portlet producer pointing to 127.0.0.1:8889, thinking that it will work for both portals since the portlet server is in same machine as well..
    So my assumption is :
    Portal1 will always load portlet from Portlet1 server and
    Portal2 will always load portlet from Portlet2 server
    but I am getting following error now... don;t have a clue what to do.. This is very urgent, I am working over the weekend over this.. any help would be highly appreciated..
    Line: -----
    <Apr 23, 2011 6:17:07 PM EDT> <Error> <oracle.portlet.client.connection.wsrp.HTTPClientTransport> <WCS-40152> <A request to the producer URL "http://127.0.0.1:8889/ApplicationAccess/portlets/WSRP_v2_Markup_Service" resulted in a status 500 response with fault string "Invalid handle "C:f5163bc7-4caa-4d4f-b031-cf475ecd099f".; nested exception is:
         oracle.portlet.producer.container.ContainerObjectNotFoundException: Object named "registration" could not be found in the persistent store.". The fault code given was "{urn:oasis:names:tc:wsrp:v2:types}InvalidRegistration". The producer generated a timestamp of 2011-04-23T18:17:06.217-04:00 and associated the following stack trace with the fault message: com.bea.wsrp.faults.InvalidRegistrationException: Invalid handle "C:f5163bc7-4caa-4d4f-b031-cf475ecd099f".; nested exception is:
         oracle.portlet.producer.container.ContainerObjectNotFoundException: Object named "registration" could not be found in the persistent store.
         at com.bea.wsrp.producer.handlers.management.ProducerDataStoreManager$ConfigurationContext.createWsrpFaultException(ProducerDataStoreManager.java:1481)
         at oracle.portlet.producer.container.persistence.WsrpFaultExceptionFactory.createWsrpFaultException(WsrpFaultExceptionFactory.java:43)
         at oracle.portlet.producer.container.persistence.PersistentProducerDataStore.getRegistrationDataContext(PersistentProducerDataStore.java:205)
         at oracle.portlet.producer.container.persistence.ProducerDataStoreImpl.getRegistrationDataContext(ProducerDataStoreImpl.java:225)
         at com.bea.wsrp.producer.handlers.management.ProducerDataStoreManager.initializeRequestContext(ProducerDataStoreManager.java:242)
         at com.bea.wsrp.producer.handlers.management.ProducerDataStoreManager.initializeRegistration(ProducerDataStoreManager.java:210)
         at com.bea.wsrp.producer.handlers.RegistrationHandleFilter.doFilter(RegistrationHandleFilter.java:56)
         at com.bea.wsrp.producer.handlers.AbstractServiceHandler.preprocess(AbstractServiceHandler.java:108)
         at com.bea.wsrp.producer.handlers.AbstractServiceHandler.service(AbstractServiceHandler.java:65)
         at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:349)
         at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:250)
         at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:208)
         at oracle.portlet.server.adapter.web.WSRP_v2_Markup_PortTypeSoapToEndpoint.initCookie(WSRP_v2_Markup_PortTypeSoapToEndpoint.java:281)
         at oasis.names.tc.wsrp.v2.bind.runtime.WSRP_v2_Markup_Binding_SOAP_Tie.invoke_initCookie(WSRP_v2_Markup_Binding_SOAP_Tie.java:295)
         at oasis.names.tc.wsrp.v2.bind.runtime.WSRP_v2_Markup_Binding_SOAP_Tie.processingHook(WSRP_v2_Markup_Binding_SOAP_Tie.java:1448)
         at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:299)
         at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:442)
    Line: -----
    Regards,
    sak007
    Edited by: user469829 on Apr 23, 2011 4:23 PM

    Sak007,
    Did u get the solution for this issue? I am also facing the similar kind of issue.
    I have a portal server, that consumes the remote portlet which is deployed on a cluster environment (Server1 and Server2). When i register my remote portlet, sometimes the registration handle holds info about server1 and sometimes it is server2. When the registration handle holds info about Server1, my application is working fine in the portal. Whereas when the registration handle holds the info about Server2. It throws the exception as:
    Invalid handle "C:10.10.0.42:-a3eb70c:130d71f8067:-7ff9".[[
    oracle.portlet.server.containerimpl.ContainerObjectNotFoundException: Object named "registration" could not be found in the persistent store.
    at oracle.portlet.server.containerimpl.persistence.SimplePersistentStorage.get(SimplePersistentStorage.java:47)
    Any pointers will be helpful.
    Note: I have visited the URl posted in above thread and it doesn't solve the issue.
    Thanks.

  • Invalid Handle Exception!

    Background: I have a SQL database created and maintained via MS Access 2003. I use JDBC to connect and interact with this database. So far my program has been able to do everything from querying a table to inserting new rows to deleting others, but has had no luck with updating rows either through the execute()/executeUpdate() methods or the ResulSet updateInt()/UpdateString() methods.
    So currently I'm recieving an Invalid Handle error during runtime for this program. I ran a stack trace and the line that gave the error was where I was creating a ResultSet from an executeQuery(). I'm unsure what Invalid Handle means, and am further baffled at this error since I have another method with the EXACT SAME line for the query and it receives no errors. To put it into better veiw I have my main class/main method, and from there I call a few different methods from this other class I have. I call this one method, works fine; I call this other method a little while afterwards and it has the exact same few lines at the beginning as the previously mentioned method. Suddenly I get this Invalid Handle error. Like I said, the error said it's happening when I'm doing ResultSet rs = stmnt.executeQuery("SELECT columns FROM table WHERE column LIKE 'string'");
    Please help! Thank you!

    i cant ever open adobe or other pdf files im not new to computers but i am far from profficient. when i ask adobe and others about invalid handles, broken ? whatever and dont have permission etc. all i get is silence or blank looks....i think adobe suks very hard and all the rest of this stuff is just terrible and i want to change to linux....i sure wish i knew more but when i ask a lot of people who claim to be knowledgable i find that all they can do is type well and open and parse documents where i know much more about most hardware and software......anyone out there able to help a dyslexic non typer???

  • SQL Exception: Invalid column index while calling stored proc from CO.java

    Hello all,
    I am getting a "SQL Exception: Invalid column index" error while calling stored proc from CO.java
    # I am trying to call this proc from controller instead of AM
    # PL/SQL Proc has 4 IN params and 1 Out param.
    Code I am using is pasted below
    ==============================================
              OAApplicationModule am = (OAApplicationModule)oapagecontext.getApplicationModule(oawebbean);
    OADBTransaction txn = (OADBTransaction)am.getOADBTransaction();
    OracleCallableStatement cs = null;
    cs = (OracleCallableStatement)txn.createCallableStatement("begin MY_PACKAGE.SEND_EMAIL_ON_PASSWORD_CHANGE(:1, :2, :3, :4, :5); end;", 1);
         try
    cs.registerOutParameter(5, Types.VARCHAR, 0, 2000);
                        cs.setString(1, "[email protected]");
                             cs.setString(2, s10);
    //Debug
    System.out.println(s10);
                             cs.setString (3, "p_subject " );
                             cs.setString (4, "clob_html_message - WPTEST" );
                   outParamValue = cs.getString(1);
    cs.executeQuery();
    txn.commit();
    catch(SQLException ex)
    throw new OAException("SQL Exception: "+ex.getMessage());
    =========================================
    Can you help please.
    Thanks,
    Vinod

    You may refer below URL
    http://oracleanil.blogspot.com/2009/04/itemqueryvoxml.html
    Thanks
    AJ

  • Handling the exception in BizTalk WCF-SQL Receive Adapter

    As per Application, BizTalk connecting to SQL Server and executing the SP for polling the data. Occasionally  we are getting Timeout SQL exception in event log.
    Customer is asking why not BizTalk handling this kind of error messages.
    Please let me know how to handle exceptions in WCF Receive location.already i set the properties like Suspend request
    message on failur and  Include exception details in faults
    But the error message is returning in Eventlog and not reaching to biztalk
    one of the error message is
    Another one is :
    DB locks happening in SQL Server

    Yes definitely, you can "Enable routing for failed messages" and subscribed to the failed message.
    Later you can create a send port or orchestration with below filter conditions-
    "ErrorReport.ErrorType == Failed Message" .
    BizTalk demotes all the properties of this message to avoid unwanted subscription and promotes only below mentioned properties under ErrorReport namespace.
    Description
    ErrorType
    FailureCategory
    FailureCode
    InboundTransportLocation
    MessageType
    OutboundTransportLocation
    ReceivePortName
    RoutingFailureReportID
    SendPortName
    Check the below articles which provide good sample for the same.
    error-message-routing-pattern-demo-in-biztalk
    http://mscerts.programming4.us/application_server/biztalk%202009%20%20%20handling%20failed%20messages%20and%20errors.aspx
    Using Failed Message Routing
    You can also setup Backup transport feature, which will only get activated in case of failure.
    You can configure it to send emails as well.
    How to Configure Backup Transport Options for a Send Port
    Which one to choose between the two-
    Using the backup transport for SMTP would allow you to send an email, but that’s normally not a good solution because you’ll just get that message, with no context, and not really know what to do with it.  Failed message routing will let you setup filters
    based on the failures (types, descriptions, etc) and this way you can organize how you handle failures.  If a pipeline validation fails you can send the message to one place to be repaired where as if a transport fails (or something else) it can be handled
    in a different way. 
    https://social.msdn.microsoft.com/Forums/en-US/09256232-d92a-448b-9c8d-db6144afee84/enable-routing-for-failed-messages-versus-backup-transport?forum=biztalkgeneral
    Thanks,
    Prashant
    Please mark this post accordingly if it answers your query or is helpful.

  • While reading from the pl/sql cursor i got "Invalid column index" exception

    Hi,
    I got the "Invalid column index" exception while reading from the cursor.
    Please advice.
    Thanks in advance
    siva

    I suppose one (or more) index in your query is in a bad state.
    Possible solutions: rebuild (with 'ALTER INDEX <index> REBUILD ...')
    drop and recreate (it's the same as above, but a little more long)

  • How to handle sql error exception in view object

    Guys,
             I have view object (with rows fetched from a sql query).
    Say the query in the VO looks like this..
    select plsql_fun(c) from dual
    (Note : the plsql function in the above query can throw an exception in some cases)
    when the plsql function throws a exception, we get sql exception  (oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation)
    Is there any way i can catch this exception and return -1 in the view object...
    Thanks in advance.

    Check out http://www.oracle.com/technetwork/issue-archive/2013/13-mar/o23adf-1897193.html
    Have you tried to surround hte executeQuery  with a try catch block?
    Timo

Maybe you are looking for