Why is a Full Database Backup (as opposed to a level 0 backup) required in Oracle after switching to ARCHIVELOG mode?
You cannot use backups from before the switch to ARCHIVELOG mode to restore and recover the database to a point in time after the switch.


Looking at this quote it makes sense. If you enable archivelog on a database where it was not enabled, then any backup that you have before archive log was enabled can't be used to do a point in time recover, since you have no archive logs to rolll forward from the backup. You just have the backups and can restore to whatever warm backups that you have.

If you take a database that has archive log enabled and disable archive log, then going forward you can't do point in time recover. You can only restore to whatever backups that you have. But any warm backup that you have from when the database was in archive log can be restored and rolled as far forward as you have archive logs.

As far as I know both a warm full backup and incremental level 0 backup are full backups and you should be able to use either to do a full point in time restore provided that the databases were in archive log mode during the backup. Probably the biggest difference between a full backup and an incremental level 0 backup is that the incremental level 0 backup will update the block change tracking file, but I'm not sure that a full hot backup will do that.

But if you want to know for certain take a database that is not in archive log mode, put it in archive log mode, do an incremental level 0 backup, drop the database and restore it. You will know for certain then.