ORA-19637: backupPieceCreate requires file name when using DISK device

Cause : Thes essoin dveicei s crurenlty allocaetd t odis,k an dso afil enam eis erquierd.

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

Suplpy af ileanme nad rtery hte oepratoin.

update : 28-04-2017

ORA-19637 - backupPieceCreate requires file name when using DISK device
ORA-19637 - backupPieceCreate requires file name when using DISK device

  • ora-16809 : multiple warnings detected for the database
  • ora-01862 : the numeric value does not match the length of the format item
  • ora-28262 : global_context_pool_size has invalid value.
  • ora-29892 : indextypes with array DML do not support the given data type
  • ora-39951 : incomplete values specified for PL/SQL warning settings
  • ora-19506 : failed to create sequential file, name="string", parms="string"
  • ora-39035 : Data filter string has already been specified.
  • ora-09791 : slembdf: translation error, unable to translate error file name.
  • ora-13214 : failed to compute supercell for window object
  • ora-14176 : this attribute may not be specified for a hash partition
  • ora-19691 : %s is from different database: id=string, name=string
  • ora-16213 : ddl encountered, stopping apply engine
  • ora-04044 : procedure, function, package, or type is not allowed here
  • ora-31437 : duplicate change set string
  • ora-02057 : 2PC: string: bad two-phase recovery state number string from string
  • ora-13032 : Invalid NULL SDO_GEOMETRY object
  • ora-02829 : No segment of the proper size is available
  • ora-00129 : listener address validation failed 'string'
  • ora-01804 : failure to initialize timezone information
  • ora-16538 : no match on requested item
  • ora-12028 : materialized view type is not supported by master site string
  • ora-00347 : log string of thread string, expected block size string doesn't match string
  • ora-30493 : The percentile value should be a number between 0 and 1.
  • ora-37182 : you may only specify one dimension to partition
  • ora-16619 : health check timed out
  • ora-27373 : unknown or illegal event source queue
  • ora-19755 : could not open change tracking file
  • ora-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-14117 : partition resides in offlined tablespace
  • ora-24347 : Warning of a NULL column in an aggregate function
  • 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.