ora10g win2003server standart edition
du skirtingi servai su shita problema


tracelogas nieko blogo nepasokaja

alert logas meta:
Tue Jun 09 15:42:59 2009
ARC0: Archive destination LOG_ARCHIVE_DEST_2 made inactive: exceeded quota
Tue Jun 09 15:43:00 2009
Errors in file d:\oracle\admin\sid_name\bdump\sid_name_arc1_1764.trc:
ORA-00313: open failed for members of log group 7 of thread 1

db_recovery_file_dest_size of 20480 MB is 1.88% 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 Jun 09 15:43:03 2009
Successfully onlined Undo Tablespace 1.
Tue Jun 09 15:43:03 2009
SMON: enabling tx recovery
Tue Jun 09 15:43:05 2009
Database Characterset is WE8MSWIN1252
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=22, OS id=328
Tue Jun 09 15:43:15 2009
Completed: alter database open
Tue Jun 09 15:45:10 2009
Errors in file d:\udump\sid_name_ora_3868.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [___intel_new_memcpy+67] [PC:0x27BE5E3] [ADDR:0xDB41E53] [UNABLE_TO_READ] []

Tue Jun 09 15:45:12 2009
Errors in file d:\udump\sid_name_ora_3868.trc:
ORA-00308: cannot open archived log 'C:\ORACLE\ORADATA\sid_name\ONLINELOG\O1_MF_7_4QV9TG3F_.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [___intel_new_memcpy+67] [PC:0x27BE5E3] [ADDR:0xDB41E53] [UNABLE_TO_READ] []

Tue Jun 09 15:46:58 2009
Errors in file d:\udump\sid_name_ora_1292.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [___intel_new_memcpy+67] [PC:0x27BE5E3] [ADDR:0xF5E1E53] [UNABLE_TO_READ] []


(sid_name vietoj yra normalus sid_neimas:)

turejau minti gal del oraklinio dzhiaugsmo su 4gb ramo (tik tiek ir yra ten, o oraklas kaip zhinia turi idomumu su 4 gb:) pakeichiau boot.ini i noexecute=alwaysoff /PAE /3GB.

Problema ishkyla vykdand didesne query i duombaze. Tik vienoj vietoj jis nuluzhta su shituo erroru, kitoj vietoj, kolkas berods vel viskas gerai, ishbandzhiau trechioj vietoj, jis tiesiog ishmeta ora nt connected to oracle ir restartuoja softa:) (chia tikrai _labai_ didele uzhkausa darant)
"Ness" <aggb_nutrinti@inbox.lt> wrote in message news:h0ljiu$odl$1@trimpas.omnitel.net...
> idomu kokia platforma (hardas, softas), ka raso tracelog?
> 
> 
> 
> "Toxis@ze_yvil_place" <tox@work.ble> wrote in message 
> news:h0l3ob$rc9$1@trimpas.omnitel.net...
>>
>> Taigi, atejo pas mane dziugi diena pavadinimu ORA-07445.
>> Ir ash net neitariu ar mes turim tiesiogini accessa su oraclu:)
>> Tiesa ash turiu itarima, kad problema yra vienam udump'o ir vienam bdumpo 
>> faile, kai jis daeina iki vieno failo - nebesugeba jo perskaityt ir 
>> keikiasi kaip vezhikas.
>> Ka ash iki shiol dariau: bendzhiau ish'cut'int visus udump'o ir bdump'o 
>> failus kitur. Permechiau udumpa kitur (ALTER SYSTEM SET user_dump_dest = 
>> 'D:\udump\' SCOPE=both;).. deja shitas fyntas padejo kokiai savaitei ar 
>> pusei savaites - shiandien vel, pasieke viena filename'a ir pradejo 
>> keiktis.
>> Gal ymanoma kazhkaip crosscheckint udumpa ir bdumpa?
>> Apskrytai, kokie vaistai yra nuo 7445'o erroro?
>>
>> Uzh pagalba - alus kaip minimum:)
>> -- 
>> ___________
>> ©Toxis 
> 
>