After the scheduled partition balancing job is triggered, you can query views for the scheduling history of the job.
Query the scheduling history of the scheduled partition balancing job from the sys tenant
Log in to the
systenant of the cluster as therootuser.Note that you must specify the corresponding parameters in the following sample code based on your actual database configurations.
obclient -h10.xx.xx.xx -P2883 -uroot@sys#obdemo -p***** -AExecute the following statement to query the scheduling history of the scheduled partition balancing job in a specified tenant.
The
CDB_SCHEDULER_JOB_RUN_DETAILSview displays the execution records of the scheduled partition balancing job namedSCHEDULED_TRIGGER_PARTITION_BALANCEin all tenants.obclient [oceanbase]> SELECT * FROM oceanbase.CDB_SCHEDULER_JOB_RUN_DETAILS WHERE TENANT_ID = 1002 AND JOB_NAME = 'SCHEDULED_TRIGGER_PARTITION_BALANCE'\GThe following result is returned:
*************************** 1. row *************************** LOG_ID: 0 LOG_DATE: NULL OWNER: NULL JOB_NAME: SCHEDULED_TRIGGER_PARTITION_BALANCE JOB_SUBNAME: NULL STATUS: NULL CODE: -7124 REQ_START_DATE: NULL ACTUAL_START_DATE: NULL RUN_DURATION: NULL INSTANCE_ID: NULL SESSION_ID: NULL SLAVE_PID: NULL CPU_USED: NULL CREDENTIAL_OWNER: NULL CREDENTIAL_NAME: NULL DESTINATION_OWNER: NULL DESTINATION: NULL MESSAGE: partitions are already balanced, no need to trigger partition balance TENANT_ID: 1002 JOB: 11 TIME: 2024-06-14 00:00:00.124110 JOB_CLASS: DEFAULT_JOB_CLASS GMT_CREATE: 2024-06-14 00:00:00.124110 GMT_MODIFIED: 2024-06-14 00:00:00.124110 *************************** 2. row *************************** LOG_ID: 0 LOG_DATE: NULL OWNER: NULL JOB_NAME: SCHEDULED_TRIGGER_PARTITION_BALANCE JOB_SUBNAME: NULL STATUS: NULL CODE: 0 REQ_START_DATE: NULL ACTUAL_START_DATE: NULL RUN_DURATION: NULL INSTANCE_ID: NULL SESSION_ID: NULL SLAVE_PID: NULL CPU_USED: NULL CREDENTIAL_OWNER: NULL CREDENTIAL_NAME: NULL DESTINATION_OWNER: NULL DESTINATION: NULL MESSAGE: SUCCESS TENANT_ID: 1002 JOB: 11 TIME: 2024-06-14 17:00:00.143494 JOB_CLASS: DEFAULT_JOB_CLASS GMT_CREATE: 2024-06-14 17:00:00.143494 GMT_MODIFIED: 2024-06-14 17:00:00.143494 2 rows in setFor more information about the fields in the
CDB_SCHEDULER_JOB_RUN_DETAILSview, see CDB_SCHEDULER_JOB_RUN_DETAILS.
Query the scheduling history of the scheduled partition balancing job from a user tenant
Log in to a MySQL or Oracle tenant of the cluster as the administrator of the user tenant.
Note that you must specify the corresponding parameters in the following sample code based on your actual database configurations.
obclient -h10.xx.xx.xx -P2883 -uroot@mysql_tenant#obdemo -p***** -AExecute the following statement to query the scheduling history of the scheduled partition balancing job in the current tenant.
The
DBA_SCHEDULER_JOB_RUN_DETAILSview displays the execution records of the scheduled partition balancing job namedSCHEDULED_TRIGGER_PARTITION_BALANCEof the current tenant.MySQL modeOracle modeExecute the following statement:
obclient [oceanbase]> SELECT * FROM oceanbase.DBA_SCHEDULER_JOB_RUN_DETAILS WHERE JOB_NAME = 'SCHEDULED_TRIGGER_PARTITION_BALANCE'\GExecute the following statement:
obclient [SYS]> SELECT * FROM SYS.DBA_SCHEDULER_JOB_RUN_DETAILS WHERE JOB_NAME = 'SCHEDULED_TRIGGER_PARTITION_BALANCE'\GA sample query result is as follows:
*************************** 1. row *************************** LOG_ID: 0 LOG_DATE: NULL OWNER: NULL JOB_NAME: SCHEDULED_TRIGGER_PARTITION_BALANCE JOB_SUBNAME: NULL STATUS: NULL CODE: -7124 REQ_START_DATE: NULL ACTUAL_START_DATE: NULL RUN_DURATION: NULL INSTANCE_ID: NULL SESSION_ID: NULL SLAVE_PID: NULL CPU_USED: NULL CREDENTIAL_OWNER: NULL CREDENTIAL_NAME: NULL DESTINATION_OWNER: NULL DESTINATION: NULL MESSAGE: partitions are already balanced, no need to trigger partition balance JOB: 11 TIME: 2024-06-14 00:00:00.124110 JOB_CLASS: DEFAULT_JOB_CLASS GMT_CREATE: 2024-06-14 00:00:00.124110 GMT_MODIFIED: 2024-06-14 00:00:00.124110 *************************** 2. row *************************** LOG_ID: 0 LOG_DATE: NULL OWNER: NULL JOB_NAME: SCHEDULED_TRIGGER_PARTITION_BALANCE JOB_SUBNAME: NULL STATUS: NULL CODE: 0 REQ_START_DATE: NULL ACTUAL_START_DATE: NULL RUN_DURATION: NULL INSTANCE_ID: NULL SESSION_ID: NULL SLAVE_PID: NULL CPU_USED: NULL CREDENTIAL_OWNER: NULL CREDENTIAL_NAME: NULL DESTINATION_OWNER: NULL DESTINATION: NULL MESSAGE: SUCCESS JOB: 11 TIME: 2024-06-14 17:00:00.143494 JOB_CLASS: DEFAULT_JOB_CLASS GMT_CREATE: 2024-06-14 17:00:00.143494 GMT_MODIFIED: 2024-06-14 17:00:00.143494 2 rows in setFor more information about the fields in the
DBA_SCHEDULER_JOB_RUN_DETAILSview, see DBA_SCHEDULER_JOB_RUN_DETAILS.