When I issue the update command in the Virtuoso Library Manager, I get an "Update Failed" message, and it mentioned having corrupt project data. I wanted to understand how to fix it. When I was browsing the Table of Contents in the "Cadence Library User Guide", I didn't see in sections which looked like it even mention library corruption. By the way, I checked the log file and a few interesting messages: ------------------------- Error (gdm): [vsupdate: Unable to lock view: File exists: /proj/chip100/.VSVAULT/PLL/schematic/.vscview.lck .... (gdm [vsupdate: Updated to version 1.1: file OPAMP/schematic/sch.cdb Error (gdmExec): command vsupdate failed with status 1 Error (gdmupdate): The command: vsupdate failed. ..... gds vsupdate updated to version 1.1: file OpampAmp2/symbol/pc.db Warning: gdmupdate exited with status 2 ------------------------------
Is this your problem, what version of icfb are u using? http://sourcelink.cadence.com/docs/db/kdb/2003/May/11090924.html Here is a snap from sourcelink, Problem statement: Using IC50ISR 5.0.0.500.31 to 5.0.0.500.35 : When doing DM operations like update, checkin, checkout on libraries with large number of cells , it fails with above mentioned error message. Error message: Error (gdmExec): command vsupdate failed with status 255 OR Error (gdmExec): command vsci failed with status 255 OR Error (gdmExec): command vsco failed with status 255 Solution: The problem has been identified by Cadence R&D to be in the wrapper script wrap3264. This script is used to facilitate picking 32/64 bit versions of versionsync binaries as needed. This is the script that is failing. It is failing because it can't handle a large number of command line arguments properly when calling ,say vsci. This Problem is already fixed but not yet available in any ISR or MSR. Till then there are two workarounds , if you must fix this problem immediately : 1. Modify the installation. Remove all the vs* and *_vs files files from <install_dir>/tools/bin (these are actually hard links to wrap3264) and replace them with copies of what's in <install_dir>/tools/bin/32bit Do the following to see which files need replacement : unix>ls -al <install_dir>/tools/bin/vs* unix>ls -al <install_dir>/tools/bin/*_vs 2. Put <install_dir>/tools/bin/32bit in your unix path before <install_dir>/tools/bin directory Either case will make the 64bit VS commands unavailable. Option 2 will only affect those users that change path. Option 1 will affect everyone that uses the installation. The issue is fixed in: IC5033USR3 IC5141 ---------------------- Cadence Internal Reference : PCR 570677
