# How use old idb with new ida 9 eh(exception) plugin?
**URL:** https://community.hex-rays.com/t/how-use-old-idb-with-new-ida-9-eh-exception-plugin/219
**Category:** IDA General
**Created:** [March 3, 2025, 12:16pm UTC](https://community.hex-rays.com/t/how-use-old-idb-with-new-ida-9-eh-exception-plugin/219 "2025-03-03T12:16:00Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@revs](https://community.hex-rays.com/u/revs)
#### Post date: [March 3, 2025, 12:16pm UTC](https://community.hex-rays.com/t/how-use-old-idb-with-new-ida-9-eh-exception-plugin/219/1 "2025-03-03T12:16:00Z")
there is a problem with using old databases in the new version of ida 9
when using the hexrays plugin with exceptions
the thing is that exceptions are not visible
you need to completely load the file from scratch for analysis in ida 9
to see exceptions
could you do something about this
I have a lot of databases that I don’t want to start reverse again to start using the hexrays plugin for exceptions
---
### Author:  [@Ndgs](https://community.hex-rays.com/u/Ndgs)
#### Post date: [March 11, 2025, 10:47pm UTC](https://community.hex-rays.com/t/how-use-old-idb-with-new-ida-9-eh-exception-plugin/219/2 "2025-03-11T22:47:05Z")
Have you tried going into the general options and clicking Reanalyze?
Personally I haven’t found much use for Reanalyze based on my use-cases but maybe it would help for your situation?
---
### Author:  [@revs](https://community.hex-rays.com/u/revs)
#### Post date: [March 12, 2025, 11:55am UTC](https://community.hex-rays.com/t/how-use-old-idb-with-new-ida-9-eh-exception-plugin/219/3 "2025-03-12T11:55:40Z")
it doest help
as example
i have already idb from ida 83
load into ida 90
after converting it to the new format of ida 90
i goto to function with try/catch
press F5 i got from ida console
> could not find valid save-restore pair for rbp
after press button “Reanalyze program”
and wait to finish reanalyze
F5 again and again
i got the same
> could not find valid save-restore pair for rbp
if i load original exe file to 90
i see a try/catch
---
### Author:  [@igor](https://community.hex-rays.com/u/igor)
#### Post date: [March 13, 2025, 12:07pm UTC](https://community.hex-rays.com/t/how-use-old-idb-with-new-ida-9-eh-exception-plugin/219/4 "2025-03-13T12:07:35Z")
Unfortunately, some information used by the eh34 plugin is only parsed on the initial load and extracting it from old IDB may be difficult or impossible. It is unlikely that we’ll work on this use case unless there is significant demand (and plenty of samples), so for now I’d suggest to transfer information from the old IDB into the new one.
---
### Author:  [@revs](https://community.hex-rays.com/u/revs)
#### Post date: [March 13, 2025, 1:12pm UTC](https://community.hex-rays.com/t/how-use-old-idb-with-new-ida-9-eh-exception-plugin/219/5 "2025-03-13T13:12:37Z")
how compatible is idc api \< ida 9.0 with idc ida 9.0 \>=
because even if compatible
a lot of manual work to remake idc script to apply the same binary loaded from scratch in the new ida 9.x
because by default the exported script
starts to delete the entire database and analyze it again
and if you didn’t know, this resulting analysis is even worse than the primary ida analysis when loading exe
I would like to receive only structures and function names in idc export
so that they can be applied over the same file in the new ida 9.x
and here we return to the topic
about local synchronization between ida
> [@Anyway to syncronize common type declaration between Ida databases?](https://community.hex-rays.com/t/anyway-to-syncronize-common-type-declaration-between-ida-databases/183):
>
> Often revers engendering target consist of multiple modules that interact between each. So they have some types that are common for them. Now is synchronizing such types between ida databases for each module are manual task that time consuming and prone to errors. AFAIK no Lumina or Teams can’t do type synchronization for different databases. Any plans to implement such feature?
---
### Author:  [@igor](https://community.hex-rays.com/u/igor)
#### Post date: [March 13, 2025, 2:05pm UTC](https://community.hex-rays.com/t/how-use-old-idb-with-new-ida-9-eh-exception-plugin/219/6 "2025-03-13T14:05:32Z")
Yes, IDC export is not ideal and was developed back when files were small and not complicated, but it’s better than nothing. You can comment out the parts which you would like to skip. A better database migration feature is on our roadmap although we don’t have a specific date at this time.