Prepared Statement Flooding

Hi Friends,
Need your help to fix this prolonging problem in one of our applications. We observe that the following queries are declared as prepared statements but have dynamic value ROWID in each.
SELECT ROWID, C. * FROM Table1 C WHERE C.VENDORLOGINID = ? AND C.VENDORTYPE = ? AND (ROWID = _ ROWID100)
SELECT ROWID, C. * FROM Table2 C WHERE C.VENDORIDCH = ? AND (ROWID = _ ROWID114)
SELECT ROWID, C. * FROM Table1 C WHERE C.VENDORLOGINIDBASE = ? AND C.VENDORTYPE = ? AND (ROWID = _ ROWID58)
This results in a FLOOD of prepared statements (over 3000) as it is an application with a very large DB.
We found out that a newer version of Ojdbc14.jar (10.2.0.3.0) is available (At present we are shipping the product with 10.2.0.1.0). We tested with this newer jar and found out bind variables are not treated as dynamic variables with this jar file. SQL queries are getting cached as expected.
This new jar file did fix the problem when our DB was 10g for the application (another), but for this current application we are using Oracle 9i.
The same jar file does not seem to be fixing the issue.
Has anybody faced similar issue before?
Ideally the 10g jar file should eb backward compatible but for some reason it is not for this particular problem.
Please can somebody help to get a solution for this problem. Do let me know if you need more information.
Thanks.

Poornima wrote:
Is the prepared statement cache common to all the Connection objects in the Connection Pool or is there a separate cache for each statement in the Connection Pool?There is a separate statement cache for each connection in the pool.
Joe

Similar Messages

Database prepared statements Flooding

Hi Friends,
Need your help to fix this prolonging problem in one of our applications. We observe that the following queries are declared as prepared statements but have dynamic value ROWID in each.
SELECT ROWID, C. * FROM Table1 C WHERE C.VENDORLOGINID = ? AND C.VENDORTYPE = ? AND (ROWID = _ ROWID100)
SELECT ROWID, C. * FROM Table2 C WHERE C.VENDORIDCH = ? AND (ROWID = _ ROWID114)
SELECT ROWID, C. * FROM Table1 C WHERE C.VENDORLOGINIDBASE = ? AND C.VENDORTYPE = ? AND (ROWID = _ ROWID58)
This results in a FLOOD of prepared statements (over 3000) as it is an application with a very large DB.
We found out that a newer version of Ojdbc14.jar (10.2.0.3.0) is available (At present we are shipping the product with 10.2.0.1.0). We tested with this newer jar and found out bind variables are not treated as dynamic variables with this jar file. SQL queries are getting cached as expected.
This new jar file did fix the problem when our DB was 10g for the application (another), but for this current application we are using Oracle 9i.
The same jar file does not seem to be fixing the issue.
Has anybody faced similar issue before?
Ideally the 10g jar file should eb backward compatible but for some reason it is not for this particular problem.
Please can somebody help to get a solution for this problem. Do let me know if you need more information.
Thanks.

