So the code which starts/stops your database is then I'm assuming all in the script /u01/oracle/proddb/9.2.0/appsutil/scripts/PROD_sjodb/addbctl.sh
That's certainly not a HP or Oracle provided script, so must be intrrnslly developed... however in all likelihood it will just contain a "ORACLE_HOME=/u01/oracle/proddb/9.2.0" statement that you can update (you might want to relocate the script somehwere under your new ORACLE_HOME as well)
Assuming that is the case, and assuming as you said that 10g is just going to be installed on a directory in an existing filesystem in the cluster then as I originally said there is no need to halt the cluster package. You might want to after the upgrade to test out failover, but you won't need to for the upgrade...
The tasks for upgrade will basically be:
1) With cluster package UP Follow standard Oracle upgrade process from 9i to 10g as described in the excellent metalink article 316889.1
2) When you are happy that the database has been fully upgraded, edit the package control file and update both the customer_defined_run_cmds and customer_defined_halt_cmds section to reflect the new path if you did move the file /u01/oracle/proddb/9.2.0/appsutil/scripts/PROD_sjodb/addbctl.sh
3) distribute the updated package control file to all cluster nodes
4) Now if you want to check everything is working correctly, just halt the package and restart (on both nodes if you want) to prove your changes worked... you seem to have indicated you know the process for this, but just in case...
cmhaltpkg oradbpkg
cmrunpkg -n
oradbpkg
----------------------------
of course if you don't want to move the file /u01/oracle/proddb/9.2.0/appsutil/scripts/PROD_sjodb/addbctl.sh and you've no intention of removing the old Oracle 9i home under /u01/oracle/proddb/9.2.0, the you really don't need to change anything at all in Serviceguard - you just need to update the addbctl.sh script with the new paths
HTH
Duncan
I am an HPE Employee