Cognos 8.3 to 8.4 UPGRADE

[sujju_tamma]

Hi Friends,

I am new to this site...
I need information on upgrade of cognos 8.3 to 8.4 ...if possible Please provide me step by step process..
Are there any advantages and disadvantages of upgrading cognos 8.3 to 8.4 ...
what are the issues do we face if we upgrade...
This info is required very quickly...Please provide me as early as possible..

[sivabisani]

Hi Friend,

As per my knowledge
I need information on upgrade of cognos 8.3 to 8.4 ...if possible Please provide me step by step processhttp://www.ibm.com/developerworks/data/library/cognos/cognosprovenpractices.html
what are the issues do we face if we upgrade...
1)Prompt Formatting -Size & Overflow functionality is not working properly in cognos 8.4(in 8.3 it's working properly)
ex: if u set the size and overflow as % to the prompt buttons.In the cognos viewer(output page) the buttons wont appear.
2)_make_timestamp () is not supporting
3)javascripts needs to be update with new functionalities.

Thanks and Regards,
Siva

[sujju_tamma]

Thanks Siva for your valuable answer and reply...

Here I am not going to use the contentstore upgrade ...as there are some other projects related data in it.

So, I am going to use Export and Import Procedure for this process..

Please let me know about this...

What issues we face after completing this.

[srinivas Pothula]

The goal of this document is to be able to easily back out in case of an
unforeseen issue.
2 Steps for Upgrading
1. Copy the production content store to a new database/instance (w/e is
relevant to the db being used). We'll call this 'test'
2. Using a dev server, install MR1 to a new directory and configure it to use
the 'test' content store
3. Upgrade the 'test' content store. Simply start the MR1 install (it always
does an upgrade check).
Other options include upgrading by package, folder or on a
report by report basis dependant on client requirements for
the upgrade (refer to the product documentation for more
detail on each of these steps).
4. Once the upgrade is complete, verify the content is what is expected.
5. Log cases where appropriate to have any issues fixed, testcases will be
required (incl. at a minimum: report spec, sample data, model and prompt
values. Possibly the content store)
6. If an upgrade is deemed successful, move the upgraded 'test' content
store back to the prod server.
7. Install MR1 to a new directory on production. Use different ports then the
RTM if you wish to have it running while you verify the installation.
8. Point the prod MR1 installation at the upgraded content store on the
production database.
9. Verify the installation/upgrade is acceptable.
10. Once verification is complete, switch to using the MR1 version and shut
down the RTM.

Regards,

Srini

[sujju_tamma]

Thanks Srini for your valuabler reply