Sponsored Content
Operating Systems AIX High Runqueue (R) LOW CPU LOW I/O Low Network Low memory usage Post 302589992 by methyl on Friday 13th of January 2012 10:37:54 AM
Old 01-13-2012
The figures in the User CPU "us" column are high for a database system. Have you checked for looping orphan prococeses ?
 

10 More Discussions You Might Find Interesting

1. Solaris

Low average cpu utilization.

Hi to all, i have an app on solaris 5.8 writed in C++ (3.2.1) that use multi threading. Hardware has 8 cpu. When i run my app i note that the average of cpu go at least at 40%, and the performance are not so higher.. There is a cpu limitation on solaris, that dedicate only a part of cpu... (3 Replies)
Discussion started by: Moodie
3 Replies

2. Solaris

malloc returning NULL if freemem high & swapmem low

Hi All, In my application malloc is returning NULL even though there is sufficient amount of free memory is available but swap memory is low. Is this possible that, if free memory is high & swap memory is low, malloc will not be able to allocate memory & return NULL ?:) Kindly look into... (5 Replies)
Discussion started by: Ritesh Kumar
5 Replies

3. Shell Programming and Scripting

low & high values

on the file Ftp'd from the mainframe ,do we have any UNIX command to replace mainframe low and values to space or null. i tried using tr and it doesn't work ... Thanks (1 Reply)
Discussion started by: rlmadhav
1 Replies

4. Shell Programming and Scripting

Picking high and low variables in a bash script - possible?

Is it possible to have a bash script pick the highest and lowest values of four variables? I've been googling for this but haven't come up with anything. I have a script that assigns variables ($c0, $c1, $c2, and $c3) based on the coretemps from grep/sed statements of sensors. I'd like to also... (5 Replies)
Discussion started by: graysky
5 Replies

5. Shell Programming and Scripting

Split file into chunks of low & high byte

Hi guys, i have a question about spliting a binary file into 2 chunks. First chunk with all high bytes and the second one with all low bytes. What unix tools can i use? And how can this be performed? I looked in manpages of split and dd but this does not help. Thanks (2 Replies)
Discussion started by: basta
2 Replies

6. HP-UX

Bad performance but Low CPU loading?

There might be some problem with my server, because every morning at 7, it's performance become bad with no DB extra deadlock. But I just couldn't figure it out. Please give me some advise, thanks a lot... According to the CPU performace chart, Daily CPU loading Maximum: 42 %, Average:36%. ... (8 Replies)
Discussion started by: GreenShery
8 Replies

7. UNIX for Dummies Questions & Answers

Kernel/ user space and high/ low mem

Need some clarification on this.... 1. how are kernel/ user spaces and high/low memory related? 2. What do they all mean when i have the kernel command line as: "console=ttyS0,115200 root=/dev/sda2 rw mem=exactmap memmap=1M@0 memmap=96M@1M irqpoll" or 2. what do mem and memmap mean in... (3 Replies)
Discussion started by: dragonpoint
3 Replies

8. AIX

Low Virtual memory available

Hi I am running AIX 5.2. My server is running low on memory. It it using about 1307775 file pages on a total of 1511424 (from vmstat -v). I looked at the memory yesterday morning, and we had plenty of free memory. I did a backup from Windows (ftp mget command) of a large file selection. From... (5 Replies)
Discussion started by: fredrivard
5 Replies

9. Red Hat

High RAM usage, extremely low swapping

Hi team I have three physical servers running on Red Hat Enterprise Linux Server release 6.2 with the following memory conditions: # cat /proc/meminfo | grep -i mem MemTotal: 8062888 kB MemFree: 184540 kB Shmem: 516 kB and the following swap conditions: ... (6 Replies)
Discussion started by: hedkandi
6 Replies

10. UNIX for Advanced & Expert Users

Linux live cd for low memory

Could I please get some recommendations of a linux live cd for low memory? (1 Reply)
Discussion started by: cokedude
1 Replies
NDB_BLOB_TOOL(1)					       MySQL Database System						  NDB_BLOB_TOOL(1)

