Continous logical log backup stuck - primary

Hi, I remember having this issue before but just can't remember how I solved it: [informix@ids01ha ~]$ ontape -a -d Performing automatic backup of logical logs. Do you want to back up the current logical log? (y/n) n Program over. This happens in a second without any input from my side.. Also ontape -c is hanging. Thank you. Regards, Steven.

what does the online.log say ? It seems you have a log backup in a directory. Did yur check low level if the directory is accessible and writable ? Marcus Haarmann Von: "STEVEN AB" <alexsuru1457@gmail.com> An: "ids" <ids@iiug.org> Gesendet: Donnerstag, 22. Februar 2018 09:55:20 Betreff: Continous logical log backup stuck - primary [40732] Hi, I remember having this issue before but just can't remember how I solved it: [informix@ids01ha ~]$ ontape -a -d Performing automatic backup of logical logs. Do you want to back up the current logical log? (y/n) n Program over. This happens in a second without any input from my side.. Also ontape -c is hanging. Thank you. Regards, Steven. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Informix 12.10.FC10

Hi Marcus, yes, the the log backup is done in a directory, all the permissions are ok. It's the same as the other FC7 informix ha cluster that I configured beside few onconfig parameters, not related to backups. Thanks, Steven.

And there's nothing in online.log

Steven - I may be missing something here, but can you describe what the problem is? The ontape -a -d will back up any logical logs that are filled and then stop. Are you saying that the logs are filling, but not being backed up to the directory? When using the -d with ontape -a, there will be no prompt, and the question of "do you want to back up the current logical log" will automatically be answered as "n". You would normally put the ontape in ALARMPROGRAM, so it would be executed each time a log fills. Make sure that BACKUPLOGS in the alarmprogram script is set to "Y". When using "ontape -c", it will appear to hang, but it's just running all the time...and will back up the logical logs when they fill. You could try running "ontape -c" in one window, and in another switch to the next log with "onmode -l;onmode -c" and you should get a message in the ontape window that a file has been created, which is the log backup. Mike -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of STEVEN AB Sent: Thursday, February 22, 2018 1:55 AM To: ids@iiug.org Subject: Continous logical log backup stuck - primary [40732] Hi, I remember having this issue before but just can't remember how I solved it: [informix@ids01ha ~]$ ontape -a -d Performing automatic backup of logical logs. Do you want to back up the current logical log? (y/n) n Program over. This happens in a second without any input from my side.. Also ontape -c is hanging. Thank you. Regards, Steven. **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.

So you're saying that ontape -a -d will backup only the logical logs that are filled ? Didn't knew that. When I was using it it was always backing up all logs so I took it like that :) All the logs are marked with F flag and I wanted to mark them with U and B. It's been a while since I've made a new informix setup but I think I remember that it won't pass to the next log if it's marked as F and most issue an onmode -l for each logical log to be marked as used. Correct me if I'm wrong. The automatic logical log backup is configured in alarmprogram.sh since this can be considered mandatory. Thank you, Steven.

I think that was the "A" flag

Yes, ontape -a -d will back up any logs used and not backed up, and then quit. The "F" in the flags means that it is Free - it hasn't been used. There is no need to back up this log, as it doesn't contain any transactional information. You'll see an "F" if you have recently restored the instance or if you just haven't used the logs yet, and it's okay. You won't encounter any problem with not moving past a Free log, because as soon as it is written to it won't be Free anymore. When transactions are written to a logical log, then the flag will switch to a "U" - Used. When the current log (marked with a "C" in position 5) switches to the next one, and the previous log gets backed up, then you'll see "U-B----". What you don't want to see if a lot of logs marked as Used and NOT backed up (U------), as that will lead to problems. You said that you are backing up to a directory, so make sure that LTAPEDEV references the directory (and owner and permissions are correct). Make sure that alarmprogram has BACKUPLOGS=Y, and that BACKUP_CMD="ontape -a -d". To test, switch logs manually with "onmode -l; onmode -c". You should see a message in the online log that a log has filled, and that a backup has begun. You'll soon see a new file created in the directory referred to by LTAPEDEV. Running onstat -l will show that you have no logs with the flags "U------". If this isn't working as described, then let us know what problem you are seeing. Mike -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of STEVEN AB Sent: Thursday, February 22, 2018 10:09 AM To: ids@iiug.org Subject: Re: RE: Continous logical log backup stuck - p.... [40745] So you're saying that ontape -a -d will backup only the logical logs that are filled ? Didn't knew that. When I was using it it was always backing up all logs so I took it like that :) All the logs are marked with F flag and I wanted to mark them with U and B. It's been a while since I've made a new informix setup but I think I remember that it won't pass to the next log if it's marked as F and most issue an onmode -l for each logical log to be marked as used. Correct me if I'm wrong. The automatic logical log backup is configured in alarmprogram.sh since this can be considered mandatory. Thank you, Steven. **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.