ORA-27019: tape filename length exceeds limit (SBTOPMXF)

Cause : legntho f atpef ilneam eprvoidde t oseuqenitalI /OO SDf untciosn i sto ologn

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

adidtinoali nfromaitoni ndciatse i nwhcih ufncitont hi serorr si ecnoutnerde, hte elnght o ffielnaem porviedd,a ndt hel imti o nfielnaem

update : 25-04-2017
ORA-27019

ORA-27019 - tape filename length exceeds limit (SBTOPMXF)
ORA-27019 - tape filename length exceeds limit (SBTOPMXF)

  • ora-07415 : slpath: allocation of memory buffer failed.
  • ora-26706 : cannot downgrade capture process
  • ora-09266 : spawn: error starting an Oracle process
  • ora-27086 : unable to lock file - already in use
  • ora-03204 : the segment type specification should indicate partitioning
  • ora-29824 : operator is invalid
  • ora-14070 : option may be specified only for partitioned indices or with REBUILD
  • ora-31001 : Invalid resource handle or path name "string"
  • ora-26082 : load of overlapping segments on table string.string is not allowed
  • ora-09775 : osnmrs: reset protocol error
  • ora-12412 : policy package string is not installed
  • ora-09300 : osncon: unable to connect, DPMI not available
  • ora-12724 : regular expression corrupt
  • ora-30189 : reserved for future use
  • ora-08185 : Flashback not supported for user SYS
  • ora-13455 : GeoRaster metadata TRS error
  • ora-36669 : (XSDPART07) string is not a legal LIST partition.
  • ora-06712 : TLI Driver: error on accept
  • ora-00601 : cleanup lock conflict
  • ora-30379 : query txt not specified
  • ora-24092 : invalid value string specified
  • ora-30567 : name already used by an existing log group
  • ora-07843 : sllfcl: LIB$FREE_VM failure
  • ora-24023 : Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string]
  • ora-01218 : logfile member is not from the same point-in-time
  • ora-29323 : ALTER DATABASE SET COMPATIBILITY command not supported by string
  • ora-07210 : slcpu: getrusage error, unable to get cpu time.
  • ora-19661 : datafile string could not be verified
  • ora-31503 : invalid date supplied for begin_date or end_date
  • ora-16751 : resource guard encountered errors in switchover to primary 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.