Oracle ' s package,function,proceture is not responding at compile time (resolution)

When you debug a procedure, function, or package, the company's firewall kills the session connection if there is no action for a long time. This time the database does not actively release the resources of the session, if the procedure, function or package debug again, it will produce a wait. Because the firewall killed by the session is still running the last debug, there will be a lock. Only wait until the database reclaims the last debug session resource or the DBA manually kill the session. Here's how to Manually kill sessions:

1, get all the information of the session

1. Select * from V$session B where B.schemaname <> ' SYS '

PS: After executing the statement there will be an action field (sessionname) and osuser (user)

You can see the session under your own user.

2. Kill the session

2. ALTER SYSTEM KILL SESSION ' sid,serial# ' IMMEDIATE;

PS: The SID and serial#==== here can be found in the first section

And then you can do it.

Oracle ' s package,function,proceture is not responding at compile time (resolution)