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

Upgrade to v7.0.2

Hello

We have a new instance of V7.0.2 set up and trying to move schema extensions from 6.1.3 to 7.0.2. I am getting an error

"Table DialogCustomSQL" not found. The schema extensions that I am porting over are not in DialogCustomSQL in 6.1.3 at all. Any ideas how I can overcome this?

Thanks in advance

  • I wasn't even aware you could migrate from v6 to v7! AFAIK there is no migration path and you need to do a fresh installation of v7, but of course I could be wrong

    Would appreciate some insight into this myself.

  • No, that's not correct.  You can absolutely migrate from 6 to 7.  You do need to make sure that any custom schema, scripts, etc. are compatible with the renamed tables and keys, however.

  • Ah thanks George, good to know that.

  • There are quite a few tables that have been removed in v7.0.2. That's the reason the custom schema extensions are not importing properly.

    We are trying to create custom schema extensions manually. However, I am posting here to find out if any one has a better way of doing this

    Thanks in advance

  • Hi mellac

    There's no chance to move schema extensions from 6.x to 7.x using the transporter tool. Both, the database schema and the transporter architecture are completely different from V6 to V7.
    If you're considering a inplace-upgrade from V6 to V7 try to get in touch with support and ask for the Upgrade whitepaper and the M61 package, which is a complex but existing way to upgrade from V6 to V7.
    If you're recreating your 6.x functionality in a new 7.x infrastructure, there is no way to transport any of the configuration.

    Best Regards
    Carsten

  • Thanks everyone for the response