Hi NW admins,
May be you know about the functions of the ST14 which is delivered by ST-A/PI which also includes:
- Transaction ST14 (Application monitor)
- Report RTCCTOOL (Servicetools Update)
- Report RSECNOTE (SAP Security Notes Check)
- Transaction ST12 (ABAP trace for EarlyWatch/GoingLive)
- Transaction ST13 (Launchpad for further analysis tools)
- new SDCC datacollectors for BW APO CRM and databases
- collectors for E2E change management
The collection of this data in ST14 is depending on the result of the database collectors. They are present in DB02 => Space => Additional Functions => Collector Logs
For error analysis you can use table DB02_COLL_LOG
Details in 1482296 – DVM Service: analysed data volume incorrect (Oracle)
Report RSORACUP (connection DEFAULT delete/create) to activate all collectors (oracle).
Details in 1002840 – No data or obsolete data in DB Space Statistic monitor
You also have to check if all entries in table TCOLL ae correct. Normally this is checked by report RTCCTOOL but you can double check it with note 12103.
If you have one of the latest versions of ST-A/PI (01R / 01Q SP2) you have to implement some corrections:
2049530 – Data Collectors corrections ST-A/PI 01R*
1936913 – Data Collectors corrections ST-A/PI 01Q SP02
1843959 – ST14 does not show data for BW analyses
Don’t forget after you implemented a new support package for ST/PI or ST-A/PI to uncomment/recomment analysis coding! Therefor use RTCCTOOL=>Addon&Upgrade assistent=> Procedure after addon implemtation..
You can also execute the report /SSF/SAO_UTILS via transaction SA38 and flag the first option ‘Uncomment/Recomment analyis coding for additional components’.
If your ST14 is working and you could collect some results than you my be prefer a other format or you don’t want so much information than you can customize it.
Check the Questions&Answers section in note 69455 – Servicetools for Applications ST-A/PI (ST14, RTCCTOOL, ST12)
Q8: deactivate single ST14 analysis subroutine ?
A8: An ST14 analysis job calls a sequence of analysis subroutines. If one subroutine fails, proceed ad follows: from the short dump get the subroutine name (e.g. AFI_FI_SCAN_T685). Run report /SSA/AXM from SE38. On the selection screen, enter the first 3 letters (e.g. ABW/ABO; check this in your report, the headline in a tree entrie includes the letters) of the subroutine name into parameter P_APPL and execute. In the left section ‘ST14 customizing’ choose ‘Mapping: Assign analy. subroutines to GRPIDs’ and press the button ‘Change’. In the following tablecontrol deselect the ‘Active’ checkbox for analysis subroutine that should be skipped and press ‘Save’.
Then schedule a new analysis from ST14.
With a double click on a row you go into detail view.
The ST14 is pretty good for analyzing BW or SCM systems. To get a quick overview were your space is wasted and what could be optimized.
For me it is the starting point of a deeper analysis, because it is platform and DB independent.
If you have any further questions, don’t hestate to comment the blog or contact me or one of my colleagues at Q-Partners ( info_at_qpcm_dot_de )
Technology Consultant at Q-Partners (www.qpcm.eu)