Results 1 to 5 of 5
  1. #1
    Join Date
    Feb 2004
    Posts
    2

    Unanswered: sqlplus misconfiguration

    Hi,

    I'm trying to install an private application that opens an shell that calls sqlplus. When this shell execute it I got the following error:

    Message file sp1<lang>.msb not found
    Error 6 initializing SQL*Plus

    I'm running this application on unix, and when I call sqlplus from MY shell (bash or ksh) it works. All the configurations of ORACLE_HOME, ORACLE_SID are set on my .profile (I even tried to set the oracle's variables at /etc/profile). But when it opens from the application's shell it doesn't work. Because the application is automatic I can't configure the ORACLE_HOME when it is running.

    Does anybody have a similar problem?

    Thanks in advance.

    Luis.

  2. #2
    Join Date
    Jul 2003
    Posts
    2,296
    What user does the application log into the Unix server as?

    Why not change that users default shell?
    - The_Duck
    you can lead someone to something but they will never learn anything ...

  3. #3
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >But when it opens from the application's shell it doesn't work
    The process which get spawned inherits its environment from its parent.
    At the time the application gets started, can this process successfully start SQL*Plus?
    (I suspect not).
    On *nix the necessary environmental variables are
    ORACLE_HOME
    ORACLE_SID
    PATH
    LD_LIBRARY_PATH

  4. #4
    Join Date
    Feb 2004
    Posts
    2
    The application executes some scripts and while it is running I can't test if sqlplus starts. On the xterm were I call the application sqlplus can start normally.
    All these environment variables are set in my .profile which I suspect that is not being loaded by the shell that the application opens.

    The user that the application logs is the same user that I'm using for calling the application. I've already tried to change the default shel for bash and ksh and it remains the same problem.

    Any more sugestions? thank you for the answers.

    Luis.

  5. #5
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    Desparate times calls for desparate measures.
    You say the application "shells out" to the OS.
    I assume it is invoking a specific executable; let's call it "foobar".
    move/rename foobar foobar2
    create a shell script called "foobar" which has two lines:
    env | sort -o /tmp/foobar.env
    foobar2
    The try it again.
    After it fails, you can examine /tmp/foobar.env
    and actually SEE the contents of the failed application's environment.

    Has this EVER worked?
    If so, what's changed?

Posting Permissions

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