PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 09/23/2013 8:11 AM by  Ronnie
Help..Not getting anywhere with Lawson Support...DME no data
 12 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Ronnie
Business Analyst
BMH
Veteran Member
(341 points)
Veteran Member
Posts:143


Send Message:

--
09/17/2013 11:45 AM
    We recently had our environment updated from 9.0.1.5 to 9.0.1.9 and suddenly DME queries that we run that have always worked and pulled data are suddenly running and returning a message of the specified query returned no data. This only happened after our update. support has had me update our IOSconfig.xml file with record count number limit, and recycle websphere etc. So far this seems to be when we are doing this on the PRTIME table. Why would we now get no results when we always have in the past for this query?

    HELP!!!!
    John Henley
    Private
    Private
    Senior Member
    (9587 points)
    Senior Member
    Posts:3213


    Send Message:

    --
    09/17/2013 11:52 AM
    Are you also pulling data from related tables?
    Thanks for using the LawsonGuru.com forums!
    John
    Greg Moeller
    Private
    Private
    Veteran Member
    (3876 points)
    Veteran Member
    Posts:1378


    Send Message:

    --
    09/17/2013 11:59 AM
    We had something similar happen to us when we went from ESP5 to 11. (with RQC). The tech that I got seemed to indicate this happens a lot with environment updates.
    Here is what the tech had me do to resolve the issue. (RQC was not returning any templates...)
    1) cd LAWDIR/productline/map/default
    2) remove the RQIA.* files rm RQIA.*
    3) cd LAWDIR/productline/rqsrc
    4) remove the RQIA.xml file rm RQIA.xml
    5) run the following commands :
    qcompile productline rq rqia
    scrgen productline rq rqia
    xscrgen.exe productline rqia

    I repeated for most of the RQI? programs.

    Keep in mind that the program file(s) that you concentrate on will likely be different.
    John Henley
    Private
    Private
    Senior Member
    (9587 points)
    Senior Member
    Posts:3213


    Send Message:

    --
    09/17/2013 12:10 PM
    Greg, this doesn't sound like anything related to addins...are you saying that was a symptom in your case?
    Thanks for using the LawsonGuru.com forums!
    John
    BarbLR
    Systems Architect
    Munson Healthcare
    Veteran Member
    (888 points)
    Veteran Member
    Posts:306


    Send Message:

    --
    09/17/2013 12:22 PM
    Is your query timing out? We have this problem in both DME queries and Add-ins after upgrading to 9.0.1.10. It happens on large tables when there is "or" logic in the query (e.g. deduction code A or deduction code B).
    Greg Moeller
    Private
    Private
    Veteran Member
    (3876 points)
    Veteran Member
    Posts:1378


    Send Message:

    --
    09/17/2013 12:38 PM
    Yes, Addins didn't work, RQC didn't work, even some of the on-line programs would return either different data or no data...
    John Henley
    Private
    Private
    Senior Member
    (9587 points)
    Senior Member
    Posts:3213


    Send Message:

    --
    09/17/2013 1:16 PM
    Ronnie, when you updated from 9.0.1.5 to 9.0.1.9 did you also load any environment patches?
    Thanks for using the LawsonGuru.com forums!
    John
    Ronnie
    Business Analyst
    BMH
    Veteran Member
    (341 points)
    Veteran Member
    Posts:143


    Send Message:

    --
    09/17/2013 2:04 PM
    Posted By BarbR on 09/17/2013 12:22 PM
    Is your query timing out? We have this problem in both DME queries and Add-ins after upgrading to 9.0.1.10. It happens on large tables when there is "or" logic in the query (e.g. deduction code A or deduction code B).

    We actually use Lawson Managed services so I am not sure if any patches were loaded, but there was not supposed to be that I know of.

    The queries were timing out at first on MY pc, but i then remembered I could change this setting and then I was able to get it run longer, but it will just return no DATA when it should be returning data.

    Yes, are using other tables as well....such as Employee table to pull name and adress info.


    Ronnie
    Business Analyst
    BMH
    Veteran Member
    (341 points)
    Veteran Member
    Posts:143


    Send Message:

    --
    09/17/2013 2:10 PM
    Posted By John Henley on 09/17/2013 12:10 PM
    Greg, this doesn't sound like anything related to addins...are you saying that was a symptom in your case?

    Thanks, I am not sure I want to do this since it is dealing with files that process our payroll functions.

    I looked in the directory just checking things out and do not see ones for PR that would maybe be PRIA, but I see similar files and XML files to what you mentioned with RQIA.


    John Henley
    Private
    Private
    Senior Member
    (9587 points)
    Senior Member
    Posts:3213


    Send Message:

    --
    09/17/2013 2:19 PM
    Ah, the irony. You use Lawson managed services, but you can't get any help. Sorry, just had to say that...

    Are you using selection criteria that is not part of an index?
    You probably should inquire as to whether or not the patch for your platform has been installed that includes JT-463289.
    Thanks for using the LawsonGuru.com forums!
    John
    Ronnie
    Business Analyst
    BMH
    Veteran Member
    (341 points)
    Veteran Member
    Posts:143


    Send Message:

    --
    09/17/2013 2:59 PM
    Posted By John Henley on 09/17/2013 02:19 PM
    Ah, the irony. You use Lawson managed services, but you can't get any help. Sorry, just had to say that...

    Are you using selection criteria that is not part of an index?
    You probably should inquire as to whether or not the patch for your platform has been installed that includes JT-463289.
    What is JT-463289? I have been looking on the Infor site but cant seem to find that one.

    Ronnie
    Business Analyst
    BMH
    Veteran Member
    (341 points)
    Veteran Member
    Posts:143


    Send Message:

    --
    09/18/2013 12:23 PM
    we are going to schedule this JT in our TEST env. Maybe this will fix the issue?
    Ronnie
    Business Analyst
    BMH
    Veteran Member
    (341 points)
    Veteran Member
    Posts:143


    Send Message:

    --
    09/23/2013 8:11 AM
    well I was actually told to hold off on this JT, because our DME's work fine in TEST. So, if we apply in TEST, it wont matter because they have always worked in test. Only in PROD are we having trouble with these DME's that reference the PRTIME table. This did not happen until our environment update. Any idea on what to check?
    You are not authorized to post a reply.