Renaming packages - Fat client install

Hello, List,
I am planning to upgrade our productions system very soon. PY and PT are
already upgraded. Full PY package is built. According the manual I am going
to rename it to PD package, create the package with the same name, etc. So
server part is pretty fast.
What about client? I remember it was a way to install PY package, copy PY to
PD and run setup.exe with some keys so the client installation was very
fast.
If somebody remembers the key, please share you knowledge.
Thanks.

Regards, Alex Shevchenko

B7332 SP17, Oracle 8.1.7, Solaris production
XE SP18 Oracle 8.1.7, Solaris test

If you want good advise, build a new full package. This way you are sure the package was generate with the specs that were copied. You will be sure that all versions and all ESU will be regenerated. That is my two cents.

Hello, Adrian,
Thank you for your answer but are you sure it is a good advice? Probably it
is - in an ideal world. However I don't consider an option to send our
office for a week's vacation while I do the production upgrade, so I have a
time frame, which is one weekend, including time needed to rollback should
we have any problems. These are my 2 Canadian cents, which might be useful.
It is the way I have being using:
1. Copied Prod to CRP (B7332)
2.Upgraded CRP to PY
3. Applied Update4 to PY
4. Built a full PY package
5. Copy Central objects from PY7333 to PD7333
6. Copy PY7333 directories to PD7333 (enterprise and deployment servers)
7. Copy OL records for Production from Prototype.
8. On Saturday - Running the installation plan for the Production
9. Apply Update 4 to PD without specification merge
10. Copy PY package to PD package. Update package.inf file,
serverpackage.inf, cheat Package Assembly, etc. (It will save me about ten
hours and will not give me any package build issues)
11. Deploy the package.
12. On Sunday - last testing and deploying the clients.

You see - installation of many clients in the same time could be an issue.
If I can spread it on several days it will be better.
I did it once, but I forgot the keys. All right, I will handle that.

Regards, Alex.

I am with you Alex. I have done upgrades myself and one weekend is very
little time to do it all "by the book".

I cannot see much harm in renaming packages, if done correctly.

When you open the initial OW install CD, you will find ONE original full
package. During installation this will be copied to all pathcodes
installed, renaming the package names, fixing the package.inf files, etc.
I do not know why I would NOT do the same manually in the need of
completing an upgrade in one weekend.

I would prefer to have some extra hours available for some last minute
testing of my PD environment rather then waiting for hours for the
package build to complete. I can build this package the next night and my
world will be perfect again.

My 2 centavos (pretty worthless),
Gerd

Re: RE: Renaming packages - Fat client install

Sorry guys, that is what I do but I have been very fortunate that all my upgrades, Full packages take less than 9 hours. So once I finished the Prod data upgrade workbench on Friday, I start the package build, go back and sleep a few hours and the package is done. Then Saturday morning deploy and Saturday afternoon and Sunday are left for user testing.

I didn't realize that your packages took forever to finish so yes, I agree with Alex.