quinta-feira, 2 de junho de 2016

Conhecendo o mundo do tal do ODA - Criando um database

Olá jovens.

Vamos direto ao ponto hoje, vamos criar uma nova base de dados no ODA X5. Assim, simples e rápido...

Vamos lá.

Então começamos preparando nosso script de criação da base: 
CREATE DATABASE TESTE...

Opa!!! Para!!! Para!!! Para!!! Para!!! 

Tipo João Kleber manja ahahahhaha... O que é isso pequeno gafanhoto, não precisamos de nada disso não.  

Mais uma vez nosso amigo OAKCLI vai nos ajudar. Vamos lá, agora é sério...

Primeiro vamos gerar um arquivo com algumas configurações. Esse não é um passo obrigatório, mas pode ser que o template do ODA não sirva para o que você quer então acho legal fazer isso.

1) Conecta como root
su - 
2) Manda o comando abaixo:
[root@odax51 ~]# oakcli create db_config_params -conf rsfile

Agora é só responder as perguntas. Eu vou colocar todo o log aqui para vocês verem. Vai ficar um pouco grande mas acho que vale a pena.
Please select one of the following for Database Block Size  [1 .. 4]:
1    => 4096
2    => 8192
3    => 16384
4    => 32768
2
Selected value is : 8192

Specify the  Database Language (1. AMERICAN 2. Others) [1]:2
Please select one of the following for Database Language    [0 .. 10] :
0    => Others
1    => ALBANIAN
2    => AMERICAN
3    => VIETNAMESE
4    => ARABIC
5    => ASSAMESE
6    => AZERBAIJANI
7    => BANGLA
8    => BELARUSIAN
9    => BRAZILIAN PORTUGUESE
10    => BULGARIAN
2
Selected value is: AMERICAN

Specify the  Database Characterset (1. AL32UTF8 2. Others) [1]:
2
Please select one of the following for Database Characterset    [0 .. 10] :
0    => Others
1    => AL32UTF8
2    => AR8ADOS710
3    => AR8ADOS720
4    => AR8APTEC715
5    => AR8APTEC715T
6    => AR8ARABICMACS
7    => AR8ASMO8X
8    => AR8HPARABIC8T
9    => AR8ISO8859P6
10    => AR8MSWIN1256
0

Please select one of the following for Database Characterset    [0 .. 21] :
11    => AR8MUSSAD768
12    => AR8MUSSAD768T
13    => AR8NAFITHA711
14    => AR8NAFITHA711T
15    => AR8NAFITHA721
16    => AR8NAFITHA721T
17    => AR8SAKHR706
18    => AR8SAKHR707
19    => AR8SAKHR707T
20    => AZ8ISO8859P9E
21    => BG8MSWIN
0

Please select one of the following for Database Characterset    [0 .. 32] :
22    => BG8PC437S
23    => BLT8CP921
24    => BLT8ISO8859P13
25    => BLT8MSWIN1257
26    => BLT8PC775
27    => BN8BSCII
28    => CDN8PC863
29    => CEL8ISO8859P14
30    => CL8ISO8859P5
31    => CL8ISOIR111
32    => CL8KOI8R
0

Please select one of the following for Database Characterset    [0 .. 43] :
33    => CL8KOI8U
34    => CL8MACCYRILLICS
35    => CL8MSWIN1251
36    => EE8ISO8859P2
37    => EE8MACCES
38    => EE8MACCROATIANS
39    => EE8MSWIN1250
40    => EE8PC852
41    => EL8DEC
42    => EL8ISO8859P7
43    => EL8MACGREEKS
0

Please select one of the following for Database Characterset    [0 .. 54] :
44    => EL8MSWIN1253
45    => EL8PC437S
46    => EL8PC851
47    => EL8PC869
48    => ET8MSWIN923
49    => HU8ABMOD
50    => HU8CWI2
51    => IN8ISCII
52    => IS8PC861
53    => IW8ISO8859P8
54    => IW8MACHEBREWS
0

Please select one of the following for Database Characterset    [0 .. 65] :
55    => IW8MSWIN1255
56    => IW8PC1507
57    => JA16EUC
58    => JA16EUCTILDE
59    => JA16SJIS
60    => JA16SJISTILDE
61    => JA16VMS
62    => KO16KSC5601
63    => KO16KSCCS
64    => KO16MSWIN949
65    => LA8ISO6937
0

Please select one of the following for Database Characterset    [0 .. 76] :
66    => LA8PASSPORT
67    => LT8MSWIN921
68    => LT8PC772
69    => LT8PC774
70    => LV8PC1117
71    => LV8PC8LR
72    => LV8RST104090
73    => N8PC865
74    => NE8ISO8859P10
75    => NEE8ISO8859P4
76    => RU8BESTA
0

Please select one of the following for Database Characterset    [0 .. 87] :
77    => RU8PC855
78    => RU8PC866
79    => SE8ISO8859P3
80    => TH8MACTHAIS
81    => TH8TISASCII
82    => TR8DEC
83    => TR8MACTURKISHS
84    => TR8MSWIN1254
85    => TR8PC857
86    => US8PC437
87    => UTF8
0

Please select one of the following for Database Characterset    [0 .. 98] :
88    => VN8MSWIN1258
89    => VN8VN3
90    => WE8DEC
91    => WE8DG
92    => WE8ISO8859P1
93    => WE8ISO8859P15
94    => WE8ISO8859P9
95    => WE8MACROMAN8S
96    => WE8MSWIN1252
97    => WE8NCR4970
98    => WE8NEXTSTEP
92
Selected value is: WE8ISO8859P1

Specify the  Database Territory (1. AMERICA 2. Others) [1]:
2
Please select one of the following for Database Territory    [0 .. 10] :
0    => Others
1    => ALBANIA
2    => ALGERIA
3    => AMERICA
4    => ARGENTINA
5    => AUSTRALIA
6    => AUSTRIA
7    => AZERBAIJAN
8    => BAHRAIN
9    => BANGLADESH
10    => BELARUS
3
Selected value is: AMERICA

Specify the  Component Language (1. en 2. Others) [1]:
2
Please select one of the following for Component Language    [0 .. 10] :
0    => Others
1    => en : Engilish
2    => fr : French
3    => ar : Arabic
4    => bn : Bengali
5    => pt_BR : Brazilian Portuguese
6    => bg : Bulgarian
7    => fr_CA : Canadian French
8    => ca : Catalan
9    => hr : Croatian
10    => cs : Czech
1
Selected value is: en
Please select one of the following for NLS Characterset  [1 .. 2]:
1    => AL16UTF16
2    => UTF8
1
Selected value is : AL16UTF16

Successfully generated the Database parameter file 'rsfile'

3) Vamos verificar o que acabamos de gerar
oakcli show db_config_params
Available DB configuration files are:
default ==> Olha aqui o default do ODA
rsfile ==> O que acabamos de criar

oakcli show db_config_params -conf rsfile -detail
DATABASE_BLOCK_SIZE       =>    8192
DATABASE_LANGUAGE         =>    AMERICAN
DATABASE_CHARACTERSET     =>    WE8ISO8859P1
DATABASE_TERRITORY        =>    AMERICA
COMPONENT_LANGUAGES       =>    en
NLS_NCHAR_CHARACTERSET    =>    AL16UTF16

4) Veja os ORACLE_HOMES disponíveis. Você vai precisar. 
[root@odax51 ~]# oakcli show dbhomes








5) Então pequeno amigo, agora é só ter o trabalho de olhar o ODA trabalhar

oakcli create database -db teste -oh OraDb11204_home1 -params rsfile 
Please enter the 'SYSASM'  password : (During deployment we set the SYSASM password to 'welcome1'):
Please re-enter the 'SYSASM' password:
Please select one of the following for Database type  [1 .. 2]:
1    => OLTP
2    => DSS
1
Selected value is : OLTP
Please select one of the following for Database Deployment  [1 .. 3]:
1    => EE : Enterprise Edition
2    => RACONE
3    => RAC
3
Selected value is : RAC
Please select one of the following for Database Class  [1 .. 5]:
1    => odb-01s  (   1 cores ,     4 GB memory)
2    =>  odb-01  (   1 cores ,     8 GB memory)
3    =>  odb-02  (   2 cores ,    16 GB memory)
4    =>  odb-04  (   4 cores ,    32 GB memory)
5    =>  odb-06  (   6 cores ,    48 GB memory)
2
Selected value is : odb-01  (   1 cores ,     8 GB memory)

