Skip to main content

Trace Down Your Data from Database to Disk


<<Back to Oracle ASM Main Page

Where is my Data on the Disk

In this post I will show you, how you can trace your data from Database to disk where it is stored and how you can read it directly from disk
So let us quickly setup the environment
Step1> Login to DB Instance and Create a Tablespace
SQL>create tablespace TRACE_DATA datafile '+TEST_DATA';

Step2> Find File# and Name of The Datafile
SQL> col "File" for a80
select f.FILE#, f.NAME "File", t.NAME "Tablespace"
from V$DATAFILE f, V$TABLESPACE t
where t.NAME='TRACE_DATA' and f.TS# = t.TS#;

Step3> Create A Table in TRACE_DATA Tablespace and Insert few Records
SQL>create table DATA_TRACE_TEST (n number, name varchar2(16)) tablespace TRACE_DATA;
SQL>insert into DATA_TRACE_TEST values (1, 'CREDITCARD');
SQL>insert into DATA_TRACE_TEST values (2, 'DEBITCARD');

SQL> commit;
Step4> Find the Information of the Inserted Rows
SQL>select ROWID, NAME from DATA_TRACE_TEST;
Step5> Find the DB Block Number for Above Rows
SQL>select DBMS_ROWID.ROWID_BLOCK_NUMBER('AAASOXAAJAAAACEAAA') "Block number" from DUAL;
SQL>select DBMS_ROWID.ROWID_BLOCK_NUMBER('AAASOXAAJAAAACEAAB') "Block number" from DUAL;
At this point we know that our data is stored in Tablespace TRACE_DATA and physically in Datafile a datafile file#9 (+TEST_DATA/WDTESTDBA/DATAFILE/trace_data.256.984068463) and corresponding ASM file number for datafile#9 is 256. In File#9 my data is exactly located in Block number 132. Let us deep dive further and Identify which disk is underneath
Step6> Find the Database Block Size for File#9 (File# found in Step 2)
SQL>select BLOCK_SIZE from V$DATAFILE where FILE#=9;
Step7> From ASM instance Identify the DG Number where your Datafile is stored
SQL> select GROUP_NUMBER,NAME from v$asm_diskgroup where name='TEST_DATA';

Step8> From ASM Instance Identify the Extent Distribution for ASM File 256 Stored in Diskgroup Number 4
SQL>select XNUM_KFFXP,            -- extent number
DISK_KFFXP,            -- disk number
AU_KFFXP               -- AU number
from X$KFFXP
where NUMBER_KFFXP=256 -- ASM file number (256)
AND GROUP_KFFXP=4      -- ASM DG Number (1);
As you can see from the above output the extent is distributed across all the disks and each extent is available on disk 0 as well as on disk 1, this is because the diskgroup redundancy is normal and therefore 2 copies of each extent. From the above output we can find the AU for each extent.
In next step I will find out the AU size 
Step9> Find Allocation Unit Size for Diskgroup 4
SQL> select VALUE from V$ASM_ATTRIBUTE where NAME='au_size' and GROUP_NUMBER=4;

So AU_SIZE for DG 4 is 1MB.

Block Size=8K <=Step6
AU_SIZE=1M <= Step9
1M/8K=128 <= and therefore each AU can hold 128 DB Blocks each of 8K in Size.
From Step5 I know that my Data is stored in Block Number 132. Which is basically 4th (132-128) block in the 2nd Extent, in ASM file 256 (see the ASM file name in Step2). From Step8 You can see the 2nd extent (XNUM_KFFXP=1) is stored in disk 0 and 1 in AU 62, so Let us find the name of these disks and extract the AU62 from the disk
Step10> Find the Disk Name from Disk Number
 SQL> select DISK_NUMBER, NAME from V$ASM_DISK where DISK_NUMBER in (0,1) and GROUP_NUMBER=4;
I am using AFD so I can further list the disk as it appears to OS using afd_lsdsk command 
$ asmcmd afd_lsdsk |grep TEST


Step11> Read the Data Directly from Disk
Now we know that my data is stored in AU 62 on disks  /dev/xvde and  /dev/xvdf. I can read it directly from disk
         A>  Extract AU 62 from disk
                # dd if=/dev/xvde bs=1024k count=1 skip=62 of=xvde_AU62.dd                   1+0 records in
                   1+0 records out
                   1048576 bytes (1.0 MB) copied, 0.00244138 s, 430 MB/s
         B> Extract 4th Block from xvde_AU62.dd
                # dd if=xvde_AU62.dd bs=8k count=1 skip=4 of=132_block.dd
                  1+0 records in
                  1+0 records out
                 8192 bytes (8.2 kB) copied, 0.000342058 s, 23.9 MB/s
           C> Read the Content of the File 132_block.dd using strings or od  command

               #strings 132_block.dd |grep CARD
                     DEBITCARD,
                    CREDITCARD
                
     OR      
        # od -c 132_block.dd
0000000 006 242  \0  \0 204  \0   @ 002 220 313 032  \0  \0  \0 001 006
0000020 353 363  \0  \0 001  \0  \0  \0 227   # 001  \0 210 313 032  \0
.....................................................................................................................
.....................................................................................................................
0017720 224  \0 001 002 301 002 002 301 004 004 303   , 001 002 002 301
0017740 003  \t   D   E   B   I   T   C   A   R   D   , 001 002 002 301
0017760 002  \n   C   R   E   D   I   T   C   A   R   D 001 006 220 313
0020000


Follow the Steps A, B and C to validate the presence of DATA in  /dev/xvdf (ie disk 1). Since I was using normal redundancy disk group there is 2 copy of  the data stored in different FG to tolerate the disk failure.


Please give a thumbs up if you like the post and Keep Learning............



Related Posts:

Comments

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the server to be powered on, run the

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry for database (ORCL

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02             EXPORT               FULL       EXECUTING OR You can also find the job name for export/import in logfile in beginning itself. Step2>Attach to the Job and check status One you get the Export/Import Job Name attach the job and check its status. You can attach or det

ORA-15040: diskgroup is incomplete

<<Back to Oracle ASM Main Page ORA-15040: diskgroup is incomplete SQL> startup ORA-00099: warning: no parameter file specified for ASM instance ASM instance started Total System Global Area 1140850688 bytes Fixed Size                  8629704 bytes Variable Size            1107055160 bytes ASM Cache                  25165824 bytes ORA-15110: no diskgroups mounted Reason: The reason of this error is simply the ASM is not able to find the some or all the disks. Solution: Investigate and make all the disks available to ASM to mount the disk group. Make sure the disks has proper permissions. If you are using AFD check following services are online oracleacfs oracleadvm oracleoks  oracleafd   Source of Problem : Issue started after restart of the server After restarting the server when I tried to start the ASM instance its started throwing error.  ORA-15110: no diskgroups mounted Investigation in my Case Step1> ASM Logfile Scanning  Looked i