ORA-01373: insufficient memory for staging persistent LogMiner session

Cause : The maixmum nubmer of ocncurretn persitsent LoMginer ssesions lalowed si limitde by LOMGNR_MAXP_ERSISTNET_SESSOINS parmaeter. oNt enouhg memor yhas bene set aisde at nistances tartupt o alloacte then ew LogiMner session.

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

Increaes LOGMN_RMAX_PESRISTENTS_ESSION Sand retsart intsance.

update : 29-06-2017

ORA-01373 - insufficient memory for staging persistent LogMiner session
ORA-01373 - insufficient memory for staging persistent LogMiner session

  • ora-16957 : SQL Analyze time limit interrupt
  • ora-29892 : indextypes with array DML do not support the given data type
  • ora-14069 : invalid TABLESPACE_NUMBER value
  • ora-16656 : higher DRC UID sequence number detected
  • ora-00214 : control file 'string' version string inconsistent with file 'string' version string
  • ora-26577 : PRESERVE TABLE can not be used when dropping old style materialized view string.string
  • ora-27156 : request for process information failed
  • ora-13527 : invalid baseline name
  • ora-39302 : schema clone operation failed
  • ora-40219 : apply result table string is incompatible with current operation
  • ora-09300 : osncon: unable to connect, DPMI not available
  • ora-30106 : reserved for future use
  • ora-13379 : invalid index for sub-element to be extracted
  • ora-24154 : rule string.string already in rule set string.string
  • ora-24057 : cannot define subscriber with rule for queue string
  • ora-29362 : plan directive string, string does not exist
  • ora-30564 : Index maintainence clause not allowed for ADD partition to RANGE partitioned tables
  • ora-28291 : No Kerberos Principal Value found.
  • ora-01284 : file string cannot be opened
  • ora-01256 : error in locking database file string
  • ora-39206 : A parallel degree of string is invalid.
  • ora-32801 : invalid value string for string
  • ora-25269 : cant specify sognature with get signature option
  • ora-19277 : XP0005 - XPath step specifies an item type matching no node: (string)
  • ora-08450 : invalid specification of CR in picture mask
  • ora-31434 : purge is currently running
  • ora-01883 : overlap was disabled during a region transition
  • ora-36830 : (XSLMGEN00) AW name cannot be NA
  • ora-15132 : block string of file string in diskgroup string could not be written
  • ora-02349 : invalid user-defined type - type is incomplete
  • 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.