• Resolved pvsnpkumar

    (@pvsnpkumar)


    Starting DB prefix change operations…..

    Your WordPress system has a total of 37 tables and your new DB prefix will be: koe_

    A backup copy of your wp-config.php file was created successfully!

    37 tables had their prefix updated successfully!

    Checking for MySQL tables of type “view”…..

    Update of the following MySQL view definition failed: select if(isnull(performance_schema.accounts.HOST),’background’,performance_schema.accounts.HOST) AS host,sum(stmt.total) AS statements,sys.format_time(sum(stmt.total_latency)) AS statement_latency,sys.format_time(ifnull((sum(stmt.total_latency) / nullif(sum(stmt.total),0)),0)) AS statement_avg_latency,sum(stmt.full_scans) AS table_scans,sum(io.ios) AS file_ios,sys.format_time(sum(io.io_latency)) AS file_io_latency,sum(performance_schema.accounts.CURRENT_CONNECTIONS) AS current_connections,sum(performance_schema.accounts.TOTAL_CONNECTIONS) AS total_connections,count(distinct performance_schema.accounts.USER) AS unique_users,sys.format_bytes(sum(mem.current_allocated)) AS current_memory,sys.format_bytes(sum(mem.total_allocated)) AS total_memory_allocated from (((performance_schema.accounts join sys.x$host_summary_by_statement_latency stmt on((performance_schema.accounts.HOST = stmt.host))) join sys.x$host_summary_by_file_io io on((performance_schema.accounts.HOST = io.host))) join sys.x$memory_by_host_by_current_bytes mem on((performance_schema.accounts.HOST = mem.host))) group by if(isnull(performance_schema.accounts.HOST),’background’,performance_schema.accounts.HOST)

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, are you saying that changing the database prefix failed in your site? If that is the case, what type of server is your site hosted in?

    Thank you

    Thread Starter pvsnpkumar

    (@pvsnpkumar)

    I am checking in my local machine with Bitnami WAMP server latest version.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, I have changed the database prefix in 3 different servers without any issues.

    Have you tested this in a live server? But remember as a precaution always create a database backup before you go ahead just in case some strange issue occurs.

    Regards

    Hi,

    I have exactly the same issue, with exactly the same error message “Update of the following MySQL view definition failed”. I was running WP on a local MAMP server.
    Would be nice if this issue could be solved because I found All In One WP Security pretty useful and I prefer to prepare a site on a local server first.

    Regards

    • This reply was modified 6 years, 4 months ago by triptrap.
    • This reply was modified 6 years, 4 months ago by triptrap.
    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi @triptrap,

    Would be nice if this issue could be solved because I found All In One WP Security pretty useful and I prefer to prepare a site on a local server first.

    In my opinion it is best that you change your database prefix in your live server and not locally in your computer or laptop using Mamp or Xampp. This will avoid any issues you might run into.

    Kind regards

    Hi mbrsolution,

    ok thank you, I will follow your suggestion then!

    Actually, I observed some more troubles when I installed the plugin and activated its security features right away on my local MAMP server, like for example being denied acces to the login area.

    The interesting thing is that I never observed these issues with my other WP site, where I installed the plugin and activated its features first on the live server and then migrated it to my local host to do futher development. That site I migrated back and forth several times and never encountered any troubles, neither on the live nor on the local server. So I guess that procedure will be my best practise and is somehow compatible with your suggestion.

    Thanks again & kind regards

    • This reply was modified 6 years, 4 months ago by triptrap.
    • This reply was modified 6 years, 4 months ago by triptrap.
Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘After DB Prefix changing getting below issue’ is closed to new replies.