Why would SAP not turn Recyclebin on to help in recoverability of dropped tables?

[linda_westerhold]

Why would SAP not turn Recyclebin on to help in recoverability of dropped tables similar to how they "don't recommend ASMM".  It is as if they are trying to stop all features that enhance the recoverability in Oracle, like if a user accidentally drops a table.  The recommended setting for Oracle Recyclebin is "OFF" from SAP's notes.  Has anyone else ignored this and ran with the Recyclebin setting "ON?"

[janos_mucsi-besze]

Hi,

the recycle bin is turned off since Oracle 10g because it was causing a lot of issues especially using BW.  The decision has been made after throughout analysis and the collected experiences.

Instead of using the recycle bin, we support the usage of flashback database, flashback table. Although not the same, but still can be used in case of some user made mistakes.

[linda_westerhold]

except if someone drops a table, then only a full database restore or Recyclebin option can be used to recover a dropped table. flashback table will fail if the DLL is changed. Flashback only works if data alone is changed, not the table structure itself.

[linda_westerhold]

Except that flashback table only works if the data alone was changed. If the table is altered or dropped, you cannot flashback the table, then you need Recyclebin or to do a database backup recovery to recover the table or restore it to another instance and copy the table. Both would take more time and effort than if we had Recyclebin enabled.