VOOZH about

URL: https://www.ibm.com/support/pages/node/6836981

⇱ Troubleshooting Db2 Mirror jobs

Troubleshooting Db2 Mirror jobs

News


Abstract

Table describing the system and user jobs for Db2 Mirror. You can use this table as a reference to find out how Db2 Mirror jobs, job descriptions, and subsystems are mapped to one another.

Content

Db2 Mirror jobs
 

The status of the jobs running to support the Db2 Mirror environment can be displayed in the Db2 Mirror GUI by selecting Db2 Mirror Jobs from the left navigation setup menu, as shown in the following figure.

👁 Selecting Db2 Mirror Jobs from setup menu

The default view lists the jobs and their general purpose on the primary node. The jobs are listed as either Core Jobs, which are Db2 Mirror system jobs that primarily handle the Db2 Mirror infrastructure or Helper Jobs that are Db2 Mirror user jobs that primarily help the various forms of replication. The tabs at the top of the panel can be used to change which node is displayed.

👁 Displaying Db2 Mirror jobs for primary node

You can use the following tables as a reference to locate a various information related to Db2 Mirror jobs. Additional information about Db2 Mirror jobs can also be found in the IBM Documentation located here.

The first table shows details about Db2 Mirror system jobs. The second table shows details for Db2 Mirror user jobs.

The first column in each table provides the following detailed information about the job:

  • A descriptive name used to identify the job.
  • A short description of the job's purpose and the function it performs. 
  • Job start:  The method that is used to start the job. Most jobs start automatically, such as when a certain subsystem starts or when Db2 Mirror is actively replicating or when replication is being resumed.
  • Job end:  The method that is used to end the job. Most jobs end automatically, such as when the job completes its task or when Db2 Mirror is suspended or terminated. Other jobs end only when a certain subsystem ends.
  • Server type:  The server type is a 30 byte character string that uniquely identifies a server job to the operating system. Most IBM-supplied servers have their server type begin with QIBM_. The server type is set by the server job by using the Change Job API.

    Use the following SQL to display all Db2 Mirror jobs and list the type of server represented by each job: 
    SELECT JOB_NAME, SERVER_TYPE 
 FROM TABLE(QSYS2.JOB_INFO(JOB_STATUS_FILTER => '*ACTIVE',
 JOB_USER_FILTER => '*ALL')) X
 WHERE SUBSTRING(JOB_NAME_SHORT, 1, 4) = 'QDBM' OR 
 SUBSTRING(JOB_NAME_SHORT, 1, 5) IN ('QMPFS', 'QMRDB', 'QOBJC', 'QSPMR')
 ORDER BY JOB_NAME_SHORT, JOB_NUMBER;

The subsequent columns provide the following information:

  • Job name:  The name of the job.
  • Job type:  The job type and job subtype values.
  • Job description:  The name and library of the job description that is used by the job. For example, QSYS/QDBMSRVR indicates library QSYS and job description QDBMSRVR.
  • Subsystem:  The name of the subsystem where the job runs.
  • Default port:  The port from which the job listens for requests.
Db2 Mirror system jobs
 

These jobs exist whenever Db2 Mirror is active or suspended. The jobs generally end when Db2 Mirror is terminated or suspended for maintenance. These jobs run under the QSYS user profile.

Job details Job name Default port
Db2 Mirror IFS infrastructure job
 

Handles infrastructure and support for the Role Mutable File System (MFS) for Db2 Mirror across both nodes.

  • Job start:

    Starts automatically whenever the Network Redundancy Group (NRG) used for accessing the integrated file system (IFS) data is active.

  • Job end:

    Ends only when the system is ended.

 QMPFS1 RDMA port 940
Db2 Mirror engine controller job
 

Handles changes to replication state for Db2 Mirror across both nodes.

  • Job start:

    Starts automatically whenever Db2 Mirror is active or suspended.

  • Job end:

    Ends automatically when Db2 Mirror is terminated or suspended for maintenance.

 QMRDBECTLR RDMA port 930
Db2 Mirror health monitor job
 

Continously monitors for any issues that might arise relating to the Db2 Mirror environment and act when an issue is detected.

  • Job start:

    Starts automatically whenever Db2 Mirror is active or suspended.

  • Job end:

    Ends automatically when Db2 Mirror is terminated or suspended for maintenance.

 QMRDBHLTHM RDMA port 933
Db2 Mirror flight recorder job
 

Handles events directed at the Db2 Mirror flight recorder and writes any entries into the flight recorder database file.

  • Job start:

    Starts automatically whenever Db2 Mirror is active or suspended. The SET_MIRROR_FLIGHT_RECORDER_INFO SQL procedure can also be used to manually start the flight recorder job.

     CALL SET_MIRROR_FLIGHT_RECORDER_INFO(ACTION=>'STARTJOB');
  • Job end:

    Ends automatically when Db2 Mirror is terminated, suspended for maintenance, or the SET_MIRROR_FLIGHT_RECORDER_INFO SQL procedure is used to end the flight recorder job.

     CALL SET_MIRROR_FLIGHT_RECORDER_INFO(ACTION=>'ENDJOB');
 QMRDBLOGR No port is used
