This is a bug. Please open an SR at MyOracleSupport as it should to be addressed.

I agree with SB that you shouldn't have done it. And that you should definitely know better than to alpha test code on a multi-user server, but that said Oracle should gracefully handle the exception without taking everything down.

"Total memory usage can grow beyond the value of MEMORY_TARGET. For example, memory is allocated to PL/SQL tables and varrays regardless of the value of MEMORY_TARGET as long as memory is available at the operating system level."

So, perhaps there is some confusion here, and the rogue transaction actually just uses all the available common memory, thus crashing other transactions, but not the database, and therefore it may not be a bug?

Edited by: BrendanP on 04-Jan-2013 14:08
Although I suppose it shouldn't have disconnected me, just dropped the transaction?