So if you have a very busy varchar2(1) column and a 16K db_block_size, a 16K block is written even if only one character in the block has changed? Seems like hotspots, er, hot blocks could do a "multiplicity" thing. You know... like the more you replicate DNA the more chance for mutation? :-)
Been watching too many movies... -----Original Message----- Sent: Monday, July 15, 2002 2:28 PM To: Multiple recipients of list ORACLE-L Dick, We're using Netapp F720's to store all our datafiles (production and test) in a small/medium OLTP environment and are quite happy with the setup. YMMV. We run out of two sets of collocated servers. At each collocation there are at least two filers and at least two servers. The filers and the servers currently have three 100BaseT network connections. One front channel and two back channels. Each LAN segment is switched. Thus any server at a location can connect to any filer at that location. Datafiles can be spread across filers or spread across channels as performance requires. The WAFL does indeed write to the nearest available inode and relinks the inode map. The unlinked inode is immediately available for rewrite unless it is a member of a snapshot. Thus while reserving unlinked blocks is inefficient from a storage perspective, it is a factor you get to control by controlling the snapshots. -rje -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Orr, Steve INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
