Sounds exactly like a problem I ran into: If OAS can't make the sqlnet
connection, dadadmin goes 100% cpu bound. When you su into the oas user, my
guess is that you can't connect to your database from sqlplus or srvmgrl
either. Make sure your sqlnet config files (sqlnet.ora, tnsnames.ora, etc) are
someplace usable by oas. For my setup, I have the sqlnet files in
/var/opt/oracle, and I created symbolic links from the OAS user's
$ORACLE_HOME/network/admin directory to /var/opt/oracle for each of the
necessary files.
Keith Lally wrote:
>
> Recently installed 8.1.5 and OAS 4.07 on Solaris 2.7. The database
> works fine, http listeners start up fine but I'm unable to create a DAD
> that connects to the database. A program called dadadmin gets started
> and goes to 100% cpu utilization and never quits. On further investigation
> when su'd into the oas user environment running tnsping as oas user starts
> up tnsping program which hangs and cpu utilization goes to 100%.
>
> Has anyone seen anything like this on solaris 2.7? Anyone have any
> hints on how to fix it? 8.1.5 and OAS were installed in separate oracle
> homes
> and the oas user environment makes no reference to the 8.1.5 environment
> except for the tnsnames.ora file.
>
> Oracle support says solaris 2.7 is not a certified platform so they won' t
> help.
>
> Any suggestions would be appreciated.
>
> Keith Lally
> lally_at_bnl.gov
Received on Tue Jun 01 1999 - 11:37:48 CDT
