1.Transaction processing template
2.initially immediate
3.v$parameter
4,oc4j user manager ,webDba role
log in as sysdba in isql*plus
5.
noarchivelog,loss control files
1.the instance aborts
2.can be restored till last whole backup
6.$ORACLE_HOME----oracle software
7.*orainstRoot.sh---creates the inventory pointer file
8.*Registrer a listener l2
1.make an entry for l2 in tnsnames.ora on the database server
2.set the local_listener parameter to l2 dynamically
3.restart l2
9.regular back up (with dbca)
em schedular back up:generate RMAN script
10.*Flashback Query :
It helps in row-level recovery from user errors;
it fails when undo data pertaining to the transaction is overwritten.
11.update a row in a table
Index:a leaf row in the index will be deleted and inserted
12.audit:4 types
13.create a replica database:
use dbca to create a template from the existing database to contain the database structure
with data files and the use the same template to create the database in the new location.
14.MTTR advisor
FAST_START_MTTR_TARGET: 0 will disable MTTR functionality
15.Roles
Roles can be granted to other roles
A role can contain both system and object privileges
16.with admin option
eg:
SQL>grant Xrole to scott with admin option
tip:the scott user can grant only the Xrole role to other users but not the privileges in it;
17.OFA(optimal flexible architecture)
18.local naming method
use the tnsnames.ora
19.ARCHIVELOG mode Take a tablespace offline with immediate option
A:if the above operation were successful,media recovery would be required to bring the tablespace online.
20.Run the SQL Acess Advisor to receive recommentations on the efficient use of indexes and materialized views to improve query performance.
21.*SGA size
22.when creating a new listener using EM information should be mandatorily provided are
①the port used by the listener
②the protocol used by the listener
③the server name where the listener runs;
23.after some action is taken to threshold Alerts.
the alert is automatically cleared and sent to the alert history.
24.BIGFILE tablespace
In order to create a BIGFILE tablespace,
①must specify local extent management.cannot be dictionary-managed.
②automatic segment space management.
③The bigfile tablespace have only one data file;
When specifying local extent management in the creation of a tablespace,you cannot specify a dictionary-managed segment storage parameter as well.FREELISTS can be specified only when extent management is dictionary。
25.the LOG_BUFFER is a static parameter.
26.protect your database from single point of failure by multiplexing the control file order:
①Configure the CONTROL_FILES parameter.
②Shut down the database instance
③Copy the control file to new location
④Restart the instance
27.REMAP_SCHEMA
28.FGA(fine-grained auditing)
・The audit trail for FGA is stored in the FGA_LOG$
・FGA enables a SQL predicate to define when to audit an event
・FGA includes the SQL statement used by the user as part of the audit event entry.
29.ASM(Automatic Storage Management)
ASM provides mirroring on file by file basis.
ASM provides automatic load balancing across all ASM disks;
阅读(813) | 评论(0) | 转发(0) |