ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST

Cause : Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.

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

No action is required.

update : 25-06-2017

ORA-16400 - quota attributes are not allowed with DB_RECOVERY_FILE_DEST
ORA-16400 - quota attributes are not allowed with DB_RECOVERY_FILE_DEST

  • ora-13776 : User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.
  • ora-10947 : trace name context forever
  • ora-31664 : unable to construct unique job name when defaulted
  • ora-30108 : invalid positional parameter value 'string'
  • ora-19241 : XP0021 - cast to type string failed
  • ora-38706 : Cannot turn on FLASHBACK DATABASE logging.
  • ora-23366 : integer value string is less than 1
  • ora-28231 : no data passed to obfuscation toolkit
  • ora-07860 : osnsoi: error setting up interrupt handler
  • ora-38417 : attribute set string does not exist
  • ora-22957 : NULL is an invalid input to powermultiset and COLLECT functions
  • ora-00034 : cannot string in current PL/SQL session
  • ora-08266 : create_ora_addr: cannot register name in nameserver
  • ora-25154 : column part of USING clause cannot have qualifier
  • ora-13063 : relationship information table is missing data for feature table [string]
  • ora-31529 : could not find publication for CDC subscriber view string.string
  • ora-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-19913 : unable to decrypt backup
  • ora-32512 : type 'string' is unknown
  • ora-19593 : datafile number string already included as string
  • ora-01874 : time zone hour must be between -12 and 14
  • ora-07633 : smsdbp: illegal protection value
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-02266 : unique/primary keys in table referenced by enabled foreign keys
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-14074 : partition bound must collate higher than that of the last partition
  • ora-07284 : sksaprd: volume size specification not terminated properly.
  • ora-37000 : (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.
  • ora-25014 : cannot change the value of a PARENT reference variable
  • ora-31600 : invalid input value string for parameter string in function 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.