cancel
Showing results for 
Search instead for 
Did you mean: 

Difference between library size and actual size of SQL Package

Former Member
0 Kudos

Hi All,

I noticed that my ASP size is growing but the database size remain constant. I suspect it is the SQL Packages that are contributing to the growth in ASP size and discovered that there is a difference between the library size and actual size of SQL Packages. E.g, R3<SID>X0000.

[http://flic.kr/p/8UtGWM] (Screen shot showing SQL package library size)

[http://flic.kr/p/8UtGXv] (Screen shot showing SQL package size capture from DBACOCKPIT)

Why is there a difference between the two sizes? Is it possible to reduce the library size of the SQL Packages so as to free up the ASP space?

What other factors could contribute to ASP growth if the database size remain constant?

Thanks in advance.

Regards,

Lim

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hi Lim,

the size information in the DSPLIB output reflects only the size of the library object, not the size of all objects within that library. The size is given in Bytes, so your libarary object R3ERQX0000 has a size of 28.8 MB. The information in DBACOCKPIT includes all objects (SQL Packages) in that library, and that is much larger. When checking, I noticed that the header in that screen is wrong, the size is actually given in kilo bytes, not in bytes, so the total size of all SQL packages in library R3ERQX0000 is 8.7 GB.

I don't know if 8.7 GB is significant in relation to the total ASP size - if so, you can delete SQL packages occasionally as described in SAP Note 63037. The SQL packages will be recreated as needed, but you might get rid of some old stuff.

Usually the fastest growing objects are journal receivers: Is your library R3ERQJRN in the same ASP as R3ERQDATA? If so, do you have a concept in place to save and delete detached journal receivers (see SAP Note 82079)?

If that does not help to identify the cause of your ASP filling, you can try using the tools RTVDSKINF and PRTDSKINF to identify the biggest objects or libraries on your system. You could also check if temporary storage is responsible: Use WRKSYSSTS and check the field "Current unprotect used".

Kind regards,

Christian Bartels.

Former Member
0 Kudos

Hi Christian,

Thanks for the detail guidance.

WRKSYSSTS shows my 'Current unprotect used' as 28980 M. Is this normal for a SAP system?

Regards,

Lim

0 Kudos

Hi Lim,

28 GB of temporary storage is not unusual for an SAP installation. SAP Note 142023 has some information how to estimate if the temporary storage used by the system is reasonable or too high. However, it only covers ABAP systems, if you have a Java instance, the Java Virtual Machine and the Java heap must be considered as well.

Kind regards,

Christian Bartels.