This content has been marked as final. Show 4 replies
Did you check MOS notes :
How to Resolve ORA-00257: Archiver is Stuck Error in 10g and higher [ID 278308.1]
backup archivelog all delete input
No database version.
No alert log excerpt.
No code showing how you are "migrating".
I see No way we can help you at this time.
Please post ALL relevant information such that someone can try to replicate the problem.
The message indicates that there are no known archivelogs to delete.
I hope that you ensure that archivelogs are backed up before they are deleted.
Hemant K Chitale
1 person found this helpful
lxiscas wrote:Sounds like you are confusing (online) redo logs with "archivelogs" (archived redo logs).
I need to migrate data from external tables to normal tables. But the connection is always frozen half the way of executing script. The error message is ORA-00257. it looks redo log file is full. I tried to delete redo log file with RMAN, but I got this error message:
You don't delete redo logs at all. You can delete archivelogs with rman, which is what your command is trying to do. Do you ever backup the archivelogs? A proper backup/recovery policy would backup the archivelogs on at least a daily (if not more often) basis, and delete them after they are backed up. That will keep the archivelog destination from filling up in all but the most extreme circumstances.
delete archivelog until time 'trunc(sysdate)';
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=43 device type=DISK
specification does not match any archived log in the repository
Any suggestion would be appreciated.