Hello Experts,
I am performing a upgrade of BW 3.1 to BW 3.5 and in the phase CHK_POSTUP I have received the following errors.
I am unble to understand this error, so please assist.
Error:
====
JOB_RDDNTPUR 25 errors
It asks to look at the LONGPOST.LOG file
Below are the contents of the LONGPOST.LOG file
=========================================================================
LOGPOST.LOG file start
=========================================================================
UPGRADEPHASE JOB_RDDNTPUR
1PEPU203X
> Messages extracted from log file "RDDNTPUR.PBW" <
Long text:
Cause
During the upgrade, a message relevant for postprocessing was written
to a log file. This message is not dealt with until the end of the
entire upgrade. The upgrade continues.
System Response
The upgrade stops in phase CHK_POSTUP. To create the reference to the
original log file, this message is generated by R3up.
What to do
Note the messages following this message and proceed according to the
instructions.
3PETG447 Table and runtime object "/BDL/CUST" exist without DDIC reference ("Transp. table")
Long text:
Cause
A runtime object was found for a table which is unknown in the ABAP
Dictionary. The table contains data, which is why, as a precaution, the
runtime object was not deleted.
Since there is a runtime object, this means the table was once created
in the ABAP Dictionary. The fact that the table can no longer be found
in the ABAP Dictionary could be due to the following reasons:
It is a customer-specific table which was created when the correction
system was switched off.
Depending on the history of your system, there may also be SAP tables
which were not deleted completely, or for which only the runtime object
was delivered without the related definition in the ABAP Dictionary.
System Response
What to do
RESET N1
Customer-specific tables
If it is a customer-specific table, and you still need the data, try to
restore the table in the ABAP Dictionary. Note the specified table type
when you do this (transparent table, pool table, and so on).
The table may still, for example, be contained in the version database.
You can access version management through the menu "Utilities" in the
in the ABAP Dictionary (transaction SE11). You may also still have a
copy of the system that still contains the table definition. You can
also display the runtime object and create the table according to the
field names, types and lengths specified in the definition. You can
display the runtime object in the menu "Extras" of the database utility
(transaction SE14).
Tables in the SAP namespace
Search for notes on these tables in OSS using the key words RDDNTPUR
and TG447.
3PETG447 Table and runtime object "/BDL/CUST_TREE" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/CUST_TREE_T" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/LOG_VIEW" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/MAINTAIN" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/MSGLOG" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/RFCDEST" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/RTCC_CUST" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/SAPOSS" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/SDCC_CUST" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/STAMP" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/TASKREP" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/TASKS" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/TASK_ATTR" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/TASK_CUST" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/TASK_CUST2" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/TASK_ICONL" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/TASK_ICONS" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/TASK_LOG" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/VIEWERS" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/BDL/_GENER_2" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/SDF/RZ20_TMPL_N" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/SDF/RZ20_TMPL_P" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "/SSF/PTAB" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "ZMATLOB" exist without DDIC reference ("Transp. table")
Long text: see above
=========================================================================
LONGPOST.LOG file end
=========================================================================
Please let me know what we can do about this, as I have read in the upgrade pdf it says that we can continue with the upgrade and resolve this later.
Thank you,
Kind regards,
Zaheer Shaikh