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 : 24-08-2017

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

  • ora-33218 : (CINSERT04) %K is not a valid value for the workspace object dimension. Values for this dimension can have at most number significant digits after rounding to number decimal places.
  • ora-23358 : invalid remote user
  • ora-39962 : invalid parameter for PLSQL_CCFLAGS
  • ora-12453 : label string already exists
  • ora-00267 : name of archived log file not needed
  • ora-09207 : sfsrd: error reading from file
  • ora-37184 : illegal value string for ADVMODE
  • ora-06022 : NETASY: channel open failure
  • ora-39023 : Version string is not supported.
  • ora-07403 : sfanfy: db_writers parameter not valid.
  • ora-19278 : Invalid value: (string) for type: (string)
  • ora-01164 : MAXLOGFILES may not exceed string
  • ora-17626 : ksfdcre: string file exists
  • ora-01699 : tablespace 'string' is being imported for point in time recovery
  • ora-22870 : ALTER TYPE with REPLACE option a non-object type
  • ora-13636 : The specified value provided for parameter string is not valid for this advisor.
  • ora-14125 : REVERSE/NOREVERSE may not be specified in this context
  • ora-01559 : MAXEXTENTS for rollback segment must be greater than 1
  • ora-01973 : Missing change number
  • ora-13402 : the rasterType is null or not supported
  • ora-14605 : Name missing for subpartition / lob segment in template
  • ora-32576 : missing TYPE keyword
  • ora-39216 : object type "string"."string" hashcode mismatch
  • ora-13276 : internal error [string] in coordinate transformation
  • ora-06001 : NETASY: port set-up failure
  • ora-23483 : object "string"."string" not allowed in this operation.
  • ora-24149 : invalid rule name
  • ora-25140 : %s space policy cannot be specified for the string extent management
  • ora-37020 : (XSMULTI01) Analytic workspace string is not in MULTI mode.
  • ora-22317 : typecode number is not legal as a number type
  • 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.