ORA-12159 TNS:trace file not writeable
This is an Oracle Database Server Message. This can be generated by the Oracle Database when running any Oracle program.
What is the cause of ORA-12159 from Oracle 11g ?
The trace file to be generated is not writeable by this user.
How to deal with ORA-12159 from Oracle 11g ?
If the user does not have write permissions in the directory to which the trace file will be written, contact an administrator to get the proper permissions or set the TRACE_DIRECTORY_CLIENT parameter in the net profile (SQLNET.ORA file) to a directory the user can write to.
Contacting Oracle support services ?
Some messages recommend contacting Oracle Support Services to report a problem. Please go here for more information : Oracle Support.
Linked Error Messages
- ORA-12151 TNS:received bad packet type from network layer
- ORA-12152 TNS:unable to send break message
- ORA-12153 TNS:not connected
- ORA-12154 TNS:could not resolve the connect identifier specified
- ORA-12155 TNS:received bad datatype in NSWMARKER packet
- ORA-12156 TNS:tried to reset line from incorrect state
- ORA-12157 TNS:internal network communication error
- ORA-12158 TNS:could not initialize parameter subsystem
- ORA-12160 TNS:internal error: Bad error number
- ORA-12161 TNS:internal error: partial data received
- ORA-12162 TNS:net service name is incorrectly specified
- ORA-12163 TNS:connect descriptor is too long
- ORA-12164 TNS:Sqlnet.fdf file not present
- ORA-12165 TNS:Trying to write trace file into swap space.
- ORA-12166 TNS:Client can not connect to HO agent.