a script to shutdown database ..... - Forum - OpenEdge RDBMS - Progress Community

a script to shutdown database .....

 Forum

a script to shutdown database .....

This question is not answered

hi all ,

we used on solaris  to shutddown the database by writing this command in a script :

proshut  databasename -by

then dump the files on tape

then restart the database .

then this script is scheduled in the crontab .

but now  with openedge11.3 under windows server2012 R2

THE DATABSE IS STARTED USING OPENEDGE EXPLORER .

BUT  THE PARAMETER -BY WITH PROSHUT IS NOT WORKING .

WHAT IS THE BEST COMMAND TO SHUTDOWN A  DATABASE STARTED WITH OPENEDGE EXPLORER ,

SO THAT TO USE THIS COMMAND IN A BATCH FILE .

IN ORDER TO SCHEDULE IT  ....

All Replies
  • James is using -bibackup all only necessary for pre 11.5?  (11.3/11.4)  to avoid this defect?  knowledgebase.progress.com/.../000054854

    Or is it recommended for other reasons also?

  • somehow yes , we shutdown the databases and then we dump the folders on a tape

    If this means that you are doing an operating system backup of the database and you trust this more than a Progress backup, then you have got things exactly backwards.  Whether online or offline, a Progress backup is ***always*** to be preferred to insure the integrity of your database.

    Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice  http://www.cintegrity.com

  • I believe it's just for that defect, but it's a pretty nasty one if you do get bitten by it.

  • > I'll bite. What is the impact or trade off of bibackup all?

    The impact is that probkup online reverts to its pre-11.3 behaviour of backing up the entire BI file.  

    The probkup online default in 11.3 and later is "bibackup active", in which probkup online backs up only the active clusters in the BI file, which has the benefit of potentially reducing backup time and size, restore time, and the time that forward processing is stalled during the backup.

    The bug (PSC00317988) is in 11.3 and 11.4 and is fixed in 11.5 and later.

  • Fantastic details to be aware of. Thank you.