Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2061350.1
Update Date:2015-10-01
Keywords:

Solution Type  Technical Instruction Sure

Solution  2061350.1 :   FS System: How to Dump Persistence Tables in Text and Binary Formats with NPperf  


Related Items
  • Oracle FS1-2 Flash Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
  •  




In this Document
Goal
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: not intended for customers

Applies to:

Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

There may be times when a dump of the system configuration database called Persistence is required for investigating a problem.  This document provides the instructions to dump the Persistence tables that have valid records in both text and binary formats, as both may be required.

 

Solution

The procedure below will create a binary and text dump of all Persistence tables that have active records.  

SSH access to the Pilot is required.  Refer to <Document 2029847.1> FS System: How to Enable SSH Access to the Pilot.

These commands will create a subdirectory named np_tables. The dumps will be the table number in hex. The binary dumps will have a .dat extension, and the text dumps will have a .txt extension. For example: table8002.dat and table8002.txt.

 

NOTE: Do not attempt to run any NPperf command without being requested to do so from Engineering.  Improper use of the NPperf command can lead to undesired consequences. Use only the NPperf commands as instructed below.

 

  1. After logging into the Pilot shell, create a directory for the data to be gathered and cd to that directory:
    [root@pilot1 ~]# mkdir /var/tmp/NP
    [root@pilot1 ~]# cd /var/tmp/NP
    [root@pilot1 NP]#
     
  2. Use the NPperf utility to dump all active Persistence tables in binary format:
    #[root@pilot1 NP]# /usr/share/pillar/bin/NPperf table=all binaryDump=yes
    In np_read_all_table()
    found 1 keys in table 0x0
    found 1 keys in table 0x4006
    found 1 keys in table 0x5004
    found 29 keys in table 0x5005
    found 1 keys in table 0x5008
    found 16 keys in table 0x5009
    ...
    found 95 keys in table 0x8011
    found 1 keys in table 0x8014
    found 1 keys in table 0x8026
    found 1 keys in table 0x8027
    found 1 keys in table 0x10000
    [root@pilot1 NP]#
     
  3. Repeat the previous command but this time dump all active Persistence tables in text format:
    [root@pilot1 NP]# /usr/share/pillar/bin/NPperf table=all binaryDump=no
    In np_read_all_table()
    found 1 keys in table 0x0
    found 1 keys in table 0x4006
    found 1 keys in table 0x5004
    found 29 keys in table 0x5005
    found 1 keys in table 0x5008
    found 16 keys in table 0x5009
    ...
    found 95 keys in table 0x8011
    found 1 keys in table 0x8014
    found 1 keys in table 0x8026
    found 1 keys in table 0x8027
    found 1 keys in table 0x10000
    [root@pilot1 NP]#
     
  4. Confirm the contents of the NP directory contains the binary and text formatted files:
    #[root@pilot1 NP]# ls np_tables
    table0.dat      table4006.txt table5008.dat table500b.txt table500f.dat table8002.txt table8009.dat table800e.txt table8026.dat
    table0.txt      table5004.dat table5008.txt table500d.dat table500f.txt table8003.dat table8009.txt table8011.dat table8026.txt
    table10000.dat  table5004.txt table5009.dat table500d.txt table5011.dat table8003.txt table800a.dat table8011.txt table8027.dat
    table10000.txt  table5005.dat table5009.txt table500e.dat table5011.txt table8004.dat table800a.txt table8014.dat table8027.txt
    table4006.dat   table5005.txt table500b.dat table500e.txt table8002.dat table8004.txt table800e.dat table8014.txt
    [root@pilot1 NP]#
      

  5. Tar or zip the entire /var/tmp/NP directory:
    #[root@pilot1 NP]# tar cvf - np_tables > NPdumpall.tar
    np_tables/
    np_tables/table10000.txt
    np_tables/table8026.txt
    np_tables/table8014.txt
    np_tables/table8011.dat
    np_tables/table0.dat
    np_tables/table5008.txt
    np_tables/table8027.txt
    np_tables/table5005.txt
    np_tables/table8002.dat
    np_tables/table4006.dat
    np_tables/table5005.dat
    ...
    np_tables/table0.txt
    np_tables/table5004.dat
    np_tables/table500b.dat
    np_tables/table8014.dat
    np_tables/table5011.dat
    [root@pilot1 NP]#
     
  6. Using a program like WinSCP, copy the NPdumpall.tar file from the Pilot to a laptop or other external terminal.

  7. Once the NPperf tables have been copied from the Pilot, clean up by removing the /var/tmp/NP directory:
    [root@pilot1 NP]# cd /var/tmp
    [root@pilot1 tmp]# rm -Rf NP
    [root@pilot1 tmp]#
      

  8. Upload the NPdumpall.tar file to Oracle Support so that it is attached to the Service Request for this issue.  See KM <Document 1596914.1> My Oracle Support - How to series -> How to upload and attach files to Service Requests using three options [Video] for details.

 

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback