DSXchange

very good contribution, thank you very much!

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 -...

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...

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.

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...

It is not necessary to compile but it is necessary to restart the DataStage services

Serices, The scheduled task delete a 1000 entries at a time and run every 30 minutes. It will loop until all the DataStage entries are purged ... so wait a bit and it will clear your old logs and your database size will decrease .. If you want just increase the number of entries to be deleted each ...

ArndW wrote:I didn't know that existed - thanks! But the OP still needs to redirect logging back to XMETA before executing the command. ...

In my case the space is maintained

Regards!

ArndW wrote:Just changing the two settings in the DSParams won't clear the XMETA space. I am not savvy enough with the XMETA tables to start clearing them, but perhaps you might be able to switch the logging back ...

just for that I am asking for help

Did you also set ORLogging = 0? The logs are not purged immediately after making the setting change, but only upon the next run, so it might take some time for the logs to be pruned down to size after ... Yes, is configured with ORLogging = 0, and the change was made three weeks ago and space don't...

I wouldn't try cleaning up space directly in XMETA unless I was certain what I was doing. Perhaps you could set a project purge for x-job runs or x-days; this will go a long way in keeping XMETA small ... I already configured all projects to only record the last five runs and did not reduce space, ...

I request your help in the next issue, I have the db2 XMETA database with 164 gb that after setting up projects with RTLogging = 1 is kept growing and kept the following weight ./T0000002 1.2G ./T0000003 162g ./T0000004/C0000000.TMP 8.0K ./T0000004 12K ./T0000001/C0000000.TMP 8.0K ./T0000001 12K ./T...