Cego Änderungsprotokoll

In the following, change log entries for the managed software packages is shown

Last 10 log entries in change log
Category	Date	Version	Log
cego	10.01.2026	2.54.0	Thoughts about redesign of cego mode started. The current design with mediator/primary/secondary with synchronous logging to secondary seems to be to complicated and fragile. A new approach might be to make secondary recovery based on complete archive logfiles, which are copied from primary to secondary asynchronously. The secondary host then must be controlled by himself ( no more mediator role ), so the complete database switch to secondary ist managed by an upper layer ( maybe not part of cego, since this also includes switch of a virtual host ) As a consequence, the cego mediator role will disappear ( just primary and secondary role are valid )
cego	09.01.2026	2.53.9	Removed PIDFILE attribute from db xml. PIDFILE should be specified by database startup with pidfile option
cego	03.01.2026	2.53.8	Version released
cego	03.01.2026	2.53.8	Small patch added to CegoAdminThread::getBackupInfo. Also empty logTS token are accepted now, since there might be still no archive logs avaiable for the backup In tools/backupManager, LOGTS was set to None, if no archive logs are available
cego	01.01.2026	2.53.7	Version released
cego	01.01.2026	2.53.7	Cleanup and reduction of logging in CegoRecoveryManager
cego	31.12.2025	2.53.7	Small improvement added to CegoAdmin to catch non existing batchfile exception
cego	30.12.2025	2.53.6	Version released
cego	29.12.2025	2.53.6	Added point in time recovery option to restore nut just pit ( timestamp ) but also to a specified lsn. This might be useful to restore exactly to a specific log entry ( timestamp is given in seconds, where multiple operations may occur )
cego	29.12.2025	2.53.6	Added shiftactive mode for cego to rescue active online redo logs to archive destination. This is useful in case of online backup recovery after a crash, so before starting recovery, the current active online redo log can be explicit shifted. With the shift, the latest LSNs are catched and a full recovery can take place. Please note : This option is just useful, if there are uncorrupted online redo logfiles available after the crash.