Cause: The log sequence number supplied in the ARCHIVE statement does not match any of the online logs for the thread. This can result from any of the following situations:
The log might have been reused for another sequence number.
The log might have been dropped.
The sequence number might be greater than the current log sequence number.
The thread might not have any logs.
Action: Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number.
Solution doesn't works for you?
POST your error in our discussion panel below.
Our DBA team will be happy to help you :)