Uploaded image for project: 'CORAL and COOL'
  1. CORAL and COOL
  2. CORALCOOL-666

Oracle DIAGNOSTIC_DEST directory created in user $HOME on client (following ORA-24550)

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: CORAL
    • Labels:
      None

      Description

      Stefan reported that a lot of log files are created in the client's $HOME in a directory oradiag_<username>. I also saw this, for instance on the coralserver node.

      Date: Mon, 16 Nov 2009 10:59:27 +0100
      From: Stefan Roiser <Stefan.Roiser@cern.ch>
      To: Andrea Valassi <Andrea.Valassi@cern.ch>
      Subject: log files

      Hi Andrea,

      I found the lcgnight afs home volume full today. It seems there are a lot of log files from oracle? E.g.

      oradiag_lcgnight/diag/clients/user_lcgnight/host_2334089177_11/cdump/core_30211

      around 450MB in total. Two questions

      - Can I remove them?
      - Could the creation of those in $HOME be avoided, if they stem from db tests?

      Thanks

      Stefan

        Attachments

          Activity

          Hide
          valassi Andrea Valassi added a comment -

          I keep this open at lowest priority for the moment. That is to say: for the moment we keep it as it is (ADR dumps will go to $HOME).

          Show
          valassi Andrea Valassi added a comment - I keep this open at lowest priority for the moment. That is to say: for the moment we keep it as it is (ADR dumps will go to $HOME).
          Hide
          valassi Andrea Valassi added a comment -

          I can also confirm that the ORA-24550 (and the oradiag dump from ADR) only happen if the client (random cycler test) is running oracle 11g. With oracle 10g the failure is less verbose (which makes it look less catastrophic, although it probably is not - actually the extra info in oracle 11g is probably very useful!).
          Andrea

          Show
          valassi Andrea Valassi added a comment - I can also confirm that the ORA-24550 (and the oradiag dump from ADR) only happen if the client (random cycler test) is running oracle 11g. With oracle 10g the failure is less verbose (which makes it look less catastrophic, although it probably is not - actually the extra info in oracle 11g is probably very useful!). Andrea
          Hide
          valassi Andrea Valassi added a comment -

          I have created an sqlnet.ora file in /afs/cern.ch/sw/lcg/external/oracle/11.2.0.1.0/admin/
          with the two lines to disable the ADR.

          Oracle recommends using different sqlnet.ora for 10g and 11g clients, so I did not modify the central sqlnte.ora which so f was used for all client applications (9i and 10g).

          Thanks to Ana, the LCG_Interface for oracle has been modified, http://lcgcmt.cvs.cern.ch/cgi-bin/lcgcmt.cgi/lcgcmt/LCG_Interfaces/oracle/cmt/requirements.diff?r1=1.20&r2=1.21
          This is used for LCGCMT-preview (for th enext 57x release?), but not (yet?) for the 56 patches used for 56d.

          Bug closed.
          Andrea

          Show
          valassi Andrea Valassi added a comment - I have created an sqlnet.ora file in /afs/cern.ch/sw/lcg/external/oracle/11.2.0.1.0/admin/ with the two lines to disable the ADR. Oracle recommends using different sqlnet.ora for 10g and 11g clients, so I did not modify the central sqlnte.ora which so f was used for all client applications (9i and 10g). Thanks to Ana, the LCG_Interface for oracle has been modified, http://lcgcmt.cvs.cern.ch/cgi-bin/lcgcmt.cgi/lcgcmt/LCG_Interfaces/oracle/cmt/requirements.diff?r1=1.20&r2=1.21 This is used for LCGCMT-preview (for th enext 57x release?), but not (yet?) for the 56 patches used for 56d. Bug closed. Andrea
          Hide
          valassi Andrea Valassi added a comment -

          Rename to mention ORA-24550.

          Show
          valassi Andrea Valassi added a comment - Rename to mention ORA-24550.
          Hide
          valassi Andrea Valassi added a comment -

          For the record: the Oracle signal handler producing these ORA-24550 can probably be completed disabled (e.g. if one wants to use the ROOT signal handler) by setting DIAG_SIGHANDLER_ENABLED=FALSE. Thanks to Luca for the suggestion.
          Andrea

          Show
          valassi Andrea Valassi added a comment - For the record: the Oracle signal handler producing these ORA-24550 can probably be completed disabled (e.g. if one wants to use the ROOT signal handler) by setting DIAG_SIGHANDLER_ENABLED=FALSE. Thanks to Luca for the suggestion. Andrea

            People

            • Assignee:
              valassi Andrea Valassi
              Reporter:
              valassi Andrea Valassi
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: