Legacy platform

Tablespaces

Since there are strong preferences, the DDLs to create temporary tablespaces and data tablespaces are left to the discretion of the customer.

Prior to production, you should plan the overall storage strategy.

We instead provide the following recommendations for your consideration:

  • You should implement tablespaces with automatic space management by specifying segment space management auto.
  • With LMTs, you may want to consider creating tablespaces that store small reference tables with the autoallocate extent allocation model:
    
       create tablespace yt1
           datafile '/u03/dbs/pyantradb/yt1_001.dbf' size 2047m
           extent management local autoallocate
           segment space management auto;
       
    
  • If you have very large tables, you may want to consider putting those tables into their own tablespace and to use the uniform extent allocation model:
    
       create tablespace yfs_order_header_t1
           datafile '/u03/dbs/pyantradb/y_order_header_t1_001.dbf' size 2002m
           extent management local uniform size 1000m
           segment space management auto;
       
    
  • You should create your temporary tablespace as a temporary data file (temp files). Temp files are used to store intermediate results (e.g., from large sort operations). Changes to temp files are not recorded in the redo logs:
    
       create temporary tablespace yfs_temp
           tempfile '/u03/dbs/pyantradb/yfs_temp_01.dbf' size 1024m
           extent management local
           uniform size 1m;
    

Tables

After creating the tablespaces, you can create a set of DDL scripts using the dbverify.sh script and the -applyddl parameter set to false, as follows:


   dbverify.sh (or .cmd) -applyddl false

This creates all the necessary CREATE TABLE and CREATE INDEX statements. You may then edit these scripts to map to your tablespaces. To prevent dbverify from generating "IndexAdds" SQLs for dropped indexes, ensure that the dropped indexes are listed in the <INSTALL_DIR>/extensions/schemagenerator/indexes_not_created.txt file. Or, if the INDEXES_NOT_CREATED property in the <INSTALL_DIR>/properties/sandbox.cfg file is configured, add the list of dropped indexes to the file referenced by the property.