| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2111.1 | | IJSAPL::MONNINK_H | | Thu Feb 06 1997 13:01 | 10 |
| Cb,
You are right, on NT there is no deinstall option so you just have to
install LinkWorks.
But make sure that it is not running anymore, before starting the
install.
Han
|
| 2111.2 | Then guide is NOT correct ??? | TAV02::CHAIM | Semper ubi Sub ubi ..... | Thu Feb 06 1997 14:22 | 8 |
| Han,
So, if I understand you correctly, the documentation is NOT correct when it
says that LINKworks must be deinstallled on NT before upgrading?
Thanks,
Cb.
|
| 2111.3 | The guide is correct in a way... *8) | QCAV02::RAVISHANKAR | NoExplainationsAreNecessary!! | Fri Feb 07 1997 04:46 | 16 |
|
Cb,
To deinstall LinkWorks on NT you've to do the foloowing steps
1. Stop all the LinkWorks Processes.
2. Using Database Manager clear all the database devices ( not delete)
3. Using the registry editor locate and delete all Key instances of
LinkWorks.
4. Using the User Manager delete the users 'omdba', 'omusr' and
'ombgusr'.
5. Using the User Manager delete the Group OP.
6. Delete the path and files %OPROOT%
7. Re-boot the system.
Ravi.
|
| 2111.4 | | IJSAPL::MONNINK_H | | Fri Feb 07 1997 09:41 | 10 |
|
Cb,
The previous reply is correct if you want to remove the installed
LinkWorks including the databases. but that is not what you want!
On NT the documentation is incorrect, just install everything over the
current installation.
Han
|
| 2111.5 | What about data and pool... | TAV02::CHAIM | Semper ubi Sub ubi ..... | Sun Feb 09 1997 06:57 | 20 |
| > To deinstall LinkWorks on NT you've to do the foloowing steps
>
> 1. Stop all the LinkWorks Processes.
> 2. Using Database Manager clear all the database devices ( not delete)
Does this mean that after the installation is complete that the data must be
LNXBMed from a former LNXBM save operation?
What about the POOL area.
Please forgive me for making the following comments:
1. The installation guide is very unclear and I doubt that anyone could
properly upgrade from V3.0.8 (May/June version) to V3.0.8 (December version).
2. This procedure is VERY USER UNFRIENDLY.
Thanks,
Cb.
|
| 2111.6 | | IJSAPL::MONNINK_H | | Mon Feb 10 1997 10:12 | 11 |
| Cb,
Again, if you install it over the existing installation then you will
only replace the executables.
Running upgrade will (instmgmt, instcell) will make sure that the
database is also at the latest level.
Han
|
| 2111.7 | No need for lnxbm restore in upgrade prcess! | TAV02::SHAPIRA | | Mon Feb 10 1997 12:47 | 30 |
| >
>Does this mean that after the installation is complete that the data must be
>LNXBMed from a former LNXBM save operation?
>
>What about the POOL area.
>
>Please forgive me for making the following comments:
>
>1. The installation guide is very unclear and I doubt that anyone could
>properly upgrade from V3.0.8 (May/June version) to V3.0.8 (December version).
>
>2. This procedure is VERY USER UNFRIENDLY.
Cb,
Without going into the issue of the quality of the docs, the procedure for
*upgrading* is simple:
1. Backup your system + lnxbm, for safety reasons.
2. Run SETUP again.
3. Run Instmgmt and instcell in upgrade mode. (I'm not sure even if this is
needed)
The data and the pool will remain. No need for LNXBM restore (unless it is all
craching in the process...)
Regards,
Yariv
|
| 2111.8 | | IJSAPL::MONNINK_H | | Mon Feb 10 1997 12:54 | 3 |
| That is it.
Han
|
| 2111.9 | | FRAIS::SPALT | | Mon Feb 10 1997 15:13 | 4 |
| could anyone post info on which NT-file security needs to be applied
to the oproot-tree (omuser with FULL-CONTROL i guess) to gain max.
security. what about the sql-srv db and transaction-log-files and their
NT-file security ?? thx paule
|