Oracle Cached Prepared Statement

Question

We recently upgraded from WL 8.1 SP3 to WL 9.2 and in the process updated the JDBC Driver for Oracle from 10.2.0.1 to 10.2.0.2. After we went live we started seeing issue in one table. The table contains some special character which is not suppose to be there.
Here is the code & table details
PreparedStatement pstmt = cn.prepareStatement("INSERT INTO INFO_TABLE(user_name,user_status) values (?,?)");
pstmt.setString(1,requestObject.getUserName());
if(requestObject.isValidUser)
pstmt.setInt(2,requestObject.getStatus());
}else
pstmt.setNull(2,Types.VARCHAR);
cn.commit();
Table description:
USER_NAME VARCHAR2(60);
USER_STATUS VARCHAR2(5);
- The USER_STATUS columns valid values are 0-4 or NULL.
The problem is on certain occasions the valid user value in the table is some special character. I got the ascii value of this character as 128. We don't know yet whether setting int value and varchar (null) value on two different flow (but cached prepared statement) is the issue.
We can fix the code to use uniform data type but we need to be sure this is what causing the problem. Further when I read the docs http://e-docs.bea.com/wls/docs90/jdbc_admin/jdbc_datasources.html
I can associate the problem I face with this pointer however as I said, we need some sort of confirmation to make this change in the production code.
Here is what I am specifically looking for
1. Is there a way to confirm this problem?
2. Can we log the prepared statement being executed and the binded value being sent to the Oracle DB?
I suspect the VARCHAR null type is being casted to int value 128.
Would really appreciate any pointers on this.
Thanks

Answer 1

Purushothaman Thambu wrote:
We recently upgraded from WL 8.1 SP3 to WL 9.2 and in the process updated the JDBC Driver for Oracle from 10.2.0.1 to 10.2.0.2. After we went live we started seeing issue in one table. The table contains some special character which is not suppose to be there.
Here is the code & table details
PreparedStatement pstmt = cn.prepareStatement("INSERT INTO INFO_TABLE(user_name,user_status) values (?,?)");
pstmt.setString(1,requestObject.getUserName());
if(requestObject.isValidUser)
pstmt.setInt(2,requestObject.getStatus());
}else
pstmt.setNull(2,Types.VARCHAR);
cn.commit();
Table description:
USER_NAME VARCHAR2(60);
USER_STATUS VARCHAR2(5);
- The USER_STATUS columns valid values are 0-4 or NULL.
The problem is on certain occasions the valid user value in the table is some special character. I got the ascii value of this character as 128. We don't know yet whether setting int value and varchar (null) value on two different flow (but cached prepared statement) is the issue.
We can fix the code to use uniform data type but we need to be sure this is what causing the problem. Further when I read the docs http://e-docs.bea.com/wls/docs90/jdbc_admin/jdbc_datasources.html
I can associate the problem I face with this pointer however as I said, we need some sort of confirmation to make this change in the production code.
Here is what I am specifically looking for
1. Is there a way to confirm this problem?
2. Can we log the prepared statement being executed and the binded value being sent to the Oracle DB?
I suspect the VARCHAR null type is being casted to int value 128.
Would really appreciate any pointers on this.
ThanksHi. I don't think there's any issue with WebLogic here, but the code you show
might confuse some drivers. I highly recommend using setString for all
varchar/char/varchar2 columns, not setInt(). If requestObject.getStatus()
has to return an int, try this:
if(requestObject.isValidUser)
pstmt.setString(2, (""+ requestObject.getStatus()) );
Joe