ilevent
asked on
Disable DB2 Logging
Hi,
We have an ERP system, which has a logging utility for audit purposes.
Every INSERT, UPDATE and DELETE is logged into its log table with for example username and date information.
This process adds some overhead to running system.
Also DB2 logs our log process too.
How can I disable DB2 log for our ERP system log?
I hope to increase performance in this way since
log table is getting bigger every day.
We have an ERP system, which has a logging utility for audit purposes.
Every INSERT, UPDATE and DELETE is logged into its log table with for example username and date information.
This process adds some overhead to running system.
Also DB2 logs our log process too.
How can I disable DB2 log for our ERP system log?
I hope to increase performance in this way since
log table is getting bigger every day.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
lol kdo
of course, if you would like to be brave, drop the triggers that create the transaction logging, or stop db2's audit facility, however I would check with management first before doing this, unless 20 years in prison appeals to you.
If you do get the go ahead, make sure you have some written document signed by somebody who is AUTHORIZED TO SIGN THE DOCUMENT. normally this would be the firm that handles the companys audit or senior management level, ie CFO or CIO or CEO.
If your problem is performance related, could you state what level of performance you see has been degraded?
If you do get the go ahead, make sure you have some written document signed by somebody who is AUTHORIZED TO SIGN THE DOCUMENT. normally this would be the firm that handles the companys audit or senior management level, ie CFO or CIO or CEO.
If your problem is performance related, could you state what level of performance you see has been degraded?
ASKER
This is what I want;
ALTER TABLE <SCHEMA_NAME>.<TABLE_NAME>
thanks for any comment.
ALTER TABLE <SCHEMA_NAME>.<TABLE_NAME>
thanks for any comment.
Hi ilevent,
Use caution here. The "NOT LOGGED INITIALLY" phrase applies only to the next update/transaction. It's not intended for "general" use.
kent
Use caution here. The "NOT LOGGED INITIALLY" phrase applies only to the next update/transaction. It's not intended for "general" use.
kent
ALTER TABLE <SCHEMA_NAME>.<TABLE_NAME>
if you rollback the transaction implicitly or because of some error, the table can only be dropped, so I would be careful in using this. Make sure that you always have a very recent backup of the database in case something should go wrong.
if you rollback the transaction implicitly or because of some error, the table can only be dropped, so I would be careful in using this. Make sure that you always have a very recent backup of the database in case something should go wrong.
Let me second lowfatspread's comment and throw in another thought.
ERP's are big, massive, inefficient "be everything to everyone" kinds of applications. There are entirely too many moving parts for any one person to know everything that's going on within one of them. Don't take dangerous steps with an ERP thinking that if the worst happens, you're only going to effect a small portion of the system.
If you've got a performance problem with one (and every ERP experiences them at some point), get a GOOD DB2/UDB systems programmer to tune up the database or buy some more hardware. And get used to the idea of "buy more hardware". I'm convinced that ERP's were invented to help meet sale's quotas in this day of declining mainframes.
Kent