Hi,
The notes shown below are critical for troubleshooting and analyzing general BWA issues. All of them are a combination of very useful notes with detailed screenshots.
- Troubleshooting BWA index server crashes:
SAP Note:1872501 - BWA Troubleshooting: TREXIndexServer crash in BWA
Highlighted points:
1. Verify whether the TREXIndexServer process has crashed and was restarted.
a. Check the BWA alerts in transaction RSDDBIAMON2
b. Check runtime of BWA processes
c. Check the trace files
2. Perform Root cause analysis of the crash.
a. Analyze the BWA system load
b. Analyze existing core files.
3. Crash Analysis using Python trace.
- Troubleshooting BWA High Memory issues:
SAP Note:1872296 - BWA Troubleshooting: High Memory Consumption
Highlighted points:
1. Check which service causes the huge memory consumption.
2. Check for long running threads.
3. Check the ratio of disk usage to main memory.
4. Verify the landscape reorganization algorithm.
5. Check for alerts in RSDDBIAMON2/TREXAdmin tool.
a. bia_indexes_size_perf_check/check_too_many_parts
b. detect_core_files
c. reorg
d. unloads
6. Check operations in BWA
7. Check the trace file.
8. Check memory relevant parameters of TREXIndexServer.ini
9. Search for known issues for your BWA revision
- Troubleshooting: BWA Indexing Errors
SAP Note: 1872295 - BWA Troubleshooting: BWA Indexing Errors
Highlighted points:
1. Check the hardware configuration, including the I/O for each blade and the network settings between BW and BWA
2. Investigate the job Logs
3. Check the application log – transaction RSDDB / alternatively SLG1
4. Check if a service was recently started in Services -> Services
5. Check if there is a high load and if this is balanced on all blades or it only happens on a specific blade
6. Trace files Analysis
7. Check the core files
8. Check the Python Trace
9. Check the var/log/ messages
- Troubleshooting: BWA Indexing Performance
SAP Note:1871790 - BWA Troubleshooting: Analyzing Indexing Performance
Highlighted points:
1. Check the BWA Alert Monitor.
2. Check the BW logs -> SM37 job log, SM21 system log, and the SLG1 application log
3. Check the Indexing settings in the BWA Monitor using RSDDBIAMON2
4. Run a BWA Check (System Check) from within RSDDBIAMON2
5. Maintain indexing statistics data in table RSDDSTATTREX and RSDDSTATTREXSERV
6. Ensure DB statistics for underlying tables and indexes are up to date
7. Check the BWA TREXAdmin tool for the load on BWA during indexing
8. Check the BWA TREXAdmin tool IndexServer trace file for any relevant error information about the process
9. Check the BWA TREXAdmin tool TREXIndexserver.ini file parameter settings
10. Extra information
- Troubleshooting: BWA Query Performance
SAP Note:1871604 - BWA Troubleshooting: Analyse Poor Query performance
Highlighted points:
1. Check whether the query uses BWA or not
2. Check where most of the runtime is spent
3. Check for any errors using the checkBIA.py python script
4. Check if a reorg is proposed by BWA
5. Check for partitioning of a huge F-Index
6. Review BWA Statistics index
7. Review the Alert server for any errors/warnings
8. Execute a Performance trace
9. Execute Python Trace
- Troubleshooting: BWA Hardware or Network Issues
SAP Note:1870916 - BWA Troubleshooting: Hardware or Network Issues
Highlighted points:
1. Check the hardware availability.
2. Validate the all services are up and running.
3. Analyze the relevant operating system logs.
4. Check the write performance to the disk.
5. Check the network performance.
6. Check that network connection between the BWA blades and the BW application servers
7. Use the traceroute command to check the network route.
- Troubleshooting: BWA Rollup/Change Run Issues
SAP Note: 1791621 - BWA Troubleshooting: Rollup/Change Run Issues
Highlighted points:
1. Parallel issues
2. Performance issues
3. Lock issues
Thanks,
Diego Seben.
SAP Active Global Support