Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can not restore database

Status
Not open for further replies.

Likes

Programmer
Apr 12, 2001
1
TH
Hi everybody,

I have a problem about restore database process.
Error message followed :

28932 28930 /usr/users/informix/corona21/bin/onbar_d -r
28932 28930 Successfully connected to Storage Manager.
28932 28930 Begin salvage for log 54.
28932 28930 Completed salvage of logical log 54.
28932 28930 Begin salvage for log 55.
28932 28930 Completed salvage of logical log 55.
28932 28930 Successfully connected to Storage Manager.
28932 28930 Begin cold level 0 restore rootdbs (Storage Manager copy ID: 8342 0).
28932 28930 Completed cold level 0 restore rootdbs.
28932 28930 Successfully connected to Storage Manager.
28932 28930 Unable to close the storage space restore: buc_fe.c : Archive API processing failed at line 920 for msgtype.
28932 28930 SQL -25582 Network connection is broken.
28932 28930 ISAM 9 Bad file number

This error messages was occur when I used command "onbar -r" .
That process wasn't complete until I killed that process. That means I wasn't restore successful.
My environment like this:
Server:: Solaris 2.6 , Informix Database Server 9.1.2 , Networker 5.0.1 , Informix Business Suite Module 1.0.1
Client:: Solaris 2.6 , Informix Database Server 7.2 , Networker 5.0.1 , Informix Business Suite Module 1.0.1

The solution that I used to backup/recover is Storege Node. I was backup data and log but client must read index via network.

Regardly,
Likes.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top