Ora-00600: internal error on 11g database in windows 2007 environment

Question

Hello , i have these problems please help me to solve it.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Windows\system32>emctl status dbconsole
Environment variable ORACLE_SID not defined. Please define it.
C:\Windows\system32>set ORACLE_SID=testsid
C:\Windows\system32>emctl status dbconsole
Oracle Enterprise Manager 11g Database Control Release 11.1.0.6.0
Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
https://local:1158/em/console/aboutApplication
Oracle Enterprise Manager 11g is not running.
Logs are generated in directory C:\app\23333941\product\11.1.0\db_3/local_testsid/sysman/log
C:\Windows\system32>sqlplus sys/@**** as sysdba
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 09:27:37 2013
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
SQL*Plus: Release 11.1.0.6.0 - Production
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
Use SQL*Plus to execute SQL, PL/SQL and SQL*Plus statements.
Usage 1: sqlplus -H | -V
    -H             Displays the SQL*Plus version and the
                   usage help.
    -V             Displays the SQL*Plus version.
Usage 2: sqlplus [ [<option>] [<logon>] [<start>] ]
  <option> is: [-C <version>] [-L] [-M "<options>"] [-R <level>] [-S]
    -C <version>   Sets the compatibility of affected commands to the
                   version specified by <version>.  The version has
                   the form "x.y[.z]".  For example, -C 10.2.0
    -F             Enables the failover mode for a RAC environment.
    -L             Attempts to log on just once, instead of
                   reprompting on error.
    -M "<options>" Sets automatic HTML markup of output.  The options
                   have the form:
                   HTML [ON|OFF] [HEAD text] [BODY text] [TABLE text]
                   [ENTMAP {ON|OFF}] [SPOOL {ON|OFF}] [PRE[FORMAT] {ON|OFF}]
    -R <level>     Sets restricted mode to disable SQL*Plus commands
                   that interact with the file system.  The level can
                   be 1, 2 or 3.  The most restrictive is -R 3 which
                   disables all user commands interacting with the
                   file system.
    -S             Sets silent mode which suppresses the display of
                   the SQL*Plus banner, prompts, and echoing of
                   commands.
  <logon> is: (<username>[/<password>][@<connect_identifier>] | /)
              [AS SYSDBA | AS SYSOPER | AS SYSASM] | /NOLOG | [EDITION=value]
    Specifies the database account username, password and connect
    identifier for the database connection.  Without a connect
    identifier, SQL*Plus connects to the default database.
    The AS SYSDBA, AS SYSOPER and AS SYSASM  options are database
    administration privileges.
    <connect_identifier> can be in the form of Net Service Name
    or Easy Connect.
      @[<net_service_name> | [//]Host[:Port]/<service_name>]
        <net_service_name> is a simple name for a service that resolves
        to a connect descriptor.
        Example: Connect to database using Net Service Name and the
                 database net service name is ORCL.
           sqlplus myusername/mypassword@ORCL
        Host specifies the host name or IP address of the database
        server computer.
        Port specifies the listening port on the database server.
        <service_name> specifies the service name of the database you
        want to access.
        Example: Connect to database using Easy Connect and the
                 Service name is ORCL.
           sqlplus myusername/mypassword@Host/ORCL
    The /NOLOG option starts SQL*Plus without connecting to a
    database.
    The EDITION specifies the value for Application
    Edition
  <start> is: @<URL>|<filename>[.<ext>] [<parameter> ...]
    Runs the specified SQL*Plus script from a web server (URL) or the
    local file system (filename.ext) with specified parameters that
    will be assigned to substitution variables in the script.
When SQL*Plus starts, and after CONNECT commands, the site profile
(e.g. $ORACLE_HOME/sqlplus/admin/glogin.sql) and the user profile
(e.g. login.sql in the working directory) are run.  The files may
contain SQL*Plus commands.
Refer to the SQL*Plus User's Guide and Reference for more information.
C:\Windows\system32>sqlplus sys/1118@testsid as sysdba
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 09:29:03 2013
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified
Enter user-name: sysdba
Enter password:
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
Process ID: 0
Session ID: 0 Serial number: 0
Enter user-name: sys
Enter password:
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
Process ID: 0
Session ID: 0 Serial number: 0
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
C:\Windows\system32>sqlplus/nolog
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 09:32:59 2013
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
SQL> connect/as sysdba
Connected.
SQL> create table test(id number, id1 number);
create table test(id number, id1 number)
ERROR at line 1:
ORA-01109: database not open
SQL> select status from v$instance;
STATUS
MOUNTED
SQL> alter database open;
ERROR at line 1:
ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0x51434A54],
[2], [], [], [], [], []
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:\Windows\system32>startup mount
'startup' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>sqlplus/nolog
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 10:05:42 2013
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
SQL> connect/as sysdba
Connected.
SQL> startup mount;
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> recover database;
Media recovery complete.
SQL> select GROUP#,SEQUENCE#,ARCHIVED,STATUS from v$log order by SEQUENCE#;
    GROUP#  SEQUENCE# ARC STATUS
         2        539 NO  INACTIVE
         3        540 NO  ACTIVE
         1        541 NO  CURRENT
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00264: no recovery required
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:\Windows\system32>sqlplus/nolog
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 10:17:10 2013
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
SQL> connect / as sysdba
Connected.
SQL> startup mount
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.
Total System Global Area  313860096 bytes
Fixed Size                  1332892 bytes
Variable Size             276826468 bytes
Database Buffers           29360128 bytes
Redo Buffers                6340608 bytes
Database mounted.
Database opened.
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-01124: cannot recover data file 1 - file is in use or recovery
ORA-01110: data file 1:
'C:\APP\23333941\ORADATA\TEST\DATAFILE\O1_MF_SYSTEM_8XB8TY3S_.DBF'
SQL> select GROUP#,SEQUENCE#,ARCHIVED,STATUS from v$log order by SEQUENCE#;
    GROUP#  SEQUENCE# ARC STATUS
         3        540 NO  INACTIVE
         1        541 NO  INACTIVE
         2        542 NO  CURRENT
SQL> restore database;
SP2-0734: unknown command beginning "restore da..." - rest of line ignored.
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-01124: cannot recover data file 1 - file is in use or recovery
ORA-01110: data file 1:
'C:\APP\23333941\ORADATA\TEST\DATAFILE\O1_MF_SYSTEM_8XB8TY3S_.DBF'
SQL>
Thanks with regards Ganaa;

Answer 1

What happened prior that resulted in the disaster scenario that you posted/
When was the last time the DB opened with out error?
What changed since then?