Alexei: Going straight from 6.0 to 8.0 seems pretty aggressive. We wanted to upgrade our 6.0 instance as fast as we could, but we went through 7.1 and 7.5 first. Each version showed incremental improvements, and it gave the users time to adjust to the changes in the look and feel. Good luck!
Greg: Actually, this is excatly what we want to avoid. We do not want end users to mess up with 7.1 and 7.5. We want them to directly jump to 8.0. The problem is that for every version if you want end users to use it it is a significant investment of time to train the users, reconfigure environment, rewrite custom portlets etc. We want to do it once :)
You cannot even upgrade directly from 6.0 to 7.5. You need to go from 6.0 -> 7.1 -> 7.5 -> 8.0. You do not need to expose each level to users, though.
If you do not have your database present when doing the upgrades, all of your current data will be lost. If you do not care about that, you could just do a clean install of 8.0 and not worry about the upgrade process at all.
Let me give a bit more insight about what we are trying to achieve. We have now HP PPM(Mercury) 6.0 up and running for several years. We want to upgrade it to 8.0 so that user will start using 8.0 right away. At the same time we want to preserve all user generated data in HP PPM during upgrade. So far we figured out that upgrade path will be:
As you can see there are three HP PPM upgrade steps and one Oracle upgrade step.
Hope this clarified what we want to achieve. Now we do a test upgrade to see how well data is transferred between the versions. So, we are setting up a test computer with v6.0 installed on it and all current data transferred to it.
Question: Do we need schema on Oracle to keep data or we can copy data to test server even without schema established and do an upgrade without schema?
check the chapter "Migrating Instances" of the SysAdmin Guide. It describt the needed steps to copy a whole ppm installation including the database. Use this guide to "clone" your existing PPM 6.0 installation
A short over view of the steps: -create a database -create the table spaces -create the needed schemas -make a dump of the existing ppm database -import the dump into your test db -run a view sql scripts
-copy the dir to your test machine -create a service with ksvc.exe if needed -modify a few server.conf parameter (i.e. BASE_URL)