# SAPup help texts $DateTime: 2020/11/26 05:15:09 $ $Id: //bc/lmt_023_REL/src/upg/SAPup/SAPupHELPE.TXT#4 $
# A help text is the text between two identifiers.
# Identifiers are lines beginning with '#PE'.
# Help text lines may not be longer than 72 characters.
#PE0010
SAPup needs a parameter file that was not found.
You can specify the full path to this file in the program
call: "SAPup pf=<filename>".
#PE0011
The system call for (re)definition of environment variables
failed. Contact SAP Local Support to find out
which variables have to be set and try to define them
manually before starting SAPup.
#PE0012
The system query of your host attributes failed.
No default values are set for SAP System or the database server.
This indicates a severe problem in your
operating system.
#PE0013
The system query of your user attributes failed.
No default values are set for the user name and path to the
SAP System start procedure. This indicates a severe
problem in your operating system.
#PE0014
Your upgrade data is  i n c o m p l e t e  !
Delete all temporary upgrade data from the disk and
re-import this data from CD ROM. After the CD ROM
has been read, check that the subdirectories
"bin", "buffer", "cofiles", "data", "exe", "log",
"sapnames", and "tmp" exist in your upgrade directory.
#PE0015
You must have full access to some central directories.
Check your permissions for the administration
user. (Do not switch to another user!)
#PE0016
The system query of the current time failed.
Check the time on your operating system.
This error indicates an unexpected time value
returned by the operating system.
#PE0017
The fopen() call failed when creating the global
SAPup log file. This indicates a fatal I/O problem in
your operating system.
#PE0018
You tried to start an upgrade phase which requires the
current upgrade environment file created in phase INITPUT.
For some reason, this file does not exist in "bin".
If your system is still operable, try to restart the
upgrade from the beginning. Remove log file SAPup.log from
"log" to start again from the beginning.
#PE0019
You tried to start an upgrade phase which requires the
current database environment file created in phase DBCHK.
For some reason, this file does not exist in "bin".
If your system is still operable, try to restart the
upgrade from the beginning. Remove log file SAPup.log from
"log" to start again from the beginning.
#PE0020
You have switched user. The current user is not the user
logged on at the beginning of the upgrade procedure.
You should on no account do this.
#PE0021
The transport directory must exist, at least as a local
directory on your machine. This directory usually connects
a system cluster and is mounted on each application server.
For information about how to install the Change and
Transport System on your SAP System, see the
documentation in the SAP System library.
#PE0022
The profile of the central instance could not be read or
the parameter values extracted from the profile are
inconsistent with the values you entered. Compare
the profile name and parameter values you
find there for <SID> and instance number with the
values you expect.
#PE0023
Error during creation of an internal table. The most likely
cause is that the allocation of dynamic memory failed.
Reduce the memory allocation by stopping non-essential
processes or increasing the virtual memory (swap space).
#PE0024
A request for dynamic memory failed. Reduce the system
memory allocation by stopping non-essential processes
or increasing the virtual memory (swap space).
#PE0025
You probably called the wrong executable.
Specify the full path to the executable
at the command line.
#PE0026
Error returned by the operating system. The upgrade
stops for security reasons. Check the possible causes
of the operating system message. To exit SAPup, choose 	
CANCEL. If you choose CONTINUE, further error messages
may appear or SAPup may continue, depending on the severity
of the error.
#PE0027
An invalid preprocessing directive was encountered in
one of the parameter files.
#PE0028
SAPup has determined that an incompatible higher version
was used before. To protect against damaging internal
data structures, SAPup ends.
Use the latest version of SAPup.
#PE0030
A file is requested by SAPup, but cannot be found in
the path specified. This data is essential for the
upgrade. Do not ignore this error.
#PE0031
The program status cannot be restored or an event
cannot be written to file "SYSSAPup.dat".

The most probably cause is a hardware problem
in your upgrade file system.
#PE0032
You have already started SAPup, which starts the actual upgrade.
The PREPARE checks can no longer be run, as they could affect
the internal upgrade control.
#PE0033
Extraction of the specified archive to disk failed.

If a read error occurs, try to repeat the import
before calling SAP Local Support. (Tip: Try cleaning the CD).
If possible, use a different CD ROM drive (on a
remote host). If this fails too, the most likely 	
explanation is that the CD itself is corrupted.

If write errors occur, check the target file system
(permissions, hardware failures, and so on). If insufficient
free space is available in the file system, take into account
that further archives may have to be unpacked.
For detailed information on free space requirements, see
your upgrade manual.

The error codes in detail are:

-1  : Unable to find the SAP structure
-2  : Error during open of LABEL file
-3  : User selected CANCEL
-4  : Unable to create directory
-5  : Unable to read TOC file
-6  : Missing write permissions
-7  : Unable to read SPC file
-8  : Memory allocation failure
-9  : Unexpected internal error
-11 : Archive does not exist
-12 : No access to archive
-13 : Target directory does not exist
-14 : No access to the target directory
-15 : Unable to change to the target directory
-16 : Unable to open archive for type check
-17 : Unable to open the archive
-18 : Unable to read the archive header (old method)
-19 : Error during read of archive data (old method)
-20 : Archive has a wrong format        (old method)
-21 : Unable to open the archive
-22 : Unable to read the archive header
-23 : Memory allocation failure
-24 : Exited due to missing free space on disk
-31 : Cannot create directory, permission denied
-32 : Cannot create directory, not a directory
-33 : Cannot create directory, too many symbolic links
-34 : Cannot create directory, read-only file system
-35 : Unable to overwrite file, no write permission
-36 : Unable to create file, permission denied
-37 : Unable to create file, is a directory
-38 : Unable to create file, not a directory
-39 : Unable to create file, file is locked
-40 : Unable to create file, too many symbolic links
-41 : Unable to create file, directory does not exist
-42 : Unable to create file, read-only file system
-43 : Unable to create file, file is busy
-44 : Unable to create file, re-open failed
-45 : Decompression error during read of archive data
-46 : Error during write, no space left on device
-47 : Error during write (other errors)
-48 : Unable to set the file creation date
-49 : Unable to change the access mode, no permission
-50 : Unable to change the access mode (other errors)
-51 : Cannot create directory
-52 : Unable to create file
-53 : Checksum error
-54 : Unable to query current working directory
-55 : Directory name too long
-56 : Key error 
-57 : Internal error
-58 : Format error in include file
-59 : Option wrong
-60 : Compression error
-61 : external CAR program not executable
-62 : Error during execution of external CAR program
-63 : Error during analysy of logfile CAR.ECO
#PE0034
More than one CDROM was requested to be used simultaneously.
While testing for access to these CDROM's, one or more were
not found.

Normally, one can perform an upgrade with only one CD drive.
As an optimization, a user might provide several CD's at the
same time, saving space and time for the copying.

The cause for this error message is that even though the user
enabled this optimization, the CD request could not be
satisfied.
#PE0036
The description for a specific type of CDROM could not
be read. This indicates an inconsistent state of the
control files in your upgrade directory. An alternative
reason is that the version of SAPup is too new.
#PE0060
The file containing static report variants is corrupted.
This indicates that your upgrade data has not been correctly
extracted from CD. Back up subdirectory "bin"
and unpack the data on the KERNEL CD again with the call

SAPup readCD
#PE0061
This is usually caused by a lack of memory. Stop all
unnecessary activities on the machine and restart SAPup.
#PE0062
The fix archive is corrupted. To prevent severe upgrade
failure and data loss, the PREPARE must be restarted with an
empty upgrade directory.
#PE0100
The program saplicense is used to install and check the
SAP System license. It must be called on the database server.

You can install a temporary 4 week license once. After that,
you have to install a permanent license.
#PE0101
The program saplicense is used to install and check the
SAP System license. During the validation of the new SAP System kernel,
an error occurred. Call SAP Local Support.
#PE0110
System query of user attributes failed. Check
your operating system for the definition of the user
you are logged on as.
#PE0111
Inconsistency in user attributes detected. Did you switch
to another user before restarting the upgrade ?
#PE0112
A child process (or subprocess) could not open the
file for redirection of its output. Check all the
file systems you are using !
#PE0113
A child process (or subprocess) could not redirect
its output to a spool file that had already been opened.
This indicates an unexpected situation for the files
being opened. Try to restart SAPup.
#PE0114
Error detected in your user environment. To set the
correct administration environment, log off and log
on again as <sid>adm.
#PE0115
File exe.lst is missing. Wrong upgrade data ?
#PE0120
Your CD ROM is not mounted correctly or you entered
the wrong path to the mount point !
Please try to mount the upgrade CD again.
Interpretation of the code displayed:
-256: Error in system routine
 -32: Path does not exist
 0x1: Scan access to path
 0x2: Write access to path
 0x4: Read access to path
 0x8: Path is a directory
The correct code for a CD ROM mount point is 13.
#PE0210
You are using the wrong CD or bad upgrade data.
Check that the data import from CD ROM was
successful. If so, contact SAP Local Support.
#PE0211
The database environment could not been evaluated.
This may be due to permission problems or a full file system.
#PE0212
The database environment file could not been written
to "bin". This may be due to permission problems
or a full file system.
#PE0213
The database environment file is not found in "bin".
Check why this file is missing or has not been
created. This is impossible when phase DBCHK has been
processed successfully.
#PE0214
Please check the validity of program tp you are using.
The default path is "exe", but this may be overwritten
by parameter "tp_path" in the parameter file of SAPup.
The call "tp getdbinfo <SID>" should write the lines
DBAVERS=...
DBASUBTYPE=...
KERNVER=...
SAPVERS=...
Possible reasons for missing or incomplete data are:
1) Your database is shut down.
2) You are using an old version of program tp.
3) The SAP System status is wrong. Refer to your upgrade
   manual.
#PE0215
Fatal internal inconsistency in the database environment.
Environment cannot be read or set consistently.
Call SAP Local Support.
#PE0216
Unexpected fopen() failure. Try to restart SAPup.
#PE0217
Inconsistency of the versions of CD groups.

The CDs used during the upgrade need to have identical
CD group versions. You can find the CD group versions
in the file GROUP.ASC on the CD.

The upgrade program has determined, theat the CD currently 
used does not fit to the CD group vresions used during
the upgrade so far.

Pleas check, if the CD currently used does really fit to
the package of CDs used so far.
#PE0300
Unexpected failure of "tp gettrbatent <SID>". Try to
restart program SAPup.
#PE0301
No output file for the preceding call "tp gettrbatent <SID>".
Try to restart program SAPup.
#PE0302
Unexpected fopen() failure. Try to restart program SAPup.
#PE0303
See the error message for instructions on how to handle
this error. If you decide to delete the entries in
table TRBAT, make sure that no tp process tries to 	
connect to your database (locally or remotely)
and check the SAP System batch queue is in a consistent status
using transactions SM37 and SM50.
#PE0305
Unexpected failure of "tp getddxttent <SID>". Try to
restart program SAPup.
#PE0306
No output file for preceding call "tp getddxttent <SID>".
Try to restart program SAPup.
#PE0307
Check the ABAP, DDIC and DB consistency of all structures
listed in table DDXTT. If you are not
able to do this, call SAP Local Support.
#PE0308
Check the ABAP, DDIC and DB consistency of all structures
listed in table DDXTF. If you are not
able to do this, call SAP Local Support.
#PE0310
Your upgrade data is incomplete. Delete all temporary
upgrade data on disk and re-import all data from CD ROM.
#PE0311
Your upgrade data is incomplete. Delete all temporary
upgrade data on disk and re-import all data from CD ROM.
#PE0312
Old upgrade data found. It is very important to remove all
temporary upgrade data before starting a subsequent upgrade.
If your SAP System profile has been already modified by the
upgrade procedure, do not remove the profile backup in
"sapnames" !
#PE0313
You changed the SID of your SAP System.
Possibly you entered <CR> as the SID of your SAP System.
Delete SAPup.log and restart this program.
#PE0314
The name of the user you are logged on as does not conform
to the naming conventions for the SAP System administrative user.
You may authorize this handling by defining parameter
'putuser' accordingly in the SAPup parameter file. However,
no support is guaranteed for this procedure.
#PE0315
Input files exist which are not owned by the user you are
logged on as. Did you import the temporary upgrade data
as another user or from another host? This is risky.
Permission problems can arise. Change the owner of all (!)
files coming from CD ROM to the correct ID, or re-import
data from CD.
#PE0316
Enter a valid client, such as "001" or "061". If the default value
is correct, you can alternatively enter <CR>.
#PE0317
Unexpected fopen() failure. Restart program SAPup.
#PE0318
The specified file does not exist or has incorrect
access attributes. The reasons may be:
- Wrong filename or pathname
- File is really missing
- File permissions deviate from standard
- Remote file system not mounted
#PE0319
Error while generating tp parameter file. The codes are:
-1 = template does not exist
-2 = file owner conflict
-3 = undefined file name
-4 = error in fopen()
#PE0320
The host name you specified is not consistent. Please use
a unique host name.
#PE0321
You entered a wrong instance number of your SAP System.
You can find the instance number in the instance profile
in the line "SAPSYSTEM = <nr>".
#PE0330
Unable to identify your SAP System in the 'sapconf' file.
Please check your installation for this configuration
file and restart SAPup. Another possibility to set up the
database type is to specify a parameter "dbatype = ..."
in the SAPup parameter file ('SAPup.par'). Specify one of
the values

