Oracle lineage issues with tables and views of the same name

[KsM00000]

Affected module
UI

Describe the bug
We have views and tables with the same names. Recently I realised that our view 'a_link' displays wrong lineage becuase it displays lineage of the deleted table 'A_LINK'.

I have reached out to the community on Slack and after some troubleshooting I was told to open a ticket here.

To Reproduce

After I hard deleted the table, view started to display correct lineage.

Expected behavior
We expect tables to show the correct lineage.

Version:

• OS: Ubuntu
• Python version: 3.9
• OpenMetadata version: 1.5.4

Additional context
I think the bug is related to the issue #17796