[20130603]dbms_space.object_growth_trend.txt

简介: [20130603]dbms_space.object_growth_trend.txt10G开始dbms_space.object_growth_trend包,来显示和预计每个段的增长情况.
[20130603]dbms_space.object_growth_trend.txt

10G开始dbms_space.object_growth_trend包,来显示和预计每个段的增长情况.这些信息来源于awr信息.

The column QUALITY has 3 different values: "GOOD", "INTERPOLATED", "PROJECTION".

- The "GOOD" value indicates that the space allocated and usage figures are accurate for that day.

- The "PROJECTED" value indicates that the space calculations are projected from the data collected by the AWR facility,
  not collected directly from the segment.

- The "INTERPOLATED" value indicates that the value was not really collected or projected from the AWR facility.

more details can be found in the : Oracle documentation

QUALITY: A value indicating how well the requested reporting interval matches the actual recording of statistics. This
information is useful because there is no guaranteed reporting interval for object size use statistics, and the actual
reporting interval varies over time and from object to object.  The values of the QUALITY column are:

-- GOOD: The value whenever the value of TIME is based on recorded statistics with a recorded timestamp within 10% of
the INTERVAL specified in the input parameters.

-- INTERPOLATED: The value did not meet the criteria for GOOD, but was based on recorded statistics before and after the
value of TIME. Current in-memory statistics can be collected across all instances in a cluster and treated as the
"recorded" value for the present time.

-- PROJECTION: The value of TIME is in the future as of the time the table was produced. In a Real Application Clusters
environment, the rules for recording statistics allow each instance to choose independently which objects will be
selected.

SQL> select * from table(dbms_space.OBJECT_GROWTH_TREND('SCHEMA','XXXX','TABLE'));

TIMEPOINT                      SPACE_USAGE SPACE_ALLOC QUALITY
------------------------------ ----------- ----------- --------------------
04-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
05-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
06-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
07-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
08-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
09-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
10-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
11-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
12-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
13-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
14-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
15-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
16-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
17-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
18-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
19-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
20-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
21-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
22-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
23-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
24-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
25-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
26-MAY-13 04.48.58.980716 PM     703755048   771751936 INTERPOLATED
27-MAY-13 04.48.58.980716 PM     708877817   780140544 GOOD
28-MAY-13 04.48.58.980716 PM     717069808   788529152 GOOD
29-MAY-13 04.48.58.980716 PM     725851247   796917760 GOOD
30-MAY-13 04.48.58.980716 PM     733947851   805306368 GOOD
31-MAY-13 04.48.58.980716 PM     741256482   813694976 GOOD
01-JUN-13 04.48.58.980716 PM     747454732   822083584 GOOD
02-JUN-13 04.48.58.980716 PM     752391653   830472192 GOOD
03-JUN-13 04.48.58.980716 PM     758085599   830472192 GOOD
04-JUN-13 04.48.58.980716 PM     759387164   833455560 PROJECTED
05-JUN-13 04.48.58.980716 PM     760688729   834947244 PROJECTED
06-JUN-13 04.48.58.980716 PM     761990294   836438928 PROJECTED
07-JUN-13 04.48.58.980716 PM     763291860   837930612 PROJECTED
08-JUN-13 04.48.58.980716 PM     764593425   839422296 PROJECTED

36 rows selected.

17:45:54 SQL> select * from table(dbms_space.OBJECT_GROWTH_TREND('XXXX','SYS_LOB0000059824C00006$$','LOB'));
TIMEPOINT                                  SPACE_USAGE              SPACE_ALLOC QUALITY
----------------------------- ------------------------ ------------------------ --------------------
04-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
05-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
06-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
07-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
08-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
09-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
10-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
11-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
12-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
13-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
14-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
15-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
16-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
17-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
18-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
19-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
20-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
21-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
22-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
23-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
24-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
25-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
26-MAY-13 05.45.54.882809 PM                         0              13614710784 INTERPOLATED
27-MAY-13 05.45.54.882809 PM                         0              13748928512 GOOD
28-MAY-13 05.45.54.882809 PM                         0              13860644208 GOOD
29-MAY-13 05.45.54.882809 PM                         0              14062412609 GOOD
30-MAY-13 05.45.54.882809 PM                         0              14285799424 GOOD
31-MAY-13 05.45.54.882809 PM                         0              14397450684 GOOD
01-JUN-13 05.45.54.882809 PM                         0              14554234880 GOOD
02-JUN-13 05.45.54.882809 PM                         0              14621343744 GOOD
03-JUN-13 05.45.54.882809 PM               14714003456              14755561472 GOOD
04-JUN-13 05.45.54.882809 PM               92449171075              92449171075 PROJECTED
05-JUN-13 05.45.54.882809 PM              170184338694             170184338694 PROJECTED
06-JUN-13 05.45.54.882809 PM              247919506313             247919506313 PROJECTED
07-JUN-13 05.45.54.882809 PM              325654673932             325654673932 PROJECTED
08-JUN-13 05.45.54.882809 PM              403389841551             403389841551 PROJECTED

36 rows selected.
--lob段的预测有问题,不知道什么原因?
--BTW:预测索引大小也可以.


目录
相关文章
|
9月前
|
SQL
Parameter ‘id‘ not found. Available parameters are [collection, list]
Parameter ‘id‘ not found. Available parameters are [collection, list]
123 0
成功解决ValueError: Number of passed names did not match number of header fields in the file
成功解决ValueError: Number of passed names did not match number of header fields in the file
成功解决DataConversionWarning: A column-vector y was passed when a 1d array was expected. Please change
成功解决DataConversionWarning: A column-vector y was passed when a 1d array was expected. Please change
|
算法
On the Correct and Complete Enumeration of the Core Search Space
在之前的文章中我们讨论了基于graph的DP-based算法,来解决join ordering的枚举问题。 这些DP算法通过join predicate描述的连通性,解决了枚举可能的表组合问题,但join graph本身(即使hypergraph)是无法完整的描述join语义的,因为连通边本身无法描述不同类型的join语义,例如left outer join/semi join/anti join...,因此即使找到了所谓的csg-cmp-pair,也不一定是有效的plan。 这篇paper讨论的就是这个问题,当枚举出一个csg-cmp-pair (S1 o S2),如何判断这是有效的join
374 0
On the Correct and Complete Enumeration of the Core Search Space
|
SQL 关系型数据库
ORA-1652: unable to extend temp segment by 128 in tablespace xxx Troubleshootin
当收到告警信息ORA-01652: unable to extend temp segment by 128 in tablespace xxxx 时,如何Troubleshooting ORA-1652这样的问题呢? 当然一般xxx是临时表空间,也有可能是用户表空间。
2048 0
|
测试技术 关系型数据库 Oracle
[20171106]DBMS_UTILITY.GET_TIME().txt
[20171106]DBMS_UTILITY.GET_TIME().txt --//有时候测试某个脚本运行时间,经常在这之前之后调用这个函数.今天奇怪的发现显示竟然是负数,感觉很奇怪做一个探究.
1013 0