Re: HELP - MFG/PRO and Progress versions

Hi Julie,

First off, I'm not a DBA and it's not my specialty and I also think you
should bring it up on the PEG.COM email group, you can even speak with
some of the Progress Software engine crew and some Progress VP's. I
think, this USENET forum is the most dead of the Progress forums and in
this respect it's even doing a mis-service.

I don't know if you're also moving to a diff platform and O/S and then
there are some option you may not be able to use. I think, the
conversion utility and the binary dump and load won't work in this
case.

AFAIK, the options are either the conversion utility especially if you
have a limited window of time for completing the conversion.

There are also a binary and ASCII dump and load. I.e. dumping the data
into files and loading them into the new database. You should do a dump
and load every once in a while to defrag and descatter ( is that even a
word ?? ) compact indices etc., in general compact and boost
performance especially if it hasn't been done in a long while.

Maybe you should try a multi-threaded ASCII dump and load. That will
work no matter what's the case. Which brings me to my next question
what's the database sizes ?

Besides that there are other things to consider, complications usually
tend to popup in our line of work. Like checking if any source files
are missing or the compiled r-code are diff from the source code ? I've
seen lot's of places where the source code was poorly managed
especially if there's been a substantial amount of customization.

So too sum things up, Let's continue this discussion on PEG.COM ( again
it's an email group not a website/forum i.e. you send and recieve email
) and we need more specifics i.e. exact versions, new O/S hardware,
database sizes etc. HTH



Julie Warden wrote:

> Group,
>
> We have an obsolete MFG/PRO Version 9.0 SP4 application that is currently
> running on Progress version 8.3. We need to replace the hardware which is
> very old, and will be upgrading the O/S, so keeping this version of
> Progress is probably not an option. Does anyone know if there will be any
> issues upgrading to Progress version 9?
>
> Since the app is obsolete and only occasionally used for inquiry, we want
> to do as little as possible. Compiling the code is expected, but what about
> database converions? There are 51 active databases on this host - sheesh!
>
> Thanks,
> Julie

.

Relevant Pages

  • Re: Is 5.0.7 ready for production?
    ... >> the database is started. ... Spent six hours on that server last night and this morning. ... does kick in and reboot the server if I wait. ... Progress to start up, but if a wait a while the machine locks instantly ...
    (comp.unix.sco.misc)
  • Re: Performance Issues
    ... I need your help in resolving performance issues. ... >> I am newly hired in a company that uses Progress Server ver. ... >> and run on one database located on one system. ...
    (comp.databases.progress)
  • Re: Trouble with JDBC
    ... These exceptions are due to no proper connection with the database ... Make sure to which version of Progress database you are connecting to ... because Progress 8.3B doesn't support Java(no jdbc drivers). ...
    (comp.databases.progress)
  • Re: Performance Issues
    ... I need your help in resolving performance issues. ... > I am newly hired in a company that uses Progress Server ver. ... > and run on one database located on one system. ...
    (comp.databases.progress)
  • Re: Creating a load simulator by calling Perl Programs - or Forking?
    ... regard (I hate progress indicators that merely indicate that the system ... If the waiting program is still running, and is still waiting, then the ... I am looking to load up the system, ... chuckle over the time halting comment... ...
    (comp.lang.perl.misc)