Greetings,
I don't know if this is the right space but I will start here first. I have a java application running in JBoss EAP 6.4 with ojdbc8.jar, jdk 1.8.0_121 and talks to an oracle 12c database. The java app is running on a Windows Server 2016 machine.
I have a peculiar case where when I call a specific stored procedure via a callable statement in one of the java classes and pass in the current timestamp as one of the IN parameters, the stored procedure seems to recognize the NLS date format of the timestamp
coming in with RR-MM-DD instead of the default of DD-MON-RR. I'm not doing any date manipulation with the parameter. I'm just running the standard var.getTime() method as you can see here:
if(gbpDate != null){
cs.setTimestamp(28, new Timestamp(gbpDate.getTime()));
}
else {
cs.setTimestamp(28, null);
}
gbpDate is defined as a standard java.util.Date field. An example of the parameters caught on the database side after cs executes are:
GBP date ~19-10-13~
Sysdate format ~19-10-03~
NLS format ~RR-MM-DD~
Is there a setting I'm missing somewhere? I can run this same stored procedure call on my local machine instance (Windows 10) and the NLS format stays DD-MON-RR.