Help in stored procedure

Question

i have a stored procedure in MSSQL which needs to be migrated to oracle 10g,i have got problem related to migration.
My mssql stored procedure is like as follows:
create procedure sample(
var1 varchar(20),
var2 varchar(20) )
as
declare @V_TBL table(col1 varchar(20), col2 varchar(20))
begin
insert into @V_TBL(col1,col2)
select col1,col2 from table1 where col1=@var1 and col2=@var2
some more logic
end
now in oracle how do i create this variable table or some other way is there to solve this?

Answer 1

> i have got problem related to migration.
Yep.. and this is to be expected. Why? Because Oracle is different than SQL-Server. And it is because of these differences that the market buys Oracle. Not because Oracle is the same as SQL-Server, but because it is difference.
The first thing you need to accept that migration is not going to be easy and painless - because of these differences.
What works and works well in SQL-Server, can spell a performance disaster in Oracle. And vice versa.
Why are temp tables typically used in SQL-Server and Sybase and Ingres and others? Because these databases have a different concurrency and isolation model than Oracle.
In these products, Writers can block Readers and Readers can block Writers.
In Oracle, a Reader will never block a Writer. A Writer will never block a Reader. One Writer will only ever block another Writer when vying for the same row. (and on a very rare occasion, when vying for the same data block that lacks sufficient transaction slots)
Simple example. I open a cursor [SELECT * FROM emp]. I fetch 10 rows of a 100 rows. You start a transaction. You issue a [DELETE FROM emp] and commit. The EMP table is now empty. I fetch the next set of 10 rows using my cursor. What do I see?
I see the next 10 rows as the EMP table looked like at the time I opened my cursor. I still see all 100 rows. Because that was The Truth at the time I opened my cursor. Oracle guarantees me a consistent read. No dirty reads.
So the "tricks" you pulled in SQL-Server to work around the reader and writer blocking issue (a failure of SQL-Server ito providing read consistency), is not applicable in Oracle. And the reasons and methods for using temp tables in SQL-Server is not valid in Oracle.
So when migrating SQL-Server stored proc code to Oracle.. it is a migration. Which means refactoring design and code. Do not expect to be able to simply port the design or code.