Progress 9.1D won't connect Vantage 6.1

D

dreamweave12

New Member
We use progress 9.1D to connect our MRP software (Vantage 6.1). We run this off a virtual server with Windows Server 2003 (Standard Edition).

Over the past year the progress 9.1D either becomes corrupt or part of the file disappears because we can no longer start Vantage up. Users that are in Vantage can stay in, but anyone who isn't cannot connect.

The Vantage screen starts to boot up and then the whole program disappears. When you try to reinstall the Vantage software and it asks to locate the Progress file on your server its is not there even though it is there Vantage doesn't think it is there. The progress 9.1d folder is still there.

The only fix I have found successful is to copy the DB folder and revert to a snapshot on our VMWare to a known good state and then copy the latest DB back to the correct folder.

I apologize I am not an IT expert so my knowledge is very limited. Over the past year this has happened 4 times and lately it has happened twice in the last week.

Any help is very appreciated.
 
If a file in the progress install disappears or becomes corrupt, I would probably focus on the VMWare or another application. Sounds like a problem outside of Progress.
 
Never have I seen any bug in Progress that would cause files that make up the database disappear. Since you mention Windows I would speculate, that, for example, your virus scanner has gone rogue - quarantining your database files for whatever reason. I am absolutely not familiar with Windows 2003 in regard to removing files that are in use. In Unix you can do that - remove a file that is in use by another process. While the file is not visible to any other process anymore it will be really removed when the process that is using the file releases the file - thus making that process work as if nothing had happened. That would explain the behavior you see.

Even though your are running your database in a VM, you should regularly backup your database and turn After Image on. This would save you a lot of trouble when you need to restore the database for whatever reason.

Not saying anything about 9.1d though ...

Heavy Regards, RealHeavyDude.
 
RealHeavyDude said:
Never have I seen any bug in Progress that would cause files that make up the database disappear. Since you mention Windows I would speculate, that, for example, your virus scanner has gone rogue - quarantining your database files for whatever reason. I am absolutely not familiar with Windows 2003 in regard to removing files that are in use. In Unix you can do that - remove a file that is in use by another process. While the file is not visible to any other process anymore it will be really removed when the process that is using the file releases the file - thus making that process work as if nothing had happened. That would explain the behavior you see.

Even though your are running your database in a VM, you should regularly backup your database and turn After Image on. This would save you a lot of trouble when you need to restore the database for whatever reason.

Not saying anything about 9.1d though ...

Heavy Regards, RealHeavyDude.
Click to expand...

Thanks for the help.

I don't fully understand your last paragragh. Do you mind rephrasing? We do use Acronis to backup up our entire server nightly. Do you mean I should use Acronis to restore the Progress file that goes missing? The DB file does not seem corrupt since it copy and paste it back once I revert to the snapshot on the VMWare.

Thanks again for your time!
 
The "probkup" command is the only way to always be absolutely certain that you have made a complete and proper backup of the db.

If the Acronis backup is made with the db offline and if it includes all of the parts of the db then it is probably fine. But if the db is online it will probably be corrupted if restored. This is because 3rd party backups are unaware of the need for synchronization of all the files in the database and, more importantly, the data that is in shared memory waiting to be written to the db files.

A "snapshot" might be ok so long as all of the db files are included and synchronized. But you need to make sure of that and some serious recovery testing is a really good idea. You don't want to find out that it wasn't properly setup when you are in the midst of a high pressure recovery process...

After-imaging is the process of logging "redo notes" that can be "rolled forward" against a restored backup to reconstruct a database. When properly setup you use after-imaging to recover to any point in time right up to the point where a problem occurred. Backups only get you to the last (good) backup. After-imaging takes you all the way. Everyone who has valuable data in their database should always have after-imaging enabled. Not having ai turned on is DBA malpractice.

I agree with RHD -- the issue with disappearing files sounds an awful lot like a rogue virus scanner.

Progress 9.1D is ancient, obsolete and unsupported. You should upgrade. OpenEdge 11.3 is the current release of Progress.
 
You must log in or register to reply here.
Back
Top