Skip to Main Content

ORDS, SODA & JSON in the Database

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.

Autonomous Database 23ai - ORDS HTTP Status Code: 571 problem when using Logon trigger

ZoltánOct 6 2024 — edited Oct 6 2024

There is a problem with the SYSDATE time due to the database time zone settings, until the session is configured:

ALTER SESSION SET SYSDATE_AT_DBTIMEZONE=TRUE;

If I want to solve this setting in the database logon trigger:

CREATE OR REPLACE TRIGGER logon_trigger_timezone
AFTER LOGON ON DATABASE
BEGIN EXECUTE IMMEDIATE 'ALTER SESSION SET sysdate_at_dbtimezone=true'; END;

Then ORDS does not work: HTTP Status Code: 571

Is there a way to set the database timezone without session configuration so that both ORDS and SYSDATE work?

This post has been answered by Zoltán on Oct 8 2024
Jump to Answer
Comments
Post Details
Added on Oct 6 2024
6 comments
167 views