From: Brandon Kohn [mailto:[EMAIL PROTECTED]] > param_init Content Server > param_put LOG_MODE DUAL > param_put CAT_CACHE_SUPPLY 1000 > param_put DATA_CACHE 4000 > param_put MAXDATADEVSPACES 20 > param_put MAXDATAPAGES 20480000 > param_put MAXUSERTASKS 20 > param_put DEADLOCK_DETECTION 1 > param_put REQUEST_TIMEOUT 30 > param_put SESSION_TIMEOUT 60 > param_checkall > param_commitsession > param_adddevspace 1 SYS DISKS001 F > param_adddevspace 1 LOG DISKLA01 10240 > param_adddevspace 1 LOG DISKLB01 10240 > param_adddevspace 1 DATA DISKDAT_001 F 10000 > param_adddevspace 1 DATA DISKDAT_002 F 10000 > param_adddevspace 1 DATA DISKDAT_003 F 10000
> What options exist for the case when the currently used database has grown to > its maximum size and more space is needed? Is there some in house solution that > allows one to create a new database with the needed capacity and then import the > content of the old database? I'm designing a database for my company now, but we > really don't know how large our data may grow, and we don't want to hit a limit a > year from now and then find out that we are stuck. The parameters MAXDATADEVSPACES and MAXDATAPAGES are the sum of the current data devspaces _and_ a "reserve" for adding new devspaces _without restarting_ the database (DBMServer command db_adddevice). This is a little bit a "high availability" feature. But this "reserve" allocates some resources in the database kernel process and on the system devspace. In your configuration above over 99% is unused (30000 pages are used by the datadevspaces and 2045000 pages "reserve"). It is not necessary to specify MAXDATADEVSPACES and MAXDATAPAGES. The DBMServer guarantees a "reserve" of one devspace with the size of the largest devspace. This "reserve" will be computed on every restart of your database. If you have consumed your "reserve" by a db_adddevice you have to restart the database to get a new "reserve". If you need more "reserve" as the DBMServer guarantees please change MAXDATADEVSPACES and/or MAXDATAPAGES to your values before the restart. Over the lifetime of a database instance you can extend your data devspace configuration up to 256 devspaces with 128 GB per devspace. (So you can not reach 20480000 pages with devspace a 10000 pages). Summary: If your are able to restart your database sometimes you do not need to know how large your database becomes over the years. Bernd -- SAP Labs Berlin
