Rollback / savepoint Issue

Question

Hi,
I'm a little confused on how the rollback to savepoint works in the database.
A transaction statement such as Rollback fires an internal commit. Does the command :
Rollback to savepoint <savepoint name> also issues an implicit commit?
I did the following which caused all the confusion:
SQL>commit;
SQL> insert into table_name values ('sdf',23,...);
SQL> 1 Row isnerted
SQL> insert into table_name values ('sdf',23,...);
SQL> 1 Row isnerted
SQL> insert into table_name values ('sdf',23,...);
SQL> 1 Row inserted
SQL> Savepoint A;
SQL> Savepoint created
SQL> insert into table_name values ('sdf',23,...);
SQL> 1 Row inserted
SQL> insert into table_name values ('sdf',23,...);
SQL> 1 Row inserted
SQL> insert into table_name values ('sdf',23,...);
SQL> 1 Row inserted
SQL> Savepoint B;
SQL> Savepoint created
SQL> insert into table_name values ('sdf',23,...);
SQL> 1 Row inserted
SQL> insert into table_name values ('sdf',23,...);
SQL> 1 Row inserted
SQL> insert into table_name values ('sdf',23,...);
SQL> 1 Row inserted
SQL> Savepoint C;
SQL> Savepoint created
Now if we do a :
SQL> Rollback to Savepoint B;
SQL> Rollback completed
Would an implicit commit be fired after this statement which would erase all marked savepoints ?
Because it was possible to do a :
SQL> Rollback to Savepoint A
SQL> Rollback Completed

Answer 1

hi,
Rollback doesn't implicitly commit anything.
commit means sth different than rollback.
When commit,
All transactions get saved in the database,
Log maintained
All locks released
etc...In Rollback to savepoint,
Related transaction rollbacked but previous one are still in pending not commited
related locked released , not all locks which is occured due to previous one.
etc...hv a nice day,
Rup