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-05-2017

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

  • ora-15117 : command only operates on one diskgroup
  • ora-07227 : rtneco: unable to set noecho mode.
  • ora-38421 : attribute string already exists
  • ora-12077 : temporary updatable materialized view log does not exist
  • ora-22634 : Error adding new instance to AnyDataSet
  • ora-19123 : fn:zero-or-one() called with a sequence containing more than one item
  • ora-02404 : specified plan table not found
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • ora-08316 : sllfsk: Error seeking in file.
  • ora-13775 : inconsistent datatype in input cursor
  • ora-06803 : TLI Driver: the IPX device file could not be opened
  • ora-01080 : error in shutting down ORACLE
  • ora-27208 : syntax error in device PARMS - environment variable value missing
  • ora-29511 : could not resolve Java class
  • ora-01104 : number of control files (string) does not equal string
  • ora-32585 : duplicate specification of a supplemental log attribute
  • ora-19018 : Invalid character in XML tag 'string'
  • ora-13125 : partition key is already set
  • ora-39122 : Unprivileged users may not perform string remappings.
  • ora-12638 : Credential retrieval failed
  • ora-32126 : Cannot perform operations on a null REF
  • ora-33080 : (XSAGDNGL40) In AGGMAP workspace object, you cannot reference dimension workspace object with both a RELATION statement and a DIMENSION statement.
  • ora-23420 : interval must evaluate to a time in the future
  • ora-00205 : error in identifying control file, check alert log for more info
  • ora-01224 : group number in header string does not match GROUP string
  • ora-12842 : Cursor invalidated during parallel execution
  • ora-01262 : Stat failed on a file destination directory
  • ora-25283 : either agent's name or address needed for non-repudiation
  • ora-01489 : result of string concatenation is too long
  • ora-13614 : The template string is not compatible with the current advisor.
  • 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.