The script is not in a text file. It is in a binary file that's why you cannot find it. Here it is CREATE TABLE ora_monitor.profiler_data ( runid NUMBER NOT NULL PRIMARY KEY, run_name VARCHAR2(100) CHECK (rtrim(run_name) != NULL), start_time DATE DEFAULT sysdate NOT NULL, user_runid NUMBER DEFAULT 1 NOT NULL, run_seq INTEGER DEFAULT 1 NOT NULL, user_sid NUMBER NOT NULL, user_name VARCHAR2(30) DEFAULT USER NOT NULL, run_cpu NUMBER DEFAULT 0, run_io NUMBER DEFAULT 0, run_memory NUMBER DEFAULT 0, run_sorts NUMBER DEFAULT 0, run_sort_ratio NUMBER DEFAULT 0, run_gets NUMBER DEFAULT 0, run_status VARCHAR2(12) DEFAULT 'INCOMPLETE', session_name VARCHAR2(100) CHECK (rtrim(session_name) != NULL), session_comments VARCHAR2(4000), run_source LONG); CREATE INDEX ora_monitor.i_profiler_data ON ora_monitor.profiler_data (user_name, session_name); GRANT SELECT, INSERT, DELETE, UPDATE ON ora_monitor.profiler_data TO PUBLIC; GRANT EXECUTE ON sys.dbms_profiler TO PUBLIC; Good luck! : Hi. : Nope. : Sorry, it creates only message box "DBMS_PROFILER package is not : installed, but : setup can continue nevertheless" (by the way, I have run PROFLOAD.SQL : script, : and it completed successfully, and actually I can see the package in SYS : schema), : and then another message box "Error executing PL/SQL script". : After that, setup completes and required table still does not exist (athough : user ORA_MONITOR does). : In fact, when I search files in DB Tools directory for context : "PROFILER_DATA", : nothing is found. It means the table is not gonna be created by these : scripts... : Looks strange, heh. : With best regards, : Koala
|