OFA V. NT default directory structure

OFA V. NT default directory structure

Post by Deborah Lu » Fri, 31 Oct 1997 04:00:00



We are in the process of installing Oracle 7.3 under NT.  I noticed that the
default install uses a completely non-OFA directory structure.  What do most
people do?  Redo the whole thing? Leave it as is?  If I go to the trouble to
redo it, do I mess up the installer under NT?

I will probably create a new database anyway because I do not like the default
database name or page size so I could rework the init file and create the
tablespaces, etc. differently while I'm at it.

Deborah Luik

 
 
 

OFA V. NT default directory structure

Post by Matthew Arroch » Sun, 02 Nov 1997 04:00:00


You need to reorganize the datafiles to use the I/O most efficiently
yourself.
Stop the database and services.  Make a copy of the datafile to be moved to
the new location.  Run svrmgr23 connect internal, issue the command:
        alter database datafile 'oldpath\file' to 'newpath\file';

This will reset where Oracle looks for the datafiles.
After running the command issue:
        select * from dba_data_files;
or      select * from v$datafile;

This will give the location the controlfile expects to find the datafile.
After verifying the controlfile no longer points to the original path,
delete the original datafile at the OS level.  This is how to spead out the
Oracle datafiles on NT.  Currently FOA on NT is a manual process.

Matthew Arrocha



Quote:> We are in the process of installing Oracle 7.3 under NT.  I noticed that
the
> default install uses a completely non-OFA directory structure.  What do
most
> people do?  Redo the whole thing? Leave it as is?  If I go to the trouble
to
> redo it, do I mess up the installer under NT?

> I will probably create a new database anyway because I do not like the
default
> database name or page size so I could rework the init file and create the
> tablespaces, etc. differently while I'm at it.

> Deborah Luik


 
 
 

OFA V. NT default directory structure

Post by thom.. » Fri, 07 Nov 1997 04:00:00


If you installed Oracle 7.3 Workgroups then that's why.  WorkGroup server
installtion is limited.  It does not allow you to configure where different
tablespaces will go where on different partitions or disk etc.  It is limited.

It puts all the datbase objects (Tablespaces) in $ORACLE_HOME/dbs (unix) or for
NT everything under \ORANT\database.

If you had Oracle Server -Enterprise version, it prompts you through a series
of configurations settings upon installation where you what certain files to
go.

I have done several installations of both products - enterprise and Workgroups
and that's just the way it works.

For workgroups after installation you now have to manually using sqlplus or the
client manager tools to move the files to where you want them to go.

What you may want find out is if Oracle has a built in parameter file that you
can edit for tablespace size and location to be used by the workgroup
installer.

Thomas


Quote:Luik) writes:
>We are in the process of installing Oracle 7.3 under NT.  I noticed that the
>default install uses a completely non-OFA directory structure.  What do most
>people do?  Redo the whole thing? Leave it as is?  If I go to the trouble to
>redo it, do I mess up the installer under NT?

>I will probably create a new database anyway because I do not like the default
>database name or page size so I could rework the init file and create the
>tablespaces, etc. differently while I'm at it.

>Deborah Luik

 
 
 

OFA V. NT default directory structure

Post by Matthias Gre » Sat, 08 Nov 1997 04:00:00



> If you installed Oracle 7.3 Workgroups then that's why.  WorkGroup server
> installtion is limited.  It does not allow you to configure where different
> tablespaces will go where on different partitions or disk etc.  It is limited.

> It puts all the datbase objects (Tablespaces) in $ORACLE_HOME/dbs (unix) or for
> NT everything under \ORANT\database.

This is definitely wrong!! We've WGS on NT and our oracle sw resides on
disk1 db-files on disk2 (RAID) and archived redo logs on disk3. It's the
way how you create your db (data-files) where you can decide how to
distribute your db-files in the way you want.

The only fact is that the default db (with scott and all others) will be
installed in the directories you mentioned. But you kick it away anyway,
when you create your own db.

For db-Installation try something like this:

