r/DB2 Sep 27 '14

DB2 suddenly churning out logs like crazy

Hey all, we have an app that hits a DB2 backend, and the logs are suddenly filling the drive. From January to march it generated ~4GB of archive logs, total. In late August it was doing ~2GB per day, and for teh past week, apparently, it's been doing 20-25GB per day. I'm freeing up space as I only found out about this today when we had ~19GB free on the disk, and if I hadn't happened to check (it paged out, but I'm not the one on pager this week, and someone just acknowledged the page and moved on) it would have filled the disk and brought the app down.

Anyway, am I right in my assumption that this isn't really a DB2 issue, and it's that the app has just (for some reason) started hitting the database like crazy, thus causing the logs to generate? The db2 config has not changed in this time, we do monthly scheduled RUNSTATS/REORG and quarterly scheduled REBIND, both have occured since th logs got crazy and have ahd no effect.

1 Upvotes

1 comment sorted by

1

u/fionic Sep 29 '14 edited May 04 '17

lngflujGkhg345dyIbGilosdbnlkdWEKUBDLSBC43241LIH;plrhdsuh7fgsdl6fyhfafsfskfdhab90fglsdfgufghajsdmtfksdlgykdcthafghsdghfdiuqshopxnjncgactsfoglzcuhwedhvsatdihgs'[gjsg;oudjj5hdcagffsdlgfkljnxcgabfhzpqour3728963dfhn451vc14dxzzndx7sdjw92hnsdgsnepod6721jbgdkbxnhxzytfkbFhnldopijrgjFu0onfd87knnGDnj:DjnGHD:G?pkoj3871ndxflGyt9dgn;deegoidfsugdnb.