Why Oracle 11g need forcedirectio option? Post: 302559025

Sponsored Content

Special Forums UNIX and Linux Applications Why Oracle 11g need forcedirectio option? Post 302559025 by radoulov on Monday 26th of September 2011 05:49:09 AM

09-26-2011

Registered User

The Oracle 11g documentation Checking NFS Mount and Buffer Size Parameters for Oracle Clusterware points to My Oracle Support bulletin 359515.1 which states:

Code:

Purpose

The purpose of this bulletin is to document the options with which the NAS systems should be mounted. 
This note does not cover the new dNFS feature that was introduced in 11g

They use the verb "should" (not "must"). From Request for Comments: 2119:

Code:

3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.

That said, it's worth noting that all this applies to GI and RAC (it's not specified if it applies to a regular databases as well).

Hope this helps.

radoulov

View Public Profile for radoulov

Find all posts by radoulov

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Switching user to oracle to connect Oracle 11g DB with 'sysdba'

I need to connect my Oracle 11g DB from shell script with 'sysdba' permissions. To do this I have to switch user from 'root' to 'oracle'. I've tried the following with no success. su - oracle -c "<< EOF1 sqlplus -s "/ as sysdba" << EOF2 whenever sqlerror exit sql.sqlcode;...

2. Programming

How do I partition an Oracle 11g Table?

Hello, I have a database called "audit_database" and I want to create two tables. Table 1 = Table 1 Table 2 = Audit I want to partition the Audit table into partitions grouped by month. I'm not familiar with table partitioning but doing some reading online shows that it can be done but...

LEARN ABOUT SUSE

apache::session::oracle

Session::Oracle(3)					User Contributed Perl Documentation					Session::Oracle(3)

NAME

       Apache::Session::Oracle - An implementation of Apache::Session

SYNOPSIS

	use Apache::Session::Oracle;

	#if you want Apache::Session to open new DB handles:

	tie %hash, 'Apache::Session::Oracle', $id, {
	   DataSource => 'dbi:Oracle:sessions',
	   UserName   => $db_user,
	   Password   => $db_pass,
	   Commit     => 1
	};

	#or, if your handles are already opened:

	tie %hash, 'Apache::Session::Oracle', $id, {
	   Handle => $dbh,
	   Commit => 1
	};

DESCRIPTION

       This module is an implementation of Apache::Session.  It uses the Oracle backing store and no locking.  See the example, and the
       documentation for Apache::Session::Store::Oracle for more details.

USAGE

       The special Apache::Session argument for this module is Commit.	You MUST provide the Commit argument, which instructs this module to
       either commit the transaction when it is finished, or to simply do nothing.  This feature is provided so that this module will not have
       adverse interactions with your local transaction policy, nor your local database handle caching policy.	The argument is mandatory in order
       to make you think about this problem.

       This module also respects the LongReadLen argument, which specifies the maximum size of the session object.  If not specified, the default
       maximum is 8 KB.

AUTHOR

       This module was written by Jeffrey William Baker <jwbaker@acm.org>.

SEE ALSO

       Apache::Session::File, Apache::Session::Flex, Apache::Session::DB_File, Apache::Session::Postgres, Apache::Session

perl v5.12.1							    2007-09-28							Session::Oracle(3)