Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 14547
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

dbOpenCellViewByType: Corrupted database encountered:

sl933

Hi,

My cadence crashed, and I had to restart and remove the lock files.

Post the crash, a cell became corrupted, which I can no longer access. When I try to access the cell, I get the following error:

(DB-270000): dbOpenCellViewByType: Corrupted database encountered: Unable to read design data from design [my_cell_name/schematic]. The long mapWindow cannot determine the byte-swap direction. The value 0x2a2a2a2a is an unexpected value. Try oaScan to scan/repair the database, revert it to a backed up version, or recreate it.


So I ran the oaScan on that corrupted cell, but it returns an error:

ERROR: (OA-131): Corrupted database encountered: Unable to read design data from design my_cell_name/schematic. The long mapWindow cannot determine the byte-swap direction. The value 0x2a2a2a2a is an unexpected value.
NOTE: 1 error encountered that prevents the scan of this database.
No inconsistencies found in 4 databases
- found in 0 of 2 designs
- found in 0 of 2 DMDatas
Finished: oaScan

Is there any other way I can try to salvage the corrupted cell?

I am using version IC6.1.8-64b.500.6.

Thanks,

Sunwoo

  • Hi Sunwoo

    It seems that you are using quite an outdated version of Virtuoso (IC618-ISR6). Would you please try oaScan from the latest version (IC618-ISR15)? If your company uses a file server, you can also check if there is a .snapshot or similar directory from which you can recover the files.

    E.g. suppose your path is /net/dir1/dir2/sunwoo, .snapshot directory might be located at /net/dir1/.snapshot, etc


    Best regards
    Quek

  • in reply to Quek

    Hi Sunwoo,

    There have been a couple of reports of this message, and sometimes it has been a true data loss (although that is extremely rare (and by extremely rare, I mean extremely rare - I've hardly ever seen this), because there is a lot of care taken to avoid the risk of losing data). As Quek suggested, the first thing is to try using a new version of oaScan from a later version - but you might also want to contact customer support. Worst case you may need to rely on backups...

    Andrew

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.