Evaluating the Results of the Checks Roadmap Step

This chapter deals with some results of the Checks roadmap step.

Context

The results of the Checks roadmap step are listed in the log file CHECKS.LOG and displayed in the associated notification popup window that opens up once this roadmap step is completed. The entries in the window can be error messages, information, or prompts for user action. Carry out the required user actions before you can start with the Preprocessing roadmap step.

The file CHECKS.LOG is located in subdirectory <update directory>/abap/log.

Procedure

Check the entries in the dialog box and perform any measures required by the information it contains.

Most of the entries are self-explanatory. In the following, you can find information and troubleshooting procedures for entries that are not self-explanatory:

Message	Action
`Insufficient freespace in the database as follows:`	Release upgrade only: The new release needs more space in the database. The existing space in your database is not sufficient to import the data for the new release. For information about the extensions that you must make, see the table that follows the message in the dialog box. Add the space you need for any extra data that is created before you actually upgrade your system. SPS update: The existing space in your database is not sufficient for the update. For information about the extensions that you must make, see the table that follows the message in the dialog box. Add the space you need for any extra data that is created before you actually update your system. The procedure is described in Extending Free Space in the SAP MaxDB Database. Note Release upgrade only: Due to limited statistical data about table and index sizes, in rare cases the Software Update Manager may ask for more free space than is needed during the upgrade. This occurs especially for index tablespaces. In this case, report an incident to help us improve the statistics.
`In Release <rel> you applied the following unconfirmed patches to your system.`	There are unconfirmed Support Packages in your SAP system (such as Support Packages for technical components SAP_BASIS, or SAP_BW). To confirm these Support Packages, call transaction SPAM.
`There are dependencies between Basis Support Packages included in phase BIND_PATCH and the patch level of the target release kernel in directory <upgrade directory>/exe.` `The disp+work needs at least patch level <number> or higher.` `Please proceed as described in note 211077.`	A Support Package included in update requires a different patch level for the SAP kernel. Proceed as described in SAP Note 211077 .
`Change the permission of these executables:`	Note This entry is only displayed if you perform a release upgrade. You have to be able to overwrite the programs of the old SAP kernel so that you can copy the new SAP kernel to directory /usr/sap/<SID>/SYS/exe/run during the upgrade. The programs that are affected are in the following lines: `ERROR> No write permission for file <program file>.` Change the write authorization with: `chmod ug+w <program file>` If the program does not belong to the group sapsys, you have to either change the group or add user <SID>adm to the group temporarily. We do not recommend that you give write authorization to others, for security reasons.
`The following function groups (FUGR) are inconsistent. The TADIR entry (and the frame program) have no corresponding entry in the master table TLIBG.`	Note This entry is only displayed if you perform a release upgrade. Your SAP system contains customer function groups that have not been entered in table TLIBG. To enter the function groups in table TLIBG, call transaction SE80. If you do not fix the problem, the customer function groups are lost during the upgrade. In case of questions or problems, report an incident on component BC-DWB-TOO-FUB.
`No write permission on <file name>:`	The specified file in the directory of user <SID>ADM cannot be overwritten because the authorizations have not been set correctly or the owner of the file is not <SID>ADM. Correct this by changing the authorizations or the owner.
`Release these open transport requests and repairs:`	Caution If you ignore open repairs, you could lose modifications. Your SAP system contains locked SAP objects in open repairs or requests. The numbers of these repairs or requests are listed. We recommend that you inform the owners of open repairs or requests so that they release them. You can continue with the update until the REPACHK2 phase. In the REPACHK2 phase, all listed open requests and repairs have to be released. For more information, see Releasing and Confirming Open Repairs and Requests. Note If open repairs that do not belong to this system appear, then this system was created by a database copy. You cannot release these repairs in the normal way. To release these repairs, release all tasks and requests in the current system. Call the Workbench Organizer (transaction SE06). All locks created by repairs and requests not known to the system are deleted. The status of the affected tasks and requests changes in this case to RELEASED. To release and confirm these open repairs, you have to log on to the system with the name of their owner. The list in the dialog box contains these names.
`Restart logs of DB conversions found.` `Outstanding DB conversions found.`	Your SAP system contains outstanding conversions and restart logs of terminated conversions. Clean these up as described under Cleaning Up Terminated Conversions in the DB Conversion Phases.
`Unresolved request found in TRBAT.` `.......` `TRBAT entry indicates that a batch job is running.` `.......` `TRBAT entry indicates that a batch job has finished.` `.......` `Corrupted TRBAT entry found.` `.......`	The transport control program tp uses table TRBAT to communicate with the SAP system. Entries found in this table by the Software Update Manager can be the remains of terminated or running imports or exports. When you prepare the update, locate any entries left over from imports or exports that terminated and clean them up. Do not delete entries made by running imports or exports during production operation. First try to process the TRBAT entries from /usr/sap/trans/bin with the following command: `tp getprots <SID>` This does not affect any imports or exports that are still running. tp informs you about possible processing problems in the file SLOG<YY><WW>.<SID>. You can monitor this file using the following command: `tail -f /usr/sap/trans/log/SLOG<YY><WW>.<SID>` where <YY> is the year (two digits) and <WW> is the calendar week (two digits). To delete any entries in TRBAT that cannot be processed and that are no longer needed, call transaction SM31. In cases of doubt we recommend that you contact SAP Support, which can assess if an entry is still needed. For more information about the transport control program tp, see the SAP Help Portal for your SAP NetWeaver source release at http://help.sap.com.
`The following indexes <number> were read:`	Note This entry is only displayed if you perform a release upgrade. Indexes whose names are identical up to the 14th character were found in a table belonging to the substitution set. The 14th character is an 'X' in one of the two names and is empty in the other. This is an inconsistency and would result in an error during the import of the substitution set. The index with the 'X' as the 14th character can only have occurred in a previous upgrade or have been created outside the SAP system. For more information, contact your SAP consultant.
`The following database tables have names that are identical to names of Basis views. The views will be created in this upgrade. Therefore ...`	Note This entry is only displayed if you perform a release upgrade. Delivered views can have names identical to the names of customer tables in the SAP namespace. You have to delete these tables. If you need the table data, you should make a backup before deleting the tables.
`Open update tasks found; please clean them up`	Make sure that you have cleaned up the following by the JOB_RSVBCHCK_R, JOB_RSVBCHCK_D, or JOB_RSVBCHCK_D_MIG phase (during downtime) at the latest: All outstanding updates All outbound queue RFC calls All open data extraction orders If you are still in the preparation phase (before the beginning of the Preprocessing roadmap step) and therefore in production operation, you have to only delete the terminated updates. Recommendation We recommend that you clean up as many updates, RFC calls, and open data extraction orders as possible. Otherwise, you have to clean them up during downtime. To find terminated or outstanding updates, proceed as follows: Call transaction SM13. Delete the default values for the client, user, and time. Select all the update requests. To find outstanding outbound queue RFC calls, proceed as follows: Call transaction SMQ1. Delete the default values for the client. Make sure that the list of outbound queue RFC calls is empty. Otherwise, you might lose data in other systems (for example, in SAP BI). Make also sure that there is no open data extraction order in the system anymore. Otherwise, changes to the ABAP Dictionary structures could have the effect that data extraction requests can no longer be read after the import and their processing terminates. See SAP Note 1081287 for more information. Repeat these checks when production operation ends. For more information, see Isolating the Primary Application Server Instance. Caution If you have installed the PI plug-in, more information is displayed.