ODA administration
you can do with oakcli
Deploy Oracle Database Appliance
Configure network for Oracle Database Appliance deployment
Patching Oracle Database Appliance
Unpacking packages into oakcli repository
Troubleshoot Oracle Database Appliance
Monitor Oracle Database Appliance
Validate Oracle Database Appliance
Applying the Core Configuration key
Copying the deployment configuration file
Locate a disk on ODA
Manage ODA Repository
Manage ODA diagnostics collection
oakcli -h command to list the different options available with oakcli:
oakcli show -h
check if whether ODA deployment is Bare Metal or Virtualized
[root@raj ~]# oakcli show env_hw
o get the ODA software version
[root@raj ~]# oakcli show version
oakcli show -h
o get the ODA software and component version
[root@raj ~]# /opt/oracle/oak/bin/oakcli show version -detail
oakcli show disk
To list ASM disk groups on ODA
[root@raj ~]# oakcli show diskgroup
To list the Local file system and ACFS file system on ODA
[root@raj ~]# oakcli show fs
To list Database homes on ODA
[root@raj ~]# oakcli show dbhomes
To list database storage on ODA
[root@raj ~]# oakcli show dbstorage
[root@raj ~]# oakcli show db_config_params
To check OAK location
[root@raj ~]# env |grep ORA
o create Database on ODA
[root@raj ~]# oakcli create database -db odatest -oh OraDb12102_home1
>> From Node0
# oakcli show disk
# oakcli show diskgroup DATA
# oakcli show diskgroup REDO
# oakcli show diskgroup RECO
# oakcli show env_hw
# oakcli show validation storage failures
# oakcli show storage -errors
>> From both the Nodes
oakcli validate -d
>> ASM Metadata from ASM instance -
SPOOL ASM.HTML
SET MARKUP HTML ON
set echo on
set pagesize 200
alter session set nls_date_format='DD-MON-YYYY HH24:MI:SS';
select 'THIS ASM REPORT WAS GENERATED AT: ==> ' , sysdate " " from dual;
select 'HOSTNAME ASSOCIATED WITH THIS ASM INSTANCE: ==> ' , MACHINE " " from v$session where program like '%SMON%';
select * from v$asm_diskgroup;
select group_number,disk_number,path,name,header_status,mode_status,failgroup from v$asm_disk
order by group_number,failgroup;
SELECT * FROM V$ASM_DISK ORDER BY GROUP_NUMBER,DISK_NUMBER;
SELECT * FROM V$ASM_CLIENT;
select * from V$ASM_ATTRIBUTE;
select * from v$asm_operation;
select * from gv$asm_operation;
select * from v$asm_alias;
select * from v$version;
show parameter asm
show parameter cluster
show parameter instance_type
show parameter instance_name
show parameter spfile
show sga
spool off
exit
select name, state from v$asm_diskgroup;
View the information for all ACFS volumes created by ODA Grid defaultly
asmcmd volinfo -G DATA -a
asmcmd volinfo -G FLASH -a
asmcmd volinfo -G REDO -a
asmcmd volinfo -G RECO -a
Get detailed file system information
/sbin/acfsutil info fs
select volume_name, volume_device, mountpath from v$asm_volume;
Verify that both the ASM-Proxy instances obtain the metadata related to ACFS from ASM instance running locally:
Ref:http://allthingsoracle.com/asm-proxy-new-instance-type-in-oracle-12c/
SELECT DISTINCT
i.instance_name asm_instance_name,
i.host_name asm_host_name,
c.instance_name client_instance_name,
c.status
FROM gv$instance i, gv$asm_client c
WHERE i.inst_id = c.inst_id;
verify that All the ASM and ACFS-related resources are running on both nodes
crsctl stat res ora.asm ora.DATA.dg ora.DATA.VOL1.advm ora.data.vol1.acfs -t
Comments
Post a Comment