Solution : https://service.sap.com/sap/support/notes/651452 (SAP Service marketplace login required)
Summary :
In SAP transaction DB13, actions highlighted in red signify issues, often caused by missing action logs due to unavailable entries in SDBAH tables, despite correct job ID usage for log retrieval. Newer SAP releases improved error minimization by job ID linkage rather than merely timestamp comparison, mitigating discrepancies arising from time variations across servers. Common errors include execution failures and large time differences between logs and actions, which can be resolved by ensuring synchronized timestamps or refreshing DB13 transactions. For detailed issue resolution, specific system messages, identified via listed diagnostic steps, are necessary to rectify issues.
Key words :
incorrectly imported sapdba role, time-controlled batch scheduler, execute time-controlled actions, global statistical run, time-controlled jobs, big time differences, considerable time differences, update optimizer statistics, longer handled separately, relevant error message
Related Notes :
| 900182 | NW 2004S: No logs displayed in DB12/DB13/DB14 |
| 853610 | Configuring transaction DB13C for Oracle |
| 825191 | Corrections in DB transactions for Oracle (3) |
| 651812 | FAQ: BR*TOOLS and SAPDBA |
| 544881 | Composite SAP note: Time-driven jobs do not run |
| 529548 | DB13: Actions are, incorrectly, displayed as failed |
| 524341 | Updating the statistics for individual partitions |
| 437648 | DB13: External program terminated with exit code 1/2 |
| 412980 | DB13: Some DBA actions are always displayed in red |
| 209900 | DB13: Incorrect status of concatenated backups |
| 134592 | Importing the SAPDBA role (sapdba_role.sql) |