Page 2 of 2
Re: Just a thought...
Posted: Tue Aug 03, 2010 3:00 am
by ArndW
jdmiceli wrote:Once all of settings suggested by ArndW and JRodriguez have been implemented, wouldn't recompiling clear the logs? That is what happens when I recompile my Server stuff. Just wondering...
Recompiling doesn't clear the logs, unfortunately.
The DBA should also reorganize the schema after the log entries are gone in order to recover the disk space used.
Posted: Tue Aug 03, 2010 10:19 am
by serices
I thought there would be the answer to my problem, but unfortunately do not have a DBA for DB2 and the logic of the DB is not easy to learn. The solutions presented here serve only to improve the reading logs.
Posted: Tue Aug 03, 2010 10:57 am
by MT
serices wrote:I thought there would be the answer to my problem, but unfortunately do not have a DBA for DB2 and the logic of the DB is not easy to learn. The solutions presented here serve only to improve the reading logs.
Hi,
well this is why DBAs are still needed
Actually what you want to achive is not the simplest task in DB2.
First off runn a reorg command on all the tables where you have deleted a lot of rows. Reorganization is done on table level in DB2 LUW (Linux, Unix and Windows).
So the command (from the shell ) could b
db2 reorg table <schemaname>.<tabname>
This will physically delete the rows which you just have marked as deleted so far.
Secondly because the space is allocated by tablespaces - in your situation by an automatic storage tablespace try running following command to reduce the size of the tablespace and returning it to the file system:
db2 alter tablspace <tablespacename> reduce
Any further reduction of space is a lot more work and needs someone with DB2 skills.
kind regards
Michael
Posted: Tue Aug 03, 2010 1:20 pm
by serices
Dear, its contribution was reduced from 22 GB to the space of my BD, but only 14% of total space.
1.2G ./T0000002
141G ./T0000003
8.0K ./T0000004/C0000000.TMP
12K ./T0000004
8.0K ./T0000001/C0000000.TMP
12K ./T0000001
33M ./T0000005
97M ./T0000000
8.0K ./T0000006/C0000000.UTM
12K ./T0000006
142G .
I appreciate your help and the rest will suggest to my boss to hire the services of a DBA.
Posted: Tue Aug 03, 2010 1:23 pm
by chulett
So... do we have a resolution now?
Posted: Tue Aug 03, 2010 1:40 pm
by serices
It is a part of the solution, because even the BD XMET much space on the disc, this was what I did ...
- cd ../db2/../bin
- ./db2
- connect to xmeta user USER using PASSWORD
- select count(*) from xmeta.LOGGING_XMETAGEN_LOGGINGEVENT1466CB5F
- delete from xmeta.LOGGING_XMETAGEN_LOGGINGEVENT1466CB5F
- REORG TABLE xmeta.LOGGING_XMETAGEN_LOGGINGEVENT1466CB5F
- ALTER TABLESPACE XMETA REDUCE