ORACLE
INFORMIX
SAPDB
DB6
MSSQL
DB2/400
#PE0331
The call "tp getdbinfo <SID>" failed.
Check the validity of the tp program you are using.
The default path is "exe", but this can be overwritten
by parameter "tp_path" in the parameter file of SAPup.
The call "tp getdbinfo <SID>" should write the lines
DBAVERS=...
DBASUBTYPE=...
KERNVER=...
SAPVERS=...
Possible reasons for missing or incomplete data are:
1) Your database is shut down.
2) You are using an old version of program tp.
3) The SAP System status is wrong. For information
   about which Releases are supported, refer to your
   upgrade manual.
#PE0332
Unable to save the database environment to file.
Contact SAP Local Support.
#PE0333
The tp call described in the error message failed.
It did not print the requested text pattern on stdout.
Continue as described in the error message or
in the upgrade documentation for this particular phase.
#PE0340
For information about which database versions are
supported, refer to your guide. All necessary information
can be found in the upgrade manual.

If an operating system or database upgrade is linked to
the SAP System upgrade, the Basis software is switched along with
the SAP System kernel, that is during the upgrade downtime.
At this point in time, the SAP System is  n o t  functional.
Use operating system and database tools to verify that the
update of this software has been successfully finished.
#PE0341
To see which database versions are supported, refer to your guide.
Using any other versions will probably lead to problems.
#PE0342
To see which SAP System releases are supported as source releases, refer
to your guide. You need another upgrade CD.
#PE0343
To see which SAP System releases are supported as source releases, refer
to your guide. You need another upgrade CD.
#PE0344
To see which SAP System releases are supported as source releases, refer
to your guide. You need another upgrade CD.
#PE0345
To see which SAP System releases are supported as source releases, refer
to your guide. You need another upgrade CD.
#PE0336
To see which releases of this SAP System add-on are supported as source
releases, refer to your guide. You need another installation CD.
#PE0338
To see which SAP System releases are supported as source releases, refer
to your guide. You need another upgrade CD.
#PE0339
To see which SAP System releases are supported as source releases, refer
to your guide. You need another upgrade CD.
#PE0346
Unexpected failure of "tp getopencorr <SID>". Try to
restart program SAPup.
#PE0347
No output file for preceding call "tp getopencorr <SID>" found.
Try to restart program SAPup.
#PE0348
Unexpected fopen() failure. Try to restart program SAPup.
#PE0349
You still have open repairs in your SAP System.
For information about how to release these corrections,
refer to your guide.
Open repairs result in inconsistent sources in
your SAP System after upgrade. Repeat this phase until
no more open repairs are found.
#PE0350
Unexpected failure of the call "tp gettbatgent <SID>" or
"tp getconvent <SID>". Try to restart program SAPup.
#PE0351
No output file of the preceding call "tp gettbatgent <SID>"
or "tp getconvent <SID>". Try to restart program SAPup.
#PE0352
Unexpected fopen() failure. Try to restart program SAPup.
#PE0353
Each entry in table TBATG represents an attempt to	
convert a database structure. If the field SEVERITY	
has the value 'E', the conversion has failed.
Check the status of the object in the Repository	
(using transactions SE11 and SE12). Using transaction
SE14, compare the structure definitions in the Repository	
and in the database. If no conversion is required,
delete the corresponding entry in table TBATG with SM31.
On the other hand, if structure conversion is necessary,
proceed as described in the upgrade manual.
Analyze all errors that are displayed and follow the
instructions given in the error dumps.

If you delete conversion requests from table TBATG,
this could result in a severe malfunction of the system.
On the other hand, TBATG entries created before the
upgrade was started might now be incorrect.
#PE0354
The batch process RDDEXECL has probably been scheduled
for an application server where the PUT directory
(/usr/sap/put on UNIX) is not available. Execute the
report RSUMOD01 manually on the central application
server to calculate the necessary Dictionary
adjustments in the releases which will be imported.
#PE0355
Invalid phase name. Possible reasons are:

- SAPup has been confused by a phase jump
- Your upgrade data is corrupted

Check the file /usr/sap/put/bin/DBENV.LST
(Windows NT: \usr\sap\put\bin\DBENV.LST)
to see whether the version of the SAP System has
been updated to the new release (lines 5-7).
If this is the case, and SAPup has  n o t  processed
the phase "END", the status is inconsistent.
Enter the start release into these lines using an
editor and restart SAPup.
#PE0356
Your upgrade data is corrupted. Reimport all data
from CD-ROM.
#PE0357
To see which operating system versions are supported,
refer to your guide. You will find all the necessary
information in the upgrade manual.

If an operating system or database upgrade is linked to
the SAP System upgrade, the Basis software is switched along with
the SAP System kernel, that is during the upgrade downtime.
At this point in time, the SAP System is  n o t  functional.
Use operating system and database tools to verify that the
update of this software has been successfully finished.

#PE0358
To see which operating system versions are supported, refer to
your guide. Using other versions will probably lead to problems.
#PE0360
An error occurred when the free space needed in the database
was compared with the free space currently available in the
database. The meaning of the return codes are:

 -1: No input file found. Please reimport all data from CD-ROM.
 -2: Unexpected fopen() error on SQL script file. Try to restart.
 -3: Unexpected write error on SQL script file. Try to restart.
 -4: Database tool not found. Call SAP Local Support.
 -5: Unable to open SQL result file. Try to restart.
 -6: Unable to open output result file. Try to restart.
 -7: Unable to open temporary output file. Try to restart.
 -8: Memory allocation error. Increase the virtual memory.
 -9: Unable to evaluate the database container for singular
     TABLE or INDEX requests. Call SAP Local Support.
-10: Error when calculating the sum of all free space requests.
     Please call the SAP Local Support.
#PE0361
Unexpected fopen() error. Try to restart.
#PE0362
Unexpected write error. Try to restart.
#PE0370
No output file found. Call SAP Local Support.
#PE0371
Unexpected fopen() error. Try to restart.
#PE0372
Error messages from database found. Analyze the
SPACECHK output files in "log". You can identify them from
their modification time (the latest log files). If you are
not able to correct the problems, call SAP Local Support.
#PE0373
You do not have enough free space on your database to upgrade
the SAP System. For information on how to extend the free
space in your database, refer to your manual. The minimum
recommended extensions are listed in the SPACECHK log file in "log".
If disk space is available, do not hesitate to increase these
values. This will prevent greater database fragmentation.
On the other hand, leave some reserve on your disks
for use in future upgrades.
#PE0375
Your combination of operating system and database
is not found in the list of supported configurations.
Call SAP Local Support.
#PE0377
An SQL-Script to report ABAP loads could not be processed or
terminated with errors. Please analyze all log files of type
LISTLOAD in the log directory.
The exit codes are:
-1 = Error during execution of the script
-2 = The SQL script could not be opened
-3 = The SQL script could not be written
-4 = No spool file of the SELECT is found
-5 = The script could not be verified
-6 = Not enough memory for list of all loads
#PE0378
The file REPLIST could not written to the default directory
("work") of the SAP System. Correct the permissions
for this directory.
#PE0380
Your upgrade data is corrupted. Reimport all data
from CD-ROM.
#PE0381
Error reading the free disk space of the file systems
where the upgrade and active SAP System executables are located. Try
to repeat SAPup. If the error still occurs, call SAP Local Support.
#PE0382
Insufficient space for log files in "log". Before continuing,
extend the relevant file system or remove files from this file
system.
#PE0383
Not enough space for SAP System kernel exchange. Before continuing,
extend the relevant file system or remove files from this file
system.
#PE0384
You did not assign write permission to all SAP System executables
(including those owned by root). Change the permissions
for these files.
#PE0385
Insufficient space for files to be copied to the specified destination.
Extend the relevant file system or link the directory
to another physical mount point. In the latter case, you have to
copy all existing files to the new directory!
#PE0386
Illegal format in ALP file: Multiple definitions found.

Contact the SAP support.
#PE0389
Modification of a profile failed. Modifications are
inserted as follows: The old parameter line is
commented out (leading '#') and a modification key is
added to the end of the line. The new parameter value is
specified in the next line. The error codes are:
-1 = Unable to open the original profile
-2 = Unable to open the new profile
-3 = Unable to open the instruction file
-4 = Unable to open the log file
-5 = Instruction file is empty
-6 = Write error on new profile
-7 = Write error on log file
-8 = Illegal instruction in file
-9 = Memory allocation failed
#PE0390
Unable to save the SAP System profile to "sapnames". You need
to be able to do this for the automatic profile
modifications performed in MODPROF. Check your hardware
and try to repeat SAPup.
#PE0391
Unexpected fopen() error. Try to restart.
#PE0392
Unexpected fopen() error. Try to restart.
#PE0393
Unexpected fopen() error. Try to restart.
#PE0394
Unexpected data error. Try to restart.
#PE0395
Unexpected write error. Try to restart.
Look for any overflow in your file systems !
#PE0396
Unexpected write error. Try to restart.
Look for any overflow in your file systems !
#PE0397
Unexpected data error. Try to restart.
#PE0398
Unexpected data error. Try to restart.
#PE0399
Error detected during SAP System shutdown. Try to shutdown the SAP System
system manually and restart SAPup.
#PE0400
Error detected during SAP System startup. 
Return Code:
  -1 : the script 'startsap' returned an error
  -2 : the test connect to the system did not work

For error analyse:
code -1:
- look in file startsap_<hostname>_<inst-nr>.log in the home directory
  of the <sidadm> user
- look at the trace and error log files in the work directory:
  /usr/sap/<SID>/DVEBMGS<inst-nr>/work
- Try to startup the SAP System manually logon as user DDIC,
  and restart SAPup.

code -2:
- Try to logon to the system as user DDIC.
- Did you change the password of user DDIC?
  If you canged the password of DDIC, you need to tell this SAPup:
  call for the original system: SAPup set ddicpwd
  call for the shadow system: SAPup set shdddicpwd
- Is the gateway process running?
  look at the trace and error log files in the work directory:
  /usr/sap/<SID>/DVEBMGS<inst-nr>/work file dev_rd
