Pete Finnigan's Oracle Security Weblog

I saw Doug's post on his http://doug.burns.tripod.com/oracle/ - (broken link) blog titled " http://doug.burns.tripod.com/oracle/index.blog?entry_id=1141778 - (broken link) dba_registry (again) last night that follows up on his own post http://doug.burns.tripod.com/oracle/index.blog?entry_id=1132480 - (broken link) dba_registry and also my post An issue with DBA_REGISTRY. In this latest post Doug discusses the issue again in depth or rather some reasoning as to why it may have happened. This is worth reading, I don't think Doug should be too embarrassed, as I said and as he alludes to now there should be something put in place by Oracle to ensure everything gets done (besides the instructions in the patch) - how about a final check script that just verifies the versions - how about a way to easily and reliably get patch levels in the binaries and databases?