logical logs not being read by ontape or onbar
Andrew Grantham (v10.00.FC10, Solaris) found neither ontape nor onbar backed up logical logs. David Link asked whether LTAPEDEV was /dev/null. It was a symbolic link to /dev/null. Marcus Haarmann explained that Informix only treats the literal /dev/null, set at startup, as no-backup, so a link still requires log backups. Whether this fixed it was not stated.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Informix v10.00.FC10
Sun solaris 5.10
I have an instance where neither ontape or onbar appears to read the logical
logs when trying to do a logical log backup to Netbackup in the case of onbar
or to a file system in the case of ontape. Any ideas why? Please don´t comment
about the version number I know this already.
Was the engine started up with LTAPEDEV=/dev/null ?
I know that used to happen to us.
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Andrew
Grantham
Sent: Wednesday, September 04, 2013 10:27 AM
To: ids@iiug.org
Subject: logical logs not being read by ontape or onbar [31357]
Informix v10.00.FC10
Sun solaris 5.10
I have an instance where neither ontape or onbar appears to read the logical
logs when trying to do a logical log backup to Netbackup in the case of onbar
or to a file system in the case of ontape. Any ideas why? Please don´t comment
about the version number I know this already.
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
David,
No it wasn´t. Well not directly. It is set to /dev/kk_null which is a symbolic
link through to /dev/null
> To: ids@iiug.org
> From: DALink@west.com
> Subject: RE: logical logs not being read by ontape or onbar [31358]
> Date: Wed, 4 Sep 2013 11:49:15 -0400
>
> Was the engine started up with LTAPEDEV=/dev/null ?
>
> I know that used to happen to us.
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Andrew
> Grantham
> Sent: Wednesday, September 04, 2013 10:27 AM
> To: ids@iiug.org
> Subject: logical logs not being read by ontape or onbar [31357]
>
> Informix v10.00.FC10
> Sun solaris 5.10
>
> I have an instance where neither ontape or onbar appears to read the logical
> logs when trying to do a logical log backup to Netbackup in the case of onbar
> or to a file system in the case of ontape. Any ideas why? Please don´t
comment
> about the version number I know this already.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Wouldn't it just be tossing the logs in the bit bucket then? You're not sending it directly to /dev/null but through the symbolic link to /dev/null.
Hi Nate,
no, anything that is not "/dev/null" will be treated as not being /dev/null
and requires a log backup
(either by onbar or ontape). Informix has no knowledge, that your device node
is a synonym to /dev/null.
And /dev/null has to be set as LTAPEDEV when the instance is started.
Modifying the value
in onconfig with an editor when the instance is running will not result in a
state that requires no log backup.
If set to /dev/null in the moment of startup, that entry will be treated
internally
so that any full log will be immediately marked as backed up.
Haven't tried to set the value using onmode -wf LTAPEDEV=/dev/null. This might
have the effect on
a running instance.
Best regards,
Marcus Haarmann
----- Ursprüngliche Mail -----
Von: "NATE HICKS" <nathaniel.hicks@trnswrks.com>
An: ids@iiug.org
Gesendet: Donnerstag, 5. September 2013 20:42:48
Betreff: Re: RE: logical logs not being read by ontape .... [31373]
Wouldn't it just be tossing the logs in the bit bucket then? You're not
sending it directly to /dev/null but through the symbolic link to /dev/null.
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.