BRARCHIVE/BRRESTORE Messages

Msg-#

Message/Meldung

Note

LFM001

<string>

Any string is printed.

 

<string>

 

LFM002

<string1> v<string2>

Tool <string1> version

   

message.

 

<string1> v<string2>

 

LFM003

Log file processing (<string>)

Tool success!

 

terminated successfully.

 
 

Log-Datei Verarbeitung (<string>)

 
 

erfolgreich beendet.

 

LFM004

Log file processing (<string>)

Tool terminated with

 

terminated with warnings.

warnings. Please check

   

previous messages

 

Log-Datei Verarbeitung (<string>)

 
 

beendet mit Warnungen

 

LFM005

Log file processing (<string>)

Tool terminated with

 

terminated with errors.

errors. Please check

   

previous messages

 

Log-Datei Verarbeitung (<string>)

 
 

endete mit Fehlern.

 

LFM006

Start of log file processing:

Printed at log file process-

 

<string1> <string2> <string3>

ing start. <string1> is the

   

encrypted timestamp,

 

Start der Log-Datei-Verarbeitung:

<string2> is a function id,

 

<string1> <string2> <string3>

<string3> is the starttime

LFM007

End of log file processing:

Printed at log file process-

 

<string> <string> <string>

ing end. <string1> is the

   

encrypted timestamp,

 

Ende der Log-Datei-Verarbeitung:

<string2> is a function id,

 

<string> <string> <string>

<string3> is the endtime

LFM008

Log file processing for database:

Prints out database for

 

<string>

which log file processing is

 

performed

 

Log-Datei-Verarbeitung fuer Datenbank:

 
 

<string>

 

LFM009

Unable to build list of log files

This message appears when an

 

to be processed.

log file to process does not

   

exist or an unexpected

 

Liste der zu verarbeitenden

failure occurs while access-

Log-Dateien kann nicht erstellt werden.

ing log file management data

   

in the admin database.

   

Check previous messages!

LFM010

Log file <string> already deleted.

An already archived log file

   

that is to be deleted cannot

 

Log-Datei <string> bereits geloescht.

be found.

LFM011

<number1> Log file(s) found for

Informational message on the

 

processing, total size <number2>MB.

number of log files found

   

for processing and their

<number1> Log-Datei(en) zum Verarbeiten

size (in MB)

gefunden, Gesamtgroesse <number2> MB.

 

LFM013

No log files found for processing.

Check previous messages if

   

this is an error or just

 

Keine Log-Dateien zum Verarbeiten

informational

 

gefunden.

 

LFM014

<number1> of <number2> log file(s)

Progress indicator.

 

processed - <number3> MB of

 
 

<number4> MB done.

 
 

<number1> von <number2> Log-Datei(en)

 
 

verarbeitet - <number3> MB von

 
 

<number4> MB fertig.

 

LFM015

Log file <string> deleted.

Log file deletion message

 

Log-Datei <string> geloescht.

 

LFM016

<number> log file(s) processed.

Number of processed log

   

files (informational)

 

<number> Log-Datei(en) verarbeitet.

 

LFM017

Log file <string> not found.

A log file was not found

   

in the expected location.

 

Log-Datei <string> nicht gefunden.

Therefore it is not

   

manageable for the DB2admin

   

tool any more! The log file

   

may have been manually

   

touched before.

   

Ensure that this will not

   

the affect SAP R/3 database

   

recoverability.

LFM019

Volume size limit reached - no more

The sum of the processed

 

log files will be processed.

log files' sizes is greater

   

than the tape_size parameter

 

Datentraeger-Groesse erreicht - keine

specifed in the SAP-DB2admin

 

weiteren Log-Dateien werden verarbeitet.

"Options" dialog.

   

Check if its value is ok.

LFM020

Program already running or was killed.

You cannot run this program

   

more than once.

 

Programm laeuft gerade oder wurde

If the program terminated

 

abgebrochen.

abnormally there may still

   

be a lock set. Therefore

   

remove the '.lock' file in

   

-/db2/<SID>/saparch

   

for log file archiving

   

-/db2/<SID>/saprest

   

for log file restoring

LFM021

Please delete the file <string> if

You cannot run this program

 

log file management tool was killed.

more than once.

   

If the program terminated

 

Bitte die Datei <string> loeschen, wenn

abnormally there may still

 

Log-Datei-Verarbeitung abgebrochen wurde.

be a lock set. Therefore

   

remove the file <string> in

   

-/db2/<SID>/saparch

   

for log file archiving

   

-/db2/<SID>/saprest

   

for log file restoring

LFM022

Setting execution lock failed.

see messages LFM020 and

   

LFM021

 

Setzen von Ausfuehrungs-Sperre

 
 

gescheitert.

 

LFM024

The log file <string> is already

In case of restoring a log

 

available.

file from an archive no

 

No restoring necessary!

processing is neccessary

   

because the log file is

 

Die Log-Datei <string> ist bereits

already available in the

 

verfuegbar

expected/requested location.

 

(kein Restore notwendig!).

 

LFM071

Saved <string1> on <string2> at position

Confirmation that a log file

 

<number>.

<string1> has been saved on

   

tape <string2> at tape

 

<string1> auf <string2> an Position

position <number>

 

<number> gespeichert.

 

LFM072

Restored <string1> from <string2> at

Confirmation that a log file

 

position <number>.

<string1> has been restored

   

from tape <string2> (tape

 

<string1> aus <string2> von Position

position <number>)

 

<number> zurueckgesichert.

 

LFM097

Parameter <string>:<number>

Setting of numeric

   

processing parameter

 

Parameter <string>:<number>

<string>

LFM098

Parameter <string1>:<string2>

