I havent seen that problem since 10.1. I thought that was fixed.
On Thu, Oct 17, 2019 at 5:05 AM Howard Latham <howard.latham@xxxxxxxxx>
solved it - shared mem segment was still attached to oracle process.
how to find if you get same problem
On Wed, 16 Oct 2019 at 00:28, Mladen Gogala <gogala.mladen@xxxxxxxxx>
But they do. I have to use "-prelim" when that happens.
On 10/15/19 3:25 PM, Tanel Poder wrote:
Yep, recovery area / archive log stuck shouldn't affect SYSDBA--
connections as they don't log their audit to in-database tables.
Tel: (347) 321-1217