#PE0401
Error detected during database shutdown. Try to shutdown the
database manually and restart SAPup.
#PE0402
Error detected during database startup. Try to startup the
database manually and restart SAPup.
#PE0404
Unable to execute program saplicense. Execution of this
program is a prerequisite for activating the new SAP System
kernel after the kernel switch in a later phase.
Call SAP Local Support.
#PE0410
Incomplete upgrade data!
#PE0411
Incomplete upgrade data!
#PE0412
Error during execution of a program of the
command list correlated to this phase. For information
about how to interpret the return code, refer to
your hardware documentation.
#PE0413
Expected log file not found on "log". The command that
writes this log file seems to be failed.
#PE0414
Unexpected fopen() error. Try to restart.
#PE0415
Error messages detected in the log file of this phase.
For information about possible error causes, see your
guide and the upgrade Notes for your release.
If you are unable to analyze the error messages,
call SAP Local Support.
#PE0420
The tp buffer file was not found. Did you remove
this file by hand? This file is essential for checking
the successful completion of your upgrade process.
#PE0421
The tp buffer file indicates that not all actions
were performed completely. Start by trying to repeat the
phase. If it fails again, call SAP Local Support.
#PE0422
Unexpected failure of "tp getdbinfo <SID>". Try this call
manually and check the system status by hand.
#PE0423
The database check shows that the upgrade was not been
completed correctly. The target release was not written to
the database. Call SAP Local Support.
#PE0425
The database check shows that you did not reach the destination
release for internal documentation. Call SAP Local Support.
#PE0440
This error indicates that the SAPup status file was modified.
CAUTION: Do not touch this file under any circumstances.
#PE0441
This error indicates that the SAPup status file was modified.
CAUTION: Do not touch this file under any circumstances.
#PE0442
The tp buffer of the preceding phase is not found.
What happened in "buffer"? Did you change anything manually?
#PE0443
Unexpected copy failure. Restart SAPup.
#PE0444
Some activities produced error messages. Messages with exit
codes lower than or equal to 8, indicate problems with single
transport objects. Exit codes greater than 8 indicate
severe general problems. For information about how to
deal with errors, refer to your manual and to the upgrade
notes for your release. In most cases, a manual repair
and repeating of the relevant upgrade phase are necessary.

If you get the message "Please check your local system id",
correct the TADIR entry 'HEAD' 'SYST' of your SAP System
System using database tools. Field SRCSYS must contain the
SID of your SAP System. You probably copied this system
from another one, but omitted to reset the transport system
with transaction SE06.
#PE0445
To analyze an activity that failed, look at the end
of file SLOG in directory "log".
For detailed error information, see either the last log
files written or the batch log files in the SAP System.
You can also look at the SAP System log. However, after
looking at the log files, you must repeat the upgrade phase.
#PE0446
Program tp does not exist, cannot be executed, or returns
an exit code indicating that an error has occurred.
Check your executables on "exe" and analyze the
error messages that can be found at the end of SAPup ECO
files. Before you repeat the upgrade phase,
try to correct the tp problems.
#PE0447
The call "tp locksys <SID>" failed !
Program tp probably does not exist or is not executable.
Repair the "exe" subdirectory.
#PE0448
Unexpected fopen() error. Try to restart SAPup.
#PE0449
To analyze an activity that failed, look at the end
of file SLOG in directory "log".
For detailed error information, see either the last log
files written or the batch log files in the SAP System.
You can also look at the SAP System log. However, after
looking at the log files, you must repeat the upgrade phase.
#PE0450
It is expected that all actions in the tp buffer are
processed. This is not the case. Do not delete anything
from "buffer", but try to finish the upgrade by repeating
this phase. Otherwise, you cannot really finish the upgrade
process. Any manipulations in the import buffer will result
in an inconsistent system which has to be reset.
The acitivity which is aborted can be determined by looking
at the tail of file SLOG... in the "log" directory.
Detailed error information can be derived either from the
last written logfiles or from batch logfile in the SAP System.
The SAP System log may help too.

Two different cases have to be distinguished:

1) At least one import step is aborted or has even not been
   started. This can be derived from the appearance of a
   Return Code >= 12 or the unchanged number of objects to be
   processed in the import buffer. Only the Return Code 0 or 4
   indicate a successfully finished import step.

   -> Remove the reason for the abort and repeat the upgrade
      phase afterwards. There is no other solution which
      makes sense, except it is mentioned in a note.

2) Some error messages are logged, but no process aborted.
   In the import buffer you can see return codes <= 8 for all
   steps to be processed in this phase.

   -> It is recommended to solve the problems which caused
      the errors. In some cases, it may be easier to ignore
      the errors here, and to solve the problems after the
      upgrade has finished. SAPup offers the option "ignore"
      in this case without prompting for a password (phase
      ACT_...), or SAPup offers "ignore" with option
      "repair severe errors". Use these methods to ignore
      single errors, the usage of passwords causes
      subsequent errors, in most cases the upgrade has
      to be reset completely.
#PE0454
Each entry in table TBATG represents an attempt to	
convert a database structure. If the field SEVERITY	
has the value 'E', the conversion has failed.

Entries where the field OBJECT starts with "MC" are
matchcode conversions that are processed at a later
stage of the upgrade. Start by checking the system
log (with transaction SM21) for database problems.
Then check the status of the objects in the Repository
with transactions SE11 and SE14. Compare the structure
definitions in the Repository with those in the database
using transaction SE14. If structure conversion is necessary,
proceed as described in the upgrade manual (RDDCLEAN,...).
Analyze all errors which displayed and follow the
instructions given in the log files.

If many conversions failed, this normally indicates
that there is a problem with the conversion program.
Trace the reason of this failure in the
system log and converter log (see Summary Log .ELG).
Eliminate the cause, call report RDDCLEAN, and repeat
the phase.

If you delete conversion requests in table TBATG,
this may cause a severe malfunction of the system.
The table TCNV stores the status of all conversions
that failed.
#PE0470
Error during file copy:
-1 = No source file found
-2 = No read permission on source
-3 = Source is a directory!
-4 = System call for copy process failed
#PE0471
Error during update of user profiles:
-1 = No startsap script found
-2 = Unable to open startsap script for read
-3 = No SAP System start profile found
-4 = Unable to open SAP System start profile for read
-5 = Unable to extract SAP System profile name
-6 = Unable to get login directory of actual user
-7 = Unable to open new profile for read/write
-8 = Unable to write new profile
#PE0472
Error during file append:
-1: No <sourcefile> characteristics found
-2: No read permission on <sourcefile>
-3: <sourcefile> is a directory
-4: Cannot open <sourcefile>
-5: Cannot open <destfile>
-6: Write error on <destfile>
#PE0473
The specified programs are called by SAPup and tp to stop and
start the SAP System. They must be callable from the path
given. Copy the existing programs to this path, specifying
the correct names.

During the upgrade, the programs or scripts may be replaced
by the new standard version. If you changed the procedures,
you have to implement these again manually.
#PE0510
Internal error. Contact SAP Local Support.
#PE0511
Error changing the name of a temporary log file copy back to
the original name. Possibly a permission problem:
-1 = No source file found
-2 = No read permission on source
-3 = Source is a directory!
-4 = System call for rename failed
#PE0512
Fatal internal error. You are using the wrong upgrade
program. Check your version of SAPup.
Always call SAPup from the following path:

UNIX:          /usr/sap/put/bin/SAPup
Windows NT:    \usr\sap\put\exe\SAPup.exe

Do not copy SAPup into the kernel directory. You only need it
for upgrade purposes. SAPup is available on every "KERNEL" CD.
#PE0513
Invalid phase name. Possible reasons are:

- SAPup has been confused by a phase jump
- Your upgrade data is corrupted.

Check the file /usr/sap/put/bin/DBENV.LST
(Windows NT: \usr\sap\put\bin\DBENV.LST)
to see whether the version of the SAP System has
been updated to the new release (lines 5-7).
If this is the case, and SAPup has  n o t  processed
the phase "END", the status is inconsistent.
Enter the start release into these lines using an
editor and restart SAPup.
#PE0514
Unable to rename a log file. Before continuing, call
SAP Local Support.
#PE0515
Unable to open a summary error log file. Check
your "log" file system.
#PE0518
Unable to log message to global log file. Check
your "log" file system.
#PE0519
Unable to write SAPup status to file. Fatal hardware
error. Restart SAPup.
#PE0520
Unable to list the contents of the SAP System kernel directory.
There is a problem with your installation. Are you
using the correct SAP system ID?
#PE0521
Unable to open log file that exists in directory.
Try to restart SAPup.
#PE0522
Unable to open temporary copy of log file.
Try to restart SAPup.
#PE0523
Error changing the name of a temporary log file copy back to
the original name. Possibly a permission problem:
-1 = No source file found
-2 = No read permission on source
-3 = Source is a directory !
-4 = System call for rename failed
#PE0524
Invalid phase name, authority check failed.
Please validate the upgrade data you are using.
#PE0610
Unexpected fopen() failure. Please try to restart SAPup.
#PE0611
Something is wrong with the "log" subdirectory. Please
check your hardware and list the directory content
manually. Then restart SAPup.
#PE0613
Problems during accumulation of summary error log file.
The meaning of the different codes are:
-1: Collect file not defined (internal error)
-2: Unable to open summary error log file
-3: Write error on summary error log file
-4: Unable to open temporary copy of single log file
-5: Write error on (copy of) single log file
Check the file system you are writing to
(that is where "log" is located).
#PE0620
Unable to open upgrade environment file for writing.
There seems to be a hardware problem.
#PE0630
The upgrade environment file is expected but not found
in "bin". You have either lost this file or did not create it
in phase INITPUT. Check your handling carefully.
To start again, remove log file SAPup.log.
#PE0631
Unexpected fopen() failure. Try to restart SAPup.
#PE0632
Unexpected inconsistency in upgrade environment file.
Are you working on upgrade data from earlier releases ?
#PE0633
The system descriptions used by SAPup and those
written to the upgrade environment file differ.
Read the upgrade manual carefully for instructions on how
to upgrade a second SAP System. If you do not know the origin
of the inconsistency detected, call SAP Local Support.
#PE0640
Problems occurred during file copy. The probably cause
is that the source file is missing. Make this file
available.
#PE0641
The specified tp command could not be executed successfully.
Look at the log files with extension .ECO for details and
correct the cause of the error.
#PE0642
Problems occurred during file copy. The probably cause
is that the target file could not be overwritten. Change
the file permissions!
#PE0643
The specified buffer, cofile, or data file are required,
but do not exist. The probable reason is that the modification
data has not been completely copied to the upgrade directory.
If you are installing or upgrading an SAP System add-on product,
call the SAP Local Support.
#PE0644
An error occurred during read of the given directory.
Try to display the contents of the directory including the
size of the files by means of your operating system.
If that is working correctly then please try to repeat the
phase.
#PE0645
To get a complete description of the upgrade the log
files belong to, SAPup tries to read the specified file.
The read attempt failed. Check the permissions of the
file and repeat the phase.
#PE0646
To get a complete description of the upgrade the log
files belong to, SAPup tries to read the specified file.
Not all data could be extracted from that file.
This probably means that the upgrade is not complete.
Did you skip some phases?
If SAPup is currently dealing with the log files you copied
to subdirectory 'upgrade' of your transport directory, the
reason may be that these log files are not complete or got
corrupted somehow.
Since this would mean that SAPup cannot handle these log files,
you had better remove the given file (or at least rename it).
Then repeat the phase.
#PE0647
To get a complete description of the upgrade the log
files belong to, SAPup tries to read the given file.
An unexpected error occurred during this read procedure.
Check the contents of the given file by displaying
it on your screen. Do the line formats look strange?
If SAPup is currently dealing with the log files you copied
to the subdirectory 'upgrade' of your transport directory, the
reason may be that these log files are not complete or got
corrupted somehow.
Since that would mean that SAPup cannot handle these log files
you had better remove the given file (or at least rename it).
Then repeat the phase.
#PE0648
Moving one or more files failed. To find out the file names, refer
to the preceding lines. Check the permissions for the source
and target directories given. Also check if the given files
are already in target directory and check their permissions.
It must be possible to overwrite the files in the target directory
and delete them from the source directory.
When you have corrected the permissions, repeat the phase.
#PE0649
Deleting one or more files failed. To find out the file names,
refer to the preceding lines. Check the permissions for the
specified source and target directories. It must be possible
to delete the specified files from the source directory.
When you have corrected the permissions, repeat the phase.
#PE0650
Copying one or more files failed. To find out the file names,
refer to the preceding lines. Check the permissions for the
specified source and target directories. If the files already
exist in the target directory, it must be possible to overwrite
them. In addition you need write permission on the target
directory. When you have corrected the permissions, repeat the
phase.
#PE0651
The file 'UPGRADES' in subdirectory 'upgrade' of your
transport directory should contain a table of contents of the
subdirectories of 'upgrade'. SAPup tried to write a new entry
into the file 'UPGRADES' and failed.
Check the permissions for this file (and all directories
in the path of that file).
When you have corrected the permissions, repeat the phase.
#PE0652
The file 'UPGRADES' in subdirectory 'upgrade' of your
transport directory should contain a table of contents of the
subdirectories of 'upgrade'. SAPup tried to read the contents of
that file but failed.
Check the permissions for this file (and all directories
in the path of that file).
When you have corrected the permissions, repeat the phase.
#PE0653
The file 'UPGRADES' in subdirectory 'upgrade' of your
transport directory should contain a table of contents of the
subdirectories of 'upgrade'. During writing to this file an
unexpected error occurred.
Try to repeat the phase. If the error recurs, contact SAP
Local Support.
#PE0654
SAPup failed to open the given directory to read its contents.
Check the permissions for the given directory and repeat
the phase.
#PE0655
SAPup failed to set the working directory to the given value.
Check that the directory exists, check the permissions for the
directory, and repeat the phase.
#PE0656
SAPup failed to create the specified (sub-)directory.
Check that all directories in the given path exist, check their
permissions, and repeat the phase.
#PE0657
The specified file could not be opened for reading.
Check the permissions for the file and repeat the phase.
#PE0658
The file 'ADJUSTPRP.LOG' in subdirectory 'log' of your
upgrade directory could not be opened.
Check the permissions for the subdirectory and the file
if it already exists. The user performing the upgrade
must be able to write to that file and must have create
authorization for the directory.

Correct the permissions and repeat the phase.
#PE0659
During phase ADJUSTPRP command files of requests might be imported
in your system. The buffer of your system is used for that.
The buffer is the file '<SID>' (that is, it has the
same name as your SAP System) in subdirectory 'buffer'.
To make sure that the contents of this file remain untouched
during that phase, the file is copied under the name 'SAP'
at the beginning of the phase. This copy procedure failed.
Check the permissions for the files 'SAP' and '<SID>' in the
subdirectory 'buffer' of your upgrade directory and the permissions
for the subdirectory 'buffer' itself. Change the permissions
as required. The user performing the upgrade should be
able to copy the file '<SID>' onto the file 'SAP'.

IMPORTANT: Do not copy the files yourself!

Repeat the phase.
#PE0660
Read log file 'ADJUSTPRP.LOG' in subdirectory 'log'
of your upgrade directory. There you will find a detailed description
of the copy procedure that failed.
Check and correct the permissions for the affected files and
directories. It is possible that the source file does not exist.
In that case, try to reconstruct the file and check the entries you
made during phase ADJUSTPRP. The entries are logged in the file
'ADJUSTPRP.LOG'.
To reconstruct the file, proceed as follows:
1) Determine the name of the corresponding request
   for example: file K904711.C11 --> request C11K904711
2) Log on to one of the application servers of the source
   system (in this case, C11) as <sid>adm of the source system.
3) Change to subdirectory 'bin' of the transport directory.
4) Execute 'tp createinfo <name of the request>'
   for example: 'tp createinfo C11K904711'
See also Note 51046.
#PE0661
Read log file 'ADJUSTPRP.LOG' in subdirectory 'log'
of your upgrade directory. There you will find a detailed description
of the read procedure that failed.
Check that the specified file exists and that its permissions are
correct. In addition the file must be a valid 'cofile'. Check this
by executing
tp showinfo <name of the request>
from the subdirectory 'bin' of the upgrade directory.
To find out the <name of the request>, take the last three letters
of the file name and shift them to the beginning of the name. Then
remove the '.' at the end (for example: K904711.C11 -> C11K904711).

Repeat the phase.
#PE0662
Read log file 'ADJUSTPRP.LOG' in subdirectory 'log'
of your upgrade directory. There you will find a detailed description
of the copy procedure that failed.
Check and correct the permissions for the respective files and
directories. It is possible that the source file being copied does
not exist. Try to reconstruct that file in this case or
double-check the entries you made during phase ADJUSTPRP. You will
find these entries logged in the file 'ADJUSTPRP.LOG' as well.
To reconstruct that file, proceed as follows:
1)  Determine the name of the corresponding request
    for example: file R904711.C11 --> request C11K904711
             or: file D904711.C11 --> request C11K904711
2)  Log on as user <sid>adm of the source system at OS level of one
    of the application servers of the source system (here C11).
3)  Change to subdirectory 'bin' of the transport directory.
4a) If the first letter of the missing file is an 'R',
    execute 'tp r3e <name of the request>'
4b) If the first letter of the missing file is an 'D',
    execute 'tp sde <name of the request>'
See also Note 51046.
#PE0663
Read log file 'ADJUSTPRP.LOG' in subdirectory 'log'
of your upgrade directory. There you will find a detailed description
of the procedure that failed.
It was a call of the form 'tp addtobuffer <request> <SID>'. The value
of the variable <request> can be found in the log file. <SID> is the
name of your SAP System.
Also check the log file 'ADJ_tp.ECO' in subdirectory
'log' of your upgrade directory.

Repeat the phase.
#PE0664
Read log file 'ADJUSTPRP.LOG' in subdirectory 'log'
of your upgrade directory. There you will find a detailed description
of the procedure that failed. Writing formatted information to a file
failed. This information is needed at a later stage of the
upgrade. Check that the specified file exists and that its permissions are
correct. Also check whether the user performing the upgrade is able to	
create the file in the specified subdirectory.

Correct the permissions and repeat the phase.
#PE0665
Read log file 'ADJUSTPRP.LOG' in subdirectory 'log'
of your upgrade directory. This contains a detailed description
of the procedure that failed.
The generation of a transport profile in subdirectory 'bin' of
your upgrade directory failed. Check that the specified file exists
and that its permissions are correct.
Also check whether the user performing the upgrade is able to	
create the file in the specified subdirectory.

Correct the permissions and repeat the phase.
#PE0666
During phase ADJUSTPRP, you decided to use some transport requests
for automatic adjustment of your modifications during the
upgrade.
The SAP System must be informed of the contents of these requests
using the command 'tp cmd all <SID> u1'. The result
was not as expected. The error situation should be well
described in the following files listed in order of detail.
Read these log files and try to resolve the problem.
log files:
  ADJUSTPRP.LOG
  SAPup.ECO           (Only the last few lines)
  ADJUSTPRP.ELG      (Points to the following files:)
  ???L??????.<SID>   (Files with generic names following the rule:
                      3 arbitrary letters, one 'L', 6 arbitrary
                      letters, one '.', name of your system)

#PE0667
During phase ADJUSTPRP command files of requests may be imported
in your system. The buffer of your system is used
for this. The buffer is the file '<SID>' (that is, it has
the same name as your SAP System) in subdirectory 'buffer'.
The contents of this file should remain untouched during that phase.
Therefore, this file is copied to the name 'SAP' at the beginning of
that phase. The copy procedure to copy the file 'SAP' back to
'<SID>' failed.
Check the permissions of the files 'SAP' and '<SID>' in the
subdirectory 'buffer' of your upgrade directory and the permissions
of the subdirectory 'buffer' itself. Change the permissions
so that the user performing the upgrade can copy the file 'SAP'
to the file '<SID>'.

IMPORTANT: Do not copy the files yourself!

Repeat the phase.
#PE0668
You cancelled the action.
Proceed as planned.
#PE0669
Read log file 'ADJUSTPRP.LOG' in subdirectory 'log'
of your upgrade directory. The status of the phase is explained
there in detail.
You expected to find a list of transport requests. This list has
not been found by SAPup. See also Note 51046. Try to configure your
environment as described in this Note.
If SAPup searched the wrong directory for the request list,
it could be that the value of the parameter 'DIR_TRANS' as found in
the SAP profile used by SAPup was wrong.

Reconfigure your environment and repeat the phase.
#PE0670
Read log file 'ADJUSTPRP.LOG' in subdirectory 'log'
of your upgrade directory. The status of that phase is explained
there in detail.
SAPup read a request list but you are missing request(s) that do not appear
in that list.
See also Note 51046 to adjust your environment.
If SAPup searched the wrong directory for the request list
it could be that the value of the parameter 'DIR_TRANS' as found in
the SAP profile used by SAPup was wrong.
Another possibility might be that the missing request was never exported
successfully by SAPup. You can redo that export if
a) the source system of that request has been upgraded successfully
   to the target release of the current upgrade
b) the upgrade directory of the source system is still available
Log on as <sid>adm of the source system in the subdirectory 'bin'
of the respective upgrade directory and execute the following
command:
../exe/SAPup export TA=<tr> TYPE=<type> LOG=<logname> REL=<release>

 where
 <tr>        : is the name of the request (for example: C11K904711)
 <type>      : is the name of the transaction used to adjust the
               objects contained in that request (SPDD or SPAU)
 <logname>   : is the name of the log (your choice)
 <release>   : is the correction level at which the request has
               been created (for example, 31G)

Reconfigure your environment and repeat the phase.
#PE0671
Internal error in function 'SAPup_prepare_adjustimp'
of the executable SAPup. Contact SAP Local Support referring
to error number: 'PE0671'.
#PE0672
Internal error in function 'SAPup_prepare_adjustimp'
of the executable SAPup. Contact SAP Local Support referring
to error number: 'PE0672'.
#PE0673
No error, additional information only.
The exit code is used in two ways.
If it is lower that zero, a particular error is encoded.
If it is greater than or equal to zero, it means that
everything is OK and the number refers to the number of relevant
transport requests.
#PE0674
An unknown statement class or type was given. This points to a severe
problem with the internal or external phase list. Contact the support.
#PE0675
To detect tables that have to be copied again during the downtime, data
base triggers are created.

To deal with failed trigger creation, error tags are put in the log file
to identify the corresponding table.

Here an internal error has occurred, please contact the support.
#PE0700
Unexpected failure of "tp showbuffer buffer=<SID>". Try to
restart program SAPup.
#PE0701
Unexpected failure of "tp modbuffer buffer=<SID>". Try to
restart program SAPup.
#PE1000
SAPup did not find substitution tables in table PUTTB.
The possible reasons are:
 a) The previous phases did not complete successfully.
 b) The SAP System to which previous phases imported to
    differs from the system table PUTTB is read from. In this
    case, you entered the wrong name for the gateway server
    or service. Correct your input with
    "SAPup set ddicpwd"        or
    "SAPup set stdpar"
#PE1001
The upgrade terminated and the System is in a
state in which the upgrade cannot be continued.
Reset your System from backup and restart the upgrade
from the beginning by removing log file SAPup.log.
#PE1002
The upgrade has brought the system to a state
where this phase can no longer be executed.
You might have reached this phase by entering a
password or you restored a backup made before
phase 'DIFF_CALC' and then started SAPup without
selecting 'proceed'.
Start SAPup again without password / with 'proceed'.
#PE1003
The upgrade has not yet reached this phase. It is
impossible to start this phase now. You may have entered
it by password.
Start SAPup again without password.
#PE1005
SAPup could not log in to your SAP System. There are several
possible reasons for this error:
 a) Your central SAP System instance is not running
 b) Your gateway server process exited
 c) You entered the wrong password for SAP System user DDIC
 d) You entered the wrong hostname for the gateway
    server process
 e) You entered the wrong gateway service name

