Share:|

Are you aware of the End of Support for Control-M 7 is November 10th 2017? If not, it’s time to get familiar with the upgrade process so you can take advantage of the new features in Control-M 9.

 

The AMIGO program is designed to assist with your plan for a successful upgrade. Please contact Customer Support to open an AMIGO case and discuss your upgrade plans.

 

To learn about the upgrade process and new enhancements in Control-M 9 and how to perform a successful upgrade at your company, join us for a Connect with Control-M live webinar on Wednesday, January 25th where Taylor Clapp will demonstrate:

 

What's new in Control-M 9

Control-M/Enterprise Manager upgrade

•     Control-M/Server upgrade

•     Tips for a successful upgrade

 

This is the link on YouTube for the recorded session:

 

Connect with Control-M: Upgrading to Control-M 9 - YouTube

 

Here is the Q&A for this webinar (Connect with Control-M: Upgrade to Control-M 9)

 

________________________________________________________________

 

Q: Managed File Transfer, is this extra license needed? Is that also same for Self Service?

A: Both Control-M Managed File Transfer and Control-M Self Service are independent licensed products. For further information about this contract reach your Sales Representative

________________________________________________________________

 

Q: Manage file transfer, does this supersede existing AFT?

A: Both modules are independent, but Managed File Transfers provides its own FTP Server and other benefits.

________________________________________________________________

 

Q: How to keep existing data and import v7 or early data migration

A: You can use the util with an export option to make separate exports of your source or destination environment. Please note that the import will replace any data on the destination Server.

________________________________________________________________

 

Q: In place upgrade is possible or not?

A: As of EM 9 FP3, it is not possible to upgrade an EM/Server or M/Server in place. You can use Agent Deployment to automate Agent upgrades from a centralized point of access.

________________________________________________________________

 

Q: Is it possible to export just static CTM/Server data and later perform the active export data as well?

A: Yes, it is possible. During the Control-M/Server export, you are prompted to shut down the Control-M/Server. If you choose not to shut it down, you will only export log and definitions in an LD file. Shortly thereafter, you can repeat the export choosing to shut the Control-M/Server down and export the LDR file that also includes runtime/active data.

________________________________________________________________

 

Q: When transferring the export files to destination environment is it necessary to use binary mode for the transfer?

A: Yes, it is.

________________________________________________________________

 

Q: Is it possible to export job definitions in an xml file from version 7 to version 8 or 9?

A: This is not supported. We recommend elevating the job definitions as described in this demonstration.

________________________________________________________________

 

Q: If the old environment was a Full Installation, Are the export and import processes performed individually for both EM and CTM/Server?

A: Yes, the process is still the same; you will just be performing them as the same user.

________________________________________________________________

 

Q: Can we do the export/import process even if the CTM/Server is still set to Managed?

A: Yes, you can. We do recommend that you set the Control-M/Server to "Unmanaged" mode to avoid any potential problems in case the Control-M/Server connects to the Control-M/Enterprise Manager server before it is elevated, which is why we recommend setting it to "Unmanaged" first.

________________________________________________________________

 

Q: Does the destination name value corresponds to the new server hostname?

A: Yes, it does. This is helpful to do when you are elevating the Control-M/Server.

________________________________________________________________

 

Q: Is there database dependency? For example previous version using different database and want to configure different database for v9?

A: No there isn't. You can move to a different supported database when upgrading Control-M

________________________________________________________________

 

Q: When upgrading from version 8 to 9, is the same process?

A: Yes, the process is largely the same going from version 8 to version 9.

________________________________________________________________

 

Q: What does the Elevate step do?

A: The elevate step was formerly known as "migrate_dc" and "promote". The elevate step makes steps internal to the database to alter the job definitions to fit the new version, and this is a necessary step.

________________________________________________________________

 

Q: Is it possible to upgrade first Control-M/Server and then Control-M/EM?

A: No, first you have to upgrade Enterprise Manager and then Control-M/Server

________________________________________________________________

 

Q: If I'm only upgrading EM, is it necessary to elevate the Control-M/Server?

A: When upgrading just Enterprise Manger you don't have to elevate Control-M/Server

________________________________________________________________

 

Q: What does it mean of Control-M server pause Mode is N when we start the Control-M services?

A: The purpose of putting the M/Server in an Un-Managed state is to ensure that there are no conflicts when elevating this in the Control-M Configuration Manager.

________________________________________________________________

 

Q: What is an "unmanaged" server?

A: Setting an M/Server to Un-Managed state means that no updates will be sent to this M/Server from the EM/Server.

________________________________________________________________

 

Q: We are upgrading from 7 to 9 in Windows SQL, we did Export/Import, how about synchronization? We thought is needed?

A: The synchronization step occurs when you are Elevating this M/Server to the destination version.

________________________________________________________________

 

Q: Can you please write your YouTube channel name

A: This is the direct link to our YouTube Channel where you'll find the webinar series

   https://www.youtube.com/playlist?list=PLu3XvW2Tbj731gkQtyplYJT2EKpbsccxV

________________________________________________________________

 

Q: Are there special considerations from 7 to 9 and Sun to Windows?

A: Please open an AMIGO ticket for specific questions.

________________________________________________________________

 

Q: Can I use this migration to move from Linux to windows, and more important, from oracle to SQL?

A: The migration translates across all supported OS and database types.

________________________________________________________________

 

Q: What Version of Oracle is supported with Control-M 9?

