Postgres Reverse Engineering error The Parameter is incorrect

I downloaded latest version of ER Studio last week.

I downloaded latest version of Postgres last week.

I can connect from ER Studio via ODBC on my local windows PC.

ER Studio can see the objects available. I select the tables I want reverse engineered. It goes through them all it appears (as script flies by).

However right at the end it pops up an error 'The parameter is incorrect'.

I unchecked all 'options' such as drive relationships from indexes etc so it becomes the most basic reverse engineer of tables only. No matter - same error.

Thoughts?

Parents
  • Hi dg1,

    I get the same issue when I reverse engineer the table: information_schema.sql_languages

    If I exclude this specific table, the process does its job as expected.

    I'd try to reverse engineer half your tables to check if it works.

    • If it works, I try to reverse engineer the other half. This should generate the error.
    • if it doesn't work, I try to reverse engineer and I hope you get half of your tables. If it also generates the message, you have several tables which can't be reverse engineered. 

    Then, I'd reverse engineer the other half of the tables which triggered the error, and iterate to find the table(s) which one triggers the issue.

    Maybe, there's something specific which is not supported by the ODBC driver which Data Architect tries to use.

    I hope this helps. Let me know.

    Cheers,

      W.

Reply
  • Hi dg1,

    I get the same issue when I reverse engineer the table: information_schema.sql_languages

    If I exclude this specific table, the process does its job as expected.

    I'd try to reverse engineer half your tables to check if it works.

    • If it works, I try to reverse engineer the other half. This should generate the error.
    • if it doesn't work, I try to reverse engineer and I hope you get half of your tables. If it also generates the message, you have several tables which can't be reverse engineered. 

    Then, I'd reverse engineer the other half of the tables which triggered the error, and iterate to find the table(s) which one triggers the issue.

    Maybe, there's something specific which is not supported by the ODBC driver which Data Architect tries to use.

    I hope this helps. Let me know.

    Cheers,

      W.

Children
No Data