ORA-210000 Oracle error: ORA-01878: specified field not found in datetime or interval

Avatar

Avatar
Validate 1
Employee
vigneshn9321496
Employee

Likes

8 likes

Total Posts

19 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile

Avatar
Validate 1
Employee
vigneshn9321496
Employee

Likes

8 likes

Total Posts

19 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile
vigneshn9321496
Employee

09-04-2018

Hi,

I have a query in my workflow and I am using an expression

DateOnly(@START_DATE) greater than or equal to DateOnly(DaysAgo(14)).

When the query runs, for a few records which fall on Daylight saving time shift, is throwing an error.

Tried to use ToDate(@START_DATE) as well, and still the same issue.

Can someone assist on how to get rid of this.

Thanks,

Vignesh

Replies

Avatar

Avatar
Give Back 50
Level 10
florentlb
Level 10

Likes

237 likes

Total Posts

1,109 posts

Correct reply

239 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 200
View profile

Avatar
Give Back 50
Level 10
florentlb
Level 10

Likes

237 likes

Total Posts

1,109 posts

Correct reply

239 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 200
View profile
florentlb
Level 10

19-04-2018

Hi Vignesh,

Can you psot a screenshot of your workflow or the activity throwing the error to check how it's configured?

Florent

Avatar

Avatar
Validate 1
Employee
vigneshn9321496
Employee

Likes

8 likes

Total Posts

19 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile

Avatar
Validate 1
Employee
vigneshn9321496
Employee

Likes

8 likes

Total Posts

19 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile
vigneshn9321496
Employee

19-04-2018

Hi Florent,

Issue was because of a few records which were present in the database which were in the Daylight saving time difference. Deleted those records and now the workflow runs fine without any issue.

Thanks,

Vignesh