Sukmar,
1. it really improves performance to use raw when you're on Unix because it
minimizes OS interference with reads and writes (a simplistic answer).
2. migration should be a snap. Something like,
- create sufficient raw space on a partition (divvy or the tool your
system provides)
- soft link the raw device to a file name that makes sense to you, e.g.
mydatabase - skip this if you've already defined the rootdbs and the
dbspace it resides in
- if you haven't yet defined or configured the new rootdbs, start
onmonitor and set all the parameters and initialize
- export old, import old to new
dbexport dbname -ss (check the options)
dbimport dbname -d dbspacename (raw dbspace)
This is sketchy and you'll probably, as usual, have to resort to the
manuals. Actually they're not half bad.
Hope this helps.
Yours,
Nick
At 07:17 AM 6/24/98 -0500, sukumar konduru wrote:
>Hi
>
>Our "rootdbs" has been created as mounted file system rather than raw
>disk space. Our database is in another dbspace which is created as raw
>diskspace.
>
>Is it really improves performance if we use raw diskspace rather than
>unix file system?. What are the
>steps needed in migrating root dbs as raw disk space?
>
>
>Thank you
>
>Sukumar Konduru
>
>
>
>
>
*********************
Nick Nobbe
NLS/BPH
Library of Congress
nnob@loc.gov