Seeing that the recovery model is set to simple and msdn states that the simple recovery model does not support point-in-time recovery - Does this mean that I won't be able to use my transaction log backups to restore the database in a disaster to an hour before it happened?
Even taking a transaction log backup is not supported for databases using the SIMPLE recovery model. This is a restriction of the database engine based on how this recovery model works, and the recovery features it doesn't support, as you mentioned.
A transaction log backup maintenance plan task automatically skips databases in SIMPLE recovery to avoid causing errors.
Which backup should be done first, the database backup or the transaction log backups? Articles that I'm busy reading say I should do the database backup first and then the transaction log backup else I will get maintenance plan errors, but I'm currently first backing up my transaction logs and then data databases and I'm not getting any errors.
For the reasons I mentioned above, it won't matter for databases using SIMPLE recovery, as they will be skipped by the transaction log backup task.
For databases in the other two recovery models, a full backup must exist before you start taking transaction log backups (just the first time), or you will get an error -- this is probably what the articles refer to.
Point-in-time recovery ability is normally driven by business need -- in other words, you determine how critical the data is and how much you can afford to lose, then set the appropriate recovery model to meet those needs, and finally create a backup solution.
Even though SIMPLE recovery does not support point-in-time recovery, if an hour of data loss is okay, perhaps a differential backup solution could work for you. (There are far too many variables that go into developing this kind of solution to give you a complete picture with what was provided in the question.)
The error not enough server storage available is misleading. This is not disk space, but Windows SMB management memory. Try restarting the target machine (where the backup is being saved), or at least restart the Server service.
See the following Microsoft support link for instructions on potential registry changes that may be necessary at the machine where the backup is being stored.
http://support.microsoft.com/kb/304101
Also, you might try a search for "Windows Server error 1130" for more info.
Best Answer
Oracle will automatically delete obsolete files. In general, you should not have to manually delete anything.
From Overview of RMAN Backup and Repository Maintenance
First, determine if you are running out of space. For example using the following query (sample output included):
If you are running out of space you have to either decrease your retention policy or increase the size of your FRA.