Dear all Infomix Gurus

I have a problem about backing up Informix database with onbar -l command. The situation is .....

I launched 'onbar -l' command and the errors in /tmp/bar_act.log is as following

2003-12-23 13:13:34 1085 1084 /usr/informix/bin/onbar_d -l -C
2003-12-23 13:13:36 1085 1084 Begin backup logical log 218053.
2003-12-23 13:13:36 1085 1084 Successfully connected to Storage Manager.
2003-12-23 13:14:13 1085 1084 SQL -25587 Network receive failed.

2003-12-23 13:14:14 1085 1084 ERROR: One or more BLOBspaces are down. Log backup has been aborted.

Hi,

You problem is not onbar, you problem is "One or more BLOBspaces are down".
Please test "onstat -d | grep PD", if appear, then look utility onspaces -s .... for take on-line, the chunks down.

onspaces -s spacename -p pathname -o offset {-O | -D} [-y] }

BTW: Merry Christmas !!!

Gustavo.

Thank you Gustavo

I have another question.
If I use 'onbar -b <dbspace>' and the result is as following..

2003-12-23 12:43:27 848 847 /usr/informix/bin/onbar_d -b rootdbs
2003-12-23 12:43:30 848 847 Begin level 0 backup rootdbs.
2003-12-23 12:43:30 848 847 Successfully connected to Storage Manager.
2003-12-23 12:44:00 848 847 Completed level 0 backup rootdbs.
2003-12-23 12:44:06 848 847 Begin backup logical log 218053.
2003-12-23 12:44:07 848 847 Successfully connected to Storage Manager.
2003-12-23 12:44:44 848 847 SQL -25587 Network receive failed.
2003-12-23 12:44:45 848 847 ERROR: One or more BLOBspaces are down. Log backup has been aborted.

as seen above, the dbspaces backed up is complete but only log that has problem. is it the BLOBspaces problem? or anything possible.

Please help me .

Merry Christmas
Cheer

Hi,
OK, Can you send me file onconfig and output of "onstat -d" ?.

Thanks.

Gustavo.

Dear Gustavo

I can send you the following information

- bar_act.log
- onconfig

now i am unable to get the output of onstat -d at this time cos I'm not at office.

Thank you very much for you help

Regards

OK,

I suggest you tree changes:
1) In onconfig the parameter ALARMPROGRAM must be log_full.sh instead of no_log.sh. This is a problem for the of logical logs back-ups.
Look for documentation guide on Veritas for set of environment variables.
2) Change OPTCOMPIND=0 intead of 2, improvement performance.
3) Change size of logical logs. You can increase the logical logs size and decrease amount the logical logs.

Good luck,

Gustavo.

Thanks for your advices, Gustavo

I will try your recommendations as soon as possible and observe the result if it works successfully.

Yours