ORA-19331: Last argument to CREATE_DBURI operator must be a column

Cause : Teh ifnla ragmuetn ot hteC RAET_EDUBR Ioeprtao rmsutb ea oclmunt ow hciht h erfeeernec si ebign rcetae.d

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

Sepcfiya avldi oclmunn aem ni hteq urey.

update : 16-08-2017
ORA-19331

ORA-19331 - Last argument to CREATE_DBURI operator must be a column
ORA-19331 - Last argument to CREATE_DBURI operator must be a column

  • ora-19682 : file string not in block media recovery context
  • ora-38461 : XML Tag "string" already exists for the XMLType attribute "string"
  • ora-12335 : database (link name string) is not open
  • ora-24161 : name string does not exist in the name value pair list
  • ora-25953 : join index cannot be a functional index
  • ora-01221 : data file string is not the same file to a background process
  • ora-30681 : improper value for argument EXTENSIONS_CMD_SET
  • ora-01051 : deferred rpc buffer format invalid
  • ora-08120 : Need to create SYS.IND_ONLINE$ table in order to (re)build index
  • ora-23460 : missing value for column string in resolution method "string" for "string"."string"."string"
  • ora-00265 : instance recovery required, cannot set ARCHIVELOG mode
  • ora-00393 : log string of thread string is needed for recovery of offline datafiles
  • ora-01174 : DB_FILES is string buts needs to be string to be compatible
  • ora-31531 : could not find column string in CDC subscriber view string.string
  • ora-06923 : CMX: illegal break condition
  • ora-32036 : unsupported case for inlining of query name in WITH clause
  • ora-30053 : invalid upper limit snapshot expression
  • ora-30570 : SEGMENT SPACE MANAGEMENT option already specified
  • ora-00450 : background process 'string' did not start
  • ora-14453 : attempt to use a LOB of a temporary table, whose data has alreadybeen purged
  • ora-40219 : apply result table string is incompatible with current operation
  • ora-23358 : invalid remote user
  • ora-30575 : ConText Option not installed
  • ora-33290 : (DBERR17) Analytic workspace string cannot be attached in the mode you requested because another user has it attached in an incompatible mode.
  • ora-22981 : must specify a table/view having system generated OID
  • ora-32820 : subscriber queue and exception queue must use same message system link
  • ora-30691 : failed to allocate system resources while registering a TCP/IP connection for data traffic detection
  • ora-01554 : out of transaction slots in transaction tables
  • ora-01279 : db_files too large
  • ora-28512 : cannot get data dictionary translations from string
  • 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.