Oracle DBA – A lifelong learning experience

ORA-0600 1880 – archivelog compression

Posted by John Hallas on March 5, 2009

We had a problem this morning on a database which runs our OMS repository. Enterprise manager access was hanging and a connect to the database took ages. The filesystem holding the bdump log files was full so I tidied that up but the database still had problems so I stopped OMS with opmnctl stopall, shutdown the database and then restarted it. The database failed to open with


ORACLE instance started.

Total System Global Area 788529152 bytes

Fixed Size 2076176 bytes

Variable Size 243270128 bytes

Database Buffers 536870912 bytes

Redo Buffers 6311936 bytes

Database mounted.

ORA-00600: internal error code, arguments: [1880], [0x110462EF8],

[0x110462C90], [1], [0], [], [], []

The server was bounced and fsck performed on the filesystems but all to no avail.

Metalink only had one hit using the ORA000 lookup tool which was a reference (note 460217.1) to maxpiecesize in the RMAN configuration causing problems when set. I immediately thought to myself how could a RMAN config setting cause a database to fail to start when it has been started many times before. However we did not have that setting enabled.

We then started looking at the trace files (most of which we had deleted earlier to release disk space) and spotted the following line in the alert log (repeated many times)

Errors in file /app/oracle/admin/SID/bdump/mtsprd1a_arc1_1532034.trc:

ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [1880] [0x1103EF620] [0x1103EF3B8] [1] [0]

Which pointed me to this in the trace files

Redo thread mounted by this instance: 1

Oracle process number: 122

Unix process pid: 786544, image: oracle@xxx (ARC1)

Detected dead process 786542; subsuming V$MANAGED_STANDBY slot

*** 2009-03-05 07:22:14.972

*** SERVICE NAME:(SYS$BACKGROUND) 2009-03-05 07:22:14.972

*** SESSION ID:(21.6335) 2009-03-05 07:22:14.972

Archivelog compression complete.

Input: 47124480 bytes Output: 45775293 bytes

Compression Performance: 94.00 percent or 7.77 bits per byte

*** 2009-03-05 07:22:14.974

ksedmp: internal or fatal error

ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [1880] [0x1103EF620] [0x1103EF3B8] [1] [0]

A Google search did not provide anything helpful but my colleague James Hardaker had seen something like this before and thought we should take off archivelog compression

startup mount;

alter database noarchivelog

alter database archivelog;

alter database open;

alter database archive log compress disable;

That did work for us and the database restarted cleanly but we need to investigate the cause of the problem. We believe it is around the area of lack of disk space when trying to compress. Hopefully the problem will be resolved as we are currently provisioning a new set of servers (HP Itanium) which will run a 2 node RAC cluster with a standby database on a third node. At the same time we will upgrade the EM database to and OMS which will improve supportability as well as performance.

3 Responses to “ORA-0600 1880 – archivelog compression”

  1. chris_c said

    Yuo may want to check with support if archivelog compression is actually supported, I looked at it late last year as a test restore was failing the response from support was that archivelog compression isn’t supported it was included in 10gR1 beta but dropped as far as I know its still not supported. The only documentation reference I could find was in the beta 10gR1 documentation.


  2. John Hallas said

    Submitted on 2009/03/05 at 3:04pm (deleted by mistake)

    Check this blog entry.

    Had similar errors to what you experienced.

    • John Hallas said

      Very interesting blog at

      The particularly relevant bit is the comment I have pasted below
      I was foolish enough to enable this on a production system. It ran fine for about four days, and then started dumping trace files, about 3 a minute. It dumped 54 GB of trace files in two days. Here is the important error:

      ORA-00600: internal error code, arguments: [1880], [0xDD044E0], [0xDD04440], [1], [0], [], [], []

      The Oracle engineer stated that Compressed Archive Logging is only partially implemented in 10, and wasn’t expected until 11 or even 12. Although he specializes in ORA-00600 errors, he had to go back to source to see what the 1880 parameter meant.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: