Re: coding issue

From: Hemant K Chitale <hemantkchitale_at_gmail.com>
Date: Fri, 16 Nov 2018 12:04:30 +0800
Message-ID: <CAMNBsZvQmZvSkDKzH_WocSTJXOU2MbmFy74Nh4p1HAmmJsitPg_at_mail.gmail.com>



This reminds of the description of automated testing in this post :

https://news.ycombinator.com/item?id=18442941

Hemant K Chitale

On Fri, Nov 16, 2018 at 7:38 AM Tanel Poder <tanel_at_tanelpoder.com> wrote:

> Not exactly the same thing, but some time ago I hit the bug 20513257
> ( kfod.bin: No such file or directory error on Linux )
>
> Solution, open <GridHome>/bin/kfod in an editor and change:
>
> OHOME=%ORACLE_HOME%
>
> To:
> OHOME=$ORACLE_HOME
>
> *On Linux!*
>
> I wonder what kind of automated tests would pass on Linux when some
> critical environment variable values go missing... but perhaps the
> hardcoded paths elsewhere in the script explain why the tests pass ... as
> long as your grid home *happens to be *the hardcoded one, it's all good...
>
> --
> Tanel Poder
> https://blog.tanelpoder.com/seminar/
>
>
> On Wed, Nov 14, 2018 at 11:10 AM Andrew Kerber <andrew.kerber_at_gmail.com>
> wrote:
>
>> So I ran into something strange the other day when I was installing an
>> oracle 18c home. I looked at the file, and found this gem hardcoded into
>> kfod in the GI home zip file:
>>
>> OHOME=/u01/app/18.0.0/grid
>> ORACLE_HOME=${OHOME}
>> export ORACLE_HOME
>>
>> exec $OHOME/bin/kfod.bin "$_at_"
>>
>> Perhaps Oracle should work on their coding just a bit.
>>
>> --
>> Andrew W. Kerber
>>
>> 'If at first you dont succeed, dont take up skydiving.'
>>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Nov 16 2018 - 05:04:30 CET

Original text of this message