Do you want to setup the EM DB Console for this database [ Y | N ] ? : N

Agora basta seguirmos o log
INFO   : Logging all actions in the file /opt/oracle/oak/log/hscodax41/patch/12.1.2.6.0/hscodax41-20160517105858.log and traces in  the file /opt/oracle/oak/log/hscodax41/patch/12.1.2.6.0/hscodax41-20160517105858.trc
INFO   : Loading the configuration file /opt/oracle/oak/onecmd/create_database.params...
INFO   : Creating the node list files...
INFO   : Setting up ssh for root...
INFO   : Setting up SSH across the Private Network...
...
INFO   : Running as root: /usr/bin/ssh -l root 192.168.16.24 /root/DoAllcmds.sh
INFO   : Running as root: /usr/bin/ssh -l root 192.168.16.25 /root/DoAllcmds.sh
INFO   : Background process 76404 (node: 192.168.16.24) gets done with the exit code 0
INFO   : Background process 76430 (node: 192.168.16.25) gets done with the exit code 0
INFO   : Setting up SSH completed successfully
INFO   : Running the command /usr/bin/rsync -tarqvz /opt/oracle/oak/onecmd/ root@192.168.16.25:/opt/oracle/oak/onecmd --exclude=*zip --exclude=*gz --exclude=*log --exclude=*trc --exclude=*rpm to sync directory
on node <192 .168.16.25="">
SUCCESS: Ran /usr/bin/rsync -tarqvz /opt/oracle/oak/onecmd/ root@192.168.16.25:/opt/oracle/oak/onecmd --exclude=*zip --exclude=*gz --exclude=*log --exclude=*trc --exclude=*rpm and it returned: RC=0
...INFO   : Did not do scp for node : hscodax41
INFO   : Running as root: /usr/bin/ssh -l root hscodax41 /root/DoAllcmds.sh
INFO   : Background process 77099 (node: hscodax41) gets done with the exit code 0
INFO   : Running as root: /usr/bin/ssh -l root hscodax42 /root/DoAllcmds.sh
INFO   : Background process 77126 (node: hscodax42) gets done with the exit code 0
INFO   : Did not do scp for node : hscodax41
INFO   : Running as root: /usr/bin/ssh -l root hscodax41 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20160517105939.sh
INFO   : Running as root: /usr/bin/ssh -l root hscodax42 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20160517105939.sh
INFO   : Background process 77181 (node: hscodax41) gets done with the exit code 0
INFO   : Background process 77207 (node: hscodax42) gets done with the exit code 0
INFO   : Setting up SSH for user oracle...
...
INFO   : checking nodes in /opt/oracle/oak/onecmd/tmp/db_nodes...
...
SUCCESS: All nodes in /opt/oracle/oak/onecmd/tmp/db_nodes are pingable and alive.
INFO   : Checking SSH setup for user (oracle) on nodes in /opt/oracle/oak/onecmd/tmp/db_nodes...
INFO   : Did not do scp for node : hscodax41
INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle hscodax41 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20160517105958.sh
INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/DoAllcmds-20160517105958.sh
INFO   : Background process 77766 (node: hscodax41) gets done with the exit code 0
INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle hscodax42 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20160517105958.sh
INFO   : Background process 77792 (node: hscodax42) gets done with the exit code 0
INFO   : Setting up ACFS storage
INFO   : Did not do scp for node : hscodax41
INFO   : Running as root: /usr/bin/ssh -l root hscodax41 /opt/oracle/oak/onecmd/tmp/acfsm_72134.sh
INFO   : Running as root: /usr/bin/ssh -l root hscodax42 /opt/oracle/oak/onecmd/tmp/acfsm_72134.sh
INFO   : Background process 77986 (node: hscodax41) gets done with the exit code 0
INFO   : Background process 78012 (node: hscodax42) gets done with the exit code 0
INFO: 2016-05-17 11:00:14: Creating the volume datastore on the diskgroup REDO of size 52 G
INFO: 2016-05-17 11:00:24: Creating acfs on volume datastore
INFO: 2016-05-17 11:00:25: Registering datastore with clusterware
INFO: 2016-05-17 11:00:38: Creating the volume datastore on the diskgroup DATA of size 1625 G
INFO: 2016-05-17 11:00:53: Creating accelerator volume acldatstore
INFO: 2016-05-17 11:00:59: Creating acfs on volume datastore
INFO: 2016-05-17 11:01:44: Registering datastore with clusterware
INFO: 2016-05-17 11:02:09: Creating the volume datastore on the diskgroup RECO of size 374 G
INFO: 2016-05-17 11:02:21: Creating acfs on volume datastore
INFO: 2016-05-17 11:02:37: Registering datastore with clusterware
INFO: 2016-05-17 11:02:50: Successfully setup the storage structure for the database 'teste'
SUCCESS: Successfully setup ACFS storage for the database teste
INFO   : Creating Database using DBCA...
INFO   : Did not do scp for node : hscodax41
INFO   : Running as root: /usr/bin/ssh -l root hscodax41 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20160517110250.sh
INFO   : Running as root: /usr/bin/ssh -l root hscodax42 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20160517110250.sh
INFO   : Background process 91175 (node: hscodax41) gets done with the exit code 0
INFO   : Background process 91201 (node: hscodax42) gets done with the exit code 0
INFO   : Running DBCA using /opt/oracle/oak/onecmd/tmp/dbca-teste.sh on hscodax41 as oracle...
INFO   : Check output in /opt/oracle/oak/onecmd/tmp/dbca-teste-20160517105858.log on hscodax41
INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle hscodax41 /opt/oracle/oak/onecmd/tmp/dbca-teste.sh
INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/dbca-teste.sh
Instance teste1 is running on node hscodax41
Instance teste2 is running on node hscodax42
INFO   : One or more Instances running on the cluster nodes.
INFO   : Running export ORACLE_HOME=/u01/app/oracle/product/11.2.0.4/dbhome_1;/u01/app/oracle/product/11.2.0.4/dbhome_1/bin/srvctl setenv database -d teste -t 'TZ=America/Sao_Paulo' to set DB timezone
INFO   : Running the command /u01/app/12.1.0.2/grid/bin/crsctl stat resource ora.teste.db -p
.INFO   : Did not do scp for node : hscodax41
..
INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle hscodax41 /opt/oracle/oak/onecmd/tmp/dbupdates-teste.sh
INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/dbupdates-teste.sh
INFO   : Running export ORACLE_HOME=/u01/app/oracle/product/11.2.0.4/dbhome_1;/u01/app/oracle/product/11.2.0.4/dbhome_1/bin/srvctl stop database -d teste
INFO   : Running export ORACLE_HOME=/u01/app/oracle/product/11.2.0.4/dbhome_1;/u01/app/oracle/product/11.2.0.4/dbhome_1/bin/srvctl start database -d teste
INFO: 2016-05-17 11:12:25: Successfully set the RMAN SNAPSHOT control file

E se tudo correu bem, acabamos assim:
SUCCESS: 2016-05-17 11:12:26: Successfully created the Database : teste

Olha só que legal, ele já fez tudo, até registrar a nova base no RAC. É ou não é nosso amigo esse tal de OAKCLI ahahahha.

Ai claro, dá uma conferida lá né o preguiça:






Bom pessoal, espero que ajude. Dica simples mas bastante útil.

Abraço
Mario

Conhecendo o mundo do tal do ODA - OAKCLI I

Olá jovens!!

Como estão? Espero que estejam bem.

A algum tempo comecei a administrar um ambiente ODA (X4-2). Ambiente bacana de se trabalhar.

Com o tempo, fui anotando algumas verificações feitas no ODA através do OAKCLI.

Seguindo o que eu acho (e se eu acho, é um achismo meu.. então pode estar errado ahahahahah) o Oracle cada vez mais quer fornecer ferramentas para facilitar o dia a dia de quem gosta de uma linha de comando. 

Assim como o ADRCI, essa é uma ferramenta de linha de comando que auxilia na realização de várias tarefas no ODA.

Hoje vou passar aqui algumas opções de verificação e validações de componentes.

Vocês verão no help que ainda podemos fazer deploy, upgrade, update, etc. Mas esse não é o foco.

Então, chega de embromation e vamos lá ao que interessa.

O OAKCLI deve ser executado como usuário root.

