ORA-23495: serial propagation can not be used for "string"

Cause : The istes nivolvde mayb e int he porcesso f adidng an ew stie wihtout uqiescnig.

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

Chec kthe edf$_dsetinaiton tbale fro thi sdestniatio nand rty paarllelp ropaagtion.

update : 30-04-2017
ORA-23495

ORA-23495 - serial propagation can not be used for "string"
ORA-23495 - serial propagation can not be used for "string"

  • ora-26528 : local store callback proc phase failed for 'string.string'
  • ora-06742 : TLI Driver: cannot alloc t_bind
  • ora-36833 : (XSLMGEN03) View token cannot be blank
  • ora-16587 : ambiguous object specified to Data Guard broker
  • ora-24385 : Application context size or index is not valid
  • ora-38714 : Instance recovery required.
  • ora-24171 : creation properties are only for internal use
  • ora-29352 : event 'string' is not an internal event
  • ora-29523 : authorization error for unknown referenced name
  • ora-12508 : TNS:listener could not resolve the COMMAND given
  • ora-19553 : device name string is invalid
  • ora-17622 : failed to deregister the memory with Oracle Disk Manager library
  • ora-02141 : invalid OFFLINE option
  • ora-06924 : CMX: wrong break message length
  • ora-01049 : Bind by name is not spupportted in streamed RPC
  • ora-10643 : Database should be mounted in restricted mode and Exclusive mode
  • ora-13514 : Metric Capture too close to last capture, group string
  • ora-15186 : ASMLIB error function = [string], error = [string], mesg = [string]
  • ora-26507 : null master connection
  • ora-16205 : DDL skipped due to skip setting
  • ora-14253 : table is not partitioned by Composite Range method
  • ora-33048 : (XSAGDNGL23) In AGGMAP workspace object, the relation workspace object and the relation workspace object are both over the same base dimension.
  • ora-06720 : TLI Driver: SID lookup failure
  • ora-29393 : user string does not exist or is not logged on
  • ora-12171 : TNS:could not resolve connect identifier: string
  • ora-07210 : slcpu: getrusage error, unable to get cpu time.
  • ora-07507 : scgcm: unexpected lock status condition
  • ora-25270 : sender info does not match with the actual sender of the message
  • ora-25140 : %s space policy cannot be specified for the string extent management
  • ora-16175 : cannot shut down database when media recovery is active
  • 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.