cancel
Showing results for 
Search instead for 
Did you mean: 

Wrong size estimate in DBSIZE.XML

Former Member
0 Kudos

Hi,

We are doing unicode export of 300gb database.

After export the dbsize.xml file showing most of the data in sapdata2.

When we are palning to import space problem is coming for that reason.

Below are the mount points and the export and import will happen in the same machine.

/dev/md/dsk/d116 39G 37G 1.8G 96% /oracle/PRD/sapdata7

/dev/md/dsk/d118 39G 37G 1.8G 96% /oracle/PRD/sapdata9

/dev/md/dsk/d110 39G 37G 1.6G 96% /oracle/PRD/sapdata1

/dev/md/dsk/d114 39G 37G 1.8G 96% /oracle/PRD/sapdata5

/dev/md/dsk/d117 39G 37G 2.1G 95% /oracle/PRD/sapdata8

/dev/md/dsk/d119 39G 36G 2.8G 93% /oracle/PRD/sapdata10

/dev/md/dsk/d111 39G 37G 1.8G 96% /oracle/PRD/sapdata2

/dev/md/dsk/d113 39G 37G 1.8G 96% /oracle/PRD/sapdata4

/dev/md/dsk/d125 98G 78G 20G 80% /oracle/PRD/sapdata11

/dev/md/dsk/d115 39G 37G 1.8G 96% /oracle/PRD/sapdata6

/dev/md/dsk/d112 39G 37G 1.8G 96% /oracle/PRD/sapdata3

New kernel and R3 tools are used.

Oracle database and solaris o/s.

sap ecc6 ehp4

Regards

Ashok Dalai

Accepted Solutions (1)

Accepted Solutions (1)

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Ashok,

please have a look at the Unicode conversion guide - section "Database Import":

There you will find:

"Tablespace sizes do not get calculated correctly. Therefore, you have to adapt the tablespace sizes before the import by editing the file DBSIZE.XML."

After this statement, database specific proposals for adaption follow.

In general it is not possible to calculate the system specific database growth precisely, as it highly depends on reorganization level of your database.

Best regards,

Nils Buerckel

SAP AG

Former Member
0 Kudos

Hi Nils,

Thank you very much for your response.

As you can see the mount points above and sum all 11 mount points it will come to 500gb.

I exported 300 gb database and after import the database size is 370 gb.We edited the dbsize.xml file and added extra space and completed the import in our development system.

Now we are planing in our production box.

My queastion is when we are doing the import ,it asked for 220gb of free space in sapdata2 even though we have other mount points free.any thing we can do to skip this manual work.

Regards

Ashok Dalai

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Ashok,

unfortunately I do not know why this happens.

However the dbsize.xml needs to be adapted BEFORE you start sapinst - otherwise the settings are not taken into account.

Best regards,

Nils Buerckel

SAP AG

markus_doehr2
Active Contributor
0 Kudos

Make sure you use the latest patch of "R3szchk" for your database. If the estimation is still wrong I'd create an OSS call.

I have done lots of (heterogeneous) migrations to various databases in the past and the sizes never fit, one always has to adapt them (or run the migrations and subsequently add space if necessary during the import).

Markus

Answers (0)