Check reasons a) and b) and restart this phase.
If the login failed for one of the other reasons,
correct the input with
"SAPup set ddicpwd"        or
"SAPup set stdpar"
#PE1006
SAPup could not read the names of the substitution tables
from your SAP System.
The SAP System function module called does not exist.
 - Log on and check system status.
 - You may have entered the wrong name for the gateway server
   or service. In this case, correct your input with
   "SAPup set ddicpwd"        or
   "SAPup set stdpar"
#PE1007
SAPup could not test whether table conversions are necessary
for Basis tables. The SAP System function module called does not
exist. Log on and check system status.
#PE1008
If SAPup proceeded with the upgrade at this point, the
displayed number of Basis tables would have to be
converted. This is because Basis tables were modified
although the SAP recommendation was not to do this.
>>> Before proceeding with the upgrade, you have to    <<<
>>>      call SAP Local Support!                       <<<
#PE1009
SAPup could not start the batch job in the SAP System.
The SAP System function module called does not exist.
Log on and check the system status.
#PE1010
SAPup could not create the named file in the named directory.
Check the permissions of the directory and the free space
in the related file system. Restart this phase.
#PE1011
SAPup got an error while writing to the named file in
the named directory. Check the free space in the related
file system. Restart this phase.
#PE1012
SAPup could not read the named file. Check if the CD
was copied and restart this phase.
#PE1015
The temporary nametabs for the substitution tables
could not be modified using RFC.
The SAP System function module called does not exist.
 - Log on and check system status.
 - You may have entered the wrong name for the gateway server
   or service. In this case, correct your input with
   "SAPup set ddicpwd"        or
   "SAPup set stdpar"
#PE1016
An error occurred for the stated number of tables, while
modifying temporary nametabs for the substitution tables.
The first of the tables is named in the error message.

>>>         Call SAP Local Support.         <<<
#PE1020
SAPup could not read the upgrade entry in table UVERS
from your SAP System.
The SAP System function module called does not exist.
 - Log on and check the system status.
 - You may have entered the wrong name for the gateway server
   or service. In this case, correct your input with
   "SAPup set ddicpwd"        or
   "SAPup set stdpar"
#PE1021
SAPup could not read the current database date and time
from your SAP System.
The SAP System function module called is not available.
 - Log on and check the system status.
 - You may have entered the wrong name for the gateway server
   or service. In this case, correct your input with
   "SAPup set ddicpwd"        or
   "SAPup set stdpar"
#PE1022
SAPup did not find an upgrade entry in table UVERS
The possible reasons are:
 a) the previous phases did not complete successfully.
 b) the SAP System previous phases imported to differs
    from the SAP System table UVERS is read from. In this
    case you entered the wrong name for the gateway server
    or service. In this case, correct your input with
   "SAPup set ddicpwd"        or
   "SAPup set stdpar"
#PE1024
During a remote function call (RFC), an error occurred.
Some standard errors are:
1) message         : ERROR SY047
--------------------------------
   The function module which has been called cannot be
   generated. Try to generate this module (transaction SE37).

2) message         : You are not authorized to logon to the target system
-------------------------------------------------------------------
   The password of user DDIC you entered in phase INITPUT is wrong.
   Leave SAPup and change the value with "SAPup set ddicpwd".

3) message         : ERROR       partner not reached
----------------------------------------------------
   The SAP System is not reachable via the gateway. One reason might
   be that the gateway service is not usable, another might be
   a missing gateway process. Last but not least, the SAP System
   could be (partially) down.

4) message         : ERROR DB094
--------------------------------
   The parameters of the report do not fit the parameters
   supplied by SAPup. Check the history of the report
   source in your system.

If function module SUBST_START_BATCHJOB or
SUBST_START_REPORT_IN_BATCH is called, some individual
return codes are important for analyzing the problem.
To see the detailed error message, choose CONTINUE.
#PE1030
A call to tp for creating an entry in DB table UVERS
failed. This table must contain one line for each upgrade
that is performed in the system.
Restart this phase.
#PE1031
Could not read tp's output when creating an UVERS entry.
This table must contain one line for each upgrade
that is performed in the system.
Check free space of the file system related to the
supplied directory. Restart this phase.
#PE1032
Could not create an entry in table UVERS.
This table must contain one line for each upgrade
that is performed in the system.
Check the free space on database. Restart this phase.
#PE1033
The upgrade status read via the gateway service
(RFC) is not the expected status. You may have entered the
wrong gateway service name or gateway hostname.
The gateway server must belong to the SAP System
you want to upgrade.
Check whether this is the case.
Correct your input with
   "SAPup set ddicpwd"        or
   "SAPup set stdpar"
#PE1034
The upgrade start time read via the gateway service
(RFC) is not the expected start time. It differs from the
start time SAPup wrote to the database.
You may have entered the wrong gateway service name or
gateway hostname. The gateway server must belong to
the SAP System you want to upgrade.
Check whether this is the case.
Correct your input with
   "SAPup set ddicpwd"        or
   "SAPup set stdpar"
#PE1035
The call to stop the SAP System succeeded. However,
afterwards, an RFC to the SAP System still worked.
This means that the SAP System is still
running. Stop the system manually and repeat
this upgrade phase.
#PE1040
The SQL script could not be executed by program tp.
The possible errors codes are:
1 : tp execution error
    -> Call SAP Local Support
2 : log file creation failed
    -> Check free space in the related file system.
       Restart this phase.
3 : SQL execution error
       Check existence of log files.
       If they do not exist, check free space in the
       related file system. Alternatively, check the files for
       SQL errors.
       Restart this phase.
4 : The SQL log file exists, but is empty.
       Contact SAP Local Support.
#PE1041
The output file of an SQL script could not be opened.
Check access permissions of the directory and free space
of the related file system. Restart the phase.
#PE1042
The database returned an SQL error during execution
of an SQL script by tp. This made it impossible to
test whether the new tables that are imported during
this phase already exist.
Restart this phase.
#PE1050
The call
           "tp lock_eu <SID>"          or
           "tp locksys <SID>"          or
           "tp unlock_eu <SID>"        or
           "tp unlocksys <SID>"
failed. Is your database running and functional?
It is possible that program tp does not exist or
cannot be executed.
#PE1051
The export of this command file failed.
Check the log file for error reasons.
#PE1052
The import of this command file failed.
Check the log file for error causes.
#PE1053
Cofile could not be added to buffer by tp.
Possible errors codes are:
1 : tp execution error
    -> Check whether program tp exists
       Check the log file for error causes.
2 : log file creation failed
    -> Check free space in the related file system.
       Restart this phase.
3 : error adding the cofile to the buffer
    -> check the log file for error causes.
#PE1054
Syncmark could not be added to buffer by tp
Possible errors codes are:
1 : tp execution error
    -> Call SAP Local Support
2 : log file creation failed
    -> Check free space in the related file system.
       Restart this phase.
3 : error during syncmark adding
    -> check the log file for error causes.
#PE1055
The call of 'tp mvntabs' failed.
Check the log file for error causes.
#PE1056
Cofile could not be created by tp.
The possible errors codes are:
1 : tp execution error
    -> Check whether program tp exists.
       Check the log file for error causes.
2 : log file creation failed
    -> Check free space in the related file system.
       Restart this phase.
3 : error during cofile creation
    -> Check the log file for error causes.
#PE1057
Modification of the buffer file failed. Possible
error codes are:
-1 : Creation of a temporary file failed
     -> Check free space in the related file system
-2 : Error during opening the buffer file.
     -> Check the existence and permissions of the
        buffer file.
-3 : Write error on temporary file
     -> Check free space in the related file system.
-4 : Write error on buffer file
     -> Check free space in the related file system.
-5 : The expected command file was not found in the buffer.
     -> Call SAP Local Support.
Restart this phase.
#PE1058
Modification of the buffer file failed. During the attempt
to delete a transport request from this buffer, an error
occurred.
The possible errors codes are:
+1 : The buffer does not exist
-1 : Error during file open (read/write)
-2 : Error during write to file
#PE1059
The tp-buffer printed could not be modified by tp.
The possible error codes are:
-1 : Error during execution of tp
-2 : Creation of stdout file failed
-3 : Error recorded by tp in stdout file
     -> read the output of tp in this file
#PE1060
SAPup could not find any substitution tables in the database.
You may have started this phase by entering a password
after having executed it.
Call SAP Local Support.
#PE1061
The SQL script could not be executed by program tp.
Therefore, the table switch might be incomplete.
The possible errors codes are:
1 : tp execution error
    -> Call SAP Local Support
2 : Log file creation failed
    -> Check free space in the related file system.
       Restart this phase.
3 : SQL execution error
       Check free space in the related file system
       and restart this phase.
If this phase fails more than once, call SAP
Local Support.
#PE1070
SAPup could not schedule the specified batch job.
In the case of errors 1, 13, 20, 23, and 27,
there are problems with the SAP System instance,
the message server or service, the batch host
or the entered DDIC password.
Check syslog and restart the phase.
Correct wrong input with
   "SAPup set ddicpwd"        or
   "SAPup set stdpar"

Error code 10 indicates an erroneous load of the program being
started in batch. Fix the problem by generating the ABAP
load. If this works, the buffered load was out-of-date.
To find out the name of the program, see the error message.

For all other errors, call SAP Local Support.
#PE1071
The name of the batch server is not known. Call the
function module TH_SERVER_LIST using transaction SE37 ->
Test -> Execute and double click on LIST. The list of
hosts and SAP System services known to the message server are displayed.

If the list is empty, your message server will not run.
See trace file "dev_ms".

If a wrong hostname is displayed (for example, upper case instead of
lower case), change the host table of the operating
system.

If you mistyped the batch server name, correct this with
"SAPup set stdpar".
#PE1072
Scheduling the named batch job failed. The error codes are:

-1:
    The RFC login of SAPup to the SAP System failed. There are
    several possible causes:
    - The password of user DDIC is not correct ("not authorized")
    - The login language is not supported (= system language)
    - The host name of the application server is not known to
      the gateway.
    - The gateway (= G-Host plus G-Service) does not exist
      or is not reachable.

    Check all the parameters you entered. On the work directory
    of SAPup (the 'tmp' subdirectory), you find a trace file
    "dev_rfc" with notes on the cause of this error.
    If the trace is not detailed enough, proceed as follows:
    - Set "CPIC_TRACE=2" in the environment of SAPup
    - Activate the SAP System trace (rdisp/trace = 2)
    - Enable the gateway trace (RfcTrace=ON in SAPup.par)

10:
    The ABAP load cannot be executed. This may be a buffer
    problem. Try to generate the report in the SAP System.
    This will solve the problem or the program has a syntax
    error, which must be solved by SAP Local Support.

1, 13, 20, 23:
    Your system configuration does not allow you to schedule the
    batch job. Analyze your system for the availability
    of batch services, the message server, and the gateway.
    Look for problems reported in the trace files of the
    system (for example /usr/sap/C11/DVEBMGS00/work/dev_disp
    and dev_ms).

27, 28:
    The host name you specified as the batch host is not
    known to the message server or no batch service is
    available on that server. Test the function module
    TH_SERVER_LIST (SE37 -> Test -> Execute, double-click
    on 'LIST'). You get a list of application servers
    and their services known to the message server.

    If the list is empty, the message server is not running.
    To find out why, analyze trace file dev_ms. If the host name
    differs from that name you expected, change the
    host table of the operating system or correct the name of
    the batch host.

If any other errors occur, contact SAP Local Support.

Correct inconsistent input to SAPup with
"SAPup set ddicpwd"        or
"SAPup set stdpar"
#PE1073
This is an internal error. If the error can be reproduced,
call SAP Local Support.
#PE1074
Unable to insert or update the named report variant,
which is essential for the upgrade progress.

