Source:SAP ERP with MaxDB: Difference between revisions
m (removed draft) |
(Prepared for translation.) |
||
Line 1: | Line 1: | ||
<div class="noprint">{{Copyright SEP AG|en}} | <translate><noinclude><div class="noprint"><languages /> | ||
{{Copyright SEP AG|en}} | |||
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/SAP|SAP ERP archive]]}}</div><br /> | {{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/SAP|SAP ERP archive]]}}</div></noinclude></translate><br /> | ||
=={{anchor|overview}}Overview== | <translate>=={{anchor|overview}}Overview==</translate> | ||
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Additional resources</b></center> | <div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><translate>Additional resources</translate></b></center> | ||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=SAP_ERP]] | | rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=SAP_ERP]] | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | See also: [[Special:MyLanguage/SAP_ERP|SAP ERP]] | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>See also: [[Special:MyLanguage/SAP_ERP|SAP ERP]]</translate> | ||
|} | |} | ||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]] | | rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]] | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |<translate>Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions.</translate> | ||
Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions. | |||
|} | |} | ||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Troubleshooting_Guide]] | | rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Troubleshooting_Guide]] | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]. | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |<translate>Problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].</translate> | ||
|} | |} | ||
</div> | </div> | ||
The MaxDB backup/restore is performed with the Database Manager CLI (<tt>dbmcli</tt>) utility, as described in the section [[Special:MyLanguage/4_4_3:SAP_ERP_with_MaxDB#calls|<tt>dbmcli</tt> calls]]. The <tt>backint</tt> is an interface program that allows <tt>dbmcli</tt> to communicate with SAP MaxDB using pipes to perform backup and restore operations. | <translate>The MaxDB backup/restore is performed with the Database Manager CLI (<tt>dbmcli</tt>) utility, as described in the section [[Special:MyLanguage/4_4_3:SAP_ERP_with_MaxDB#calls|<tt>dbmcli</tt> calls]]. The <tt>backint</tt> is an interface program that allows <tt>dbmcli</tt> to communicate with SAP MaxDB using pipes to perform backup and restore operations. | ||
==={{anchor|requirements}}Requirements=== | ==={{anchor|requirements}}Requirements=== | ||
To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met: | To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:</translate> | ||
*Check the [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#MAX-DB|support matrix]] for the list of supported MaxDB versions. Note that all components for setting up the MaxDB extension are already included in the SEP sesam installation packages. | *<translate>Check the [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#MAX-DB|support matrix]] for the list of supported MaxDB versions. Note that all components for setting up the MaxDB extension are already included in the SEP sesam installation packages.</translate> | ||
*SEP sesam Server v. 4.4.3 or higher. Check [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]], [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]] or [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]]. | *<translate>SEP sesam Server v. 4.4.3 or higher. Check [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]], [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]] or [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]].</translate> | ||
*Install the SAP ERP database on MaxDB v. 6.2 or 7.2.5. | *<translate>Install the SAP ERP database on MaxDB v. 6.2 or 7.2.5.</translate> | ||
*Install the [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]] package on the SAP ERP server. You can download it from {{download}}. The installation procedure is slightly different depending on the operating system type (Linux/Unix or Windows). For details on OS specific installation, see [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide|SEP sesam Quick Install Guide]]. | *<translate>Install the [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]] package on the SAP ERP server. You can download it from {{download}}. The installation procedure is slightly different depending on the operating system type (Linux/Unix or Windows). For details on OS specific installation, see [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide|SEP sesam Quick Install Guide]]. | ||
=={{anchor|installation}}Installing SAP ERP on MaxDB== | =={{anchor|installation}}Installing SAP ERP on MaxDB== | ||
Line 36: | Line 36: | ||
==={{anchor|Unix}}On Linux/Unix=== | ==={{anchor|Unix}}On Linux/Unix=== | ||
Once you have downloaded your [https://download.sep.de/linux/ SEP sesam Linux Client] on the SAP ERP server, proceed as follows: | |||
<ol><li>Unpack the <tt>tar-archive</tt> into a temporary directory. The archive contains the following files: | Once you have downloaded your [https://download.sep.de/linux/ SEP sesam Linux Client] on the SAP ERP server, proceed as follows:</translate> | ||
<ol><li><translate>Unpack the <tt>tar-archive</tt> into a temporary directory. The archive contains the following files:</translate> | |||
*<tt>backint_sapdb</tt> | *<tt>backint_sapdb</tt> | ||
*<tt>backint_sapdb.utl</tt> | *<tt>backint_sapdb.utl</tt> | ||
*<tt>bsi.env</tt> | *<tt>bsi.env</tt> | ||
<li>Copy the <tt>backint_sapdb</tt> file to {{path|<SESAM_ROOT>/bin/sesam}} directory as a ''root'' user. This file has to be executable for the MaxDB user. You can also use a different directory. In this case, you have to adjust the configuration accordingly. | <li><translate>Copy the <tt>backint_sapdb</tt> file to {{path|<SESAM_ROOT>/bin/sesam}} directory as a ''root'' user. This file has to be executable for the MaxDB user. You can also use a different directory. In this case, you have to adjust the configuration accordingly.</translate></li> | ||
<li>Check if the programs <tt>sbc</tt> and <tt>sbc_com_interface</tt> are executable for the MaxDB user in the directory {{path|<SESAM DIR>/bin/sesam}}. | <li><translate>Check if the programs <tt>sbc</tt> and <tt>sbc_com_interface</tt> are executable for the MaxDB user in the directory {{path|<SESAM DIR>/bin/sesam}}.</translate></li> | ||
<li>Copy the file <tt>backint_sapdb.utl</tt> to the MaxDB <tt><wrk_directory></tt> (e.g., {{path|/usr/sapdb/indep_data/wrk/CER}}, if the database DBsid is ''CER'').</li></ol> | <li><translate>Copy the file <tt>backint_sapdb.utl</tt> to the MaxDB <tt><wrk_directory></tt> (e.g., {{path|/usr/sapdb/indep_data/wrk/CER}}, if the database DBsid is ''CER'').</translate></li></ol> | ||
<translate>==={{anchor|Windows}}On Windows=== | |||
Once you have installed your [https://download.sep.de/windows/ SEP sesam Windows Client] on the SAP ERP server, proceed as follows:</translate> | |||
Once you have installed your [https://download.sep.de/windows/ SEP sesam Windows Client] on the SAP ERP server, proceed as follows: | <ol><li><translate>SEP sesam Windows Client already includes the necessary files for the MaxDB:</translate> | ||
<ol><li>SEP sesam Windows Client already includes the necessary files for the MaxDB: | |||
*<tt>backint_sapdb</tt> | *<tt>backint_sapdb</tt> | ||
*<tt>backint_sapdb.utl</tt> | *<tt>backint_sapdb.utl</tt> | ||
*<tt>bsi.env</tt> | *<tt>bsi.env</tt> | ||
<li>The <tt>backint_sapdb.exe</tt> program is located in the directory {{path|<SESAM ROOT>\bin\sesam}}. You can copy it to a different directory, e.g., the MaxDB <tt>bin</tt> directory. In this case, you have to adjust the configuration accordingly. | <li><translate>The <tt>backint_sapdb.exe</tt> program is located in the directory {{path|<SESAM ROOT>\bin\sesam}}. You can copy it to a different directory, e.g., the MaxDB <tt>bin</tt> directory. In this case, you have to adjust the configuration accordingly.</translate></li> | ||
<li>Copy the files <tt>backint_ sapdb.utl</tt> and <tt>bsi.env</tt> from the directory {{path|<SESAM ROOT>/skel/}} to the MaxDB <tt><wrk_ directory></tt> (e.g., {{path|C:\Program Files\sapdb\indep_data\wrk\CER}}, if the database DBsid is ''CER'').</li></ol> | <li><translate>Copy the files <tt>backint_ sapdb.utl</tt> and <tt>bsi.env</tt> from the directory {{path|<SESAM ROOT>/skel/}} to the MaxDB <tt><wrk_ directory></tt> (e.g., {{path|C:\Program Files\sapdb\indep_data\wrk\CER}}, if the database DBsid is ''CER'').</translate></li></ol> | ||
<translate>=={{anchor|server}}Configuration on SEP sesam Server== | |||
After you have installed SAP ERP on MaxDB, proceed as follows:</translate> | |||
After you have installed SAP ERP on MaxDB, proceed as follows: | <ol><li><translate>Configure your SAP ERP as a SEP sesam client by adding it to the SEP sesam environment: '''Main Selection''' -> '''Components''' -> '''Topology''' -> '''New Client''' -> add your SAP ERP client. For details, see [[Special:MyLanguage/Configuring_Clients|Configuring Clients]].</translate></li> | ||
<ol><li>Configure your SAP ERP as a SEP sesam client by adding it to the SEP sesam environment: '''Main Selection''' -> '''Components''' -> '''Topology''' -> '''New Client''' -> add your SAP ERP client. For details, see [[Special:MyLanguage/Configuring_Clients|Configuring Clients]].</li> | <li><translate>Additionally, you have to create at least one backup task for the SAP ERP server with the '''MaxDB''' [[Special:MyLanguage/SEP_sesam_Glossary#task_type|task type]]. Note that the entry for source can be specified freely. For details, see [[Special:MyLanguage/Creating_a_Backup_Task|Creating a Backup Task]].</translate></li> | ||
<li>Additionally, you have to create at least one backup task for the SAP ERP server with the '''MaxDB''' [[Special:MyLanguage/SEP_sesam_Glossary#task_type|task type]]. Note that the entry for source can be specified freely. For details, see [[Special:MyLanguage/Creating_a_Backup_Task|Creating a Backup Task]].</li> | {{<translate>note</translate>|<translate>This task cannot be used for regular ''Path'' backups. It is recommended that you configure more dedicated tasks, e.g., to distinguish database backups from archive log backups. Which data is actually backed up depends on the respective SAP ERP backup call.</translate>}} | ||
{{note|This task cannot be used for regular ''Path'' backups. It is recommended that you configure more dedicated tasks, e.g., to distinguish database backups from archive log backups. Which data is actually backed up depends on the respective SAP ERP backup call.}} | |||
</ol> | </ol> | ||
=={{anchor|client}}Configuration on the SEP sesam SAP ERP MaxDB client== | <translate>=={{anchor|client}}Configuration on the SEP sesam SAP ERP MaxDB client== | ||
In order for MaxDB to be able to use the SEP sesam <tt>backint_sapdb</tt> program, you have to adjust the following entries in the profile file (default: {{path|<wrk_directory>/bsi.env}}):</translate> | |||
;BACKINT = <translate><full path of the <tt>backint_sapdb</tt> program></translate> | |||
;INPUT = <translate><full path of the input file>: This file is used by the MaxDB server to communicate with the <tt>backint</tt> program.</translate> | |||
;OUTPUT = <translate><full path of the output file>: This file is used by the MaxDB server to communicate with the <tt>backint</tt> program.</translate> | |||
;ERROROUTPUT = <translate><full path of the error file>: Contains the error messages of the <tt>backint</tt> program.</translate> | |||
;PARAMETERFILE = <translate><full path of the parameter file which will be used>: In this file the SEP sesam specific parameters are adjusted.</translate> | |||
;CHECK_AVAILABILITY <translate><number>BACKUPS: Number of the old backups queried during restore. | |||
For details, see [http://maxdb.sap.com/doc/7_7/45/74841112e14022e10000000a1553f6/content.htm Creating the Configuration File for Backint for SAP MaxDB] and [http://maxdb.sap.com/doc/7_7/a9/8a1ef21e4b402bb76ff75bb559a98a/content.htm Example of a Configuration File for Backint for SAP MaxDB]. | For details, see [http://maxdb.sap.com/doc/7_7/45/74841112e14022e10000000a1553f6/content.htm Creating the Configuration File for Backint for SAP MaxDB] and [http://maxdb.sap.com/doc/7_7/a9/8a1ef21e4b402bb76ff75bb559a98a/content.htm Example of a Configuration File for Backint for SAP MaxDB]. | ||
'''Example of a <tt>bsi.env</tt> file:''' | '''Example of a <tt>bsi.env</tt> file:'''</translate> | ||
'''''On Linux''''' | '''''<translate>On Linux</translate>''''' | ||
BACKINT /opt/sesam/bin/sesam/backint_sapdb | BACKINT /opt/sesam/bin/sesam/backint_sapdb | ||
INPUT /tmp/infile4sapdb | INPUT /tmp/infile4sapdb | ||
Line 85: | Line 89: | ||
CHECK_AVAILABILITY 20BACKUPS | CHECK_AVAILABILITY 20BACKUPS | ||
'''''On Windows''''' | '''''<translate>On Windows</translate>''''' | ||
BACKINT "C:\Program Files\SEPsesam\bin\sesam\backint_sapdb.exe" | BACKINT "C:\Program Files\SEPsesam\bin\sesam\backint_sapdb.exe" | ||
INPUT C:\temp\CER_sapdb.in | INPUT C:\temp\CER_sapdb.in | ||
Line 96: | Line 100: | ||
CHECK_AVAILABILITY 20BACKUPS | CHECK_AVAILABILITY 20BACKUPS | ||
{{Note| | {{<translate>Note</translate>| | ||
*MaxDB does not support spaces in the file names for <tt>INPUT</tt>, <tt>OUTPUT</tt> and <tt>PARAMETERFILE</tt>! | *<translate>MaxDB does not support spaces in the file names for <tt>INPUT</tt>, <tt>OUTPUT</tt> and <tt>PARAMETERFILE</tt>!</translate> | ||
*Setting the <tt>CHECK_AVAILABILITY</tt> is important for the restore. If not set, SAP ERP asks SEP sesam Server about the status of all performed backups, which can take considerable time. By setting the <tt>CHECK_AVAILABILITY</tt> only the last <tt><number>BACKUPS</tt> are requested. Make sure that there is no space between the number and <tt>BACKUPS</tt>; the syntax is <tt><number>BACKUPS</tt>.}} | *<translate>Setting the <tt>CHECK_AVAILABILITY</tt> is important for the restore. If not set, SAP ERP asks SEP sesam Server about the status of all performed backups, which can take considerable time. By setting the <tt>CHECK_AVAILABILITY</tt> only the last <tt><number>BACKUPS</tt> are requested. Make sure that there is no space between the number and <tt>BACKUPS</tt>; the syntax is <tt><number>BACKUPS</tt>.</translate>}} | ||
You can create several profile files. They are declared to the MaxDB by setting the environment variable <tt>BSI ENV</tt>. | <translate>You can create several profile files. They are declared to the MaxDB by setting the environment variable <tt>BSI ENV</tt>. | ||
Example for setting the environment variable <tt>BSI ENV</tt>: | Example for setting the environment variable <tt>BSI ENV</tt>:</translate> | ||
dbmcli -d CER -u dbm,dbm dbm_configset -raw BSI_ENV /usr/sapdb/indep_data/wrk/CER/bsi.env | dbmcli -d CER -u dbm,dbm dbm_configset -raw BSI_ENV /usr/sapdb/indep_data/wrk/CER/bsi.env | ||
You can set different values for <tt>PARAMETERFILE</tt> in the respective profile files; for example, to use different media pools. | <translate>You can set different values for <tt>PARAMETERFILE</tt> in the respective profile files; for example, to use different media pools. | ||
You have to configure at least the following parameters in the <tt>PARAMETERFILE</tt>: | You have to configure at least the following parameters in the <tt>PARAMETERFILE</tt>:</translate> | ||
;SESAM_SERVER = <SEP_sesam_Server>: The name of the SEP sesam Server. | ;SESAM_SERVER = <translate><SEP_sesam_Server>: The name of the SEP sesam Server.</translate> | ||
;SESAM_JOB = <SEP sesam SAP MaxDB client task>: The name of the SEP sesam backup task which you have configured before. For details, see section above [[Special:MyLanguage/4_4_3:SAP_ERP_with_MaxDB#server|Configuration on SEP sesam Server]]. | ;SESAM_JOB = <translate><SEP sesam SAP MaxDB client task>: The name of the SEP sesam backup task which you have configured before. For details, see section above [[Special:MyLanguage/4_4_3:SAP_ERP_with_MaxDB#server|Configuration on SEP sesam Server]].</translate> | ||
;SESAM_DRIVE=<SEP_sesam_drive_number>: The number of the SEP sesam drive that you want to use for backup. | ;SESAM_DRIVE=<translate><SEP_sesam_drive_number>: The number of the SEP sesam drive that you want to use for backup.</translate> | ||
;SESAM_POOL=<SEP sesam media pool>: The name of the SEP sesam media pool that you want to use for backup. | ;SESAM_POOL=<translate><SEP sesam media pool>: The name of the SEP sesam media pool that you want to use for backup.</translate> | ||
;SSB_LOGFILE=<log_file_name>: Full path of the SEP sesam <tt>backint</tt> log file. | ;SSB_LOGFILE=<translate><log_file_name>: Full path of the SEP sesam <tt>backint</tt> log file. | ||
Optionally, set the additional parameters: | Optionally, set the additional parameters:</translate> | ||
;SBC=<SEP_sesam_path>: Full path of the SEP sesam backup program. It only has to be set if the standard <tt>sbc</tt> cannot be used. | ;SBC=<translate><SEP_sesam_path>: Full path of the SEP sesam backup program. It only has to be set if the standard <tt>sbc</tt> cannot be used.</translate> | ||
;PORT=<SEP_sesam_Server_communication_port>: Only required if the ''STPD'' port was changed during the SEP sesam Server installation. | ;PORT=<translate><SEP_sesam_Server_communication_port>: Only required if the ''STPD'' port was changed during the SEP sesam Server installation.</translate> | ||
;SESAM_TAPESERVER=<Remote_device_server>: IP name of the RDS for backup. By using this entry you can specify the backup net. | ;SESAM_TAPESERVER=<translate><Remote_device_server>: IP name of the RDS for backup. By using this entry you can specify the backup net. | ||
'''Example of a parameter (<tt>.utl</tt>) file:''' | '''Example of a parameter (<tt>.utl</tt>) file:'''</translate> | ||
'''''On Linux''''' | '''''<translate>On Linux</translate>''''' | ||
SESAM_SERVER=seplinux | SESAM_SERVER=seplinux | ||
SESAM_JOB=lxsap01_SAP | SESAM_JOB=lxsap01_SAP | ||
Line 131: | Line 135: | ||
SSB_LOGFILE=/sapdb/data/wrk/CER/backint_CER.log | SSB_LOGFILE=/sapdb/data/wrk/CER/backint_CER.log | ||
'''''On Windows''''' | '''''<translate>On Windows</translate>''''' | ||
SESAM_SERVER=seplinux | SESAM_SERVER=seplinux | ||
SESAM_JOB=win03_SAP | SESAM_JOB=win03_SAP | ||
Line 138: | Line 142: | ||
SSB_LOGFILE=C:\ProgramData\sdb\globaldata\wrk\CER\backint_CER.log | SSB_LOGFILE=C:\ProgramData\sdb\globaldata\wrk\CER\backint_CER.log | ||
=={{anchor|log_files}}SAP ERP log files on MaxDB== | <translate>=={{anchor|log_files}}SAP ERP log files on MaxDB== | ||
The following log files are written by the individual SAP ERP backup modules in the MaxDB <tt><wrk_ directory></tt> (e.g., {{path|/sapdb/data/wrk/CER}} or {{path|/usr/sapdb/indep_ data/wrk/CER}}, if the database DBsid is ''CER''). | The following log files are written by the individual SAP ERP backup modules in the MaxDB <tt><wrk_ directory></tt> (e.g., {{path|/sapdb/data/wrk/CER}} or {{path|/usr/sapdb/indep_ data/wrk/CER}}, if the database DBsid is ''CER''). | ||
Line 152: | Line 156: | ||
'''Example''' | '''Example''' | ||
In the following example, we have created three external media for full, incremental and log backup. These are pipes that are used to transfer the data between the MaxDB and SEP sesam. | In the following example, we have created three external media for full, incremental and log backup. These are pipes that are used to transfer the data between the MaxDB and SEP sesam.</translate> | ||
'''''Syntax''''' | '''''<translate>Syntax</translate>''''' | ||
<medium_put> <medium_name> <location_type> <backup_type> [<size> [<block size> [<overwrite> [<autoloader> [<os_command> [<tool_type>]]]]]] | <translate><medium_put></translate> <translate><medium_name></translate> <translate><location_type></translate> <translate><backup_type></translate> [<translate><size></translate> [<translate><block size></translate> [<translate><overwrite></translate> [<translate><autoloader></translate> [<translate><os_command></translate> [<translate><tool_type></translate>]]]]]] | ||
'''''On Linux''''' | '''''<translate>On Linux</translate>''''' | ||
OS> dbmcli -d TST -u dbm,dbm -c medium_put BACKData /tmp/sapdb/TST/data PIPE DATA 0 8 YES YES pwd BACK | OS> dbmcli -d TST -u dbm,dbm -c medium_put BACKData /tmp/sapdb/TST/data PIPE DATA 0 8 YES YES pwd BACK | ||
OS> dbmcli -d TST -u dbm,dbm -c medium_put BACKPages /tmp/sapdb/TST/pages PIPE PAGES 0 8 YES YES pwd BACK | OS> dbmcli -d TST -u dbm,dbm -c medium_put BACKPages /tmp/sapdb/TST/pages PIPE PAGES 0 8 YES YES pwd BACK | ||
Line 164: | Line 168: | ||
OS> dbmcli -d TST -u dbm,dbm -c medium_getall # print list of defined media | OS> dbmcli -d TST -u dbm,dbm -c medium_getall # print list of defined media | ||
'''''On Windows''''' | '''''<translate>On Windows</translate>''''' | ||
The backup medium name of a type <tt>PIPE</tt> must be added to the following syntax {{path|\\.\pipe\<pipe_name>}}. For details, see [http://maxdb.sap.com/doc/7_7/45/1125da4d9e7307e10000000a1553f7/content.htm medium_put]. | <translate>The backup medium name of a type <tt>PIPE</tt> must be added to the following syntax {{path|\\.\pipe\<pipe_name>}}. For details, see [http://maxdb.sap.com/doc/7_7/45/1125da4d9e7307e10000000a1553f7/content.htm medium_put].</translate> | ||
C:\> dbmcli -d TST -u dbm,dbm -c medium_put BACKData \\.\pipe\TST-Data PIPE DATA 0 8 YES YES pwd BACK | C:\> dbmcli -d TST -u dbm,dbm -c medium_put BACKData \\.\pipe\TST-Data PIPE DATA 0 8 YES YES pwd BACK | ||
Line 173: | Line 177: | ||
C:\> dbmcli -d TST -u dbm,dbm -c medium_getall | C:\> dbmcli -d TST -u dbm,dbm -c medium_getall | ||
=== Setting the environment variable <tt>BSI ENV</tt> === | <translate>=== Setting the environment variable <tt>BSI ENV</tt> ===</translate> | ||
'''''On Linux''''' | '''''<translate>On Linux</translate>''''' | ||
OS> dbmcli -d TST -u dbm,dbm dbm_configset -raw BSI_ENV /usr/sapdb/wrk/TST/bsi.env | OS> dbmcli -d TST -u dbm,dbm dbm_configset -raw BSI_ENV /usr/sapdb/wrk/TST/bsi.env | ||
'''''On Windows''''' | '''''<translate>On Windows</translate>''''' | ||
C:\> dbmcli -d TST -u dbm,dbm dbm_configset -raw BSI_ENV | C:\> dbmcli -d TST -u dbm,dbm dbm_configset -raw BSI_ENV | ||
C:\ProgramData\sdb\globaldata\wrk\TST\bsi.env | C:\ProgramData\sdb\globaldata\wrk\TST\bsi.env | ||
=== Full backup in cold mode === | <translate>=== Full backup in cold mode ===</translate> | ||
OS> dbmcli -d TST -u dbm,dbm -c db_cold # set to cold | OS> dbmcli -d TST -u dbm,dbm -c db_cold # set to cold | ||
OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKData migration | OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKData migration | ||
=== Full backup in warm mode === | <translate>=== Full backup in warm mode ===</translate> | ||
OS> dbmcli -d TST -u dbm,dbm -c db_warm # set to warm | OS> dbmcli -d TST -u dbm,dbm -c db_warm # set to warm | ||
OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKData migration | OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKData migration | ||
=== Incremental backup === | <translate>=== Incremental backup ===</translate> | ||
OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKPages migration | OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKPages migration | ||
=== Log backup === | <translate>=== Log backup ===</translate> | ||
OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKLog | OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKLog | ||
=== Full restore === | <translate>=== Full restore === | ||
See also: https://wiki.scn.sap.com/wiki/display/MaxDB/HowTo+-+SAP+MaxDB+Recovery+with+Database+Manager+CLI | See also: https://wiki.scn.sap.com/wiki/display/MaxDB/HowTo+-+SAP+MaxDB+Recovery+with+Database+Manager+CLI</translate> | ||
OS> dbmcli -d <DBsid> -u dbm,dbm -c db_cold # set database to cold mode | OS> dbmcli -d <DBsid> -u dbm,dbm -c db_cold # <translate>set database to cold mode</translate> | ||
OS> dbmcli -d <DBsid> -u dbm,dbm -c db_admin # set database to admin mode | OS> dbmcli -d <DBsid> -u dbm,dbm -c db_admin # <translate>set database to admin mode</translate> | ||
OS> dbmcli -d <DBsid> -u dbm,dbm -uUTL # connect to the database | OS> dbmcli -d <DBsid> -u dbm,dbm -uUTL # <translate>connect to the database</translate> | ||
>backup_ext_ids_forget # should return OK, clears backup list | >backup_ext_ids_forget # <translate>should return OK, clears backup list</translate> | ||
>backup_ext_ids_get BACKData # should return OK, requests backups from server, device "BACKData" | >backup_ext_ids_get BACKData # <translate>should return OK, requests backups from server, device</translate> "BACKData" | ||
>backup_ext_ids_list # should return OK | >backup_ext_ids_list # <translate>should return OK</translate> | ||
# and displays a list of EBIDS | # <translate>and displays a list of EBIDS</translate> | ||
# use backup_ext_ids_listnext to scroll further | # <translate>use backup_ext_ids_listnext to scroll further</translate> | ||
# Format: | # <translate>Format:</translate> | ||
# Availability External Backup ID Save Type Date and Time | # <translate>Availability External Backup ID Save Type Date and Time</translate> | ||
# AVAILABLE <EBID 1> DATA MIGRATION <Date 1> | # AVAILABLE <EBID 1> DATA MIGRATION <Date 1> | ||
# use full string enclosed in | as EBID | # <translate>use full string enclosed in | as EBID</translate> | ||
>service_connect # open service connection | >service_connect # <translate>open service connection</translate> | ||
>recover_start BACKData DATA ExternalBackupID "<EBID 1>" # should return OK | >recover_start BACKData DATA ExternalBackupID "<EBID 1>" # <translate>should return OK</translate> | ||
> db_execute clear log # reset logfiles | > db_execute clear log # <translate>reset logfiles</translate> | ||
> db_warm # should return OK | > db_warm # should return OK | ||
>exit | >exit | ||
=== Consistency check of the backup with <tt>recover_check</tt> === | <translate>=== Consistency check of the backup with <tt>recover_check</tt> ===</translate> | ||
OS> dbmcli -d TST -u <ADMNAME>,<PASSWORT> -uSRV | OS> dbmcli -d TST -u <ADMNAME>,<PASSWORT> -uSRV | ||
Line 225: | Line 229: | ||
dbmcli on CER>backup_ext_ids_list | dbmcli on CER>backup_ext_ids_list | ||
'''''Example on Windows:''''' | '''''<translate>Example on Windows:</translate>''''' | ||
C:\Users\Administrator>dbmcli.exe -d MAXDB -U dbadmin1 -uSRV | C:\Users\Administrator>dbmcli.exe -d MAXDB -U dbadmin1 -uSRV | ||
Line 241: | Line 245: | ||
AVAILABLE|MAXDB MAXDB_7123782847 \\.\pipe\MAXDB-Data|DATA MIGRATION|2019-10-16 16:57:06| | AVAILABLE|MAXDB MAXDB_7123782847 \\.\pipe\MAXDB-Data|DATA MIGRATION|2019-10-16 16:57:06| | ||
This command shows a list of the respective SEP sesam savesets. The output is divided by the pipe sign (|), the second parameter includes the external backup ID: | <translate>This command shows a list of the respective SEP sesam savesets. The output is divided by the pipe sign (|), the second parameter includes the external backup ID:</translate> | ||
AVAILABLE|CER CER___6225258851 /tmp/sapdb/CER/data|DATA MIGRATION|2019-12-31 10:43:06| | AVAILABLE|CER CER___6225258851 /tmp/sapdb/CER/data|DATA MIGRATION|2019-12-31 10:43:06| | ||
Line 247: | Line 251: | ||
AVAILABLE|CER CER___6225285526 /tmp/sapdb/CER/log|LOG RECOVERY |2019-12-31 10:47:33| | AVAILABLE|CER CER___6225285526 /tmp/sapdb/CER/log|LOG RECOVERY |2019-12-31 10:47:33| | ||
The following example shows a <tt>recover_check</tt> call for the ''LOG'' backup type: | <translate>The following example shows a <tt>recover_check</tt> call for the ''LOG'' backup type:</translate> | ||
'''Call:''' | '''<translate>Call:</translate>''' | ||
dbmcli on CER>service_connect | dbmcli on CER>service_connect | ||
dbmcli on CER>recover_check <BACKUP_NAME> LOG ExternalBackupID "<BACKUP_ID>" AUTOIGNORE | dbmcli on CER>recover_check <BACKUP_NAME> LOG ExternalBackupID "<BACKUP_ID>" AUTOIGNORE | ||
'''Example:''' | '''<translate>Example:</translate>''' | ||
dbmcli on CER>recover_check BACKLog LOG ExternalBackupID "CER CER___6225285526 /tmp/sapdb/CER/log" AUTOIGNORE | dbmcli on CER>recover_check BACKLog LOG ExternalBackupID "CER CER___6225285526 /tmp/sapdb/CER/log" AUTOIGNORE | ||
OK | OK | ||
Line 282: | Line 286: | ||
Converter Page Count | Converter Page Count | ||
<div class="noprint"> | <translate><noinclude><div class="noprint"> | ||
==See also== | ==See also== | ||
[[Special:MyLanguage/SAP|SAP ERP]]</div> | [[Special:MyLanguage/SAP|SAP ERP]]</div></noinclude></translate> |
Revision as of 11:47, 10 December 2020
Overview
The MaxDB backup/restore is performed with the Database Manager CLI (dbmcli) utility, as described in the section dbmcli calls. The backint is an interface program that allows dbmcli to communicate with SAP MaxDB using pipes to perform backup and restore operations.
Requirements
To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:
- Check the support matrix for the list of supported MaxDB versions. Note that all components for setting up the MaxDB extension are already included in the SEP sesam installation packages.
- SEP sesam Server v. 4.4.3 or higher. Check Hardware requirements for SEP sesam Server, RDS or SEP sesam Client.
- Install the SAP ERP database on MaxDB v. 6.2 or 7.2.5.
- Install the SEP sesam Client package on the SAP ERP server. You can download it from SEP Download Center. The installation procedure is slightly different depending on the operating system type (Linux/Unix or Windows). For details on OS specific installation, see SEP sesam Quick Install Guide.
Installing SAP ERP on MaxDB
Before proceeding, make sure that the requirements above are met.
On Linux/Unix
Once you have downloaded your SEP sesam Linux Client on the SAP ERP server, proceed as follows:
- Unpack the tar-archive into a temporary directory. The archive contains the following files:
- backint_sapdb
- backint_sapdb.utl
- bsi.env
- Copy the backint_sapdb file to
<SESAM_ROOT>/bin/sesam
directory as a root user. This file has to be executable for the MaxDB user. You can also use a different directory. In this case, you have to adjust the configuration accordingly. - Check if the programs sbc and sbc_com_interface are executable for the MaxDB user in the directory
<SESAM DIR>/bin/sesam
. - Copy the file backint_sapdb.utl to the MaxDB <wrk_directory> (e.g.,
/usr/sapdb/indep_data/wrk/CER
, if the database DBsid is CER).
On Windows
Once you have installed your SEP sesam Windows Client on the SAP ERP server, proceed as follows:
- SEP sesam Windows Client already includes the necessary files for the MaxDB:
- backint_sapdb
- backint_sapdb.utl
- bsi.env
- The backint_sapdb.exe program is located in the directory
<SESAM ROOT>\bin\sesam
. You can copy it to a different directory, e.g., the MaxDB bin directory. In this case, you have to adjust the configuration accordingly. - Copy the files backint_ sapdb.utl and bsi.env from the directory
<SESAM ROOT>/skel/
to the MaxDB <wrk_ directory> (e.g.,C:\Program Files\sapdb\indep_data\wrk\CER
, if the database DBsid is CER).
Configuration on SEP sesam Server
After you have installed SAP ERP on MaxDB, proceed as follows:
- Configure your SAP ERP as a SEP sesam client by adding it to the SEP sesam environment: Main Selection -> Components -> Topology -> New Client -> add your SAP ERP client. For details, see Configuring Clients.
- Additionally, you have to create at least one backup task for the SAP ERP server with the MaxDB task type. Note that the entry for source can be specified freely. For details, see Creating a Backup Task.
Note | |
This task cannot be used for regular Path backups. It is recommended that you configure more dedicated tasks, e.g., to distinguish database backups from archive log backups. Which data is actually backed up depends on the respective SAP ERP backup call. |
Configuration on the SEP sesam SAP ERP MaxDB client
In order for MaxDB to be able to use the SEP sesam backint_sapdb program, you have to adjust the following entries in the profile file (default: <wrk_directory>/bsi.env
):
- BACKINT = <full path of the backint_sapdb program>
- INPUT = <full path of the input file>
- This file is used by the MaxDB server to communicate with the backint program.
- OUTPUT = <full path of the output file>
- This file is used by the MaxDB server to communicate with the backint program.
- ERROROUTPUT = <full path of the error file>
- Contains the error messages of the backint program.
- PARAMETERFILE = <full path of the parameter file which will be used>
- In this file the SEP sesam specific parameters are adjusted.
- CHECK_AVAILABILITY <number>BACKUPS
- Number of the old backups queried during restore.
For details, see Creating the Configuration File for Backint for SAP MaxDB and Example of a Configuration File for Backint for SAP MaxDB.
Example of a bsi.env file:
On Linux
BACKINT /opt/sesam/bin/sesam/backint_sapdb INPUT /tmp/infile4sapdb OUTPUT /tmp/outfile4sapdb ERROROUTPUT /tmp/backint4sapdb.err PARAMETERFILE /usr/sapdb/indep_data/wrk/CER/backint_CER.utl TIMEOUT_SUCCESS 600 TIMEOUT_FAILURE 300 # ORIGINAL_RUNDIRECTORY /opt/SAPDB/wrk/P1 CHECK_AVAILABILITY 20BACKUPS
On Windows
BACKINT "C:\Program Files\SEPsesam\bin\sesam\backint_sapdb.exe" INPUT C:\temp\CER_sapdb.in OUTPUT C:\temp\CER_sapdb.out ERROROUTPUT C:\temp\CER_backint4sapdb.err PARAMETERFILE C:\ProgramData\sdb\globaldata\wrk\P1\backint_CER.utl TIMEOUT_SUCCESS 600 TIMEOUT_FAILURE 300 # ORIGINAL_RUNDIRECTORY C:\ProgramData\sdb\globaldata\wrk\P1 CHECK_AVAILABILITY 20BACKUPS
Note | |
|
You can create several profile files. They are declared to the MaxDB by setting the environment variable BSI ENV.
Example for setting the environment variable BSI ENV:
dbmcli -d CER -u dbm,dbm dbm_configset -raw BSI_ENV /usr/sapdb/indep_data/wrk/CER/bsi.env
You can set different values for PARAMETERFILE in the respective profile files; for example, to use different media pools.
You have to configure at least the following parameters in the PARAMETERFILE:
- SESAM_SERVER = <SEP_sesam_Server>
- The name of the SEP sesam Server.
- SESAM_JOB = <SEP sesam SAP MaxDB client task>
- The name of the SEP sesam backup task which you have configured before. For details, see section above Configuration on SEP sesam Server.
- SESAM_DRIVE=<SEP_sesam_drive_number>
- The number of the SEP sesam drive that you want to use for backup.
- SESAM_POOL=<SEP sesam media pool>
- The name of the SEP sesam media pool that you want to use for backup.
- SSB_LOGFILE=<log_file_name>
- Full path of the SEP sesam backint log file.
Optionally, set the additional parameters:
- SBC=<SEP_sesam_path>
- Full path of the SEP sesam backup program. It only has to be set if the standard sbc cannot be used.
- PORT=<SEP_sesam_Server_communication_port>
- Only required if the STPD port was changed during the SEP sesam Server installation.
- SESAM_TAPESERVER=<Remote_device_server>
- IP name of the RDS for backup. By using this entry you can specify the backup net.
Example of a parameter (.utl) file:
On Linux
SESAM_SERVER=seplinux SESAM_JOB=lxsap01_SAP SESAM_DRIVE=2 SESAM_POOL=fullpool SSB_LOGFILE=/sapdb/data/wrk/CER/backint_CER.log
On Windows
SESAM_SERVER=seplinux SESAM_JOB=win03_SAP SESAM_DRIVE=2 SESAM_POOL=fullpool SSB_LOGFILE=C:\ProgramData\sdb\globaldata\wrk\CER\backint_CER.log
SAP ERP log files on MaxDB
The following log files are written by the individual SAP ERP backup modules in the MaxDB <wrk_ directory> (e.g., /sapdb/data/wrk/CER
or /usr/sapdb/indep_ data/wrk/CER
, if the database DBsid is CER).
- backint, sbc, and sbc_com_interface
- The programs backint_sapdb, sbc and sbc_com_interface write in the log file which was set during the configuration of the SSB LOGFILE entry in the parameter file, e.g.,
/sapdb/data/wrk/CER/backint_CER.log
.
- dbmcli
- The MaxDB dbmcli program writes its log files into the work directory, e.g.,
/sapdb/data/wrk/CER/dbm.ebp
.
dbmcli calls
MaxDB backup and restore commands can be invoked with the Database Manager CLI dbmcli program. The dbmcli is included in the MaxDB software. For details on DBM commands, see MaxDB documentation.
Example
In the following example, we have created three external media for full, incremental and log backup. These are pipes that are used to transfer the data between the MaxDB and SEP sesam.
Syntax
<medium_put> <medium_name> <location_type> <backup_type> [<size> [<block size> [<overwrite> [<autoloader> [<os_command> [<tool_type>]]]]]]
On Linux
OS> dbmcli -d TST -u dbm,dbm -c medium_put BACKData /tmp/sapdb/TST/data PIPE DATA 0 8 YES YES pwd BACK OS> dbmcli -d TST -u dbm,dbm -c medium_put BACKPages /tmp/sapdb/TST/pages PIPE PAGES 0 8 YES YES pwd BACK OS> dbmcli -d TST -u dbm,dbm -c medium_put BACKLog /tmp/sapdb/TST/log PIPE LOG 0 8 YES YES pwd BACK OS> dbmcli -d TST -u dbm,dbm -c medium_getall # print list of defined media
On Windows
The backup medium name of a type PIPE must be added to the following syntax \\.\pipe\<pipe_name>
. For details, see medium_put.
C:\> dbmcli -d TST -u dbm,dbm -c medium_put BACKData \\.\pipe\TST-Data PIPE DATA 0 8 YES YES pwd BACK C:\> dbmcli -d TST -u dbm,dbm -c medium_put BACKPages \\.\pipe\TST-Pages PIPE PAGES 0 8 YES YES pwd BACK C:\> dbmcli -d TST -u dbm,dbm -c medium_put BACKLog \\.\pipe\TST-Log PIPE LOG 0 8 YES YES pwd BACK C:\> dbmcli -d TST -u dbm,dbm -c medium_getall
Setting the environment variable BSI ENV
On Linux
OS> dbmcli -d TST -u dbm,dbm dbm_configset -raw BSI_ENV /usr/sapdb/wrk/TST/bsi.env
On Windows
C:\> dbmcli -d TST -u dbm,dbm dbm_configset -raw BSI_ENV C:\ProgramData\sdb\globaldata\wrk\TST\bsi.env
Full backup in cold mode
OS> dbmcli -d TST -u dbm,dbm -c db_cold # set to cold OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKData migration
Full backup in warm mode
OS> dbmcli -d TST -u dbm,dbm -c db_warm # set to warm OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKData migration
Incremental backup
OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKPages migration
Log backup
OS> dbmcli -d TST -u dbm,dbm -uUTL -c backup_start BACKLog
Full restore
See also: https://wiki.scn.sap.com/wiki/display/MaxDB/HowTo+-+SAP+MaxDB+Recovery+with+Database+Manager+CLI
OS> dbmcli -d <DBsid> -u dbm,dbm -c db_cold # set database to cold mode OS> dbmcli -d <DBsid> -u dbm,dbm -c db_admin # set database to admin mode OS> dbmcli -d <DBsid> -u dbm,dbm -uUTL # connect to the database >backup_ext_ids_forget # should return OK, clears backup list >backup_ext_ids_get BACKData # should return OK, requests backups from server, device "BACKData" >backup_ext_ids_list # should return OK # and displays a list of EBIDS # use backup_ext_ids_listnext to scroll further # Format: # Availability External Backup ID Save Type Date and Time # AVAILABLE <EBID 1> DATA MIGRATION <Date 1> # use full string enclosed in | as EBID >service_connect # open service connection >recover_start BACKData DATA ExternalBackupID "<EBID 1>" # should return OK > db_execute clear log # reset logfiles > db_warm # should return OK >exit
Consistency check of the backup with recover_check
OS> dbmcli -d TST -u <ADMNAME>,<PASSWORT> -uSRV dbmcli on CER>backup_ext_ids_get <BACKUPNAME> # e.g. BACKLog dbmcli on CER>backup_ext_ids_list
Example on Windows:
C:\Users\Administrator>dbmcli.exe -d MAXDB -U dbadmin1 -uSRV dbmcli.exe on MAXDB>backup_ext_ids_get BACKData OK --- C:\Program Files\sdb\MaxDB\pgm\dbmcli.exe on MAXDB>backup_ext_ids_list OK END AVAILABLE|MAXDB MAXDB_7115418748 \\.\pipe\MAXDB-Data|DATA MIGRATION|2019-10-15 17:43:05| AVAILABLE|MAXDB MAXDB_711542630 \\.\pipe\MAXDB-Data|PAGES MIGRATION|2019-10-15 17:44:21| AVAILABLE|MAXDB MAXDB_7123701371 \\.\pipe\MAXDB-Data|DATA MIGRATION|2019-10-16 16:43:31| AVAILABLE|MAXDB MAXDB_712375260 \\.\pipe\MAXDB-Data|PAGES MIGRATION|2019-10-16 16:52:04| AVAILABLE|MAXDB MAXDB_7123782847 \\.\pipe\MAXDB-Data|DATA MIGRATION|2019-10-16 16:57:06|
This command shows a list of the respective SEP sesam savesets. The output is divided by the pipe sign (|), the second parameter includes the external backup ID:
AVAILABLE|CER CER___6225258851 /tmp/sapdb/CER/data|DATA MIGRATION|2019-12-31 10:43:06| AVAILABLE|CER CER___6225271628 /tmp/sapdb/CER/pages|PAGES MIGRATION|2019-12-31 10:45:14| AVAILABLE|CER CER___6225285526 /tmp/sapdb/CER/log|LOG RECOVERY |2019-12-31 10:47:33|
The following example shows a recover_check call for the LOG backup type:
Call: dbmcli on CER>service_connect dbmcli on CER>recover_check <BACKUP_NAME> LOG ExternalBackupID "<BACKUP_ID>" AUTOIGNORE Example: dbmcli on CER>recover_check BACKLog LOG ExternalBackupID "CER CER___6225285526 /tmp/sapdb/CER/log" AUTOIGNORE OK Returncode 0 Date 20091231 Time 00110347 Server qslxmax01 Database CER Kernel Version Kernel 7.7.06 Build 009-121-202-944 Pages Transferred 312 Pages Left 0 Volumes 1 Medianame BACKLog Location /tmp/sapdb/CER/log Errortext Label LOG_000000001 Is Consistent First LOG Page 0 Last LOG Page 349 DB Stamp 1 Date 20091230 DB Stamp 1 Time 00111532 DB Stamp 2 Date 20091231 DB Stamp 2 Time 00104514 Page Count 291 Devices Used 1 Database ID qslxmax01:CER_20091231_104306 Max Used Data Page Converter Page Count