Skip to main content

Search

Welcome to Tibero GTS!

Issue Where Registered JOB Does Not Execute Automatically

Document Type | Troubleshooting

Category | Administration

Applicable Product Version | 6FS07

Document Number | TADTS014

 

Issue

An issue has occurred where registered JOBs do not execute automatically.
If a registered Job does not execute automatically, check the result of the following SQL query.
SELECT COUNT(*) FROM _DD_OBJ WHERE OWNER_ID = 0 AND NAME = '_AGENT_DUMMY';
If the query result count = 0, it indicates that the internal _AGENT_DUMMY table has not been created, and agent threads such as the job scheduler and tpm (tibero performance monitor) collector are not running.
 
 

Cause

This table is an internal table created to prevent agent threads from running during the execution of system.sh (a shell script that creates dynamic performance views inside the DB) after DB installation.
Normally, if system.sh runs successfully, the _AGENT_DUMMY table is recreated after the script execution.
However, this issue occurred because an error happened during a previous system.sh execution, and the table was not created properly.
 
 

Solutions

Execute $TB_HOME/scripts/systbl_create_agent.sql to create the internal table.
SQL> @systbl_create_agent.sql
After recreating the _AGENT_DUMMY table, verify whether the job operates normally.
Note
Run $TB_HOME/scripts/systbl_create_agent.sql to recreate the _AGENT_DUMMY table and verify that the job operates normally.
 
 
 

Related to