RSS out of sync

Hello, We have issue with comvault today and primary informix instance logical backup stopped which led to logical log full and stopped instance. As quick solution, i have taken manual log backup with ontape -a -d which backed up log files to local directory. server was bounced once to fix the issue before i jump in and backup logical files manully and brought Informix online. Now RSS instance was not applying logs and seems to be struck or waiting for something. I checked onstat -g rss verbose and it looks good. informix:/home6/loglogdb/backup> onstat -g rss verbose IBM Informix Dynamic Server Version 12.10.FC8WE -- Read-Only (RSS) -- Up 00:30:25 -- 1071512 KbytesRSS Server control block: 0x47860a78 Local server type: RSS Server Status : Active Source server name: onesada Connection status: Connected Last log page received(log id,page): 16927,447 Sequence number of last buffer received: 326 Sequence number of last buffer acked: 326 Delay Apply: Not configured. Stop Apply: Not configured. Delay or Stop Apply not active. Log file output : 17:29:53 Started 1 B-tree scanners. 17:29:53 B-tree scanner threshold set at 5000. 17:29:53 B-tree scanner range scan size set to -1. 17:29:53 B-tree scanner ALICE mode set to 6. 17:29:53 B-tree scanner index compression level set to med. 17:29:53 Physical Recovery Started at Page (12:1426406). 17:29:53 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored. 17:29:53 smx creates 1 transports to server onesada 17:29:53 Peer node onesada has version 65538 17:29:53 RSS Server onesada - state is now connected 17:29:53 setting version information for onesada 65538 17:29:53 Dataskip is now OFF for all dbspaces 17:29:53 Restartable Restore has been ENABLED 17:29:53 Recovery Mode 17:29:53 Logical Recovery Started. 17:29:53 20 recovery worker threads will be started. 17:29:53 Start Logical Recovery - Start Log 16926, End Log ? 17:29:53 Starting Log Position - 16926 0x270a018 17:29:54 B-tree scanners disabled. 17:29:55 DR: RSS secondary server operational 17:29:55 Started processing open transactions on secondary during startupServer in fast recovery until these open transactions finish 17:29:55 Finished processing open transactions on secondary during startup. ------------- no output post this---------------------------I found on RSS instance side that is showing logical log files full. Do we need to perform any manual backup? 47a92230 112 U------ 16917 4:1110053 10000 10000 100.00 47a92298 113 U------ 16918 4:1120053 10000 10000 100.00 47a92300 114 U------ 16919 4:1130053 10000 10000 100.00 47a92368 115 U------ 16920 4:1140053 10000 10000 100.00 47a923d0 116 U------ 16921 4:1150053 10000 10000 100.00 47a92438 117 U------ 16922 4:1160053 10000 10000 100.00 47a924a0 118 U------ 16923 4:1170053 10000 10000 100.00 47a92508 119 U------ 16924 4:1180053 10000 10000 100.00 47a92570 120 U------ 16925 4:1190053 10000 10000 100.00 47a925d8 121 U---C-L 16926 4:1200053 10000 10000 100.00 47a92640 122 U------ 16627 4:1210053 10000 10000 100.00 47a926a8 123 U------ 16628 4:1220053 10000 10000 100.00 Regards, Bala ------------------------------ Cherry ------------------------------

Apparently the fact that you backed up those logs on the primary didn't make it to the RSS yet (in which log did this occur?), and I'm afraid this will not recover itself. What you can try, on this RSS, is: - onmode -ky - oninit -PHY --forget_logs - onmode -d RSS onesada HTH, Andreas ------------------------------ Andreas Legner ------------------------------

Hello Andreas, Yes, It worked. you saved my day. :) RSS is getting sync now. 20:04:00 Logical Recovery Started. 20:04:00 20 recovery worker threads will be started. 20:04:00 Start Logical Recovery - Start Log 16926, End Log ? 20:04:00 Starting Log Position - 16926 0x270a018 20:04:00 DR: Cleared 10 KB of logical log in 0 seconds. 20:04:00 Warning: Log Unique Id 16627 is marked as backed up without a real backup. 20:04:00 Warning: Log Unique Id 16628 is marked as backed up without a real backup. 20:04:00 Warning: Log Unique Id 16629 is marked as backed up without a real backup. ++++++++++++ output clipped +++++++++++++++ 20:04:00 Warning: Log Unique Id 16923 is marked as backed up without a real backup. 20:04:00 Warning: Log Unique Id 16924 is marked as backed up without a real backup. 20:04:00 Warning: Log Unique Id 16925 is marked as backed up without a real backup. 20:04:01 Defragmenter cleaner thread now running 20:04:01 Defragmenter cleaner thread cleaned:0 partitions 20:04:01 B-tree scanners disabled. 20:04:02 DR: RSS secondary server operational 20:04:02 Started processing open transactions on secondary during startupServer in fast recovery until these open transactions finish 20:04:02 Finished processing open transactions on secondary during startup. 20:04:03 Logical Log 16926 Complete, timestamp: 0xb989e9d4. 20:04:04 Checkpoint Completed: duration was 1 seconds. 20:04:04 Mon May 15 - loguniq 16927, logpos 0x610c0, timestamp: 0xb98a0eb5 Interval: 53701 ------------------------------Cherry ------------------------------

Cherry: Separate but related issue: This is why I always recommend that my clients have at least enough logical logs configure to be able to survive for four days without the logs filling and blocking transactions, just in case the log back ups fail for some reason, even over a long weekend! You need more logical logs! Art ------------------------------ Art S. Kagel, President and Principal Consultant ASK Database Management Corp. www.askdbmgt.com ------------------------------