[Manoj]

Hi,

Are you running MONyog in a Windows OS? if yes, make sure the service is running with admin privileges, by default it is “Local system”.

[Manoj]

Hi DonQuichote,

Thanks for your help. We will look into these issues on Monday and will let you know if we want more help!

Thanks again.

Regards,

Manoj

[Manoj]

Hi John,

Bug confirmed, thanks for reporting.

This is a bug in counter definition and we will fix this in next release(2.5 Beta 3) with high priority. Similar bug is there with “The number of temporary tables created in memory” counter also.

As a quick fix you can change the counter definitions by navigating to Tools->Customize,

select “temporary tables – 04” (For changing the issue with “The number of temporary tables created on disk”) change the javascript to the following

obj = {

Group : “Temporary Tables”,

Name : “Created on disk”,

Formula : “Created_tmp_disk_tables”,

Uptime : MONyog.MySQL.GlobalStatus.Uptime,

Format : “NumCounterWithSeconds”,

Value : function()

{

if(MONyog.MySQL.Custom.Available != 1)

return “(n/a)”;

return MONyog.MySQL.GlobalStatus.Created_tmp_disk_tables;

},

DocText : “The number of temporary tables created on disk.”+

” If this value is high, you should consider increasing the value of tmp_table_size and max_heap_table_size.”+

” MySQL uses the lowest of these variables to determine whether a temporary table can be created in memory.”+

” Excessive temporary tables on disk are bad for performance”

}

_ALL_COUNTERS.push(obj);

select “temporary tables – 03” (For changing the issue with “The number of temporary tables created in memory”) change the javascript to the following

obj = {

Group : “Temporary Tables”,

Name : “Total tables created”,

Formula : “Created_tmp_tables”,

Uptime : MONyog.MySQL.GlobalStatus.Uptime,

Format : “NumCounterWithSeconds”,

Value : function()

{

if(MONyog.MySQL.Custom.Available != 1)

return “(n/a)”;

return MONyog.MySQL.GlobalStatus.Created_tmp_tables;

},

DocText : “The number of temporary tables created in memory”

}

_ALL_COUNTERS.push(obj);

that's all, now the graph will show the values correctly.

Once again thanks for reporting,

[Manoj]

Hi,

In the MONyog interface goto Tools->Customize, from the left pane you can select the appropriate group to edit, if the counter is your own I suggest you add it in “mycounters – custom” group.

[Manoj]

Ok, Thanks for the details, we fixed this in 6.55 trunk itself.

[Manoj]

SQLyog v6.54, but i am sure it is not related!, issue with ObjectBrowser is also not reproducable.. It is instantaneous!

[Manoj]

Now i tried it in “MySQL Version : 5.0.37-community-nt”, still not able to reproduce the issue

[Manoj]

still sync completed in <30sec.

Can you try this in another system?

[Manoj]

The dump is working fine with FireFox, just download and rename as .sql.

Here the structure sync is taking 26 sec only to complete.

MySQL Version : 5.0.45-community-nt-log

Processor : Intel® Core(tm)2 Duo CPU E4500 @ 2.20GHz, 2194 Mhz, 2 Core(s), 2 Logical Processor(s)

System Type : X86-based PC

Total Physical Memory : 2,029.00 MB

Available Physical Memory : 666.14 MB

Total Virtual Memory : 4.21 GB

[Manoj]

Bug confirmed with CPU graph in Dashboard.

CPU Dashboard graph is reporting old values wrongly. We will fix this with high priority.

As a quick solution you can use Monitors/Advisors->History/trend to see the old values.

[Manoj]

Hi Shlomo,

Currently there is no way to reorder the servers registered in MONyog. MONyog will show the servers in the order of registration untill it is restarted, once it is restarted it will show in the order of the foldername used to store the information(shown as 000X in the right side). Normally it will be same if you restarted with out deleting any servers registered.

Suppose you registered server A (Folder name 0001) and server B (Folder name 0002) .Then delete server A, adn add server C(This will use Folder 0001 again). Now MONyog will show Server B then Server C. If we resterted MONyog in this condition it will show Server C first.

Thanks for you suggestion, we added this to our feature list, this is too late for MONyog 2.0, we will consider this in next release.

[Manoj]

Hi,

thanks for you suggestions. We have almost finished 6.2 and it is too late for putting into this one. But we will study in detail after that we will comeup with a good solution.

[Manoj]

Hi,

No, Currently no way to show the database as well as table size.

We added this to our TODO list, but we cannot currently tell in which version it will be released as the priorities are different.

[Manoj]

First about the error:-

You have a very large BULK INSRT. 99.9 % certain that a single insert statement exceeds the max_allowed_packet setting in server configuration!

You can solve this by following any of these two options,

1)While exporting you can choose not to use BULK inserts as well as in SQLyog “tools .. preferences ('general' tab)” you can define the BULK size. BULK INSERTS means that more than one row of data are included with every INSERT statement.

A FAQ here:http://webyog.com/faq/content/24/101/en/ab…-and-bulks.html

2)In the MySQL configuration file (my.cnf/my,ini) you enter a line in the [mysqld] section reading like

max_allowed_packet=100M

(or whatever size you want. Default is as low as 1M with recent MySQL versions. A BLOB can be up to 64M in size).

Now about views as table:-

Every view is first created as a table while importing and will be removed when the actual view is created(No DATA is imported, only the structure!), you can see this in the SQL dump. This is required because a view can refer to another view which is not yet created!.

[Manoj]

Hi,

There is an option in preferences that may be helpful. “Always select objects tab…” keep this option unchecked and make sure you are in some other tab while clicking the '+' in the object browser. Then it won't update the Objects tab.

[Author]

Posts