su -
cd /opt/oracle/oak/bin/

Claro, vamos dar uma olhada no Help primeiro:


     [root@zema02 bin]# ./oakcli -h
Usage:  oakcli show       - show disk, diskgroup, expander, controller, 
                                    server, processor,  memory, power, cooling, 
                                    network, enclosure, storage, version,
                                    dbhomes, databases, db_config_params, 
                                    core_config_key, env_hw, asr
oakcli apply      - applies the core_config_key
oakcli locate     - locates a disk
oakcli deploy     - deploys the Database Appliance
oakcli update     - updates the Database Appliance
oakcli validate   - validates the Database Appliance
oakcli manage     - manages the oak repository, diagcollect e.t.c
  oakcli unpack     - unpack the given package to oak repository
oakcli copy       - copies the deployment config file
oakcli upgrade    - upgrades database
oakcli stordiag   - run storage diagnostic tool on both node
oakcli test       - test asr
oakcli orachk     - performs configuration settings check on ODA
oakcli configure  - configures the network or asr
oakcli create     - creates database,dbhome,db_config_params file
oakcli delete     - deletes database,dbhome,db_config_params file

Podemos também verificar o help por hierarquia.


      [root@zema02 bin]# oakcli show -h
Usage:
    oakcli show {disk|diskgroup|expander|controller|server|processor|
                 memory|power|cooling|network|enclosure|storage|
                 core_config_key|version|dbhomes|databases|
                 db_config_params|asr|env_hw} []
where:
disk                    - About the disk
diskgroup               - Asm disk group
expander                - Expander
controller              - Controller
storage                 - All storage components
version                 - Running software version
dbhomes                 - Installed oracle database homes
databases               - Database names
db_config_params        - db_config_params file
asr                     - Asr configuration
env_hw                  - Environment and Hardware 
                                                  information
server                  - Details of server sub-system
processor               - Details of processor sub-system
memory                  - Details of memory sub-system
power                   - Details of power supply 
                                                  sub-system
cooling                 - Details of cooling sub-system
network                 - Details of network sub-system
enclosure               - Details of enclosure sub-system
core_config_key         - Core configuration

Agora é só brincar com as opções. Aqui uma lista dos discos disponíveis
  • Informações dos discos

      [root@zema02 bin]# oakcli show disk

NAME            PATH            TYPE            STATE           STATE_DETAILS
e0_pd_00        /dev/sda        HDD             ONLINE          Good
e0_pd_01        /dev/sdb        HDD             ONLINE          Good
e0_pd_02        /dev/sdaa       HDD             ONLINE          Good
e0_pd_03        /dev/sdab       HDD             ONLINE          Good
e0_pd_04        /dev/sdac       HDD             ONLINE          Good
e0_pd_05        /dev/sdad       HDD             ONLINE          Good
e0_pd_06        /dev/sdae       HDD             ONLINE          Good
e0_pd_07        /dev/sdaf       HDD             ONLINE          Good
e0_pd_08        /dev/sdag       HDD             ONLINE          Good
e0_pd_09        /dev/sdah       HDD             ONLINE          Good
e0_pd_10        /dev/sdai       HDD             ONLINE          Good
e0_pd_11        /dev/sdaj       HDD             ONLINE          Good
e0_pd_12        /dev/sdak       HDD             ONLINE          Good
e0_pd_13        /dev/sdal       HDD             ONLINE          Good
e0_pd_14        /dev/sdam       HDD             ONLINE          Good
e0_pd_15        /dev/sdan       HDD             ONLINE          Good
e0_pd_16        /dev/sdao       HDD             ONLINE          Good
e0_pd_17        /dev/sdap       HDD             ONLINE          Good
e0_pd_18        /dev/sdaq       HDD             ONLINE          Good
e0_pd_19        /dev/sdar       HDD             ONLINE          Good
e0_pd_20        /dev/sdas       SSD             ONLINE          Good
e0_pd_21        /dev/sdat       SSD             ONLINE          Good
e0_pd_22        /dev/sdau       SSD             ONLINE          Good
e0_pd_23        /dev/sdav       SSD             ONLINE          Good

  • Informações dos diskgroups criados

     [root@zema02 bin]# oakcli show diskgroup

