ORA-23496: can not change disabled status for "string" and "string"

Cause : The idsablde stauts fo rthiss ite si seti nteranlly ofr sycnhronziatio ndurign addnig a enw matser wtihoutq uiesicng.

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

Ensuer addnig a enw matser wtihoutq uiesicng fniishe dbefoer invkoing htis porceduer.

update : 21-08-2017

ORA-23496 - can not change disabled status for "string" and "string"
ORA-23496 - can not change disabled status for "string" and "string"

  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-19750 : change tracking file: 'string'
  • ora-10585 : Test recovery can not apply redo that may modify control file
  • ora-23361 : materialized view "string" does not exist at master site
  • ora-00295 : datafile/tempfile number string is invalid, must be between 1 and string
  • ora-38711 : Corrupt flashback log block header: block string
  • ora-19733 : COMPATIBLE parameter needs to be string or greater
  • ora-24101 : stopped processing the argument list at: string
  • ora-06596 : unsupported LOB operation in RPC call
  • ora-04015 : ascending sequences that CYCLE must specify MAXVALUE
  • ora-01725 : USERENV('COMMITSCN') not allowed here
  • ora-14007 : missing LESS keyword
  • ora-19601 : output file is string string (string)
  • ora-12684 : encryption/crypto-checksumming: Diffie-Hellman seed too small
  • ora-06539 : target of OPEN must be a query
  • ora-22618 : attribute is a BAD NULL in the image handle
  • ora-01171 : datafile string going offline due to error advancing checkpoint
  • ora-14295 : column type or size mismatch between partitioning columns and subpartitioning columns
  • ora-16417 : Activation occurred after recovery from standby redo log files; a full database backup is required
  • ora-08111 : a partitioned index may not be coalesced as a whole
  • ora-26715 : time limit reached
  • ora-16793 : logical standby database guard is unexpectedly off
  • ora-13357 : extent type does not contain 2 points
  • ora-07549 : sftopn: $OPEN failure
  • ora-15166 : cluster in rolling downgrade from version [string] to [string]
  • ora-09208 : sftcls: error closing file
  • ora-12412 : policy package string is not installed
  • ora-39017 : Worker request not supported when job is in string state.
  • ora-14628 : specification of bounds is inconsistent with LIST method
  • ora-19271 : XP0051 - invalid atomic type definition
  • 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.