Results 1 to 6 of 6
  1. #1
    Join Date
    Dec 2004
    Posts
    3

    Unanswered: Oracle Clinical: NORMLAB2 errors

    I can not generate the views for NORMLAB2. It will not generate for test or for stable. My labs are properly linked and assigned. When I attempt to generate the view it tells me there is an .out file for the psub job. It does not create an .out file but I get this error in the .log file

    tarting 3GL command...
    Enter value for clinical_study_id:
    User requested Interrupt or EOF detected.
    Exit status of 3GL=1, Pid=2762
    Completed with FAILURE status.

    Anyone else ever encountered this?

  2. #2
    Join Date
    Jan 2004
    Location
    Croatia, Europe
    Posts
    4,094
    Provided Answers: 4
    I'm really sorry, but I must admit I don't understand what you're talking about ... For stable? Your labs are linked? psub job? tarting (starting?) 3GL command? If there wasn't the subject, I'd never say it's about Oracle ...

    Could you explain it a little bit more? Until someone else finds the solution for your problem?

  3. #3
    Join Date
    Jul 2006
    Posts
    2

    Oracle clinical Normlab2

    We recently upgraded OC from 403 to 4051
    We get the same error.

    Found line in oratab file for database "VOC19".
    echo Code env "45" found in opa_settings for database "VOC19".
    echo Database "VOC19" found in oratab.
    echo Setting ORACLE_HOME and ORACLE_SID for local database "VOC19"
    echo Setting RXC_ROOT
    echo ...Done.
    LOGNAME=tester1
    Connected to database.
    Job started.
    Database state set to P
    Starting 3GL command...
    Enter value for clinical_study_id:
    User requested Interrupt or EOF detected.
    Exit status of 3GL=1, Pid=24452
    Completed with FAILURE status.

    Let us know if you have any idea as to why this may be happening. Thanks.

  4. #4
    Join Date
    Dec 2004
    Posts
    3
    oh wow! That was two years ago. I think the labnorm module wasn't installed correctly or the correct privileges weren't granted. All I know is that the DBA changed something and it worked like a charm. I will follow up with her, if she still works there, and see if I can't get some advice from her.

    Are you allowed to post to metalink? It has been 1 1/2 years since 4.05 came out so I imagine there is a wealth of data about this issue. If no one has access to metalink I would suggest that it is worth the price, OC is a strange creature, and you can't maintain it without the solutions posted on it.

    p.s. I used to live where there were a lot of OC jobs and I now I live in southern Florida. Do you know of any positions down there?

    Thanks, j

  5. #5
    Join Date
    Jul 2006
    Posts
    2

    Ravi

    Thanks for replying soon.
    There are many OC jobs available in the east coast and california now.
    Metalink is very useful.
    But it has very little on Normlab2 as it is not oracle product. I typed this
    error in all search engines.
    Only google was able to provide your posting and for the error.
    We installed OC 4.5 and we are experiencing this problem with normlab. If
    you can find from the DBA, it will be helpful.
    Your name? Are you working in OC in florida?
    Thank you,
    Ravi

  6. #6
    Join Date
    Dec 2004
    Posts
    3
    That's right , I forgot that it isn't an Oracle product.

    Unfortunately, I can't get in touch with the DBA. Perhaps try re-installing the normlab module. Also review what sort of priveleges the different accounts have. Additionally, try checking the rxc account. PSUB sends rxc an e-mail when it is restarted, but funny things happen to PSUB if there is any e-mail in the RXC account.

    It has been a while since I have used OC, I am doing mostly SAS work in Florida. I will try some of my other DBA friends and see what they have to say. I remember how frustrating NORMLAB is, at one job we gave up on it and ran the lab norms in sas.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •