The SQL scripts that configure Oracle ATG Web Commerce databases on Oracle do not set storage parameters to control how free database space is allocated. You should spread your tablespaces across several disk drives and disk controllers. The size of the tablespaces needed to store Commerce tables depends on your specific requirements in terms of the catalog items you have, the expected number of user profiles and Web site visitors, and the expected transaction volume.
To allocate space, you need to specify the initial extent and the incremental extent for the tables that are likely to expand significantly. The initial extent parameter limits the amount of space that is reserved initially for a table’s data segment. The incremental extent limits the additional space that is reserved when the segment’s initial data blocks become full, and more space is required.
To begin, you can set the extent sizes for the tablespaces to be 512K with pctincrease equal to 50. If you are loading the Motorprise reference application on an Oracle database, you should configure the storage parameters for the following Commerce tables:
Table Name | Initial Extent | Incremental Extent |
|---|---|---|
| 1M | 1M |
| 1M | 1M |
| 1M | 1M |
| 4M | 2M |
| 4M | 2M |
Note: These storage parameters are guidelines only. As previously mentioned, the optimal settings for your database may vary depending on the expected number of user profiles, Web site visitors, and catalog items, as well as the expected transaction volume.
To specify a storage parameter, include it in the STORAGE clause of the CREATE TABLE statement for these tables. For additional information about configuring storage parameters, see your Oracle documentation.
