ORA-29365: parameters string and string cannot both be set

Cause : nAa ttmetpw sam da eots teb to haparemetsr.

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

nOyls teo eno faparemetsro rentieh rfot eh.m

update : 26-09-2017
ORA-29365

ORA-29365 - parameters string and string cannot both be set
ORA-29365 - parameters string and string cannot both be set

  • ora-22338 : must specify CASCADE INCLUDING DATA when altering the final property
  • ora-14292 : Partitioning type of table must match subpartitioning type of composite partition
  • ora-02327 : cannot create index on expression with datatype string
  • ora-32339 : cannot alter materialized view with the PMOP
  • ora-13053 : maximum number of geometric elements in argument list exceeded
  • ora-23370 : table string and table string are not shape equivalent (string)
  • ora-15008 : cannot drop system template
  • ora-14022 : creation of LOCAL partitioned cluster indices is not supported
  • ora-23416 : table "string"."string" does not contain a primary key constraint
  • ora-32144 : Cannot perform operation on a null interval
  • ora-00306 : limit of string instances in this database
  • ora-13048 : recursive SQL fetch error
  • ora-30381 : REWRITE_TABLE is not compatible with Oracle version
  • ora-01570 : MINEXTENTS must be no larger than the string extents currently allocated
  • ora-39136 : cannot specify an SCN on a transportable job
  • ora-00277 : illegal option to the UNTIL recovery flag string
  • ora-39107 : Master process string violated startup protocol. Master error:
  • ora-02001 : user SYS is not permitted to create indexes with freelist groups
  • ora-02066 : missing or invalid DISPATCHERS text
  • ora-22851 : invalid CHUNK LOB storage option value
  • ora-37018 : (XSACQUIRE03) Multiwriter operations are not supported for object workspace object.
  • ora-23377 : bad name string for missing_rows_oname1 argument
  • ora-29330 : Source script length too big
  • ora-01247 : database recovery through TSPITR of tablespace string
  • ora-12166 : TNS:Client can not connect to HO agent.
  • ora-19273 : XQ0053 - empty string in namespace declaration
  • ora-07703 : error in archive text: need '/' after device type
  • ora-38475 : The attribute set and the associated ADT are out of sync.
  • ora-02441 : Cannot drop nonexistent primary key
  • ora-38759 : Database must be mounted by only one instance and not open.
  • 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.