cancel
Showing results for 
Search instead for 
Did you mean: 

Size of QAS after system copy is not equal to PRD

Former Member
0 Kudos

Hello,

We are doing system copy on Db2, 9.05 on AIX , ECC system using redirect restore method.

My Production system size is

564669480960 = DATABASESIZE

and capacity is

1287016382464=DATABASECAPACITY

I got this using

db2 " Call GET_DB_SIZE_INFO" utility and same is in DBACOCKPIT.

Now,

After redirect restore my QAS size is

815242248192=DATABASESIZE

capacity

844350050304=DATABASECAPACITY

We performed redirect restore after creating script - db2db6br etc , and restore  command.

Basically this has affected me a lot ! All my calculations with respect to a further client copy is spoilt and my client copy in QAS ( x ->y ) doubling the space is affected.

Any reason why the size increased after restore ?

Let me know please.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

Thanks but sorry, I did not investigate rather recreated.

In my opinion there was error with the script and created a large PSAPTEMP.

But was to stay the query DB_SIZE and DBACOCKPIT do show approximately size of

all the containers.

( I should not be asking the question ).

Regards,

Former Member
0 Kudos

Hello,

Thanks for the help,

I actually restored the DB once again and the space was fine.

The problem was with PSAPTEMP it got increased enormously.

Thanks again.

former_member188883
Active Contributor
0 Kudos

Hi Alex,

For my knowledge: How

The problem was with PSAPTEMP it got increased enormously. 

Any investigation done by you why this happened during 1st restore and not during 2nd restore?

Regards,

Deepak Kori

Former Member
0 Kudos

Hi,

Thanks,

But the query and size in  DBACOCKIPT give the same result.

I mean if my DBACOCKIPT db size for PRD is X GB I assume my QAS size after restore will

also be X GB.

But after restore X+Y has come .

I need to explain this to customer.

former_member188883
Active Contributor
0 Kudos

Hi Alex,

Please share following information

1) SAP_Basis release and patch level

2) Whether latest dbacockpit corrections have been applied

3) full redirect command used to perform the database restoration

4) Whether DB compress is active on Production system ?

5) SAP kernel level on PRD and QAS ?

Regards,

Deepak Kori

former_member188883
Active Contributor
0 Kudos

Hi Alex,

The results from get_dbsize_info include only used pages  in the tablespaces. This means that it essentially covers table data and index data and not much else. It also means that if you have DMS tablespaces with a large amount of free space, you may have more space actually taken up on disk than the value of DATABASESIZE as reported by get_dbsize_info.

Request you to compare the values at tablespace level using command

db2pd -d <DBSID> -tablespaces

Hope this helps.

Regards,

Deepak Kori