Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 3471
  • 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

"Instance name is not unique" even though there are no instances named like so

kitmonisit

I am trying to rename an instance to, for example, K0, but I get an error (SCH-1025): Instance name "K0" is not unique. I am sure that there are no other instances currently named K0 in the schematic.

Is this a bug?

I think this is a cache problem. Is there a way I can clear the cache of instance names? 

Parents
  • Andrew Beckett

    In the CIW, can you try do this (with the schematic open for edit):

    cv=geGetEditCellView()
    inst=dbFindAnyInstByName(cv "K0")

    does it return anything?

    I have seen one case where the check above (actually it was for an iterated instance) returned nil, and I had to do (at the UNIX level):

    oaScan  -lib libName -cell cellName -view schematic

    which reported an issue with the database, and then I called it again with -repair to fix it. Note that you need to have the schematic closed in the editor to be able to run oaScan.

    But most lilely it is that you really have an instance called K0 somewhere...

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    In the CIW, can you try do this (with the schematic open for edit):

    cv=geGetEditCellView()
    inst=dbFindAnyInstByName(cv "K0")

    does it return anything?

    I have seen one case where the check above (actually it was for an iterated instance) returned nil, and I had to do (at the UNIX level):

    oaScan  -lib libName -cell cellName -view schematic

    which reported an issue with the database, and then I called it again with -repair to fix it. Note that you need to have the schematic closed in the editor to be able to run oaScan.

    But most lilely it is that you really have an instance called K0 somewhere...

    Regards,

    Andrew.

Children
No Data

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.