ORA-13836: invalid attribute value specified

Cause : An invalid attribute value was specified for an alter SQL profile operation.

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

Verify the attribute value.

update : 30-04-2017

ORA-13836 - invalid attribute value specified
ORA-13836 - invalid attribute value specified

  • ora-16818 : Fast-Start Failover suspended
  • ora-12516 : TNS:listener could not find available handler with matching protocol stack
  • ora-27475 : "string.string" must be a string
  • ora-22981 : must specify a table/view having system generated OID
  • ora-32412 : encrypted column "string" not allowed in the materialized view log
  • ora-28336 : cannot encrypt SYS owned objects
  • ora-09207 : sfsrd: error reading from file
  • ora-22854 : invalid option for LOB storage index
  • ora-33308 : (DBVALID04) SEVERE ERROR: Record number used but not allocated
  • ora-19582 : archivelog file header validation for string failed
  • ora-22130 : buffer size [string] is less than the required size [string]
  • ora-12659 : Error received from other process
  • ora-12497 : maximum combined categories exceeds string
  • ora-01107 : database must be mounted for media recovery
  • ora-13754 : "SQL Tuning Set" "string" does not exist for user "string".
  • ora-19707 : invalid record block number - string
  • ora-26035 : Error attempting to encrypt or decrypt column
  • ora-32027 : There is no string column with the matching type in string.string.
  • ora-22293 : LOB already opened in the same transaction
  • ora-31455 : nothing to ALTER
  • ora-02486 : Error in writing trace file string
  • ora-09291 : sksachk: invalid device specified for archive destination
  • ora-38788 : More standby database recovery is needed
  • ora-09960 : Unable to establish signal handler for termination signal
  • ora-00364 : cannot write header to new log member
  • ora-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-24087 : Invalid database user string
  • ora-19378 : invalid mode
  • ora-25959 : join index must be of the bitmap type
  • ora-28141 : error in creating audit index file
  • 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.