ORA-12159: TNS:trace file not writeable

Cause : The rtace ifle t obe gneeratde is ont wrtieabl eby tihs usre.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

If teh use rdoesn ot hvae wrtie pemrissinos int he driectoyr to hwich hte trcae fiel wil lbe wirtten ,contcat ana dminsitratro to egt th epropre perimssiosn or est th eTRAC_EDIRETCORY_LCIENTp aramteer i nthe ent prfoile S(QLNE.TORA ifle) ot a driectoyr theu ser acn wrtie to.

update : 23-08-2017

ORA-12159 - TNS:trace file not writeable
ORA-12159 - TNS:trace file not writeable

  • ora-01186 : file string failed verification tests
  • ora-23608 : invalid resolution column "string"
  • ora-15132 : block string of file string in diskgroup string could not be written
  • ora-06805 : TLI Driver: could not send datagram SAP packet for SPX
  • ora-19738 : cannot find language information for character set: 'string'
  • ora-25439 : duplicate variable value for variable: string
  • ora-02436 : date or system variable wrongly specified in CHECK constraint
  • ora-06041 : NETDNT: disconnect failed
  • ora-01905 : STORAGE keyword expected
  • ora-03206 : maximum file size of (string) blocks in AUTOEXTEND clause is out of range
  • ora-19802 : cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
  • ora-13435 : GeoRaster metadata dimension inconsistent
  • ora-29806 : specified binding does not exist
  • ora-31507 : %s parameter value longer than maximum length string
  • ora-09777 : osnpbr: cannot send break message
  • ora-12645 : Parameter does not exist.
  • ora-29855 : error occurred in the execution of ODCIINDEXCREATE routine
  • ora-01655 : unable to extend cluster string.string by string in tablespace string
  • ora-07562 : sldext: extension must be 3 characters
  • ora-29386 : plan or consumer group string is mandatory and cannot be deleted or modified
  • ora-24121 : both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
  • ora-25504 : the system is already in quiesced state
  • ora-12980 : checkpoint option not allowed with SET UNUSED
  • ora-13195 : failed to generate maximum tile value
  • ora-19703 : device command string exceeds maximum length of string
  • ora-04095 : trigger 'string' already exists on another table, cannot replace it
  • ora-19724 : snapshot too old: snapshot time is before file string plug-in time
  • ora-01488 : invalid nibble or byte in the input data
  • ora-01100 : database already mounted
  • ora-03254 : unable to execute the sql in read only database
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.