IV35825: BUSY HOUR REPORTS MAY FAIL IF THE DATE-TIME SCOPE SELECTED ARE NON-CONSECUTIVE DAYS RESULTING IN A PKN: Error

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as Vendor Solution.

Error description

  • Some BusyHour reports may fail when selecting a date-time scope
    that has non-consecutive days and if the first days in the gaps
    by chance has a busyhour at the midnight hour.
    
    The report's error will show in the Prospect Client's Status
    Monitor:
    job status msg:  "rgp.sh failed with exit status := 255"
    and
    task status msg: "Waiting for response (#2). Connection broke to
    DataServer...
    
    The report's wmtm-1-<jobid>.log will contain at the bottom this
    error:
    PKN: Error - primary key is null for object <blank>  in
    table/column:  individual/TSTAMP
    

Local fix

  • A temporary workaround is to either include the day or days in
    the gap or break up the report into multiple reports with
    consecutive days for the date time scope.
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • PROBLEM DESCRIPTION:
    
    BUSY HOUR REPORTS MAY FAIL IF THE DATE-TIME SCOPE SELECTED ARE
    NON-CONSECUTIVE DAYS RESULTING IN A PKN: Error
    
    PROBLEM SUMMARY:
    
    Some BusyHour reports may fail when selecting a date-time scope
    that has non-consecutive days and if the first days in the gaps
    by chance has a busyhour at the midnight hour.
    
    The report's error will show in the Prospect Client's Status
    Monitor:
    job status msg:  "rgp.sh failed with exit status := 255"
    and
    task status msg: "Waiting for response (#2). Connection broke to
    DataServer...
    
    The report's wmtm-1-<jobid>.log will contain at the bottom this
    error:
    PKN: Error - primary key is null for object <blank>  in
    table/column:  individual/TSTAMP
    
    RESOLUTION:
    Workaround is sufficient.
    
    CONCLUSION:
    No permanent fixes required as agreed by customer.
    
    TEMPORARY FIX:
    
     A temporary workaround is to either include the day or days in
    the gap or break up the report into multiple reports with
    consecutive days for the date time scope.
    

APAR Information

  • APAR number

    IV35825

  • Reported component name

    PROSPECT

  • Reported component ID

    5724T0500

  • Reported release

    807

  • Status

    CLOSED ISV

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-24

  • Closed date

    2013-10-29

  • Last modified date

    2013-10-29

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Prospect

Software version:

807

Reference #:

IV35825

Modified date:

2013-10-29

Translate my page

Machine Translation

Content navigation