Monday, August 16, 2010

ORA-00600: internal error code, arguments: [kck_rls_check must use (11,0,0,0,0) or lower], [kdt.c], [9486], [11.2.0.1.0]

I tested some about spfile and then found.
ORA-00600: internal error code, arguments: [kck_rls_check must use (11,0,0,0,0) or lower]
found out Oracle Support [ID 1064264.1] and they told it relates to an internal check on the compression compatibility(default -> 11.2.0.1). then test:
SQL> select value from v$parameter where name='_compression_compatibility';

no rows selected

SQL> create pfile='/tmp/pfile' from memory;

File created.

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL> startup pfile='/tmp/pfile';
ORA-00600: internal error code, arguments: [kck_rls_check must use (11,0,0,0,0) or lower], [kdt.c], [9486], [11.2.0.1.0], [], [], [], [], [], [], [], []
checked and solved (_compression_compatibility='11.2.0.1' -> _compression_compatibility='11.2.0')
$ grep compression_compatibility /tmp/pfile
_compression_compatibility='11.2.0.1'

$ grep compression_compatibility /tmp/pfile
_compression_compatibility='11.2.0'

SQL> startup pfile='/tmp/pfile';
ORACLE instance started.

Total System Global Area 790941696 bytes
Fixed Size 1339428 bytes
Variable Size 222302172 bytes
Database Buffers 557842432 bytes
Redo Buffers 9457664 bytes
Database mounted.
Database opened.

SQL> select value from v$parameter where name='_compression_compatibility';

VALUE
------------------------------
11.2.0
Actually we can remove '_compression_compatibility' from parameter file and start database.

2 comments:

Anonymous said...

Thank you for posting. Your "before test" was not valid. Querying v$parameter only shows non-hidden parameters. You would need to grep the pfile after it was created from memory.

Anonymous said...

Very Very helpful. I was troubleshooting this issue for almost 2 hours when I came across your blog. Thank you for the solution