Re: IFS daemons will not stay up

I think this may be the same issue I had yesterday on AIX. Have a look at the log files within the $ORACLE_HOME/ifs<ver>/log dir. If its the same problem two of the logs from the IFS processes have a message about TNS permissions.

I my case the problem was that root could not invoke Oracle and connect to the database with ORACLE_SID set, it needed to go via the listener with TWO_TASK. The problem is easy to recreate with sqlplus, but the only hits I found on metalink for it were to do with NOSUID mounts and incorrect suid bit on the oracle executable. These didn't fit the problem, so I've raised a TAR.

If your problem matches, then you should be able to work around it be amending the ifs.env (I think thats the name) in the ifs<ver>/bin dir to use TWO_TASK instead of the ORACLE_SID. If I've got the name wrong, check the ifsstart script. The env file is sourced quite early on.

Hope this helps.

Darryl Snedeker wrote:

> I've got TAR's open on this issue ,but I'm not encouraged with the line of
> questioning and progress to date.
>
> I'm attempting to run iFS against an 8.1.7 database on a Solaris 2.6 machine
> which has 4GB of memory. I successfully start (ifsstart) the ifs background
> processes as root, but these processes eventually die with the following
> messages:
>
> Unable to start iFS ServerManager
> Invalid credentials specified
>
> Unable to start iFS ServerManager
> Invalid credentials specified
>
> In addition, even while the processes are running, I cannot access the admin
> port (1717).
>
> I've run through the configuration tool (ifsconfig) numerous times and to no
> avail.
>
> Any suggestions, tips, or solutions would be greatly appreciated.
>
> -Darryl
  Received on Sat Feb 17 2001 - 10:10:55 CET