The “show capture detail” returns a status of “waiting for logfile”
Normally Capture will error out when a log wrap situation is encountered. It is now possible to instruct the Capture to stop altogether or wait for a specified time interval before attempting to restart once it encounters a log wrap. This is done by configuring the Capture parameter SP_OCT_LOGWRAP_RESTART to a value of 0 or a specific time interval expressed in seconds. If it set to 0, then the Capture will remain stopped till the archived logs required by it are restored and the Capture is then restarted manually. If it is set to a specific time interval, then Capture will restart after the elapse of that time interval. It is imperative that the archive logs required by Capture be restored during that time interval or else Capture will keep attempting to read the archive logs, stop if the logs are not restored and then make another attempt to read them and so on.
If you wish to have Capture stop altogether when encountering a log wrap, set the parameter as follows and bounce Capture to have the parameter take effect:
sp_ctrl>set param SP_OCT_LOGWRAP_RESTART 0
sp_ctrl>stop capture
sp_ctrl>start capture
In the event a log wrap occurs after the above setting of Capture, then Capture will be stopped due to error when encountering a log wrap. You can restore the missing archive log(s) and then manually restart Capture.
If you wish to have Capture stop for a designated time interval when encountering a log wrap and then subsequently restart and keep checking for the availability of the missing archive logs, set the parameter as follows and bounce Capture to have the parameter take effect:
sp_ctrl>set param SP_OCT_LOGWRAP_RESTART <n seconds> (where n is an integer)
sp_ctrl>stop capture
sp_ctrl>start capture