DiskGroups
----------
DATA
RECO
REDO

  • Informações dos servidores

      [root@zema02 bin]# ./oakcli show server
Power State              : On
Open Problems            : 0
Model                    : ODA X4-2
Type                     : Rack Mount
Part Number              : 33144597+1+1
Serial Number            : 1446NMP00E
Primary OS               : Not Available
ILOM Address             : XXX.XX.XX.XX
ILOM MAC Address         : 00:00:X0:00:X0:X0
Description              : Oracle Database Appliance X4-2 1446NMP00E
Locator Light            : Off
Actual Power Consumption : 244 watts
Ambient Temperature      : 20.000 degree C
Open Problems Report     : System is healthy


  • Informações da versão

     [root@zema02 bin]# oakcli show version
Version
     -------
     2.10.0.0.0

  • Informações dos processadores e quantidade de core's habilitados

      [root@zema02 bin]# oakcli show processor

NAME  HEALTH HEALTH_DETAILS PART_NO. LOCATION   MODEL                         MAX_CLK_SPEED TOTAL_CORES ENABLED_CORES

CPU_0 OK     -              060E     P0 (CPU 0) Intel(R) Xeon(R) CPU E5-2697  2.700 GHZ       12          12

CPU_1 OK     -              060E     P1 (CPU 1) Intel(R) Xeon(R) CPU E5-2697  2.700 GHZ       12          12

  • Informações de energia, temperatura, etc

      [root@zema02 bin]# oakcli show power

NAME        HEALTH HEALTH_DETAILS PART_NO. SERIAL_NO.         LOCATION INPUT_POWER OUTPUT_POWER INLET_TEMP      EXHAUST_TEMP

Power_Supply_0  OK     -              7079395  000000X+0000XX00X0 PS0      Present     110 watts    30.500 degree C 35.312 degree C

Power_Supply_1  OK     -              7079395  000000X+0000XX00X0 PS1      Present     108 watts    35.750 degree C 39.375 degree C

  • Se está com a core_config_key implantada. 

     [root@zema02 bin]# oakcli show core_config_key
Optional core_config_key is not applied on this machine yet !


Importante: Se houvesse uma chave, seria mais ou menos isso:
 Host's serialnumber = 00000XX00X7 
     Configured Cores = 16


  • Informações das bases que lá estão:

     [root@zema02 bin]#  oakcli show databases

Database Name    Database Type  Database HomeName   
Database HomeLocation                       Database Version        
---------------- -------------  ----------------    
-----------------------------------------   ---------------------  
orcl              RAC            OraDb11204_home1    
/u01/app/oracle/product/11.2.0.4/dbhome_1   11.2.0.4.2(18031668,18031740)

tttt              RAC            OraDb11204_home1   
/u01/app/oracle/product/11.2.0.4/dbhome_1   11.2.0.4.2(18031668,18031740)

xxxx              RAC            OraDb11204_home1   
 /u01/app/oracle/product/11.2.0.4/dbhome_1   11.2.0.4.2(18031668,18031740)

É isso. É tranquilo. Só olhar o help e mandar bala.

O validate segue o mesmo ponto...
Vamos ver o help.

[root@zema02 ~]# oakcli validate -h

Usage:
oakcli  validate [-V | -l | -h]
oakcli  validate [-v] [-f absolute output_file_name] 
                         [-a | -d | -c check1[,check2]]

ARGUMENTS:
-v      verbose output
-f      output_file_name.The output is sent to the file 
                        instead of standard output
-a      run all checks
-d      run only default checks.
-c      check1[,check2] run specific checks
-l      list the checks and description
-V      Print the Version
-h      print help
EXAMPLES:
oakcli validate -l
oakcli validate -a
oakcli validate -c DiskCalibration
oakcli validate -c SystemComponents,NetworkComponents,asr

Uma lista com descrição do que é validado em cada teste também está lá.

[root@zema02 ~]# oakcli validate -l

Checkname -- Description
=========    ===========
*SystemComponents  -- Validate system components based on ilom sensor 
                              data readings
*OSDiskStorage     -- Validate OS disks and filesystem information
*SharedStorage     -- Validate Shared storage and multipathing 
                              information
