How To Fix FG908 - Old archive files and data base are unchanged

SAP Error Message - Details

• Message type: E = Error

• Message class: FG - Program Error Messages

• Message number: 908

• Message text: Old archive files and data base are unchanged

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FG908 - Old archive files and data base are unchanged ?

  The SAP error message FG908 ("Old archive files and database are unchanged") typically occurs during the archiving process when the system detects that the archive files being processed have not changed since the last time they were accessed. This can happen for several reasons, and understanding the cause is essential for resolving the issue.
  Causes:
  
  No New Data to Archive: The most common reason for this error is that there are no new records that meet the archiving criteria since the last archiving run.
  Incorrect Archiving Object Configuration: The archiving object may not be configured correctly, leading to the system not recognizing any new data.
  File System Issues: There may be issues with the file system where the archive files are stored, preventing the system from accessing or recognizing changes.
  Database Locking: If the database is locked or if there are transactions that are preventing changes from being committed, this error may occur.
  Archiving Process Not Completed: If the previous archiving process did not complete successfully, it may lead to inconsistencies that trigger this error.
  
  Solutions:
  
  Check Archiving Logs: Review the archiving logs to see if there are any warnings or errors that provide more context about the issue.
  Verify Archiving Object Settings: Ensure that the archiving object is correctly configured and that the selection criteria for archiving are appropriate.
  Run Archiving Program Again: If you suspect that there are new records to archive, try running the archiving program again.
  Check for Database Locks: Use transaction codes like SM12 to check for any locks on the database that might be preventing changes.
  File System Check: Ensure that the file system where the archive files are stored is accessible and functioning correctly.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: You may find it useful to use transaction codes such as SARA (Archive Administration) to manage archiving processes and check the status of archiving objects.
  SAP Documentation: Refer to the official SAP documentation for detailed information on archiving processes and best practices.
  SAP Community: Engaging with the SAP Community can provide insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.