Workload Automation

Expand all | Collapse all

CA Tuesday Tip: WAAE R11.3 SP1 upgrade step by step

  • 1.  CA Tuesday Tip: WAAE R11.3 SP1 upgrade step by step

    Posted 11-13-2012 09:17 AM
    CA Tuesday Tip: WAAE R11.3 SP1 Upgrade step-by-step by Stacey Ruggiero Sr. Support Engineer 11/13/2012

    https://support.ca.com/irj/portal/solncdndtls?aparNo=RI48705&os=ANY&fc=2&actionID=3


    Published Document: RI48705
    TITLE: ALL-CA WAAE R11.3 SP1 UPGRADE/REINSTALL REFERENCE

    ***** Product Documentation Change *****

    This document is intended to assist AE R11.3
    users who are planning/implementing upgrade to
    the latest AE R11.3 SP1 release as recommended
    by the CA WA Dist Support team. This document
    will provide a step-by-step approach of all the
    portions of this effort, which have been
    verified by a walk-through within the AE Level 2
    support area.

    Please make sure you review and understand these
    various sections and their associated steps.

    If you have any questions, please contact the CA
    Workload Automation AE level 1 team by opening a
    Support ticket by using the CA Support Site WEB
    page link selection from the left side labeled:
    Open a Case

    HYPER: NO

    DISTRIBUTION CODE: A (A=Available, I=Internal)

    DOWNLOAD INFORMATION:

    NODE: ftp.ca.com

    PATH: /CAproducts/unicenter/autosys/all/RI48705

    FILES: RI48705.CRZ________ ___________________ ___________________
    ___________________ ___________________ ___________________

    PROBLEM RESOLUTION: Follow the instructions below:

    ---------------------------------------------------------------------

    This is a "How to" document guide for installation/upgrade to CA
    Workload Automation AutoSys Edition (CA WAAE) R11.3 SP1 product
    release.

    This document is intended to assist AE R11.3 users who are
    planning or implementing upgrade to the latest CA WAAE R11.3 SP1
    release as recommended by the CA WA Dist Support team.

    To Download the required CA WAAE 11.3 SP1:
    ------------------------------------------

    Use the CA Support Site WEB page link selection from the left side
    labeled: "Download Center"

    Within this page "Product" selection: "CA Workload Automation AE
    Server 1 - 2 CPUs MULTIPLATFORM"
    Within the "Select a Release" menu choose: "R11.3"
    Within the "Select a Gen Level" menu choose: "SP1"

    You will now see a list of ISO files for the AE R11.3 SP1 product
    release that will need to be downloaded in order to perform the
    first step of this procedure. The details for this are listed below
    based on Platform and Component.

    To Download the required WCC 11.3 SP1 release:
    ----------------------------------------------

    Use the CA Support Site WEB page link selection from the left
    side labeled: Download Center

    Within this page "Product" selection: "CA Workload Control Center
    - MULTI-PLATFORM"
    Within the "Select a Release" menu choose: "R11.3"
    Within the "Select a Gen Level" menu choose: "SP1"

    You will now see a list of ISO files for the WCC R11.3 SP1 product
    release that will need to be downloaded in order to perform the first
    step of this procedure. The details for this are listed below based
    on Platform and Component.

    Planning: Basic safety consideration and High level architecture:
    -----------------------------------------------------------------

    First obtain current system and database backups/snapshots

    Recommendations:
    ----------------

    It is recommended that all components be upgraded, and running at
    the same version. Mixing versions of UWCC, EEM, AutoSys Scheduler/
    Agent/Client components can cause unknown behavior.

    It is recommended to follow the order mentioned below while
    performing installation or upgrade.

    Installation:-
    - CA Common Components (CCC) r11.3 SP1
    - CA Workload Automation AE (WAAE) r11.3 SP1
    - CA Workload Control Center (WCC) r11.3 SP1

    Upgrade:-
    - CA Workload Automation AE (WAAE) r11.3 SP1
    - CA Common Components (CCC) r11.3 SP1
    - CA Workload Control Center (WCC) r11.3 SP1

    Note: EEM 8.4 SP4 CR11 and CA CCS 11.2 SP2 are available in CA
    Common Components (CCC) r11.3 SP1 DVD.

    CA Workload Automation AE r11.3 SP1 UNIX/Linux:
    -----------------------------------------------

    Note:
    - CA WAAE may startup after install if autostart is chosen with
    original install.
    - It is strongly recommend to take the backup of $AUTOSYS,
    $AUTOUSER, /etc/auto.profile and /etc/auto.$AUTOSERV
    - If command sponsor is selected for installation on machine where
    ipv6 is not enabled, check the /etc/hosts file and confirm that
    it does not have an entry for ipv6 loopback. Comment the entry if
    present (i.e. #::1)
    - CA recommends unique Agent names. For more information, please
    refer to RI45635.
    - It is recommended to run the below commands and collect the
    output before upgrade:
    a. env (to be run as the user performing the upgrade)
    b. $AUTOSYS/bin/autoflags -a
    c. $AUTOSYS/bin/as_info
    - Media Distribution: DVD03143415E.iso

    1. Stop CA WAAE Services as follows:
    Login as the owner of CA WAAE executable and execute the following
    a. $CASHCOMP/bin/unisrvcntr stop waae_agent-<AGENT_NAME>
    waae_sched.$AUTOSERV waae_server.$AUTOSERV
    b. Take the backup of current CA WAAE file system (i.e.
    /opt/CA/WorkloadAutomationAE).

    2. Execute wa_setup.sh from 11.3 SP DVD image
    a. ./wa_setup.sh
    b. It opens up WA AE r11.3 maintenance wizard showing the update
    options "Modify", "Update/Reinstall", "Remove"

    3. Select "Update/Reinstall" and Click Next to continue.
    Review Settings dialog appears, listing the components that will
    be updated.

    4. Upon clicking Next in "Review Settings dialog" the actual SP
    upgrade begins.
    a. The Monitor Progress dialog appears, showing the elapsed time
    and Overall Progress.
    b. It takes a while to complete the upgrade. Once it reaches 100%,
    the Setup Complete dialog appears, listing errors, if any.
    c. Log will be created at /opt/CA/installer/log/
    CAWorkloadAutomationAE.reinstall.<YYYYMMDDHHMMSS>.log

    5. For Server installation only, one need to do the following post
    upgrade task against each Database of all AE instances.
    a. This post upgrade task information will be shown in the "Update
    Complete" dialog that appears after the completion of upgrade.
    b. Change to $AUTOSYS\dbobj\<ORA or SYB or MSQ> and execute
    RefreshAEDB.pl against each Event Server (in DUAL Server Mode)
    and follow the instructions that RefreshAEDB.pl asks for.
    i. cd $AUTOSYS\dbobj\<DB>
    ii. perl RefreshAEDB.pl

    Important Notes:

    a. This step must be done for each WA AE Server instance. It is
    not required for Client only, Agent only or SDK only
    installs.
    b. This step must be done twice in case of DUAL Server mode
    once using Primary database and 2nd time using secondary
    database.

    6. Verify that the upgrade is complete by running the following:
    a. Output of CA WAAE autoflags -a
    147 ANY 11.3 SP1 xxxxxxxx hostname
    b. Output of the SQL query "select str_val from ujo_alamode where
    type='AEDB_VERSION'" should report "11.3.1"

    7. Apply WA AE 11.3 SP1 HOT fix that resolves the critical issues.
    HOT fix is mandatory to be applied on WA SE Server and optional on
    AE Clients and not required to be applied on Agents/SDK machines.

    CA Support URL for 11.3 SP1 HOT fix is:
    https://support.ca.com/irj/portal/anonymous/phpsupcontent?
    contentID={F82B1E8D-F135-4B3B-B4E6-631B49BF699F}.

    8. Start CA WAAE Services as follows (if not using Scheduler High
    Availability or DUAL Databases (HADS).

    Login as the owner of WAAE executable and execute the following:
    $CASHCOMP/bin/unisrvcntr start waae_agent-<AGENT_NAME>
    waae_sched.$AUTOSERV waae_server.$AUTOSERV

    9. Synchronize the databases.

    Note: Synchronize database after applying WAAE 11.3 SP1 HOT fix.
    autobcp may return error without the HOT fix.

    a. cd to appropriate dbobj dir
    (i.e. cd $AUTOSYS\dbobj\<ORA or SYB or MSQ>)
    b. Run the autobcp "perl ./autobcp<ORA/SYB/MSQ>.pl"
    c. Please note ORACLE_HOME should be set for oracle database
    before running autobcp.
    d. Provide the following details:
    i. source db (or current db to be copied)
    ii. destination db (usually secondary db)
    iii. source user id/password
    iv. destination user id/password
    v. dump name
    e. Confirm if it is ok to delete data in secondary db.

    10. For Scheduler High availability.

    a. AE may startup after install/upgrade if autostart is chosen.
    It may be necessary to disable services to prevent startup.
    b. Always start Primary scheduler, then Shadow, and Tiebreaker
    (if applicable), in that order, after the upgrades are
    completed.

    CA Common Components r11.3 SP1 UNIX/Linux:
    ------------------------------------------

    Note:
    - EEM 8.4 SP4 CR11 is available in 11.3 SP1 CCC.
    - CA CCS 11.2 SP2 is available with 11.3 SP1 CCC.
    - If Workload Control Center (WCC) , EEM , CA Event Management,
    Event Agent and CA Common Communication Interface (CCI) are not
    used, this section can be skipped.
    - It is recommended to run the below commands and collect the
    information before upgrade:
    a. set (to be run as the user performing the upgrade)
    b. $CASHCOMP/bin/univer
    c. $CASHCOMP/bin/ca_version
    d. Log into EEM GUI and locate "About" link to right.
    Collect the version information.
    - Media Distribution: DVD03151649E.iso

    1. Login as root.

    2. Locate and mount media.

    3. Check if environment is setup. If not, source /etc/profile.CA

    4. cd to media location.

    5. ./ccc_setup.sh # Execute install script

    6. Choose "Update/Reinstall"

    7. Installer will stop services if they are running. Choose "Next"
    accepting that.

    8. Choose "Next".

    9. Once the install completes choose "Finish".

    10. If EEM is selected for upgrade, check version of EEM after
    upgrade
    a. grep Version $IGW_LOC/iPoz.conf #should say 8.4.411
    b. Log into EEM GUI and locate "About" link to right - should
    say 8.4.411

    CA Workload Control Center(WCC) r11.3 SP1 Linux/UNIX:
    ------------------------------------------------------

    Note:
    - It is strongly recommended to take back-up of conf files of all
    components present in WCC Install Location.
    - wrapper.conf file for each component gets overwritten when WCC is
    upgraded. Then all the existing values will change to Default.
    Once upgrade is done, wrapper.conf has to be manually replaced
    with the backed up file.
    - Install script UnixInstaller.sh supports -console and -graphical
    command line arguments. Choose whatever is convenient.
    - Before upgrading AE SDK (step#4 and #5 in WCC Install/Upgrade
    procedure below), one should determine if SDK upgrade is
    necessary. Please follow the procedure show below to check if
    one can skip step# 4 & #5 below.

    a. Login to the WCC server root.

    b. export LD_LIBRARY_PATH as shown below:

    # export LD_LIBRARY_PATH=/opt/CA/WorkloadAutomationAE/
    autosys/lib:$LD_LIBRARY_PATH

    Note: Above path should be exported accordingly. In the above
    path it was assumed that SDK was installed at default
    location.

    c. Check the build number using autoflags -i

    # /opt/CA/WorkloadAutomationAE/autosys/bin/autoflags -i

    If the output from above command is greater than or equal to 147
    then skip step#4 & #5 below as AE SDK was already upgraded to SP1.

    - Media Distribution:
    - AIX and HP-UX platforms are not available
    - DVD04074755E.iso (Sun Solaris)
    - DVD04074856E.iso (Linux)

    1. Login as root.

    2. Locate and mount the appropriate media.

    3. set|more # make sure $CA_WCC_INSTALL_LOCATION is set. If not,
    source /etc/profile.CA

    4. ./UnixInstaller.sh -console # execute installer

    5. Install CA Workload Automation AE SDK r11.3 SP1 by choosing
    Option 1 in installer.

    6. To Upgrade SDK to R11.3 SP1 choose the default selection -
    "Update/Reinstall" and proceed next with default selections.

    7. Allow the installer to run to completion.

    8. Then choose option 2 - Install "Workload Control Center R11.3 SP1"

    9. Enter to read/scroll EULA text.

    10. Enter 'Y' to accept the EULA.

    11. Choose Next to proceed with Reinstall. This option is required to
    upgrade WCC R11.3 to SP1. Existing installation will not be lost.

    12. Proceed next through the rest of the install observing defaults.

    13. Provide EEM Server's password.

    14. Leave default for keeping current policies in case same EEM
    server is used; do not overwrite existing unless you wish to.
    Change EEM server if required.

    15. Allow the installer to run to completion.

    16. Select 0 to exit when the install completes.

    17. Check version
    $CA_WCC_INSTALL_LOCATION/uejmver.sh
    Level: 11.3
    Service Pack: 1
    Build Number: 64

    CA Workload Automation AE r11.3 SP1 Windows:
    --------------------------------------------

    Note:
    - It is strongly recommended to take the backup of %AUTOSYS% and
    %AUTOUSER% directories.
    - Agent names should be unique. For more information, please
    refer to RI45635.
    - It is recommended to run the below commands and collect the
    output before upgrade:
    a. set (to be run as the user performing the upgrade)
    b. %AUTOSYS%/bin/autoflags -a
    c. %AUTOSYS%/bin/as_info
    - Media Distribution: DVD03141626E.iso

    1. Stop the CA Workload Automation AE (WAAE) services.
    a. Start the CA Workload Automation AE Administrator GUI.
    b. Click the "Services" button on the toolbar.
    c. Select the "CA Workload Automation AE Scheduler".
    d. Click the "Stop Service" button.
    e. Select the "CA Workload Automation AE Agent".
    f. Click the "Stop Service" button.
    g. Select the "CA Workload Automation AE Application Server".
    h. Click the "Stop Service" button.

    Note: Right-click on the service and select "Stop" from pull-down
    menu to stop the services.

    2. Take the backup of current CA WAAE file system (i.e.
    <Drive>:\Program Files\CA\Workload Automation AE).

    3. Execute DVD\EWA\setup.exe from 11.3 SP DVD image.

    4. It opens up WAAE r11.3 "Welcome" dialog showing the update options
    "Modify", "Repair","Remove".

    5. Select "Repair" and Click Next to continue.

    6. "Review Settings" dialog appears listing the components that will
    be updated.

    7. Upon clicking Next in "Review Settings dialog" the actual SP
    upgrade begins.

    8. The Setup Status" dialog appears, showing the Overall Progress.

    9. It takes a while to complete the upgrade. Once it reaches 100%,
    then it shows "Installation Complete" dialog. Log will be created
    at %TEMP%\WAAE_Install.log .

    10. For Server installation only, one need to do the following post
    upgrade task. This post upgrade task information will be shown in
    the above "Installation Complete" dialog that appears after the
    completion of upgrade.

    Change to %AUTOSYS%\dbobj\<ORA or SYB or MSQ> and execute
    RefreshAEDB.pl against each Event Server (in DUAL Server Mode)
    and follow the instructions that RefreshAEDB.pl asks for.
    a. Open CA WAAE Command Prompt.
    b. cd %AUTOSYS%\dbobj\<DB>
    c. perl RefreshAEDB.pl

    Important Notes:

    - This step must be done for each WA AE Server instance. It is
    not required for Client only, Agent only or SDK only installs
    - This step must be done twice in case of DUAL Server mode once
    using Primary database and 2nd time using secondary database.

    11. Verify that the upgrade is complete by running the following:
    a. Output of CA WAAE autoflags -a
    147 Windows_NT ANY 11.3 SP1 0 hostname
    b. Output of the SQL query "select str_val from ujo_alamode where
    type='AEDB_VERSION'" should report "11.3.1"

    12. Apply WA AE 11.3 SP1 HOT fix that resolves the critical issues.
    HOT fix is mandatory to be applied on WA SE Server and optional
    on AE Clients and not required to be applied on Agents/SDK
    machines. CA Support URL for 11.3 SP1 HOT fix is:
    https://support.ca.com/irj/portal/anonymous/phpsupcontent?
    contentID={F82B1E8D-F135-4B3B-B4E6-631B49BF699F}.

    13. Start the CA WAAE services if you are not using High Availability
    or DUAL Server.
    a. Start the CA Workload Automation AE Administrator GUI.
    b. Click the "Services" button on the toolbar.
    c. Select the "CA Workload Automation AE Scheduler".
    d. Click the "Start/Resume Service" button.
    e. Select the "CA Workload Automation AE Agent".
    f. Click the "Start/Resume Service" button.
    g. Select the "CA Workload Automation AE Application Server".
    h. Click the "Start/Resume Service" button.

    Note: Right-click on the service and select "Start" from
    pull-down menu to start the services.

    14. Synchronize the databases

    Note: Synchronize database after applying WA AE 11.3 SP1 HOT fix.
    autobcp may return error without the HOT fix.

    a. cd to appropriate dbobj dir (i.e. cd %AUTOSYS%\dbobj\<ORA or
    SYB or MSQ>).
    b. Run the autobcp "perl ./autobcp<ORA/SYB/MSQ>.pl".
    c. Please note ORACLE_HOME should be set for oracle database
    before running autobcp.
    d. Provide the following details:
    i. source db (or current db to be copied).
    ii. destination db, usually secondary db.
    iii. source user id/password.
    iv. destination user id/password.
    v. dump name.

    e. Confirm if it is ok to delete data in secondary db

    15. For Scheduler High availability
    a. AE may startup after install/upgrade if autostart is chosen.
    It may be necessary to disable services to prevent startup.
    b. Always start Primary scheduler, then Shadow, and Tiebreaker
    (if applicable), in that order, after the upgrades are
    completed.

    CA Common Components r11.3 SP1 Windows:
    ---------------------------------------

    Note:
    - EEM 8.4.411 is available in 11.3 SP1 CCC. If EEM has to be
    upgraded, it is recommended to follow the procedure mentioned
    in EEM Product documentation and take required back-up.
    - CA CCS 11.2 SP2 is available in 11.3 SP1 CCC.
    - If Workload Control Center (WCC) , EEM , CA Event Management,
    Event Agent and CA Common Communication Interface (CCI) are not
    used, this section can be skipped.
    - It is recommended to run the below commands and collect the
    information before upgrade:
    a. set (to be run as the user performing the upgrade)
    b. %CASHCOMP%/bin/univer
    c. %CASHCOMP%/bin/ca_version
    d. Log into EEM GUI and locate "About" link to right.
    Collect the version information.
    - Media Distribution: DVD03151508E.iso

    1. Login as administrator and mount the media.

    2. Select "CA Common Components".

    3. Click "Install".

    4. Click "Add/Modify", then click "Next".

    5. Read/Accept EULA, then click "Next".

    6. Applicable Components should be selected, click "Next".

    7. If EEM is selected for upgrade, installer prompts for EiamAdmin
    "EEM" password, provide details and click "Next".

    8. Click "Install".

    9. Click "Done" when it completes.

    10. If EEM is selected for upgrade, check the version after upgrade.
    Log into EEM GUI and locate "about" link to right - should say
    8.4.411

    CA Workload Control Center r11.3 SP1 Windows:
    ---------------------------------------------

    Note:

    - It is strongly recommended to take backup of conf files of all
    components present in WCC Install Location.
    - wrapper.conf file for each component gets overwritten when WCC is
    upgraded. Then all the existing values will change to Default.
    Once upgrade is done, wrapper.conf has to be manually replaced
    with the backed up file.
    - Media Distribution: DVD04074655E.iso

    1. Login as administrator and mount media.

    2. Run the PE_i386.EXE installer.

    3. Select "Install CA Workload Automation AE SDK".

    4. To Upgrade SDK to R11.3 SP1, proceed Next with default selections.

    5. Allow the installer to run to completion. Reboot the server.

    6. Run the PE_i386.EXE installer.

    7. Select "CA Workload Control Center" and click Install.

    8. Click "NEXT" on Welcome screen.

    9. Scroll through the License agreement. Agree to the EULA and click
    "Next".

    10. Click "Next" on "Reinstalling CA Workload Control Center" popup.
    This option is required to upgrade WCC R11.3 to SP1.

    11. Proceed through the install accepting defaults.

    12. Select Keep Policies in case same EEM server is used; do not
    overwrite existing policies unless you wish to overwrite. Change
    EEM server, if required.

    13. Click Install and allow the installer to run to completion.

    14. Exit the installer and reboot server.

    15. After Server Restart, check the version.
    cd %CA_WCC_INSTALL_LOCATION%
    .\uejmver.bat

    - Version should be
    Level: 11.3
    Service Pack: 1
    Build Number: 64

    Thank you for your continued support of CA and its products. If you
    have any questions about this Product Documentation Change or any other
    questions about this product, please contact your local CA Technical
    Support organization.

    PRODUCT(S) AFFECTED: AutoSys Base RELEASE 11.3


  • 2.  RE: CA Tuesday Tip: WAAE R11.3 SP1 upgrade step by step

    Posted 11-13-2012 04:41 PM
    Here is the link to the 11.3 sp1 release notesthat documents what is fixed with sp1
    https://support.ca.com/cadocs/7/j009633e.pdf

    Agent Log Retrieval Failed If a job’s std_out_file or std_err_file contained a Windows UNC (Universal Naming Convention) name, the CA Workload Automation AE server did not send the AFM to the agent correctly. Therefore, those logs could not be viewed from the command line (autosyslog), CA WCC, or the SDK application. For example, if a job named test_unc_log had a standard output file named \\remote_nt\test_unc_out.log, the following error messages were displayed when you tried to retrieve it using autosyslog -j test_unc_log -t O:
    CAUAJM_E_10682 Requested log file for the specified job could not be found.
    CAUAJM_E_50138 *** No agent files found for job_name test_unc ***

    Arguments Not Passed in Command Jobs
    The job failed if command name and arguments were enclosed in quotes separately. Now, you can use quotes for both the command name and arguments.
    Note: If the command name has spaces, the quotes cannot be used for arguments. For example, you cannot use command "C:\Program files\test.bat" “20” “In Progress”.

    autoping –s Failed
    The agent on the specified machine went down if you executed the autoping -s command, for example, autoping -m machine_name -s. autorep Command Displayed Unnecessary Information

    autorep Command Displayed Unnecessary Information
    The autorep command displayed unnecessary information about an overridden filewatcher job.
    The following messages were displayed:
    autorep -j fw -q -o 1
    override_job: fw
    /*CAUAJM_I_10350 Over-Ride #1 Set by User: root@aadrh53-ora on [12/23/2010 17:05:27]*/
    /*CAUAJM_I_10352 Was RUN on run_num=1,487, Started on: 12/23/2010 17:05:41*/
    watch_file_min_size: -9223372036854775808
    watch_interval: 240
    The minimum size is not displayed now, when watch_file_min_size attribute was not overridden.

    autorep Failed To Generate Global Blob Report
    The autorep command failed to generate the global blob report when you used an asterisk character with the –z option. Also, the files containing the blob data were not stored in the directory specified using the -f option.
    autosys_secure Option 5 Not Displayed
    If you did not have execute rights for the CA EEM as-control SECADM default policy, option 5 (manage users@host) of the autosys_secure command was not displayed.

    Blob or Glob Attribute Not Updated as Expected
    When the blob was uploaded to the database and the job was defined, the blob or glob attribute was updated as expected. If the job was redefined (using update_job or override_job commands) to update the blob or glob with a new value, the blob or glob was taking the old value instead of picking the new value. CA Workload Automation SE Jobs Held in READY State

    CA Workload Automation SE Jobs Held in READY State
    When CA Workload Automation SE jobs were submitted to CA Workload Automation AE, the jobs were held in READY state. This happened when the CA Workload Automation AE scheduler was running and the cross-platform application was recycled. The mainframe application sent a setup request which was ignored by the scheduler because of a bug.

    CA EEM Servers List was Limited to 64 Characters
    When you enabled external security using the autosys_secure command, the CA EEM servers list that you could specify was limited to 64 characters.
    You can specify a comma-separated list of CA EEM servers if you configure multiple CA EEM servers for the failover. The entire list of CA EEM servers can now be up to 255 characters.

    Changed Status Set to Blank
    When you ran a SQL stored procedure for SENDEVENT (ujo_sendevent) to send a CHANGE_STATUS event to Success, it was setting the status to a blank instead.

    chase Command Did Not Display the Status of All Jobs
    The chase command stopped processing the job status after it received the following status message:
    CAUAJM_I_50175 An event for this job has come in during examination. Everything is fine.
    The chase command verifies the status of jobs based on the job object ID (joid) order. Any job with a joid higher than that of the job that received the above status message did not get processed by chase command, that is, did not display a status message.

    Cross-Instance Communication Issue
    The cross-instance communication from a CA Workload Automation AE r11.3 instance to a Unicenter AutoSys JM 4.5 instance was not successful if you changed the database password using the autosys_secure command. The autosys_secure command did not update the encrypted password in the ujo_alamode table. Cross-Platform Manager Did Not Work as Expected

    Cross-Platform Manager Did Not Work as Expected
    When the CA Workload Automation AE secondary scheduler took over while a CA Workload Automation AE job was in flight, the status of the in-flight job was not sent to the cross-platform scheduling manager.

    Datamover Issue
    When you ran the datamover utility, the following error messages were displayed intermittently:
    RowCounter failed on table ujo_asbnode --java.sql.SQLException: ORA-00942:
    table or view does not exist
    RowCounter failed on table ujo_afm_strings --java.sql.SQLException:
    ORA-00942: table or view does not exist
    This happened because the RowCounter thread failed to shut down properly and ran over the truncator thread space.

    Datamover Metadata Corrected
    The Metadata definitions of Datamover are corrected to reflect the current database schema.

    Documentation Typo Corrected
    Remote Note is corrected to Remote Node in the application server log file.
    Note: Every instance of this typo was corrected in the application server log file.

    Error Messages in z/OS Job
    The error messages of the zos_dsn_updated and zos_dsn_renamed attributes had the values of 0, 1, or both. The error messages are updated to Y, N, or both.

    exclude_calendar Attribute Ignored
    The job schedule information based on the exclude_calendar attribute was displayed in scheduler log even if the date_conditions attribute of that job was set to zero. Exit Code Not Displayed on the Console

    Exit Code Not Displayed on the Console
    The exit code was not displayed on the console while inserting all jobs that were successful using the jil command.

    Forecast Command Failed
    The forecast command failed to report the following while the autorep command reported them as running:
    ■ When you specified the end of the run window to fall in the next day in the run_window attribute of the job definition, forecast failed to recognize this and did not report the job.
    ■ When you defined a day-based box job with children that are dependent on each other and are also day-based jobs, forecast did not report these dependencies.

    Forecast Command Displayed Duplicate Output
    If the parent box job had date-time condition and the child job had starting condition, the forecast command displayed the output of the child job twice.

    Forecast Report Did Not Consider exclude_calendar
    The report generated by the forecast command did not consider the calendar specified in the exclude_calendar attribute of the given job.

    FQDN Names Not Obtained During a Reverse Lookup
    When you perform a reverse lookup, the FQDN names were not obtained for machines that failed.

    Global Variable Name Not Enclosed in Braces
    The global variable name specified in a job definition was not enclosed in braces.
    As a workaround, manually enclose the global variable in braces, for example, $${env.var}. Global Variable Names with a Period or a Space Not Properly Resolved

    Global Variable Names with a Period or a Space Not Properly Resolved
    If the global variable name specified in a job definition contained a period or a space character, the global variable name was not resolved properly.
    To fix this problem, help ensure that you enclose the period or space in braces, for example, $${env.var}.

    Incorrect Forecast Command for Box Job
    When you generated a forecast report of a child box job, the report was generated for the child job without considering the parent job's schedule.

    IP Address Cached
    When CA Workload Automation AE failed over, the scheduler continued to run jobs on the old IP address of the agent machine, even when the address of agent machine was changed. This happened because of the cached IP address.

    Issue with SNMP Traps
    The machine name was not passed in the SNMP traps for the EP_SHUTDOWN and EP_ROLLOVER alarms.

    Jobs Held in STARTING Status
    Jobs that were running on legacy adapters were held in the STARTING status intermittently. This happened because the agent received the wrong job identifier, so it could not send information back with the right job identifier.

    Jobs Held in ACTIVATED, STARTING, or RUNNING State
    Jobs were held in ACTIVATED, STARTING, or RUNNING status when a database fetch failure occurred. Busy Jobs with Override on Virtual Machine Were Held in STARTING State

    Busy Jobs with Override on Virtual Machine Were Held in STARTING State
    When you defined a new job on a virtual machine that included an agent that was busy running jobs, the jobs with overrides were held in STARTING state. The scheduler experienced a database arithmetic overflow error. The error messages were displayed in the scheduler log.

    Jobs with Look-Back Condition Did Not Start Automatically
    A job was defined with a look-back condition did not start automatically even when the job’s condition was met. This happened when the dependent job was updated or recreated. Also, job_depends command displayed that the condition for the job did not meet.

    Memory Leak Detected
    A memory leak was detected in the application server when access to delete a calendar or a cycle was denied.

    Primary Scheduler Did Not Respond
    The primary scheduler stopped responding when an ORA-03126 (Oracle database) error was encountered.

    Redirection Operators Failed in std_out and std_err Attributes
    When the oscomponent.noforceprofile, oscomponent.profiles.src.delay, and oscomponent.profiles.global.override controlling options were enabled in the agent, the job having the redirection operators in the std_out_file and std_err_file attributes failed. sap_step_parms Attribute Value Not Updated

    sap_step_parms Attribute Value Not Updated
    When you updated an SAP job while autotrack was ON (autotrack level=1), the sap_step_parms attribute value was not updated. The following error messages were displayed:
    CAUAJM_E_18416 Event Server: <autoprd> Failed Query: <BEGIN :RetVal :=
    ujo_audit_msg_log (113, 74, 'variant', 'ZTEST_UNIX', 'N'); END;>
    CAUAJM_E_18402 ORA-20870: Insert of ujo_audit_msg_log failed - -1 -ERROR-
    ORA-00001: unique constraint (AEDBADMIN.XPKUJO_AUDIT_MSG) violated ORA-06512:
    at "AEDBADMIN.UJO_AUDIT_MSG_LOG", line 27 ORA-06512: at line 1
    CAUAJM_E_18400 An error has occurred while interfacing with ORACLE.
    CAUAJM_E_18401 Function <doExecute> invoked from <execute> failed <761>
    CAUAJM_E_10057 ERROR logging audit data//autotrack may have unpredictable results

    Scheduler Did Not Respond for Jobs with Long Global Variables
    The scheduler stopped responding when you started a job that used a global variable with length greater than 64 characters, although the maximum length that can be specified for a global variable is 100.

    Scheduler Log Did Not Respond
    When CA Workload Automation AE was running on a machine where OS was using external authentication services like LDAP or VAS, the scheduler log stopped responding immediately after the startup. The event processing was not affected.

    Scheduler Deadlock on DBMaint
    If you ran the DBMaint command to maintain the database while many jobs were actively running, the scheduler stopped responding. sendevent –E CHANGE_PRIORITY Command Did Not Work

    sendevent –E CHANGE_PRIORITY Command Did Not Work
    The sendevent command failed when the queue priority for a job was changed to zero, for example, sendevent –E CHANGE_PRIORITY –q 0 –J job_name.
    The following error messages were displayed in the event_demon log file:
    [09/23/2011 13:51:43] CAUAJM_I_40245 EVENT: CHANGE_PRIORITY JOB: KG0-BU-LOG-01
    [09/23/2011 13:51:43] CAUAJM_E_18802 Error from SQLExecute() Failed with SQL_ERROR.
    [09/23/2011 13:51:43] CAUAJM_E_18601 SQLSTATE: 42000, Native error: 102,
    Message: [Microsoft][ODBC SQL Server Driver][SQL Server] Incorrect syntax near '='.
    [09/23/2011 13:51:43] CAUAJM_E_18601 SQLSTATE: 42000, Native error: 8,180 , Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared.
    [09/23/2011 13:51:43] CAUAJM_E_18611 Event Server: <smicl02w2k3e:AEDB> Failed Query: <UPDATE ujo_job_status SET run_priority=0 WHERE joid=105 and job_ver=>
    [09/23/2011 13:51:43] CAUAJM_E_40225 Trouble processing Event [WAEz10000032]!
    [09/23/2011 13:51:43] CAUAJM_I_40245 EVENT: ALARM ALARM: EVENT_HDLR_ERROR JOB: KG0-BU-LOG-01
    [09/23/2011 13:51:43] <event_hdlr error>

    sendevent Command Did Not Work As Expected
    When an alarm was sent for a job manually using the sendevent command, the job object id (joid) for the job was not stored in the alarm table and was set to zero instead.
    The alarm was not displayed in the detailed report for the job generated using the following command:
    autorep -J job_name -d

    Slow Data Migration
    Migrating data from CA Workload Automation AE 4.5.1 to CA Workload Automation AE r11.3 was slow. In this release, the initial heap size and the maximum heap size are increased to 512M and 1024M respectively, making the migration faster. ujo_sendevent Failed

    ujo_sendevent Failed
    A manual execution of the ujo_sendevent database procedure or function that failed for the following database:
    For Sybase and MS-SQL:
    When you executed ujo_sendevent to generate a CHANGE_STATUS event, the following error message was displayed:
    Invalid STATUS
    For Oracle:
    When you executed ujo_sendevent with a date or time input to generate a CHANGE_STATUS event, the following error message was displayed:
    Invalid STATUS
    aedbadmin.ujo_sendevent('CHANGE_STATUS','33713_hendry_test', 'INACTIVE','', '01/12/2012 18:00','Reset for today');
    Also, the ujo_sendevent generated the wrong event text. The following error message was displayed:
    ORA-06502: PL/SQL: numeric or value error: character to number conversion error. Update Job Condition

    Update Job Condition
    When a job in a box was updated after you specified a one-time override on the box job, the following error messages were displayed:
    CAUAJM_I_50323 Inserting/Updating job: test_job
    CAUAJM_E_18416 SQL Query <BEGIN :RetVal := ujo_put_job
    (0,63372,1,'','','',-1,0, 0,0,'test_box',0,0,'','Administrator@lodivm11vs1029',0,'','','',0,'','','',0
    ,0,0,0,0,0,0,0,'',0,'test_job','',0,99,'localhost',0,0,0,0,'','',0,102659911,'Administrator@lodivm11vs1029','',0,'','','',0,0,'','','','','',0,'','', :B_joid,
    :B_job_ver, :B_over_num, :B_wf_joid); END;> failed
    CAUAJM_E_18402 ORA-01422: exact fetch returns more than requested number of rows
    ORA-06512: at "AEDBADMIN.UJO_PUT_JOB", line 136
    ORA-06512: at line 1
    CAUAJM_I_18403 Processing OCI function ODEFIN(34)
    CAUAJM_E_18400 An error has occurred while interfacing with ORACLE.
    CAUAJM_E_18401 Function <doExecute> invoked from <nextRow> failed <860>
    CAUAJM_E_19028 Trouble with database connection. Please manually delete the job "test_job" and redefine it again.
    CAUAJM_I_50205 Database Change WAS Successful!
    The job is now updated when the RefreshAEDB script updates the database, the tablespaces (for Oracle), and all the schema objects.

    Average Run Delay Column Displayed Negative Values (Oracle Application Server only)
    In CA WCC, the Average Run Delay in Job Run report displayed negative values on an Oracle application server.

    Datamover Failed to Validate Oracle Real Application Cluster (RAC) Database (Oracle only)
    When you migrated data to an Oracle RAC database, the datamover utility failed to validate the database. This happened because you cannot connect to the Oracle RAC database using the JDBC thin client drivers.
    As a workaround, you must run the datamover utility on individual nodes of the Oracle RAC database. ujo_sendevent with Time Failed (Oracle only)

    ujo_sendevent with Time Failed (Oracle only)
    When you executed ujo_sendevent stored procedure manually with time as an input, the procedure execution failed and displayed the following error:
    ORA-06502: PL/SQL: numeric or value error: character to number conversion error.

    autosyslog –e Command Reported Error (Windows only)
    Even when the users with Administrators or Power Users group rights executed the autosyslog -e command, the following error was displayed:
    CAUAJM_E_50135 Only Administrators or Power Users can execute autosyslog

    Build Number Not Updated When Upgraded (Windows only)
    When you upgraded from CA Workload Automation AE r11.3 to CA Workload Automation AE r11.3 SP1, the build number was not updated in the CA Workload Automation AE Administrator GUI. The build number should be updated from 138 to 147.

    Default DCA URL Setting Blank (Windows only)
    The default URL location of DCA integration in the CA Workload Automation AE Administrator was blank. The default URL location has been updated to https://dcamgr:443/aip/sc; therefore, you need to change only your DCA host name now.

    Default DCA URL Location Not Populated After the Upgrade (Windows only)
    The default URL location https://dcamgr:443/aip/sc was not populated after the upgrade to r11.3 SP1.

    Excess EVENT_HDLR_ERROR Alarm (Windows only)
    When the scheduler ran with heavy loads, it raised the EVENT_HDLR_ERROR alarm and the jobs were not rescheduled. This happened because of the deadlocks in the ujo_setup_next database table with ujo_batch_move_event and ujo_batch_get_event stored procedures. Incremental 2 Patch Installation Failed (Windows only)

    Incremental 2 Patch Installation Failed (Windows only)
    An error was encountered while installing the incremental 2 patch in GUI mode on a Windows server. The default paths were not populated.

    Installation Failed (Windows only)
    The CA Workload Automation AE installation that failed on Windows when it failed to install SSA. The SSA installation that failed because the installer installed CAPKI 4.1.4, while it requires CAPKI 4.1.6 or higher.

    Instance Administration Window Disappeared (Windows only)
    When you clicked either the Instance Wide Encryption or the zOS Encryption tab on the Instance - CA Workload Automation AE Administrator window of CA Workload Automation AE Administrator and pressed the Enter key, the tab disappeared.

    Patch Not Applied To All Agents (Windows only)
    When you upgraded from CA Workload Automation AE r11.3 to CA Workload Automation AE r11.3 SP1, the patch was applied to only one agent per machine instead of all agents.

    Agent Installation Failed (Solaris only)
    The agent Installation that failed on Solaris 8 and the following error message was displayed:
    !! Script executed with error: 1
    Script or command "as_postinterview.sh" failed with exit code 1.

    Database Password Update in the Configuration File (UNIX only)
    When you updated the database password using the autosys_secure command, the password was updated on all lines that correspond to the DBAccess parameter in the configuration file, irrespective of whether the lines were commented or not. SSA Installation Created Circular Links (UNIX only)

    SSA Installation Created Circular Links (UNIX only)
    The SSA installation created circular links. This issue was fixed with the SSA 2.1.44+ installer.

    Installation Error (UNIX only)
    If the time zone settings contained a space, for example, America/New York, the CA Workload Automation AE installation log displayed the following error message:
    /opt/CA/WorkloadAutomationAE/autouser.ACE/autosys.sh.rhel6x32: line 33: York:
    command not found
    The CA Workload Automation AE services failed to start automatically after the installation.

    Timezone Information Not Determined (UNIX only)
    If the time zone settings contained a space, for example, America/New York, the timezone information was not determined correctly because a shell script error occurred.


  • 3.  RE: CA Tuesday Tip: WAAE R11.3 SP1 upgrade step by step

    Posted 02-08-2013 04:06 PM
    This PIB has been withdrawn and is no longer available at the link.