This content has been marked as final. Show 1 reply
This cannot be done without application changes or moving your application into a separate database. As SYSDATE is a reserved word, you would need to change all references to quoted identifier "SYSDATE" to be able to use a user-defined function "SYSDATE".
You could theoretically try to change SYSDATE just for your application by connecting in the dedicated server mode through a separate listener started with another TZ variable, but such mixing of time zones in one instance is not recommended. I am not even sure if it is supported at all. It could pose problems in some situations, generate non-continuous timestamps in alert.log, confuse time based point-in-time recovery, etc.