Reports setting of textual

   

processing parameter

 

Parameter <string1>:<string2>

<string1>

LFM100

Internal error at locatation

Reports internal processing

 

<string>-<number>.

error the specified location

   

in the program source file.

 

Interner Fehler an der Stelle

This could be an unhandled

 

<string>-<number>.

and unexpected error

   

returned by a C function.

LFM102

Following backup device will be used:

Informational.

<string>

 
 

Folgendes Sicherungs-Geraet wird

 
 

benutzt: <string>

 

LFM103

Following backup volume will be used:

The backup volume <string>

 

<string>

is one out of the list of

   

volumes specified in the

 

Folgender Sicherungs-Datentraeger wird

SAP-DB2admin Option

 

benutzt: <string>

'tape_pool'.

LFM104

<number> scratch volume will be used.

If "SCRATCH" is specified as

 

the 'tape_pool' parameter

 
 

<number> Scratch-Datentraeger wird

in SAP-DB2admin: Options

 

benutzt.

then always SCRATCH is used

 

as volume name

 

LFM105

<number> free backup volume(s) found,

SAP-DB2admin checks for the

 

<number> required.

next free volume to use for

   

log file archiving. This

 

<number> freie(r) Sicherungs-Datentraeger

message appears if none can

 

gefunden, <number> erforderlich.

be found.

   

Check if a new tape should

   

be used (initialize first).

LFM109

Files will be saved to ADSM.

Informational.

 

Dateien werden ins ADSM gesichert.

 

LFM112

Files will not be compressed.

Informational.

   

Compression currently not

Dateien werden nicht komprimiert.

supported.

LFM121

Processing of the protocol file <string>

The protocol file records

 

failed.

all steps of a log file

   

management process.

 

Verarbeiten der Protokolldatei <string>

For the failure cause check

 

gescheitert.

previous messages.

LFM124

Query option set - no processing.

Informational.

 

Abfrage-Option gesetzt -

 
 

keine Verarbeitung.

 

LFM126

Unattended mode active - no confirmation

Informational.

 

required.

Attended mode is currently

   

not supported.

 

Unbeaufsichtigter Modus aktiv - keine

 
 

Bestaetigung erforderlich.

 

LFM129

Force option set - no label checking

Be sure that you really want

 

during initialization.

to init the tape without

   

checking wether it is

 

Force-Option gesetzt - keine Kennsatz-

already in use and therefore

Pruefung bei Initialisierung.

not available for re-init.

LFM130

Archive device type: <string>

Tape or ADSM are currently

   

supported.

 

Sicherungs-Geraetetyp: <string>

 

LFM131

All volumes get the name SCRATCH.

This informational message

   

appears when the parameter

 

Alle Datentraeger bekommen den Namen

'tape_pool' in the

 

SCRATCH.

SAP-DB2admin Options is set

   

to scratch.

LFM132

Show option set - volume label will be

Informational.

 

displayed.

 
 

Show-Option gesetzt - Datentraeger-

 
 

Kennsatz wird angezeigt.

 

LFM133

Label of volume in device <string>:

Informational.

 

Kennsatz von Datentraeger in Geraet

 
 

<string>:

 

LFM135

Query with check option set -

Informational!

 

no processing.

Work to be performed and

   

preconditions are checked.

 

Abfrage-mit-Pruefung-Option gesetzt -

 
 

keine Verarbeitung.

 

LFM151

No valid log file management option specified (‘-s’, ‘-i’,...)

An action to be performed by the log file management tools has to be specified. If this message occurs in SAP-DB2admin, contact SAP.

 

Keine gueltige Option zur Log-Datei-Verwaltung angegeben (‘-s’, ‘-i’,...)

 

LFM152

Environment variable <string> is not set.

In some cases processing

   

continues because a default

 

Umgebungsvariable <string> ist nicht

value is applied. In other

 

gesetzt.

cases the variable must be

   

set first.

LFM153

Unknown option '<string>' found at

If the affected tool has

 

position <number>.

been called manually then

   

re-enter the call string

 

Unbekannte Option '<string>' an der

with correct syntax.

 

Stelle <number> gefunden.

If this error occurs during

   

processing of the

   

SAP-DB2admin tool then this

   

should be reported to SAP

   

as an error.

LFM154

Unexpected option value '<string>'

If the affected tool has

 

found at position <number>.

been called manually then

   

re-enter the call string

 

Unerwarteter Optionswert '<string>'

with correct syntax.

 

an der Stelle <number> gefunden. If this error occurs during

 
   

processing of the

   

SAP-DB2admin tool then this

   

should be reported to SAP

   

as an error.

LFM155

No value found for option <string>.

More data was expected for

   

option <string>.

 

Kein Wert fuer Option <string> gefunden.

If the affected tool has

   

been called manually then

   

re-enter the call string

   

with correct syntax.

   

If this error occurs during

   

processing of the

   

SAP-DB2admin tool then this

   

should be reported to SAP

   

as an error.

LFM156

Illegal value '<string>' found for

More data was expected for

 

option <string>.

option <string>.

   

If the affected tool has

 

Illegaler Wert '<string>' fuer Option

been called manually then

 

<string> gefunden.

re-enter the call string

   

with correct syntax.

   

If this error occurs during

   

processing of the

   

SAP-DB2admin tool then this

   

should be reported to SAP

   

as an error.

LFM157

Value '<string>' for option <string>

If the affected tool has

 

longer than <number> characters.

been called manually then

   

re-enter the call string

 

Wert '<string>' fuer Option <string>

with matching format.

 

laenger als <number> Zeichen.

If this error occurs during

   

processing of the

   

SAP-DB2admin tool then this

   

