Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

ORA-01841: (full) year must be between -4713 and +9999, and not be 0 on Rest Data Source calls

We are encountering an ORA-01841 error when processing the response from a REST Data Source call in Oracle APEX 23.2.6. The request itself executes successfully and updates the external system, but when APEX attempts to process the response, it throws a date-related error - even though the response does not contain any date fields.

Key Observations:

  • The POST request completes successfully, and the changes are applied as expected.
  • No response are returned, only the error
  • The error only occurs when the parameters contain Norwegian characters (æ, ø, å).
  • Without special characters, the request and response work as expected.
  • The issue started two weeks ago, with no known changes to the configuration.
  • The data profile encoding is set to default.
  • Before this issue, the same request and response worked without problems.

Debug shows the request body that is processed in the Rest data source:

making POST request to API.com, using request body:

{
"para1": "XYZ",
"para2": "1",
"para3": "ABC123",
"para4": false,

"para5":"Verkt\u00F8ybod hall 2" }

\u00F8 = ø

Error message:

ORA-01841: (full) year must be between -4713 and +9999, and not be 0
ORA-06512: at "APEX_230200.WWV_FLOW_EXEC_API", line 1861
ORA-06512: at "APEX_230200.WWV_FLOW_EXEC_WEB_SRC", line 3199
...

Questions:

  • Could APEX be misinterpreting special characters, leading to a format issue?
  • Should the data profile encoding be explicitly set to UTF-8 or another encoding?
  • Has anyone experienced a similar issue in APEX 23.2.6?
  • What is the best approach to ensure APEX handles these characters correctly?

Any insights would be appreciated. Thank you.

Comments

Post Details

Added on Feb 26 2025
3 comments
284 views