Ir para conteúdo

Arquivado

Este tópico foi arquivado e está fechado para novas respostas.

Muricy

Base não conecta e desmonta automáticamente.

Recommended Posts

Estou com um probleminha...Instalei o servidor Oracle Xe e funciona perfeitamente...Conectado a um sistema em VB ele funciona tranquilamente...Foi criado um utilitário que todos os dias a 00:30 ele dispara o comando "exp usuario/senha file=backup.dmp log=backup.log owner=CADASTROS statistics=none"Ai vem um problema... algumas vezes ao tentar entrar no Sistema usando a Base Oracle ela esta desmontada... e para voltar a funcionar, tenho que Parar a Base e Iniciar novamente.Logo no inicio não acontecia... mas sempre depois de 2 ou 3 dias começa a dar esse problema todos os dias.Alguem pode me dizer se o comando EXP requer que a base seja montada novamente depois??? ou onde posso localizar o log do servidor para poder encontrar o que pode estar acontecendo?Obrigado a todos.

Compartilhar este post


Link para o post
Compartilhar em outros sites

Muricy, Verifica o ALERT.log da sua instância Oracle, que se encontra no diretorio BDUMP. O EXP não precisa estar em MOUNT, alias, ele nem funciona em MOUNT, somente OPEN! Alguma rotina de backup COLD deve estar sendo realizada na empresa e esqueçeram de colocar o comando ALTER DATABASE OPEN; Abraços,

Compartilhar este post


Link para o post
Compartilhar em outros sites

