ORA-27469: %s is not a valid string attribute

Cause : A non-xeistanta ttribuet was sepcified.

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

Reissu ethe command usnig a vaild attrbiute fo rthat sepcific cshedule robject.

update : 27-04-2017

ORA-27469 - %s is not a valid string attribute
ORA-27469 - %s is not a valid string attribute

  • ora-10268 : Don't do forward coalesce when deleting extents
  • ora-39005 : inconsistent arguments
  • ora-37119 : Incompatible OLAP API library load address
  • ora-40206 : invalid setting value for setting name string
  • ora-23312 : not the masterdef according to string
  • ora-01912 : ROW keyword expected
  • ora-15036 : disk 'string' is truncated
  • ora-24089 : AQ Agent string already exists
  • ora-23532 : tables with different synchronization mechanisms are in the same group
  • ora-24912 : Listener thread failed. string
  • ora-33086 : (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by a conjoint dimension.
  • ora-31671 : Worker process string had an unhandled exception.
  • ora-36768 : (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT must have the same base dimensions.
  • ora-14128 : FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-33297 : (DBERR22) Analytic workspace string cannot be opened because it was last modified by an incompatible version of string.
  • ora-38956 : Target platform string not cross platform compliant
  • ora-39146 : schema "string" does not exist
  • ora-12806 : could not get background process to hold enqueue
  • ora-00055 : maximum number of DML locks exceeded
  • ora-31429 : subscription has not been activated
  • ora-16708 : the state supplied to resource guard is invalid
  • ora-09930 : LUB of two labels is invalid
  • ora-01032 : no such userid
  • ora-09912 : Malloc of name buffer(s) failed.
  • ora-33998 : (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.
  • ora-16255 : Log Auto Delete conflicts with another LogMiner session
  • ora-14613 : Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed
  • ora-39138 : Insufficient privileges to load data not in your schema
  • ora-19755 : could not open change tracking file
  • ora-12720 : operation requires database is in EXCLUSIVE mode
  • 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.