10.2.0.2 Upgrade Tips

Question

Yesterday I tried to upgrade my 10.2.0.1 to 10.2.0.2 on my RHEL3 box,then I run into the problem with the "ORA-00821: current sga_target=210M , need at least 316M" during the postinstallation when I tried to startup upgrade. Luckily I found a solution in the Asktom.com (and alydan.com too), However, I could not use his solution directly, Because I use "startup force pfile=init$my_SID.temp", I could only mount the instance but not open and got the error ORA-01092 ("ORACLE instance terminated. Disconnected force") After i checked with my alert log, whcih suggested me to use "UPGRADE" instead of "FORCE", and it worked. So I could continue with the regular upgrade processes. Here are the summary of my steps:
1. cd $ORACLE_HOME/dbs
2. strings -a spfile$my_SID.ora > init$my_SID.temp
mv spfile$my_SID.ora spfile$my_SID.ora.old
3. vi init$my_SID.temp, increase the sga_target up above 320M
4. at oracle user setting, connect / as sysdba
5. SQL> startup upgrade pfile='$ORACLE_HOME/dbs/init$my_SID.temp'
6 SQL> ORACLE instance started.
Database mounted
Database open
7 SQL> create spfile from pfile='$ORACLE_HOME/dbs/init$my_SID.temp';
File created
8. SQL> exit
9. at prompt login as sysdba again
10. SQL> startup upgrade
the rest steps will be same as in the metalink note 4547817. It came out everything fine till now. I think the original metalink note should tell people to alter system set the sga_target=316M; (or above) when altering other initialization parameters. So this problem will not show out.

Answer 1

It does in a way. You just have to make the connection to what they are trying to say.
If you look at step 6 in Section 7.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters
6. If you use Automatic Shared Memory Management, ensure that the value of the SGA_TARGET initialization parameter size is at least 50M greater then sum of the values SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters.
They could have been a little more clear.