General discussion

Locked

SQLNet.ORA and Connect Internal

By jccerami ·
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?

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

SQLNet.ORA and Connect Internal

by craig_hochgraef In reply to SQLNet.ORA and Connect In ...

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.

Collapse -

SQLNet.ORA and Connect Internal

by jccerami In reply to SQLNet.ORA and Connect In ...

Poster rated this answer

Collapse -

SQLNet.ORA and Connect Internal

by jccerami In reply to SQLNet.ORA and Connect In ...

This question was closed by the author

Back to Networks Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums