Is it possible that a database needs a recovery after closing down the database while one of the tablespaces, and in this case the temporary tablespace, is still in backup mode?
This error occured when a script responsible for our online backup failed at one point and ended prematurely.
Can't remember if you do this at mount level or open level.
alter tablepaspace tablespace_name end backup;
you can find which tablespaces are in backup mode by querying v$backup.status.
That statement is indeed correct. It works when the database is online.
It works both in SQL*PLUS and after "connect internal" in svrmgrl.
However, I was wondering whether it caused the database to crash after being shutdown before the tablespace is brought back out of backup mode.
This shouldn't cause a database crash, all it does it freeze the header on the datafiles that are housed by the tablespace.
This will ensure that the scn in the header does not change whilst the datafiles are being backed up.
If you want to find the cause of your crash the best thing to do would be to review your alert.log.
Look for any errors, ddl etc just before the instance crashed.