Re: Physical restore failed
Wally Tang's ontape physical restore kept failing, first with "could not fork server connection" and then "function read archive backup failed code -2 errno 0". Suggestions included checking device ownership/permissions with ls -lL (including symlinks), verifying the HP-UX logical volumes were read/write in SAM, and checking ONCONFIG/sqlhosts plus the online.log since the fork error means the engine couldn't restart mid-restore. Martin Fuerderer suggested focusing on reading the backup file: TAPEBLOCKSIZE/TAPESIZE mismatch, a truncated or multi-volume backup, readability via dd, and tracing with truss/strace. No resolution is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Wally, Try rechecking the full ownership permissions and privileges on the devices with ls -lL and not just with the usual ls -l. If you are using symbolic links then also apply the ls -lL to the symbolic links. Regards, Bruce
Hi Bruce, I rechecked the full ownership permissions and privileges on the devices, they are correctly set as ownership, permissions, and privileges. But the restore still returned with error: Physical restore failed - function read archive backup failed code -2 errno 0 Wally Tang DOD-Defense Media Center - IT Lockheed Martin - IT 23755 Z Street Riverside, CA 92518-2017 951-413-2246 E-mail: wally.tang.ctr@dma.mil -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Brucemarchu@aol.com Sent: Friday, April 23, 2010 7:43 PM To: ids@iiug.org Subject: Re: Physical restore failed [19844] Wally, Try rechecking the full ownership permissions and privileges on the devices with ls -lL and not just with the usual ls -l. If you are using symbolic links then also apply the ls -lL to the symbolic links. Regards, Bruce **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.
Wally- Here's something else you can check. I'm guessing that your devices are logical volumes. Look at the properties of the logical volumes in SAM. The access permission should be read/write: #sam Select "Disks and File Systems" Select "Logical Volumes" Highlight a logical volume you are using for your database Actions: View more information You should get something that looks like this: Logical Volume: lvol6 Volume Group: invg01 Attributes to View: [ General ->] Logical Volume Size (Mbytes): 2048 Extent Size (Mbytes): 4 Contiguous Allocation: no Usage: Unused Bad Block Relocation: yes Access Permission: read/write If the access permission says, "Read Only", go into Actions, Modify and change it to read/write. --EEM > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > Tang, Wally, CTR, DMA-Riv/IT > Sent: Monday, April 26, 2010 4:27 PM > To: ids@iiug.org > Subject: RE: Physical restore failed [19853] > > Hi Bruce, > > I rechecked the full ownership permissions and privileges on the > devices, > they are correctly set as ownership, permissions, and privileges. But > the > restore still returned with error: > > Physical restore failed - function read archive backup failed code -2 > errno > 0 > > Wally Tang > DOD-Defense Media Center - IT > Lockheed Martin - IT > 23755 Z Street > Riverside, CA 92518-2017 > 951-413-2246 > E-mail: wally.tang.ctr@dma.mil > > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > Brucemarchu@aol.com > Sent: Friday, April 23, 2010 7:43 PM > To: ids@iiug.org > Subject: Re: Physical restore failed [19844] > > Wally, > > Try rechecking the full ownership permissions and privileges on the > devices > with ls -lL and not just with the usual ls -l. If you are using > symbolic links then also apply the ls -lL to the symbolic links. > > Regards, > Bruce > > *********************************************************************** > ***** > *** > Forum Note: Use "Reply" to post a response in the discussion forum. > > > *********************************************************************** > ******** > Forum Note: Use "Reply" to post a response in the discussion forum.
Thank you, Everett. I checked the logical volumes as you suggested from SAM, they all have read/write permission. Please advice. Wally Tang DOD-Defense Media Center - IT Lockheed Martin - IT 23755 Z Street Riverside, CA 92518-2017 951-413-2246 E-mail: wally.tang.ctr@dma.mil -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Everett Mills Sent: Monday, April 26, 2010 2:44 PM To: ids@iiug.org Subject: RE: Physical restore failed [19854] Wally- Here's something else you can check. I'm guessing that your devices are logical volumes. Look at the properties of the logical volumes in SAM. The access permission should be read/write: #sam Select "Disks and File Systems" Select "Logical Volumes" Highlight a logical volume you are using for your database Actions: View more information You should get something that looks like this: Logical Volume: lvol6 Volume Group: invg01 Attributes to View: [ General ->] Logical Volume Size (Mbytes): 2048 Extent Size (Mbytes): 4 Contiguous Allocation: no Usage: Unused Bad Block Relocation: yes Access Permission: read/write If the access permission says, "Read Only", go into Actions, Modify and change it to read/write. --EEM > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > Tang, Wally, CTR, DMA-Riv/IT > Sent: Monday, April 26, 2010 4:27 PM > To: ids@iiug.org > Subject: RE: Physical restore failed [19853] > > Hi Bruce, > > I rechecked the full ownership permissions and privileges on the > devices, > they are correctly set as ownership, permissions, and privileges. But > the > restore still returned with error: > > Physical restore failed - function read archive backup failed code -2 > errno > 0 > > Wally Tang > DOD-Defense Media Center - IT > Lockheed Martin - IT > 23755 Z Street > Riverside, CA 92518-2017 > 951-413-2246 > E-mail: wally.tang.ctr@dma.mil > > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > Brucemarchu@aol.com > Sent: Friday, April 23, 2010 7:43 PM > To: ids@iiug.org > Subject: Re: Physical restore failed [19844] > > Wally, > > Try rechecking the full ownership permissions and privileges on the > devices > with ls -lL and not just with the usual ls -l. If you are using > symbolic links then also apply the ls -lL to the symbolic links. > > Regards, > Bruce > > *********************************************************************** > ***** > *** > Forum Note: Use "Reply" to post a response in the discussion forum. > > > *********************************************************************** > ******** > Forum Note: Use "Reply" to post a response in the discussion forum. **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.
Check Art's post from last night. He thinks the real problem is not your
devices, but your configuration. Post your onconfig, sqlhosts files and what
shows up in your online.log when you tried to run the restore.
--EEM
Quotage:
Wait, I didn't notice this before. The ontape output says:
> Physical restore failed - could not fork server connection
That means the real problem is that it could not start up the engine
instance after restoring the reserved pages so that the engine could
complete the restore. This is usually a problem with some parameter in the
ONCONFIG file or with the configuration of the server's sqlhosts file
entries. What does the server message log say at the time the engine tried
to start up last during the restore? The time of the restore below was:
April 22 at 13:03
Art
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Tang, Wally, CTR, DMA-Riv/IT
> Sent: Tuesday, April 27, 2010 8:23 AM
> To: ids@iiug.org
> Subject: RE: Physical restore failed [19873]
>
> Thank you, Everett. I checked the logical volumes as you suggested from
> SAM, they all have read/write permission.
>
> Please advice.
>
> Wally Tang
> DOD-Defense Media Center - IT
> Lockheed Martin - IT
> 23755 Z Street
> Riverside, CA 92518-2017
> 951-413-2246
> E-mail: wally.tang.ctr@dma.mil
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Everett Mills
> Sent: Monday, April 26, 2010 2:44 PM
> To: ids@iiug.org
> Subject: RE: Physical restore failed [19854]
>
> Wally-
>
> Here's something else you can check. I'm guessing that your devices are
> logical volumes. Look at the properties of the logical volumes in SAM.
> The
> access permission should be read/write:
>
> #sam
>
> Select "Disks and File Systems"
> Select "Logical Volumes"
> Highlight a logical volume you are using for your database
> Actions: View more information
>
> You should get something that looks like this:
>
> Logical Volume: lvol6
> Volume Group: invg01
>
> Attributes to View: [ General ->]
>
> Logical Volume Size (Mbytes): 2048 Extent Size (Mbytes): 4
> Contiguous Allocation: no Usage: Unused
> Bad Block Relocation: yes Access Permission: read/write
>
> If the access permission says, "Read Only", go into Actions, Modify and
> change
> it to read/write.
>
> --EEM
>
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> > Tang, Wally, CTR, DMA-Riv/IT
> > Sent: Monday, April 26, 2010 4:27 PM
> > To: ids@iiug.org
> > Subject: RE: Physical restore failed [19853]
> >
> > Hi Bruce,
> >
> > I rechecked the full ownership permissions and privileges on the
> > devices,
> > they are correctly set as ownership, permissions, and privileges. But
> > the
> > restore still returned with error:
> >
> > Physical restore failed - function read archive backup failed code -2
> > errno
> > 0
> >
> > Wally Tang
> > DOD-Defense Media Center - IT
> > Lockheed Martin - IT
> > 23755 Z Street
> > Riverside, CA 92518-2017
> > 951-413-2246
> > E-mail: wally.tang.ctr@dma.mil
> >
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> > Brucemarchu@aol.com
> > Sent: Friday, April 23, 2010 7:43 PM
> > To: ids@iiug.org
> > Subject: Re: Physical restore failed [19844]
> >
> > Wally,
> >
> > Try rechecking the full ownership permissions and privileges on the
> > devices
> > with ls -lL and not just with the usual ls -l. If you are using
> > symbolic links then also apply the ls -lL to the symbolic links.
> >
> > Regards,
> > Bruce
> >
> >
> ***********************************************************************
> > *****
> > ***
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
> >
> ***********************************************************************
> > ********
> > Forum Note: Use "Reply" to post a response in the discussion forum.
>
> ***********************************************************************
> *****
> ***
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
> ***********************************************************************
> ********
> Forum Note: Use "Reply" to post a response in the discussion forum.
Thanks, I am going through his suggestions.
Wally Tang
DOD-Defense Media Center - IT
Lockheed Martin - IT
23755 Z Street
Riverside, CA 92518-2017
951-413-2246
E-mail: wally.tang.ctr@dma.mil
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Everett Mills
Sent: Tuesday, April 27, 2010 6:35 AM
To: ids@iiug.org
Subject: RE: Physical restore failed [19874]
Check Art's post from last night. He thinks the real problem is not your
devices, but your configuration. Post your onconfig, sqlhosts files and what
shows up in your online.log when you tried to run the restore.
--EEM
Quotage:
Wait, I didn't notice this before. The ontape output says:
> Physical restore failed - could not fork server connection
That means the real problem is that it could not start up the engine
instance after restoring the reserved pages so that the engine could
complete the restore. This is usually a problem with some parameter in the
ONCONFIG file or with the configuration of the server's sqlhosts file
entries. What does the server message log say at the time the engine tried
to start up last during the restore? The time of the restore below was:
April 22 at 13:03
Art
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Tang, Wally, CTR, DMA-Riv/IT
> Sent: Tuesday, April 27, 2010 8:23 AM
> To: ids@iiug.org
> Subject: RE: Physical restore failed [19873]
>
> Thank you, Everett. I checked the logical volumes as you suggested from
> SAM, they all have read/write permission.
>
> Please advice.
>
> Wally Tang
> DOD-Defense Media Center - IT
> Lockheed Martin - IT
> 23755 Z Street
> Riverside, CA 92518-2017
> 951-413-2246
> E-mail: wally.tang.ctr@dma.mil
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Everett Mills
> Sent: Monday, April 26, 2010 2:44 PM
> To: ids@iiug.org
> Subject: RE: Physical restore failed [19854]
>
> Wally-
>
> Here's something else you can check. I'm guessing that your devices are
> logical volumes. Look at the properties of the logical volumes in SAM.
> The
> access permission should be read/write:
>
> #sam
>
> Select "Disks and File Systems"
> Select "Logical Volumes"
> Highlight a logical volume you are using for your database
> Actions: View more information
>
> You should get something that looks like this:
>
> Logical Volume: lvol6
> Volume Group: invg01
>
> Attributes to View: [ General ->]
>
> Logical Volume Size (Mbytes): 2048 Extent Size (Mbytes): 4
> Contiguous Allocation: no Usage: Unused
> Bad Block Relocation: yes Access Permission: read/write
>
> If the access permission says, "Read Only", go into Actions, Modify and
> change
> it to read/write.
>
> --EEM
>
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> > Tang, Wally, CTR, DMA-Riv/IT
> > Sent: Monday, April 26, 2010 4:27 PM
> > To: ids@iiug.org
> > Subject: RE: Physical restore failed [19853]
> >
> > Hi Bruce,
> >
> > I rechecked the full ownership permissions and privileges on the
> > devices,
> > they are correctly set as ownership, permissions, and privileges. But
> > the
> > restore still returned with error:
> >
> > Physical restore failed - function read archive backup failed code -2
> > errno
> > 0
> >
> > Wally Tang
> > DOD-Defense Media Center - IT
> > Lockheed Martin - IT
> > 23755 Z Street
> > Riverside, CA 92518-2017
> > 951-413-2246
> > E-mail: wally.tang.ctr@dma.mil
> >
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> > Brucemarchu@aol.com
> > Sent: Friday, April 23, 2010 7:43 PM
> > To: ids@iiug.org
> > Subject: Re: Physical restore failed [19844]
> >
> > Wally,
> >
> > Try rechecking the full ownership permissions and privileges on the
> > devices
> > with ls -lL and not just with the usual ls -l. If you are using
> > symbolic links then also apply the ls -lL to the symbolic links.
> >
> > Regards,
> > Bruce
> >
> >
> ***********************************************************************
> > *****
> > ***
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
> >
> ***********************************************************************
> > ********
> > Forum Note: Use "Reply" to post a response in the discussion forum.
>
> ***********************************************************************
> *****
> ***
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
> ***********************************************************************
> ********
> Forum Note: Use "Reply" to post a response in the discussion forum.
****************************************************************************
***
Forum Note: Use "Reply" to post a response in the discussion forum.
Hi,
as this thread is going on since a while now, I may be a bit lost ... :-(
But I assume that the latest error that you still get is this?:
> Physical restore failed - function read archive backup failed code -2
> errno 0
And you have no longer the error telling about "... could not fork server
..."?
Assuming the above, the error message
"Physical restore failed - function read archive backup failed"
seems to me pointing to a problem with reading the backup file - rather
than
writing the backup data to the restore files on disk. So I would check
things in
this direction ... Of interest may be:
- when does the error occur?
Pretty much right after answering the last prompt of the restore?
Or some time passes and ontape is doing something before the error
occurs?
- Is the backup just a single file? Or are several backup files involved?
- Is the backup file in a local file system? Or is it mounted from remote?
- Is the setting of TAPEBLOCKSIZE correct? I.e. is it the same as it was
when the backup was taken?
- Was the backup really successful? I.e. was all the data written to the
backup file(s)?
No data is missing due to the backup file being "full" during the backup
(check TAPESIZE parameter).
If the backup was taken with some script that expects that all backup
data fits into a single file,
then maybe it didn't anymore due to data growth, ontape requested a
second "tape" but nobody noticed
(because script is run unattended and error/return codes discarded)?
- Is the backup file readable by a UNIX system utility? Like "dd" run by
the same user as the restore?
- You may want to check, what ontape is doing during the restore. You can
use a system utility
like "truss" or "strace" to trace system calls. If there is a system
call stumbling upon a problem with
a file, this shoul dbe visible in the trace output ...: what is the real
error and errno of the system call and
what file was being worked on at the time ...
Finally, to be sure that the problem is not on the IDS server side:
- check, as suggested before by Art Kagel, the IDS message log file (see
MSGPATH parameter):- Is the IDS server started at all?
- Is it started correctly?
- Does it have problems itself (not caused by ontape) after a correct
start?
The answers to all of the above questions should allow some zeroing in on
the problem.
Regards, Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
IBM Deutschland Research & Development GmbH
Chairman of the Supervisory Board: Martin Jetter
Board of Management: Dirk Wittkopp
Corporate Seat: Boeblingen, Germany
Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294
ids-bounces@iiug.org wrote on 04/27/2010 03:23:20 PM:
>
> Thank you, Everett. I checked the logical volumes as you suggested from
> SAM, they all have read/write permission.
>
> Please advice.
>
> Wally Tang
> DOD-Defense Media Center - IT
> Lockheed Martin - IT
> 23755 Z Street
> Riverside, CA 92518-2017
> 951-413-2246
> E-mail: wally.tang.ctr@dma.mil
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Everett Mills
> Sent: Monday, April 26, 2010 2:44 PM
> To: ids@iiug.org
> Subject: RE: Physical restore failed [19854]
>
> Wally-
>
> Here's something else you can check. I'm guessing that your devices are
> logical volumes. Look at the properties of the logical volumes in SAM.
The
> access permission should be read/write:
>
> #sam
>
> Select "Disks and File Systems"
> Select "Logical Volumes"
> Highlight a logical volume you are using for your database
> Actions: View more information
>
> You should get something that looks like this:
>
> Logical Volume: lvol6
> Volume Group: invg01
>
> Attributes to View: [ General ->]
>
> Logical Volume Size (Mbytes): 2048 Extent Size (Mbytes): 4
> Contiguous Allocation: no Usage: Unused
> Bad Block Relocation: yes Access Permission: read/write
>
> If the access permission says, "Read Only", go into Actions, Modify and
> change
> it to read/write.
>
> --EEM
>
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> > Tang, Wally, CTR, DMA-Riv/IT
> > Sent: Monday, April 26, 2010 4:27 PM
> > To: ids@iiug.org
> > Subject: RE: Physical restore failed [19853]
> >
> > Hi Bruce,
> >
> > I rechecked the full ownership permissions and privileges on the
> > devices,
> > they are correctly set as ownership, permissions, and privileges. But
> > the
> > restore still returned with error:
> >
> > Physical restore failed - function read archive backup failed code -2
> > errno
> > 0
> >
> > Wally Tang
> > DOD-Defense Media Center - IT
> > Lockheed Martin - IT
> > 23755 Z Street
> > Riverside, CA 92518-2017
> > 951-413-2246
> > E-mail: wally.tang.ctr@dma.mil
> >
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> > Brucemarchu@aol.com
> > Sent: Friday, April 23, 2010 7:43 PM
> > To: ids@iiug.org
> > Subject: Re: Physical restore failed [19844]
> >
> > Wally,
> >
> > Try rechecking the full ownership permissions and privileges on the
> > devices
> > with ls -lL and not just with the usual ls -l. If you are using
> > symbolic links then also apply the ls -lL to the symbolic links.
> >
> > Regards,
> > Bruce
> >
> >
***********************************************************************
> > *****
> > ***
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
> >
***********************************************************************
> > ********
> > Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
****************************************************************************
> ***
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>