should be reported to SAP

   

as an error.

LFM159

Error reading configuration parameter

 
 

'<string>' from admin database '<string>'

 
 

Fehler beim Lesen des

 
 

Konfigurationsparameters '<string>'

 
 

aus DB '<string>'

 

LFM164

Illegal value '<string1>' found for

Check in SAP-DB2admin:

 

parameter <string2>.

Options and correct the

   

parameter <string2>

 

Illegaler Wert '<string1>' fuer

 
 

Parameter <string2> gefunden.

 

LFM165

Parameter <string1> is not set in

Parameter <string1> is not

 

<string2>

set though it is required.

   

Check in SAP-DB2admin:

 

Parameter <string1> ist nicht gesetzt in

Options and set it in the

 

<string2>

admin database <string2>

LFM169

Value '<string>' of parameter <string>

It is recommended that you

 

ignored - '<string>' assumed.

check the cause for this

   

message. However, processing

 

Wert '<string>' von Parameter <string>

will continue.

 

wird ignoriert - '<string>' angenommen.

 

LFM170

Value of parameter <string> should be

Check <string> in

 

enclosed in double quotes.

SAP-DB2admin: Options and

   

correct it.

 

Wert des Parameters <string> sollte in

 
 

Anfuehrungszeichen stehen.

 

LFM171

Value '<string1>' of parameter <string2>

Check <string2> in call

 

longer than <number> characters.

parameters or in the

   

SAP-DB2admin: Options and

 

Wert '<string1>' fuer Parameter <string2>

correct it.

 

laenger als <number> Zeichen.

It the message is caused by

   

an incorrect call string

   

during SAP-DB2admin

   

processing then report it

   

to SAP.

LFM174

Dollar character missing.

Correct in SAP-DB2admin:

   

Options.

 

Dollar-Zeichen fehlt.

 

LFM175

Character 'K' or 'M' should directly

K(=Kilobyte) or M(=Megabyte)

 

follow volume size.

must be specified.

   

Correct in SAP-DB2admin:

 

Zeichen 'K' oder 'M' sollte direkt

Options.

 

der Datentraeger-Groesse folgen.

 

LFM180

Backup devices with and without rewind

Hint: for AIX with rewind

 

have the same address.

should be similar to

   

'/dev/rmt0' and without

 

Sicherungs-Geraete mit und ohne rewind

rewind '/dev/rmt0.1'.

 

haben die gleiche Adresse.

Correct in SAP-DB2admin:

 

Options.

 

LFM202

Saving <string>

Informational.

 

Sicherung von <string>

 

LFM203

to <string>...

Informational.

 

auf <string>...

 

LFM204

Percentage done: <number>%, estimated

Informational.

 

end time: <hours>:<minutes>

 
 

Prozentsatz fertig: <number>%, geschaetzte

 
 

Endzeit: <Stunden>:<Minuten>

 

LFM205

Backup volume initialization.

Informational.

 

Sicherungs-Datentraeger-Initialisierung.

 

LFM206

End of backup volume initialization.

Informational.

 

Ende der Sicherungs-Datentraeger-

 
 

Initialisierung.

 

LFM207

Volume in device '<string1>' will be

Informational.

 

initialized with name '<string2>'

 
 

Datentraeger in Einheit '<string1>' wird

 
 

initialisiert mit Namen '<string2>'

 

LFM208

Volume with name <string1> required

Informational.

 

in device <string2>

 
 

Datentraeger mit Namen <string1>

 
 

erforderlich in Geraet <string2>

 

LFM209

Volume in device <string1> has label

Informational.

<string2>

 
 

Datentraeger in Einheit <string1> hat

 
 

Label <string2>

 

LFM210

Volume in device <string> has no label.

Volume has to be initialized before it can be used for log file management. Informational!

 

Datentraeger in Einheit <string> hat kein Label.

 

LFM212

Please check the volume or the device!

A tape volume may not be

   

inserted into the device.

 

Pruefen Sie bitte den Datentraeger oder

Check the device.

 

das Geraet!

 

LFM213

Rewind of volume in device <string>

For more details look at

 

failed.

previous messages.

 

Spulen von Datentraeger in Geraet <string>

 
 

gescheitert.

 

LFM214

Label on volume in device <string> not

Check if the correct tape

 

found.

volume is entered.

   

The tape should have been

 

Kennsatz auf Datentraeger in Geraet

previously initialized for

 

<string> nicht gefunden.

log file archiving:

   

SAP-DB2admin:Tape Management

LFM215

Label on volume in device <string> has

Check if the correct tape

 

wrong format.

volume is entered.

   

The tape should have been

 

Kennsatz auf Datentraeger in Geraet

previously initialized for

 

<string> hat falsches Format.

log file archiving:

   

SAP-DB2admin:Tape Management

LFM216

Wrong volume <string1> in device

Check if the correct tape

<string2>, should be: <string2>

volume is entered.

 

Falscher Datentraeger <string1> in Geraet

 
 

<string1>, sollte sein: <string3>

 

LFM217

Lock period for volume <string1> in

Tape must not be used at

 

device <string2> not expired.

this time. You may want to

   

reuse it anyhow - then first

 

Sperrfrist fuer Datentraeger <string1>

initialize the tape again

 

in Geraet <string2> nicht abgelaufen.

(using 'force'-option)

LFM218

Checking label on volume in device

Check previous messages for

 

<string> failed.

more details.

 

Kennsatz-Pruefung auf Datentraeger in

 
 

Geraet <string> gescheitert.

 

LFM219

Initialization of volume <string> in

Check previous messages for

 

device <string> failed.

more details.

 

Initialisierung von Datentraeger <string>

 
 

