升级ORACLE CLUSTERWARE执行root102.sh时报如下错误： /usr/lib/hpux64/dld.so: Unable to find library 'libclntsh.so.10.1'. /sbin/init.d/init.cssd[757]: 22886 Killed /usr/lib/hpux64/dld.so: Unable to find library 'libclntsh.so.10.1'. /sbin/init.d/init.cssd[763]: 22949 Killed /usr/lib/hpux64/dld.so: Unable to find library 'libclntsh.so.10.1'. /sbin/init.d/init.cssd[763]: 23005 Killed /usr/lib/hpux64/dld.so: Unable to find library 'libclntsh.so.10.1'. /sbin/init.d/init.cssd[763]: 23127 Killed /usr/lib/hpux64/dld.so: Unable to find library 'libclntsh.so.10.1'. /sbin/init.d/init.cssd[763]: 23184 Killed
解决方法：
修改'libclntsh.so.10.1' and 'libttsh10.so'文件的权限为755，owner为oracle.
重新执行root102.sh即可。
接下来就是升级db software以及数据字典即可。 通过dbua或手工升级。
11. For Oracle RAC installations: a. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges: b. $ sqlplus /nolog c. SQL> CONNECT SYS AS SYSDBA d. Enter password: SYS_password e. SQL> STARTUP NOMOUNT f. Set the CLUSTER_DATABASE initialization parameter to FALSE: g. SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile; h. Shut down the database: i. SQL> SHUTDOWN 12. Enter the following SQL*Plus commands: 13. SQL> STARTUP UPGRADE 14. SQL> SPOOL patch.log 15. SQL> @?/rdbms/admin/catupgrd.sql 16. SQL> SPOOL OFF 17. Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script. This list provides the version and status of each SERVER component in the database. 18. If necessary, rerun the catupgrd.sql script after correcting any problems. 19. Restart the database: 20. SQL> SHUTDOWN IMMEDIATE 21. SQL> STARTUP 22. 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. 23. SQL> @?/rdbms/admin/utlrp.sql 24.
Note: When the 10.2.0.4 patch set is applied to an Oracle10g Standard Edition database, there may be 54 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation. Ignore any messages indicating that the database contains invalid recycle bin objects similar to the following: BIN$4lzljWIt9gfgMFeM2hVSoA==$0
25. Run the following command to check the status of all the components after the upgrade: 26. SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY; In the output of the preceding command, the status of all the components should be VALID for a successful upgrade. 27. If you are using the Oracle Recovery Manager catalog, enter the following command: 28. $ rman catalog username/password@alias 29. RMAN> UPGRADE CATALOG; 30. For Oracle RAC installations: a. Set the CLUSTER_DATABASE initialization parameter to TRUE: b. SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile; c. Restart the database: d. SQL> SHUTDOWN IMMEDIATE e. SQL> STARTUP f. Start any database services that you want to use: g. $ srvctl start service -d db_name -s service_name 31. To configure and secure Enterprise Manager follow these steps: Ensure the database and Listener are operational. o In the case of a single instance, execute o emca -upgrade db o In the case of Oracle Real Application Clusters (RAC), execute o emca -upgrade db -cluster
