asked on

addm retention time

oracle 11.2.0.4
aix 6.1

I have retention time set to 100 days yet when I run an addm report I only get the last 3 days.
Can someone tell me why or how to get more days to display when I run an addm report?

ASKER CERTIFIED SOLUTION

Barry Cunney

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

bkreynolds48

ASKER

Snapshot Interval Retention Interval
------------------------- -------------------------
60 14400

Barry Cunney

Hi,
Also, if possible, please execute the following query on your Oracle server and post up the output:

select client_name,JOB_NAME,JOB_STATUS,JOB_START_TIME,JOB_DURATION from DBA_AUTOTASK_JOB_HISTORY where JOB_START_TIME >systimestamp -10 and client_name='auto optimizer stats collection'

Open in new window

Thank you

bkreynolds48

ASKER

no rows selected

bkreynolds48

ASKER

after looking at this carefully the addm script seems to skip over when asking for how many days - is that a bug in 11g? the awr report works fine in that area

Barry Cunney

Hi
Please log in as an administrator and execute the following

select client_name,JOB_NAME,JOB_STATUS,JOB_START_TIME,JOB_DURATION from DBA_AUTOTASK_JOB_HISTORY

Open in new window

The ADDM report analyzes data in the Automatic Workload Repository (AWR) so we need to try and establish if the AWR snapshots are running.

Please fully confirm which addm script you are running when it seems to skip over how many days

bkreynolds48

ASKER

I run this
@?/rdbms/admin/addmrpt

here is the output from the query

