uadmin ? ? Post: 302307123

Sponsored Content

Operating Systems Solaris uadmin ? ? Post 302307123 by StarSol on Tuesday 14th of April 2009 04:12:18 PM

04-14-2009

Registered User

uadmin ? ?

I have an oracle cluster management and noticed that when Oracle evict a node (Sun Solaris 10 server); it does cause a reboot that looks like a power outage (reference to 3320 Disk Array Configuration for Oracle 10) that is not logged in the messages log. After further investigation, it was found out that Oracle is issuing "/sbin/uadmin 1 1". The man page for uadmin is not very useful so I checked the internet and found out that "uadmin 1 1" means do not sync filesystems and reboots to multi-user mode. I have tested "uadmin 1 1" and "uadmin 2 1" (which means sync the filesystems and reboots to multi-user mode) and noticed that when in both cases the messages log does not show who issued the command (like what you see when you issue "reboot")! In the case of "uadmin 2 1" the last thing the messages log shows is "syncing file systems..." and then nothing until the server comes back up.

I have contacted Sun and the support claimed that when uadmin is issued it should be logged in the messages log but after some time of discussion he agreed that the messages log do not log it but does not know why.

Anybody know more details on this command, what is the different between it and "reboot" and why it is behaving like this if this is the proper behavior?

I have already considerable amount of time searching so any response is might be helpful and appreciated.

StarSol

View Public Profile for StarSol

Find all posts by StarSol

LEARN ABOUT LINUX

ndb_print_schema_file

NDB_PRINT_SCHEMA_(1)					       MySQL Database System					      NDB_PRINT_SCHEMA_(1)

NAME

       ndb_print_schema_file - print NDB schema file contents

SYNOPSIS

       ndb_print_schema_file file_name

DESCRIPTION

       ndb_print_schema_file obtains diagnostic information from a cluster schema file.
	       Usage

	   ndb_print_schema_file file_name

       file_name is the name of a cluster schema file. For more information about cluster schema files, see MySQL Cluster Data Node FileSystemDir
       Files[1].

       Like ndb_print_backup_file and ndb_print_sys_file (and unlike most of the other NDB utilities that are intended to be run on a management
       server host or to connect to a management server) ndb_schema_backup_file must be run on a cluster data node, since it accesses the data
       node file system directly. Because it does not make use of the management server, this utility can be used when the management server is
       not running, and even when the cluster has been completely shut down.
	       Additional Options

       None.

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/.

NOTES

	1. MySQL Cluster Data Node FileSystemDir Files
	   http://dev.mysql.com/doc/ndbapi/en/ndb-internals-ndbd-filesystemdir-files.html

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_PRINT_SCHEMA_(1)