in Geraet <string> gescheitert.

 

LFM220

Volume in device <string> is write

Check the tape medium and

 

protected!

remove the protection

   

facility.

 

Datentraeger in Geraet <string> ist

 
 

schreibgeschuetzt!

 

LFM221

Writing volume label to <string> failed.

Check previous messages for

   

more details.

 

Schreiben des Datentraeger-Labels

 
 

auf <string> gescheitert.

 

LFM222

Copying <string1> to/from <string2> failed

Check previous messages for

 

due to previous errors.

more details.

 

Kopieren von <string1> auf/von <string2>

 
 

gescheitert aufgrund frueherer Fehler.

 

LFM227

Not enough disk space in <string>.

Either free space in

 

Available: <number1> MB; needed: <number2>

<string> or set the

 

MB.

DB2DB6_RETRIEVE_PATH to

   

a directory with enough

 

Nicht genug Plattenplatz in <string>.

free space.

 

Verfuegbar <number1> MB; benoetigt:

 
 

<number2> MB.

 

LFM229

Starting ADSM-access for data transfer

Informational.

 

Starte ADSM-Zugriff fuer Datentransfer

 

LFM230

ADSM data transfer ended successfully.

Informational.

 

ADSM-Datentransfer erfolgreich beended.

 

LFM231

ADSM data transfer failed.

Check previous messages.

   

Also refer to ADSM manuals.

 

ADSM Datentransfer gescheitert.

 

LFM232

<number> of <number> file(s) saved by

Informational.

 

ADSM backup process.

 
 

<number> von <number> Datei(en) durch

 
 

ADSM Backup-Vorgang gesichert.

 

LFM233

Error in ADSM backup process while

Check previous messages.

 

saving file <string>

Backup processing will end.

 

Fehler in ADSM Backup-Vorgang bei

 
 

Sicherung der Datei <string>

 

LFM234

Tape has to be initialized prior to usage.

Use SAP-DB2admin to initialize the tape first.

 

Band muss vor Benutzung initialisiert werden.

 

LFM235

Recommended number of usages of volume

Initailize a new tape with

 

<string> exceeded.

the label <string>.

   

Continuing to use this tape

 

Empfohlene Anzahl der Benutzungen von

will increas the danger of

 

Datentraeger <string> ueberschritten.

loss of data.

LFM236

Perhaps volume initialization with option

In SAP-DB2admin: Tape

 

'<string>' required.

Management perform tape

   

initialization using

 

Vielleicht Datentraeger-Initialisierung

the 'force' option.

 

mit Option '<string>' erforderlich.

 

LFM237

Scratch volume required in device

Ensure this if 'SCRATCH'

 

<string>

is specified in the

   

SAP-DB2admin: Options

 

Scratch-Datentraeger erforderlich

'tape_pool' parameter.

 

in Geraet <string>

 

LFM238

cpio continuation volume required

Informational.

 

in device <string>

 
 

cpio-Fortsetzungs-Datentraeger

 
 

erforderlich in Geraet <string>

 

LFM239

No label checking on cpio

Informational.

 

continuation volume.

 
 

Keine Kennsatz-Pruefung auf

 
 

cpio-Fortsetzungs-Datentraeger.

 

LFM240

Less data backed up than the size of

Check previous messages.

 

file <string>

 
 

Weniger Daten gesichert als die Groesse

 
 

der Datei <string>

 

LFM241

Checking label on volume in device

Informational.

 

<string>

 
 

Kennsatz-Pruefung auf Datentraeger in

 
 

Geraet <string>

 

LFM242

Scratch volume in device <string1> will

Informational.

 

be renamed to <string2>

 
 

Scratch-Datentraeger in Geraet <string1>

 
 

wird umbenannt in <string2>

 

LFM243

Log file <string1> is on archive <string2> (Type <string3>). Expected archive <string4>!

Further processing depends on the context. So check for further messages.

 

Log-Datei <string1> befindet sich im Archiv <string2> (Typ <string3>). Archiv <string4> erwartet!

 

LFM244

Resubmit restore for log file <string> with correct archive!

Processing will continue. However, restart the restore process with the correct archive specification.

 

Restore fuer Log-Datei <string> bitte mit korrektem Archiv erneut starten!

 

LFM245

Log file <string> is not archived on any tape. Check other archives!

Processing will continue. However, the log file will not be restored in this process. This can be done later on by specifying the correct archive.

 

Log-Datei <string> wurde nicht auf Band archiviert, sondern evtl. in einem anderen Archiv!

 

LFM251

Function <string1> failed at location

Internal processing error.

 

<string2>:<string3>

Check the previous messages

   

and check if you or your

 

Funktion <string1> gescheitert an der

system administrtor can

 

Stelle <string2>:<string3>

solve the problem. Otherwise

   

report to SAP.

LFM252

Function <string1> failed for '<string2>'

Internal processing error.

 

at location <string3>:<string4>

Check the previous messages

   

and check if you or your

 

Funktion <string1> gescheitert fuer

system administrtor can

 

'<string2>' an der Stelle

solve the problem. Otherwise

 

<string3>:<string4>

report to SAP.

LFM253

errno <number>: <string>

Internal error number.

 

errno <number>: <string>

 

LFM254

Memory allocation of <number> bytes

Try again. If the problem

 

failed at location <string1>:<string2>

persists please report

   

the problem to SAP.

 

Speicheranforderung von <number> Bytes

 
 

gescheitert an der Stelle

 
 

<string1>:<string2>

 

LFM261

Program canceled by signal <number>!

Any internal condition

   

(probably program error)

 

Programm durch Signal <number>

caused a signal. Report to

 

abgebrochen!

SAP.

