Senior Consultant

Cursors defined in procedures will have a local scope, which means they can't be used by other procedures.
Cursors defined in package specifications have global scope, which means that they can be utilised and accessed by other methods.

It's used to describe all of the dependencies that the current user has between procedures, packages, triggers, and functions. Name, dependency type, type, referenced owner, and other columns are returned.

A PL/SQL cursor is simply a pointer to a memory location containing SQL statements and statement processing metadata. A context area is the name given to this memory space. For obtaining and processing more than one row, this unique region takes use of a specific feature called cursor.
There are two types of cursor : Implicit Cursor and Explicit Cursor

In PL/SQL, a trigger is a stored procedure that specifies what action has to be taken by the database when an event related to the database is performed.
Syntax:
TRIGGER trigger_name
trigger_event
[ restrictions ]
BEGIN
actions_of_trigger;
END;

1. By issuing a procedure call statement from another block, a stored procedure is run explicitly. When a triggering INSERT, UPDATE, or DELETE statement is issued on the associated table, Oracle implicitly fires (executes) triggers, regardless of which user is connected or which application is being utilized.
2. SQL and PL/SQL statements, as well as stored procedures, can be included in a trigger. Stored procedures, on the other hand, do not invoke triggers directly. DML statements that can trigger triggers are included in stored procedures.
3. Triggers are not parameterized, whereas procedures can contain parameters.

Rowid is a permanent unique identifier for that row, whereas rownum is a temporary unique identifier for that row. The rownum, on the other hand, is only transitory. The rownum number will relate to another row if you update your query, but the rowid will not.
As a result, ROWNUM is a sequential number that only applies to a single SQL transaction. The ROWID, on the other hand, is a unique ID for a row.

Tip 1 : The cross questioning can go intense some time, think before you speak.
Tip 2 : Be open minded and answer whatever you are thinking, in these rounds I feel it is important to have opinion.
Tip 3 : Context of questions can be switched, pay attention to the details. It is okay to ask questions in these round, like what are the projects currently the company is investing, which team you are mentoring. How all is the work environment etc.
Tip 4 : Since everybody in the interview panel is from tech background, here too you can expect some technical questions. No coding in most of the cases but some discussions over the design can surely happen.