DiskCalibration    -- Check disk performance with orion
*NetworkComponents -- Validate public and private network components
*StorageTopology   -- Validate external JBOD connectivity
asr                -- Validate asr components based on asr config 
                              file and ilom sensor data readings

* -- These checks are also performed as part of default checks

  • Podemos, por exemplo, validar a topologia do Storage

     [root@zema02 ~]# oakcli validate -c StorageTopology

It may take a while. Please wait...
INFO    : ODA Topology Verification
INFO    : Running on Node1
INFO    : Check hardware type
SUCCESS : Type of hardware found : X4-2
INFO    : Check for Environment(Bare Metal or Virtual Machine)
SUCCESS : Type of environment found : Bare Metal
INFO    : Check number of Controllers
SUCCESS : Number of Internal LSI SAS controller found : 1
SUCCESS : Number of External LSI SAS controller found : 2
INFO    : Check for Controllers correct PCIe slot address
SUCCESS : Internal LSI SAS controller   : 50:00.0
SUCCESS : External LSI SAS controller 0 : 30:00.0
SUCCESS : External LSI SAS controller 1 : 40:00.0
INFO    : Check if JBOD powered on
SUCCESS : 1JBOD : Powered-on
INFO    : Check for correct number of EBODS(2 or 4)
SUCCESS : EBOD found : 2
INFO    : Check for External Controller 0
SUCCESS : Controller connected to correct ebod number
SUCCESS : Controller port connected to correct ebod port
SUCCESS : Overall Cable check for controller 0
INFO    : Check for External Controller 1
SUCCESS : Controller connected to correct ebod number
SUCCESS : Controller port connected to correct ebod port
SUCCESS : Overall Cable check for controller 1
INFO    : Check for overall status of cable validation on Node1
SUCCESS : Overall Cable Validation on Node1
INFO    : Check Node Identification status
SUCCESS : Node Identification
SUCCESS : Node name based on cable configuration found : NODE1
INFO    : Check JBOD Nickname
SUCCESS : JBOD Nickname set correctly : Oracle Database Appliance - E0
INFO    : The details for Storage Topology Validation can also 
                  be found in log 

file=/opt/oracle/oak/log/zema02/storagetopology/StorageTopology-2015-05-14-11:13:59_59781_137.log

  • Ou as informações de network 

     [root@zema02 ~]# oakcli validate -c NetworkComponents

INFO: Doing oak network checks
RESULT:  Detected active link for interface eth0 with link speed 
                 10000Mb/s and cable type as Twinax
RESULT:  Detected active link for interface eth1 with link speed 
                 10000Mb/s and cable type as Twinax
RESULT:  Detected active link for interface eth2 with link speed 
                 1000Mb/s and cable type as Twisted Pair
RESULT:  Detected active link for interface eth3 with link speed 
                 1000Mb/s and cable type as Twisted Pair
WARNING: No Link detected for interface eth4 with cable type 
                 as Twisted Pair
WARNING: No Link detected for interface eth5 with cable type as 
                 Twisted Pair

INFO: Checking bonding interface status

RESULT:  Bond interface bond0 is up configured in mode:load 
                 balancing (round-robin) with current active interface as
 Slave1 interface is eth2 with status:up Link fail count=0 
                 Maccaddr:00:10:e0:62:a5:c2
 
                 Slave2 interface is eth3 with status:up Link fail count=0 
                 Maccaddr:00:10:e0:62:a5:c3

WARNING: Bond interface bond1 has the following current status:down

RESULT:  Bond interface bond1 is down configured in mode:
                 fault-tolerance (active-backup) with current active 
                 interface as None
     Slave1 interface is eth4 with status:down Link fail count=0 
                 Maccaddr:00:10:e0:62:a5:c4

 Slave2 interface is eth5 with status:down Link fail count=0 
                 Maccaddr:00:10:e0:62:a5:c5

SUCCESS: eth0 is running 192.168.16.25
SUCCESS: eth1 is running 192.168.17.25

E assim podemos validar várias informações.

É isso jovens. Espero ter ajudado quem, como eu, está começando com o ODA.

That's it my friends...

Mario

Postagem em destaque

[ORACLE] Embedding ONNX model for Vector Search tests with Oracle Database 23ai

Hello, everyone. How's it going? Today, I'm going to show you how to load an ONNX model into the Oracle 23ai database for your vecto...