homerslmpson
asked on
Help with Solaris 2.4 Importing of a Database
We have a very old SUN SPARC workstation running Solaris 2.4 (SunOS v5.4).
It's being used to run Sybase. The database in it is acting up. We have a spare SUN workstation with nearly identical specs and are trying to restore the backup database from workstation to the other.
When we try to do this, we get the following error message:
Msg 7205, Level 17, State 2:
Line 1:
Can't open a connection to site 'SYB_BACKUP'. See the error log file in the SQL Server boot directory.
Unfortunately I don't know where the error log file is. I am not familiar with Solaris.
That is how we tried to restore the database backup:
1. Use RCP to copy the dump file from the spare server to the primary server. And name the copy "frombkup_mydb.dump".
2. Drop the old database from the primary server, and re-create an empty one.
3. Then use the following command to load the database from the backup dump file:
load database mydb from "/export/home/syb11.dump/f rombkup_my db.dump"
Does anyone know why the restore doesn't work?
Please help if possible.
It's being used to run Sybase. The database in it is acting up. We have a spare SUN workstation with nearly identical specs and are trying to restore the backup database from workstation to the other.
When we try to do this, we get the following error message:
Msg 7205, Level 17, State 2:
Line 1:
Can't open a connection to site 'SYB_BACKUP'. See the error log file in the SQL Server boot directory.
Unfortunately I don't know where the error log file is. I am not familiar with Solaris.
That is how we tried to restore the database backup:
1. Use RCP to copy the dump file from the spare server to the primary server. And name the copy "frombkup_mydb.dump".
2. Drop the old database from the primary server, and re-create an empty one.
3. Then use the following command to load the database from the backup dump file:
load database mydb from "/export/home/syb11.dump/f
Does anyone know why the restore doesn't work?
Please help if possible.
My guess was when you restore the database onto a "new" server, there must be a license requirment, that was why it tried to connect to the database website ...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I actually got the answer from somewhere else.
The other answer was very close. But it was not specific.
The other answer was very close. But it was not specific.