Alphamek, obrigado por sua atenção...Olha o log como esta...Completed: alter database openTue Apr 24 00:34:30 2007db_recovery_file_dest_size of 10240 MB is 0.98% used. This is auser-specified limit on the amount of space that will be used by thisdatabase for recovery-related files, and does not reflect the amount ofspace available in the underlying filesystem or ASM diskgroup.Tue Apr 24 00:34:31 2007Starting ORACLE instance (normal)Tue Apr 24 02:08:10 2007KCF: write/open error block=0x79 online=1 file=2 D:\APPS\SIXX\ORACLEEXE\ORADATA\XE\UNDO.DBF error=27072 txt: 'OSD-04008: WriteFile() failure, unable to write to fileO/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.'Tue Apr 24 02:08:11 2007Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_dbw0_3668.trc:ORA-01242: data file suffered media failure: database in NOARCHIVELOG modeORA-01114: IO error writing block to file 2 (block # 121)ORA-01110: data file 2: 'D:\APPS\SIXX\ORACLEEXE\ORADATA\XE\UNDO.DBF'ORA-27072: File I/O errorOSD-04008: WriteFile() failure, unable to write to fileO/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.DBW0: terminating instance due to error 1242Tue Apr 24 02:08:12 2007Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_q001_1048.trc:ORA-01242: data file suffered media failure: database in NOARCHIVELOG modeTue Apr 24 02:08:12 2007Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_psp0_3040.trc:ORA-01242: data file suffered media failure: database in NOARCHIVELOG modeTue Apr 24 02:08:12 2007Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_lgwr_3568.trc:ORA-01242: data file suffered media failure: database in NOARCHIVELOG modeTue Apr 24 02:08:13 2007Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_mman_2788.trc:ORA-01242: data file suffered media failure: database in NOARCHIVELOG modeTue Apr 24 02:08:13 2007Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_ckpt_2896.trc:ORA-01242: data file suffered media failure: database in NOARCHIVELOG modeTue Apr 24 02:08:14 2007Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_j000_1028.trc:ORA-01242: data file suffered media failure: database in NOARCHIVELOG modeTue Apr 24 02:08:15 2007Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_pmon_3504.trc:ORA-01242: data file suffered media failure: database in NOARCHIVELOG modeTue Apr 24 02:08:25 2007Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_reco_2164.trc:ORA-01242: data file suffered media failure: database in NOARCHIVELOG modeTue Apr 24 02:08:25 2007Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_smon_3964.trc:ORA-01242: data file suffered media failure: database in NOARCHIVELOG modeTue Apr 24 02:08:28 2007Instance terminated by DBW0, pid = 3668Dump file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\alert_xe.logTue Apr 24 08:23:03 2007ORACLE V10.2.0.1.0 - Production vsnsta=0vsnsql=14 vsnxtr=3Windows Server 2003 Version V5.2 Service Pack 1CPU : 2 - type 586, 2 Physical CoresProcess Affinity : 0x00000000Memory (Avail/Total): Ph:111M/511M, Ph+PgF:895M/1257M, VA:1945M/2047MTue Apr 24 08:23:03 2007Starting ORACLE instance (normal)LICENSE_MAX_SESSION = 0LICENSE_SESSIONS_WARNING = 0Picked latch-free SCN scheme 2Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DESTAutotune of undo retention is turned on. IMODE=BRILAT =10LICENSE_MAX_USERS = 0SYS auditing is disabledksdpec: called for event 13740 prior to event group initializationStarting up ORACLE RDBMS Version: 10.2.0.1.0.System parameters with non-default values: sessions = 49 __shared_pool_size = 79691776 __large_pool_size = 8388608 __java_pool_size = 4194304 __streams_pool_size = 0 spfile = D:\APPS\SIXX\ORACLEEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA sga_target = 146800640 control_files = D:\APPS\SIXX\ORACLEEXE\ORADATA\XE\CONTROL.DBF __db_cache_size = 50331648 compatible = 10.2.0.1.0 db_recovery_file_dest = D:\APPS\SIXX\OracleExe\app\oracle\flash_recovery_area db_recovery_file_dest_size= 10737418240 undo_management = AUTO undo_tablespace = UNDO remote_login_passwordfile= EXCLUSIVE dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB) shared_servers = 4 job_queue_processes = 4 audit_file_dest = D:\APPS\SIXX\ORACLEEXE\APP\ORACLE\ADMIN\XE\ADUMP background_dump_dest = D:\APPS\SIXX\ORACLEEXE\APP\ORACLE\ADMIN\XE\BDUMP user_dump_dest = D:\APPS\SIXX\ORACLEEXE\APP\ORACLE\ADMIN\XE\UDUMP core_dump_dest = D:\APPS\SIXX\ORACLEEXE\APP\ORACLE\ADMIN\XE\CDUMP db_name = XE open_cursors = 300 os_authent_prefix = pga_aggregate_target = 41943040PSP0 started with pid=3, OS id=388PMON started with pid=2, OS id=1620MMAN started with pid=4, OS id=3448DBW0 started with pid=5, OS id=4024CKPT started with pid=7, OS id=2504RECO started with pid=9, OS id=2380MMON started with pid=11, OS id=2056LGWR started with pid=6, OS id=372SMON started with pid=8, OS id=2160CJQ0 started with pid=10, OS id=292MMNL started with pid=12, OS id=3896Tue Apr 24 08:23:17 2007starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...starting up 4 shared server(s) ...Oracle Data Guard is not available in this edition of Oracle.Tue Apr 24 08:23:23 2007alter database mount exclusiveTue Apr 24 08:23:28 2007Setting recovery target incarnation to 2Tue Apr 24 08:23:29 2007Successful mount of redo thread 1, with mount id 2501862075Tue Apr 24 08:23:29 2007Database mounted in Exclusive ModeCompleted: alter database mount exclusiveTue Apr 24 08:23:30 2007alter database openTue Apr 24 08:23:32 2007Beginning crash recovery of 1 threadsTue Apr 24 08:23:32 2007Started redo scanTue Apr 24 08:23:35 2007Completed redo scan 1455 redo blocks read, 309 data blocks need recoveryTue Apr 24 08:23:35 2007Started redo application at Thread 1: logseq 22, block 64485Tue Apr 24 08:23:36 2007Recovery of Online Redo Log: Thread 1 Group 1 Seq 22 Reading mem 0 Mem# 0 errs 0: D:\APPS\SIXX\ORACLEEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_32D88N1Y_.LOGTue Apr 24 08:23:40 2007Completed redo applicationTue Apr 24 08:23:40 2007Completed crash recovery at Thread 1: logseq 22, block 65940, scn 1291010 309 data blocks read, 307 data blocks written, 1455 redo blocks readTue Apr 24 08:23:45 2007Thread 1 advanced to log sequence 23Thread 1 opened at log sequence 23 Current log# 2 seq# 23 mem# 0: D:\APPS\SIXX\ORACLEEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_32D89JPY_.LOGSuccessful open of redo thread 1Tue Apr 24 08:23:46 2007SMON: enabling cache recoveryTue Apr 24 08:23:54 2007Successfully onlined Undo Tablespace 1.Tue Apr 24 08:23:54 2007SMON: enabling tx recoveryTue Apr 24 08:23:55 2007Database Characterset is AL32UTF8replication_dependency_tracking turned off (no async multimaster replication found)Starting background process QMNCQMNC started with pid=19, OS id=3848Tue Apr 24 08:24:08 2007Completed: alter database openTue Apr 24 08:24:15 2007db_recovery_file_dest_size of 10240 MB is 0.98% used. This is auser-specified limit on the amount of space that will be used by thisdatabase for recovery-related files, and does not reflect the amount ofspace available in the underlying filesystem or ASM diskgroup.Tue Apr 24 08:24:21 2007Starting ORACLE instance (normal)

Compartilhar este post


Link para o post
Compartilhar em outros sites

Você está com o serviço de ARCHIVE ligado e com o banco em NOARCHIVELOG?Abraços,

Alphamek, Como posso verificar essas informações para lhe passar?Fiz a instalação padrão do Oracle XE e não mudei nada.

Compartilhar este post


Link para o post
Compartilhar em outros sites

Para verificar faça o seguinte:

 

conect-se no banco de dados com o usuário SYS AS SYSDBA, exemplo:

 

C:\> set ORACLE_SID=XEC:\> echo %ORACLE_SID%C:\> sqlplus sys as sysdba

Depois, para verificar o serviço de ARCHIVE, basta executar:

 

SQL> archive log list

E coloque a resposta aqui no fórum.

 

Abraços, ;)

Compartilhar este post


Link para o post
Compartilhar em outros sites

×

Informação importante

Ao usar o fórum, você concorda com nossos Termos e condições.