Discussion Locked

SQLNet.ORA and Connect Internal

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We're running Oracle 8.1.5 on HP-UX 10.20. In order to change the location Oracle was writing it's log and trace files to we created a SQLNet.ORA file with the necessary parameters. The next time we tried to start SVRMGRL and "connect internal" svrmgr would ask for a password. After we removed the SQLNet.ORA, we were no longer asked for the password. Why is svrmgr doing this? Is there a way to have the sqlnet.ora file and not be asked for a password?

3 replies

by craig_hochgraef

I suggest that you redirect the log and trace files via the database's init.ora file by updating the background_dump_dest and log_archive_dest to the new path. Then just restart the instance and not bother with the sqlnet.ora file.

This discussion is closed to new replies.