Re: Using symbolic links for data files ??
Date: 1996/01/08
Message-ID: <4cs9pn$phq_at_arl-news-svc-1.compuserve.com>#1/1
Author: jgreene_at_aol.com (Jgreene)
Organization: America Online, Inc. (1-800-827-6364)
Date: 12/24/94 11:04 AM
Newsgroups: comp.databases.oracle
Subject: Re: Using symbolic links for data files ?? Reply To:
jgreene_at_aol.com (Jgreene)
In article <1994Dec19.152251.487_at_cho006>,
Chris Little <little_c_at_cho006.cho.ge.com> wrote:
>Running Oracle 7.0.16 on HP-UX 9.04
>
>By default, the oracle installer places data files in the
>$ORACLE_BASE/data/SID directory, but the Installation Guide
>implies that data files should be distributed across multiple
>devices and that the directory $ORACLE_BASE/data/SID should
>be empty.
>
>My intention is create symbolic links in this directory which
>point to data files distributed across multiple disks. This way,
>if I need to move a file, I can take the tablespace offline,
>move the file, modify the link, and bring the tablespace back
>online again, without having to ALTER TABLESPACE RENAME DATAFILE...
>
>This approach would also seem beneficial for backup and recovery
>because all symbolic links for a database are in a single directory.
>
>Has anybody out there done this, or does anybody see a problem with
>this? I would be grateful for any helpful comments and advice.
>
I have worked on a 13 GB Oracle database that uses this for almost all
of
its files. With the exception of a few tablespaces like system, tools,
etc., most of the data was located on mirrored raw partitions. A link
directory was created that contained nothing but the symbolic links to
the
raw device files. We chose the names of the links so that they
identified
what the tablespace was (i.e. it had sa in the title for sales or di for
dimensions, along with an identifier to show whether it contained tables
or indexes and a sequential number since we had many disks associated
with
a tablespace). It worked well. It was easy when a disk was lost to
restore the data to an alternate disk and then merely modify the link.
Since many of the error messages that identified problems with data
files
list the data file name (and number, but who remembers the numbers), it
helped to be able to identify what data was affected by reading the name
of the link. Good luck.
Received on Mon Jan 08 1996 - 00:00:00 CET