Ordinal binding and Named binding cannot be combined!

[Keith Larsen]

I'm seeing an error when I execute cstmt.setInt(1,fromVendor); in the code below. When I step through the code I see in TRCCallableStatement.errMsgMixedBind has the following value: "Ordinal binding and Named binding cannot be combined!"

I can see fromVendor=141 and toVendor=5020 so there are no null parameters.

public String mergeVendor(int fromVendor, int toVendor) throws AgentException {
	boolean success = false;
	CallableStatement cstmt = null;
	java.sql.Connection jdbcConn = null;
    
	String status = "success";


	jdbcConn = getJDBCConnection();
			
	cstmt = jdbcConn.prepareCall("{call license.merge_vendors(fromVendor,toVendor)}");

	cstmt.setInt(1,fromVendor);
	cstmt.setInt(2, toVendor);

	success = cstmt.execute();
		       
	ResultSet rs = (ResultSet)cstmt.getObject(1);

[Fatih Keles]

cstmt = jdbcConn.prepareCall("{call license.merge_vendors(?,?)}");  

[Keith Larsen]

That worked. Thanks.

[priya chitra]

Hi. I am getting a similar message in callable statement as "ordinal binding and named binding cannot be combined together" when calling a procedure. The proc is returning null when calling through Java, whereas in SQL developer it is not returning null. The procedure has 14 IN parameters and 1 OUT Parameter "{call EMPLOYEE_INSERT_DTLS(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}"

[Martin Vashko]

Please continue the discussion in the other thread. Thanks!