DBA Wiz

The secedit command is a command-line tool that is used to configure and analyze security of a database. The syntaxes of using the secedit command are as follows:
secedit /configure/db/cfg/overwrite/areas/log/quiet This syntax is used to configure the security.
secedit /analyze /db/cfg/overwrite/log/quiet This syntax is used to analyze the security.
The parameters used with the above command are as follows:
/db: It provides the path to the database that contains security template.
/cfg: It specifies the path to the security template that contains default security settings.
/overwrite: It is used to empty the database during the process of importing the security template.
/areas: It specifies the areas where the security is to be applied. If this argument is not specified, all security settings in the security database are applied to the system.
/log: It specifies a file that is used to log the status of the configuration process.
/quiet: It specifies that the configuration or the analysis process should take place without prompting a user.

The MERGE command can be used to conditionally update or insert data depending on its presence. This helps to reduce table scans and perform the operation in parallel. A user can wrap up the whole transformation process into this one Oracle MERGE command, referencing the external table function and the table in one command as the source for the MERGED Oracle data.

A linked report is an item of the Report Server that supplies an access point to an existing report. Typically, it is analogous to a shortcut that can be used to open a file. A linked report is the derivative of an existing report. It always inherits layout and data source properties from the original report. All other properties may not be the same as that original report including security, parameters, subscriptions, and schedules.

The Report Wizard is a tool within Report Designer that helps a user through the process of creating a report. The report wizard can be used to select a report data and create a matrix or tabular report. Following are the five steps that should be taken to create a report through a Report Wizard:
Select a Data Source.
Design a Query.
Choose a Report Type.
Choose a Style.
Name the Report.

An ad hoc report is a report that can be created using an existing report model with the help of Report Builder. These reports refer chiefly to reports of Report Builder and not to reports that can be created with the use of the Report Wizard. Ad hoc reports control report models and pre-defined templates to enable information workers to quickly and easily explore business data using familiar terminology and data structures implemented in the report model. These reports can be saved and run locally or published to a report server, just like other reports in the Reporting Services.

The following privileges of Database Administrator are revoked by Oracle Database Vault:
BECOME USER
SELECT ANY TRANSACTION
CREATE ANY JOB
CREATE EXTERNAL JOB
EXECUTE ANY PROGRAM
EXECUTE ANY CLASS
MANAGE SCHEDULER
DEQUEUE ANY QUEUE
ENQUEUE ANY QUEUE
MANAGE ANY QUEUE

Oracle Database Vault addresses database security concerns in the following manner:
Administrative privileged account access to application data: Oracle Database Vault prevents the DBA from accessing those schemas that are protected by FIN Realm. Although the DBA is the most powerful and trusted user, the DBA does not need access to application data existing in the database.
Separation of duties for application data access: The FIN Realm Owner that is created in Oracle Database Vault has the permission to access the FIN Realm schemas.

When an Oracle Virtual Private Database (VPD) policy protected table, view, or synonym is accessed by a user either directly or indirectly, the SQL statement issued by a user is changed dynamically by the Oracle Database. The function that enforces the VPD security policy returns a dynamic WHERE clause, particularly known as predicate, that gets attached to the SQL statement. The Oracle VPD policies can be enforced on SELECT, INSERT, UPDATE, DELETE, and INDEX statements. Example: The query fired by a user is as follows: SELECT * FROM DB1.EMPLOYEES; A dynamic WHERE clause added to the statement by the Oracle VPD policy is as follows: SELECT * FROM DB1.EMPLOYEES; WHERE DEP_ID = 101; Now, the user will be able to see the details of only those employees who work in the department having department ID 101. It is also possible to take into account the session information and then display the data according to the user. Example: SELECT * FROM DB1.EMPLOYEES; WHERE DEP_ID = 101; SYS_CONTEXT(‘USERENV’,'SESSION_USER’);

The synax of the SELECT INTO statement is as follows: select_into_statement ::= SELECT [{DISTINCT | ALL}] {* | select_item [, select_item]…} INTO {variable_name [, variable_name]…| record_name} FROM {table_reference | [THE] (subquery)} [alias] [, {table_reference | [THE] (subquery)} [alias]]… rest_of_statement [rest_of_statement]…;