Dumpla
dumpla#
About dumpla#
ddumpla outputs the contents of loganchor files, which are saved in binary form, in the form of text.
Loganchor files contain information that is necessary in order to recover physically stored information (i.e. data files).When a database is created using the CREATE DATABASE statement, Altibase creates these files and stores them with the sequential names loganchor# (where "#" = 1, 2, or 3). Altibase stores these three files, which have the same contents, in the three respective directories specified using the LOGANCHOR_DIR property in altibase.properties. The reason that three files are maintained is to be prepared in the event that some of the files become lost or corrupt. These files contain information about all of the database's tablespaces and the data files stored in them, as well as recovery-related information. When the database is started, this information is used to load the database into memory and prepare to provide service.
dumpla <loganchor_file_name>
Syntax#
Description#
Outputs the content of a loganchor file in the form of text.
Example#
At a shell prompt, type the following:
$ dumpla loganchor0
Output#
dumpla displays the contents of a loganchor file in the following format:
[LOGANCHOR ATTRIBUTE SIZE]#
This section indicates the amount of space that is occupied by each kind of data in the loganchor file. The contents of this section are as follows:
| Field Name | Value (bytes) | Description |
|---|---|---|
| Loganchor Static Area | From 0 (zero) to the maximum value of the unsigned int type | The size of the static information in the loganchor file. Most of this information is information that is required for recovery. |
| Tablespace Attribute | From 0 (zero) to the maximum value of the unsigned int type | The size of the stored tablespace attributes |
| Checkpoint Path Attribute | From 0 (zero) to the maximum value of the unsigned int type | The size of the stored checkpoint path attributes |
| Checkpoint Image Attribute | From 0 (zero) to the maximum value of the unsigned int type | The size of the stored checkpoint image attributes |
| Disk Datafile Attribute | From 0 (zero) to the maximum value of the unsigned int type | The size of the stored disk datafile attributes |
[LOGANCHOR HEADER]#
This is loganchor header information, such as the version of the database and the checkpoint Log Sequence Number (LSN). For more information about Log Sequence Numbers, please refer to "dumplf Output Items".
| Field Name | Value | Description |
|---|---|---|
| Binary DB Version | Major.minor.patch e.g., 6.2.1 | The version of the database executable file with which the loganchor file was created |
| Archivelog Mode | Archivelog |No-Archivelog | Indicates whether the database is running in archive mode |
| Transaction Segment Entry Count | ||
| Begin Checkpoint LSN | FileNo, Offset | The LSN that was current when checkpointing most recently began. |
| End Checkpoint LSN | FileNo, Offset | The LSN that was current when checkpointing was most recently completed. |
| Disk Redo LSN | FileNo, Offset | The redo start point for a DRDB. |
| LSN for Recovery from Replication | FileNo, Offset | Recovers from replicaiton starts with this LSN. |
| Server Status | SERVER_SHUTDOWN |SERVER_STARTED | Logs the server state. This value is changed to SERVER_STARTED when the server is started and to SERVER_SHUTDOWN when the server is shut down normally. If this value is already set to SERVER_STARTED when the server starts, this indicates that the server was shut down abnormally, so the server will perform restart recovery. |
| End LSN | FileNo, Offset | The LSN of the first log that is written to when the server is started up after having shut down normally |
| ResetLog LSN | FileNo, Offset | The Reset LSN that was set during incomplete recovery |
| Last Created Logfile Num | From 0 (zero) to the maximum value of the unsigned int type | The number of the most recently created log file |
| Delete Logfile(s) Range | Format: [first logfile no. ~ last logfile no.] The numbers of the first and last log files that were deleted. | The range of the most recently deleted log files. When checkpointing is completed, log files that are no longer necessary are deleted. These numbers indicate the range of log files that were deleted. |
| Update And Flush Count | From 0 (zero) to the maximum value of the unsigned int type | The number of times that loganchor files were changed and flushed |
| New Tablespace ID | From 0 (zero) to the maximum value of the unsigned int type | The identifier for the next new tablespace. When a tablespace is created, this value will be used as its identifier, and will then be incremented. |
[TABLESPACE ATTRIBUTE]#
This section provides information about the tablespace. The contents of this section are as follows:
| Field Name | Value | Description |
|---|---|---|
| Tablespace ID | From 0 (zero) to the maximum value of the unsigned int type | The identifier of the tablespace |
| Tablespace Name | String. e.g., SYS_TBS_MEM_DIC | The name of the tablespace |
| New Database File ID | From 0 (zero) to the maximum value of the unsigned int type | The identifier that will be given to the next file to be added to the tablespace |
| Extent Management | FREE EXTENT BITMAP TABLESPACE | This indicates how extents are managed when a disk tablespace is created. At present, only FREE EXTENT BITMAP TABLESPACE is supported. If FREE EXTENT BITMAP TABLESPACE is enabled, bitmaps can be used to manage the free extents in a disk tablespace. |
| Tablespace Status | Refer to Possible Tablespace Status Values in [TABLESPACE ATTRIBUTE]. | Indicates the current status of the tablespace |
| Tablespace Type | 0 - 8 (Refer to Possible Tablespace Type Values in [TABLESPACE ATTRIBUTE]) | Indicates the type of the tablespace |
| Checkpoint Path Count | The number of checkpoint paths | The number of checkpoint image file paths. This applies only to memory tablespaces. |
| Autoextend Mode | AutoExtend |Non-AutoExtend | Indicates whether the tablespace extends in size automatically. This applies only to memory tablespaces |
| Shared Memory Key | From 0 (zero) to the maximum value of the unsigned int type | The shared memory key for a database that resides in shared memory. This applies only to memory tablespaces |
| Stable Checkpoint Image Num | 0|1 | The number corresponding to the set of checkpoint image files that is stable after checkpointing has taken place. This applies only to memory tablespaces |
| Init Size | From 0 (zero) to the maximum value of the unsigned int type | The initial size (MB) of the tablespace |
| Next Size | From 0 (zero) to the maximum value of the unsigned int type | The increment by which the tablespace automatically increases in size (MB) |
| Maximum Size | From 0 (zero) to the maximum value of the unsigned int type | The maximum size of the tablespace. |
| Split File Size | From 0 (zero) to the maximum value of the unsigned int type | When a memory tablespace is created, it consists of multiple files of this size. For example, if a tablespace 1 GB in size is to be created and the split file size is 100 MB, then 10 files will be created. |
In [TABLESPACE ATTRIBUTE], Tablespace Status can have the following values:
| Value | Description |
|---|---|
| OFFLINE | Currently offline |
| ONLINE | Currently online |
| INCONSISTENT | In an inconsistent state |
| CREATING | Being created |
| DROPPING | Waiting to be dropped, because the transaction that will drop the database has not been committed yet |
| DROP_PENDING | The transaction that will drop the database has been committed but the tablespace is still waiting to be dropped because one or more operations are still pending. |
| DROPPED | Deleted (dropped) |
| DISCARDED | Discarded |
| BACKUP | Being backed up |
| SWITCHING_TO_OFFLINE | Being brough online |
| SWITCHING_TO_ONLINE | Being taken offline |
The possible values of Tablespace Type in [TABLESPACE ATTRIBUTE] are as follows:
| Value | Description |
|---|---|
| 0 | MEMORY SYSTEM DICTIONARY |
| 1 | MEMORY SYSETM DATA |
| 2 | MEMORY USER DATA |
| 3 | DISK SYSTEM DATA |
| 4 | DISK USER DATA |
| 5 | DISK SYSTEM TEMP |
| 6 | DISK USER TEMP |
| 7 | DISK SYSTEM UNDO |
| 8 | VOLATILE USER DATA |
[MEMORY CHECKPOINT PATH ATTRIBUTE]#
This section indicates the path in which checkpoint image files are saved for a memory tablespace. The contents of this section are as follows:
| Field Name | Value | Description |
|---|---|---|
| Tablespace ID | From 0 (zero) to the maximum value of the unsigned int type | The identifier of the tablespace |
| Checkpoint Path | String | The checkpoint impage file path |
[MEMORY CHECKPOINT IMAGE ATTRIBUTE]#
This section indicates the checkpoint image information for a memory tablespace. The contents of this section are as follows:
| Field Name | Value | Description |
|---|---|---|
| Tablespace ID | From 0 (zero) to the maximum value of the unsigned int type | The identifier of the tablespace |
| File Number | From 0 (zero) to the maximum value of the unsigned int type | The file number |
| Create LSN | < FileNo, Offset> | The LSN that was current at the time at which the data file was created |
| Create On Disk (PingPong 0) | Created|None | Whether the set of checkpointing files identified by #0 has been created |
| Create On Disk (PingPong 1) | Created|None | Whether the set of checkpointing files identified by #1 has been created |
| ChangeTracking DataFileDescSlot ID | From 0(zero) to the maximum value of the unsigned int type | The DataFileDescSlot ID of the changeTracking file bound to the memory checkpoint image |
[DISK DATABASE FILE ATTRIBUTE]#
This information indicates the path in which the data file or files for a disk tablespace are saved. The contents of this section are as follows:
| Field Name | Value | Description |
|---|---|---|
| Tablespace ID | From 0(zero) to the maximum value of the unsigned int type | The identifier of the tablespace |
| Database File ID | From 0(zero) to the maximum value of the unsigned int type | The identifier of the data file |
| Database File Path | String | The data file path |
| Create LSN | < FileNo, Offset> | The LSN that was current at the time that the dat file was created |
| Database File Status | Refer to Database File Status Values for [DISK DATABASE FILE ATTRIBUTE] | The file state |
| Autoextend Mode | AutoExtend| Non-AutoExtend | Whether auto extension mode has been set |
| Create Mode | 0|1 | 0: The file was reused 1: The file is a newly created file |
| Initialize Size | From 0 (zero) to the maximum value of the unsigned int type | The initial size (MB) of the data file |
| Current Size | From 0 (zero) to the maximum value of the unsigned int type | The initial size (MB) of the data file |
| Next Size | From 0 (zero) to the maximum value of the unsigned int type | The increment by which the data file automatically increases in size (MB) |
| Maximum Size | From 0 (zero) to the maximum value of the unsigned int type | The maximum size (MB) of the data file |
| ChangeTracking DataFileDescSlot ID | From 0(zero) to the maximum value of the unsigned int type | The ID of the DataFileDescSlot of the changeTracking file bound to the disk datafile |
In [DISK DATABASE FILE ATTRIBUTE], Database File Status means the following:
| Value | Description |
|---|---|
| OFFLINE | Offline |
| ONLINE | Online |
| CREATING | Being created |
| BACKUP_BEGIN | Backup has started |
| BACKUP_END | Backup is being completed |
| DROPPING | Being dropped (deleted) |
| RESIZING | Being resized |
| DROPPED | Has been dropped |
The following is an example of some of the information output by dumpla:
[ DISK DATABASE FILE ATTRIBUTE ]
Tablespace ID [ 2 ]
Database File ID [ 0 ]
Database File Path C:\altibase_home\dbs\system001.dbf]
Create LSN [0, 4443 ]
Database File Status [ ONLINE ]
Autoextend Mode [ Non-Autoextend ]
Create Mode [ 0 ]
Initialize Size [10 MBytes(1280 Pages)]
Current Size [10 MBytes(1280 Pages)]
Next Size [0 MBytes(0 Pages)]
Maximum Size [0 MBytes(0 Pages)]
[Change Tracking ATTRIBUTE]#
This section provides information about the changeTracking file. The contents of this section are as follows:
| Field Name | Value | Description |
|---|---|---|
| Last Flush LSN | FileNo, Offset | The LSN at the time data changed in memory were written to files |
| Change Tracking Manager State | String. e.g., CHANGE TRACKING MGR ENABLED | The page change tracking state |
| Change Tracking File Name | String | The changeTracking file path |
[Backup Info ATTRIBUTE]#
This section provides information about the backupInfo file. The contents of this section are as follows:
| Field Name | Value | Description |
|---|---|---|
| Delete Archivelog File Range | FileNo, Offset | The number of the archive log file which can be completely recovered, even after deletion |
| Last Backup LSN | FileNo, Offset | The LSN at the time of the most recently performed backup |
| Before Backup LSN | FileNo, Offset | The LSN prior to the time of the most recently performed backup |
| Backup Info Manager State | String. e.g., BACKUP INFO MGR INITIALIZED | The backup information file manager state |
| Backup Directory Path | String. e.g., /backup_dir/ | The backup path |
| Backup Info File Name | String | The backup information file name |