Hi folks,
My database DB03 is circular logging. I called the db2 procedure:
get_dbsize_info to get the database size as below:
Parameter Name : SNAPSHOTTIMESTAMP
Parameter Value : 2008-04-08-06.39.49.518070
Parameter Name : DATABASESIZE
Parameter Value : 24666112
Parameter Name : DATABASECAPACITY
Parameter Value : 6063167488
then, I did the db backup. The backup image size as below:
-rw-r----- 1 db2inst1 db2grp1 54308864 April 7 23:26
DB03.0.db2inst1.NODE0000.CATN0000.20080407232545.001
The database size info is not the same or close to the backup image
size!! Can somebody tell me what's going on?
Should we not use db2 procedure get_dbsize_info to gather database
size info? If so, what else it should be used for gathering database
size info?
Laurence
juraj.hrapko@gmail.com - 08 Apr 2008 15:08 GMT
Backup file contains some more info about the DB, than only the data.
I think, this could be the reason for having bigger backup than the db
size. Anyway, you can use the compress switch with the backup
command :)
> Hi folks,
>
[quoted text clipped - 23 lines]
>
> Laurence
Laurence - 09 Apr 2008 03:43 GMT
Well, the value that is returned by the db2 procedure
'get_dbsize_info' is the same as the size of total tablespaces within
database DB03.
As I do the 'du -sb $HOME/db2inst1/NODE0000/SQL00003', the summary
size of DB03 Path is 41152360. That is more close to the backup image
size.
For your information.
Laurence