ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

View - Creating a Static Database from a Current Database


Article ID: 237513


Updated On:




We have run a SARDBASE UNLOAD on an existing database, to use as the source for a static database on another system.

There are a few questions to address:

1) How do you estimate the required Database index and data space required on the existing database?

2) For those reports that are on DASD during the UNLOAD, once they are LOADed to a new database, will there be any impact on the static database?

3) Will there be any impact on the existing database during the LOAD process?


Release : 14.0

Component :


As the client was creating what would be a static database (no additional report collection or backup processing), the space needs for the database can be obtained from the runnng of a SARDBASE STATUS FULL:

//XXXXXXXX JOB ...                                                
//SYSPRINT DD  SYSOUT=*                                           
//SYSIN    DD *                                                   
STATUS FULL                                                       

If you multiply the number of Total Cylinders by the Percentage Usage, you will come up with (for INDEX and DATA), the number of cylinders needed for the target database. 

The target database would be created using SARDBASE ADDDS INDEX and ADDDS DATA to allocate the index and data portions, respectively.

It is suggested to stop the activity on the source database, using "/P sarstc".

Once the dataset from the SARDBASE UNLOAD of the source database is available, a SARDBASE LOAD can be used to populate the target database.

As a SARDBASE UNLOAD is a snapshot of a database, and asthe target database would be static, there will be no impact on the source database with doing a SARDBASE LOAD.