Performance Issues in the MSSQL Database
If CrystalBridge® Analysis Extractor is executed on an MSSQL database, the first step often takes up 50% of the total process runtime. This is the step where the scan retrieves the information from the database statistics. This might be because an SAP® standard storage procedure in the MSSQL database has not been updated with a performance improvement implemented by SAP®.
The first step of Analysis Extractor is to collect information from the database statistics. For this purpose, the SAP® standard service MSS_GET_TABLE_SIZE_INFO is executed. Finally, the default storage sap_get_table_size_info is created. This storage process must be optimized to avoid performance issues. For information on reducing performance issues, see the following link.
Importing System Usage Statistics from Other Systems
The CrystalBridge® Analysis Extractor can transfer system usage information extracted from the production system to a scanned non-production system.
The impact analysis for example determines how often certain ABAP reports, transactions and remote function calls have been used in the past few months. This data is also known as ST03N data and is extracted using the CrystalBridge® Analysis Extractor. Therefore, it is necessary to perform the scan in the production system.
If the CrystalBridge® Analysis Extractor is executed in a system that has been copied from the production system to perform the analysis, it is possible that the ST03N data cannot be copied. System usage information is lost in the process.
In this case, we recommend using an SAP® standard function to make the information available in the scanned non-production system. For more information, refer to the following link SAP® Note 2568736. This SAP® Note contains a simple report to transfer the ST03N data to the scanned system as an XML file after the export from the production system.
Size of the Temporary Segment PSAPTEMP in the Oracle Database
The temporary segment in the tablespace PSAPTEMP must be large enough to execute extensive queries with aggregated functions as well as queries on cluster tables. If the maximum allowed size for the temporary table is exceeded, the corresponding queries are canceled.
In Oracle, this error can occur when a temporary table is to be created in a tablespace that does not have enough storage space, or when the storage limit of the temporary table is exceeded.
