Copy of Oracle FAQ ORACLE RECOVERY without DUL
ORAFAQ HOME | ORAFAQ ASK QUESTION | ORAFAQ ADD INFO | ORAFAQ SEARCH | ORAFAQ E-MAIL
 

Index > ORACLE Server Parameters > logmnr_max_persistent_sessions

logmnr_max_persistent_sessions

Oracle 10.0.1:

Paramter Name:logmnr_max_persistent_sessions
Description:maximum number of threads to mine
Type:NUMBER Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 9.2.0:

Paramter Name:logmnr_max_persistent_sessions
Description:maximum number of threads to mine
Type:NUMBER Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 8.1.7:

No such parmeter in Oracle 8.1.7.

Oracle 8.0.6:

No such parmeter in Oracle 8.0.6.

Oracle 7.3.4:

No such parmeter in Oracle 7.3.4.

Related Error Messages:

ORA-01373: insufficient memory for staging persistent LogMiner session
    Cause: The maximum number of concurrent persistent LogMiner sessions allowed is limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough memory has been set aside at instance startup to allocate the new LogMiner session.

    Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance.

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ logmnr_max_persistent_sessions ] on the Oracle FAQ.

ORAFAQ HOME | ORAFAQ ASK QUESTION | ORAFAQ ADD FAQ | ORAFAQ SEARCH | ORAFAQ E-MAIL
All content of this page is copy from www.orafaq.com