Re: Oracle and W32.Bugbear.B@mm

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Ivica Dimjasevic

    #1

    Re: Oracle and W32.Bugbear.B@mm

    I don't know. This redo log corruption occurred on three machines with
    Personal 8.0.4., in period of two days, and on every system Bugbear was
    detected.

    We have installations of PE 8.0.4. in many locations. At the end of day a
    procedure is started on each location. It prepares data for sending to
    central location. Procedure deletes "transfer" tables and inserts data into.
    After that we use EXP80 to export these transfer tables. Export file is
    zipped and sent to e-mail client (Outlook express in our case). This process
    worked without errors for 3 years until now.

    It is very strange that on all machines redo log corruption occurred when
    export file was created and sent to e-mail.

    Is it possible that Windows memory swapping makes these errors? Machines
    have only 128 MB RAM with Win2000 installed (more than 200 MB is allocated
    when all application are running).
    Any ideas?

    Ivica


    "Jim Kennedy" <kennedy-down_with_spamm ers@comcast.net wrote in message
    news:ZqqOa.1777 $OZ2.726@rwcrns c54...
    It would have to corrupt the file system or specific files. Just like if
    you took a disk editor and flipped some bits on a file (eg a redo log
    file).
    Not a lot that Oracle can do about that. Good thing you have a backup.
    Jim
    >
    "Ivica Dimjasevic" <remove_smokeso ft@hi.htnet.hrw rote in message
    news:bec862$2e1 5$1@as201.hinet .hr...
    Hi!

    Maybe question is offtopic but I need help.
    Is it possible that Bugbear.B causes redo log file corruption on machine
    with Oracle 8.0.4. Personal Edition?

    Oracle can't open database because of error:
    ORA-00356: inconsistent lengths in change description
    ORA-00353: log corruption near block 374 change 14057424 time 07/03/03
    13:15:04
    ORA-00312: online log 1 thread 1: 'C:\ORANT\DATAB ASE\...'

    We found W32.Bugbear.B@m m on machine and we are 100% sure that on
    07/03/03
    at 13:15 Outlook express was started.

    Thanx.

    Ivica
    >
    >
Working...