Upgrade OnDemand 8.3 to 8.5

[fbucchi]

Hello, I have to upgrade Ondemand 8.3 (7.1.2.6) to 8.5 and I read some articles in this forum about that and also IBM technical documents. I would make the migration in the following way, but I would like your opinion if you have already been through this experience ..

Current Architecture
AIX: 5.3.11.0 64-bit
OnDemand: 7.1.2.6
DB2: 8.2 FP7 32-bit
TSM Client API: 5.5 32-bit

Architecture after upgrade
AIX: 6.1 64 bit
OnDemand: 8.5.0.4 64-bit
DB2: 9.7 FP5 64-bit
TSM Client API: 6.2 64-bit

Initially we will clone the current server into a new server, in this way, my idea is to make all the migration in the new hardware without users connected working with the application and also have the server available for download/upload services, software installation, etc, etc.

The tasks would be:

1. Backup OnDemand Database, File Systems and configuration files
2. Migrate OnDemand instance from 32 to 64 bits
3. Application test
4. Upgrade OnDemand 7.1.2.6 to 7.1.2.15 (I think may be is not necessary)
5. Application test
6. Install DB2 9.7 64 bits
7. Install latest DB2 9.7 fix pack
8. Backup OnDemand Database, File Systems and configuration files
9. DB2 Upgrade process to convert OnDemand Database from 8.2 to 9.7
10. Uninstall OnDemand 8.3
11. Install OnDemand 8.5.0.0 and 8.5.0.0 ODWEK
12. Run commands to use Database with OnDemand 8.4.1 or higher
   arsdb-I instance_name-uv
   arsdb-I instance_name-mv

13. Run commands to modify System Log table
   arssyscr -I instance_name -l
   arstblsp -I instance_name -a 1 -g "System Log"

14. Run commands to create table System Load
   i. Run the Following SQL query:
   select id from arssys

   ii. If the value returned is less than 5000, run the Following SQL command:
   Update Arssys UPDATE SET id = 5000

   iii. Run the Following Command:
   arssyscr-I instance_name-a

15. Recreate ARSUSRGRP, ARSLOAD, ARSNODE, and tables index ARSAPP
   i. Drop the indexes:
   arsdb-I instance_name-efv arsusrgrp
   arsdb-I instance_name-efv arsload
   arsdb-I instance_name-efv arsnode
   arsdb-I instance_name-efv arsapp

   ii. Create the new indexes:
   arsdb-I instance_name-rfv arsusrgrp
   arsdb-I instance_name-rfv arsload
   arsdb-I instance_name-rfv arsnode
   arsdb-I instance_name-rfv arsapp

   iii. Reorg and update statistics on all the OnDemand system tables:
   arsdb-I instance_name-mv

16. Install IBM Global Security Kit Crypt V8 and IBM Global Security Kit V8 SSL
17. Application test
18. Backup OnDemand Database, File Systems and configuration files
19. Upgrade OnDemand and ODWEK to 8.5.0.4 following instructions of each readme
20. Application test
21. Upgrade TSM API Client from 5.5 32 bits to 6.2 64 bits
22. Application test
23. Install WAS 7.0.0.0
24. Install latest WAS 7.0 fix pack
25. Install 1.0.4.4 WEBi
26. OnDemand testing from WEBi

If everything goes well, I'll plan the migration to OD 9.

I appreciate your comments and suggestions
Thanks and regards
Federico Bucchi

[Justin Derrick]

Hi Federico!

Thanks for posting this checklist -- but I have two questions...

Is step 14 for fixing the System Log bug in the 8.4 upgrade?

What is step 15 for?  Doesn't arsdb -uv do this for you?

-JD.

[fbucchi]

Hi Justin! I hope you 're well.. Some of these steps (14 and 15 included) I extracted from technote 21446135

http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21446135

but I'm trying to know f these steps make sense and if the upgrade would work in this way.

Thanks and regards
Federico Bucchi

[kbsiva]

Hi ,

 I did step 16 right after step 11 . Also you have not mentioned setting the code page in ars db config file. None of the ars database commands would work they will give you a error message. I did not do step 14. We upgraded from on demand 7.x to 8.4.1 to 8.5.0.5 and have was 7.0.0.23 and webi 1.0.4.4

[fbucchi]

Hi Kbsiva, good morning.. .. thanks for your reply and suggestions. Regarding the code page, if you refer to the following

Steps to Set the value of ARS_ORIGINAL_CODEPAGE
       - UNIX Servers
           Run-u arsdb without ARS_ORIGINAL_CODEPAGE in the ars.cfg for
           information on the proper setting for ARS_ORIGINAL_CODEPAGE.

           An example of running the arsdb-u-I command without <OD_INSTANCE>
           ARS_ORIGINAL_CODEPAGE in the ars.cfg is:
             arsdb: Unable to initialize environment. The return code is -1.
                   If this is a new (created in 8.5) instance, then define
                   In ars.cfg ARS_ORIGINAL_CODEPAGE = 819. Otherwise, if this is
                   an existing instance (created prior to 8.5), then define
                   In ars.cfg ARS_ORIGINAL_CODEPAGE = 923. Once set,
                   ARS_ORIGINAL_CODEPAGE must never change.

           Edit the file and add the ars.cfg ARS_ORIGINAL_CODEPAGE parameter set
           Appropriate to the value arsdb Determined by the command.

I contemplated in step 19, since this information is from Fix Pack 2 and later .. If not this, what are you referring to?

Based on their experience, does make sense the rest of the steps?
Thanks in advance
Regards
Federico Bucchi

[kbsiva]

Hi,
 Good afternoon. Yes that is after Step 19, it is needed only when you upgrade from 8.5.0.0 to higher versions. Sorry I did not mention after what step. I did not face any major issue with the upgrade itself. Just followed the read me and it was pretty straight forward.

Thanks
Siva

[fbucchi]

Hi Siva....thanks for your reply. I'll let you know after upgrade!
Regards and have good weekend!
Federico Bucchi

[rgator]

Normally the upgrade path is to install fixpacks on top of what you already have...
I'm wanting to go from 8.4.1.5 to 9.0.. I have to go through 8.5...
but don't understand the uninstall current version and install 8.5 piece..

Does it really take the full install for 8.5?
How do you install the full base and not lose what you have already installed?