CLIENT_NAME JOB_NAME JOB_STATUS JOB_START_TIME JOB_DURATION
-------------------- ------------------------------ ------------------------------ --------------------------------------------------------------------------- ---------------------------------------------------------------------------
sql tuning advisor ORA$AT_SQ_SQL_SW_3023 SUCCEEDED 08-MAR-15 06.00.02.101237 AM AMERICA/NEW_YORK +000 00:07:25
sql tuning advisor ORA$AT_SQ_SQL_SW_3022 SUCCEEDED 07-MAR-15 06.00.00.714970 AM AMERICA/NEW_YORK +000 01:00:07
sql tuning advisor ORA$AT_SQ_SQL_SW_3021 SUCCEEDED 06-MAR-15 10.00.01.126940 PM AMERICA/NEW_YORK +000 01:00:08
sql tuning advisor ORA$AT_SQ_SQL_SW_3001 SUCCEEDED 05-MAR-15 10.00.02.153609 PM AMERICA/NEW_YORK +000 00:25:24
sql tuning advisor ORA$AT_SQ_SQL_SW_2981 SUCCEEDED 04-MAR-15 10.00.02.579243 PM AMERICA/NEW_YORK +000 00:42:49
sql tuning advisor ORA$AT_SQ_SQL_SW_2961 SUCCEEDED 03-MAR-15 10.00.02.645866 PM AMERICA/NEW_YORK +000 00:22:24
sql tuning advisor ORA$AT_SQ_SQL_SW_2941 SUCCEEDED 02-MAR-15 10.00.01.461957 PM AMERICA/NEW_YORK +000 00:49:35
sql tuning advisor ORA$AT_SQ_SQL_SW_2921 SUCCEEDED 01-MAR-15 06.00.02.346262 AM AMERICA/NEW_YORK +000 01:04:09
sql tuning advisor ORA$AT_SQ_SQL_SW_2901 SUCCEEDED 28-FEB-15 10.05.14.676949 AM AMERICA/NEW_YORK +000 00:42:28
sql tuning advisor ORA$AT_SQ_SQL_SW_2881 STOPPED 28-FEB-15 06.00.02.577019 AM AMERICA/NEW_YORK +000 01:10:33
sql tuning advisor ORA$AT_SQ_SQL_SW_2861 SUCCEEDED 27-FEB-15 10.00.02.386687 PM AMERICA/NEW_YORK +000 01:00:04
sql tuning advisor ORA$AT_SQ_SQL_SW_2841 SUCCEEDED 26-FEB-15 10.00.02.632426 PM AMERICA/NEW_YORK +000 01:00:04
sql tuning advisor ORA$AT_SQ_SQL_SW_2821 SUCCEEDED 25-FEB-15 10.00.01.515668 PM AMERICA/NEW_YORK +000 01:00:07
sql tuning advisor ORA$AT_SQ_SQL_SW_2801 SUCCEEDED 24-FEB-15 10.00.01.698962 PM AMERICA/NEW_YORK +000 01:00:08
sql tuning advisor ORA$AT_SQ_SQL_SW_2781 SUCCEEDED 23-FEB-15 10.00.02.474661 PM AMERICA/NEW_YORK +000 01:00:03
sql tuning advisor ORA$AT_SQ_SQL_SW_2761 SUCCEEDED 22-FEB-15 06.00.00.488434 AM AMERICA/NEW_YORK +000 00:03:44
sql tuning advisor ORA$AT_SQ_SQL_SW_2742 SUCCEEDED 21-FEB-15 06.00.02.512085 AM AMERICA/NEW_YORK +000 00:40:14
sql tuning advisor ORA$AT_SQ_SQL_SW_2741 SUCCEEDED 20-FEB-15 10.00.02.658893 PM AMERICA/NEW_YORK +000 01:00:11
sql tuning advisor ORA$AT_SQ_SQL_SW_2721 SUCCEEDED 19-FEB-15 10.00.02.597595 PM AMERICA/NEW_YORK +000 01:00:06
sql tuning advisor ORA$AT_SQ_SQL_SW_2701 STOPPED 18-FEB-15 10.00.01.244869 PM AMERICA/NEW_YORK +000 01:11:26
sql tuning advisor ORA$AT_SQ_SQL_SW_2681 SUCCEEDED 17-FEB-15 10.00.01.723992 PM AMERICA/NEW_YORK +000 01:00:02
sql tuning advisor ORA$AT_SQ_SQL_SW_2661 SUCCEEDED 16-FEB-15 10.00.02.623605 PM AMERICA/NEW_YORK +000 01:00:03
sql tuning advisor ORA$AT_SQ_SQL_SW_2641 SUCCEEDED 15-FEB-15 06.00.02.392991 AM AMERICA/NEW_YORK +000 01:00:02
sql tuning advisor ORA$AT_SQ_SQL_SW_2622 SUCCEEDED 14-FEB-15 06.00.02.499076 AM AMERICA/NEW_YORK +000 01:00:13
sql tuning advisor ORA$AT_SQ_SQL_SW_2621 SUCCEEDED 13-FEB-15 10.00.02.582411 PM AMERICA/NEW_YORK +000 01:00:11
sql tuning advisor ORA$AT_SQ_SQL_SW_2601 SUCCEEDED 12-FEB-15 10.00.02.669640 PM AMERICA/NEW_YORK +000 01:00:08
sql tuning advisor ORA$AT_SQ_SQL_SW_2581 SUCCEEDED 11-FEB-15 10.00.02.584115 PM AMERICA/NEW_YORK +000 01:00:08
sql tuning advisor ORA$AT_SQ_SQL_SW_2561 STOPPED 10-FEB-15 10.00.03.058555 PM AMERICA/NEW_YORK +000 01:11:21
sql tuning advisor ORA$AT_SQ_SQL_SW_2541 SUCCEEDED 09-FEB-15 10.00.02.767130 PM AMERICA/NEW_YORK +000 00:03:32
sql tuning advisor ORA$AT_SQ_SQL_SW_2521 SUCCEEDED 08-FEB-15 06.00.02.557875 AM AMERICA/NEW_YORK +000 00:02:49
sql tuning advisor ORA$AT_SQ_SQL_SW_2502 SUCCEEDED 07-FEB-15 06.00.02.547184 AM AMERICA/NEW_YORK

bkreynolds48

ASKER

I read through the script - it was defining number of days as 3 instead of asking for the number of days

bkreynolds48

ASKER

now that I know the issue, I can deal with that. Do you know of a book where I can study more about the addm and awr reports and how to adjust them to find just the data I want to see instead of looking at all of the data on the report?