Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84248members
353348posts

[Imported] CDBEventJournal SeqNo changing upon swapping or fail over of servers

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

Solved
sbeadle
Janeway Janeway
Janeway
0 Likes
1
433

[Imported] CDBEventJournal SeqNo changing upon swapping or fail over of servers

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: hardin4019, originally posted: 2019-09-18 12:05:19 Id:517
Has anyone else experienced this, and is there a way to synchronize the SeqNo between servers? We have a third party software that is pulling the data via SQL Query, and uses the SeqNo to maintain the last record pulled so it doesn't get duplicates. The problem being that if there is a fail over, the SeqNo of the new server doesn't match the old server, and even when you go back to the original server, the SeqNo doesn't appear to pick back up from where it left off. Is there something other than the SeqNo that we should be using that isn't effected by server swaps?


Accepted Solutions
sbeadle
Janeway Janeway
Janeway
0 Likes
0
432

Re: [Imported] CDBEventJournal SeqNo changing upon swapping or fail over of servers

>>Responses imported from previous forum


Reply From User: geoffpatton, posted: 2019-09-18 14:30:31
I would try using RecordId or FileId and File Offset.


Reply From User: BevanWeiss, posted: 2019-09-18 21:43:03
[at]geoffpatton said:
I would try using RecordId or FileId and File Offset.

I'd be careful using the RecordId also... we've encountered situations where this wasn't unique.
The FileId and File Offset would be guaranteed unique on a particular server. But between two servers which might not have consistent data I'm not sure on this either.

It's a great question for Schneider Tech Support however. If you do find a globally unique and consistent identifier for CDBEventJournal entries please let me know 🙂

See Answer In Context

1 Reply 1
sbeadle
Janeway Janeway
Janeway
0 Likes
0
433

Re: [Imported] CDBEventJournal SeqNo changing upon swapping or fail over of servers

>>Responses imported from previous forum


Reply From User: geoffpatton, posted: 2019-09-18 14:30:31
I would try using RecordId or FileId and File Offset.


Reply From User: BevanWeiss, posted: 2019-09-18 21:43:03
[at]geoffpatton said:
I would try using RecordId or FileId and File Offset.

I'd be careful using the RecordId also... we've encountered situations where this wasn't unique.
The FileId and File Offset would be guaranteed unique on a particular server. But between two servers which might not have consistent data I'm not sure on this either.

It's a great question for Schneider Tech Support however. If you do find a globally unique and consistent identifier for CDBEventJournal entries please let me know 🙂