Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

No cookies to display.

ORA-00257: archiver error

Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
  • User AvatarKiran Dalvi
  • 13 Sep, 2023
  • 0 Comments
  • 45 Secs Read

ORA-00257: archiver error

The ORA-00257 error is a very common Oracle database error. The most likely cause of this message is that the destination device is out of space to store the redo log file.

Choose one of the following actions to resolve the problem:

  1. Add more space to the mount where the logs are going.
  2. Take a backup of the logs via RMAN and have it delete input.  Please Note , If your backups are going to the same destination your archive logs are going, you  need to take a backup on a different mount point.
  3. Delete the archive logs if it is not required to restore the database.
  4. Move the archivelog location to another mount/drive/location temporarily while you do one of the above.
  5. increase the db_recovery_file_dest_size to a larger size that will allow for more archivelogs to be written to the archivelog location.

 

Hope it Helps!