LFM265

Execution of program '<string>' failed.

External program cannot be

   

executed.

 

Ausfuehrung des Programms '<string>'

Check previous messages.

 

gescheitert.

 

LFM266

Program '<string>' interrupted, exit

External program terminated

 

status: <number>

due to an interrupt.

   

Check previous messages.

 

Programm '<string>' unterbrochen, exit

 
 

status: <number>

 

LFM267

Asynchronous execution of program failed.

Check for previous messages.

 

Asynchrone Ausfuehrung eines Programms

 
 

gescheitert.

 

LFM268

Asynchronous execution of program

Check for previous messages.

 

interrupted, exit status: <number>

 
 

Asynchrone Ausfuehrung eines Programms

 
 

unterbrochen, exit status: <number>

 

LFM270

Unknown process with ID <number>

Ignore this message.

 

terminated.

 
 

Unbekannter Prozess mit ID <number>

 
 

beendet.

 

LFM271

Read from a pipe failed for '<string>'

The output of an external

   

program <string> cannot be

 

Lesen von einer Pipe gescheitert fuer

read through the pipe.

 

'<string>'

Check for previous messages.

LFM272

Execution of program '<string>' through

Check for previous messages.

 

pipe failed.

 
 

Ausfuehrung des Programms '<string>' ueber

 
 

pipe gescheitert.

 

LFM273

Determination of file status for <string>

File status could not be

 

failed.

determined due to previous

   

errors.

 

Ermittlung von Dateistatus fuer <string>

 
 

gescheitert.

 

LFM274

File <string> not found.

Check on your file system

   

for probable reasons.

 

Datei <string> nicht gefunden.

 

LFM275

File <string> is not a regular file.

If <string> seems to be a

   

corrupted file name contact

 

Datei <string> ist keine normale Datei.

SAP. Otherwise check your

   

file system.

LFM276

File/directory <string> is empty.

 
 

Datei/Verzeichnis <string> ist leer.

 

LFM278

Command output of '<string>':

Informational.

 

Kommando-Ausgabe von '<string>':

 

LFM279

Return code from '<string>': <number>

Check for previous messages.

   

Informational.

 

Return-Code von '<string>': <number>

 

LFM281

Program interrupted by signal <number>.

Check for previous messages.

 

Programm durch Signal <number>

 
 

unterbrochen.

 

LFM282

Directory <string> not found.

 
 

Verzeichnis <string> nicht gefunden.

 

LFM283

Command/Output buffer overflow.

Report this to SAP.

   

An output string was too

 

Kommando-/Ausgabepuffer uebergelaufen.

long to continue processing

LFM288

Error <number> recording action start in

Check for previous messages.

 

<string>

Also check if the config

   

database ADM<SID> can be

 

Fehler <number> beim Protokollieren des

accessed (by a manual

 

Aktions-Beginns in <string>

connect statement)

LFM289

Unable to retrieve list of log files from

Check for previous messages.

 

location '<string>' with status

Also check if the config

 

'<string>'.

database ADM<SID> can be

   

accessed (by a manual

 

Fehler beim Ermitteln der Liste der Log-

connect statement)

 

Dateien aus Lokation '<string>' mit Status

 
 

'<string>'.

 

LFM290

Could not put log file '<string>' (ID =

Check for previous messages.

 

<number>) to location <number>

Also check if the config

 

(state <string>).

database ADM<SID> can be

   

accessed (by a manual

 

Log-Datei '<string>' (ID = <number>)

connect statement)

 

konnte nicht in Lokation <number> (Status

 
 

<string>) gebracht werden.

 

LFM291

Could not get object ID of log file

Check for previous messages.

 

'<string>'.

Also check if the config

   

database ADM<SID> can be

 

Objekt-ID von Log-Datei '<string>'

accessed (by a manua

 

konnte nicht ermittelt werden.

connect statement)

LFM292

Could not set column '<string>' in

Check for previous messages.

 

table '<string>' for object '<number>'

Also check if the config

   

database ADM<SID> can be

 

Spalte '<string>' in Tabelle '<string>'

accessed (by a manual

 

konnte fuer Objekt '<number>' nicht

connect statement)

 

gesetzt werden

 

LFM293

Could not remove log file '<string>'

Check for previous messages.

 

(ID = <number>) from location <number>.

Also check if the config

   

database ADM<SID> can be

 

Log-Datei '<string>' (ID = <number>)

accessed (by a manual

 

konnte nicht aus Lokation <number>

connect statement)

 

geloescht werden.

 

LFM294

Could not get an ID for <string>-location

Check for previous messages.

 

'<string>' (<string>).

Also check if the config

   

database ADM<SID> can be

 

Fuer die <string>-Lokation '<string>'

accessed (by a manual

 

(<string>) konnte keine ID erzeugt werden.

connect statement)

LFM295

Could not create location entry for

Check for previous messages.

 

<string>-location '<string>'

Also check if the config

 

(location ID = <number>).

database ADM<SID> can be

   

accessed (by a manual

 

Es konnte kein Eintrag fuer die

connect statement)

 

<string>-Lokation '<string>'

 
 

(location ID = <number>) gemacht werden.

 

LFM296

Location ID entry of type '<string>' for

Check for previous messages.

'<string>' not found.

Also check if the config

   

database ADM<SID> can be

 

Keine Lokation-ID (Typ '<string>') fuer

accessed (by a manual

 

'<string>' gefunden.

connect statement)

LFM297

Object with ID=<number> deleted from admin| Informational.

 
 

database.

 
 

Objekt mit ID=<number> aus Admin Datenbank

 
 

geloescht.

 

LFM298

Error <number> recording action stop in

Check for previous messages.

 

