I use this type of activity to zap stale users accounts and their old
objects etc.. Also try to get them to change passwords as well.
- Kirti
> -----Original Message-----
> From: Bruce Page [SMTP:bpage_at_kimball.com]
> Sent: Tuesday, June 06, 2000 2:10 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Rebuilding database to change block size
>
> Also check your I/O and see if you have any bottle necks. You could use
> this as a chance to move tablespaces easily to other file systems. You
> could move tables to different tablespaces. You can change your free list
> parameter.
>
> You are at a point where you can take a step back and say "What can I
> change now that I cannot easily change later?"
>
>
> -----Original Message-----
> From: Mike Lanteigne [ <mailto:mikel_at_shec.com>]
> Sent: Tuesday, June 06, 2000 1:00 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: Rebuilding database to change block size
>
>
> Hi Jay,
>
> I'd take this opportunity to do a little more. What I've done in the past
> is
> to pre-create a script to create the tablespaces, database objects,
> users,
> etc. That way when you're done, you'll have a script to create the
> database
> anytime you want, and you'll have a better feel for your database.
>
> Mike
>
>
>
>
>
> ----- Original Message -----
> To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
> Sent: Tuesday, June 06, 2000 11:50 AM
>
>
> > Okay, we finally got enough storage space to hold an export of our
> > datawarehouse so I'm going to change the block size from 4 to 16.
> >
> > Obviously I'm testing this on a small play database first, but I've
> never
> > done this before so I have several questions and would welcome any
> > advice/comments/criticisms. Here's what I was thinking of:
> >
> > 1. Do a full export (consistent=y) as sys. Backup control file to
> trace
> > (just as an extra precaution).
> > 2. Shutdown database.
> > 3. Cold backup of all files.
> > 4. Drop all datafiles,control files, redo logs. Any other cleanup
> > necessary? Or since the CREATE DATABASE command will erase data in
> existing
> > datafiles, can I just skip this step entirely?
> > 5. Change db_block_size in init.ora file
> > 6. Start database in NOMOUNT mode.
> >
> > Here's where I'm on somewhat thinner ice:
> > 7. Issue create database command. Is there a way to generate this
> > automatically from the existing database? It's easy enough to write
> from
> > scratch but I'd rather not take chances with typos if I don't have to.
> > 8. Change sys and system passwords.
> > 9. I definitely want to precreate a few tablespaces where I want to
> change
> > the initial extent parameter. Is it necessary to precreate all
> tablespaces
> > and users (I can generate that script very easily)?
> > 10. Import database as sys.
> >
Received on Tue Jun 06 2000 - 13:56:47 CDT