Check whether the error can be reproduced. If so, try to
delete the report variant before repeating.

User DDIC must be authorized to modify report variants.

Further hints are reported in the log file of this phase.
#PE1075
This is probably an internal error of SAPup. Other possible
causes are destroyed files in the upgrade directory or
a wrong version of SAPup being called by mistake.

Unpack the data on the CD "Kernel" again and start the
SAPup delivered with this CD. If the error recurs,
call SAP Local Support.
#PE1076
This error was triggered after three unsuccessful attempts
to read the job status of the named job via RFC.

If the SAP System is running correctly, check the job
status manually and wait until the job is finished. Exit
SAPup and start the program again.

However, the SAP System is probably not running. In this case,
restart the SAP System, check the system status, and repeat
the upgrade phase.
#PE1077
Return code -1 indicates an RFC login failure.
There are several possible causes:
- The password of user DDIC is not correct ("not authorized")
- The login language is not supported (= system language)
- The host name of the application server is not known to
  the gateway.
- The gateway (= gateway host plus gateway service) does not exist
  or is not reachable.

Check all the parameters you entered. The SAPup work directory
(the 'tmp' subdirectory) contains a trace file
"dev_rfc" with information on the cause of this error.
If the trace is not detailed enough, proceed as follows:
- Set "CPIC_TRACE=2" in the environment of SAPup
- Activate the SAP System trace (rdisp/trace = 2)
- Enable the gateway trace (RfcTrace=ON in SAPup.par)

Correct inconsistent input to SAPup with
"SAPup set ddicpwd"        or
"SAPup set stdpar"

Return code -6 appears when no more memory can be allocated
for a new internal table of SAPup. Stop all unnecessary
processes or increase the virtual memory available (extend
the swap space).

#PE1078
The specified report has to write a log file to the 'tmp'
subdirectory with a name conforming to the pattern specified.
A missing log file indicates a severe error.

Check the status of the batch job started last.
If the job did not terminate successfully, analyze the
cause (using the SYSLOG), and remove the errors.
If the job ran successfully, the job could not write to the
upgrade directory, most likely because this directory is
not mounted on the host where the job has been started.
Alternatively, correct the input of parameter BATCHHOST.

Before you can continue the upgrade, the report must
have executed successfully.
#PE1080
SAPup could not check the correctness of table indexes.
The called SAP System function module does not exist.
Log on and check the system status.
#PE1085
The listed indexes were found in the database. Each line
contains the index name following the conventions:
 10-character table name plus 3-character index extension
and
 10-character table name plus 3-character index extension
    plus "X"
for one index extension.
This is not consistent with the ABAP Dictionary and must be
repaired at database level. During subsequent steps of the
upgrade, one of the two index names in each
line has to be unused, because one of them must be used for
the set of substitution tables and your database system cannot
handle duplicate index names on different tables.

Log on to your database and check the listed indexes. Remove
the indexes that lead to inconsistencies.
Note: It is possible that such an index was created on a
      table other than the one listed.
#PE1090
Severe error during log file analysis. The possible error
codes are:
         2       : check accumulated errors in the
                   log file (return code > 8)
	 1       : check accumulated single errors in the log file
	-1       : no log file found - check free space on file systems
	           and check your SAP System status
	-2 to -4 : internal error - contact SAP Local Support
	-5 to -6 : error when appending files or removing a file -
                   check free space in upgrade file systems
	-7       : No line was found in the analyzed log files
	           Check whether the process that produced this file
                   was aborted
        -8       : I/O errors occurred during log file analysis.

For positive error code, look into the summary file of this analysis.

The logfiles can be given as a pattern.
The meaning of the pattern is the following (f.e.: "^DS.....\.SID$"):
  ^ : stands for the beginning of the line
  $ : stands for the end of the line
  . : stands for exacly one arbitrary character
  \ : escapes the following sign.
      the pattern '\.' is f.e. one dot '.',
      the pattern '\\' is one backslash '\'.
#PE1091
At least one error was found in the log file(s). An accumulated list
of the errors is to be found in the specified file. Check the
error(s) and restart the phase.
#PE1092
For at least one object an error was found in the log file(s).
They are accumulated in the named file. Check the error(s) and
restart the phase.
#PE1093
At least one error was found in the log file(s).
They are accumulated in the named file.

Depending on the report being called, it may be possible to ignore
the error(s). For information on the error, refer to the phase description
in the upgrade manual. If you do not find any information on the error
message, call SAP Local Support.
#PE1100
Error detected at execution of mass import program.
For information about how to interpret the return code,
refer to your operating system manuals.
#PE1110
The specified file could not be renamed for saving.
Check the free space on the related file system.
#PE1120
The log file that should have been created by the started
batch job does not exist. It is possible that your
batch server has no access to the upgrade directory.
Check this and restart this phase.
#PE1121
The started batch job terminated abnormally.
Maybe your batch server has no access to the
upgrade directory. Check this and restart this phase.
#PE1122
The started batch job terminated abnormally.
Analyze the short dump in the system (start with SM37).
Log on to your SAP System and check the SYSLOG (SM21).
#PE1130
No space request has been evaluated. Start
report RSVTRSUM in the SAP System (SE38) and try
to analyze the error condition.
#PE1140
An error happened when reading file names from the named
directory. Check access permissions and restart this phase.
#PE1150
The file characteristics of the files in the named directory
cannot be read. If the directory is on a CD ROM, check that
the CD has been mounted.
#PE1160
The displayed file contains free space requests for your
database without the dynamic part calculated in this phase.
During read of this file, an error occurred.
-1 : Unable to create internal table
-2 : Unable to append a table row
-3 : Unable to free the internal table
-4 : Input file is missing or has wrong permissions

Try to extract the file from the CD archives manually.
#PE1161
The displayed file contains the names of all tables
that will be converted during this upgrade. During read
of this file, an error occurred.
-1 : Unable to create internal table
-2 : Unable to append a table row
-3 : Unable to free the internal table
-4 : Input file is missing or has wrong permissions

Try to extract the file from the CD archives manually.
#PE1162
The new space request file cannot be written.
The return codes have the following significance:
-1 : Unable to open the file
-2 : Write error on file
-3 : Unable to create an internal table

Try to restart the phase. If the error is
reproducible, call SAP Local Support.
#PE1170
The Basis source release could not be read correctly
from the database.
Possible causes of this problem are:

 - Errors have been ignored in earlier phases

 - The environment variables for the database software
   are not set correctly. In this case tp has read
   inconsistent values from the database. Check
   if the output of 'tp getdbinfo <SAPSID>' contains lines
   that start with string 'COMPVERS'. If these lines
   exist, check the database environment variables
   as described in the upgrade manual. In addition, check the
   login scripts for user <sapsid>adm.
   NOTE: If this problem is found directly after an
         upgrade to ORACLE 8.0, the database environment
         variables are probably not set correctly.
         Correct these variables (and the login scripts) and
         restart the database.

#PE1200
Some of the data transfers to transparent tables terminated
abnormally. Log on to the SAP System and check the states
of the batch jobs named RSVTRCPY_<number> using transaction SM37.
In addition, check the syslog using transaction SM21.

Using transaction SE16 or SE17, check table VTRUM which
contains the names of all tables to be transferred using
transaction SE16 or SE17. The transfer has been aborted
for tables where field VTRUM-STATUS is set to 'A'.

#PE1201
         NOT USED YET
Not all table data could be transferred because all started
batch jobs aborted. The most likely reason is that you
have inconsistent data in some of the tables (for example, BLANKs
in numeric fields).

You do not have to deal with the tables with inconsistent data
at this point. You can repair them at the end of the
upgrade when the system is back in production. In this case,
these tables are not converted to transparent ones now.
This has no effect on your system apart from impairing
performance. SAPup will recognize that these tables were not
transferred and will request you to correct the causes of the
errors when your SAP System is back in production.
( To correct these errors, you will have to stop your
  SAP System, lock it, and start it again. You can wait	
  to do this until you have sufficient time.)

If you have enough time to analyze the causes of the
errors now, we recommend that you do so. Then you will
not need to restart the system again after the upgrade.

In this case, log on to the SAP System and check table
VTRUM, which contains the names of all the tables to be
transferred. Use transaction SE16 or SE17 for this.
The transfer was terminated for tables where field
VTRUM-STATUS is set to 'A'.

   >>> CAUTION: never modify table VTRUM <<<

Check the system log.

Use transaction SM37 to check the aborted jobs named
RSVTRCPY<number>. You will find the description of the
error that caused the job to abort in the job's log file.
#PE1210
The data on this language CD does not match the
SAP System source release. For the correct language CD, refer to
the upgrade manual.
#PE1211
An internal error occurred during validation of the
mounted language CD. Check carefully that the
correct CD is mounted. If this is the case, call SAP
Local Support for assistance.
#PE1212
The specified directory was not found. For each language,
a different subdirectory has be found on the CD. Please
confirm the content of your language CD and try reading
the data once more.
#PE1213
The data on this language CD does not match the upgrade data.
For the correct language CD, refer to the upgrade manual.
#PE1214
The data on this language CD does not match the upgrade data.
For the correct language CD, refer to the upgrade manual.
Please note that you need different CDs for the repository
switch method and the delta import method.

The language data must fit the requirements of the target
release. You cannot use old language CDs.
#PE1220
Instead of the requested number of characters, an error code
was returned when writing to the specified file.
Check the file system that the file is written to.
#PE1221
Error when selecting between a number of different options.
The return codes have the following significance:
-1 = user canceled operation
-2 = internal error in user interface
-3 = internal error in function call
-4 = error during memory allocation
#PE1222
A file containing an internal table of SAPup was not found.
Call SAP Local Support. The upgrade cannot be continued
without this data.
#PE1223
The return values are:
-1 = A file list is missing from the PUT directory
-2 = memory allocation error
-3 = operator canceled because of error messages
#PE1224
Login via RFC failed. Usually, this is caused by a
an SAP System not running. In some phases of the upgrade,
this could be the correct status for the System, that is,
RFC login must fail at this point.
If this is the case, ignore the error message.
#PE1225
The status of an SAP System batch job could not be evaluated by RFC.
There are two probable causes:
1) The gateway service is not available,
   for example, the gateway server has terminated or was not
   started.
2) The System cannot be reached, for example because of a system
   shutdown or a change to the DDIC password.
#PE1226
One or more batch jobs that were started by SAPup have terminated.
Analyze the cause of this using transactions SM21 (SYSLOG)
and SM37 (batch administration).
After you removed the cause, repeat this phase.
#PE1230
Usually, the lock is caused by batch jobs which were
scheduled in an earlier language import. Delete
these jobs and start again.
#PE1231
Call SAP Local Support.
#PE1232
The data extracted from the language CD is incomplete or
does not match the desired upgrade. Start by checking that
the directory can be reached from the batch server. If this
is the case, check the CD label.
The data files on CD are named "TEXT<L>..." and "DOCU<L>..."
with <L> = language identifier. These data files must
exist for all languages together with all control files
located on the same directory on CD.
#PE1233
The reason for the failed scheduling of the batch job
might be reported in the SYSLOG of your SAP System.
This problem is often caused by user DDIC not having
the correct permissions for scheduling batch jobs.
#PE1234
Exit SAPup and start this phase again with "init".
#PE1235
The tools to change your database mode received error
messages. Start by trying to repeat the phase. If this
does not help, call SAP Local Support.
#PE1239
The add-on installation or the upgrade which you are
currently running require another add-on to be installed
first. Please install this add-on with the required version
before you continue with the original action. If the
required add-on version contains a pattern ("*"), any
version is allowed, which matches the pattern.
#PE1240
The SAP System add-on CD inserted contains no data
that can be used for this upgrade.
The CD contains a catalog "R3ADDON.PAR" which lists all update
packages on this CD. The validity of each update package
may be defined. To see the reason why a package has been
rejected, see the phase log file.


You probably require a different add-on CD.

