Method R Discussion GroupMethod R helps developers, DBAs, and decision-makers optimize Oracle-based software in every phase of the software life cycle. |
||
Discuss Method R products, techniques, and events. Ask new questions or post your own responses. |
For those of you who may be at the same level of Oracle Experience as I am (we all have to start somewhere, right?), here are a couple of issues I had with the install, with solutions explained (both require a sysdba logon):
1. We had hardened our DB by revoking DBMS_RANDOM from Public - so I had to explicitly grant it to the Hotsos ILO owner. 2. The creation of the Public synonym DBMS_SUPPORT failed (and no indication was given for the failure :( ) - so we had to manually create the synonym. Then, if you noticed, Hotsos provides a neat, yet undocumented, Unit Test Script that actually tests the ILO install. If you change directories to the Unit_Tests directory (within your Hotsos_2.1 directory) and logon to sqlplus as the Hotsos ILO owner, you can execute the @test.sql test script and this is what you can expect to see: Package created. No errors. Package body created. No errors. Package created. No errors. Package body created. No errors. Package created. No errors. Package body created. No errors. ============================================================ HOTSOS_SYSUTIL Unit tests for version 2 ============================================================ *** Turn tracing on *** *** Writing unit test message to trace file *** *** Writing datestamp to trace file *** *** Writing unit test message to alert log *** *** Turn tracing off *** * Check Defaults: get_db_major_ver - 9-------------------------> SUCCESS * Check Defaults: get_spid - 288-------------------------------> SUCCESS * Check Defaults: get_session_type - USER----------------------> SUCCESS * Check Defaults: get_instance_name - ipdev1-------------------> SUCCESS * Check Defaults: get_service_name - --------------------------> FAILURE * Check Defaults: get_session_user - HOTSOS--------------------> SUCCESS * Check Defaults: get_ip_address - ----------------------------> SUCCESS * Check Defaults: get_terminal - IPDBDNV01---------------------> SUCCESS * Check Defaults: get_session_id - 127680----------------------> SUCCESS * Check Defaults: get_os_user - PAYCHEX\gfrechet---------------> SUCCESS * Check Defaults: get_session_id - 127680----------------------> SUCCESS * Check Defaults: get_client_id - PAYCHEX\gfrechet~IPDBDNV01~sqlplus.exe-> SUCCESS * Check After SET: get_client_id = UT_CLIENT_ID----------------> SUCCESS * Check After RESET: get_client_id = PAYCHEX\gfrechet~IPDBDNV01~sqlplus.exe-> SUCCESS * Package Results ---------------------------------------------> FAILURE ============================================================ HOTSOS_SYSUTIL Unit tests completed with failures. ============================================================ ============================================================ *** Please verify that a trace file was generated with entries *** corresponding to the preceding tests, and that an entry was *** written to the alert log. ============================================================ ============================================================ HOTSOS_ILO_TIMER Unit tests for version 2 ============================================================ * Package Results ---------------------------------------------> SUCCESS ============================================================ HOTSOS_ILO_TIMER Unit tests completed successfully. ============================================================ ============================================================ HOTSOS_ILO_TASK Unit tests for version 2 ============================================================ * Check Defaults: get_nesting_level for 0----------------------> SUCCESS * Check After SET: get_nesting_level for 7---------------------> SUCCESS * Check Defaults: get_is_apps for FALSE------------------------> SUCCESS * Check After SET: get_is_apps for TRUE------------------------> SUCCESS * Check Defaults: get_trace for FALSE--------------------------> SUCCESS * Check Defaults: get_write_wall_time for FALSE----------------> SUCCESS * Check if GET_CONFIG returns TRACE = FALSE--------------------> SUCCESS * CHECK if GET_CONFIG returns WALL = FALSE---------------------> SUCCESS * Check After SET: get_trace for TRUE--------------------------> SUCCESS * Check After SET: get_write_wall_time for TRUE----------------> SUCCESS * Check After SET if GET_CONFIG returns TRACE = TRUE-----------> SUCCESS * CHECK After SET if GET_CONFIG returns WALL = TRUE------------> SUCCESS * Check After SET: get_trace for TRUE--------------------------> SUCCESS * Check After SET: get_write_wall_time for FALSE---------------> SUCCESS * Check After SET if GET_CONFIG returns TRACE = TRUE-----------> SUCCESS * CHECK After SET if GET_CONFIG returns WALL = FALSE-----------> SUCCESS * Check After SET: get_trace for TRUE--------------------------> SUCCESS * Check After SET: get_write_wall_time for TRUE----------------> SUCCESS * Check After SET if GET_CONFIG returns TRACE = TRUE-----------> SUCCESS * CHECK After SET if GET_CONFIG returns WALL = TRUE------------> SUCCESS * Check After SET: get_trace for FALSE-------------------------> SUCCESS * Check After SET: get_write_wall_time for TRUE----------------> SUCCESS * Check After SET if GET_CONFIG returns TRACE = FALSE----------> SUCCESS * CHECK After SET if GET_CONFIG returns WALL = TRUE------------> SUCCESS * Check After SET: get_trace for FALSE-------------------------> SUCCESS * Check After SET: get_write_wall_time for FALSE---------------> SUCCESS * Check After SET if GET_CONFIG returns TRACE = FALSE----------> SUCCESS * CHECK After SET if GET_CONFIG returns WALL = FALSE-----------> SUCCESS * V_REC_BAS = V_REC_RETURN : Single Level----------------------> SUCCESS * V_TAB_BAS = V_TAB_RETURN : Single Level----------------------> SUCCESS * V_REC_BAS = V_REC_RETURN : Two Levels------------------------> SUCCESS * V_TAB_BAS = V_TAB_RETURN : Two Levels------------------------> SUCCESS * V_REC_BAS = V_REC_RETURN : Three Levels----------------------> SUCCESS * V_TAB_BAS = V_TAB_RETURN : Three Levels----------------------> SUCCESS * V_REC_BAS = V_REC_RETURN : Two Levels After End--------------> SUCCESS * V_TAB_BAS = V_TAB_RETURN : Two Levels After End--------------> SUCCESS * V_REC_EMPTY = V_REC_RETURN : AFTER END_ALL_TASKS-------------> SUCCESS * V_TAB_EMPTY = V_TAB_RETURN : AFTER END_ALL_TASKS-------------> SUCCESS * Package Results ---------------------------------------------> SUCCESS ============================================================ HOTSOS_ILO_TASK Unit tests completed successfully. ============================================================ PL/SQL procedure successfully completed. Package dropped. Package dropped. Package dropped. I hope this post is helpful to others. (Cary, trying to put that diamond in my manager's hand) Thanks, |
Powered by FogBugz