<string>

Also check if the config

   

database ADM<SID> can be

 

Fehler <number> beim Protokollieren des

accessed (by a manual

 

Aktions-Endes in <string>

connect statement)

LFM299

Datamodel in admin database '<string>' may

Check for previous messages.

 

be out of order (e.g. missing entries)!

Also check if the config

   

database ADM<SID> can be

 

Daten in Admin Datenbank '<string>' evtl.

accessed (by a manual

 

nicht in Ordnung (z.B. fehlende

connect statement)

 

Eintraege)!

 

LFM300

Could not get location ID of log file

Check for previous messages.

 

<string> (<number>) for state '<string>'.

Also check if the config

   

database ADM<SID> can be

 

Lokations-ID fuer Log Datei <string>

accessed (by a manual

 

(<number>) mit Status '<string>' konnte

connect statement)

 

nicht ermittelt werden.

 

LFM301

Could not get log file entry

Check for previous messages.

 

(Object ID: <number>) from database

Also check if the config

 

'<string>'.

database ADM<SID> can be

   

accessed (by a manual

 

Eintrag fuer Log-Datei (Objekt-ID:

connect statement)

 

<number>) nicht in Datenbank '<string>' |

 
 

gefunden.

 

LFM302

Could not get location record for ID = <number>.

Unexpected error. Contact SAP support.

 

Eintrag fuer Lokation mit ID = <number> nicht gefunden.

 

LFM303

Unexpected data ‘<string>‘ returned by <string>.

Unexpected error. Contact SAP support.

 

Unerwartete Daten ‘<string>‘ durch <string> erhalten.

 

LFM304

Could not get location ID for log file <string1> (<number>) with location type ‘<string2>‘.

Probably the log file <string1> is not available at any location of type <string2>. Check if it is available on another medium and proceed accordingly.

 

Lokations-ID fuer Log-Datei <string> (<number>) mit Lokations-Typ ‘<string>‘ konnte nicht ermittelt werden.

 

LFM305

Could not delete object with ID=<number> (<string>) from admin database.

Check further messages (i.e. reason message). In case the reason is not obvious, contact SAP.

 

Objekt mit ID=<number> (<string>) konnte nicht aus Admin Datenbank geloescht werden.

 

LFM306

Expected a new object id for ‘<string1>‘ (<string2>).

SAP-DB2admin expected that a new object <string1> of type <string2> should be generated. But the object was already there! Report this to SAP.

 

Neue Objekt-ID fuer ‘<string1>‘ (<string2>) erwartet.

 

LFM307

Could not create object ‘<string1>‘ (<string2>).

SAP-DB2admin couldn’t create a new object <string1> of type <string2>. Check further messages for the reason. In case the reason is not obvious, contact SAP.

 

Objekt ‘<string1>‘ (<string2>) konnte nicht erzeugt werden.

 

LFM308

Could not get object ID of tape ‘<string>‘.

Maybe no tape with name <string> has been initialized before.

 

Objekt-ID von Band ‘<string>‘ konnte nicht ermittelt werden.

 

LFM309

Could not add log file ‘<string1>‘ to tape <string2>‘s table of contents at position <number>.

Check further messages. If the problem is not obvious, contact SAP.

 

Log-Datei ‘<string1>‘ konnte nicht im Inhaltsverzeichnis von Band <string2> (Pos. <number>) angelegt werden.

 

LFM310

Connect to database failed.

Check for previous messages.

   

Also check if the config

   

database ADM<SID> can be

 

Verbindungsaufbau zu Datenbank

accessed (by a manual

 

gescheitert.

connect statement)

LFM311

A database connection to the admin

Check for previous messages.

 

database <string> does not exist.

Also check if the config

   

database ADM<SID> can be

 

Es existiert keine Verbindung

accessed (by a manual

 

zur Admin-Datenbank <string>.

connect statement)

LFM312

Could not record step in the admin

Check for previous messages.

 

database\n Error Isolation: <string>

Also check if the config

   

database ADM<SID> can be

 

Arbeitsschritt konnte nicht in Admin-DB

accessed (by a manual

 

protokolliert werden:\n<string>

connect statement)

LFM313

Tape volume ‘<string1>‘ has already been initialized in the past. It will be re-initialized!

Informational during tape initialization.

 

Band ‘<string>‘ wurde bereits einmal initialisiert und wird jetzt neu initialisiert!

 

LFM314

Could not get ‘<string1>‘ from table ‘<string2>‘.

Check the reason message.

 

‘<string1>‘ konnte aus Tabelle ‘<string2>‘ nicht gelesen werden.

 

LFM315

Could not get contents of tape <string>.

Check the reason message.

 

Kann Inhalt von Band <string> nicht ermitteln.

 

LFM316

Tape <string>‘s table of contents not empty.

A tape cannot be reused even if the lock period has expired without reinitialization.

 

Inhaltsverzeichnis von Band <string> ist nicht leer.

 

LFM351

Restoring <string>

Informational.

 

Zurueckladen von <string>

 

LFM355

from <string>...

Informational.

 

von <string>...

 

LFM359

Restore of <string> failed.

Check previous messages.

   

There could be different

 

Zurueckladen von <string> gescheitert.

causes.

LFM360

Not enough disk space in <string> for

Space check detected

 

restore, missing <number> MB.

insufficient resources.

   

Check your file system.

 

Nicht genug Plattenplatz in <string> fuer

Restoring cannot start

 

Zurueckladen, fehlt <number> MB.

in this case.

LFM369

<string> is not a directory.

Check your file system.

   

Check for previous errors.

 

<string> ist kein Verzeichnis.

 

LFM374

<number> of <number> file(s) restored

