On 22 July 2010 12:39, Karsten Gaul <[email protected]> wrote: > hum how do i put this? > > no but it is the only one using that specific db server. however, the same > db server is used by at least one more app. That's why it is kinda bad that > the db crashes because the other app is way more important than my load > test. anyhow, this second app, being a qa version of mine, should not > produce that much traffic that it, even in addition to my load test, causes > the db to crash.
I don't know how to administer Oracle dbs, but it does seem strange that an external application can cause it to crash. Surely there must be ways to configure the DB so that it remains active even under heavy load? Or at least it should degrade gracefully. For example, limiting the number of active connections, limiting resources that can be used by a single connection. That might also give a better clue as to which queries are causing the problem. > rgds > Karsten > > Am 22.07.2010 13:16, schrieb Deepak Goel: >> >> Hey >> >> Is your app the only app running on the server? >> >> Deepak > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
