Skip to main content

Search

Welcome to Tibero GTS!

Specifying the Node for Job Execution in TAC Environment

Document Type | Technical Information

Category | Administration

Applicable Product Versions | 6FS07, 7FS02

Document Number | TADTI025

 

Overview

In a TAC (Tibero Active Cluster) environment, you can specify that jobs be executed on a particular node depending on the nature of the work or system load. This helps prevent unnecessary resource distribution and optimizes OS resource usage on the operating node, thereby enhancing system stability.
 
 

Method

Syntax

Example usage of the DBMS_JOB.INSTANCE procedure.
DBMS_JOB.INSTANCE
(
job IN BINARY_INTEGER,
instance IN BINARY_INTEGER,
force IN BOOLEAN DEFAULT FALSE
);
  • job: The number of the JOB to execute.
  • instance: The INSTANCE on which the JOB will be executed.
Note
0: Means ANY_INSTANCE
1: Refers to node 1
2: Refers to node 2
  • force: This feature is not supported, so the value is ignored.
 

Example

An example of setting job number 13 to execute on node 2.
SQL> exec DBMS_JOB.INSTANCE (13,2,null);

PSM completed.
-> Sets job number 13 to execute on node 2.


SQL> SELECT * FROM DBA_JOBS WHERE INSTANCE=2;


       JOB SCHEMA_USER
---------- -----------
NEXT_DATE
--------------------------------------------------------------------------------
INTERVAL
--------------------------------------------------------------------------------
BROKEN   FAILURES
------ ----------
WHAT
--------------------------------------------------------------------------------
  INSTANCE
----------
LAST_DATE
--------------------------------------------------------------------------------
THIS_DATE
--------------------------------------------------------------------------------
        13           0
2025/04/30 00:00:00
TRUNC(SYSDATE)+1
N               0
DBMS_JOB.PURGE_LOG(30);
         2
2025/04/29 00:00:00

1 row selected.
 
 
 

Related to