HI,

Wonder if anyone has seen this behaviour before.....

INFORMIX VERSION :
IBM Informix Dynamic Server Version 11.50.UC2

BACKUP : ONBAR via NETBACKUP policy

Occasionally we start running a backup and it backups up the rootdbs and then the determinates/aborts.

the online.log :
---------------------------------------------------------
17:06:09 Level 0 Archive started on rootdbs
17:06:21 Archive on rootdbs ABORTED.
17:06:21 Aborted by client.
---------------------------------------------------------


the BAR act log shows :
----------------------------------------------------------------------
2009-10-01 17:07:16 20799 20797 /opt/local/informix_ods/bin/onbar_d -b -w -L 0
2009-10-01 17:07:16 20799 20797 Working with veritas-netbackup as generic storage manager.
2009-10-01 17:07:19 20799 20797 Archive started on rootdbs, ods_dbs_017, ods_dbs_006, ods_dbs_003, ods_dbs_028, ods_dbs_014, ods_d
bs_038, ods_dbs_040, ods_dbs_015, ods_dbs_005, ods_dbs_041, ods_dbs_011, ods_dbs_037, ods_dbs_029, ods_dbs_023, ods_dbs_039, ods_dbs
_009, ods_dbs_033, ods_dbs_012, ods_dbs_021, ods_dbs_032, ods_dbs_031, ods_dbs_022, ods_dbs_016, ods_dbs_036, ods_dbs_035, ods_dbs_0
07, ods_dbs_004, ods_dbs_013, ods_dbs_025, ods_dbs_010, ods_dbs_027, ods_dbs_002, ods_dbs_030, ods_dbs_019, ods_dbs_055, ods_dbs_001
, ods_dbs_034, ods_dbs_054, ods_dbs_026, ods_dbs_008, pseudo_temp_dbs2, ods_dbs_018, pseudo_temp_dbs, dbasedbs, repo_ps_001, ods_dbs
_052, ods_dbs_053, llogsdbs (Requested Level 0).
2009-10-01 17:07:19 20799 20797 Unable to start the storage space backup: Another archive is already in progress on DBspace ods_db
s_017..
2009-10-01 17:07:19 20799 20797 Archive on rootdbs, ods_dbs_017, ods_dbs_006, ods_dbs_003, ods_dbs_028, ods_dbs_014, ods_dbs_038,
ods_dbs_040, ods_dbs_015, ods_dbs_005, ods_dbs_041, ods_dbs_011, ods_dbs_037, ods_dbs_029, ods_dbs_023, ods_dbs_039, ods_dbs_009, od
s_dbs_033, ods_dbs_012, ods_dbs_021, ods_dbs_032, ods_dbs_031, ods_dbs_022, ods_dbs_016, ods_dbs_036, ods_dbs_035, ods_dbs_007, ods_
dbs_004, ods_dbs_013, ods_dbs_025, ods_dbs_010, ods_dbs_027, ods_dbs_002, ods_dbs_030, ods_dbs_019, ods_dbs_055, ods_dbs_001, ods_db
s_034, ods_dbs_054, ods_dbs_026, ods_dbs_008, pseudo_temp_dbs2, ods_dbs_018, pseudo_temp_dbs, dbasedbs, repo_ps_001, ods_dbs_052, od
s_dbs_053, llogsdbs ABORTED (Requested Level 0).
----------------------------------------------------------------------

This may have come about us CTRL C and previous backup, however we have checked the ps -ef|grep onbar and their are no ONBAR processes running. We have even tried an ontape -s -L 0 and similar message.

The workaround to this is to restart the instance. But this should be happening and restarting an instance on a 24/7 server is quite painfull.

Has anyone ever got this issue/any ideas would be much appreciated.

Many Thanks
Raj

Hi,

You message log shows archive started at 17:06:09
17:06:09 Level 0 Archive started on rootdbs

You have pasted the contents of bar log which are from 2009-10-01 17:07:16
Can you please attach current days message log, bar log, output of onstat -g ntt, output of ps -fu informix
On TSM, we have a seperate log file , can you attach that as well?

regards,

Nitin

Thanks for your reply,

sadly these logs have now been overwritten. The machine was part of a pre-live setup, which went live last sunday. all logs were cleared down.

thanks very much for your response, am sure we encounter this error again. will be sure to keep the logs and pasted them in this thread.

thanks
RAJ