Db2 Mirror object replication manager job
 

Manages Db2 Mirror receiver jobs for nondatabase object replication.

  • Job start:

    Starts automatically whenever Db2 Mirror is active or suspended.

  • Job end:

    Ends automatically when Db2 Mirror is terminated or suspended for maintenance.

 QMRDBORM RDMA port 931


Back to top

Db2 Mirror user jobs
 

These jobs are typically active when Db2 Mirror is active or resuming. These jobs typically end or recycle themselves for the cases specified. Users should generally not attempt to end these jobs except at the direction of IBM service.

More troubleshooting tips for server jobs can be found here:  TCP/IP troubleshooting tips.

NOTE:  A horizontal scroll bar maybe present at the bottom of the table if the screen is too small to display the full content.

Job details Job name Job type Job description Subsystem Default port
Db2 Mirror database listener job
 

Listens for Db2 Mirror connect requests and gives the descriptor to a QDBMSRVR prestart job to handle the database request from the source node.

  • Job start:

    Starts automatically whenever Db2 Mirror is active or suspended.

  • Job end:

    Ends automatically when Db2 Mirror is terminated or suspended for maintenance.

  • Server type:

    QIBM_OS400_DBM_SVR_DDM_DRDA

 QDBMLSTN Batch job QGPL/QDFTSVR QSYSWRK RDMA port 946
Db2 Mirror database object replication jobs
 

Handles active replication of database objects on the target node. Additional information can be found here: QDBMSRVR jobs.

  • Job start:

    Automatically started by the system when the QUSRWRK subsystem starts or for the first database replication-eligible action handled by the target node. Can also be started by starting the prestart jobs by using the following CL command:

     STRPJ SBS(QUSRWRK) PGM(QDBMSRVR)
  • Job end:

    Automatically ended or recycled to a prestart wait (PSRW) job status when the activation group or source node job that initiated the database replication-eligible action ends. Can also be ended by ending the prestart jobs by using the following CL command:

     ENDPJ SBS(QUSRWRK) PGM(QDBMSRVR)
  • Server type:

    QIBM_OS400_DBM_SVR_DDM_DRDA

 QDBMSRVR Prestart Batch job QSYS/QDBMSRVR QUSRWRK or configurable RDMA port 946
Db2 Mirror exit program jobs
 

Handles calling exit programs that use the QUSER user profile for important changes detected with Db2 Mirror exit points. Additional information can be found here: Monitoring by using exit points.

  • Job start:

    Starts automatically whenever a program needs to be called for a Db2 Mirror exit point.

  • Job end:

    Ends automatically after the program called for the Db2 Mirror exit point is completed.

  • Server type:

    Not applicable

 QMRDBEEXIT Batch job QSYS/QMRDBEEXIT QSYSWRK No port is used
Db2 Mirror internal resynchronization job
 

Handles the resynchronization processing that occurs in the background when Db2 Mirror replication is suspended and limited internal Db2 Mirror communication between the nodes is available.

  • Job start:

    Starts automatically whenever Db2 Mirror replication is suspended and limited internal Db2 Mirror communication between the nodes is available.

  • Job end:

    Ends automatically after internal resynchronization is completed.

  • Server type:

    Not applicable

 QMRDBESLTD Batch job QSYS/QMRDBESYNC QSYSWRK No port is used
Db2 Mirror resynchronization jobs
 

Handles the resynchronization processing that occurs in the background when Db2 Mirror replication is resumed.

  • Job start:

    Starts automatically whenever Db2 Mirror replication is resumed. The job is initially started on the primary node with a subsequent job started on the secondary node to complete the resynchronization.

  • Job end:

    Ends automatically after resynchronization is completed.

  • Server type:

    Not applicable

 QMRDBESYNC or
QMRDBES<IASP‑number> for database IASPs		 Batch job QSYS/QMRDBESYNC QSYSWRK No port is used
IFS Object Synchronization jobs for IBM i Migrate While Active
 

Handles resynchronization for tracked integrated file system objects. The resynchronization processing will save and restore the object from the source node to the copy node.

  • Job start:

    Starts automatically whenever a SYNCHRONIZE action is received by the Migration Manager.

  • Job end:

    Ends automatically after synchronization is completed or Data Synchronization is PAUSED.

  • Server type:

    Not applicable

 QMRDBISYNC Batch job QSYS/QMRDBESYNC QSYSWRK No port is used
Object Restore Synchronization jobs for IBM i Migrate While Active
 

