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 : 29-04-2017

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

  • ora-12086 : table "string"."string" is not an object table
  • ora-24364 : internal error while padding blanks
  • ora-01061 : cannot start up a V8 server using a V7 client application
  • ora-09745 : smscre: vm_allocate error, unable to create shared memory.
  • ora-10917 : TABLESPACE GROUP cannot be specified
  • ora-30066 : test support - drop rollback segment wait
  • ora-22305 : attribute/method/parameter "string" not found
  • ora-00323 : Current log of thread string not useable and all others need archiving
  • ora-27143 : OS system call failure
  • ora-09884 : Two Task interface: SID doens't match current PU
  • ora-30013 : undo tablespace 'string' is currently in use
  • ora-36887 : (XSSRF06) Error rewriting OLAP DML expression. Column name string is not a valid ADT column.
  • ora-25501 : ALTER SYSTEM QUIESCE RESTRICTED command failed
  • ora-04098 : trigger 'string.string' is invalid and failed re-validation
  • ora-38437 : The ADT "string" may not contain any user methods.
  • ora-29838 : insufficient privileges to execute the operator(s)
  • ora-19754 : error reading from change tracking file
  • ora-21523 : functionality not supported by the server (object mode only)
  • ora-13348 : polygon boundary is not closed
  • ora-14288 : index is not partitioned by Composite Range method
  • ora-02423 : schema name does not match schema authorization identifier
  • ora-39098 : Worker process received data objects while loading metadata. Invalid process order range is string..string
  • ora-12660 : Encryption or crypto-checksumming parameters incompatible
  • ora-16727 : resource guard cannot close database
  • ora-26735 : operation not allowed on the specified file group version
  • ora-28001 : the password has expired
  • ora-10665 : Inject Evil Literals
  • ora-01160 : file is not a string
  • ora-26745 : cursors (string) are not sufficient
  • ora-16170 : Terminal recovery may have left the database in an inconsistent state
  • 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.