Log Writer Slave Issues in 12.1.0.2 – mainly on IBM AIX and HP-UX but also on Linux

Currently we see a lot of issues with the Multiple Logwriter feature in Oracle Database 12.1.0.2, especially on the IBM AIX platform.

What are Multiple LGWRs?

You will see multiple LGnn (Log Writer Worker) processes on multiprocessor systems, The LGWR (Log Writer) creates worker processes (slaves) to improve the performance of writing to the redo log. LGnn (Log Writer Worker) processes are not used when there is a SYNC standby destination. Possible processes include LG00LG99.

Here is a list of new background processes in Oracle Database 12.1:
MOS Note 1625912.1 – New Background Processes In 12c 

For deep dive information about how to trace the LGWR (and DBWR) and the differences 11.2/12.1 and wait events and much more, please see this Deep Dive PDF from an UKOUG talk from Frits Hoogland.

Known Symptoms:

Solution:

Turn off multiple logwriters on IBM AIX and HP-UX – and I turn off multiple logwriters on Linux as well. We are seeing the issues mainly on IBM AIX and HP-UX.

Set in your spfile:

_use_single_log_writer=true

See also:

–Mike

10 thoughts on “Log Writer Slave Issues in 12.1.0.2 – mainly on IBM AIX and HP-UX but also on Linux

  1. We just hit that bug five days before going live with our ERP upgrade. Our database got corrupted and it wouldnt come up not even after applying the _use_single_log_writer=true parameter.

    Scary stuff.

  2. Roberto,

    really sorry to hear that. The patch listening seems to say that the patch should be included into the most recent PSU. Did you apply this upfront to your home?

    Cheers
    Mike

  3. This could be the case – but I lost track a bit.
    My current recommendation to all customers on AIX (and potentially on Linux as well):

    _use_single_log_writer=true

    Mike

  4. Hi Mike ,

    We encounter the same issue.

    Impossible to open database !!!

    Any suggestion please to avoid restore …
    Best regards.
    Kais

    SQL> alter database open ;
    alter database open
    *
    ERROR at line 1:
    ORA-00600: internal error code, arguments: [kcrfrgv_nextlwn_scn], [1771859328],
    [26], [1771859330], [26], [], [], [], [], [], [], []

  5. hi,
    i’m installing 12C on AIX 7.2

    I came across all of the problem that you mention in this Blog and now it fixed.

    i have one more big issue ,
    i can’t create a new db with the DBCA i got error
    ORA-00449: background process ‘MMON’ unexpectedly terminated with error 448

    this is from the instillation log :

    File Validations Successful.
    Copying database files
    DBCA_PROGRESS : 1%
    DBCA_PROGRESS : 2%
    DBCA_PROGRESS : 8%
    DBCA_PROGRESS : 13
    DBCA_PROGRESS : 27
    Creating and starting Oracle instance
    ORA-00449: background process ‘MMON’ unexpectedly terminated with error 448
    ORA-01012: not logged on

    can you advice ?

  6. Hi Tomer,

    glad to hear that the blog helped you.

    Even though I’m not "Support" I did quickly check MOS and there are several issues reported on AIX (mostly during shutdown).

    Please check: patch 23089357 (or Oracle Support Document 23089357.8 (Bug 23089357 – Shutdown fails with ORA-449 "background process MMNL unexpectedly) can be found at: https://support.oracle.com/epmos/faces/DocumentDisplay?id=23089357.8) – there seem to be several issues on AIX 7.1.4 and newer with MMON and its little brother MMNL (MMon Light).

    No guarantee that it fixes it. But worth a try.

    Did you see any other errors in the alert.log?

    Do you let DBCA create one of the default databases (Data Warehouse or OLTP or whatever)? Then please try instead to create a CUSTOM database with DBCA, something I’d recommend you generally as you can decide which options you’d like to have created. The so called SEED databases have all options in it which may stretch your future upgrade timings.

    Cheers
    Mike

Leave a Reply

Your email address will not be published. Required fields are marked *