Hope you can answer this...
Our application (written by a 3rd party) runs a stats build which deals with a huge number of records and as this is the 1st build it includes everything from day one.
The problem is that during the INSERT into a table the process appears to just stop. Its status is ACTIVE but the reads, gets & changes stay static (for days if we leave it). I suspect (either wrongly or rightly!) that there must be a resource or space issue, but I don't understad why the job doesn't fail. We don't use archive logging, just three redo logs that circulate (although too often for my liking).
Any ideas anyone?
Cheers
dklloyd
Our application (written by a 3rd party) runs a stats build which deals with a huge number of records and as this is the 1st build it includes everything from day one.
The problem is that during the INSERT into a table the process appears to just stop. Its status is ACTIVE but the reads, gets & changes stay static (for days if we leave it). I suspect (either wrongly or rightly!) that there must be a resource or space issue, but I don't understad why the job doesn't fail. We don't use archive logging, just three redo logs that circulate (although too often for my liking).
Any ideas anyone?
Cheers
dklloyd