My Oracle Support Banner

Before Update Trigger On Systimestamp Is Setting The Incorrect Value (Doc ID 2669747.1)

Last updated on MAY 21, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.

Symptoms

Behavior can be seen when using an update trigger on tables to check if an update on the table causes any column values to be changed.

If not, this is known as a dummy update, and the column that indicates a record has been changed, should keep its original value.

To identify if there are any changes ORA_HASH is used and old and new column values are compared.

If no changes are found column <column_name> which is set to SYSTIMESTAMP in the DDL is changed; ie :NEW.<column_name> is set to :OLD.<column_name>.

You can consider the below object definitions:

 

 



Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.