Solotion upgrade to 10.1.0.3, it show internal 500 error im em web console

Question

Note:
solotion upgrade from 10.1.0.2 to 10.1.0.3, it show internal 500 error im em web console
If you do not run the catpatch.sql script as described in this section and you start up a database for normal operation, then "ORA-13516: SWRF Operation failed: CATPROC not valid" errors will occur.
For RAC installations, start node applications on each node of the cluster as follows:
$ srvctl start nodeapps -n nodename
For single-instance installations, start the listener as follows:
$ lsnrctl start
Note:
If you are using the Oracle OLAP option, make sure that the listener is running.
If you are using ASM, start the ASM instance.
Use SQL*Plus to login to the database as the SYS user with SYSDBA privileges:
$ sqlplus "/ AS SYSDBA"
Start the database:
SQL> STARTUP
Set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
Set the value of the JAVA_POOL_SIZE initialization parameter to at least 120 MB:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='120M' SCOPE=spfile;
Shut down the database:
SQL> SHUTDOWN
Enter the following SQL*Plus commands:
Note:
If you are applying this patch set to a cluster database, then set the CLUSTER_DATABASE initialization parameter to FALSE before starting it in upgrade mode. After you have run the catpatch.sql script, reset this initialization parameter to TRUE.
SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catpatch.sql
SQL> SPOOL OFF
Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script.
This list provides the version and status of each SERVER component in the database.
If necessary, rerun the catpatch.sql script after correcting any problems.
Restart the database:
SQL> SHUTDOWN
SQL> STARTUP
Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
SQL> @?/rdbms/admin/utlrp.sql
Note:
When the 10.1.0.3 patch set is applied to an Oracle Database 10g Standard Edition database, there may be 42 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation.
If you are using the Oracle Recovery Manager catalog, enter the following command:
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;

Answer 1

Note:
solotion upgrade from 10.1.0.2 to 10.1.0.3, it show internal 500 error im em web console
If you do not run the catpatch.sql script as described in this section and you start up a database for normal operation, then "ORA-13516: SWRF Operation failed: CATPROC not valid" errors will occur.
For RAC installations, start node applications on each node of the cluster as follows:
$ srvctl start nodeapps -n nodename
For single-instance installations, start the listener as follows:
$ lsnrctl start
Note:
If you are using the Oracle OLAP option, make sure that the listener is running.
If you are using ASM, start the ASM instance.
Use SQL*Plus to login to the database as the SYS user with SYSDBA privileges:
$ sqlplus "/ AS SYSDBA"
Start the database:
SQL> STARTUP
Set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
Set the value of the JAVA_POOL_SIZE initialization parameter to at least 120 MB:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='120M' SCOPE=spfile;
Shut down the database:
SQL> SHUTDOWN
Enter the following SQL*Plus commands:
Note:
If you are applying this patch set to a cluster database, then set the CLUSTER_DATABASE initialization parameter to FALSE before starting it in upgrade mode. After you have run the catpatch.sql script, reset this initialization parameter to TRUE.
SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catpatch.sql
SQL> SPOOL OFF
Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script.
This list provides the version and status of each SERVER component in the database.
If necessary, rerun the catpatch.sql script after correcting any problems.
Restart the database:
SQL> SHUTDOWN
SQL> STARTUP
Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
SQL> @?/rdbms/admin/utlrp.sql
Note:
When the 10.1.0.3 patch set is applied to an Oracle Database 10g Standard Edition database, there may be 42 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation.
If you are using the Oracle Recovery Manager catalog, enter the following command:
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;