Michael,
Looks like the hard disk that /jnl is mounted on is dying a slow
painful death,
you've proved that this is problem is external to Ingres which is
helpful.

Try looking in /var/adm/messages (IIRC there is also a syslog file
somewhere) or at the console itself,
or look for in mail sent to the root user; some disk/hardware error
messages should be appearing somewhere
to confirm the failure.

In the meantime, you could create a symbolic link from the
/jnl/ingres/jnl path to a new directory
on a different physical disk, this will cause the jnls to be created
away from the problem
area which should stop the archiver crashing and give you usable (but
unsupported) journals.
This is a step forward as you currently have no journals. Take your DB
checkpoints more often
if you're concerned about using symbolic links in this way.

Another suggestion;
There is a script called acpexit in the utility directory which is
called when the archiver
shutsdown, you could change this script to notify you via email (or
some other means) of archiver problems.

HTH
Steve McElhinney

I've had a similar problem in the last week...

ingres 2.6/3035 64bit (solaris 9 64bit)

I have a database named training, now I did roll this forward last week, but
for some reason the ../jnl/training directory got untar'ed as a file and not
a directory, this not surprisingly caused the archiver to stop.

I've also had problems where I've typed createdb the os replies command not
found. you type "which createdb", the os replies /systems/ingres/bin, you
then type createdb test, the os replies command not found.

Work that one out.

I'm not suere whether there's something wrong with Ingres or Solaris I've
got calls logged for both.

what kit are you running this on?

-----Original Message-----
From: stevem@141.com [mailto:stevem@141.com]
Sent: 29 September 2004 11:16
To: info-ingres@ams.org
Subject: Re: [Info-Ingres] Jnl Sub-Directory Disappear

Michael,
Looks like the hard disk that /jnl is mounted on is dying a slow
painful death,
you've proved that this is problem is external to Ingres which is
helpful.

Try looking in /var/adm/messages (IIRC there is also a syslog file
somewhere) or at the console itself,
or look for in mail sent to the root user; some disk/hardware error
messages should be appearing somewhere
to confirm the failure.

In the meantime, you could create a symbolic link from the
/jnl/ingres/jnl path to a new directory
on a different physical disk, this will cause the jnls to be created
away from the problem
area which should stop the archiver crashing and give you usable (but
unsupported) journals.
This is a step forward as you currently have no journals. Take your DB
checkpoints more often
if you're concerned about using symbolic links in this way.

Another suggestion;
There is a script called acpexit in the utility directory which is
called when the archiver
shutsdown, you could change this script to notify you via email (or
some other means) of archiver problems.

HTH
Steve McElhinney

_______________________________________________
Info-ingres mailing list

English:- This message is confidential. If you are not the intended
recipient of the message then please notify the sender immediately. Any of
the statements or comments made above should be regarded as personal and not
necessarily those of Bro Morgannwg NHS Trust, any constituent part or
connected body. Cymraeg:- Mae'r neges hon yn gyfrinachol. Os nad chi yw'r
derbynnydd y bwriedid y neges ar ei gyfer, byddwch mor garedig â rhoi gwybod
i'r anfonydd yn ddi-oed. Dylid ystyried unrhyw ddatganiadau neu sylwadau a
wneir uchod yn rhai personol, ac nid o angenrhaid yn rhai o eiddo
Ymddiriedolaeth GIG Bro Morgannwg, nac unrhyw ran gyfansoddol ohoni na
chorff cysylltiedig.