CA Service Management

 View Only
Expand all | Collapse all

17.1.08 - grloader does not see existing mdr

  • 1.  17.1.08 - grloader does not see existing mdr

    Posted May 08, 2020 06:00 AM
    Hi,
    in a customer's system we are loading from twa to mdb (update CIs with mdr).

    MDR is created:
    but grloader says that mdr cannot be found:

    We've already recreated MDR.
    Error does not disappear.
    In reference-system it works.

    Any idea what we can look for?

    Regards,
    Peter


    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------


  • 2.  RE: 17.1.08 - grloader does not see existing mdr

    Broadcom Employee
    Posted May 11, 2020 08:53 AM
    Hi Peter,

    Can you share the actual error you see in the grloader logs?


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



  • 3.  RE: 17.1.08 - grloader does not see existing mdr

    Posted May 12, 2020 01:53 AM
    Hi Brian,
    here a snip from GRLoader.log:

    05/12 04:25:59.748 INFO  grCI 382 Read in CI, now processing..

    05/12 04:25:59.748 INFO  grCIKey 312 grCIKey900 Finished with Key: name(IT.....699) mdr_name(Empirum) mdr_class(Empirum) fed_asset_id(PNIT.....699)

    05/12 04:25:59.748 INFO  GRLoader 304 Not found: MDR name(Empirum) MDR class(Empirum)

    05/12 04:25:59.795 INFO  grCIKey 312 grCIKey900 Finished with Key: id(28F4523DA........4737E58F) name(IT.....699) mdr_name(Empirum) mdr_class(Empirum) fed_asset_id(PNIT.....699)

    05/12 04:25:59.827 INFO  grDataMgr 1257 update of (ci_twa_ci) handle (ci_twa_ci:2000109522) completed successfully


    Nothing in stdlog for it, nothing else for this ci in GRLoader.log
    MDR is existing on this machine.

    Thanks and Regards,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 4.  RE: 17.1.08 - grloader does not see existing mdr

    Broadcom Employee
    Posted May 12, 2020 04:45 AM
    Hi Peter,

    Check if there is no other CI or MRD with the same that may be inactive?


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



  • 5.  RE: 17.1.08 - grloader does not see existing mdr

    Posted May 13, 2020 03:10 AM
    Hi Brian,
    no, no inactive CIs with same MDR. It occurs for all existing CIs which have to be updated with MDR.
    I'll try sugestion of Michael tomorrow and keep you informed.

    Thanks and Regards,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 6.  RE: 17.1.08 - grloader does not see existing mdr

    Posted May 13, 2020 01:33 AM
    Hi Peter.
    How about checking the sql queries grloader is using to find the MDR?
    At least you would then know, why the mdr is not found.
    Regards.
    ....Michael

    ------------------------------
    Principal Services Consultant
    HCL Enterprise Studio
    Germany
    ------------------------------



  • 7.  RE: 17.1.08 - grloader does not see existing mdr

    Posted May 13, 2020 02:16 AM
    Hi Michael,
    I have no direct access to customers system today.
    Do I have to set loglevel for this or can I see the sql-statements anywhere else? STDLOG does not have any info and Grloader.lg does not help there.

    Thanks,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 8.  RE: 17.1.08 - grloader does not see existing mdr
    Best Answer

    Posted May 13, 2020 02:35 AM
    Edited by Christopher Hackett May 22, 2020 01:23 PM
    Try using
    pdm_logstat -f sqlclass.c MILESTONE
    If it is a MSSQL DB.

    ------------------------------
    Principal Services Consultant
    HCL Enterprise Studio
    Germany
    ------------------------------



  • 9.  RE: 17.1.08 - grloader does not see existing mdr

    Posted May 13, 2020 03:12 AM
    Hi Michael,
    I'll try it tomorrow beeing online at customer.
    Danke dir ...

    Thanks and Regards,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 10.  RE: 17.1.08 - grloader does not see existing mdr

    Posted May 18, 2020 11:49 AM
    Any news?

    ------------------------------
    Principal Services Consultant
    HCL Enterprise Studio
    Germany
    ------------------------------



  • 11.  RE: 17.1.08 - grloader does not see existing mdr

    Posted May 19, 2020 01:00 AM
    Hi Michael,
    at my last meeting with the client, we didn't have much time to investigate this phenomenon. Strangely enough, the error does not occur when you set individual records which are marked with this 'error' to 'Ready' in the TWA.

    Further tests are scheduled for next week.

    Regards,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 12.  RE: 17.1.08 - grloader does not see existing mdr

    Posted May 26, 2020 07:36 AM
    Edited by Peter Schmidt May 26, 2020 07:36 AM
    Hi,
    debugging sql-queries didn't help in this case.
    When I'm trying the selects (before error) manually they are all working nice and as expected - no error that mdr was not found.

    Nice effect is
    - I set mdr-errors in TWA to 'ready'
    - I copy command (grloader-call) from script to Dos-Box
    - call grloader manually
    --> no MDR-Error can be seen after the manual grloader - run.

    That's my workaround for now.


    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------