<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>OracleOnLinux &#187; Experiments</title>
	<atom:link href="http://www.oracleonlinux.cn/category/oracle/experiments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.oracleonlinux.cn</link>
	<description>Oracle and Linux,I Love U.</description>
	<lastBuildDate>Wed, 08 Sep 2010 10:28:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>10g utilities:How to use LogMiner I</title>
		<link>http://www.oracleonlinux.cn/2010/05/20/10ghow-to-use-logminer/</link>
		<comments>http://www.oracleonlinux.cn/2010/05/20/10ghow-to-use-logminer/#comments</comments>
		<pubDate>Wed, 19 May 2010 18:31:56 +0000</pubDate>
		<dc:creator>Asher</dc:creator>
				<category><![CDATA[Experiments]]></category>
		<category><![CDATA[Oracle]]></category>

		<guid isPermaLink="false">http://www.oracleonlinux.cn/?p=255</guid>
		<description><![CDATA[


在对数据库做不完全恢复的时候，如果我们能够精确的定位到出错的时间点的话，那么，我们可以在很大的程度上一次性地保证不完全恢复成功。所以，问题也就是我们应该怎么能够准确定位这个人为错误（如误删除表，错误的提交DML）发生的时间？接下来，要跟大家分享一下关于10g里LogMiner这个“日志挖掘器”的用法，也就是，在Oracle 10g版本的数据库，应该怎么使用LogMiner：
首先：简单介绍一下LogMiner工具。LogMiner 是Oracle公司从产品8i以后提供的一个非常有实用价值的分析工具，使用该工具可以轻松获得Oracle Online redo logs或者Archived logs日志文件中的具体内容。日志文件中记录了所有对数据库的数据块儿进行过改变的操作，而Logminer正是可以挖掘日志文件的利器。
其次：该如何使用Logminer？在早期的数据库版本里，LogMiner在默认情况下，并没有安装，需要手工的以SYSDBA身份去执行$ORACLE_HOME/rdbms/admin/dbmslm.sql以及$ORACLE_HOME/rdbms/admin/dbmslmd.sql这两个脚本。前者是创建DBMS_LOGMNR package，后者用于创建DBMS_LOGMNR_D这个包。在10g版本的数据库，这两个PL/SQL 包默认已经创建，我们就无须再去执行那两个脚本，可以直接对其调用。
然后：需要说明的一点，在Oracle 10g数据库版本里面，默认情况下，联机日志文件记录的内容并非提供任何的Supplemental logging,也就是说默认情况下使用LogMiner只能看到DDL操作。要想看到DML操作的话，在DML操作产生新的日志记录之前我们要启用最低的Supplemental logging,而启用这一特性又分为在数据库级别以及表级别，以下简单演示在全库级别启用最低Supplemental logging:
确认当前数据库Supplemental logging:
SQL&#62; select supplemental_log_data_min from v$database;
SUPPLEME
--------
NO
启用Supplemental logging，以便可以通过LogMiner看到日志文件中记录的关于DML操作的相关信息：
SQL&#62; alter database add supplemental log data;
Database altered.
SQL&#62; select supplemental_log_data_min from v$database;
SUPPLEME
--------
YES
日志“挖掘&#8221;结束，可以禁用Supplemental logging：
SQL&#62; alter database drop supplemental log data;
Database altered.
接下来：该说说具体使用LogMiner的方法了：
使用方法1：
1.1确认数据库当前的日志文件信息：
SQL&#62; select * from v$log;
    GROUP#    THREAD#  SEQUENCE#    [...]]]></description>
		<wfw:commentRss>http://www.oracleonlinux.cn/2010/05/20/10ghow-to-use-logminer/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>oracle 10g SYSAUX tablespace</title>
		<link>http://www.oracleonlinux.cn/2010/01/27/oracle-10g-sysaux-tablespace/</link>
		<comments>http://www.oracleonlinux.cn/2010/01/27/oracle-10g-sysaux-tablespace/#comments</comments>
		<pubDate>Wed, 27 Jan 2010 10:57:09 +0000</pubDate>
		<dc:creator>Asher</dc:creator>
				<category><![CDATA[Experiments]]></category>
		<category><![CDATA[Oracle]]></category>
		<category><![CDATA[Tablespace]]></category>

		<guid isPermaLink="false">http://www.oracleonlinux.cn/?p=207</guid>
		<description><![CDATA[The SYSAUX(System Auxiliary) tablespace is a new feature of Oracle 10g database,before 10g release,there wasn&#8217;t this tablespace.After you created your database via DBCA(Database Configuration Assistant) tool,the SYSAUX tablespace was created for you automatically.
But what&#8217;s the mainly function of that tablespace? Why Oracle present the SYSAUX tablespace? Does it bring some benefit for the database or [...]]]></description>
		<wfw:commentRss>http://www.oracleonlinux.cn/2010/01/27/oracle-10g-sysaux-tablespace/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>revoke sysdba from user_name</title>
		<link>http://www.oracleonlinux.cn/2010/01/21/revoke-sysdba-from-user_name/</link>
		<comments>http://www.oracleonlinux.cn/2010/01/21/revoke-sysdba-from-user_name/#comments</comments>
		<pubDate>Thu, 21 Jan 2010 10:38:44 +0000</pubDate>
		<dc:creator>Asher</dc:creator>
				<category><![CDATA[Experiments]]></category>
		<category><![CDATA[Oracle]]></category>

		<guid isPermaLink="false">http://www.oracleonlinux.cn/?p=202</guid>
		<description><![CDATA[把sysdba权限授予给user1之后，orapwSID文件中记录了user1的信息，但是将sysdba权限从user1收回之后，orapwSID文件中依然有user1用户。这是为什么呢？？？
可是联机文档上明明说：
A user&#8217;s name remains in the password file only as long as that user has at least one of these two privileges. If you revoke both of these privileges, Oracle Database removes the user from the password file.

以下是我的实验步骤：
1看到字典里面记录的只有SYS用户拥有SYSDBA和SYSOPER系统权限：
SQL&#62; select * from v$pwfile_users;
USERNAME                       SYSDB SYSOP
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212; &#8212;&#8211; &#8212;&#8211;
SYS           [...]]]></description>
		<wfw:commentRss>http://www.oracleonlinux.cn/2010/01/21/revoke-sysdba-from-user_name/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>ORA-03113: end-of-file on communication channel</title>
		<link>http://www.oracleonlinux.cn/2009/12/14/ora-03113-end-of-file-on-communication-channel/</link>
		<comments>http://www.oracleonlinux.cn/2009/12/14/ora-03113-end-of-file-on-communication-channel/#comments</comments>
		<pubDate>Mon, 14 Dec 2009 15:57:45 +0000</pubDate>
		<dc:creator>Asher</dc:creator>
				<category><![CDATA[Experiments]]></category>
		<category><![CDATA[Oracle]]></category>

		<guid isPermaLink="false">http://www.oracleonlinux.cn/?p=174</guid>
		<description><![CDATA[Tonight,after I did some changes on the parameter(processes,changed it from 150 default to 2),I issued the commands below:
SQL&#62; alter system set processes=2 scope=spfile;
System altered.
SQL&#62; shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL&#62; startup;
ORA-03113: end-of-file on communication channel
SQL&#62; !oerr ora 03113
03113, 00000, &#8220;end-of-file on communication channel&#8221;
// *Cause: The connection between Client and Server process was broken.
// *Action: [...]]]></description>
		<wfw:commentRss>http://www.oracleonlinux.cn/2009/12/14/ora-03113-end-of-file-on-communication-channel/feed/</wfw:commentRss>
		<slash:comments>94</slash:comments>
		</item>
		<item>
		<title>Multiplexing Oracle Control File</title>
		<link>http://www.oracleonlinux.cn/2009/10/18/multiplexing-oracle-control-file/</link>
		<comments>http://www.oracleonlinux.cn/2009/10/18/multiplexing-oracle-control-file/#comments</comments>
		<pubDate>Sun, 18 Oct 2009 12:06:40 +0000</pubDate>
		<dc:creator>Asher</dc:creator>
				<category><![CDATA[Experiments]]></category>
		<category><![CDATA[Oracle]]></category>

		<guid isPermaLink="false">http://www.oracleonlinux.cn/?p=98</guid>
		<description><![CDATA[1 Multiplexing the control file when using SPFILE
Firstly, Obtain the information of your control file
SQL&#62; select * from v$controlfile;



STATUS
NAME
 IS_ 
 BLOCK_SIZE 
 FILE_SIZE_BLKS 


 
 /u01/oradata/helen/control01.ctl 
NO
16384
430


 
 /u01/oradata/helen/control02.ctl 
NO
16384
430



also you can issue this command show parameter control_files  to get the information of your control file.
Secondly, Make sure that your server is using [...]]]></description>
		<wfw:commentRss>http://www.oracleonlinux.cn/2009/10/18/multiplexing-oracle-control-file/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