create database oracle
    logfile    
                group 1 ('c:\ora_redo\wdblog1.ora',
                        'f:\ora_redo\wdblog1.ora',
                        'e:\ora_redo\wdblog1.ora') size 500K reuse,
                group 2 ('c:\ora_redo\wdblog2.ora',
                        'f:\ora_redo\wdblog2.ora',
                        'e:\ora_redo\wdblog2.ora')size 500K reuse,
                group 3 ('c:\ora_redo\wdblog3.ora',
                        'f:\ora_redo\wdblog3.ora',
                        'e:\ora_redo\wdblog3.ora')size 500K reuse
    character set WE8ISO8859P1
        datafile 'd:\dbf\dbsystem.ora' size 600M reuse
        MAXLOGMEMBERS 4
;

create public rollback segment rb_temp storage(initial 50K next 50K
OPTIMAL 1M MINEXTENTS 10);
alter rollback segment rb_temp online;

create tablespace makler
    datafile 'd:\dbf\dbmakler.ora' size 1000M reuse
    default storage (initial 4k next 4k pctincrease 10 minextents 1
maxextents 121);
create tablespace makler_idx
    datafile 'd:\dbf\dbindex.ora' size 700M reuse
    default storage (initial 4k next 4k pctincrease 10 minextents 1
maxextents 121);
create tablespace rollback_data
    datafile 'd:\dbf\dbrollb.ora' size 100M reuse
    default storage (initial 50k next 50k minextents 7 maxextents 121);
create tablespace temporary_data
    datafile 'd:\dbf\dbtemp.ora' size 1000M reuse
    default storage (initial 1M next 1M pctincrease 5 minextents 1
maxextents 121);

alter user system temporary tablespace temporary_data;
alter user system default tablespace system;

create public rollback segment rb1 storage(initial 10M next 1M)
  tablespace rollback_data;

alter rollback segment rb1 online;

alter rollback segment rb_temp offline;

create public rollback segment rb2 storage(initial 10M next 1M)
  tablespace rollback_data;

alter rollback segment rb2 online;

-- theses large rollback segs are for db-population.

> If you had Oracle Server -Enterprise version, it prompts you through a series
> of configurations settings upon installation where you what certain files to
> go.

> I have done several installations of both products - enterprise and Workgroups
> and that's just the way it works.

> For workgroups after installation you now have to manually using sqlplus or the
> client manager tools to move the files to where you want them to go.

> What you may want find out is if Oracle has a built in parameter file that you
> can edit for tablespace size and location to be used by the workgroup
> installer.

> Thomas


> Luik) writes:

> >We are in the process of installing Oracle 7.3 under NT.  I noticed that the
> >default install uses a completely non-OFA directory structure.  What do most
> >people do?  Redo the whole thing? Leave it as is?  If I go to the trouble to
> >redo it, do I mess up the installer under NT?

> >I will probably create a new database anyway because I do not like the default
> >database name or page size so I could rework the init file and create the
> >tablespaces, etc. differently while I'm at it.

> >Deborah Luik

--
Regards

M.Gresz    :-)

 
 
 

OFA V. NT default directory structure

Post by thom.. » Sun, 09 Nov 1997 04:00:00


Matthias,

  You must not have read fully what I wrote.  In Work Groups the default
installation defaults all the db objects SYSTEM, RBS, TEMP, USER in one
subdirectory.  What you just hinted to are manually issuing sql statements to
move or create the datafiles to different partitions.

  I said nothing about you can't change or move db objects once WG is
installed.  That would be ludicrus for Oracle.

Thomas


Gresz) writes:

>> If you installed Oracle 7.3 Workgroups then that's why.  WorkGroup server
>> installtion is limited.  It does not allow you to configure where different
>> tablespaces will go where on different partitions or disk etc.  It is
limited.

>> It puts all the datbase objects (Tablespaces) in $ORACLE_HOME/dbs (unix) or
for
>> NT everything under \ORANT\database.

>This is definitely wrong!! We've WGS on NT and our oracle sw resides on
>disk1 db-files on disk2 (RAID) and archived redo logs on disk3. It's the
>way how you create your db (data-files) where you can decide how to
>distribute your db-files in the way you want.

>The only fact is that the default db (with scott and all others) will be
>installed in the directories you mentioned. But you kick it away anyway,
>when you create your own db.

>For db-Installation try something like this:

