We are at moment testing Automic 12 and we would like to start using ILM. I have problems to understand the link/difference between partitions and containers. Could you please help?The answer to your questions may be found here in the documentation : https://docs.automic.com/documentation/webhelp/english/AWA/12.0/DOCU/12.0/AWA%20Guides/Content/AWA/Admin/admin_ILM_partitioning.htm
About the variables UC_ILM_CONTAINERS_*: Should each container be defined on a single oracle datafile?
Can different containers share the same datafile?
In the documentation I find these 3 container example for the UC_ILM_CONTAINER_STATISTICS:
Key Value
1 UC4_DATA_STATISTICS_1
2 UC4_DATA_STATISTICS_2
3 UC4_DATA_STATISTICS_3
Is this definition correct?
Key Value
1 UC4_DATA_STATISTICS
2 UC4_DATA_STATISTICS
3 UC4_DATA_STATISTICS
Then the 3 container in the same datafile.
Here is an excerpt that seems relevant to answer this question :
"
Partitions, Partition Sets, Containers, and Tablespaces / Filegroups
As described in the terminology section above, partition sets are divisions of logical parts in a database whereas tablespaces / filegroups denote the physical storage areas of the data. Partition sets are a set of all partitioned tables which belong together.
ILM uses so-called containers to map partitions to tablespaces / filegroups (i.e., to define where partition sets have to be stored).
Example: Three containers are defined and describe the following mapping:
| Container | Mapping of Partition Sets | Mapping To Tablespace / Filegroup |
|---|---|---|
| 1 | 1, 4, 7, ... | Tablespace 1 |
| 2 | 2, 5, 8, ... | Tablespace 2 |
| 3 | 3, 6, 9, ... | Tablespace 3 |
In other words :
- partition = logical space
- data file (MS SQL) / tablespace (Oracle) = physical space
- container = maps partitions to tablespaces
Kind regards,
Antoine