How Robert in this case, Resume this stale pipe?

Robert, A Data Engineer, found that Pipe become stale as it was paused for longer than the limited retention period for event messages received for the pipe (14 days by default) & also the previous pipe owner transfers the ownership of this pipe to Robert role while the pipe was paused.

How Robert in this case, Resume this stale pipe?
A . PIPE needs to recreate in this scenario, as pipe already past 14 days of period & stale.
B . He can apply System function SYSTEM$PIPE_STALE_RESUME with ALTER PIPE statement.
C . Robert can use SYSTEM$PIPE_FORCE_RESUME function to resume this stale pipe.
D . select sys-tem$pipe_force_resume (‘mydb.myschema.stalepipe’,’staleness_check_override, ownership_transfer_check_override’);
E . ALTER PIPES … RESUME statement will resume the pipe.

View Answer

Answer: D

Explanation:

When a pipe is paused, event messages received for the pipe enter a limited retention period. The period is 14 days by default. If a pipe is paused for longer than 14 days, it is considered stale.

To resume a stale pipe, a qualified role must call the SYSTEM$PIPE_FORCE_RESUME function and input the STALENESS_CHECK_OVERRIDE argument. This argument indicates an under-standing that the role is resuming a stale pipe.

For example, resume the stale stalepipe1 pipe in the mydb.myschema database and schema: SELECT SYS-TEM$PIPE_FORCE_RESUME(‘mydb.myschema.stalepipe1′,’staleness_check_override’); While the stale pipe was paused, if ownership of the pipe was transferred to another role, then resuming the pipe requires the additional OWNERSHIP_TRANSFER_CHECK_OVERRIDE argument. For example, resume the stale stalepipe2 pipe in the mydb.myschema database and schema, which transferred to a new role:

SELECT SYS-TEM$PIPE_FORCE_RESUME(‘mydb.myschema.stalepipe1′,’staleness_check_override, own-ership_transfer_check_override’);