This command will show you where your archivelogs are being written to: What you need to do is to run the following commands to find out where your archivelogs are being written to and how much space you have allocated for them to take up. If there is plenty of physical space on the disk or mount that your archivelog files are being written to then you need to connect to the database and check for logical space. I would recommend using rman for either the backup or delete methods as this will keep your catalog of backups up to date and clean.
You can either point your archivelogs to write to a new disk or mount with sufficient space, you can backup your archivelogs and delete input, or you can just delete the archivelogs if you won’t need them to restore your database. If you have run out of physical space you have a few options. The first step to fixing this issue would be to log into your server and see if you have run out of physical space on one of your disks or mounts. When you get this error your database hangs and will not allow anyone besides admin level users to log into the database to perform maintenance to fix the problem.
#ORA 00257 ARCHIVER ERROR CONNECT AS SYSDBA FULL#
Click to download full Oracle Error eBookĪ very common Oracle database error that is basically telling you that you have run out of logical or physical space on the mount, disk, or your db_recovery_file_dest location that holds your archivelogs.
0 kommentar(er)
