Moving db to a new host

T

TabulaRasa

New Member
Hi,

I am complete newbie to Progress db administration. We have to move progress db from one host to another. Application support suggested to stop db, copy files over to the correct folder \db and then run [FONT=&quot]prostrct repair <dbname>. It did work for one db but not the main, prod one.

The error message when I try to start db from Progress Explorer is:
Error in startup of database localhost:20931 ...
BROKER: ** This process terminated with exit code 1. (8619)
BROKER:** Cannot find or open file ... (wrong path to the file !), errno=2, (43) (JUNMsg024)

Obviously it is looking for a file in a wrong place :) but how to fix that?

Any help would be much appreciated, link to a relevant paragraph in Progress DBA guide or simple instructions how to correct the path and restart db?

Thanks

Mateo
[/FONT]
 
Its not the correct way to do the move from one host to another. Why dont you try to explain the complete picture.
1. OS on both hosts
2. Progress version
3. What application are you talking about
4. how many databases
5. What else runs on the host-01 along with the databases
6. What script are you trying to run and what all does it do..

Once you have all that information, maybe you will get a good answer that you can actually use and one that works.

HTH
 
Sorry, my bad

Both hosts running windows server 2003
DB version is 9.1
2 databases (PROD and RPT)
no other applications running on the new host. It si dedicated to host progress - it did have some old dev progress dbs ruuning on it but they have been stopped before the move.

No particular scripts:

1. stopped dbs on the source,
2. copied entire db folder to the new host,
3. ran prostrct repair <dbname>
4. Tried to start db through Progress Explorer

Above are the exact steps we tried

Regards

Mateo
[FONT=&quot]
[/FONT]
 
Generally there is nothing wrong copying the database with OS utilities as long as you know what you are doing ( know all files you need to copy and do not miss one ). Although I always recommend either procopy or a combination of probkup and prorest to make sure that you've got everything you need.

Obviously you were missing some files which belong to the database but do not reside in your db folder. Another possibility is that the structure description file which resides in the database folder is not up to date ...

Before copying a database with an OS copy you should do:

  • Just in case: Generate a version of the structure description that reflects the current structure of your database. You can do this with the prostrct list command.
  • Analyze the file created to be sure to pick up all files that are listed in it.
Most likely you skipped this steps and ended up with a corrupt database on the target host because you missed some files ...


Heavy Regards, RealHeavyDude.
 
Thanks mate for such propmt reply.

Back to reading instructions and trying again.

I might end up using backup/restore option, sound bit more reliable.

Regards

Mateo
 
Depending on the size of your database, a backup/restore could be a lot longer than doing a copy. Look at the RPT database .lg file and it may give you more information. Check the .st file that you have in your database folder, thats the one that it uses when you do the prostrct repairt <dbname>. If you have a different .st file that needs to be used to repair, you can prostrct repair <dbname> <stfilename>.

HTH
 
You must log in or register to reply here.
Back
Top