On Thu, Jan 10, 2013 at 1:58 PM, Harvey Rothenberg <forensic2...@yahoo.com>wrote:
> To All: > > I have a member of another professional ListServ needing help with: > > > 1. Pulling the content of an existing Oracle DB so that another > project could be loaded and worked upon. > 2. He also needs assistance in coming up with an SQL query for a > targeted group of information or created internal "bookmarks". > > > The use of this Oracle DB application is for finding forensic evidence > from a source of a RAW image of a hard drive. So there is content * > retention* issues at play also. > > This other professional seems to be mostly concerned with how to empty an > Oracle DB of its' content properly, relationally, and completely to a > secure location and/or device so that it can later be re-loaded and then > again worked upon with everything intact. > > Does anyone have any solid suggestions or recommendations ? I look > forward to your assistance in this matter and my thanks for your time, now. > > Regards, > Harvey Rothenberg > Systems Integrator/Security Specialist NOT a DBA > > I'm not an Oracle or forensics expert, but I do support systems that run Oracle. I think that the approach of "cleaning out" a database is somewhat off track. It doesn't make much sense to "empty" the files, only to reload them later, when you're just talking about moving the same data around on disk. I think it would be better to create a separate Oracle instance for each job that needs to be performed, and when the job is done, shut down the instance and archive the database files directly. If you really want to, you could dump the data using data pump to make the archived files a little less Oracle version dependent. ❧ Brian Mathis
_______________________________________________ Discuss mailing list Discuss@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
