Awr dbms_sqltune package

Question

Hi,
Our company doesn't currently have oem installed on production. This will be done in March. Right now I am working with the sqltune package to access the database on the dev server before I run it on production. I was running the following procedure below and requested the GOLDUSER schema.
Down in the load_sqlset procdure I think I have the load_option and update_option set to the correct values. I could be wrong though. By setting these all I want is to extract the old sql statements and performace tune them.
I get those sql statements listed out and also I get a different named schema under "tables with new potential indices" (LEADUSERS).
Should I be concerned with this? Would someone just look this procedure over to see if it is correct?
I would appreciate your help in this matter.
Thanks in advance.
al
declare
cursor_1 dbms_sqltune.sqlset_cursor;
begin
open cursor_1 for
select value(p)
from table(dbms_sqltune.select_workload_repository)
750,
1501,
'parsing_schema_name= ''GOLDUSER'' AND executions > 25',
null,
null,
null,
null,
null,
10)) p;
dbms_sqltune.load_sqlset(
sqlset_name => 'prod_awr',
populate_cursor => cursor_1,
load_option => 'MERGE',
update_option => 'ACCUMULATE');
end;
/

Answer 1

Check this one:
http://www.oracle-base.com/articles/10g/AutomaticSQLTuning10g.php
OR
DECLARE
ret_val VARCHAR2(4000);
BEGIN
ret_val := dbms_sqltune.create_tuning_task(
task_name=>'t1',
sql_id=>' '); Execute the sql prior to this and get the sql_id in place it here
dbms_sqltune.execute_tuning_task('t1');
END;
check the status by,
SELECT status FROM DBA_ADVISOR_LOG WHERE task_name ='t1';
Upon completion of the above,
SET LONG 100000
SET LONGCHUNKSIZE 99999
SET LINESIZE 20000
SELECT DBMS_SQLTUNE.REPORT_TUNING_TASK( 't1') FROM DUAL;