L'outil "sosreport" sur Oracle Linux

L'outil "sosreport" permet de collecter les informations sur le hardware et les configurations de Linux.

Pour l'utiliser:

[root@host ~]# sosreport

sosreport (version 1.7)

This utility will collect some detailed  information about the
hardware and  setup of your  Enterprise Linux  system.
The information is collected and an archive is  packaged under
/tmp, which you can send to a support representative.
This information will be used for diagnostic purposes ONLY
and it will be considered confidential information.

This process may take a while to complete.
No changes will be made to your system.

Press ENTER to continue, or CTRL-C to quit.

One or more plugins have detected a problem in your configuration.
Please review the following messages:

process:
    * one or more processes are in state D (sosreport might hang)

Are you sure you would like to continue (y/n) ? y

Please enter your first initial and last name [texans]: hetche
Please enter the case number that you are generating this report for: 1

 plugin system finished ...
 Completed.

Creating compressed archive...

Your sosreport has been generated and saved in:
  /tmp/sosreport-hetche.1-797857-a51333.tar.bz2

The md5sum is: b9c7ff320009c7b19ad48b93eca51333

Please send this file to your support representative.

Par défaut le résultat est généré dans le répertoire /tmp.
Pour le générer à un autre emplacement, lancer l'utilitaire comme suit:

TMP=/home/hetche sosreport

Hope it helps...

Lecture des fichiers binaires avec la command "strings"

La commande strings peut être utilisé pour visualiser le contenu d'un fichier binaire.

Par exemple, pour voir le contenu d'un fichier olr dans un environnement grid infrastructure 11g (en cluster ou en standalone):

sudo su -
cd $GRID_HOME/cdata
strings host1.olr

Exemple de contenu obtenu:

[root@host1 cdata]# strings host1.olr |grep SPFile
tp://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.grid-pnp.org/2005/11/gpnp-profile gpnp-profile.xsd" ProfileSequence="36" ClusterUId="63077d79ae5dcf99fff118cfb1a5c515" ClusterName="crstest11g" PALocation=""><gpnp:Network-Profile><gpnp:HostNetwork id="gen" HostName="*"><gpnp:Network id="net1" IP="142.41.242.0" Adapter="bond0" Use="public"/><gpnp:Network id="net2" IP="192.168.30.0" Adapter="bond1" Use="cluster_interconnect"/></gpnp:HostNetwork></gpnp:Network-Profile><orcl:CSS-Profile id="css" DiscoveryString="+asm" LeaseDuration="400"/><orcl:ASM-Profile id="asm" DiscoveryString="/dev/oracleasm/disks/*" SPFile="+OCR_VOTE/crstest11g/asmparameterfile/registry.253.801067269"/><ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"><ds:SignedInfo><ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/><ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/><ds:Reference URI=""><ds:Transforms><ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/><ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"> <InclusiveNamespaces xmlns="http://www.w3.org/2001/10/xml-exc-c14n#" PrefixList="gpnp orcl xsi"/></ds:Transform></ds:Transforms><ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><ds:DigestValue>3mfJqBrkkNz2lvK1CJXvq2/UtJw=</ds:DigestValue></ds:Reference></ds:SignedInfo><ds:SignatureValue>scGjbnPKShIDg/NAVJXkn399lt7ifLjbdH6DAHVZnJGSOmZwlcrfSL/mqOHyzHNgtRyhW6yGs+rXukexq0dPI+PtiLTkN6yX1JrC6rdsxemwtoPJAyA9X5lJhdcy4nfNQ/Mv0+nfGlnMXcvBIhGjPiLeFtKmuGUHOvbz+U47hfk=</ds:SignatureValue></ds:Signature></gpnp:GPnP-Profile>
[root@host1 cdata]#

Hope it helps....

ORA-27300: OS system dependent operation:semget failed with status: 28

Dans un environnement Oracle LInux 5.5, en voulant démarrer une instance ou une base de données, je reçois le message suivant:

[oracle@svrhost1 ~]$ srvctl start instance -d exem -i exem1
PRCR-1013 : Failed to start resource ora.exem.db
PRCR-1064 : Failed to start resource ora.exem.db on node svrhost1
CRS-5017: The resource action "ora.exem.db start" encountered the following error:
ORA-27154: post/wait create failed
ORA-27300: OS system dependent operation:semget failed with status: 28
ORA-27301: OS failure message: No space left on device
ORA-27302: failure occurred at: sskgpcreates
. For details refer to "(:CLSN00107:)" in "/ora01/logi/crs/crs_11g/log/svrhost1/agent/crsd/oraagent_oracle/oraagent_oracle.log".

CRS-2674: Start of 'ora.exem.db' on 'svrhost1' failed
[oracle@svrhost1 ~]$

Le document suivant explique quoi faire:

Database Startup Fails with ORA-27300: OS system dependent operation:semget failed with status: 28 [ID 949468.1]

En fait il s'agit de la configuration des sémaphores.

[root@svrhost1 etc]# ipcs -s | grep ^0 | cat -n

     1  0x224685fe 0          root      0          2

     2  0x00000000 360449     hpsmh     600        1

     3  0x00000000 65538      hpsmh     600        1

     4  0x00000000 98307      hpsmh     600        1

…......

   136  0x8c711c30 1497596039 oracle    640        156

   137  0x8c711c31 1497628808 oracle    640        156

   138  0x8c711c32 1497661577 oracle    640        156

   139  0x8c711c33 1497694346 oracle    640        156

   140  0x8c711c34 1497727115 oracle    640        156

[root@svrhost1 etc]# sysctl -a  |grep sem

kernel.sem = 250        32000   100     142

#kernel.sem = SEMMSL SEMMNS SEMOPM  SEMMNI

La commande suivante montre que ces paramètres ont été modifiés par le package Oracle-Validated

[root@svrhost1 etc]# grep sem sysctl.conf

# Oracle-Validated setting for kernel.sem is '250 32000 100 142'

kernel.sem = 250 32000 100 142

[root@svrhost1 etc]# rpm -qa | grep oracle-va

oracle-validated-1.0.0-22.el5

La valeur du paramètre peut être modifiée avec la commande:

[root@svrhost1 etc]# echo "250 64000 100 250" > /proc/sys/kernel/sem

[root@svrhost1 etc]# sysctl -a | grep sem

kernel.sem = 250        64000   100     250 

Hope it helps