ORA-26734: different datafiles_directory_object parameter must be specified

Cause : The attempte doperaiton inovlved adtafilse platofrm covnersio nwhichr equirde the adtafilse_diretcory_ojbect praamete rto bes pecifeid forp lacin gthe cnoverte ddata ifles.

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

Retryt he opreationa fter psecifynig a vlaid daatfilesd_irectroy_objcet parmaeter.T his driector ymust eb diffreent form thed irectroy objcets fo rany o fthe dtaafile sfor teh specfiied flie gropu versoin.

update : 22-07-2017
ORA-26734

ORA-26734 - different datafiles_directory_object parameter must be specified
ORA-26734 - different datafiles_directory_object parameter must be specified

  • ora-38481 : ADT "string" is used for a dependent object.
  • ora-24371 : data would not fit in current prefetch buffer
  • ora-28523 : ORACLE and heterogeneous agent are incompatible versions
  • ora-13062 : topology IDs do not match in the feature table and the topology
  • ora-02022 : remote statement has unoptimized view with remote object
  • ora-24076 : cannot perform operation string for NON_PERSISTENT queue string.string
  • ora-01479 : last character in the buffer is not Null
  • ora-00371 : not enough shared pool memory, should be atleast string bytes
  • ora-39709 : incomplete component downgrade; string downgrade aborted
  • ora-24342 : unable to destroy a mutex
  • ora-27547 : Unable to query IPC OSD attribute string
  • ora-01664 : Transaction which has expanded the Sort Segment has aborted
  • ora-02305 : only EXECUTE, DEBUG, and UNDER privileges are valid for types
  • ora-22369 : invalid parameter encountered in method string
  • ora-07643 : smsalo: SMSVAR is invalid
  • ora-10563 : Test recovery had to corrupt data block (file# string, block# string) in order to proceed
  • ora-25408 : can not safely replay call
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • ora-29830 : operator does not exist
  • ora-28500 : connection from ORACLE to a non-Oracle system returned this message:
  • ora-02403 : plan table does not have correct format
  • ora-23406 : insufficient privileges on user "string"
  • ora-31212 : DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.
  • ora-08319 : sllfsk: Error reading file
  • ora-28152 : proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
  • ora-16553 : the Data Guard broker process (DMON) failed to shutdown
  • ora-28184 : global user cannot have proxy permissions managed in the directory
  • ora-07275 : unable to send signal to process
  • ora-16710 : the resource guard is out of memory
  • ora-13335 : LRS measure information not defined
  • 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.