Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Connect 2026 Agenda Now Available: Explore Sessions
cancel
Showing results for 
Search instead for 
Did you mean: 
al3x
Contributor II
Contributor II

ORA-01891: Datetime/Interval internal error

Hello

We have an issue for Qlik Replicate Task Reload. In case a reload is initated the task goes into a "Recovering" status. This issued migh correlate to the change from sommertime to wintertime this weekend or to uprgrading oracle to container based database. 

Any hints on debugging this further?

Login on the database manually and triggering "SELECT SESSIONTIMEZONE FROM dua" is working. 

Here is an exerpt from logs. Username and domain are anonymized. 

00002556: 2024-10-28T09:29:04:77770 [SOURCE_CAPTURE ]I: Source endpoint 'Oracle' is using provider syntax 'Oracle' (provider_syntax_manager.c:941)
00002557: 2024-10-28T09:29:04:77971 [SORTER ]I: There is no saved state for sorter (sorter.c:536)
00002557: 2024-10-28T09:29:04:78139 [SORTER ]I: 'Stop reading when memory limit reached' is set to false (sorter.c:660)
00002557: 2024-10-28T09:29:04:87863 [STREAM_COMPONEN ]I: Going to connect to Oracle server abc.company.local with username USER_NAME (oracle_endpoint_imp.c:871)
00002557: 2024-10-28T09:29:04:127014 [STREAM_COMPONEN ]T: Going to prepare the statement 'select value from v$nls_parameters where parameter = 'NLS_CHARACTERSET'' (oracle_endpoint_conn.c:702)
00002557: 2024-10-28T09:29:04:127619 [STREAM_COMPONEN ]T: Going to prepare the statement 'select value from v$nls_parameters where parameter = 'NLS_NCHAR_CHARACTERSET'' (oracle_endpoint_conn.c:712)
00002557: 2024-10-28T09:29:04:129605 [STREAM_COMPONEN ]T: SESSIONTIMEZONE: '+01:00' (oracle_endpoint_capture.c:142)
00002557: 2024-10-28T09:29:04:131107 [STREAM_COMPONEN ]V: Oracle error code is '1891' (oracle_endpoint_capture.c:162)
00002557: 2024-10-28T09:29:04:131114 [STREAM_COMPONEN ]T: ORA-01891: Datetime/Interval internal error [1020417] (oracle_endpoint_capture.c:162)
00002557: 2024-10-28T09:29:04:131122 [STREAM_COMPONEN ]T: Failed to execute statement 'SELECT SESSIONTIMEZONE FROM dual' [1020417] (oracle_endpoint_capture.c:165)
00002557: 2024-10-28T09:29:04:131165 [STREAM ]V: Stream stream_0. Source locks buffer 0 (stream.c:2071)

Kind regards

Labels (1)
1 Solution

Accepted Solutions
al3x
Contributor II
Contributor II
Author

Hello @Dana_Baldwin , @john_wang 


Thank you very much for your prompt response and for the ideas you provided to address the issue. Our database administrators have tried various approaches, and it appears that a database restart may have resolved the problem. For the time being, we don’t plan to investigate this issue further.

Best regards,
Alex

 

View solution in original post

4 Replies
john_wang
Support
Support

Hello @al3x ,

Thanks for reaching out to Qlik Community!

>> Login on the database manually and triggering "SELECT SESSIONTIMEZONE FROM dua" is working. 

I'm assuming you login on the database by using the same Oracle account, please confirm.

>> ORA-01891: Datetime/Interval internal error

Please check was there any network disconnection issue, and what's the Oracle version etc.

I'd like to suggest opening a support ticket with Diagnostics Packages, Our support team will be more than happy to assist you.

Regards,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
Dana_Baldwin
Support
Support

Hi @al3x 

In addition to what @john_wang has suggested, do the timezone files match between the Oracle server and the Oracle client installed on the Replicate server? The instant client for example may not include the complete set of timezone entries the server has.

Also, please verify that you are using a version of the Oracle client that is supported for use with the Oracle server version you are connecting to. I've seen this issue with Oracle 12 client connecting to Oracle 19 server for example.

Thanks,

Dana

al3x
Contributor II
Contributor II
Author

Hello @Dana_Baldwin , @john_wang 


Thank you very much for your prompt response and for the ideas you provided to address the issue. Our database administrators have tried various approaches, and it appears that a database restart may have resolved the problem. For the time being, we don’t plan to investigate this issue further.

Best regards,
Alex

 

john_wang
Support
Support

Thank you so much for your support and the update @al3x !

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!