Informational.

 

by backup utility.

 
 

<number> von <number> Datei(en) durch

 
 

Backup-Utility zurueckgeladen.

 

LFM400

Revision level: <string>

Informational.

   

(maps to build's SCCSID)

 

Revisionsstand: <string>

 

LFM408

BRRESTORE action ID: <string>

Informational.

   

(=r<encrypted timestamp>)

 

BRRESTORE Aktions-ID: <string>

 

LFM409

BRRESTORE function ID: <string>

Informational.

 

BRRESTORE Funktions-ID: <string>

 

LFM410

Log file ‘<string>‘ will not be restored.

Check further messages for the reason. Processing will continue.

 

Log-Datei ‘<string>‘ wird nicht zurueckgesichert.

 

LFM414

Log file(s) for restore: <string>

Informational.

 

Log-Datei(en) zum Zurueckladen: <string>

 

LFM415

Name of volume to be used cannot be determined.

If the utility is called through SAP-DB2admin, please check if you entered a correct volume name. If you called the utility manually, check the ‘-v’ option.

 

Name des benoetigten Bandes kann nicht ermittelt werden.

 

LFM416

<number> file(s) found to restore,

Informational.

 

total size <number> MB.

 
 

<number> Datei(en) zum Zurueckladen

 
 

gefunden, Gesamtgroesse <number> MB.

 

LFM417

Could not get position of log file ‘<string1>‘ on tape ‘<string2>‘.

Check further messages.

 

Position der Log-Datei ‘<string1>‘ auf Band ‘<string2>‘ kann nicht ermittelt werden.

 

LFM418

<number> of <number> file(s) restored -

Informational.

 

<number> MB of <number> MB done.

 
 

<number> von <number> Datei(en)

 
 

zurueckgeladen - <number> MB

 
 

von <number> MB fertig.

 

LFM421

Backup device type for restore: <string>

Informational.

 

Sicherungs-Geraetetyp fuer

 
 

Zurueckladen: <string>

 

LFM428

File <string> will be overwritten.

Informational.

 

Datei <string> wird ueberschrieben.

 

LFM550

Backup utility call generated warnings.

Check previous messages.

 

Warnungen beim Aufruf des Backup-Utility.

 

LFM551

Error(s) during '<string>': can be treated

It is important to check the

 

as warnings within the given context.

reason for the error(s).

   

However, the current task

 

Fehler waehrend '<string>': sind unter

completed successfully.

 

den gegeben Umstaenden nur Warnungen.

 

LFM560

Error during BACKINT initialization.

Any parameters may be not

   

correct. Check previous

 

Fehler bei BACKINT-Initialisierung.

messages for the cause.

LFM561

Unable to install signal handler(s).

This probably is a problem

   

on operating system level.

 

Signal-Behandlung konnte nicht

Retry. If the problem does

 

eingerichtet werden.

not disappear then report it

   

to SAP.

LFM562

Could not start audit log - I/O error

The audit log protocols ADSM

 

(rc = <number>)

activity in a file. This is

   

just a warning and will

 

Protokolldatei kann nicht geschrieben

result in not having the

 

werden - I/O-Fehler (rc = <number>)

protocol available. However,

   

actions will be logged in

   

SAP-DB2admin-Database.

LFM563

Unable to access list of files to be

This is an internal error.

 

processed.

Report to SAP.

 

Liste der zu bearbeiteten Log-Dateien

 
 

kann nicht zugegriffen werden.

 

LFM564

<string> ended for log file <string>

Reports the result of an

 

(rc = <number>)

ADSM Backup/Restore action.

   

In case of errors check

 

<string> beendet fuer Log-Datei <string>

previous messages.

 

(rc = <number>).

 

LFM565

Saved <string><string> auccessfully.

Informational.

 

<string><string> erfolgreich gesichert.

 

LFM566

Restored <string><string> auccessfully.

Informational.

 

<string><string> erfolgreich

 
 

zurueckgespielt.

 

LFM567

Failed to save <string> (rc = <number>)!

Check previous messages.

 

Cannot continue...

 
 

<string> konnte nicht gesichert werden

 
 

(rc = <number>)! Vorgang wird

 
 

abgebrochen...

 

LFM568

Internal error in BACKINT! <string>

Internal errors prevent the

   

action from continuing. Even

 

Interner Fehler in BACKINT! <string>

protocolling is not possible

   

any more. Output is to

   

STDERR

LFM569

Error copying file <string> to <string>

Check previous messages.

 

(rc = <number>).

Check the filesystem and

   

file access permissions.

 

Fehler beim Kopieren von <string>

 
 

nach <string> (rc = <number>).

 

LFM570

Error initializing ADSM session.

ADSM may be unavailable.

 

Ask your ADSM administrator

 
 

Fehler beim Verbindungsaufbau mit ADSM.

for possible reasons.

LFM571

ADSM error <number>: <string>

If there's no obvious cause

   

for <string> then report to

 

ADSM Fehler <number>: <string>

SAP. First check with your

   

ADSM expert.

LFM572

Error terminating ADSM.

Check previous messages.

 

Fehler beim Beenden der ADSM Verbindung. |

 

LFM573

Error creating directory: <string>

Check the file access

 

(rc = <number>).

permissions and the possibly

   

already existing ownership

 

Fehler beim Anlegen von Verzeichnis

of <string>.

 

<string> (rc = <number>).

It is recommended to set the

   

DB2DB6_TEMP_DIR to a path

   

for which the db2<sid> user

   

has exclusive write

   

permission. This will

   

prevent other users from

   

having a directory with the

   

same name.

LFM574

Could not end audit log - I/O error

The audit log protocols ADSM

 

(rc = <number>)

activity in a file. This is

   

just a warning and will

 

Protokolldatei kann nicht abgeschlossen

result in not having the

 

werden - I/O-Fehler (rc = <number>)

protocol available. However,

   

actions will be logged in

   

SAP-DB2admin-Database.

LFM575

Error registering ADSM filespace

Check the previous message.

 

'<string>' of Type '<string>'.

Processing cannot continue.

 

Fehler beim Registrieren des ADSM

 
 

Filespace '<string>' (Typ: '<string>').

 

LFM576

ADSM mgmt class bind (<string>) failed!

Check the previous message.

 

(FS-name: <string> - HL-name: <string> -

Processing cannot continue.

 

LL-name: <string>)

 
 

Fehler beim Binden der <string>

 
 

ADSM-Mgmt-Klasse! (FS-name: <string> -

 
 

HL-name: <string> - LL-name: <string>)

 

LFM577

Error beginning ADSM transaction.

Check the previous message.

   

Processing cannot continue.

 

Fehler beim Starten einer ADSM

 
 

Transaktion.

 

LFM578

Error sending object to ADSM.

Check the previous message.

   

Processing cannot continue.

 

Fehler beim Senden eines Objektes ins

Ask your ADSM administrator.

 

ADSM.

 

LFM579

Error reading data from file '<string>'

Data to transfer to ADSM is

 

(rc = <number>).

read blockwise from <string>

   

and failed. Retry later!

 

Fehler beim Lesen aus Datei '<string>'

If the problem persists try

 

(rc = <number>).

to access the file with

   

operating system commands

   

(e.g. copy) and check if it

   

is possible. If not, the

   

log file may be corrupt.

   

Backup your database! The

   

log file will not allow

   

recovery any more.

LFM580

Error sending data to ADSM.

Check the previous message.

   

Processing cannot continue.

 

Fehler beim Senden von Daten ins ADSM.

Ask your ADSM administrator.

LFM581

Error closing file '<string>' just

In case of restoring a log

 

sent/retrieved to/from ADSM.

file try again.

   

Check if the received file

 

Fehler beim Schliessen der Datei

size matches the expected

 

'<string>' (soeben ins/von ADSM

size. Then everything should

 

gesichert/abgeholt).

be ok.

LFM582

Error opening file '<string>' to be

Check file access permission

 

sent/retrieved to/from ADSM.

and try again.

   

Also check if in case of

 

Fehler beim Oeffnen der Datei '<string>'

archiving to ADSM the file

 

(sollte ins/von ADSM

<string> exists.

 

gesichert/zurueckgeladen werden).

 

LFM583

Error ending to send object to ADSM.

Check the previous message.

 

Fehler beim Abschluss des Sendevorganges

 
 

eines Objektes ins ADSM.

 

LFM584

Error ending ADSM transaction.

Check the previous message.

 

Fehler beim Beenden einer ADSM

 
 

Transaktion.

 

LFM585

ADSM reason <number>: <string>

This message gives more info

   

about the failure of an ADSM

 

ADSM Ursache <number>: <string>

operation. Check it

   

carefully.

LFM586

Error beginning ADSM <string> query.

Check the previous message.

 

Fehler beim Start einer ADSM-<string>

 
 

Abfrage.

 

LFM587

Error ending ADSM <string> query.

Check the previous message.

 

Fehler beim Beenden einer ADSM-<string>

 
 

Abfrage.

 

LFM588

Query for ADSM objects found no match.

Check the previous message.

 

Abfrage von ADSM-Objekten erzielte

 
 

keinen Treffer.

 

LFM589

Error beginning getting data from ADSM

Check the previous message.

 

'<string>' repository.

 
 

Fehler beim Starten des Datentransfers

 
 

aus ADSM '<string>'-Ablage

 

LFM590

Error getting object from ADSM <string>

Check the previous message.

 

repository.

 
 

Fehler beim Abholen eines Objektes aus

 
 

ADSM-<string>-Ablage.

 

LFM591

Error getting data from ADSM.

Check the previous message.

 

Fehler beim Datentransfer aus ADSM.

 

LFM592

Error writing data to file '<string>'

Data to get from ADSM is

 

(rc = <number>).

read blockwise from ADSM

   

and failed. Retry later!

 

Fehler beim Schreiben in Datei

If the problem persists

 

'<string>' (rc = <number>).

check the access permissions

   

in the target path.

LFM593

Error ending getting object from

Check the previous message.

 

ADSM <string> repository.

 
 

Fehler beim Abschliessen des

 
 

Objekttransfers aus ADSM <string>-Ablage.

 

LFM594

Error ending getting data from ADSM

Check the previous message.

 

<string> repository.

 
 

Fehler beim Abschliessen des

 
 

Datentransfers aus ADSM <string>-Ablage.

 

LFM595

No files to retrieve from ADSM found.

Check the ADSM configuration

   

files to ensure that the

 

Keine Dateien zum Abholen aus ADSM

utility connected to the

 

gefunden.

correct ADSM service. Also

   

ask the ADSM server admin

   

if your session connects to

   

the correct ADSM repository.

   

If this can be ensured and

   

the file still is not there

   

then check again if it had

   

been saved to ADSM!

   

If the log file cannot be

   

located then you are not

   

able to rollforward to a

   

point in time logged in

   

this file or later.

   

Check previous messages.

LFM596

Error querying ADSM session information.

Check the previous message.

 

Fehler beim Abfragen der ADSM-Session

 
 

Information.

 

LFM600

Reason code: <number> - Message:Gives additional information

 
 

<string>

to a previous failure. This

   

reason message is very

 

Ursache: <number> - Grund: <string>context dependent.