If you are uncertain, contact SAP Local Support.
#PE1241
Not all parameters required to include an SAP System add-on in
the upgrade are defined. SAPup needs
- add_on_rl                (version)
- sap_target_rl            (SAP System target release)
- import_token             (description of archives)
- full_task                (request list of all objects)
- delta_task               (request list of the objects changed)
#PE1242
The archive directory of add-on data could not been found.
Call SAP Local Support.
#PE1243
Error unpacking a compressed file listed in the specified
archive directory. Unpacking the archives is a prerequisite
for the update of the relevant add-on software.
Call SAP Local Support.
#PE1244
The specified add-on product is registered in your SAP System,
but no update package has been integrated into this upgrade.
Each add-on supplement CD contains a catalog "R3ADDON.PAR",
which contains all update packages on this CD. For each				
package, some conditions may be defined that specify
the validity of the update package. To see the reason why
a package has been rejected, see the phase log file.

If you continue with the upgrade, all add-on data will be
lost. If you are uncertain how to proceed, call SAP Local Support.
#PE1245
The SAPup you are using is corrupted. Call SAP Local
Support.
#PE1246
Not all the necessary parameters for installing or updating
an SAP System add-on product are defined. SAPup requires
- add_on_id                (name)
- add_on_rl                (version)
- delta_task               (request list of the objects changed)
#PE1247
A request has been found that could not be assigned to an
add-on product. This is an internal error or some data
is corrupted. Call SAP Local Support.
#PE1248
No requests have been found for the designated add-on product.
This is an internal error or some data is corrupted.
Call SAP Local Support.
#PE1249
To keep an add-on product, the object list
of the installation is required. The transport request is
read from column 'Fulltask' or 'Deltatask' of table AVERS,
with priority for 'Fulltask'. In this case, the AVERS entry
does not contain any name of a transport request.
#PE1250
The addition of two free space requests for the database
system failed. The return codes have the following significance:
-1 = Unable to open the file displayed.
-2 = Unable to create an internal table.
     This is probably a memory allocation problem
-3 = Error during write to the file displayed.
     This is probably a hardware problem.
#PE1251
The addition of two free space requests for the file
system failed. The return codes have the following significance:
-1 = Unable to open the file displayed.
-2 = Unable to create an internal table.
     This is probably a memory allocation problem
-3 = Error during write to the file displayed.
     This is probably a hardware problem.
#PE1252
The printed add-on software component is also listed as main
software component in this upgrade. This cannot be supported,
a software component is either a main or an add-on component.
Please contact the vendor of your add-on, with a prepared
upgrade the add-on product can be renamed.
#PE1253
One or more add-on products were found which are in the final
state of its installation but not closed yet. Finish the
installation using SAPup (sapupgrade) or transaction SAINT.
After this, you can continue the currently started
installation or upgrade.
#PE1255
The buffers of your central SAP System instance must be validated
automatically during the upgrade. This is controlled by
the parameter "rdisp/bufrefmode" in your instance profile.
The DEFAULT profile usually contains this parameter too.
Change the value in the instance profile or DEFAULT profile
from "exeoff" to "exeauto", that is change it to

"sendoff,exeauto"       or
"sendon,exeauto"

Do not forget to restart the system afterwards!
#PE1202
Data cannot be imported to a client that is locked
against SAP System upgrade during the upgrade. Such a
client is unusable after the upgrade and cannot be rebuilt.

To remove a lock against SAP upgrade, use transaction SM31.
To do so, call transaction SM31, enter table name T000,
and choose 'Maintain'. Then choose the locked client by
double-clicking. Under the title 'Restrictions' you can
set the button 'No SAP upgrade in customer client' to	
'not chosen'. Afterwards save your change and leave transaction	
SM31.
#PE1260
This software update requires a certain patch level. Some
Support Packages or other types of patches are missing.
Apply the correct patch level from the OSS system
or SAPNet using transaction SPAM.
#PE1261
This software update requires a certain patch level. It is
essential that you import the requested Support Packages, etc.
before you continue. Support Packages are imported from the
OSS system or SAPNet using transaction SPAM.
#PE1262
Unconfirmed patches and Support Packages may cause inconsistencies.
Revoke or confirm the patches using transaction SPAM.
#PE1265
Before you can include a patch or packet of patches in the upgrade,
you have to load the patch data and attributes. For SAP
corrections such as Support Packages, HR Support Packages,
etc. use report RSSPDASS for this (has been RSSPAM13 in the past,
do not use anymore).
The report is imported together with the upgrade tools
in PREPARE. It runs on all start releases released for
this upgrade.
#PE1266
Saving the current status of patch inclusion failed.
Check the file system that contains the upgrade directory.

Error Codes:
-1 = Error during file open
-2 = Error during write to file
#PE1267
The inclusion of Support Packages for the target release needs
the patch requests which represent these packages. This is done
either by a naming convention, or with the help of the function
module DELIVERY_DESCRIBE_STATE_DIFF.

In your case, the requests could not be determined.

If the error message contains a Function Error Code, the
function module failed. In this case, most likely a SPAM update
is necessary to enable the calculation of the patch requests.
#PE1300
The specified locales are not installed on this machine, but
are required by the SAP System to support all your installed
languages in the selected language area.

The installation of locales is operating-system-dependent.
For information on installing these locales, contact
your hardware partner.
#PE1301
At the start of the upgrade, the system's code page was set to
a different value. Using another code page than originally set
can cause serious corruption of the table data in the database.
The data written with the old code page might be unreadable or
might be misinterpreted when the new code page is used.
Set the system back to the old code page or contact
SAP Local Support.
#PE1320
The specified component is not installed in your system. Please find
the supported components in the upgrade manual. You need a
different upgrade CD.
#PE1321
The release level of the specified component is too low.
For information on the supported component releases, see
the upgrade manual. You need a different upgrade CD.
#PE1322
The release level of the specified component is too high.
For information on the supported component releases, see
the upgrade manual. You need a different upgrade CD.
#PE1400
There is an inconsistency in the saved versions of the PREPARE
module. This error can only be corrected by SAP.
Contact SAP Local Support.
#PE1401
The status information file for PREPARE could not be read.
Check whether the file exists and whether write/read permission
is set for user <sapsid>adm.
If this is the case, there is a hardware problem.
#PE1402
The status information file for PREPARE could not be created.
Check whether you can create the file as user <sapsid>adm with
write/read permission for user <sapsid>adm.
This could be a hardware problem.
#PE1403
The status information file for PREPARE could not be written.
Check whether the file exists and whether write/read permission
is set for user <sapsid>adm.
If this is the case, there is a hardware problem.
#PE1404
An error occurred when selecting the PREPARE module. Repeat the
selection. If the error recurs, leave the selection screen
with 'cancel'. Then leave the program with 'exit' and start again.
If the error still occurs, the problem must be analyzed by SAP.
Contact SAP Local Support.
#PE1405
The requirements for starting PREPARE have not been fulfilled.
#PI1406
PREPARE performs checks before the upgrade to make sure that the upgrade
runs smoothly with as few user entries as possible. Before it can do
this, PREPARE must import some programs and tables.
These checks and imports are combined in PREPARE modules, which you can
select individually. PREPARE manages the PREPARE modules and checks
that they are executed in the correct order. You can select and execute
several modules at once, whereby the successful execution of some
modules is a prerequisite for the execution of others.
Some of the modules must have been successfully executed before the
upgrade is started. Other modules, which can be used for further
preparations, are optional and have a longer runtime. The mandatory
modules include those which are to be executed once only. All other
modules can be executed as often as required.

Note: Modules containing imports can impair performance in SAP System.
#PI1407
The attributes of the PREPARE module are called "mandatory", "execute
only once" and "predecessor" in the text that follows.
These attributes can have the following values:

  mandatory:
      yes :  the module must have been executed successfully before the
             upgrade.
      no:    module execution is optional for further processing.

  execute only once:
      yes :  under normal circumstances, the module should only be 	
             executed successfully once.
      no:    the module can be executed as often as required.

  predecessor:
    Name of the PREPARE module which must have been executed successfully
    before this module can be executed. This will be the case if the
    predecessors of a PREPARE module selected for execution are executed
    sequentially.


The following PREPARE modules are available:

Parameter input:
 The parameters which SAPup requires are prompted.
  mandatory:      	yes
  execute only once:	no
  predecessor: 		none

Initialization:
 The requirements for executing the dependent PREPARE modules are
 fulfilled.
  mandatory:      	yes
  execute only once:	no
  predecessor: 		Parameter input

Import:
 Programs and table entries needed for the PREPARE checks are imported.
 This can impact on performance in SAP System. This module should be
 executed only once.
  mandatory:	        yes
  execute only once: 	yes
  predecessor:		Initialization

Extension:
 Languages, add-on products, support packages for the target release 
 as well as the transports for automatic modification adjustment are
 selected.
  mandatory:        	 yes
  execute only once:	 no
  predecessor:       	 Import

Integration:
 The selected add-on products and support packages are integrated into
 the upgrade.
  mandatory:        	 yes
  execute only once:	 no
  predecessor:       	 Extension

Installation:
 The parameters needed for the shadow system are prompted and
 the preparations for the operation of the shadow system are performed.
  mandatory:             yes
  execute only once:     no
  predecessor:           Integration

General checks:
 Some of the requirements for the upgrade are checked. These checks
 are made again during the upgrade. They include checks for space
 in the database and file system, checks for open repairs, and so on.
  mandatory:         	yes
  execute only once:	no
  predecessor:          Integration

Activation checks:
 PREPARE checks whether activation errors should be expected during
 the upgrade. This includes customer tables using SAP data elements
 which are deleted during the upgrade and tables which have the same
 name as data elements. These checks are not repeated during the upgrade
 because of their long runtime. If you are developing in your system,
 we recommend that you execute this module again shortly before upgrading.
  mandatory:         	yes
  execute only once: 	no
  predecessor:      	Integration

Necessary checks for conversions:
 PREPARE checks whether you can reduce the time for conversions during the
 upgrade by performing manual actions before the upgrade or with an
 incremental conversion.
  mandatory:         	yes
  execute only once: 	no
  predecessor:    	    Integration

Optional checks for conversions:
 All the tables to be converted which are known to SAP are written to a
 file together with their size and table type (transparent, pooled, cluster).
 PREPARE also checks whether there is enough space on the database
 to convert the tables and create indexes. This space check takes the
 size of the tables in your system into consideration and is therefore
 more exact than the space check in the "General checks" module,
 requiring a longer runtime.
  mandatory:         	no
  execute only once: 	no
  predecessor:          Integration

Modification support:
 PREPARE determines the modifications in the system which have
 to be adjusted during or after the upgrade. You can display
 the results in SAP System with transaction SPDD/SPAU after executing
 the module.
 This module has a long runtime. As of source Release 4.5B,
 you can reduce the runtime of this module and of the upgrade.
 For more information, see the Upgrade Guide under 'Upgrade
 Administration' and 'Reducing Upgrade Runtime in Modified Systems'.
  mandatory:         	no
  execute only once: 	no
  predecessor:       	Integration

Pre-processing:
 PREPARE executes upgrade phases before the start of the upgrade to
 minimize their runtime during the upgrade. These phases are executed
 again during the upgrade to make sure that the action performed by these
 phases were complete.
 This module has a longer runtime.
  mandatory:         	no
  execute only once: 	no
  predecessor:       	Integration

#PE1408
Resetting PREPARE failed. Check whether
 - the database is running
 - tp can connect to the database with
   '/usr/sap/put/exe/tp connect <SAPSID> pf=/usr/sap/put/bin/TPPARAM'
   (for UNIX)
   '\usr\sap\put\exe\tp connect <SAPSID> pf=\usr\sap\put\bin\TPPARAM'
   (for NT)
