List and make sure all the target files are available to move or delete.įor example, we'd like to keep the files newer than 7 days. Sometimes, you might be not able to access RMAN in the first place, to free up the space of archived log destinations manually, you can refer to following steps in order to solve ORA-00257. RMAN> delete archivelog until time 'sysdate - 5/1440' 3. The following command will keep archived logs only 5 minutes. RMAN> delete archivelog until time 'sysdate - 1/24' The following command will keep archived logs only 1 hour. RMAN> delete archivelog until time 'sysdate - 3' The following command will keep archived logs only latest 3 days. That is to say, we keep none of online archived logs. This RMAN command will delete all archived logs without prompting you the confirmation. If you're in an urgent situation, you can delete all archived logs without asking anything. Either local or remote database could cause the error, you should release some space to make the database move. If they are in good conditions, the possible causes could be from the remote database that is connected by local database links for refreshing local materialized views. The first action we should take is to check all the archived log destinations LOG_ARCHIVE_DEST_ n or DB_RECOVERY_FILE_DEST to make sure they have enough space. ![]() A scheduler job which is refreshing materialized views threw an error ORA-00257 in the alert log like this: ORA-12012: error on auto execute of job 78450
0 Comments
Leave a Reply. |