RE: onbar problems
Posted in 2000
Topics: Backup & Restore
Onbar is looking for a "sm_versions" file, NOT "sm_versions.std".
The "sm_versions.std" file is a sample one.
-----Original Message-----
From: DGO [mailto:derek@cardinalgroup.com]
Sent: Wednesday, October 11, 2000 11:59
To: informix-list@iiug.org
Subject: onbar problems
I can't seem to get ONBAR to perform correctly. Each time I run it whether
it be from the command prompt or through ISA (web based gui replacing IECC)
I repeatedly get the following error:
ERROR: Unable to open file d:\\informix/etc/sm_versions
No such file or directory
The thing is that the sm_versions.std file is exactly where this points!
I've checked and rechecked permissions, etc and I continually get this. Any
ideas?
Thanks for the help. This is quite new to me.
I now have visibility to the next problem:
I have gotten rid of the extension on sm_versions using cp (thanks Brice).
I now get the following in the bar_<<servername>> log:
2000-10-11 16:01:12 380 389 d:\\informix\\bin\\onbar_d -l
2000-10-11 16:01:12 380 389 Begin backup logical log 1.
2000-10-11 16:01:16 380 389 XBSA Error (BSAInit): A system error occurred.
Aborting XBSA session.
2000-10-11 16:01:16 380 389 WARNING: The logical logs are full. ON-Bar
may encounter errors writing to the
sysutils database.
Looking in the NT event log, I see similar entries.
When looking at the log files in ISA, 9 of the 11 are full, the 10th is only
10% full and the 11th hasn't been touched.
"Bernstein, Rick" <rbernste@alarismed.com> wrote in message
news:8s2fvv$ru1$1@news.xmission.com...
>
> Onbar is looking for a "sm_versions" file, NOT "sm_versions.std".
> The "sm_versions.std" file is a sample one.
>
> -----Original Message-----
> From: DGO [mailto:derek@cardinalgroup.com]
> Sent: Wednesday, October 11, 2000 11:59
> To: informix-list@iiug.org
> Subject: onbar problems
>
>
> I can't seem to get ONBAR to perform correctly. Each time I run it
whether
> it be from the command prompt or through ISA (web based gui replacing
IECC)
> I repeatedly get the following error:
>
> ERROR: Unable to open file d:\\informix/etc/sm_versions
> No such file or directory
>
> The thing is that the sm_versions.std file is exactly where this points!
> I've checked and rechecked permissions, etc and I continually get this.
Any
> ideas?
>
Derek,
Now it looks like it can't find your storage manager. What storage manager
are you using?
Doug
"DGO" <derek@cardinalgroup.com> wrote in message
news:8s2hej$b2t$1@bob.news.rcn.net...
> Thanks for the help. This is quite new to me.
>
> I now have visibility to the next problem:
>
> I have gotten rid of the extension on sm_versions using cp (thanks Brice).
> I now get the following in the bar_<<servername>> log:
>
> 2000-10-11 16:01:12 380 389 d:\\informix\\bin\\onbar_d -l
> 2000-10-11 16:01:12 380 389 Begin backup logical log 1.
> 2000-10-11 16:01:16 380 389 XBSA Error (BSAInit): A system error
occurred.
> Aborting XBSA session.
> 2000-10-11 16:01:16 380 389 WARNING: The logical logs are full. ON-Bar
> may encounter errors writing to the
> sysutils database.
>
> Looking in the NT event log, I see similar entries.
>
> When looking at the log files in ISA, 9 of the 11 are full, the 10th is
only
> 10% full and the 11th hasn't been touched.
>
> "Bernstein, Rick" <rbernste@alarismed.com> wrote in message
> news:8s2fvv$ru1$1@news.xmission.com...
> >
> > Onbar is looking for a "sm_versions" file, NOT "sm_versions.std".
> > The "sm_versions.std" file is a sample one.
> >
> > -----Original Message-----
> > From: DGO [mailto:derek@cardinalgroup.com]
> > Sent: Wednesday, October 11, 2000 11:59
> > To: informix-list@iiug.org
> > Subject: onbar problems
> >
> >
> > I can't seem to get ONBAR to perform correctly. Each time I run it
> whether
> > it be from the command prompt or through ISA (web based gui replacing
> IECC)
> > I repeatedly get the following error:
> >
> > ERROR: Unable to open file d:\\informix/etc/sm_versions
> > No such file or directory
> >
> > The thing is that the sm_versions.std file is exactly where this points!
> > I've checked and rechecked permissions, etc and I continually get this.
> Any
> > ideas?
> >
>
>