Skip to Content

Control-M/Server PACTV.9.0.21.308

BMC Software is releasing Control-M/Server patch PACTV.9.0.21.308, which corrects the following problems in Control-M/Server on Linux and Windows.

Information
Important
  • Verify that Control-M/Server 9.0.21.300 and Control-M/Server PACTV.9.0.21.302 are installed before you install this patch. PACTV.9.0.21.305 and PACTV.9.0.21.306 are included and you do not need to install them before you install this patch.
  • If your Control-M/Server is installed on Linux with an Oracle database or Windows with an MSSQL database, verify that patch PACTV.9.0.21.307 is installed before you install this patch.​​​​
  • The installation and uninstallation processes shut down your Control-M/Server components, install the patch, and then restart the components.

Corrected Problems

The following table describes the problems that are corrected in Control-M/Server PACTV.9.0.21.308.

Tracking NumberPatchDescription
CTM-12884PACTV.9.0.21.308

A job remains in Executing status for five minutes, which delays post-processing, if this job performs an if-action that is defined to force a different job to execute, regardless of the scheduling criteria (Run Job and Ignore Scheduling Criteria) and the Server attribute is set to a local Control-M/Server where this job is not defined.

CTM-13578PACTV.9.0.21.308

Jobs that are defined with a Run Job and Ignore Scheduling Criteria if-action might force the target job more than once, even though that job has already started execution.

CTM-13479PACTV.9.0.21.308An information disclosure vulnerability appears in Control-M/Server when you use Control-M Automation API.
CTM-13658PACTV.9.0.21.308An injection vulnerability appears in Control-M/Server when you use Control-M Automation API.
CTM-13506PACTV.9.0.21.308Some jobs appear in the ctmlog as disappeared even though they have successfully completed executing on the Agent.
CTM-11713PACTV.9.0.21.308

Control-M/Server fails to order jobs because the CMR_CAPTURE_DEFS table is not properly cleared during the New Day procedure. The following error appears in the CE log:

815_00:00:13.026, "Operation Primary failed (retry 0)", [WARNING], T@119, T:ctm.ActiveMgr.119, , , com.bmc.ctms.kernel.KeepTrying, KeepTrying::execute, "java.lang.reflect.InvocationTargetException
…
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'CMR_CAPTURE_DEFS_PK'. Cannot insert duplicate key in object 'dbo.CMR_CAPTURE_DEFS'. The duplicate key value is (249446, 1).
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)

CTM-13029PACTV.9.0.21.306

SMART folder and regular folder orders that are initiated by job If-Actions are incorrectly ignored when the %%INTO_TABLE_ORDERID system variable value is LEGACY and the Unique Flow option is selected.

CTM-13074PACTV.9.0.21.306

Jobs fail to execute and appear to wait for a Control resource even though the resource is available when the job definitions contain a %%NODEID system variable. The following error message appears in the CE process log:

0625_16:33:25.568, "Job (10/0000a) - Job's original nodeid <NODEID> has been replaced to <NODEID>, as a result of %%NODEID. Sent back to wet check", [FINER], T@3017, T:ctm.Selector.IO.3017, "SL Job (10/0000a)", , com.bmc.ctms.selector.entity.Submit, Submit::doSubmit, ,

CTM-13163PACTV.9.0.21.306

Cyclic jobs in a SMART folder, whose Keep folder for scheduling attribute checkbox is selected, fail to execute after the New Day procedure when the RUN_CYCLIC_AFTER_NEW_DAY_OLD_MODE Control-M/Server configuration parameter is set to Y.

CTM-13237PACTV.9.0.21.306

After a you activate workload policy that is defined to restrict job runs to 0 with a Between (specific date and time) date type, jobs wait indefinitely with a job status of Wait Workload outside of the defined time frame. The following message appears in the Output tab:

Job <Job_Name> is waiting for the workload policy jobs limit to be allowed.

CTM-12762PACTV.9.0.21.306Control-M/Server fails to run (order) jobs when they include an auto-edit variable value that contains an ' (apostrophe).

CTM-2822

PACTV.9.0.21.305Workload Policies incorrectly remain active when they are outside of their defined active time range.
CTM-10074PACTV.9.0.21.305Jobs that are submitted for execution through a Network Load Balancer Router might remain in Pre-Execution status for a long period of time.
CTM-11858PACTV.9.0.21.305Jobs that use LIBMEMSYM variable lists are submitted without variables.
CTM-12024PACTV.9.0.21.305

Control-M/Server incorrectly interprets newlines as four characters long, instead of one, in if-action email notification body text. If the body of an email contains x newlines + y characters, this is interpreted as 4x newline characters + y characters, and the maximum 4,000-character limit is quickly exceeded. This causes the New Day procedure to freeze at the download stage when you order the job. The following error appears in the Control-M/EM Gateway log:

ERROR: value too long for type character varying(4000).

CTM-12080

PACTV.9.0.21.305

A job that is ordered by an If-Action set to Run Job and Ignore Scheduling Criteria, and runs on the same Control-M/Server as the original job, is ordered into the wrong folder when the %%INTO_TABLE_ORDERID variable of the action is set to LEGACY.

CTM-12231PACTV.9.0.21.305The ctmvar utility fails to create a new variable when it temporarily fails to add an entry in CMR_DBLOG database table.
CTM-12512PACTV.9.0.21.305

The job order is delayed when the job was ordered via a different job what-if action order on a remote Control-M/Server and the name of this job contains one or more spaces..

CTM-12677PACTV.9.0.21.305Order requests, such as ctmorder, ctmudly, and ctmudchk, that are executed via CLI on the Control-M/Server host, via Control-M Web, or internally on in Control-M/Server as part of the New Day procedure might never complete, even though all jobs are ordered. This might occur when there is an unexpected issue with Kafka.

