Re: ORA-01031 following install of 8.1.7.4 patch

"Steve Ball" <steve_at_sdball.com> wrote in message news:9097d0f0.0309120118.7ffd924e_at_posting.google.com...
> Dave,
>
> Many thanks for your reply - spot on.
>
> I also eventually managed to find the info I required - from this
> metalink article - from a previous poster [Andrea Salzano, May 21 2003
> in group it.comp.software.database... thanks also!]
>
> To assist future frustrated readers, I'll try and summarise the found
> problem & solution, and include as much info as possible
>
> For future purposes, the extract from this metalink note 69642.1 is
> given at the foot of the mail.
>
> Here was the cause of the problem (and hence why the metalink note -
> in particular STEP 6 - solved it.
>
> Summary of problem:
> My connect internal was prompting for a password [instead of just
> connecting] was due to a problem with UNIX groups.
> Although I was logged in as the oracle user, right group etc... I had
> had an earlier problem linking the binaries during install of patch
> 8.1.7.4.
>
> Initial Problem - problems installing the patch:
> ------------------------------------------------
>
> This problem was principally due to me *not* including the
> $ORACLE_HOME/lib64 path in the LD_LIBRARY_PATH environment variable.
>
> This caused during Oracle to have problems running the installer of
> the patch, in particular the following issues:
>
> [for these issues, look into your .../oraInventory/logs directory, in
> particular installActions.log (there may be previously named logs with
> timestamps in the name also)]
>
> Note: I ignored some of these errors using the oracle installer. Once
> install had been complete, I tried to re-run it, but it said I didn't
> need to (patches already installed)... in this case, look at the log
> and run the make files individually, at the command-line... for this,
> you'll run something like:
>
> make -f <long path to a .mk file> <target>
> e.g. make -f /...oraclepath.../network/lib/ins_net_client.mk
> client_sharedlib
>
> ... once you're sure all runs ok, you can (8.1.7+ I believe) then run
> "relink all" to relink all libraries.
>
> OK: as a result of missing lib64, I received an error in the make.log
> of
>
> if [ -d <oracle_home>/lib64] ; then \
> ; \
> fi
>
> ...error ; not expected in line 2.
>
> Looking into the ins_net_client.mk I see that this line evaluated to
> the variable $(GENCLNTSH64) and this must have been blank. I then put
> in the actual path of the genclntsh64 program, and got over that
> compilation step.
>
> The next step compained that v9 commands were being used in a non -v9
> binary in $ORACLE_HOME/rdbms/lib/config.s ...
> I was stumped here, so I copied that file from another - working
> install; ok, after that, I could then relink all binaries and my patch
> & db worked ok.
>
> Main problem - ORA-01031
> ------------------------
>
> In summary (and see step 6 of the metalink note): the config.s file
> had in it a *different* groupname to the one I was using...
>
> I edited this, re-ran
> relink all
>
> and hey presto... all worked.
>
>
>
>

IIRC the terms of Metalink access prohibit distributing it's contents on the Internet

-- 
Sybrand Bakker
Senior Oracle DBA

to reply remove '-verwijderdit' from my e-mail address