Precisely what does onsmsync do when it is run with no parameters, and
in what order, i.e., what is it using as basis of comparison: storage
manager, sysutils database or ixbar file? Will I lose data if someone
mistakenly runs onsmsync without parameters? Also, the manual is
somewhat equivocal on this point: Does onsmsync behave differently if
it is run in single-user mode?

Using IDS 10.00.FC6 on RHEL4/2.6.9

On 30/08/2011 14:27, red_valsen wrote:
onsmsync usage

[-g <gen> | -t <time> | -i <interval>] [-s] [-O] [-f <filename> |
<spaces>]
-b

-b synchronizes the sysutils database and ON-Bar emergency boot file
-f pathname of file containing list of storage spaces
-g number of generations/versions of level 0 backup to retain
-i time interval (age) before which objects should be expired
-t datetime before which objects should be expired
-s skip syncing objects that are already expired from storage manager.
-O override internal error checks - enforce policy strictly
<spaces> list of storage spaces to check for expiration

I doubt whether running onsmsync (in Single User mode) as informix would
result in anything different happening.

On Aug 30, 9:47*am, "Jonny... (AT) Usenet-News (DOT) net" <Jonny...@Usenet-
News.net> wrote:
Thank you ever so much for your redundant response, but I need a
useful answer from somebody who can reply knowledgeably.

On 30/08/2011 16:43, red_valsen wrote:
1. Running onsmsync with no options synchronises the ixbar file and the
sysutils database with what the storage manager knows.

From the manual :

no options
Synchronizes the sysutils database and emergency boot file with the
storage-manager catalog

e.g. You can drop / create the sysutils database and remove the
ixbar.<SERVERNUM> file, then running onsmsync the ixbar file and the
sysutils database is populated from the storage manager information.

You will not lose data if someone runs it "mistakenly" without any
parameters.

2. Running in single user mode as informix and it runs fine - identical.

3. Review the BAR_ACT_LOG file for more details, and if even more
details are required set BAR_DEBUG to various values from 1 to 9 (I
would NOT recommend setting higher that 5 in a big instance).

10.00.FC6 is no longer in support.