Skip to main content

We have a custom solution that is erroring out - error message below - calling the DOC_ISSUE_API.  This code has been running for over five years without issue.  We have spent a few days troubleshooting and debugging and have not been able to pinpoint the issue.  The data set looks clean, so we are not sure where to look next.  Any advice/guidance would be appreciated.

 

Thank you in advance.

 

 

 

 

 

 

@bkelliher the error message seems to be missing from your post. It would be helpful to see the error message in order for anyone to provide any guidance 😀.


 


Hi @bkelliher 

 

ORA-01858 is related to incorrect format in Date fields.

By looking at your error stack, it could potentially one of the date fields added in attr parameter to Doc_Issue_API method being called has incorrect format.

 

Can you mention which Doc_Issue_API method is being calling from your application and the values being passed? It would be easy to figure the problem.

 

Cheers!

Damith


Thank you for your response.  Below is the code snippet from the app as well as a data stream  capture during debug.   Again, this has been working without error for over 5 years - until Jan. 2, 2024.

 

        cmdOracle = New Oracle.ManagedDataAccess.Client.OracleCommand
        cmdOracle.Connection = connOracle
        cmdOracle.CommandType = CommandType.StoredProcedure
        cmdOracle.CommandText = "DOC_ISSUE_API.New__"
        cmdOracle.Transaction = transOracle

 

 

 


Thank you for your response.  Below is the code snippet from the app as well as a data stream  capture during debug.   Again, this has been working without error for over 5 years - until Jan. 2, 2024.

 

        cmdOracle = New Oracle.ManagedDataAccess.Client.OracleCommand
        cmdOracle.Connection = connOracle
        cmdOracle.CommandType = CommandType.StoredProcedure
        cmdOracle.CommandText = "DOC_ISSUE_API.New__"
        cmdOracle.Transaction = transOracle

 

 

 

Hi @bkelliher 

Your date time fields incorrect date fields

Eg: 03-Jan-2024

Correct date format acceptable is 2024-Jan-03 (YYYY-MM-DD)

 

Hope it helps!

Damith


Thank you for your reply - and that makes sense - curious thing is this code has been running for over 5 years untouched.  


Thank you for your reply - and that makes sense - curious thing is this code has been running for over 5 years untouched.  

 

Hi @bkelliher 

 

If it’s a client application, maybe the regional settings could be where you can start checking. It’s something which can change unnoticed and make problems ;)


Reply