How To Fix PO397 - Device cache reset as a long host name changed

SAP Error Message - Details

• Message type: E = Error

• Message class: PO - Spooler message

• Message number: 397

• Message text: Device cache reset as a long host name changed

What causes this issue?

You have maintained a long host name for a destination host in
transaction SPAD. This change is activated for all devices that use
this destination host.

System Response

All devices that use this destination host must be updated in the cache
in order to take the new assignment into account.

How to fix this error?

No action necessary.

Procedure for System Administrators

A message is automatically sent to every application server to tell
them to reset the device cache.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PO397 - Device cache reset as a long host name changed ?

  The SAP error message "PO397 Device cache reset as a long host name changed" typically occurs in the context of SAP printing and device management. This error indicates that the device cache has been reset due to a change in the hostname of the server or system where the SAP application is running. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Hostname Change: The error is triggered when the hostname of the SAP application server changes, and the system detects that the device cache (which stores printer and device configurations) is no longer valid.
  Network Configuration Changes: Changes in network settings, such as DNS updates or changes in the server's IP address, can also lead to this error.
  Long Hostname: The term "long hostname" suggests that the new hostname exceeds the character limit or is not recognized properly by the SAP system.
  
  Solution:
  
  
  Reset Device Cache:
  
  You can manually reset the device cache in SAP. This can be done by navigating to the transaction code SPAD (Spool Administration) and clearing the device cache.
  After clearing the cache, restart the SAP application server to ensure that the changes take effect.
  
  
  
  Check Hostname Configuration:
  
  Verify the hostname configuration in the SAP system. Ensure that the hostname is correctly set and does not exceed the character limit.
  You can check the hostname settings in the transaction code RZ10 (Profile Maintenance) or RZ11 (Profile Parameter Maintenance).
  
  
  
  Update Printer Settings:
  
  If you are using specific printers, ensure that the printer settings in SAP are updated to reflect any changes in the hostname.
  You may need to reconfigure the printers in the SPAD transaction.
  
  
  
  Network Configuration:
  
  Ensure that the network configuration is correct and that the DNS settings are properly pointing to the new hostname.
  If applicable, update any relevant entries in the /etc/hosts file on the server.
  
  
  
  Check SAP Notes:
  
  Look for any relevant SAP Notes that may address this specific error. SAP frequently updates its knowledge base with solutions for known issues.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SPAD: Spool Administration
  RZ10: Profile Maintenance
  RZ11: Profile Parameter Maintenance
  
  
  SAP Documentation: Refer to the official SAP Help Portal for documentation on spool administration and printer configuration.
  SAP Community: Engage with the SAP Community forums for discussions and solutions related to 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.