Does anyone have experienced the behavior of big file tablespace resize
operations in chunks of 64M with a very large number of resize operations?
If yes, how did you mitigate this behavior?
I see some tablespaces being incremented with over 15k Resize operations of
64M in size but sometimes times defined size by autoextend on next (10G) is
The problem is the huge number of resize operations are replied in the
standby database and looks to struggle to handle both redo apply and resize
operations creating significant apply lag .