>create database oracle
>    logfile
>            group 1 ('c:\ora_redo\wdblog1.ora',
>                    'f:\ora_redo\wdblog1.ora',
>                            'e:\ora_redo\wdblog1.ora') size 500K reuse,
>            group 2 ('c:\ora_redo\wdblog2.ora',
>                    'f:\ora_redo\wdblog2.ora',
>                            'e:\ora_redo\wdblog2.ora')size 500K reuse,
>            group 3 ('c:\ora_redo\wdblog3.ora',
>                    'f:\ora_redo\wdblog3.ora',
>                            'e:\ora_redo\wdblog3.ora')size 500K reuse
>    character set WE8ISO8859P1
>    datafile 'd:\dbf\dbsystem.ora' size 600M reuse
>    MAXLOGMEMBERS 4
>;

>create public rollback segment rb_temp storage(initial 50K next 50K
>OPTIMAL 1M MINEXTENTS 10);
>alter rollback segment rb_temp online;

>create tablespace makler
>    datafile 'd:\dbf\dbmakler.ora' size 1000M reuse
>    default storage (initial 4k next 4k pctincrease 10 minextents 1
>maxextents 121);
>create tablespace makler_idx
>    datafile 'd:\dbf\dbindex.ora' size 700M reuse
>    default storage (initial 4k next 4k pctincrease 10 minextents 1
>maxextents 121);
>create tablespace rollback_data
>    datafile 'd:\dbf\dbrollb.ora' size 100M reuse
>    default storage (initial 50k next 50k minextents 7 maxextents 121);
>create tablespace temporary_data
>    datafile 'd:\dbf\dbtemp.ora' size 1000M reuse
>    default storage (initial 1M next 1M pctincrease 5 minextents 1
>maxextents 121);

>alter user system temporary tablespace temporary_data;
>alter user system default tablespace system;

>create public rollback segment rb1 storage(initial 10M next 1M)
>  tablespace rollback_data;

>alter rollback segment rb1 online;

>alter rollback segment rb_temp offline;

>create public rollback segment rb2 storage(initial 10M next 1M)
>  tablespace rollback_data;

>alter rollback segment rb2 online;

>-- theses large rollback segs are for db-population.

>> If you had Oracle Server -Enterprise version, it prompts you through a
series
>> of configurations settings upon installation where you what certain files to
>> go.

>> I have done several installations of both products - enterprise and
Workgroups
>> and that's just the way it works.

>> For workgroups after installation you now have to manually using sqlplus or
the
>> client manager tools to move the files to where you want them to go.

>> What you may want find out is if Oracle has a built in parameter file that
you
>> can edit for tablespace size and location to be used by the workgroup
>> installer.

>> Thomas


(Deborah
>> Luik) writes:

>> >We are in the process of installing Oracle 7.3 under NT.  I noticed that
the
>> >default install uses a completely non-OFA directory structure.  What do
most
>> >people do?  Redo the whole thing? Leave it as is?  If I go to the trouble
to
>> >redo it, do I mess up the installer under NT?

>> >I will probably create a new database anyway because I do not like the
default
>> >database name or page size so I could rework the init file and create the
>> >tablespaces, etc. differently while I'm at it.

>> >Deborah Luik

>--
>Regards

>M.Gresz    :-)

 
 
 

1. OFA compliant server directories?

there is no reason to prefer one over the other inasmuch as the use of
$ORACLE_HOME is the major feature of OFA. defining $ORACLE_BASE is a first
step for cases in which you elect to allow the installer to define
$ORACLE_HOME and its subdirectories; if you define it in the environment prior
to your first OFA install, it will be used as-is.

structures of the form "/u01/oracle/..." are perfectly acceptable in practice.

--
Dave Mausner, Consulting Manager, Braun Technology Group, Chicago.

2. D2 CS => Oracle: EExternalException on Connect with running Delphi

3. OFA Structure issue (for gurus only)

4. Deleting default triggers

5. Help: OFA vs. RAID5 Best Drive Config

6. seeking development work

7. Oracle OFA vs. HP-UX filesystem layout

8. NT Technical Specialist, OFA, Contract

9. Oracle server setup standards on NT - OFA or not

10. OFA standard - What is the best NT server configuration

11. OFA compliance with NT

12. OFA on NT