Monitoring the Dispatcher Queue

本文介绍了如何使用SAP系统的内置工具来监控和分析工作进程的状态,包括如何查看工作进程的详细信息,如状态、占用时间等,并提供了针对不同状态的工作进程进行故障排查的方法。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

Dispatcher statistics

Occasionally, it may be useful to analyze the work process dispatcher queue. Statistics on dispatcher activities are available via the server overview at the following path:

TOOLS • ADMINISTRATION • MONITOR • SYSTEM MONITORING • SERVER (Transaction SM51)

Then, mark an SAP instance with the cursor and select Go To • SERVER • INFORMATION • QUEUE INFO.

A list appears, showing information for each work process type on the requests currently waiting, the maximum number of user requests since the SAP instance was started, the maximum possible number of user requests for each queue, and the number of requests read and written.

The information about the dispatcher queue is especially important when the system is not responding because the number of requests in the queue is much larger than the number of work processes. In this situation, the SAP system does not have any more work processes available to perform an analysis. To obtain the queue data, call the auxiliary program dpmon (option P).

Monitoring work processes

You can monitor the actions of SAP work processes by using the TIME, STATUS, REASON, ACTION/REASON FOR WAITING, and TABLE fields in the work process overview. Note the following points:

->Are there sufficient idle (status: WAITING) work processes of each type on each SAP instance?
->Are there programs that use a work process for too long (TIME field)?
    If so, the user should check this program and see if it has any errors.
    A detailed program analysis may also be necessary.
-> Check the STATUS, REASON, ACTION/REASON FOR WAITING and TABLE fields to see whether more than 20% of the work processes are performing the same action. The main problems with this can be one of the following:

 ~If more than 20% of the work processes are in PRIV mode or in the roll-in or roll-out phase, this indicates a problem with SAP memory management.
 ~If more than 40% of work processes are performing a database action, such as SEQUENTIAL READ, COMMIT, etc., this indicates a database problem.
 ~If more than 20% of work processes are reading the same table at the same time, there may be a problem with an expensive SQL statement or exclusive lock waits in the database.

You can call the work process overview at the operating system level with the d pmon program. This is particularly necessary if the performance problem is so massive that no work processes can be used for the analysis.

Procedure Road map for Analyzing SAP Work Processes:

SAP Work Process Overview (Transaction Code SMSO/SM66)

  ? Work Processes with StatusRunning?

      ? Corresponding Actions: Direct Read, Sequential Read, Insert, Update, Delete, Commit

          0 Database Lock Monitor (Transaction Code DB01)

              ? ExclusiveLock Waits?

                 Analyze the Process Holding the Lock.

          0 Database Process Monitor (Transaction ST04, Function Oracle Session)

              Analyze Expensive SOL Statements.

          0 SOL Trace (Transaction Code ST05)

              Analyze Expensive SOL Statements.

   ?Corresponding Actions: Load Report, or semaphore1 ?

        Analyze SAP Program Buffer - Buffer Too Small?

    ? Corresponding Action:Roll-in, Roll-out, or semaphore6?

       Analyze SAP Memory Management- Extended Memory or Roll Buffer Too Small?

   ? Work Processes with Status Stopped? 

       ?Corresponding Reason: PRIV.

          Analyze SAP Memory Management- Extended Memory or Roll Buffer Too Small?

        ? Corresponding Reason: CPIC?

            RFC Destinations(Transaction SM59, Test RFC Destination Function)

            Check for Unavailable or Slow RFC Destinations.

            Work Process Overview(Transaction Code SM50/SM66) in Target System

            Check for Bottlenecks, e. g., Due to All Work Processes in The Target System Being Occupied.

   ? Work Processes with Status Complete?

           Save the Work Process Trace File for Analysis, and Restart the Work Process.




内容概要:本文档定义了一个名为 `xxx_SCustSuplier_info` 的视图,用于整合和展示客户(Customer)和供应商(Supplier)的相关信息。视图通过连接多个表来获取组织单位、客户账户、站点使用、位置、财务代码组合等数据。对于客户部分,视图选择了与账单相关的记录,并提取了账单客户ID、账单站点ID、客户名称、账户名称、站点代码、状态、付款条款等信息;对于供应商部分,视图选择了有效的供应商及其站点信息,包括供应商ID、供应商名称、供应商编号、状态、付款条款、财务代码组合等。视图还通过外连接确保即使某些字段为空也能显示相关信息。 适合人群:熟悉Oracle ERP系统,尤其是应付账款(AP)和应收账款(AR)模块的数据库管理员或开发人员;需要查询和管理客户及供应商信息的业务分析师。 使用场景及目标:① 数据库管理员可以通过此视图快速查询客户和供应商的基本信息,包括账单信息、财务代码组合等;② 开发人员可以利用此视图进行报表开发或数据迁移;③ 业务分析师可以使用此视图进行数据分析,如信用评估、付款周期分析等。 阅读建议:由于该视图涉及多个表的复杂连接,建议读者先熟悉各个表的结构和关系,特别是 `hz_parties`、`hz_cust_accounts`、`ap_suppliers` 等核心表。此外,注意视图中使用的外连接(如 `gl_code_combinations_kfv` 表的连接),这可能会影响查询结果的完整性。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值