Derby
  1. Derby
  2. DERBY-2189

Derby scripts does not work in C-shell even after setting DERBY_HOME

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Invalid
    • Affects Version/s: 10.2.1.6
    • Fix Version/s: None
    • Component/s: Demos/Scripts
    • Labels:
      None
    • Environment:
      Linux

      Description

      Even after setting DERBY_HOME to the right path the scripts in bin/ complain of the env variable DERBY_HOME not been set.

      swift rajderby/db-derby-10.2.2.0-bin> echo $DERBY_HOME
      /local1/LINUX/rajderby/db-derby-10.2.2.0-bin
      swift rajderby/db-derby-10.2.2.0-bin> bin/ij
      Error: DERBY_HOME is not set. Please set the DERBY_HOME environment variable
      to the location of your Derby installation.

      The scripts work just fine in the 'bash' and 'sh' environments, hence marking this issue Trivial - enough for tracking purposes only.

        Activity

        Hide
        Rajesh Kartha added a comment -

        I had tried with both setenv and set earlier. Not sure what was wrong, but it is true setenv should work in C-shell.

        In any case, I ran it now on a different set of machines, Solaris 10 and SLES 10.0, and the sripts does work with setenv.
        Hence marking this issue as Invalid.

        Show
        Rajesh Kartha added a comment - I had tried with both setenv and set earlier. Not sure what was wrong, but it is true setenv should work in C-shell. In any case, I ran it now on a different set of machines, Solaris 10 and SLES 10.0, and the sripts does work with setenv. Hence marking this issue as Invalid.
        Hide
        Knut Anders Hatlen added a comment -

        How did you set DERBY_HOME? If you use "set DERBY_HOME=...", it will be a local variable which is not visible to subprocesses. I tested with "setenv DERBY_HOME ..." and it worked.

        Show
        Knut Anders Hatlen added a comment - How did you set DERBY_HOME? If you use "set DERBY_HOME=...", it will be a local variable which is not visible to subprocesses. I tested with "setenv DERBY_HOME ..." and it worked.

          People

          • Assignee:
            Unassigned
            Reporter:
            Rajesh Kartha
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development