Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PLSQL

Status
Not open for further replies.

datamart

IS-IT--Management
Oct 27, 2003
50
0
0
IN
Hi,
I have a front-end application that inserts a record in a table. There is an insert-update trigger on that table(table2) that calls a pl-sql.
there is a piece of select statement in the plsql block.
*********
select col1, col2, col3
into var1, var2, var3
from table1
where cond1
*********
when the application inserts a record in the table(table 2 - not same as the table1), the trigger invokes the plsql and does not not continue beyond the select block mentioned above.
But when I manually, i insert a record into table2, the trigger invokes the plsql and the complete plsql runs successfully.

does anyone have an idea wat cud be the issue.

thanks.
 
Please paste the trigger into this forum. Without looking at the trigger, there is no way to determine the problem.

Bill
Oracle DBA/Developer
New York State, USA
 
I realised that the application updates table2 but defers a commit on it until the entire transaction is complete. In the meanwhile, the plssql tries to select from table2. I verified that the plsql doesnt select anything from table2.

when i insert the record manually in table1, this does not involve table2 in the scenario, hence the process runs successfully.
i guess, i have to find out some way by which the plsql bypasses the read-lock on table2.

any ideas anyone..
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top