NAME
ndb_blob_tool - check and repair BLOB and TEXT columns of MySQL Cluster tables SYNOPSIS
ndb_blob_tool options table [column, ...] DESCRIPTION
This tool can be used to check for and remove orphaned BLOB column parts from NDB tables, as well as to generate a file listing any orphaned parts. It is sometimes useful in diagnosing and repairing corrupted or damaged NDB tables containing BLOB or TEXT columns. The basic syntax for ndb_blob_tool is shown here: ndb_blob_tool [options] table [column, ...] Unless you use the --help option, you must specify an action to be performed by including one or more of the options --check-orphans, --delete-orphans, or --dump-file. These options cause ndb_blob_tool to check for orphaned BLOB parts, remove any orphaned BLOB parts, and generate a dump file listing orphaned BLOB parts, respectively, and are described in more detail later in this section. You must also specify the name of a table when invoking ndb_blob_tool. In addition, you can optionally follow the table name with the (comma-separated) names of one or more BLOB or TEXT columns from that table. If no columns are listed, the tool works on all of the table's BLOB and TEXT columns. If you need to specify a database, use the --database (-d) option. The --verbose option provides additional information in the output about the tool's progress. The following table includes options that are specific to ndb_blob_tool. Additional descriptions follow the table. For options common to most MySQL Cluster programs (including ndb_blob_tool), see Options Common to MySQL Cluster Programs(1). Table 17.14. ndb_blob_tool Options and Variables: MySQL Cluster NDB 7.2 +---------------------------+-------------------------------------+-------------------------------------+ |Format | Description | Added / Removed | +---------------------------+-------------------------------------+-------------------------------------+ | | Check for orphan blob parts | | | --check-orphans | | All MySQL 5.5 based releases | +---------------------------+-------------------------------------+-------------------------------------+ | | Database to find the table in. | | | --database=db_name, | | All MySQL 5.5 based releases | | | | | | -d | | | +---------------------------+-------------------------------------+-------------------------------------+ | | Delete orphan blob parts | | | --delete-orphans | | All MySQL 5.5 based releases | +---------------------------+-------------------------------------+-------------------------------------+ | | Write orphan keys to specified file | | | --dump-file=file | | All MySQL 5.5 based releases | +---------------------------+-------------------------------------+-------------------------------------+ | | Verbose output | | | --verbose, | | All MySQL 5.5 based releases | | | | | | -v | | | +---------------------------+-------------------------------------+-------------------------------------+ o --check-orphans +--------------------+-------------------+ |Command-Line Format | --check-orphans | +--------------------+-------------------+ | | Permitted Values | | +---------+---------+ | | Type | boolean | | +---------+---------+ | | Default | FALSE | +--------------------+---------+---------+ Check for orphaned BLOB parts in MySQL Cluster tables. o --database=db_name, -d +--------------------+--------------------+ |Command-Line Format | --database=db_name | +--------------------+--------------------+ | | -d | +--------------------+--------------------+ | | Permitted Values | | +----------+---------+ | | Type | string | | +----------+---------+ | | Default | [none] | +--------------------+----------+---------+ Specify the database to find the table in. o --delete-orphans +--------------------+-------------------+ |Command-Line Format | --delete-orphans | +--------------------+-------------------+ | | Permitted Values | | +---------+---------+ | | Type | boolean | | +---------+---------+ | | Default | FALSE | +--------------------+---------+---------+ Remove orphaned BLOB parts from MySQL Cluster tables. o --dump-file=file +--------------------+---------------------+ |Command-Line Format | --dump-file=file | +--------------------+---------------------+ | | Permitted Values | | +---------+-----------+ | | Type | file name | | +---------+-----------+ | | Default | [none] | +--------------------+---------+-----------+ Writes a list of orphaned BLOB column parts to file. The information written to the file includes the table key and BLOB part number for each orphaned BLOB part. o --verbose +--------------------+-------------------+ |Command-Line Format | --verbose | +--------------------+-------------------+ | | -v | +--------------------+-------------------+ | | Permitted Values | | +---------+---------+ | | Type | boolean | | +---------+---------+ | | Default | FALSE | +--------------------+---------+---------+ Provide extra information in the tool's output regarding its progress. Example First we create an NDB table in the test database, using the CREATE TABLE statement shown here: USE test; CREATE TABLE btest ( c0 BIGINT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY, c1 TEXT, c2 BLOB ) ENGINE=NDB; Then we insert a few rows into this table, using a series of statements similar to this one: INSERT INTO btest VALUES (NULL, 'x', REPEAT('x', 1000)); When run with --check-orphans against this table, ndb_blob_tool generates the following output: shell> ndb_blob_tool --check-orphans --verbose -d test btest connected processing 2 blobs processing blob #0 c1 NDB$BLOB_19_1 NDB$BLOB_19_1: nextResult: res=1 total parts: 0 orphan parts: 0 processing blob #1 c2 NDB$BLOB_19_2 NDB$BLOB_19_2: nextResult: res=0 NDB$BLOB_19_2: nextResult: res=0 NDB$BLOB_19_2: nextResult: res=0 NDB$BLOB_19_2: nextResult: res=0 NDB$BLOB_19_2: nextResult: res=0 NDB$BLOB_19_2: nextResult: res=0 NDB$BLOB_19_2: nextResult: res=0 NDB$BLOB_19_2: nextResult: res=0 NDB$BLOB_19_2: nextResult: res=0 NDB$BLOB_19_2: nextResult: res=0 NDB$BLOB_19_2: nextResult: res=1 total parts: 10 orphan parts: 0 disconnected NDBT_ProgramExit: 0 - OK The tool reports that there are no NDB BLOB column parts associated with column c1, even though c1 is a TEXT column. This is due to the fact that, in an NDB table, only the first 256 bytes of a BLOB or TEXT column value are stored inline, and only the excess, if any, is stored separately; thus, if there are no values using more than 256 bytes in a given column of one of these types, no BLOB column parts are created by NDB for this column. See Section 11.6, "Data Type Storage Requirements", for more information. COPYRIGHT
Copyright (C) 1997, 2014, Oracle and/or its affiliates. All rights reserved. This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/. SEE ALSO
For more information, please refer to the MySQL Reference Manual, which may already be installed locally and which is also available online at http://dev.mysql.com/doc/. AUTHOR
Oracle Corporation (http://dev.mysql.com/). MySQL 5.5 01/30/2014 NDB_BLOB_TOOL(1)
All times are GMT -4. The time now is 05:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy