Hello!

We have a batch process developed in MKS korn shell, where we connect
to Oracle using:

....
SQL_CODE=`plus33 -s /@$ENVIRON<< SQLBLOCK
....
/
EXIT
SQLBLOCK`
....

In this case Oracle take the integral user login. And it is working
properly if we run script from the shell environment, but it fail to
connect to Oracle if we trying to run scheduled batch process.

Suppose user login is user/password. Then MKS connect to Oracle using
OPS$USER/password login. I think problem is in '$' sign, because for
Korn shell it is special character. And if we put:

....
SQL_CODE=`plus33 -s 'OPS$USER/password'@$ENVIRON<< SQLBLOCK
....
/
EXIT
SQLBLOCK`
....

It is working, but without quotes:
SQL_CODE=`plus33 -s OPS$USER/password@$ENVIRON it is fail again.

Please, advise anybody how to resolve this problem.

TIA.

Vladimir Uzlaner

"Vladimir Uzlaner" <uzlanerv@yahoo.com> schrieb im Newsbeitrag news:76fc9868.0412211229.5b2a4e7c@posting.google.c om...
> Hello!
> In this case Oracle take the integral user login. And it is working
> properly if we run script from the shell environment, but it fail to
> connect to Oracle if we trying to run scheduled batch process.
>
> Suppose user login is user/password. Then MKS connect to Oracle using
> OPS$USER/password login. I think problem is in '$' sign, because for
> Korn shell it is special character. And if we put:
You sure the cron job isn't run as root?

Lots of Greetings!
Volker

Vladimir Uzlaner wrote:
> Hello!
>
> We have a batch process developed in MKS korn shell, where we connect
> to Oracle using:
>
> ...
> SQL_CODE=`plus33 -s /@$ENVIRON<< SQLBLOCK
> ...
> /
> EXIT
> SQLBLOCK`
> ...
>
> In this case Oracle take the integral user login. And it is working
> properly if we run script from the shell environment, but it fail to
> connect to Oracle if we trying to run scheduled batch process.
>
> Suppose user login is user/password. Then MKS connect to Oracle using
> OPS$USER/password login. I think problem is in '$' sign, because for
> Korn shell it is special character. And if we put:
>
> ...
> SQL_CODE=`plus33 -s 'OPS$USER/password'@$ENVIRON<< SQLBLOCK
> ...
> /
> EXIT
> SQLBLOCK`
> ...
>
> It is working, but without quotes:
> SQL_CODE=`plus33 -s OPS$USER/password@$ENVIRON it is fail again.
>
> Please, advise anybody how to resolve this problem.
>
> TIA.
>
> Vladimir Uzlaner

Generally, a problem with missing environment variables.
Too long ago I worked with MKS (v1, I believe, over 15 years back?)
to give you a specific answer

--
Regards,
Frank van Bortel