ORA-23431: wrong state: string

Cause : The routine was executed against a replicated object group that was in the wrong state.

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

Make sure that the replicated object group is in the state given in the error message.

update : 20-08-2017
ORA-23431

ORA-23431 - wrong state: string
ORA-23431 - wrong state: string

  • ora-13783 : invalid tuning scope
  • ora-16222 : automatic Logical Standby retry of last action
  • ora-29525 : referenced name is too long: 'string'
  • ora-26102 : relative file # in file header is string rather than string for file string
  • ora-10902 : disable seghdr conversion for ro operation
  • ora-22298 : length of directory alias name or file name too long
  • ora-08117 : Index Organized Table operation released its block pin
  • ora-12812 : only one PARALLEL or NOPARALLEL clause may be specified
  • ora-38753 : Cannot flashback data file string; no flashback log data.
  • ora-36272 : (XSCGMDLAGG04) 'workspace object' is not a valid operator for the AGGREGATION function.
  • ora-29317 : datafile string does not exist
  • ora-06958 : Failed to access configuration file
  • ora-01082 : 'row_locking = always' requires the transaction processing option
  • ora-19921 : maximum number of string rows exceeded
  • ora-40254 : priors cannot be specified for one-class models
  • ora-08453 : more than one V symbol specified in picture mask
  • ora-38434 : could not evaluate expression "string"
  • ora-36628 : (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object.
  • ora-14122 : only one REVERSE or NOREVERSE clause may be specified
  • ora-24388 : Unsupported functionality in fast path mode
  • ora-07252 : spcre: semget error, could not allocate semaphores.
  • ora-06558 : buffer in dbms_pipe package is full. No more items allowed
  • ora-16766 : Redo Apply unexpectedly offline
  • ora-22280 : no more buffers available for operation
  • ora-02255 : obsolete 7.1.5
  • ora-07612 : $GETUAI failed in retrieving the user's clearance level
  • ora-30964 : The XML Index was not usable.
  • ora-37013 : (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.
  • ora-21602 : operation does not support the specified typecode
  • ora-29507 : query derived from USING clause found zero or many rows
  • 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.