Re: tune for INSERT performance?

You don't need to recreate the whole database to increase the log file size; you can probably even get away with this during normal on-line hours (depending on load).

Just add a couple of log file with the size you want, force a couple of log switches and delete the old ones:

SQLDBA> alter database add logfile 'whatever-filename-you-like' size 20M;
SQLDBA> alter database add logfile 'another-filename-you-like' size 20M;
SQLDBA> alter system switch logfile;
SQLDBA> alter system switch logfile;
SQLDBA> alter database drop logfile 'name-of-old-logfile';
SQLDBA> alter database drop logfile 'name-of-other-old-logfile';

the syntax varies a bit if your are running with multiple members of each group.

if you're in doubt about the names of your log files, then check the V$LOG table.

And don't forget to update your backup, so the next time you make a cold backup, you back up the new log files :-)

Hope this helps

--
Karl
Oracle Certified DBA


Gregg Sporar wrote in message <34A00853.67949CED_at_i2.com>...


>Thomas Kyte wrote:

>

>> You should look at your log files to see how large (or small) they are.

 You


>> might have the default 512k log files which are way too small.  Look in

 the file


>> \orant\rdbms73\trace\{$ORACLE_SID}alrt.ora and see if you have any

 "checkpoint


>> not complete..." type of messages.  These indicate that log files are not

 sized


>> appropriately for the amount of work you want to do.  Try increasing the

 log


>> files.

>>

>

>It looks like this may be where the problem is: we do have the default size

 log


>files and lots of those "checkpoint not complete..." messages.  My thanks

 to you and


>all the others who responded; I'll recreate the database after the holidays

 and


>start the testing over again.

>

>Thanks,

>

>Gregg Sporar

>i2 Technologies

>

>