This thread is old and undiscussed since first post.
Don't understand why but i got some ideas.
1. First of all, i doubt that this is JDBC issue. JDBC PreparedStatement caching has nothing to do with sharability of SQL statements in Oracle.
If this is JDBC issue, what a silly bug it is... But silly things happen quite often :(
2. I think some cursor-related views like V$SQL_SHARED_CURSOR, V$SQL and V$SQLAREA should be investigated. The notorious bind mismatch can cause unwanted unshareable SQL statements which look exactly same each other.

Prepared Statement too fast?

I have an app that performs thousands of inserts at a time via prepared statements. A batch of insert statements could contain 100's to 10,000's of insert statements in it. When a batch is completed, an execute batch is performed. Now when our users started moving to more data to process they said that the database locked up and they had to restart it( Informix 9.3 using the JDBC driver from IBM ). I switched to using standard executeUpdate() statements and they have not reported any problems yet, but could the prepared statement cause such a problem with the database? I have made sure that the preparedstatement is called once and closed at the end and I have not encountered this problem on my machine, but since my code was the only thing running at the time, I have to assume it was something that I am doing.
One thing to note:
I am inserting into a table that has over a million rows in it and contains about 7 indexes. I know doing an insert on such a big table that is heavily indexed could slow it down, but not to a point that its locking the database.
I do not know how prepared statements send the insert commands to the database, but could they be sent too many at a time and cause a flood of commands to overload the database?
We are evaluating a JDBC driver from a commercial vendor( DataDirect ). Could a more commercial JDBC driver implement this kind of load more efficiently?
Any information would be helpful. Thanks.

That sounds ok unless each item was big (no blobs right?)Correct. all primitive types except for two date values.
There are two possible scenarios. One there were
other processes running which is how the knew exactly
when the server locked up. Two there were no other
processes running so all they know is that it locked
up either during or after your process. If your
process completed then it has nothing to do with your
process. Or does your process run continually (if so
then why would it have not failed before?)It does not run as a daemon, but this process could take several hours. A good run will take 2 hours to process 250,000 source records. The reason they were checking the database is because without proper indexing, this process took over 24 hours. When I first wrote the app, I made the rookie mistake of putting the prepared statements in a while loop and what that did is create soo many locks that it overwhelmed the system, so the customer got use to checking for that to make sure that still was not an issue. I do not do that anymore, but they still check and if there is a locking issue, my code still gets the blame. Also keep in mind I have their production database here and I run the code on my machine and do not get any problems. My main reason for asking these questions is so I don't kill myself trying to figure out why their database is locking up and putting the blame in the wrong place. I rewrote the insert statements to fix the problem when I was not even sure the prepared statements was the problem. I was just checking to see if anyone out here has noticed any problems with using prepared statements at such a high volume.

Use of Prepared Statement in adf

Hi Experts,
I am confused with the Use of prepared statement in adf.
My use case is ,
I have to update a table from every page in my application under certain conditions.
My question is ,
whether I have to create the VO iterator binding in every page and by calling the createinsert and insert the data in to the table or
use a common method in the Application module impl
which is using a prepared statement,(which is not even creating the ViewObject ) like
PreparedStatement st = null;
String sql = "INSERT INTO hr.departments (DEPARTMENT_ID,    DEPARTMENT_NAME,   MANAGER_ID,   LOCATION_ID) VALUES (seq,?,?,?)";
            st=getDBTransaction().createPreparedStatement(sql,0);
            st.setString(1, name);
            st.setString(2, mgr_id);
            st.setString(3, Loc_id);
            st.execute();
getDBTransaction().commit();which is the best approach?
Studio Edition Version 11.1.1.2.0
Ranjith

Ranjith,
Without further understanding the use case, there's not really much difference between the two approaches. In both cases, you'd have a binding in the page definition (either an iterator binding for the VO or a method binding for the AM service method). Both will use bind variables. The main difference I can see is that, depending on how you have configured your AM pooling settings, the VO method will incur fewer parses in the DB because the AM will cache prepared statements for you.
John

Proving prepared statements are being reused

How can I prove that a prepared statement from a JDBC driver is being reused / pooled ?
What essentially I want to do is to have prepared statements reused to reduce hard parsing ... but I also need to prove that the statements are being reused. If I query the statement in V$SQLAREA, the column PARSE_CALLS does not seem to be distinguish between hard parse and soft parse:
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch3204.htm#1126299
I am only interested for now in proving the just ONE statement is being reused ... which mean that the number of hard parses is very low compared to the number of soft parses for that ONE statement.
Regards,
jms
Message was edited by:
jms

Hi,
No, parse calls is all soft and hard parse together. What you would see, if used absolutely correctly, would be 1 hard parse per session and many executions.
But since v$sql is obviously not linked to v$session other than at the time of exection, you see the aggregated parse calls and executions for each cursor. So what you should see is parse calls go up relatively slowly to the number of exections.
However, you can see soft and hard parses using the v$sesstat and v$statname views so you can see soft and hard parses on a session by session basis, be these are again aggregated, so you can't see soft / hard counts per cursor, only the total for a session.
What I see a lot of the time is they don't get it quite right, so hard parses is low but soft parses are high, so they are still parsing when they don't need to, but at least they are binding and using shareable SQL, which is a step in the right direction.
When I say 'they', it is a generic reference to all Java/.Nyet programmers writing front end code where they just don't 'get' parsing and binding because it's just too complicated and hey, SQL Server isn't like this...!
HTH
Chris

When to use prepared statement in java?

Hi all,
If we have query like select * from {tablename} (Here tablename is the variable) then will the use of prepared staement improve the performance? My guess is use of statement in this case is a better option rather than prepared statement as the tablename may change for every other query.I think are not useful if tablename changes.They are useful only when the where clause has dynamic values.

cantor wrote:
Are you sure that your approach is possible? The next example causes exception for me.
PreparedStatement ps = conn.prepareStatement("select * from ?");
ps.setString(1, "TABLE_NAME");
ps.executeQuery();
I didn't say that he should solve it in that way. He should create one prepared statement like this "select a, b, c from tablename1" and another prepared statement when he wants to execute "select d, e, f from tablename2"
>
And as I understand, this code will not improve perfomance (and even will not work). As I said it can.
Prepared statements make possible usage compiled queries inside DB. When DB gets prepared statement call, it need to parse it only once. And it can collect some statistic to improve execution plan. But when table name is not specified, this approach will not work.Yes it might. There are database drivers that can cache prepared statements and it's isn't likely that he executes that query on more than e.g. 20 tables?
The database can also cache compiled statements in a cache.
Kaj

How do I handle NULL returns from prepared statement?

Thanks in advance to all those who respond. As a beginner with Java/JSP/JDBC, I need all the help I can get!
Here's the problem...
I'm using a prepared statement in JSP to query a MySQL database.
If there is a value to return, everything works properly.
If the query returns a NULL (empty set) value, I get the following error:
javax.servlet.ServletException: Before start of result set
Here's the code (no negative comments please...I know I'm violating some conventions! I'll restructure it later. Right now I just need help with handling the NULL case):
<%
Driver DriverAppt = (Driver)Class.forName(MM_test_DRIVER).newInstance();
Connection ConnAppt = DriverManager.getConnection(MM_test_STRING,MM_test_USERNAME,MM_test_PASSWORD);PreparedStatement StatementAppt = ConnAppt.prepareStatement("SELECT lastname FROM appts_pid1 WHERE user_id = " + Recordset1__MMColParam + " AND year = " + yy + " AND month = '" + months[mm] + "' AND date = " + dates[dd] + " AND appttime = '16:15:00'");
ResultSet Appt = StatementAppt.executeQuery();
boolean Appt_isEmpty = !Appt.first();
boolean Appt_hasData = !Appt_isEmpty;
Object Appt_data;
int Appt_numRows = 0;
%>
Thanks for the help!!!

I think I have a better handle on what's occurring here. To cut to the heart of the problem, I'm going to give a very simple example that illustrates what type of error handling I need.
HERE'S THE EXAMPLE:
Let's say that I have a database of users. There are only two columns in the database: user_id and lastname. There are only 2 users, user_id "1" has lastname "Jones" and user_id "2" has lastname "Smith".
I built a very simple web interface that let's a user enter a number to see if there's a lastname associated with that record. The user has no way of knowing if the user_id exists or not, so they may or may not enter a valid number.
If the user enters a valid user_id (in this case "1" or "2"), then the correct lastname is displayed. If the user enters an invalid user_id (in this case, anything other than "1" or "2") then I get the same "Before start of result set" error that I'm getting in my real application.
So, the question is: WHERE IN THIS CODE WOULD I HANDLE THE RETURN OF AN EMPTY SET?
The goal here is to have the sentence say "The user's lastname is .", basically returning null. If there has to be a value, then have the last sentence say "The user's lastname is unknown."
If you can solve this simple example, you'll have also solved the problem with my main application!!!! :-)
Here's the example code:
<%@ page contentType="text/html; charset=iso-8859-1" language="java" import="java.sql.*" errorPage="" %>
<%@ include file="Connections/example.jsp" %>
<%
String Recordset1__MMColParam = "1";
if (request.getParameter("user_id") !=null) {Recordset1__MMColParam = (String)request.getParameter("user_id");}
%>
<%
Driver DriverRecordset1 = (Driver)Class.forName(MM_example_DRIVER).newInstance();
Connection ConnRecordset1 = DriverManager.getConnection(MM_example_STRING,MM_example_USERNAME,MM_example_PASSWORD);
PreparedStatement StatementRecordset1 = ConnRecordset1.prepareStatement("SELECT * FROM test_table WHERE user_id = " + Recordset1__MMColParam + "");
ResultSet Recordset1 = StatementRecordset1.executeQuery();
boolean Recordset1_isEmpty = !Recordset1.next();
boolean Recordset1_hasData = !Recordset1_isEmpty;
Object Recordset1_data;
int Recordset1_numRows = 0;
%>
<html>
<head>
<title>Untitled Document</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body>
<form action="test.jsp" method="get" enctype="application/x-www-form-urlencoded" name="form1" target="_self">
<p> Submit a user id and a lastname will be displayed.</p>
<p>
<input type="text" name="user_id">
<input type="submit" name="" value="Submit">
</p>
</form>
<p>The User's lastname is <%=(((Recordset1_data = Recordset1.getObject("lastname"))==null || Recordset1.wasNull())?"":Recordset1_data)%>.</p>
</body>
</html>
<%
Recordset1.close();
StatementRecordset1.close();
ConnRecordset1.close();
%>
A huge "THANK YOU!!!!" to all those who've helped me here!!!

Connection/ResultSets/Prepared Statement opening and closing

Hi all another question that was sparked by a thread that I recently read. I believe it was duffmo who got the code from jverd. The code I am referring to is to have an open and close connection specified in a Utility or Database class. I wanted to know if there was any issues with having methods that open and close connections/result sets/ preparedStatements. Currently I am putting the finally blocks inside each of my methods. There is obvious benefits to putting the methods in a class on their own (namely code re-use) but I wanted to know if there are any dangers. (This may seem like a dumb question, but I've found from experience it's the things that you don't know that will cost you loads of time).
thanks again.

Hi all another question that was sparked by athread
that I recently read. I believe it was duffmo who
got the code from jverd. Generally speaking it's fine.
But as always you may have some long term design
issues to think about. If you build a simple
framework that consists of one class and that does
all that your program does then great.
Once you start add more complexity though you'll want
to be careful that you aren't reinventing the Spring
wheel or even ending up implementing your own
connection pool. Both of which, judging from posts
here seem to happen from time to time.
So I guess all in all, yes it's much better than
scattering the code all about but depending on what
you are going to be doing with it you may want to
look at the various ORM frameworks to see if they are
really the direction you should be going in.Thanks for the information cotton. I just wanted to make certain that it was a sensible thing to do. When I had first asked about connections I was told they should be opened an closed in the same spot, unfortunately I took that explanation a little too much to heart, and started opening and closing every connection resultset and prepared statement in each of the DAO classes that I was using.
Guess it's going to be a bit of work to refactor, but worth it for the cleaner code that will result.

Pass table name as parameter in prepared Statement

Can I pass table name as parameter in prepared Statement
for example
select * from ? where name =?
when i use setString method for passing parameters this method append single colon before and after of this parameter but table name should be send with out colon as SQL Spec.
I have another way to make sql query in programing but i have a case where i have limitation of that thing so please tell me is it possible with prepared Statment SetXXx methods or not ?
Thanks
Haroon Idrees.

haroonob wrote:
I know ? is use for data only my question is this way to pass table name as parameterI assume you mean "how can I do it?" As I have already answered "is this the way?" with no.
Well, I would say (ugly as it is) String concatenation, or stored procedures.

Could not find prepared statement with handle %.

Greetings. I've seen several posts for this error on the web, but no clear cut answers. I captured the code below in profiler, with the intention of replaying in mgmt studio.
However, the attempt end in the following error: "Could not find prepared statement with handle 612."
declare @p1 int
set @p1=612
declare @p2 int
set @p2=0
declare @p7 int
set @p7=0
exec sp_cursorprepexec @p1 output,@p2 output,N'@P0 int,@P1 int,@P2 int,@P3 int,@P4 bit',N'EXEC dbo.mySproc @P0,@P1,@P2,@P3,@P4 ',4112,8193,@p7 output,219717,95,NULL,1,0
select @p1, @p2, @p7
Something noteworthy is that my sproc only has 5 input parameters, but this makes it look like it has many more.
How do I manipulate the code enough to make it work in mgmt studio? Thanks!
TIA, ChrisRDBA

In profiler you would normally see RPC:Starting and RPC:Completed. The statement shown in RPC staring is what you need to pick because as Erland explained, completed would show "funky" behavior.
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Problem in prepared Statement

hi,
i have used following prepared Statement for the update in database.
Can any one tell me that,How can i use date in following method.
I have 4 field for date as given below:(BOLD shown)
I have used String in that place.
It is not working.
PreparedStatement pstatement = conn.prepareStatement(
"UPDATE sec_mast SET catg_code=?, vou_no=?, vou_date=?, vou_amt=?, due_date1=?, due_date2=?, mat_date=? where sec_no=? ");
pstatement.setInt(1,Integer.parseInt(request.getParameter("catg_code")));
pstatement.setString(2,request.getParameter("vou_no"));
pstatement.setString(3,request.getParameter("vou_date"));
pstatement.setInt(4,Integer.parseInt(request.getParameter("vou_amt")));
pstatement.setString(5,request.getParameter("due_date1"));
pstatement.setString(6,request.getParameter("due_date2"));
pstatement.setString(7,request.getParameter("mat_date"));
pstatement.setInt(8,Integer.parseInt(request.getParameter("sec_no")));
int rowCount = pstatement.executeUpdate();
conn.setAutoCommit(false);
conn.setAutoCommit(true);
plz help me

thanx for u r reply.
MY whole code is shown as below:
This page is for the updating the values in database..
<html>
<body>
<table>
<tr>
<td>
<%@ page import="javax.servlet.*" %>
<%@ page import="javax.servlet.http.*" %>
<%@ page language="java" import="java.sql.*" %>
<%
try {
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection conn=DriverManager.getConnection("jdbc:odbc:pf","scott","ttlscott");
System.out.println("got connection");
%>
<%
String action = request.getParameter("action");
// Check if an update is requested
if (action != null && action.equals("update")) {
conn.setAutoCommit(false);
PreparedStatement pstatement = conn.prepareStatement(
"UPDATE sec_mast SET sec_no=? , catg_code=?, face_val=?, pur_val=?, int_paid=?, int_recd=?, brkr=?, vou_no=?, vou_date=?, vou_amt=?, due_date1=?, due_date2=?, lf_no=?, mat_date=? where tot_val=? ");
pstatement.setInt(1,Integer.parseInt(request.getParameter("sec_no")));
pstatement.setInt(2,Integer.parseInt(request.getParameter("catg_code")));
pstatement.setInt(3,Integer.parseInt(request.getParameter("face_val")));
pstatement.setInt(4,Integer.parseInt(request.getParameter("pur_val")));
pstatement.setInt(5,Integer.parseInt(request.getParameter("int_paid")));
pstatement.setInt(6,Integer.parseInt(request.getParameter("int_recd")));
pstatement.setInt(7,Integer.parseInt(request.getParameter("brkr")));
pstatement.setString(8,request.getParameter("vou_no"));
pstatement.setString(9,request.getParameter("vou_date"));
pstatement.setInt(10,Integer.parseInt(request.getParameter("vou_amt")));
pstatement.setString(11,request.getParameter("due_date1"));
pstatement.setString(12,request.getParameter("due_date2"));
pstatement.setString(13,request.getParameter("lf_no"));
pstatement.setString(14,request.getParameter("mat_date"));
pstatement.setInt(15,Integer.parseInt(request.getParameter("tot_val")));
int rowCount = pstatement.executeUpdate();
conn.setAutoCommit(false);
conn.setAutoCommit(true);
%>
<%
// Create the statement
Statement statement = conn.createStatement();
ResultSet rs = statement.executeQuery
("SELECT * from sec_mast ");
%>
<%
// Iterate over the ResultSet
while ( rs.next() ) {
%>
<tr>
<form action="security_update.jsp" method="get">
<input type="hidden" value="update" name="action">
<td><input value="<%= rs.getInt("sec_no") %>" name="sec_no"></td>
<td><input value="<%= rs.getInt("catg_code") %>" name="catg_code"></td>
<td><input value="<%= rs.getInt("face_val") %>" name="face_val"></td>
<td><input value="<%= rs.getInt("pur_val") %>" name="pur_val"></td>
<td><input value="<%= rs.getInt("int_paid") %>" name="int_paid"></td>
<td><input value="<%= rs.getInt("int_recd") %>" name="int_recd"></td>
<td><input value="<%= rs.getInt("brkr") %>" name="brkr"></td>
<td><input value="<%= rs.getInt("tot_val") %>" name="tot_val"></td>
<td><input value="<%= rs.getString("vou_no") %>" name="vou_no"></td>
<td><input value="<%= rs.getDate("vou_date") %>" name="vou_date"></td>
<td><input value="<%= rs.getInt("vou_amt") %>" name="vou_amt"></td>
<td><input value="<%= rs.getDate("due_date1") %>" name="due_date1"></td>
<td><input value="<%= rs.getDate("due_date2") %>" name="due_date2"></td>
<td><input value="<%= rs.getString("lf_no") %>" name="lf_no"></td>
<td><input value="<%= rs.getDate("mat_date") %>" name="mat_date"></td>
<td><input type="submit" value="Update"></td>
</form>
</tr>
<%
%>
</table>
<%
// Close the ResultSet
rs.close();
// Close the Statement
statement.close();
// Close the Connection
conn.close();
} catch (SQLException sqle) {
out.println(sqle.getMessage());
} catch (Exception e) {
out.println(e.getMessage());
%>
</td>
</tr>
</body>
</html>

Application is in 'Prepared' state instead of 'Active' state.

I m using below code to deploy an application on weblogic 11g
import java.io.*;
import java.util.Hashtable;
import weblogic.deploy.api.tools.*; //SesionHelper
import weblogic.deploy.api.spi .*; //WebLogicDeploymentManager
import javax.enterprise.deploy.spi.TargetModuleID;
import javax.enterprise.deploy.spi.status.ProgressObject;
import javax.enterprise.deploy.spi.status.DeploymentStatus;
import javax.enterprise.deploy.shared.ModuleType;
import javax.enterprise.deploy.spi.Target;
import javax.management.MBeanServerConnection;
import javax.management.remote.JMXConnector;
import javax.management.remote.JMXConnectorFactory;
import javax.management.remote.JMXServiceURL;
import javax.naming.Context;
public class WeblogicTest
     public static void main(String ar[]) throws Exception
          System.out.println("Start Deploying");
          WebLogicDeploymentManager deployManager=SessionHelper.getRemoteDeploymentManager( "t3", "10.0.0.47", "7003", "weblogic",
          "weblogic123");
          System.out.println("Deploy Manager : " + deployManager);
          DeploymentOptions options = new DeploymentOptions();
          options.setName("TC33");          //TODO
          Target targets[] = deployManager.getTargets();
          System.out.println("Target : " + targets);
          Target deployTargets[]=new Target[1];
          int temp=0;
          for (temp=0; temp < targets.length; temp++){
               if(targets[temp].getName().equals("managed_2")){
                    deployTargets[0]=targets[temp];
          ProgressObject processStatus=deployManager.distribute(deployTargets, new
                    File("\\\\10.0.0.47\\Builds\\VertexTest\\domain1\\tc3.3b74_6.2.2011.19\\test.ear"), null,options);
          DeploymentStatus deploymentStatus=processStatus.getDeploymentStatus() ;
          System.out.println("UnDeploymentStayus.getMessage(): "+deploymentStatus.getMessage() );
System.out.println("Start sleeping");
          Thread.sleep(10000);
System.out.println("End sleeping");
          TargetModuleID[] targetModuleIDs=deployManager.getAvailableModules(ModuleType.EAR, deployTargets);
          System.out.println("\n\t targetModuleIDs [] = "+targetModuleIDs);
          for (int j=0;j<targetModuleIDs.length;j++){
               System.out.println("\n\t "+targetModuleIDs[j]);
               deployManager.start(targetModuleIDs);
               deployManager.start(targetModuleIDs);
}This code successfully deployed my application on desired managed server but my application is in 'Prepared' state instead of 'Active' state.
Currently, I have to manually update my application's state to 'Active'.
Can anybody tell me if I am missing something in my code.

It actually looks fine, but what could be the problem is the time to deploy your application and
the sleep command of ten seconds. When your sleep is finished, is your application deployment finished?
Maybe you can add a while loop using the isCompleted method of the DeploymentStatus class, for example,
ProgressObject processStatus = deployManager.distribute(deployTargets, new File("\\\\10.0.0.47\\Builds\\VertexTest\\domain1\\tc3.3b74_6.2.2011.19\\test.ear"), null,options);
DeploymentStatus deploymentStatus = processStatus.getDeploymentStatus() ;
while (!deploymentStatus.isCompleted()) {
    Thread.sleep(1000);
TargetModuleID[] targetModuleIDs = deployManager.getAvailableModules(ModuleType.EAR, deployTargets);
System.out.println(targetModuleIDs);
if (targetModuleIDs.length > 0) {
    deployManager.start(targetModuleIDs);
}Or something else along those lines.

Batch updates with callable/prepared statement?

The document http://edocs.bea.com/wls/docs70/oracle/advanced.html#1158797 states
that "Using Batch updates with the callableStatement or preparedStatement is
not supported". What does that actually mean? We have used both callable and prepared
statements with the batch update in our current project (with the Oracle 817 db).
It seems to run ok anyway.

So the documentation should state that batch updates do not work ok in old versions
of JDriver for Oracle, BUT work correctly with newer version. Additionally, batch
updates work ok when used with Oracle supplied jdbc-drivers?
"Stephen Felts" <[email protected]> wrote:
Support for addBatch and executeBatch in the WLS Jdriver for Oracle was
added in 7.0SP2.
It was not available in 6.X or 7.0 or 7.0SP1.
"Janne" <[email protected]> wrote in message news:3edb0cdc$[email protected]..
The document http://edocs.bea.com/wls/docs70/oracle/advanced.html#1158797
states
that "Using Batch updates with the callableStatement or preparedStatementis
not supported". What does that actually mean? We have used both callableand prepared
statements with the batch update in our current project (with the Oracle817 db).
It seems to run ok anyway.

Prepared statements related problem

Hi,
i have this strange problem with prepared statements i think.
When i execute an insert query without prepared statements i works fine (always), when i use prepared statements it sometimes gives a db error saying i'm trying to insert a null value.
The problem is that I'm not!!!
If i were why does it work sometimes?
It may be a bug but i don't know where to look for it... is it a prepared statements, application server or db2 problem?

This is the code...
     public void insertArticolo(Articolo item) throws Exception {
          PreparedStatement ps = null;
               try {
                    StringBuffer sql = new StringBuffer("insert into RUW.RUWT1_ARTICOLO (");
                    sql.append("C_ENTE, C_CONCESSIONE,N_ANNO_RUOLO,N_PROGR_RUOLO,N_PARTITA,N_PROGR_PARTITA,N_PROGR_TRIBUTO, ");
                    sql.append("C_TRIBUTO, C_TIPO_UFF,C_UFFICIO,");
                    sql.append("C_TIPO_IMP, N_ANNO_IMP, L_CARICO, S_ARTICOLO");
                    sql.append(") values (");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?" + ", ");
                    sql.append("?");
                    sql.append(")");
                    ps = connectionCreatePreparedStatement(sql.toString());
                    System.out.println(sql.toString());
                    KeyArticolo keyArticolo = item.getKeyArticolo();
                    KeyPartita keyPartita = keyArticolo.getKeyPartita();
                    Ente ente = keyPartita.getKeyRuolo().getEnte();
                    System.out.println("/"+ ente.getCodEnte()+ "/");
                    System.out.println("/"+ keyPartita.getKeyRuolo().getConcessione().getCodConc()+ "/");
                    System.out.println("/"+ keyPartita.getKeyRuolo().getAnnoRuolo()+ "/");
                    System.out.println("/"+ keyPartita.getKeyRuolo().getProgRuolo()+ "/");
                    System.out.println("/"+ keyPartita.getNumPartita()+ "/");
                    System.out.println("/"+ keyPartita.getProgPartita()+ "/");
                    System.out.println("/"+ item.getKeyArticolo().getProgArticolo()+ "/");
                    System.out.println("/"+ item.getCodEntrata()+ "/");
                    System.out.println("/"+ ente.getTipoUfficio()+ "/");
                    System.out.println("/"+ ente.getCodUfficio()+ "/");
                    System.out.println("/"+ item.getTipoImposta()+ "/");
                    System.out.println("/"+ item.getAnnoImposta()+ "/");
                    System.out.println("/"+ item.getCaricoOrigine()+ "/");
                    if (item.getDescArticolo().equals("")) {
                         item.setDescArticolo(" ");
                    System.out.println("/"+ item.getDescArticolo()+ "/");
                    ps.setLong(1,ente.getCodEnte());
                    ps.setLong(2,keyPartita.getKeyRuolo().getConcessione().getCodConc());
                    ps.setLong(3,keyPartita.getKeyRuolo().getAnnoRuolo());
                    ps.setLong(4,keyPartita.getKeyRuolo().getProgRuolo());
                    ps.setLong(5,keyPartita.getNumPartita());
                    ps.setLong(6,keyPartita.getProgPartita());
                    ps.setLong(7,item.getKeyArticolo().getProgArticolo());
                    ps.setString(8,item.getCodEntrata());
                    ps.setString(9,ente.getTipoUfficio());
                    ps.setString(10,ente.getCodUfficio());
                    ps.setString(11,item.getTipoImposta());
                    ps.setLong(12,item.getAnnoImposta());
                    ps.setLong(13,item.getCaricoOrigine());
                    ps.setString(14,item.getDescArticolo());
                    ps.executeUpdate();
               catch (Exception e) {
                    e.printStackTrace();
                    connectionCloseStatement(ps);
                    throw e;
          }and this is the result of the systemout
[10/03/06 14.07.07:051 CET] 76357635 SystemOut O insert into RUW.RUWT1_ARTICOLO (C_ENTE, C_CONCESSIONE,N_ANNO_RUOLO,N_PROGR_RUOLO,N_PARTITA,N_PROGR_PARTITA,N_PROGR_TRIBUTO, C_TRIBUTO, C_TIPO_UFF,C_UFFICIO,C_TIPO_IMP, N_ANNO_IMP, L_CARICO, S_ARTICOLO) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
/13199/
/66/
/2002/
/1564/
/28330/
/1/
/2/
/0997/
/120/
/2002/
/11900/
/ /

Prepared statement help

Hello all!
I am trying to get this prepared statement to work but am getting an error that I cant understand.
Basically I have a class file that the ps resides in. I am calling the ps from a jsp.
Here is the code:
public void recordUsage(String userid, String ipaddress, String page, String filename)
       String insertStatement = "INSERT INTO usageLog(userId,ipAddress, localTime, page, fileName) VALUES(?,?,?,?,?)";
            try
            {   java.util.Date currentDate=new java.util.Date();//Create a date object for the timestamp
                java.sql.Timestamp ts=new java.sql.Timestamp(currentDate.getTime());//Create the timestamp from the above date object.
                Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
                objConn = java.sql.DriverManager.getConnection("jdbc:odbc:sensorWeek","","");
                PreparedStatement ps = objConn.prepareStatement(insertStatement);
                ps.setString(1, userid);
                ps.setString(2, ipaddress);
                ps.setTimestamp(3, ts);
                ps.setString(4, page);
                ps.setString(5, filename);
                ps.executeUpdate();
                objConn.commit();
                ps.close();
                objConn.close();
                System.out.println("recordusage method called");
            catch (SQLException s)
                System.err.println("DataBase PROBLEM");
                s.printStackTrace();
            catch (Exception e)
                    System.err.println("Error in recordUsage method");
                    e.printStackTrace();
}Here is the error generated:(I hate to dump this on you)
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: sensorPac.methodClass.record(Ljava/lang/String;Ljava/lang/String;)V
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
     at java.lang.Thread.run(Thread.java:534)
root cause
javax.servlet.ServletException: sensorPac.methodClass.record(Ljava/lang/String;Ljava/lang/String;)V
     at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:536)
     at org.apache.jsp.download_jsp._jspService(download_jsp.java:93)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
     at java.lang.Thread.run(Thread.java:534)
TIA!!

And what makes you think that the above code is causing the problem?

Prepared Statement Flooding

Similar Messages

Maybe you are looking for