Re: Mixing OLTP with DSS

[Tom Pall]

Oracle 8i uses a different aging algorithm than before.  It waits for blocks to be accessed several times before considering keeping them around.  That way the full scan of a big table won't push other tables out.  If aging becomes a problem, remember you can now size a keep and recycle buffer pool (The names only suggest the buffers' intended purposes.  Each follows the same aging algorithm.) and can alter table/index/partition to assign it a new buffer cache online.   If the data OLTP and DSS don't have to be accessed in the same query, it makes sense to create a new database to contain the OLTP data.  Not only will the caches be separate, their rollback, redo and process will be separate as well.  Plus, you'll be able to backup or take one down without bothering the other one.   If the data has to be accessed together, you'll have to weigh the impact using database links in with the other pros and cons of creating a separate database.   ----- Original Message ----- From: Rick Stephenson To: Multiple recipients of list ORACLE-L Sent: Tuesday, October 29, 2002 12:19 PM Subject: Mixing OLTP with DSS Am I looking for trouble by mixing an OLTP type database with a DSS type database?   I currently have a relatively small database that is used for quick lookup type actions.  The company wants to add a much bigger and constantly growing application for historical reporting on the same machine.  Should I create another instance or keep it in the same instance?   Keeping it in the same instance would seem to defeat having anything cached seeing that the large reports will flush out the cache each and every time.   I am running Oracle 8.1.7, on Solaris 2.8.   Any suggestions would be helpful.   Thanks,   Rick Stephenson