问题描述
在Oracle集群中(多台机器协作为一个数据库提供服务)，"sysdate"功能是否总是返回一致的答案?即使服务器的操作系统时钟报告了不一致的值?
In an Oracle cluster (more than one machine co-operating to serve one database) will the "sysdate" function always return a consistent answer? Even if the servers' Operating System clock reports inconsistent values?
推荐答案
我强烈怀疑SYSDATE也与OS链接.请特别注意需要使用它的原因.如果有任何实现事件增量跟踪的逻辑(例如，您正在执行增量导出)，并且您必须确保没有遗漏任何项目以及没有重复项，则该跟踪应基于顺序ID而不是SYSDATE.
I would strongly suspect that SYSDATE is OS-linked too. Be very watchful of the reason why you need to use it. If have any logic which implements incremental tracking of events (e.g. you're doing incremental exports) and you must ensure no items left out as well as no duplication, base the tracking on sequential IDs rather than SYSDATE.
实际上，即使对于非集群系统也是如此，因为SYSDATE有时会更改(节省时间，系统管理员错误...).
In fact, this is true even for non-cluster systems, as SYSDATE can sometimes change (time savings, sysadmin errors...).
这篇关于在Oracle集群中，sysdate是否总是返回一致的答案?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！