The RUN_INSPECTION procedure manually triggers a Root Service inspection for the current tenant to verify the consistency of internal metadata. The inspection checks the following information:
- The integrity of system statistics (sys_stat)
- The integrity of system parameters (sys_param)
- The consistency of system table schemas
- The correctness of data version (data_version)
Limitations and considerations
Both system tenants and user tenants can trigger a Root Service inspection for the current tenant.
Syntax
DBMS_SCHEMA.RUN_INSPECTION();
Considerations
The system has a scheduled task named SCHEDULED_RUN_INSPECTION that periodically triggers Root Service inspections. The default interval is 1500 seconds. You can use the repeat_interval attribute of the DBMS_SCHEDULER.SET_ATTRIBUTE procedure to modify the interval. For example, to change the interval of the SCHEDULED_RUN_INSPECTION task to 30 minutes:
obclient(root@mysql001)[(none)]> CALL DBMS_SCHEDULER.SET_ATTRIBUTE('SCHEDULED_RUN_INSPECTION', 'repeat_interval', 'FREQ=SECONDLY; INTERVAL=1800');
If the scheduled task has not yet reached its execution time, you can manually call the DBMS_SCHEMA.RUN_INSPECTION() procedure to quickly trigger a Root Service inspection.
Examples
A user tenant triggers a Root Service inspection for the current tenant.
obclient(root@mysql001)[(none)]> CALL DBMS_SCHEMA.RUN_INSPECTION();