A: An Oracle 11 and 12C database server

________________________________________________________________

 

Q: If we want to upgrade from Solaris to Windows 2012 Server, how does that affect the upgrade path?  How can we determine if the Windows 2012 Server is correctly sized for the current load on Unix (100-200K job executions per day?

A: Please open an AMIGO ticket to address concerns specific to your upgrade and also request assistance with the Control-M sizing template.

________________________________________________________________

 

Q: Can I export job definitions from v9 into v8?

A: If using the Control-M 9 client, you are given the option to export this definition in a format compatible with that version of Control-M.

________________________________________________________________

 

Q: Can we shutdown EM/Server processes using root_menu/ctm_menu by using Shutdown all options before the export?

A: Yes, just make sure that there are no processes still running in the background and make sure Database is still up and running.

________________________________________________________________

 

Q: So no new jobs will run in an "unmanaged" state?

A: Jobs that are scheduled to run will continue to run.

________________________________________________________________

 

Q: How are Control-M Agents upgraded while transition? For example: you are at version 8 and you have a new server in place, how do you propose the transition?

A: For such case you can add the new CTM/Server 9 to the authorized hosts list for the current Agent so it can received job submissions from that new CTM/Server v9 and once you shutdown the v8 then you can change the Primary host definitely to new CTM/Server v9

________________________________________________________________

 

Q: we have some v6.x and v7. Agents, do we need to upgrade them 1st prior to EM and Server upgrade?

A: Usually Agents are upgraded after EM and CTM/Server are done, but you can upgrade them first too. If you have any concern please open an AMIGO ticket.

________________________________________________________________

 

Q: This demo implies that all the agents get pointed to the new server.  Is that the case, or will we need to go through our agents and re-point them to the new server?

A: When exporting the M/Server, you are given the option to enter an Authorized M/Server for the defined Agents on the M/Server you are exporting.

________________________________________________________________

 

Q: If we have some existing tables in new CTM9 and after importing those table will be deleted or it will be there?

A: When you perform the import it will overwrite the existing data

_____________________________________________________________

 

Q: How to migrate for distribution keeping all existing sys parms?

A: System parameters are included in an EM export.

________________________________________________________________

 

Q: Our plug in control module for java and web services is 6.3.02.100, will there be a new version?

A: Latest version for Control-M for Web Services, Java and Messaging is version 8.0.00

________________________________________________________________

 

Q: How to pass global conditions b/w different EM servers?

A: Global conditions are just passed between different Control-M/Servers under same Control-M/EM.

________________________________________________________________

 

Q: Can we upgrade from V6.4 to V9?

A: Yes you can.

________________________________________________________________

 

Q: Does ctrl-m 9 support a database in a clustered SQL environment?

A: Control-M 9 supports clustered installations.

________________________________________________________________

 

Q: You indicated the upgrade is to take place on other Servers?

A: Yes, it is not an 'in-place' upgrade.

________________________________________________________________

 

Q: We have database and Control-m upgrade planned. Do we need to upgrade the database before the Control-M upgrade?

A: Please open an AMIGO ticket to discuss specific questions like these

________________________________________________________________

 

Q: Our SQL database version is 2014 sp1. Will this be compatible with v9?

A: Further information about Control-M compatibility with Oracle can be found in the Release Notes:

 

http://documents.bmc.com/supportu/documents/32/33/483233/483233.pdf

 

http://documents.bmc.com/supportu/documents/11/75/481175/481175.pdf

________________________________________________________________

 

Q: Do we need to point all the agents to the new server if the new server is not yet one of the authorized servers?

A: Yes you do

________________________________________________________________

 

Q: Is possible the upgrade from version 6 to version 9? Are there any restrictions?

A: You can go from 6.4.01 to version 9 without any problem as stated in the Upgrade guide:

 

http://documents.bmc.com/supportu/952/39/29/483929/483929.pdf

________________________________________________________________

 

Q: Upgrading from V8 with PostgreSQL to v9 with MSSQL. Will there be any criteria to consider with the upgrade?

A: Just make sure to use a supported Database version as stated in the Release Notes:

 

http://documents.bmc.com/supportu/documents/32/33/483233/483233.pdf

 

http://documents.bmc.com/supportu/documents/11/75/481175/481175.pdf

________________________________________________________________

 

Q: Can we upgrade our EM from version 7 to version 9 1st and upgrade Control-M at a later date?

A: Yes you can

________________________________________________________________

 

Q: After CTM9 migration we have to manually upgrade the agent or we can use new feature of v9 to upgrade the agent

A: You can use the Agent Deploy feature

________________________________________________________________

 

Q: I noticed on your EM import it had errors in the log for Self Service and BIM, were those ok?

A: The error message are due to the fact that there were some obsolete data in the original V8 environment. Further information about those errors can be found in the following article:

 

https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000113328

________________________________________________________________

 

Q: Do we have a new version of OEBS plugin? What are other plugins are available with release 9.0?

A: Latest version for Control-M for Oracle E-Business Suite is 9.0.00 you can check latest release in our site

________________________________________________________________

 

Q: Can add multiple authorized servers during the upgrade?

A: No, you are only given the option to add one M/Server.

________________________________________________________________

 

Q: V9 high availability available for both EM and control-m server for Postgres DB?

A: Yes, HA is available for both EM and M/Server components when using BMC supplied Postgres.

________________________________________________________________