a.) You are implementing security in your database and observed that the following privileges were granted to public. UTL_SMTP, UTL_TCP, UTL_HTTP and UTL_FILE. Strip public of the above privileges.
b.) You want to set up traditional auditing in your database and you were told that the audit record should be stored in the database. Display the steps to turn auditing on.
c.) If your audit information goes into the database where would you find it?
d.) Issue a query to audit anyone that drops employees table that belong to HR.
e.) Using standard auditing, Issue a query to audit any one that drops a sequence and view, that belongs to another schema.
f.) Issue a command to audit anyone that drops a role.
g.) Issue a command to audit anyone that creates a table, user, view, tablespace, sequence and profile.
h.) Using the standard auditing, issue a command to audit anyone that does and update or delete from the employees table that belong to hr.
i.) Issue a query to audit all activity on emp table that belongs to scott.
j.) Issue a query to stop auditing the following any one that creates a view and tablespace.
k.) List 10 privileges that are audit by default in Oracle 11g. Google this!
l.) Issue a query to audit every activity done by SCOTT and HR users in the database.
m.) Issue a query to allow your audit record to be stored on the OS instead of the database.
n.) If your audit information goes to the OS what determines where it goes on your OS. Show me the parameter.
o.) It is ok to share accounts in Oracle true/false.
p.) Display the command to turn on auditing for the sys user
q.) The DBA and the system administrator must be the same people true/false
r.) What is main difference between fine grain audit and the standard audit?
s.) What procedure do you use to set up fine grain auditing?
t.) Where do the audit records for fine grain auditing go?
u.) Set up fine grain audit called all_sal that will capture the query by anyone that does a select, insert, update and delete on the salary column of the emp table that belongs to Scott.
v.) Set up fine grain audit called high_sal to capture anyone that queries any salary over 5000 in the employee table owned by HR.
w.) Issue a select * from scott.emp by a non sys users. Then query the database to show me how the statement is captured in your audit record. Make sure you include in your query the database user who issued the query, the machine that was used the time the query was issued and the sql statement that was used.
x.) Disable the fine grain audit for the audit that queries any salary over 5000 in the employee table owned by HR
y.) Drop the 2 fine grain audit policy you created.
a.) Configure your undo tablespace to retain 4 days of data.
b.) Issue a command to make let your undo tablespace guarantee every database in it for at least the set retention.
c.) You don’t want the undo data in your undo tablespace to be guaranteed anymore. Issue a command to change it.
d.) Issue a command to show whether your undo tablespace is in guarantee or in no guarantee
e.) Increase your current undo tablespace size to 5g.
f.) Issue a command to display which undo tablespace your database is using?
g.) What is ORA-01555 snapshot too old error?
h.) A user got this error ORA-01650: unable to extend rollback segment—- what is the problem and how do you fix it.
i.) Create a new undo tablespace with 3g size called undotbs3. Make sure undotbs3 automatically extends when full set the initial to 10m and the maxsize to unlimited.
j.) Make undotbs3 you just created the new database default undo tablespace
k.) Add one more datafile to your undo tablespaces undotbs3 with 2g size. Let the datafile automatically increase when full set the initial to 10m and the maxsize to unlimited
l.) Drop your old undo tablespace undotbs1
m.) Mention 2 differences between undo data and redo data.
WE ARE THE LEADING ACADEMIC ASSIGNMENTS WRITING COMPANY, BUY THIS ASSIGNMENT OR ANY OTHER ASSIGNMENT FROM US AND WE WILL GUARANTEE AN A+ GRADE