Handles resynchronization for tracked Non-Db2 Mirror replication eligible objects residing within libraries. The resynchronization processing will save and restore the object from the source node to the copy node.

  • Job start:

    Starts automatically whenever a SYNCHRONIZE action is received by the Migration Manager.

  • Job end:

    Ends automatically after synchronization is completed or Data Synchronization is PAUSED.

  • Server type:

    Not applicable

 QMRDBNSYNC Batch job QSYS/QMRDBESYNC QSYSWRK No port is used
Submitted Job Tracker job
 

Handles events and processes notifications from job notification exit points. Additional information can be found here:  Submitted Job Tracker.

  • Job start:

    Starts with a QSYSWRK subsystem autostart entry. Can also be started by calling a program by using the following CL command:

     CALL PGM(QSYS/QMRDBJNFYS)
  • Job end:

    Ends when the QSYSWRK subsystem is ended.

  • Server type:

    Not applicable

  • NOTE:

    Submitted Job Tracker is a work management feature of the IBM i operating system and can be used without Db2 Mirror.

 QMRDBJNFY Autostart job QSYS/QMRDBJNFY QSYSWRK No port is used
Db2 Mirror receiver jobs
 

Handles active replication for nondatabase objects on the target node.

  • Job start:

    Starts automatically whenever Db2 Mirror is active.

  • Job end:

    Ends automatically whenever mirroring is terminated or suspended.

  • Server type:

    QIBM_MRDB_ORVCR

 QMRDBORCVR Batch job QSYS/QMRDBORCVR QSYSWRK RDMA port 932
ObjectConnect for Db2 Mirror receiver job
 

Handles ObjectConnect for Db2 Mirror operations request to copy an object that is not replicated by Db2 Mirror. Gives requests to copy the object to a QOBJCMRSVR job to handle the requested operation from the source node. Additional information can be found here:  ObjectConnect for Db2 Mirror.

  • Job start:

    Starts automatically whenever the Network Redundancy Group (NRG) for System Object Replication is active and the AUTO_START configuration parameter is set to YES.

    The CHANGE_MIRROR_OBJECTCONNECT SQL procedure can also be used to manually start the server:

     CALL CHANGE_MIRROR_OBJECTCONNECT(STATE=>'START');
  • Job end:

    Ends automatically whenever the Network Redundancy Group (NRG) for System Object Replication becomes inactive or the SQL procedure CHANGE_MIRROR_OBJECTCONNECT is used to end the server:

     CALL CHANGE_MIRROR_OBJECTCONNECT(STATE=>'END');
  • Server type:

    QIBM_SVR_OBJCDB2

 QOBJCMRRCV Batch job QUSRSYS/QOBJCRCV QUSRWRK RDMA port 950
ObjectConnect for Db2 Mirror server jobs
 

Handles any ObjectConnect for Db2 Mirror operations to copy objects from the source node to the target node.

  • Job start:

    Starts automatically whenever the ObjectConnect for Db2 Mirror receiver job is started.

    The number of server jobs to start can be specified by setting the MINIMUM_JOBS configuration parameter on the SQL procedure CHANGE_MIRROR_OBJECTCONNECT:

     CALL CHANGE_MIRROR_OBJECTCONNECT(MINIMUM_JOBS=>5);
  • Job end:

    Ends automatically after the ObjectConnect operation is completed or the Network Redundancy Group (NRG) used for System Object Replication becomes inactive.

  • Server type:

    QIBM_SVR_OBJCDB2

 QOBJCMRSVR Batch Immediate job QUSRSYS/QOBJCRCV QUSRWRK No port is used
Db2 Mirror spool file replication job
 

Handles replication of newly closed spooled files eligible for replication from the object tracking list to the target node on a predetermined spooled file resynchronization interval. Additional information can be found here:  Spooled file resynchronization interval.

  • Job start:

    Starts with a QSYSWRK subsystem autostart entry. Can also be started by using the CL command to resubmit the job by using the QSPMRSYNC job description and specifying the QSPMRSYNC job name:

     SBMJOB JOB(<job-name>) JOBD(QSPMRSYNC)
 USER(*JOBD) RTGDTA(*JOBD)

    For database IASPs, use QSPMR00<IASP-number> as the job name.

  • Job end:

    Ends when the QSYSWRK subsystem is ended or Db2 Mirror is terminated.

  • Server type:

    Not applicable

 QSPMRSYNC or
QSPMR00<IASP‑number> for database IASPs		 Autostart job QSYS/QSPMRSYNC QSYSWRK No port is used


Back to top

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000001hExAAI","label":"DB2 Mirror"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.4.0;and future releases"},{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SSLLPF","label":"IBM Db2 Mirror for i"},"ARM Category":[{"code":"a8m0z0000001hExAAI","label":"DB2 Mirror"}],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.4.0;and future releases"}]

Was this topic helpful?

Document Information

Modified date:
07 October 2024

UID

ibm16836981