Oracle Recycle Bin
13 views
Skip to first unread message
Chris Cranford
May 19, 2022, 7:22:06 PM5/19/22
to debe...@googlegroups.com
Hi everyone -
I'm looking at ways to improve the Oracle connector's overall performance and one of those ways is to address whether we can use a different mining strategy by default. Part of this effort is to verify that we're in a position to make some educated decisions about DDL changes ourselves as we decode the redo events. One of those corner cases involves the DROP TABLE command.
An Oracle database since 10g has the option to enable what is known as the RECYCLEBIN. This is an area where when a table is dropped using DROP TABLE, the table isn't technically gone. Oracle instead renames the table and all its objects, places it in the RECYCLEBIN and this allows the DBA to restore a table should it have been dropped by accident rather than needing to restore from a backup.
I'd like to know from your perspective, first does your environment use the RECYCLEBIN feature in production or is that mostly a feature enabled soley in DEV/TST environments? And if RECYCLEBIN is enabled in production, what is the frequency in which your DBA purges old objects. The reason this is important is that it has a direct impact on how Oracle LogMiner materializes DML events when a table is dropped and I'd like to get an understanding of whether we need to deal with not having RECYCLEBIN enabled or is that mostly a corner case for most environments.
Looking forward to your feedback!
Chris
I'm looking at ways to improve the Oracle connector's overall performance and one of those ways is to address whether we can use a different mining strategy by default. Part of this effort is to verify that we're in a position to make some educated decisions about DDL changes ourselves as we decode the redo events. One of those corner cases involves the DROP TABLE command.
An Oracle database since 10g has the option to enable what is known as the RECYCLEBIN. This is an area where when a table is dropped using DROP TABLE, the table isn't technically gone. Oracle instead renames the table and all its objects, places it in the RECYCLEBIN and this allows the DBA to restore a table should it have been dropped by accident rather than needing to restore from a backup.
I'd like to know from your perspective, first does your environment use the RECYCLEBIN feature in production or is that mostly a feature enabled soley in DEV/TST environments? And if RECYCLEBIN is enabled in production, what is the frequency in which your DBA purges old objects. The reason this is important is that it has a direct impact on how Oracle LogMiner materializes DML events when a table is dropped and I'd like to get an understanding of whether we need to deal with not having RECYCLEBIN enabled or is that mostly a corner case for most environments.
Looking forward to your feedback!
Chris
Reply all
Reply to author
Forward
0 new messages