Do you have any question about this error?
Message type: E = Error
Message class: RT - Monitoring infrastructure MSG and alert texts
Message number: 690
Message text: Cannot delete old job &1; delete manually
When transferring from the old performance database to the Central
Performance History, new jobs are scheduled, and other jobs that are
no longer required are deleted, among other things. The deletion of the
old jobs is performed automatically when you choose <LS>Technical
Infrastructure -> Central Perf.History -> Background Job</> in
transaction RZ21.
The system could not delete the old jobs.
Delete the following jobs manually:
SAP_CCMS_CEN_DATA_COLL
SAP_CCMS_PERFDB_COLL
SAP_CCMS_PERFDB_REORG
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
RT690
- Cannot delete old job &1; delete manually ?The SAP error message RT690 "Cannot delete old job &1; delete manually" typically occurs when there is an attempt to delete a background job that is either still active, has not been fully processed, or is in a state that prevents it from being deleted automatically by the system.
Cause:
- Job Status: The job may still be in an active or finished state that does not allow for automatic deletion.
- Job Lock: The job might be locked by another process or user, preventing its deletion.
- Job History: The job may have a history or logs that need to be addressed before it can be deleted.
- Authorization Issues: The user attempting to delete the job may not have the necessary authorizations to perform the deletion.
Solution:
- Check Job Status: Use transaction code
SM37
to check the status of the job. If it is still active or in a finished state, you may need to wait until it is fully processed.- Manual Deletion: If the job is confirmed to be in a state that allows for deletion, you can manually delete it using transaction code
SM37
:
- Find the job in the list.
- Select the job and choose the option to delete it.
- Check for Locks: Ensure that there are no locks on the job. You can check for locks using transaction code
SM12
.- Review Authorizations: Ensure that you have the necessary authorizations to delete background jobs. If not, contact your SAP administrator to grant the required permissions.
- Job Logs: If the job has logs or spool requests associated with it, consider reviewing or deleting those first.
Related Information:
SM37
: Monitor background jobs.SM12
: Display and manage locks.SM21
: Check system logs for any related errors.If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
RT689
Cannot start data collection check
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RT688
Initialization is performed in background
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RT691
System &1 not found under the monitored systems
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RT692
No monitored systems found in group &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.