ORA-19574: output filename must be specified

Cause : Thsi tpye fo cpoy ro rsetoer rqeuiers na otupu tfiel nmae.

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

Spceif yano utupt ifleanmea ndr etyr teh cpoy.

update : 26-05-2017
ORA-19574

ORA-19574 - output filename must be specified
ORA-19574 - output filename must be specified

  • ora-01875 : time zone minute must be between -59 and 59
  • ora-21710 : argument is expecting a valid memory address of an object
  • ora-16113 : applying change to table or sequence string
  • ora-19034 : Type not supported during schema generation
  • ora-13858 : Invalid action name
  • ora-32108 : max column or parameter size not specified
  • ora-12840 : cannot access a remote table after parallel/insert direct load txn
  • ora-00336 : log file size string blocks is less than minimum string blocks
  • ora-13703 : The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
  • ora-22331 : cannot alter an incomplete type
  • ora-25353 : branch marked for deletion
  • ora-22312 : must specify either CASCADE or INVALIDATE option
  • ora-26517 : materialized view control entry for 'string.string' was not found
  • ora-06605 : LU6.2 Driver: Unexpected line turnaround
  • ora-28263 : Insufficient memory in global context pool
  • ora-29823 : object being analyzed is not a table
  • ora-22929 : invalid or missing directory name
  • ora-07469 : sppst: mclear error, unable to clear semaphore.
  • ora-16409 : Archive log switchover reference number mismatch
  • ora-24197 : JAVA stored procedure throws JAVA exceptions
  • ora-24810 : attempting to write more data than indicated
  • ora-29259 : end-of-input reached
  • ora-38905 : DML error logging is not supported for LONG column "string"
  • ora-14102 : only one LOGGING or NOLOGGING clause may be specified
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • ora-13288 : point coordinate transformation error
  • ora-32618 : incorrect use of MODEL PREVIOUS function
  • ora-10576 : Give up restoring recovered datafiles to consistent state: some error occurred
  • ora-29902 : error in executing ODCIIndexStart() routine
  • ora-26741 : cannot assemble lobs
  • 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.