We have database using OLTP system (document management system OPENTEXT).
There is a lot of transactions occur inside database.

Sequentially, we get a lot of messages as -
Thread 1 cannot allocate new log, sequence 13124
Private strand flush not complete
...
...
...

I read a lot about right redo log sizing - but I have not found effective way yet.
I came across the parameter - fast_start_mttr_target

Also when chose 'Sizing Advice' in Oracle Enterprise manager for optimal redo log size - it says:
The database cannot recommend the optimal redolog file size. Please set the initialization parameter FAST_START_MTTR_TARGET.

Can we enable that parameter, where Oracle recommends to enable it basing on article -
http://www.dba-oracle.com/oracle_tips_sizing_advisor.htm?

If there are any best practices for that parameter for OLTP systems?
If answer is yes, we can enable it - what value should we set?

With regards!