You have not answered my questions.
1) You state that the database is currently 4GB. How do you know this? What are you looking at that tells you this?
2) You imply that whatever you looked at to obtain the 4GB number is not a suitable number for knowing how large the database is and determining how rapidly it is growing, Without knowing what number you looked at (see question #1) we cannot suggest a better one. And without knowing the purpose of your inquiry we can only accidentally provide a correct answer.
None the less...
There are several widely used ways of looking at database "size". The correct method for your purpose depends on the answers to the questions above. There may also be other considerations that would depend on unknowns that you have yet to reveal.
1) Look at the disk footprint. You are running UNIX so you can use the "du -k" command. So long as the filesystems that you look at only contain relevant database files that would be sufficient. On the other hand -- if you need to separate database files from a collection of other stuff you could use "ls -l" to get the size of each and every extent and then add them up. An up to date list of extents related to any particular database can be obtained from "prostrct list dbName". The output will come to the screen and will also go to a file named dbName.st.
2) Start PROMON. Go to #5 "Activity". Look at "DB Size".
3) Run "proutil dbName -C dbanalys > dbName.out". Write a program to parse the output and calculate the storage area by storage area size. This kind of breakdown and trending will result in many independent sizes which can then be summed up to provide a total size. But if you are trying keep an eye on when extents might need to be added to storage areas something along these lines is one approach.
4) Grow to know and love the VST and Meta-schema tables. For instance:
Code:
for each dictdb._AreaStatus no-lock:
display
_AreaStatus
with
1 column
side-labels
.
end.
