Internal Error Ora-600 Kdsgrp1
Contents |
my clients has a database job that runs weekly in the early hours of the morning. I have a cron job configured on their server to check the database alert log for errors on a regular basis and email me with any that it finds.This morning when I checked
Ora 00600 Internal Error Code Arguments
my emails there was one from that job reporting the following:Errors in file /u01/app/oracle/10.2/rdbms/log/
[13013], [5001], [517], [4260059], [139], [4260059], [3], [] in the alert log and sometimes, the database stops working ... Workaround SQL> Select object_name,object_type,owner from dba_objects where data_object_id=517; OBJECT_NAME--------------------------------------------------------------------------------OBJECT_TYPE OWNER------------------- ------------------------------COL_USAGE$TABLE SYSSQL> analyze table SYS.COL_USAGE$ validate structure online;Table analyzed.SQL> analyze table SYS.COL_USAGE$ validate structure cascade online;analyze table SYS.COL_USAGE$ validate structure cascade online*ERROR at line 1:ORA-00600: internal error code, arguments: [kdsgrp1], http://dbadave.co.uk/ora-00600-kdsgrp1-in-database-alert-log/ [], [], [], [], [], [],[]SQL> select index_name from dba_indexes where table_name='COL_USAGE$';INDEX_NAME------------------------------I_COL_USAGE$SQL> Set long 1000000SQL> Select dbms_metadata.get_ddl('INDEX','I_COL_USAGE$','SYS') from dual;DBMS_METADATA.GET_DDL('INDEX',--------------------------------------------------------------------------------CREATE UNIQUE INDEX "SYS"."I_COL_USAGE$" ON "SYS"."COL_USAGE$" ("OBJ#", "INTCOL#") PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST http://oracleonlinux-n.blogspot.com/2015/01/ora-00600-internal-error-code-arguments.html GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "SYSTEM"SQL> drop index "SYS"."I_COL_USAGE$";Index dropped.SQL> CREATE UNIQUE INDEX "SYS"."I_COL_USAGE$" ON "SYS"."COL_USAGE$" ("OBJ#", "INTCOL#") PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "SYSTEM";Index created.SQL> analyze table SYS.COL_USAGE$ validate structure cascade online; Table analyzed. --------------------------------------------------------------------------------------------------------------- Oracle Doc ID : 816784.1 Posted by shareefpkd at 9:21 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive ▼ 2015 (2) ► February (1) ▼ January (1) ORA-00600: internal error code, arguments: [13013]... ► 2014 (1) ► September (1) ► 2013 (5) ► May (2) ► February (1) ► January (2) ► 2012 (3) ► November (2) ► March (1) About Me sha
September 2011 Oracle Magazine Online 2016 2015 2014 2013 2012 2011 2010 January 2011 March 2011 May 2011 July 2011 September 2011 November 2011 TECHNOLOGY: Support As Published In September/October 2011 Troubleshooting Internal Errors By Tamzin Oscroft A http://www.oracle.com/technetwork/issue-archive/2011/11-sep/o51support-453463.html guide to assessing and resolving ORA-600 and ORA-7445 errors If you’re an Oracle DBA, you’re likely to have come across an error message in your Oracle Database alert.log files prefixed by either ORA-600 or ORA-7445, such http://rakeshchandrachowke.blogspot.com/2012/08/error-at-line-1-ora-00600-internal.html as Thu Jan 20 13:35:52 2011 Errors in file /DATA/oracle/admin/ prod/udump/prod_ora_2131.trc: ORA-00600: internal error code, arguments: [ktfbtgex-7], [1015817], [1024], [1015816], [], [], [], [] Because these internal error messages include no attached explanation in the way internal error that external error messages do (for example, “ORA-00942: table or view does not exist”), it is difficult to assess the seriousness of the error and whether it is cause for concern. This column explains what you can do to assess some ORA-600 or ORA-7445 errors and identify solutions. ORA-600 or ORA-7445: What Is the Difference? ORA-600 is a catchall message that indicates an error internal to the database code. The key point to internal error ora-600 note about an ORA-600 error is that it is signaled when a code check fails within the database. At points throughout the code, Oracle Database performs checks to confirm that the information being used in internal processing is healthy, that the variables being used are within a valid range, that changes are being made to a consistent structure, and that a change won’t put a structure into an unstable state. If a check fails, Oracle Database signals an ORA-600 error and, if necessary, terminates the operation to protect the health of the database. The first argument to the ORA-600 error message indicates the location in the code where the check is performed; in the example above, that is ktfbtgex-7 (which indicates that the error occurred at a particular point during tablespace handling). The subsequent arguments have different meanings, depending on the particular check. An ORA-7445 error, on the other hand, traps a notification the operating system has sent to a process and returns that notification to the user. Unlike the ORA-600 error, the ORA-7445 error is an unexpected failure rather than a handled failure. The Oracle function in which that notification signal is received is usually, from Oracle Database 10g onward, contained in the ORA-7445 error message itself. For example, in the error message ORA-07445: exception enco
Solution 1: Try to rebuild Indexes and ANALYZE TABLE Table_Name VALIDATE STRUCTURE; Solution 2: Still You are getting the same Error... Try this.. BEGIN DBMS_REPAIR.SKIP_CORRUPT_BLOCKS ( SCHEMA_NAME => 'SCOTT', OBJECT_NAME => 'DEPT', OBJECT_TYPE => dbms_repair.table_object, FLAGS => dbms_repair.skip_flag); END; / Check this Query: SELECT OWNER, TABLE_NAME, SKIP_CORRUPT FROM DBA_TABLES WHERE OWNER = 'SCOTT'; OWNER TABLE_NAME SKIP_COR SCOTT ACCOUNT DISABLED SCOTT BONUS DISABLED SCOTT DEPT ENABLED Create a Backup table same as this table. Then take the backup into backup table and drop the original. Rename backup to original. If the table is very big use Bulk collect to take backup. Run statistics for New Table. Posted by Rakesh Chandra Chowke at 4:58 AM No comments: Post a Comment Newer Post Home Subscribe to: Post Comments (Atom) Followers Blog Archive ► 2016 (1) ► February (1) ► 2014 (2) ► September (1) ► January (1) ▼ 2012 (3) ► October (1) ► September (1) ▼ August (1) ERROR at line 1: ORA-00600: internal error code, a...