|
View previous topic :: View next topic
|
| Author |
Message |
Sourabh_1221
New User
Joined: 24 Jan 2010
Posts: 2
Location: India
|
|
|
|
Hi,
In our DB2 database we have few provision tables.A couple of times we had issues when some person manually edited test tables rows that caused system instability.
My Question is there any way to put a check anywhere in adb2 by which can identify who manually edited and saved table.
or if there is any way by which we can generate reports that can reflect who has updated which row manually in which table.
Thanks!! |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Suggest that "some person" should not be able to "manually edit" production tables. . .
This would fail any audit or quality review. Indeed, it probably means that any/all of the data is possibly tampered with.
For these tables, there should be a maintanace process that will do the updates as well as generate an audit trail of what was done and by whom. |
|
| Back to top |
|
|
Sourabh_1221
New User
Joined: 24 Jan 2010
Posts: 2
Location: India
|
|
|
|
Thanks dick for reply.
Usually Editing happens in test DB2 provision tables as lot of persons simultaneously works in test DB2 tables.
I will be thankful if you can send me any reference link using which I can have an idea of implementing maintanace process that can help us in generating Audit reports of what was done and by whom.
Thanks!! |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| My Question is there any way to put a check anywhere in adb2 by which can identify who manually edited and saved table. |
on the test environment is not usual to do some quick and dirty manual data fixing.
anybody with the proper authorizations can use qmf,spufi,dsntep to do manual table update
har to control or limit ! usually in the test environment the rules are a bit relaxed! |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
I'm not aware of a link. . .
The environments i've supported have implemented an audit table (or series of tables) and when maintenance is performed, it is also posted in the audit. It i not difficult, but it is done in all of the maintenance programs. Typically, these are the online transactions that are recordrd. Large updaes done in batch might not be recorded the same way. It depends on the needs of the organization.
In these environments, maintenance is only done thru the installed maintenance code - not ad hoc queries.
If developers are permited to modify test data on the fly as they need, other developers may be impacted if this is not coordinated.
Several database systems have an easy was to process the log of transactions executed to aid looking for this type of info. I'm not aware of an easy way to do this with db2. . . Maybe someone else is. . . |
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
| The only method I've seen of limiting this kind of problem is to assign ranges of key values to various groups of developers and hope that each group remains "inside" their assigned ranges. |
|
| Back to top |
|
|
|
|
