Hi @smithmich,
That table should definitely be present in a healthy OJS 2.3.2 installation. I think you’re running into the situation described on this thread – your database at some point was partially upgraded, but the upgrade failed and the journal continued to operate with the database stranded between the two versions. Do you know the journal’s upgrade history?
Regards,
Alec Smecher
Public Knowledge Project Team