#PI1409
A password is necessary if you want to ignore a PREPARE module with
status 'failed' or 'canceled'. Only use a password after an error
analysis with clear-cut results and after consulting SAP. Support cannot
be guaranteed if you do not consult SAP. Only a few cases are known where
it makes sense to ignore a PREPARE module with a password. On the other
hand, a large number of cases are known where this resulted in serious
inconsistencies, at worst rendering database recovery necessary.
#PI1410
Graphical representation of how the PREPARE modules are linked to one
another:

                     +---------------+
                     |Parameter input|
                     +---------------+
                             ^
                             |
                      +--------------+
                      |Initialization|
                      +--------------+
                             ^
                             |
                         +-------+
                         | Import|
                         +-------+
                             ^
                             |
                        +---------+
                        |Extension|
                        +---------+
                             ^
                             |
                       +-----------+
                       |Integration|
                       +-----------+
                             ^
                             |
    +----+-----+-------------+-+------------------+--------+-------+
    |    |     |               |                  |        |       |
+---+---+|+----+-----+ +-------+--------+ +-------+-------+|+------+-----+
|General|||Activation| |Necessary checks| |Optional checks|||Modification|
|checks |||checks    | |for conversions | |for conversions|||Support     |
+-------+|+----------+ +----------------+ +---------------+|+------------+
         |                                                 |
   +-----+------+                                    +-----+-------+
   |Installation|                                    |Pre-execution|
   +------------+                                    +-------------+

#PI1500
You cannot use the patch integration file that was read from CD or downloaded 
from the OSS to upgrade your system.

Download the file from the OSS that is valid for the configuration described 
above and execute 'repeat after download' again. If a valid file is not 
available, this may be due to the following reasons:

 - The desired upgrade is not supported. 
   Contact your SAP Local Support to confirm this.

 - This upgrade does not require a patch integration file. 
   Contact your SAP Local Support to confirm this. If you assume by mistake
   that the upgrade does not require a patch integration file, 
   your system is inconsistent after the upgrade, and you must reset the 
   system to the status it had before the upgrade.

The option 'repeat PREPARE module' lets you repeat the PREPARE module 
'Extension'. This is necessary, for example, if patches or add-ons that should 
have been included in the upgrade were forgotten during the first execution
of module 'Extension'. The patch integration file is only valid if all the 
patches and add-ons have been included.

The option 'reset PREPARE' lets you run a complete PREPARE again. To do this:
1. Choose 'reset PREPARE'. This stops PREPARE.
2. Call SAPup with the option 'reset prepare'. 
   This resets the data in the system.
3. Delete the contents of the upgrade directory, but not the upgrade 
   directory itself.
4. Start PREPARE again from the CD.

#PI1501
You cannot use the patch integration file generated in your system for the 
upgrade due to inconsistencies.

Try to regenerate this file and then choose 'repeat' to perform the check 
again.

The option 'reset PREPARE' lets you run a complete PREPARE again. To do this:
1. Choose 'reset PREPARE'. This stops PREPARE.
2. Call SAPup with the option 'reset prepare'. 
   This resets the data in the system.
3. Delete the contents of the upgrade directory, but not the upgrade 
   directory itself.
4. Start PREPARE again from the CD.

#PEAD01
Error reading the parameter file. Check whether the
files exist and have read/write permissions for user <sid>adm:
for UNIX:
         /usr/spool/sql/config/<SID>
         $DBROOT/wrk/config/<SID>
for NT:
         %DBROOT%\config\<SID>
#PEAD02
A database administration user is connected to the database. SAPup
must connect as administration user to finish the upgrade. Disconnect
the administrator user (utility or xcontrol) to allow SAPup
to proceed with the upgrade.
#PEAD03
A database action of SAPup as database administrator did not finish
correctly. For further information, see the utility log file
in directory /usr/sap/put/tmp.
#PEA04
A database action of SAPup as database administrator did not finish
correctly. The database connect was refused because of a wrong
user/password combination. Possible causes are as follows:
a: The database is not in warm mode
   Check the database state with :
         x_cons <SID> show stat
   If the state is cold start the database :
         xutil -U c restart
b: The user entry of the key 'w' of the XUSER file is not correct.
   Check whether you can connect the database :
         xquery -U w
   If you cannot connect to the database, correct the XUSER
   entry for user key 'w'.
#PEA05
A database action of SAPup as database administrator did not finish
correctly because the database is OFFLINE. Restart the database
with xcontrol or 'startsap db'.
#PE1409
The upgrade directory being used and the value of the profile parameter
DIR_PUT must be identical.

The upgrade tool failed to adjust this parameter dynamically in the system.

You have the following options:

1. Adjust the parameter manually in the default profile. You must restart
   the system afterwards!
2. Restart the upgrade from scratch. By using option
        -srvarg=/DSUService/abapupgdir=<DIR_PUT>
   for the DVD STARTUP script, the tool will use the current setting, so
   you don't have to restart the system.
#PE1420
Evaluation of the tables that have to be converted
externally using R3trans (download/upload) has failed.

The conversion cannot be performed using the ABAP systems
converter because the tables are of fundamental significance
to the current SAP System release and converting the tables would
destroy the System.

=> Do not convert online (causes irreparable corruption)

Try to fix the problem described with the return code.
If this fails, call SAP Local Support.

Meaning of the return codes:
 +1        Dump does not exist        (file not found)
 -1        Error during read          (check file system)
 -2        Illegal table header       (internal error)
 -5        RFC error during read      (check SAP System)
 -6        Write error on dump file   (check file system)
-10        Error during convert       (internal error)
-11        memory allocation error    (check virtual memory)
#PE1421
Saving to file of the list of all tables to be converted
externally (using R3trans) failed.

The conversion cannot be performed using the ABAP systems
converter because the tables are of fundamental significance
to the current SAP System release and converting the tables would
destroy the System.

=> Do not convert online (causes irreparable corruption)

Try to fix the problem described with the return code.
If this fails, call SAP Local Support.

Meaning of the return codes:
 -1        RFC error                  (check SAP System)
 -2        Illegal table header       (internal error)
 -3        Write error on dump file   (check file system)
-10, -12   Error during convert       (internal error)
#PE1422
The movement of tables from internal to external conversion
has failed (the function module SUBST_MODIFY_EXTERN_CNV_TABLE
is called).

The conversion cannot be performed using the ABAP systems
converter because the tables are of fundamental significance
to the current SAP System release and converting the tables would
destroy the System.

=> Do not convert online (causes irreparable corruption)

It is probable that the SAP System can no longer be
reached using RFC. Try to start the SAP System again.
If this does not help, please call the SAP Local Support.
#PE1423
SPAM_SET_STATUS: No help available
#PE1424
Reading from table PUTTB resulted in wrong data structure.
Most likely, the table PUTTB has got the wrong (old) format.
Please perform the following checks:

1. Check phases TOOLIMPD, MVNTAB_TOOL, TOOLIMPI, TOOLIMPM
   for possible errors.

2. Go to transaction se11 and display table PUTTB.
   use Menu 'Extras': 'database object > check' 
   and                'runtime object > check'
   to further analyse the error.

If the database object is consitent with the dictionary,
and the runtime object is inconsistent, there may be a
problem with the syncronisation.
In this case, check the parameter "rdisp/bufrefmode" in your 
instance profile. The parameter must be
"sendoff,exeauto"       or
"sendon,exeauto"
Do not forget to restart the system after changing this paramer!
#PE1430
The requested group of transport classes is not defined.
THis is caused by inconsistent control data, you may have
mixed files in the upgrade directory or the upgrade is in
a preliminary test state.
#PE1431
The tp call "tp getspacerequirements" failed for the printed
transport order. Please check the last written file with extension
.ECO or have a look into the tp SLOG file.

The feature has been implemented in release 4.6C
#PE1432
The meaning of the return codes are:
-1 = The printed log file was not found, please repeat the phase
     and check the file system where the upgrade directory is on.
-2 = Memory allocation failed. Please increase the virtual memory.
#PE1433
The meaning of the return codes are:
-1 = The script file under "bin" could not be opened for write
-2 = Error during write of script file 
-3 = Error during enhancement of script file
-4 = The script to select the clients from table T000 did not
     produce a result or the result is empty

Please try to repeat the phase.
#PE1434
The selection of relations between database object and
database container failed. The meaning of the return codes are:

-2 = No relations were found
-1 = The ouput file of the SQL script DBOBJLOC.<DBtype> is missing
 1 = Error during script execution
 2 = Unable to write the ouput file of the SQL script
 3 = Unable to execute the SQL script
 4 = The ouput file of the SQL script is empty
#PE1435
The calculation of the free space consumption out of the R3trans
volume data failed. The meaning of the return codes are:

 -1 = Memory allocation failure, increase the virtual memory
 -2 = The file containing all export relations is missing
      (control data are incomplete)
 -3 = Invalid table handle, repeat the phase
-11 = Memory allocation failure, increase the virtual memory
-12 = No relations between database object and database
      container found, repeat the phase
-31 = Error during file open for read, check your file system
-32 = Error during file open for write, check your file system
-33 = Unable to condense the free space consumption (internal error)
#PE1436
The upload of all package data located in the inbox of directory
DIR_EPS_ROOT transfers the package description into the database
of your system. Because all files are scanned, this may take
a while.

The upload has to be repeated, if new packages are downloaded
from the network or from CD.

Check the SAP profile parameter DIR_EPS_ROOT and the SYSLOG.
If you cannot repair the error, start report RSSPDASS as an
alternative to the upload performed by SAPup.
#PE1437
The package data have to be downloaded from the network or
from CD (into the inbox of directory DIR_EPS_ROOT) and
then uploaded to the database of the SAP system.

At least one of these steps has not been performed. SAPup asks
for the second step when repeating the phase. As an alternative,
start report RSSPDASS.
#PE1438
The package data can not be extracted to the upgrade directory.
Please repeat the download into  the inbox of directory
DIR_EPS_ROOT, the package (extension .PAT) may be destroyed.

The SAP system must have write access to the upgrade directory.

As an alternative, start report RSSPDASS.
#PE1439
The specified file does could not be read. The file ist part
of the shipment and is required to continue with the upgrade.

This could be caused by the following situations:
- The file is not readable by the operation system user running 
  the upgrade.
- The directory, where this file resides, is mounted from another
  computer. Check for NFS problems.
#PE1440
The upgrade installs an additional instance, whose SID is identical
to the productive system. The two systems differ only by the
instance numer. This number must be different from the productive
system (and from all other systems on this machine).

Please make sure that the instance number that you specify for the
shadow system is unique.
#PE1450
An inconsistency has been detected in your system, that needs to 
be fixes manually.

In tables TA<dba> and IA<dba> a logical container (TABART) is 
mapped to an existing container (TABSPACE) on the database.
The containers listed in the error message do not exist on the 
database.
A "create table ..." statement for a table using one of these
TABARTs will fail.

You need to map each TABART to an existing container.

On INFORMIX and ORACLE you can list the existing tablespaces (containers)
using sapdba.
On DB6 you can list the tablespaces using the call
db2 list tablespaces
Or you can call transaction db02.
#PE1451
A control file contains a macro like '$CDNR2PATH(3)' which will be
expanded to the path of the numbered CD where R3load (or another
tool) will find the data.

The problem is that less CD paths are defined, so the number cannot
be expanded.

There is a problem with the upgrade control files. Please contact
SAP support.
#PE1453
An ambiguous container mapping has been found in tables TA<dba>/IA<dba>:

The upgrade is shipped with predefined space requirements. This fixed part
is only given as container sizes. The container names will be mapped
to the actual containers in your system.

For some databases, we assume that tables and indexes for a given
tabart are in the same tablespace. This is not the case for the
aforementioned tabarts.

As a result, the predefined free space requirements cannot be mapped
uniquely to the corresponding containers.
 
If you ignore this, it may result in requirements that are too high for
some containers and too low for some other containers.

Alternatively, you can fix the mapping in tables TA<dba> and IA<dba>.

See also note 541542.
