| Title: | DEC/EDI |
| Notice: | DEC/EDI V2.1 - see note 2002 |
| Moderator: | METSYS::BABER |
| Created: | Wed Jun 06 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3150 |
| Total number of notes: | 13466 |
Hi, A customer is about to move his V1.3A + Filebridge system to a new VAX. The new system has different disc names. It seems that all he has to do is to add the new definition of DECEDI$TOP into decedi$sylogicals.com - is that enough? Is there anything extra which Filebridge requires? Are the old disc names held anywhere else which should be changed? He has Oracle support coming in to ensure RDB is healthy after the move, so it's only EDI and FBR specific worries he has. Thanks for any recommendations grahame
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3064.1 | where is edi$disk defined? | ZUR01::ASHG | Grahame Ash @RLE | Wed Mar 19 1997 15:33 | 8 |
From the FBR conf, I gather we only need to edit fbr$startup.com. DECEDI$TOP is defined from EDI$DISK, so it would probably make more sense to redefine this - I can't see where EDI$DISK is defined! Thanks, grahame | |||||
| 3064.2 | Good news if it's really this simple | ZUR01::ASHG | Grahame Ash @RLE | Thu Mar 20 1997 07:59 | 19 |
OK, I can't find any advice to contradict the assumptions I'm making, which are: - DEC/EDI and FBR reference the databases only via logical names defined in their startup command files. - if the whole system is moved, then redefining the logical names within these command files is all that is necessary - the Oracle people will be taking care that the databases themselves are OK (i.e. they don't need to know of any 'special' ways in which our products use the DBs) If anyone feels I'm about to shoot myself in the foot (and the customer in the head!), please let me know asap as the move is this weekend. Cheers, grahame | |||||
| 3064.3 | METSYS::THOMPSON | Thu Apr 03 1997 13:04 | 5 | ||
How did it go? Everything ok? cheers Mark | |||||