Note that there are some explanatory texts on larger screens.

plurals
  1. POException in thread "main" java.sql.SQLException: Missing defines
    primarykey
    data
    text
    <p><br> I have done below sample JDBC program which retrieving user details.Now i am getting surprised that from same callable statement i am getting different result set for same output parameter index.Ideally it should return same ResultSet object.</p> <ol> <li>when i got the resultset then i am moving cursor -1 to 0.</li> <li>i am retrieving data from another resultset for the same output param using column name then i am getting following exception</li> </ol> <p>,</p> <p><em><strong>Exception in thread "main" java.sql.SQLException: Missing defines</em></strong></p> <pre><code> System.out.println("Before loading connection"); DriverManager.registerDriver(new oracle.jdbc.OracleDriver()); Connection connection = DriverManager.getConnection( "jdbc:oracle:thin:@170.45.3.165:1541/testdb.mycomp.com", "admin", "admin123"); System.out.println("Connection loaded " + connection); CallableStatement callProcedure = connection .prepareCall("{call ADMIN_USER.Fetch_User_Details(?,?)}"); callProcedure.setString(1, "userid=testid"); callProcedure.registerOutParameter(2, oracle.jdbc.OracleTypes.CURSOR); callProcedure.execute(); ResultSet resultUserDetails = (ResultSet) callProcedure.getObject(2); resultUserDetails.next(); ResultSet resultUserDetails1 = (ResultSet) callProcedure.getObject(2); String username = resultUserDetails1.getString(COL_NAME_USER_NAME); System.out.println(resultUserDetails); System.out.println(resultUserDetails1); System.out.println(resultUserDetails == resultUserDetails1); </code></pre> <p><strong>Can anyone has any idea why we are getting two different resultset for same output index from callable statement?</strong></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload