Uncommited transactions remain after Instance Recovery

Question

After Instance Recovery, the database seems to contain uncommitted transactions. Please provide an explanation for the following:
create table t1
as
select *
from all_objects;
commit;
create table t2
as
select *
from all_objects;
update t2
set object_id = 1 where rownum = 1;
shutdown abort;
Neither table t2 nor the update to it were committed (right?), therefore, once the database starts up t2 should not be there. On the contrary, it is still there. In the Oracle Database Backup and Recovery Advanced Guide 10g Release 2, page 11-9, explains how the uncommitted transactions are removed (rolled back) in the Roll Backward step (transaction recovery) of the Instance recovery process.
Any insight on this is highly appreciated. Thanks.

Answer 1

Note also following scenario run with SYSDBA privileges:
bas002> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Prod
PL/SQL Release 10.2.0.2.0 - Production
CORE    10.2.0.2.0      Production
TNS for 32-bit Windows: Version 10.2.0.2.0 - Production
NLSRTL Version 10.2.0.2.0 - Production
bas002>
bas002> drop table t2;
drop table t2
ERROR at line 1:
ORA-00942: table or view does not exist
bas002> create table t2
  2  as
  3  select *
  4  from all_objects;
Table created.
bas002>
bas002> update t2
  2  set object_id = 1 where object_id=258;
1 row updated.
bas002>
bas002> shutdown abort;
ORACLE instance shut down.
bas002> startup
ORACLE instance started.
Total System Global Area  192937984 bytes
Fixed Size                  1288484 bytes
Variable Size             130025180 bytes
Database Buffers           54525952 bytes
Redo Buffers                7098368 bytes
Database mounted.
Database opened.
bas002>
bas002> select count(*) from t2 where object_id=1;
  COUNT(*)
         0
bas002>Message was edited by:
Pierre Forstmann