ORA-01278: error creating file 'string'

Cause : An operating system error occurred while attempting to create a trace file specified in the command ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename'.

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

Check the error stack for more detailed information.

update : 27-04-2017
ORA-01278

ORA-01278 - error creating file 'string'
ORA-01278 - error creating file 'string'

  • ora-12226 : TNS:operating system resource quota exceeded
  • ora-25329 : AQ array operations not allowed on 8.0 queues
  • ora-26524 : nls subsystem initialization failure for product=string, facility=string
  • ora-30938 : No prefix defined for namespace 'string' (particle string)
  • ora-27026 : skgfrls: sbtend returned error
  • ora-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-09798 : Label comparison failed.
  • ora-14272 : only a partition with higher bound can be reused
  • ora-25284 : Invalid value string for string
  • ora-01292 : no log file has been specified for the current LogMiner session
  • ora-10919 : Default temporary tablespace group must have at least one tablespace
  • ora-04031 : unable to allocate string bytes of shared memory ("string","string","string","string")
  • ora-32141 : get method does not match the type of the parameter
  • ora-16637 : an instance failed to access the Data Guard broker configuration
  • ora-31062 : Cannot delete an unsaved resource
  • ora-37113 : OLAP API initialization error: (string)
  • ora-16151 : Managed Standby Recovery not available
  • ora-02175 : invalid rollback segment name
  • ora-23303 : application raised generic exception during deferred RPC
  • ora-38742 : Flashback log file has incorrect log reset status.
  • ora-01954 : DEFAULT ROLE clause not valid for CREATE USER
  • ora-02807 : Allocation of memory for I/O vectors failed.
  • ora-02759 : Not enough request descriptors available
  • ora-22897 : no scope clause specified for user-defined REF column "string"
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • ora-15111 : conflicting or duplicate STRIPE options
  • ora-13112 : cannot delete topo_geometry layer [string] from topology
  • ora-26029 : index string.string partition string initially in unusable state
  • ora-24309 : already connected to a server
  • ora-14053 : illegal attempt to modify string in string statement
  • 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.