getVLDBInfo

Returns detailed information about a VLDB.

Request

<getVLDBInfo type=" "/>

Reply

<getVLDBInfo>
   <basicInfo>
      <vldbState/>
      <version>
         <majorVersion/>
         <minorVersion/>
         <releaseNumber/>
         <buildNumber/>
      </version>
      <backEndVersion>
         <majorVersion/>
         <minorVersion/>
         <releaseNumber/>
         <buildNumber/>
      </backEndVersion>
      <vldbBuildDate value=" "/>
      <vldbLoadTime value=" "/>
      <numProcessThreads/>
      <numRunningThreads/>
      <backEndDatabasePath/>
      <autoLoadVLDB/>
   </basicInfo>
   <statisticsInfo>
      <vldbCreateCount/>
      <vldbDeleteCount/>
      <vldbModifyCount/>
      <vldbLookupCount/>
      <vldbTotalRequests/>
      <vldbErrorCount/>
      <vldbAuthErrorCount/>
   </statisticsInfo>
   <repairInfo>
      <repairState/>
      <repairPercentComplete/>
      <repairLevel/>
      <repairStartTime value = " "/>
      <repairEndTime value=" "/>
      <repairStatus/>
      <repairCompletionCode/>
   </repairInfo>
   <result value=" ">
      <description/>
   </result>
</getVLDBInfo>

Elements

basicInfo

Specifies the basic information if the type specifies all or basic.

vldbState

Specifies the state of the VLDB:

  • initializing
  • stopped
  • running
  • broken
  • underRepair
  • unknown
version

Specifies the version of the VLDB.

majorVersion

Specifies the major version number.

minorVersion

Specifies the minor version number.

buildNumber

Specifies the build number.

backEndVersion

Specifies the version of the VLDB backend.

releaseNumber

Specifies the release number.

vldbBuildDate

Specifies the date that the vldb.nlm file was built.

vldbLoadTime

Specifies the time that the vldb.nlm file was loaded.

numProcessThreads

Specifies the number of threads the VLDB requested to use.

numRunningThreads

Specifies the number of threads that the VLDB is currently using.

backEndDatabasePath

Specifies the path where the backend database is located.

autoLoadVLDB

Specifies that the VLDB is set up to be auto loaded when the server is started.

statisticsInfo

Specifies the statistical information if the type specifies all or statistics.

vldbCreateCount

Specifies the number of volumes that were added to the VLDB.

vldbDeleteCount

Specifies the number of volumes that were deleted from the VLDB.

vldbModifyCount

Specifies the number of volumes that were modified in the VLDB.

vldbLookupCount

Specifies the number of volumes that were looked up in the VLDB.

vldbTotalRequests

Specifies the total number of requests made to the VLDB.

vldbErrorCount

Specifies the number of errors in VLDB requests.

vldbAuthErrorCount

Specifies the number of authorization errors.

repairInfo

Specifies the repair information if the type specifies all or repair.

repairState

Specifies the state of repairs:

  • notRepairing
  • repairing
  • complete
  • failed
  • unknown
repairPercentComplete

Specifies how complete (as a percentage) the current repair is.

repairLevel

Specifies the level of the current repair:

  • none
  • lowLevel
  • refresh
  • rebuild
  • unknown
repairStartTime

Specifies the time the current or last repair started.

repairEndTime

Specifies the time the current or last repair ended.

repairStatus

Specifies the status of the current repair:

  • success
  • failed
  • aborted
  • unknown
repairCompletionCode

Specifies the error code that was returned by the last repair operation.

result

Specifies an error value or 0 (for no error).

description

Specifies a text description of the result.

Attributes

type

Specifies the properties of the VLDB to return:

  • all
  • basic
  • statistics
  • repair

If all is specified, all the information for the VLDB is returned. Otherwise, only the specified type of requested information is returned.

value

Specifies the decimal value of the date. The high 16 bits is the year, followed by 8 bits for the month. The last 8 bits is the day.

or

Specifies the UTC decimal time.

Example

A nssRequest packet to returns VLDB information is as follows:

<nssRequest>
   <vldb>
      <getVLDBInfo type="all">
      </getVLDBInfo>
   </vldb>
</nssRequest>

Depending on the management context, the following are examples of reply packets that can be returned:

Usual Reply

A nssReply packet to the get VLDB information command follows:

<nssReply>
   <vldb>
      <getVLDBInfo>
         <basicInfo>
            <vldbState>running</vldbState>
            <version>
               <majorVersion>3</majorVersion>
               <minorVersion>1</minorVersion>
               <releaseNumber>0</releaseNumber>
               <buildNumber>37</buildNumber>
            </version>
            <backEndVersion>
               <majorVersion>3</majorVersion>
               <minorVersion>1</minorVersion>
               <releaseNumber>0</releaseNumber>
               <buildNumber>33</buildNumber>
            </backEndVersion>
            <vldbBuildDate value="131203344">
               2002-1-16
            </vldbBuildDate>
            <vldbLoadTime value="1015620810">
               Mar 8, 2002   1:53:30 pm
            </vldbLoadTime>
            <numProcessThreads>1</numProcessThreads>
            <numRunningThreads>1</numRunningThreads>
            <backEndDatabasePath>
               sys:\etc</backEndDatabasePath>
            <autoLoadVLDB>true</autoLoadVLDB>
         </basicInfo>

         <statisticsInfo>
            <vldbCreateCount>4</vldbCreateCount>
            <vldbDeleteCount>0</vldbDeleteCount>
            <vldbModifyCount>0</vldbModifyCount>
            <vldbLookupCount>0</vldbLookupCount>
            <vldbTotalRequests>10</vldbTotalRequests>
            <vldbErrorCount>0</vldbErrorCount>
            <vldbAuthErrorCount>0</vldbAuthErrorCount>
         </statisticsInfo>

         <repairInfo>
            <repairState>notRepairing</repairState>
             <repairPercentComplete>0</repairPercentComplete>
            <repairLevel>rebuild</repairLevel>
            <repairStartTime value="1015620814">
               Mar 8, 2002   1:53:34 pm
            </repairStartTime>
            <repairEndTime value="1015620815">
               Mar 8, 2002   1:53:35 pm
            </repairEndTime>
            <repairStatus>success</repairStatus>
            <repairCompletionCode>0</repairCompletionCode>
         </repairInfo>

         <result value="0">
            <description/>success</description>
         </result>
      </getVLDBInfo>
   </vldb>

   <result value="0">
      <description/>zOK</description>
   </result>
</nssReply>

No Management Context

If there is no management context defined, the following response returns:

<nssReply>
   <vldb>
      <getVLDBInfo>
         <result value="0">
            <description/>success</description>
         </result>
         <basicInfo>
         <statisticsInfo>
         <repairInfo>
      </getVLDBInfo>
   </vldb>
</nssReply>

Management Context: VLDB Server Running

If a management context is defined for a VLDB server, the following response returns:

Note that for NetWare 6.5 SP2, replica server names are relative to the management context. For NetWare 6.5 SP1, replica server names are fully distinguished eDirectory names.

<nssReply>
   <vldb>
      <getVLDBInfo>
         <result value="0">
            <description/>success</description>
         </result>
         <basicInfo>
            <managementContext>
               <ndsObject>nss.prv.novell</ndsObject>
               <tgtTree>novell_inc</tgtTree>
            </managementContext>
            <backEndDB>vdqad</backEndDB>
            <serverName>vldb-master</serverName>
            <serverName>vldb-other.nss.prv</serverName>
            <vldbState>running</vldbState>
            <version>
               <majorVersion>3</majorVersion>
               <minorVersion>20</minorVersion>
               <releaseNumber>0</releaseNumber>
               <buildNumber>157</buildNumber>
            </version>
            <backEndVersion>
               <majorVersion>3</majorVersion>
               <minorVersion>20</minorVersion>
               <releaseNumber>0</releaseNumber>
               <buildNumber>152</buildNumber>
            </backEndVersion>
            <vldbBuildDate value="131203344">2002-1-16</vldbBuildDate>
            <vldbLoadTime value="1015620810">Mar 8, 2002  1:53:30 pm
               </vldbLoadTime>
            <numProcessThreads>1</numProcessThreads>
            <numRunningThreads>1</numRunningThreads>
            <backEndDatabasePath>sys:\etc</backEndDatabasePath>
            <autoLoadVLDB>true</autoLoadVLDB>
         </basicInfo>
         <statisticsInfo>
            <vldbCreateCount>4</vldbCreateCount>
            <vldbDeleteCount>0</vldbDeleteCount>
            <vldbModifyCount>0</vldbModifyCount>
            <vldbLookupCount>0</vldbLookupCount>
            <vldbTotalRequests>10</vldbTotalRequests>
            <vldbErrorCount>0</vldbErrorCount>
            <vldbAuthErrorCount>0</vldbAuthErrorCount>
         </statisticsInfo>
         <repairInfo>
            <repairState>notRepairing</repairState>
            <repairPercentComplete>0</repairPercentComplete>
            <repairLevel>rebuild</repairLevel>
            <repairStartTime value="1015620814>Mar 8, 2002 1:53:34 pm
               </repairStartTime>
            <repairEndTime value="1015620815">Mar 8, 2002 2:53:35 pm
               </repairEndTime>
            <repairStatus>success</repairStatus>
            <repairCompletionCode>0</repairCompletionCode>
         </repairInfo>
      </getVLDBInfo>
   </vldb>
</nssReply>

Management Context: VLDB Server Not Running

If a management context is defined for a VLDB server but the server isn't running, the following response returns:

<nssReply>
   <vldb>
      <getVLDBInfo>
         <result value="0">
            <description/>success</description>
         </result>
         <basicInfo>
            <managementContext>
               <ndsObject>nss.prv.novell</ndsObject>
               <tgtTree>novell_inc</tgtTree>
            </managementContext>
            <backEndDB>vdqad</backEndDB>
            <serverName>vldb-master</serverName>
            <serverName>vldb-other.nss.prv</serverName>
            <vldbState>notLoaded</vldbState>
         </basicInfo>
         <statisticsInfo/>
         <repairInfo/>
      </getVLDBInfo>
   </vldb>
</nssReply>

Management Context: Not a VLDB Server

If a management context is defined and the server isn't a VLDB server, the following response returns:

<nssReply>
   <vldb>
      <getVLDBInfo>
         <result value="0">
            <description/>success</description>
         </result>
         <basicInfo>
            <managementContext>
               <ndsObject>nss.prv.novell</ndsObject>
               <tgtTree>novell_inc</tgtTree>
            </managementContext>
            <backEndDB>vdqad</backEndDB>
            <serverName>vldb-master</serverName>
            <serverName>vldb-other.nss.prv</serverName>
            <vldbState>notVLDBServer</vldbState>
         </basicInfo>
         <statisticsInfo/>
         <repairInfo/>
      </getVLDBInfo>
   </vldb>
</nssReply>