[Mahesh]

We have fixed this issue in this special build.

To Download Click here

Please verify and update the status.

Thanks,

Mahesh

[Mahesh]

We have tried migration from v3.75 to v4.12 but could not able to reproduce this scenario.

Can you please tell us certain information mentioned below:

1) Attach a MONyog.log file

2) Attach a screenshot showing processlist page of problematic server?

Also what does other MySQL client returns on execution of:

SHOW FULL PROCESSLIST;

Also please paste the result of this query here itself.

3) MySQL server version?

[Mahesh]

Do I need to reregister the servers in the new system?

— There is no need to re-register server if you are copying from older version to newer version of MONyog.

We tried at our end — Migration of v3.65 /data/ folder from Windows to Linux where MONyog v4.02 is running, it displays registered servers in Linux system.

BTW: Source — Windows XP and Target – CentOS 5.5(64 bit).

To reproduce this issue we need some information mentioned below:

1) Exact Windows and Linux version ?

2) Zip and attach MONyog.log file from MONyog running in Linux (/usr/local/MONyog/MONyog.log)

[Mahesh]

It will be better to have web meeting.

Please tell us in which timezone you are in and suitable time to have online screen sharing session using GoToMeeting?

You can create a ticket for privacy

http://webyog.com/support

[Mahesh]

Please try MONyog(MySQL Monitoring and Advisory tool)

The Query Analyzer feature of MONyog helps you identify problem SQL. MONyog can find problem SQL by one or more of the following methods:

1.

Taking SHOW PROCESSLIST snapshots at regular intervals (using MONyog Sniffer)

2.

Using MySQL Proxy to collect profiling data (using MONyog Sniffer)

3.

Parsing Slow Query Log and General Query Log (using MONyog Log Parser)

There are several advantages and disadvantages of each approach.

SHOW PROCESSLIST is available in all MySQL versions and it is the easiest to setup. However, taking a snapshot of SHOW PROCESSLIST does not guarantee that all queries will be captured. Many short-lived queries can be missed between two successive snapshots. It is a quick and easy way to find long running queries.

Log parsing requires some additional setup. Also, switching on the General Query Log puts a significant amount of load on the server. You should always keep the Slow Query Log switched on. Parsing the Slow Query Log is an effective way to find bad queries.

Using MySQL Proxy gives you the most accurate information on profiling SQL. However, during profiling you have to configure your clients to connect to MySQL Proxy, which in turn connects to MySQL server. Using MySQL Proxy ensures that all queries are profiled. It helps you to find problematic queries that don't take much time, but are executed thousands of times. Eliminating such queries can significantly improve the performance of your application.

To use the MONyog Query Analyzer functionality for a specific server, the server 'general query log' or 'slow query log' details must be configured in 'Connection Settings' or a 'query sniffer' must be enabled for that server.

Using the above tools to find problem SQL is almost always a post-mortem excercise. In certain situations you may want real-time notifications for long-running queries. MONyog can continuously monitor queries in real-time and send notifications (on mail or SNMP) for queries that take more than a specified amount of time to execute. You can also specify an option to kill such queries instantly.

You can download TRIAL version of MONyog from here:

http://webyog.com/en/downloads.php

[Mahesh]

This is really weird behavior.

Can you attach a source and target .SQL dump (zip format) where this issue is reproducible.

If you are unable to upload dump files here please follow the steps mentioned below:

We have created an account for you to send files here, http://www.yousendit.com/login.php

Please login with the below details,

Email : [email protected]

Password : tester

and send file(zipped) to email address “[email protected]” mentioning subject as “Datasync problem”

You can create a ticket for privacy of data

http://webyog.com/support

[Mahesh]

We have fixed this problem,

Now you can download from Customer Area.

Sorry for the inconvenience.

[Mahesh]

Hi Saleem,

I think it will be better idea to have GoTo meeting session.

Please create a ticket from here :

http://webyog.com/support/

Also please attach a job file(s) created with both 7.x and 8.x, Connection type(Direct,HTTP,SSH) and mention which timezone you are in and suitable time to have online meeting session in ticket itself ?

[Mahesh]

Can you please check with other applications like Notepad,MSPAINT etc..

Also please tell OS type and language used?

[Mahesh]

Also, This issue may happen if table(s) are getting locked somehow.

Please change the all tables type to INNODB because MYISAM table(s) uses table level locking.

Try scheduled backup after changing table(s) type to INNOdb.

[Mahesh]

This looks weird, can you attach a .SQL file created using “Backup as SQLdump” option (zip and attach).

Also You can create a support ticket from here for privacy of data:

http://webyog.com/support/

Thanks for the information.

[Mahesh]

Are you able to backup successfully particular table using “Backup table as SQL dump..” ?

Select a table from Object browser — > Right Click –> Export –> “Backup table as SQL dump”

[Mahesh]

We tried with latest version v8.53 and import of data works fine except warnings.

Please try with latest version and let us know the status? as v.5.21 is very old (almost 3+ years)

[Mahesh]

Please tell,

1) Program version you are using ?

2) Which import option you used “Import from External data” OR “Import CSV data using LOAD LOCAL..” ?

3) Can you please attach a table structure and CSV file used while importing ?

[Mahesh]

Thanks for your suggestion.

We will discuss this within team and get back to you.

[Author]

Posts