Installing Control-M/Server Patch PACTV.9.0.21.308 on Linux

This procedure describes how to install Control-M/Server patch PACTV.9.0.21.308 on Linux.

Information
Important
  • You must install this patch on every host where Control-M/Server is installed.
  • In a High Availability environment, you must install this patch on active and non-active hosts.​

Before You Begin

  • Verify that Control-M/Server 9.0.21.300 and Control-M/Server PACTV.9.0.21.302 are installed before you install this patch.
  • If your Control-M/Server is installed on Linux with an Oracle database or Windows with an MSSQL database, verify that patch PACTV.9.0.21.307 is installed before you install this patch.

Begin

  1. Download the installation package from Control-M/Server 9.0.21 Patches.
  2. Log in to the account where Control-M/Server is installed and copy the installation package to a temporary directory on your local hard drive (not a network drive).
  3. Run the following command to extract the package:
    unzip PACTV.9.0.21.308.zip
  4. In a High Availability environment, stop the Control-M/Server Configuration Agent on the non-active environment to avoid automatic failover.
  5. Navigate to the following directory:
    <Extracted_Directory>/PACTV.9.0.21.308
  6. Do one of the following:
    • Interactive Installation: Run the following command:
      ./install_patch.sh
      The installation file shuts down your Control-M/Server components, installs the patch, and restarts the components.
    • Automatic Installation: Run the following command:
      ./install_patch.sh -s
      The installation file shuts down your Control-M/Server components, installs the patch, and restarts the components.
  7. Follow the on-screen instructions until the installation is complete.
    The installation file shuts down your Control-M/Server components, installs the patch, and restarts the components.
  8. In a High Availability environment, do the following:
    1. Verify that the Control-M/Server Configuration Agent on the non-active environment is up after the installation completes.
    2. Repeat the entire procedure on the non-active environment.

Installing Control-M/Server Patch PACTV.9.0.21.308 on Windows

This procedure describes how to install Control-M/Server patch PACTV.9.0.21.308 on Windows.

Information
Important
  • You must install this patch on every host where Control-M/Server is installed.
  • In a High Availability environment, you must install this patch on active and non-active hosts.​

Before You Begin

  • Verify that Control-M/Server 9.0.21.300 and Control-M/Server PACTV.9.0.21.302 are installed before you install this patch.
  • If your Control-M/Server is installed on Linux with an Oracle database or Windows with an MSSQL database, verify that patch PACTV.9.0.21.307 is installed before you install this patch.

Begin

  1. Download the installation package from Control-M/Server 9.0.21 Patches.
  2. Log in to the account where Control-M/Server is installed, copy the installation package to a temporary directory on your local hard drive (not a network drive), and then extract the package.
  3. In a High Availability environment, stop the Control-M/Server Configuration Agent on the non-active environment to avoid automatic failover.
  4. Navigate to the following directory:
    <Extracted_Directory>\PACTV.9.0.21.308
  5. From the temporary directory, do one of the following:
    • Interactive Installation: Run the following command:
      install_patch.bat
      The installation file shuts down your Control-M/Server components, installs the patch, and restarts the components.
    • Automatic Installation: Run the following command:
      install_patch.bat -s
      The installation file shuts down your Control-M/Server components, installs the patch, and restarts the components.
  6. Follow the on-screen instructions until the installation is complete.
    The installation file shuts down your Control-M/Server components, installs the patch, and restarts the components.
  7. In a High Availability environment, do the following:
    1. Verify that the Control-M/Server Configuration Agent on the non-active environment is up after the installation completes.
    2. Repeat the entire procedure on the non-active environment.

Uninstalling Control-M/Server Patch PACTV.9.0.21.308 from Linux

This procedure describes how to uninstall Control-M/Server patch PACTV.9.0.21.308 from Linux.

Information
Important

In a High Availability environment, you must uninstall this patch from active and non-active hosts.​

Begin

  1. Log in to the account where Control-M/Server is installed.
  2. In a High Availability environment, stop the Control-M/Server Configuration Agent on the non-active environment to avoid automatic failover.
  3. Navigate to the following directory:
    <Control-M/Server_Home>/patches/PACTV.9.0.21.308
  4. Run the following command:
    ./uninstall_patch.sh
    The uninstall file shuts down your Control-M/Server components, uninstalls the patch, and restarts the components.
  5. In a High Availability environment, run the following command on the non-active environment:
    ./uninstall_patch.sh
    The uninstall file shuts down your Control-M/Server components, uninstalls the patch, and restarts the components.
    Verify that the Control-M/Server Configuration Agent on the non-active environment is up after the uninstallation completes.

Uninstalling the Control-M/Server Patch PACTV.9.0.21.308 from Windows

This procedure describes how to uninstall Control-M/Server patch PACTV.9.0.21.308 from Windows.

Information
Important

In a High Availability environment, you must uninstall this patch from active and non-active hosts.​

Begin

  1. Log in to the account where Control-M/Server is installed.
  2. In a High Availability environment, stop the Control-M/Server Configuration Agent on the non-active environment to avoid automatic failover.
  3. Navigate to the following directory:
    <Control-M/Server_Home>\patches\PACTV.9.0.21.308
  4. Run the following command:
    uninstall_patch.bat
    The uninstall file shuts down your Control-M/Server components, uninstalls the patch, and restarts the components.
  5. In a High Availability environment, run the following command on the non-active environment:
    uninstall_patch.bat
    The uninstall file shuts down your Control-M/Server components, uninstalls the patch, and restarts the components.
    Verify that the Control-M/Server Configuration Agent on the non-active environment is up after the uninstallation completes.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Control-M 9.0.21