ORA-03113: fin de archivo en el canal de comunicac

Fijate en el AlertDB.log en el directorio Admin a ver si hay un error, si un close normal no debería haber este error pero verifica o transcribe las lineas del alert.log para ver que pasó.

Busque el archivo del alert  y esto es lo que dice cuando subo y bajo la db.
Tue Jul 22 10:21:28 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 150
sga_max_size = 419430400
__shared_pool_size = 184549376
__large_pool_size = 4194304
__java_pool_size = 4194304
__streams_pool_size = 0
spfile = C:\ORACLE\PRODUCT\10.2.0\DB_1\DBS\SPFILEORA10G.ORA
sga_target = 385875968
control_files = C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\CONTROL01.CTL, C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\CONTROL02.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 184549376
compatible = 10.2.0.1.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = C:\oracle\product\10.2.0/flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
max_enabled_roles = 148
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=ora10gXDB)
job_queue_processes = 10
audit_file_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORA10G\ADUMP
background_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORA10G\BDUMP
user_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORA10G\UDUMP
core_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORA10G\CDUMP
db_name = ora10g
open_cursors = 300
pga_aggregate_target = 95420416
Deprecated system parameters with specified values:
max_enabled_roles
End of deprecated system parameter listing
PMON started with pid=2, OS id=4796
PSP0 started with pid=3, OS id=3840
MMAN started with pid=4, OS id=4092
DBW0 started with pid=5, OS id=3308
LGWR started with pid=6, OS id=4952
CKPT started with pid=7, OS id=5572
SMON started with pid=8, OS id=2296
RECO started with pid=9, OS id=5552
CJQ0 started with pid=10, OS id=4656
MMON started with pid=11, OS id=2372
Tue Jul 22 10:21:31 2008
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Jul 22 10:21:31 2008
starting up 1 shared server(s) ...
Tue Jul 22 10:21:31 2008
ALTER DATABASE MOUNT
MMNL started with pid=12, OS id=3832
Tue Jul 22 10:21:35 2008
Setting recovery target incarnation to 2
Tue Jul 22 10:21:35 2008
Successful mount of redo thread 1, with mount id 3979630955
Tue Jul 22 10:21:35 2008
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Tue Jul 22 10:21:36 2008
ALTER DATABASE OPEN
Tue Jul 22 10:21:37 2008
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Tue Jul 22 10:21:40 2008
Started redo scan
Tue Jul 22 10:21:45 2008
Completed redo scan
157003 redo blocks read, 8231 data blocks need recovery
Tue Jul 22 10:21:52 2008
Started redo application at
Thread 1: logseq 19229, block 24532
Tue Jul 22 10:21:54 2008
Recovery of Online Redo Log: Thread 1 Group 1 Seq 19229 Reading mem 0
Mem# 0 errs 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\REDO01.LOG
Mem# 1 errs 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\REDO01A.LOG
Tue Jul 22 10:22:00 2008
Recovery of Online Redo Log: Thread 1 Group 4 Seq 19230 Reading mem 0
Mem# 0 errs 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\REDO04.LOG
Mem# 1 errs 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\REDO04A.LOG
Tue Jul 22 10:22:04 2008
Completed redo application
Tue Jul 22 10:22:05 2008
Completed crash recovery at
Thread 1: logseq 19230, block 88340, scn 939400325
8231 data blocks read, 8231 data blocks written, 157003 redo blocks read
Tue Jul 22 10:22:13 2008
Thread 1 advanced to log sequence 19231
Thread 1 opened at log sequence 19231
Current log# 2 seq# 19231 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\REDO02.LOG
Current log# 2 seq# 19231 mem# 1: E:\ORACLE\PRODUCT\10.2.0\ORADATA\REDO02A.LOG
Successful open of redo thread 1
Tue Jul 22 10:22:14 2008
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue Jul 22 10:22:15 2008
SMON: enabling cache recovery
Tue Jul 22 10:22:25 2008
Successfully onlined Undo Tablespace 1.
Tue Jul 22 10:22:25 2008
SMON: enabling tx recovery
Tue Jul 22 10:22:28 2008
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Tue Jul 22 10:22:42 2008
Starting background process QMNC
QMNC started with pid=20, OS id=2572
Tue Jul 22 10:22:45 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_p002_4552.trc:
ORA-00600: internal error code, arguments: [4198], [9], [], [], [], [], [], []
Tue Jul 22 10:22:58 2008
Doing block recovery for file 2 block 89
Block recovery from logseq 19231, block 14 to scn 939400372
Tue Jul 22 10:23:00 2008
Recovery of Online Redo Log: Thread 1 Group 2 Seq 19231 Reading mem 0
Mem# 0 errs 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\REDO02.LOG
Mem# 1 errs 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\REDO02A.LOG
Block recovery completed at rba 19231.44.16, scn 0.939400373
Doing block recovery for file 21 block 61519
Block recovery from logseq 19231, block 69 to scn 939400400
Tue Jul 22 10:23:04 2008
Recovery of Online Redo Log: Thread 1 Group 2 Seq 19231 Reading mem 0
Mem# 0 errs 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\REDO02.LOG
Mem# 1 errs 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\REDO02A.LOG
Block recovery completed at rba 19231.69.16, scn 0.939400401
Tue Jul 22 10:23:17 2008
SMON: Restarting fast_start parallel rollback
Tue Jul 22 10:23:28 2008
Completed: ALTER DATABASE OPEN
Tue Jul 22 10:23:29 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_p002_4552.trc:
ORA-00600: internal error code, arguments: [4198], [9], [], [], [], [], [], []
Tue Jul 22 10:23:32 2008
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Jul 22 10:23:44 2008
Doing block recovery for file 2 block 89
Block recovery from logseq 19231, block 14 to scn 939400372
Tue Jul 22 10:23:46 2008
Recovery of Online Redo Log: Thread 1 Group 2 Seq 19231 Reading mem 0
Mem# 0 errs 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\REDO02.LOG
Mem# 1 errs 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\REDO02A.LOG
Block recovery completed at rba 19231.44.16, scn 0.939400373
Doing block recovery for file 21 block 61519
Block recovery from logseq 19231, block 69 to scn 939400422
Tue Jul 22 10:23:49 2008
Recovery of Online Redo Log: Thread 1 Group 2 Seq 19231 Reading mem 0
Mem# 0 errs 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\REDO02.LOG
Mem# 1 errs 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\REDO02A.LOG
Block recovery completed at rba 19231.8057.16, scn 0.939400423
Tue Jul 22 10:24:07 2008
SMON: ignoring slave err,downgrading to serial rollback
Tue Jul 22 10:24:13 2008
ORA-01555 caused by SQL statement below (SQL ID: 6a1s7m686av6k, Query Duration=8 sec, SCN: 0x0000.37fe1e16):
Tue Jul 22 10:24:13 2008
SELECT /* OPT_DYN_SAMP */ /*+ ALL_ROWS IGNORE_WHERE_CLAUSE NO_PARALLEL(SAMPLESUB) opt_param('parallel_execution_enabled', 'false') NO_PARALLEL_INDEX(SAMPLESUB) NO_SQL_TUNE */ NVL(SUM(C1),:"SYS_B_0"), NVL(SUM(C2),:"SYS_B_1") FROM (SELECT /*+ NO_PARALLEL("PP_VMMOVIEQ") FULL("PP_VMMOVIEQ") NO_PARALLEL_INDEX("PP_VMMOVIEQ") */ :"SYS_B_2" AS C1, :"SYS_B_3" AS C2 FROM "CONSTR"."PP_VMMOVIEQ" SAMPLE BLOCK (:"SYS_B_4" , :"SYS_B_5") SEED (:"SYS_B_6") "PP_VMMOVIEQ") SAMPLESUB
Tue Jul 22 10:24:49 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_smon_2296.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Tue Jul 22 10:24:54 2008
ORACLE Instance ora10g (pid = 8) - Error 600 encountered while recovering transaction (6, 0).
Tue Jul 22 10:24:54 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_smon_2296.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Tue Jul 22 10:24:58 2008
Thread 1 advanced to log sequence 19232
Current log# 3 seq# 19232 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\REDO03.LOG
Current log# 3 seq# 19232 mem# 1: E:\ORACLE\PRODUCT\10.2.0\ORADATA\REDO03A.LOG
Tue Jul 22 10:25:18 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_smon_2296.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Tue Jul 22 10:25:25 2008
ORACLE Instance ora10g (pid = 8) - Error 600 encountered while recovering transaction (6, 0).
Tue Jul 22 10:25:26 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_smon_2296.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Tue Jul 22 10:25:41 2008
Starting background process EMN0
EMN0 started with pid=24, OS id=4032
Tue Jul 22 10:25:41 2008
Shutting down instance: further logons disabled
Tue Jul 22 10:25:51 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_smon_2296.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Tue Jul 22 10:25:57 2008
ORACLE Instance ora10g (pid = 8) - Error 600 encountered while recovering transaction (6, 0).
Tue Jul 22 10:25:57 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_smon_2296.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Tue Jul 22 10:26:00 2008
Stopping background process QMNC
Tue Jul 22 10:26:00 2008
Stopping background process CJQ0
Tue Jul 22 10:26:01 2008
Stopping background process MMNL
Tue Jul 22 10:26:02 2008
Stopping background process MMON
Tue Jul 22 10:26:04 2008
Shutting down instance (immediate)
License high water mark = 10
Tue Jul 22 10:26:04 2008
Stopping Job queue slave processes
Tue Jul 22 10:26:06 2008
Thread 1 advanced to log sequence 19233
Current log# 1 seq# 19233 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\REDO01.LOG
Current log# 1 seq# 19233 mem# 1: E:\ORACLE\PRODUCT\10.2.0\ORADATA\REDO01A.LOG
Tue Jul 22 10:26:08 2008
Job queue slave processes stopped
Tue Jul 22 10:26:11 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_smon_2296.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Tue Jul 22 10:26:13 2008
ORACLE Instance ora10g (pid = 8) - Error 600 encountered while recovering transaction (6, 0).
Tue Jul 22 10:26:13 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_smon_2296.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Tue Jul 22 10:26:16 2008
All dispatchers and shared servers shutdown
Tue Jul 22 10:26:16 2008
ALTER DATABASE CLOSE NORMAL
Tue Jul 22 10:26:26 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_smon_2296.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Tue Jul 22 10:26:32 2008
Errors in file c:\oracle\product\10.2.0\admin\ora10g\bdump\ora10g_pmon_4796.trc:
ORA-00474: SMON process terminated with error
Tue Jul 22 10:26:32 2008
PMON: terminating instance due to error 474
Instance terminated by PMON, pid = 4796
Gracias por la ayuda q  me puedas brindar

No tengo experiencia con esos errores, hay una serie de ora600 que diría que son para el soporte de oracle.
El error aparentemente se da cuando intenta recuperar una transacción y se genera un ora-01555 que en el peor de los casos puede darse x un problema en algún bloque del undo y en el mejor puede ser por un undo relativamente chico (habría que agrandar el undo o bien crear otro más grande y apuntarlo con el parámetro undo_tablespace. También hay un parametro (con el que no estoy familiarizado, vengo de 9i y voy camino a 11) que es el db_recovery_file_dest_size y no se si no puede estar quedándose corto, pero ahí estoy simplemente pensando en voz alta porque no tengo ninguna idea de como lo usa.
Pero ojo que quizá estes en una situación de contactar al soporte de oracle porque si no levanta vas a tener que recuperar la base de datos.

intente ampliando db_recovery_file_dest_size y nada. No me deja mirar el espacio del undo, porque toca que este open, entonces por ese lado tampoco supe como.
Actualmente solo tengo exp de los esquemas individuales, no de la db full, y pues en esta db no esta en archivelog.  Como era para  pruebas no tenia configurado un esquema de seguridad ante fallos.
Tu me podrías indicar si como podría hacerla recuperación de la bd?
Gracias.