Hi,
if I understood you correctly, then you did a so called "warm restore"
of this one dbspace ? I.e. the database server was still running with
all other dbspaces being OK ?
In that case you have to restore logical logs. The logical logs need
to be applied to this one restored dbspace to "let it catch up" with
the rest of the system, so that the whole system will be consistent
again.
Without logical log restore, the dbspace (only physically restored)
has the state of the time when the backup was done. But since the
system has moved on in the meantime (i.e. some work was done
in the other dbspaces), this physiaclly restored dbspace is not in
sync with the rest. Logical restore is needed to get it there.
If you do not have logical logs backed up, then you are at a loss at
this point. In this case all you can do is restore the complete system
(i.e. a cold restore), so that everything gets to the same state and
thus will be in sync. Of course that means you will loose the work
done since the last backup (level-0 or level-1) that is restored.
If you want to recover such work also, you need to backup and keep
logical logs so that you can restore them ...
The zipping and unzipping that you did with the backup sounds
about right. This should not be the problem.
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
owner-informix-list@iiug.org wrote on 26.05.2005 19:33:22:
> onstat -d shows ) free space>
> On 5/26/05, Gentian Hila <genti.tech@gmail.com> wrote:
> > I run a backup ontape -s which was saved to a file and then zipped it
> > through gzip and then unzipped it and restored through:
> >
> > ontape -r -D dbsdata> >
> > but I didn't restore any logical logs ? Should I have restored them.
> >
> > Now dbsdata shows as Disabled in DBSPACES status I get a ND for
dbsdata
> >
> > How can I enable it ?
>
> sending to informix-list
sending to informix-list