| Change control for PL/SQL [message #635566] |
Wed, 01 April 2015 06:51  |
John Watson
Messages: 8964
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
Hello - I'm looking for a facility that will track changes to code, some sort of source code control system. The emphasis is not so much on managing change, as detecting change. I've been Googling around, but haven't found anything that would help. The closest is the Oracle Datbase Firewall, which can scan all stored objects and report on any changes. That would do, but it is not possible for me to install the Firewall just for that.
Anyone know of any third party products to do this sort of thing?
Thank you for any insight.
|
|
|
|
|
|
| Re: Change control for PL/SQL [message #635568 is a reply to message #635567] |
Wed, 01 April 2015 07:59  |
John Watson
Messages: 8964
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
Thank you for the idea - I'll look into it, it might be a solution. This is all about security, and if someone has the ability to modify code they may also have the ability to disable triggers. But in combination with audit (and 12.x Unified Audit really is, I think, impossible to hack) it might do.
A tool would be nice, though.
|
|
|
|
| Re: Change control for PL/SQL [message #635569 is a reply to message #635566] |
Wed, 01 April 2015 08:02 |
gazzag
Messages: 1119
Registered: November 2010
Location: Bedwas, UK
|
Senior Member |
|
|
John,
In the past I have implemented a LOGIN and an OWNER schema solution to stop unauthorised/uncontrolled changes. The schema objects are all owned by the <app_name>_OWNER schema, for example, whose account is locked and whose password is expired. The <app_name>_LOGIN schema has the required privileges and synonyms pointing at the <app_name>_OWNER schema objects. Is that something like what you have in mind?
|
|
|
|
|
|
|
|
| Re: Change control for PL/SQL [message #635574 is a reply to message #635571] |
Wed, 01 April 2015 09:15 |
gazzag
Messages: 1119
Registered: November 2010
Location: Bedwas, UK
|
Senior Member |
|
|
|
I did also retro-fit it to an existing environment. The existing application schema was renamed "<app_name>_OWNER". Then, if you call the "login" schema the same name as the current application schema as well as creating appropriate synonyms, no changes to the application should be required.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
