We recenlty upgraded from 16.3 to 16.6. since then ive been experiencing the following Errors when i open the company OLB library.
ERROR(ORCAP-1558): Unexpected error in database access.ERROR(ORDBDLL-1016): File not found
At first i was able to just click through the errors and it would end up working, it was annyoing but i could make my canges and additions and all was OK, but just today it has now got worse where it closes the library when it gets the error. So now i cant get my work done. None of the other engineers here are expereincing this issue on their machines.
Any Ideas? What database is it referinging to, the olb file is local to my machine is it calling that library a database?
In reply to oldmouldy:
Do you know of any simple way to determine what symbol or symbols are corrupt?
I do still find this very strange. I would think that if there was a corruption issue that everyone using the library would be experiencing the same behavior, but none of the other engineers have been seeing this issue. Also it only started happening when i upgraded from 16.3 to 16.6. The other engineers have also upgraded to 16.6 as well. The one difference i can think of is that im running windows7 64bit.
In reply to C4Blake:
You might have found a solution already, but I just realized that this is caused by one or more corrupted symbols. The error is still there in 16.2 and upwards, but it seems like 16.6 is reporting the error more frequently(a lot of dialog boxes).
Open the library in Orcad, highlight the top symbol and the step through all with the down arrow. Click once pr. symbol. When you come to the corrupted symbol you wil get the error and Orcad might crash. Then do as described above, that means delete the .opj file and then copy all working symbols from the old library to a new.
It might be an easier way of detecting the corrupted symbol, but this was the quickest for me.
In reply to Cantstandya:
Thanks Cantstandya - the click through tip worked great for me.
Basically, that's what we've been doing as well. Search for the corrupted symbol and copy everything else to a new library. HOWEVER - that's not the end of it. Our library team has been having had to deal with this weekly!
I appreciate the methodology from "oldmouldy", that will help us track down the process issue(s) we may be doing to create this error.
This should NOT BE AN ERROR! It would be very nice if Cadence would fix it!!! Can we please get cleanup on aisle 5, "Library symbol cache editors"? Or does anyone know of an "add-on" for library management that will help resolve the issue?