Fix more asynchronous RPC semantic implementation errors

Environment

• Version:

Starting seekdb (OceanBase seekdb) source revision 1-4c2c597a011cf7c61df7520df7d61ef2381c02ca.
observer (OceanBase seekdb)

REVISION: 1-4c2c597a011cf7c61df7520df7d61ef2381c02ca
BUILD_BRANCH: master
BUILD_TIME: Jun 12 2026 23:24:36
BUILD_FLAGS: RelWithDebInfo|Sanity
BUILD_INFO: obbuild-sanity-master-101149

• Is this a temporary version provided by RD?: No
• Reproducibility: To be determined (must appear/occasionally/uncertain/other)
• Test Changes: To be determined (This was released after adding xx test scenarios/changing to new machines/newly running xx tools/replacing new versions)
• Other environmental anomalies or changes: To be determined (No/clog disk full/manual done.../xx exception injected)

Description

This issue tracks the need to fix more asynchronous RPC semantic implementation errors.

Steps to Reproduce

Please provide detailed steps. Describe the workload run on the environment, actions taken before the issue occurred, and any test changes. Attach relevant SQL scripts if possible.

Strongly discouraged: Only posting ERROR logs or stack traces without context.

Additional Information

For issues reported by external business teams, please correctly select the "Work Item Type" based on the actual situation:

• Customer Service Feedback: Specifically refers to issues before production deployment or during POC, where a product bug is clearly identified and requires a fix and release.
• Online Issue: Issues that occur after production deployment, clearly identified as product bugs, but not yet classified as a fault.
• Online Fault: Issues that occur after production deployment, clearly identified as product bugs, causing business errors or public impact on the customer side. (The final determination of a fault is at the discretion of the delivery service team.)

The issue names no files, tests, entry points, or reproducible workload. Start by locating the asynchronous RPC implementation in the seekdb source and establish a reproducible semantic failure; done means the identified errors are fixed and the relevant behavior is validated.