Re: HELP! ORACLE ADVICE NEEDED ASAP!!

Oh boy,

    Let me be among the first, since I am sure you will get many comments. (mine are inline)

heebe_at_my-deja.com wrote in message <7lftab$em7$1_at_nnrp1.deja.com>...
>Please help,
>
>I am conducting an Oracle security Review and have come to an impasse
>regarding the following steps:
>
>1. Review the script output for the USER PRIVILEGE DUMP to determine
>whether any users have been granted default tablespace of SYSTEM.

    If the SYSTEM TABLESPACE becomes filled Oracle stops running. The     default DEFAULT TABLESPACE is SYSTEM. So, users for whom another     DEFAULT TABLESPACE has not been specified will be busy filling up the     SYSTEM TABLESPACE and Oracle may stop running. This can be avoided     by specifying a different DEFAULT TABLESPACE for the users. You could     even go so far as to have a unique default for each user or group of users.
>
>2. Review the script output for the LOG FILE DUMP to determine whether
>the archivelog is activated for critical database files; Review the
>script output for the PARAMETERS DUMP to determine where archive logs
>are maintained; Determine whether archive logs are protected from
>logical access; Determine whether a copy of the archive logs are
>maintained off-site; Determine whether physical security over archive
>logs is maintained.

    A correction, you are either running with archivelogs for the entire database

    instance or you aren't. You don't get to pick and choose. The archive logs

    are needed to recover the database when the system or the disk crashes.     Although Oracle itself rarely, if ever, crashes sooner or later you will have

    a hardware failure or a system crash and you will NEED your archive logs.

    In order to fully recover to the current point in time you will need a copy of

    the database backup, control files, init and configuration files, the archives,

    and the redo logs. If you lose the redo logs you will only be able to recover

    to the time of the last log switch.
>
>3. Ensure that multiple Redo Logs are maintained on Different Servers.

    No, you really don't want to do that. The Redo logs are Oracle's hot spot.

    They are constantly being written. Performance will suffer if they are on a

    different server. It is much better to mirror them on the same system.

>
>What is the risk with regard to these items? Why do I need to worry
>about the above steps. Any advice is appreciated!!!
>
>heebe_at_hotmail.com
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.

regards

Jerry Gitomer Received on Thu Jul 01 1999 - 12:38:28 CDT