"needs media recovery" after a successful recovery ???

Question

RMAN novice here....
Oracle 9.2.0.1.0 on Redhat Linux (Itanium)
Running in NOarchivelog mode
In RMAN, I backed up a set of datafiles in read only mode taking this approach....
sql "alter tablespace foo read only";
configure channel 1 device type disk format 'backupdisk/mybackuparea/foo.dbf.bck';
backup datafile 'dbdisk/mydb/foo.dbf';
sql "alter tablespace foo read write;
Everything seemed to go fine.
After some time, I wanted to restore/recover. This is what I did (again, in RMAN"...
sql "alter fablespace foo offline";
restore datafile 'dbdisk/mydb/foo.dbf';
recover datafile 'dbdisk/mydb/foo.dbf' noredo;
sql "alter tablespace foo online";
My first stab at it, without the "noredo" failed. But with the "noredo" I got
"Starting recover at ...."
A set of channel assignment statements
"Finished recover at ..."
Looks to have run OK.
But then, when I try to put the tablesopace back online...
"failure of sql command on default channel at...."
"failure during parse/execution of SQL statement: alter tablespace foo online"
"file 1 needs media recovery"
"data file 1: 'dbdisk/mydb/foo.dbf'"
What gives?
Thanks for any help

Answer 1

I've read the books and googled this to death.
Looks like I'm screwed.
At this point, I don't even care about the datafile or the tablespace it contained. I just want my database back.
I dropped the tablespace and it's datafile (and it's data too). I'll have to repopulate from scratch.
Lesson learned
This is what I want to do.....
I want to do a 1x/wk backup of a schema (not the whole DB, I don't have enough disk space for that, just 1 of the schemas). I've designed the thing such that each schema has it;s own tablespaces (no overlap) and each tablespace maps to a single datafile.
I would have liked to do some sort of online backup of the schema (read/write while backup is happening), but I'll settle for read only. If Oracle can't hack that, then I'll take the tablespaces offline.
The schema contains hundreds of millions of records, and the load preocess involves several times that number of data manipulation statements (deletes, updates, inserts). I'd rather not use archivelog mode because I don't have the disk space for it. And, given the volume and nature of the data I'm loading (hundreds of millions of records, created from the data in large raw data files), and how it's being loaded (precompiled C/SQL programs), I would never have need to "rerun" the enormous archives for any reason.
So...
1) backup a single schema (an exclusive set of tablespaces/datafiles)
2) as "online" as possible
3) in noarchivelog mode.
The only thing that I've seen that can do this is EXPORT/IMPORT. I tried that, but extrapolating IMPORT performance, even with all the streamlining recommendations, would take over 3 days. For this reason, IMPORT is not a viable option.
-dave