1.查询系统使用的是哪一组日志文件：数据库
select * from v$log;服务器
2.查询正在使用的组所对应的日志文件：session
select * from v$logfile;oracle
3.强制日志切换：工具
alter system switch logfile;性能
4.查询历史日志：ui
select * from v$log_history;spa
5.查询日志的归档模式：日志
select dbid,name,created,log_mode from v$database;
6.查询归档日志的信息：
select recid,stamp,thread#,sequence#,name from v$archived_log;
7.增长与删除日志文件组
alter database add logfile group 1 ('/home1/oracle/oradata/ora8i/log1a.log'),'/home2/oracle/oradata/ora8i/log1b.log') size 100M;
alter database drop logfile group 1;
8.增长与删除日志成员
alter database add logfile member '/home1/oracle/oradata/ora8i/log1a.log' to group 1,'/home1/oracle/oradata/ora8i/log2a.log' to group 2;
alter database drop logfile member '/home1/oracle/oradata/ora8i/log1a.log' ;
9.日志文件移动
alter database rename file '/home1/oracle/oradata/ora8i/log1a.log' to '/home2/oracle/oradata/ora8i/log1a.log';
执行该命令以前必须保证该日志文件物理上已经移动到新目录
10.清除日志文件
alter database clear logfile '/home1/oracle/oradata/ora8i/log1a.log';
该命令用于不能用删除组及组成员命令删除日志时使用
======================================================
Oracle日志查看一．Oracle日志的路径：登陆：sqlplus "/as sysdba"查看路径：SQL> select * from v$logfile;SQL> select * from v$logfile;(#日志文件路径)二．Oracle日志文件包含哪些内容：（日志的数量可能略有不一样）control01.ctl example01.dbf redo02.log sysaux01.dbf undotbs01.dbfcontrol02.ctl redo03.log system01.dbf users01.dbfcontrol03.ctl redo01.log SHTTEST.dbf temp01.dbf三．Oracle日志的查看方法：SQL>select * from v$sql (#查看最近所做的操做)SQL>select * fromv $sqlarea（#查看最近所做的操做）Oracle 数据库的全部更改都记录在日志中，从目前来看，分析Oracle日志的惟一方法就是使用Oracle公司提供的LogMiner来进行，由于原始的日志信 息咱们根本没法看懂，Oracle8i后续版本中自带了LogMiner,而LogMiner就是让咱们看懂日志信息的工具,经过这个工具能够：查明数据 库的逻辑更改，侦察并更正用户的误操做，执行过后审计，执行变化分析。 四．LogMiner的使用：一、建立数据字典文件（data-dictionary）1).首先在init.ora初始化参数文件中，添加一个参数UTL_FILE_DIR，该参数值为服务器中放置数据字典文件的目录。如：UTL_FILE_DIR = ($ORACLE_HOME\logs) ,从新启动数据库，使新加的参数生效：SQL> shutdown;SQL>startup;2).而后建立数据字典文件 SQL> connect /as sysdba SQL> execute dbms_logmnr_d.build(dictionary_filename => 'dict.ora',dictionary_location => '/data1/oracle/logs');PL/SQL procedure successfully completed二、建立要分析的日志文件列表 1).建立分析列表，即所要分析的日志 SQL>execute dbms logmnr.add logfile(LogFileName => '/data1/oracle/oradata/akazamdb/redo01.log',Options => dbms_logmnr.new); PL/SQL procedure successfully completeds 2).添加分析日志文件，一次添加1个为宜 SQL>execute dbms_ logmnr.add_ logfile(LogFileName => '/data1/oracle/oradata/akazamdb/redo01.log',Options => dbms_logmnr.ADDFILE); PL/SQL procedure successfully completed三、使用LogMiner进行日志分析(具体要查询什么内容能够本身修改)（1）无限制条件SQL> EXECUTE dbms_logmnr.start_logmnr(DictFileName=>'/data1/oracle/logs/v816dict.ora '); （2）有限制条件 经过对过程DBMS_ LOGMNR.START_LOGMNR中几个不一样参数的设置，能够缩小要分析日志文件的范围。经过设置起始时间和终止时间参数咱们能够限制只分析某一时间范围的日志。以下面的例子，咱们仅仅分析2007年9月18日的日志：SQL> EXECUTE dbms_logmnr.start_logmnr(DictFileName => ' /data1/oracle/logs/ v816dict.ora ', StartTime => to_date('2007-9-18 00:00:00','YYYY-MM-DD HH24:MI:SS')EndTime => to_date(''2007-9-18 23:59:59','YYYY-MM-DD HH24:MI:SS ')); 也能够经过设置起始SCN和截至SCN来限制要分析日志的范围：SQL> EXECUTE dbms_logmnr.start_logmnr(DictFileName => ' /data1/oracle/logs/ v816dict.ora ',StartScn => 20,EndScn => 50); 四、观察分析结果（v$logmnr_contents）到如今为止，咱们已经分析获得了重做日志文件中的内容。动态性能视图v$logmnr_contents包含LogMiner分析获得的全部的信息。SELECT sql_redo FROM v$logmnr_contents; 若是咱们仅仅想知道某个用户对于某张表的操做，能够经过下面的SQL查询获得，该查询能够获得用户DB_ZGXT对表SB_DJJL所做的一切工做。SQL> SELECT sql_redo FROM v$logmnr_contents WHERE username='DB_ZGXT' AND tablename='SB_DJJL'; 需 要强调一点的是，视图v$logmnr_contents中的分析结果仅在咱们运行过程'dbms_logmrn.start_logmnr'这个会话的 生命期中存在。这是由于全部的LogMiner存储都在PGA内存中，全部其余的进程是看不到它的，同时随着进程的结束，分析结果也随之消失。最后，使用过程DBMS_LOGMNR.END_LOGMNR终止日志分析事务，此时PGA内存区域被清除，分析结果也随之再也不存在。五、查看LogMiner工具分析结果 SQL> select * from dict t where t.table_name like '%LOGMNR%';-看全部与logmnr相关的视图 TABLE_NAME COMMENTS ------------------------------ -------------------------------------------------------------------------------- GV$LOGMNR_CALLBACK Synonym for GV_$LOGMNR_CALLBACK GV$LOGMNR_CONTENTS Synonym for GV_$LOGMNR_CONTENTS GV$LOGMNR_DICTIONARY Synonym for GV_$LOGMNR_DICTIONARY GV$LOGMNR_LOGFILE Synonym for GV_$LOGMNR_LOGFILE GV$LOGMNR_LOGS Synonym for GV_$LOGMNR_LOGS GV$LOGMNR_PARAMETERS Synonym for GV_$LOGMNR_PARAMETERS GV$LOGMNR_PROCESS Synonym for GV_$LOGMNR_PROCESS GV$LOGMNR_REGION Synonym for GV_$LOGMNR_REGION GV$LOGMNR_SESSION Synonym for GV_$LOGMNR_SESSION GV$LOGMNR_STATS Synonym for GV_$LOGMNR_STATS GV$LOGMNR_TRANSACTION Synonym for GV_$LOGMNR_TRANSACTION V$LOGMNR_CALLBACK Synonym for V_$LOGMNR_CALLBACK V$LOGMNR_CONTENTS Synonym for V_$LOGMNR_CONTENTS V$LOGMNR_DICTIONARY Synonym for V_$LOGMNR_DICTIONARY V$LOGMNR_LOGFILE Synonym for V_$LOGMNR_LOGFILE V$LOGMNR_LOGS Synonym for V_$LOGMNR_LOGS V$LOGMNR_PARAMETERS Synonym for V_$LOGMNR_PARAMETERS V$LOGMNR_PROCESS Synonym for V_$LOGMNR_PROCESS V$LOGMNR_REGION Synonym for V_$LOGMNR_REGION V$LOGMNR_SESSION Synonym for V_$LOGMNR_SESSION TABLE_NAME COMMENTS ------------------------------ -------------------------------------------------------------------------------- V$LOGMNR_STATS Synonym for V_$LOGMNR_STATS V$LOGMNR_TRANSACTION Synonym for V_$LOGMNR_TRANSACTION GV$LOGMNR_LOGS 是分析日志列表视图 分析结果在GV$LOGMNR_CONTENTS 视图中，可按如下语句查询： select scn,timestamp,log_id,seg_owner,seg_type,table_space,data_blk#,data_obj#,data_objd#, session#,serial#,username,session_info,sql_redo,sql_undo from logmnr3 t where t.sql_redo like 'create%'; 若是不能正常查询GV$LOGMNR_CONTENTS视图，并报如下错误，ORA-01306: 在从 v$logmnr_contents 中选择以前必须调用 dbms_logmnr.start_logmnr() 。可采用以下方法： create table logmnr3 as select * from GV$LOGMNR_CONTENTS;Oracle端口：1521