Clarity Service Management

Expand all | Collapse all

CA SDM upgrade from 17.1 to 17.2 failed at upgrading MDB patch

  • 1.  CA SDM upgrade from 17.1 to 17.2 failed at upgrading MDB patch

    Posted 09-13-2019 02:55 PM
    CA SDM upgrade from 17.1 to 17.2 failed at upgrading MDB patch, below are the logs from install.log file.
    Any inputs please 


    2019/09/13 13.45.25.803 DEBUG [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [ProgressPage] Task State Changed. TaskID: task.sdm.patch.mdb.17.2,Applying CA Service Desk Manager MDB Update(s) : 17.2 , Old State: running, New State:failed
    2019/09/13 13.45.25.804 INFO [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [DeployThread] Saving task status to DB for task task.sdm.patch.mdb.17.2
    2019/09/13 13.45.25.804 INFO [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [DeployThread] Saving task 'task.sdm.patch.mdb.17.2' status to DB ....
    2019/09/13 13.45.25.804 INFO [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [DatabasePersister] Saving component install state to database.
    2019/09/13 13.45.25.804 DEBUG [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [DatabasePersister] Insert/Update Parameters: productCode (0); currVersion (17.2); status(failed); packageId(task.sdm.patch.mdb.17.2)
    2019/09/13 13.45.25.822 DEBUG [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [DatabasePersister] Query Parameters: lower(machineName) - (servername); lower(packageid) - (task.sdm.patch.mdb.17.2); productCode(0)
    2019/09/13 13.45.25.823 INFO [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [DatabasePersister] al_cdb_componentinstallstate count 1
    2019/09/13 13.45.25.826 DEBUG [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [DatabasePersister] Update to al_cdb_componentinstallstate successful
    2019/09/13 13.45.25.826 INFO [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [DeployThread] Task 'task.sdm.patch.mdb.17.2' status saved to DB ....
    2019/09/13 13.45.25.826 DEBUG [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [ProgressPage] ProgressPage - Task Error.
    2019/09/13 13.45.25.826 DEBUG [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [ProgressPage] Task Error. TaskID: task.sdm.patch.mdb.17.2,Applying CA Service Desk Manager MDB Update(s) : 17.2
    2019/09/13 13.45.31.517 WARN [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [Messages] Unable to find resource task.sdm.patch.mdb.17.2 in bundle com/ca/smsi/installui/resources/ui/configui
    2019/09/13 13.45.31.531 INFO [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [SDMPatch] Copying log files from D:\PROGRA~3\CA\SERVIC~1\patches\cum2 to C:\Users\ADMINK~3\AppData\Local\Temp\casm\Patching\LEH_20190913_132944\SDM_MDB_20190913_134516
    2019/09/13 13.45.31.564 INFO [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [SDMPatch] Log files copied successfully to C:\Users\ADMINK~3\AppData\Local\Temp\casm\Patching\LEH_20190913_132944\SDM_MDB_20190913_134516
    2019/09/13 13.45.32.490 INFO [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [SDMPatch] Log files copied successfully to C:\Users\ADMINK~3\AppData\Local\Temp\casm\Patching\LEH_20190913_132944\SDM_MDB_20190913_134516
    2019/09/13 13.45.40.432 INFO [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [SDMPatch] Log files copied successfully to C:\Users\ADMINK~3\AppData\Local\Temp\casm\Patching\LEH_20190913_132944\SDM_MDB_20190913_134516
    2019/09/13 13.45.40.432 DEBUG [DeployThread: Applying CA Service Desk Manager MDB Update(s) : 17.2 ] [Task] inside initErrMap() generic. This method should be overloaded if possible
    2019/09/13 13.45.41.432 INFO [DeployThread] [DeployThread] task.sdm.patch.mdb.17.2 : failed
    2019/09/13 13.45.41.432 INFO [DeployThread] [DeployThread] Abort requested while running task: Applying CA Service Desk Manager MDB Update(s) : 17.2
    2019/09/13 13.49.50.757 DEBUG [main] [InstallerUI] Copying to D:\Program Files (x86)\CA\SC\logs201909131349
    2019/09/13 13.49.50.757 DEBUG [main] [InstallerUI] Copying from C:\Users\ADMINK~3\AppData\Local\Temp\casm


  • 2.  RE: CA SDM upgrade from 17.1 to 17.2 failed at upgrading MDB patch

    Posted 09-16-2019 06:48 AM
    Hi Rajasheker ,

    The mdb_install.log would be more helpful in this regards. Try locating in and upload it to the post.

    P.S. upload the actual log instead of copying the contents thereof. Ij juts makes it easier to review the log that way ;-)


    ------------------------------
    Kind Regards,
    Brian
    ------------------------------



  • 3.  RE: CA SDM upgrade from 17.1 to 17.2 failed at upgrading MDB patch

    Posted 09-16-2019 09:34 AM
    ​I'll follow this post, because in a test environment when upgrading from 14.1 to 17.2 directly I got the same problem upgrade fails at patch MDB 17.2 No error in install_log nor install_mdb.log.


  • 4.  RE: CA SDM upgrade from 17.1 to 17.2 failed at upgrading MDB patch

    Posted 09-16-2019 11:04 AM
    Edited by Yonatan Felipe Sosa Sanchez 09-16-2019 11:04 AM
    Hi Rajasheker Chittanur,

    Check next query into your database, if you have results you need to solve it because 17.2 try to create new unique index in crwf where check ([object_id], [sequence]):


    select object_id

                 ,sequence

                 ,count(sequence)

    from crwf

    group by object_id

                 ,sequence

    having count(sequence) > 1



    ------------------------------
    Regards,
    Yonatan Sosa Sanchez
    IT Services Specialist
    ------------------------------



  • 5.  RE: CA SDM upgrade from 17.1 to 17.2 failed at upgrading MDB patch

    Posted 09-16-2019 11:21 AM
    ​Hi,

    Since I'm following that post, I executed the SQL query and found out that on one request I had two workflows with same "Sequence" number. It's been inserted by an external Web application. I guess problem was there.

    I changed the sequence with a pdm_load -u command. I'll give feedback on further update results,

    Thanks for your help

    Here's my Query:

    select ref_num, crwf.* from crwf, call_req

    where crwf.object_id = call_req.persid

    and crwf.object_id IN

    (

    select object_id

    from crwf

    group by object_id

    ,sequence

    having count(sequence) > 1

    )

    order by call_req.persid




  • 6.  RE: CA SDM upgrade from 17.1 to 17.2 failed at upgrading MDB patch

    Posted 09-16-2019 11:33 AM
    Benoit.......

    Thanks for the feedback.

    Please update this thread if your 14.1->17.2 upgrade completed successfully

    ------------------------------
    Paul Coccimiglio
    Principal Support Engineer
    Broadcom Inc.
    ------------------------------



  • 7.  RE: CA SDM upgrade from 17.1 to 17.2 failed at upgrading MDB patch

    Posted 09-16-2019 04:02 PM
    ​Well bad news... since I had one request with two workflows having the same number (both had sequence 200) for same request, I changed one for 150. the one with the "older" ID I'd say.

    It didn't work. Same error at same moment. I tried installing using: DVD500000000002491.iso. Today I downloaded again files from Broadcom (CA Support Portal) and it's now : DVD0000000000605.iso.

    Since I'm working on Virtual machines in the test environment, I can restore to old configuration at anytime and try anything again. Maybe my files from DVD500000000002491  were wrong.

    I'll keep you posted.

    Attached are the errors I got while installing.

    Attachment(s)

    txt
    insall_log_FR.txt   9K 1 version


  • 8.  RE: CA SDM upgrade from 17.1 to 17.2 failed at upgrading MDB patch

    Posted 09-17-2019 03:26 PM
    ​I'm almost sure that problem is caused by an SQL procedure that doesn't complete successfully. Is there an easy way to know what are the SQL Queries called when upgrading from MDB 17.1 to 17.2?

    So then I could run each of them individually and see where it blocks.

    I think of that because, in here SDM and other software from the Service Management solution have been used for more than 10 years here, when it was called Unicenter, and version 12 and version 14... Our MDB database is maybe suffering from oldiness