Thanks for the update, I will check further.

Thanks,

I am having same issue, I reviewed the document suggested but those bugs apply to lower version, I have the patches suggested, running in EXA machine.
I am doing RAT in two DBs, in one of them is running but not in the other.
I review the disk types and in the DB that is running no having enq: FB contention has NORMAL redundancy.

I reviewed and follow the doc: ID 2277855.1
SQL> select session_id,SQL_ID,EVENT,P1,P1text,P2,P3,WAIT_TIME,SESSION_STATE,TIME_WAITED from v$active_session_history where event like '%FB%';
SQL> select name from v$tablespace where ts#=P2; ----------->>> P2 value from above
SQL> SELECT dbms_utility.data_block_address_block(p3) "BLOCK", dbms_utility.data_block_address_file(p3) "FILE" from dual; ---->>> P3 Value from Above

I need to determine the table for that block and file.
I am using :
SELECT segment_type, segment_name
FROM dba_extents
WHERE file_id = 1
AND 3840 BETWEEN block_id AND block_id + blocks -1;

I am creating a SR w/ Support, any help will be welcome.

Thank you
- Eric