error when analyzing expression: Timestamp out of range

mgverticamgvertica
edited January 30 in General Discussion

Recently I received many of this warning and size of catalog vertica.log was up to 70GB!
[EE] error when analyzing expression: Timestamp out of range
what happened?

Best Answer

  • mgverticamgvertica
    Accepted Answer

    I found the solution:
    my query was:
    select count(1) from my_table where col1>=TIMESTAMPADD(HOUR, -1, NOW()); -- col1 in nullable
    when i change it to this the problem solved:
    select count(1) from my_table where col1>=TIMESTAMPADD(HOUR, -1, NOW()) and col1 is not null;
    it's a bit exciting that nullable timestamp columns can generate huge warning logs and occupy memory!

Answers

  • moshegmosheg Employee

    Something like the following can produce this error:
    SELECT to_timestamp('999999999-12-22','DD Mm Y');
    To find which command produced it in your system, try this:
    grep -B 2 -e 'Timestamp out of range' /your_catalog_path/vertica.log | tail -2

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file

Can't find what you're looking for? Search the Vertica Documentation, Knowledge Base, or Blog for more information.