SAP Basis Tech Supports

Symptom
Issues which may occur with operating system release V5R4M0 will be collected together in this note
1. After an upgrade several work processes go into LCKW when starting the system. This can make logging-on difficult or even impossible. After some time you see SQL error -913 (SQL0913) occurring.2. You want to convert objects after an upgrade using ‘First Touch’. As a result, the performance becomes very poor or an ABAP short dump follows.3. You receive an ABAP short dump with the following error message: DBIF_DSQL2_SQL_ERROR The database reports -913.4. Application servers can no longer access the DB server5. You are using either your own or modified SAP reports, which contain no ‘ORDER BY’ clause in their SELECTs, nevertheless it is assumed that the records will be returned in primary key sequence.6. Problems may occur, especially in connection with BW table partitioning, due to the addition of new fields in the system catalog views7. SAP system cannot be started. In the WP joblogs there are SQL0189 errors (Coded Character Set Identifier 13488 not valid).8. MCH1210 occurs when creating tables or views9. Work processes show errors related to the memory-based database monitor, such as “Error CPF9898 in QQQSSDBM: DATABASE MONITOR HAS BEEN HALTED AND MUST BE CLEARED” or MCH0601 “Space offset x’80C3B28F’ or x’0000000000000000′ is outside current limit for object QQQDBMTR”.10.Systems with kernel release lower than 4.6DError ZDATE_ADJUST_FAILED with accompanying error message “zdate: strange database timestamp” occurs in systems with kernel release 3.1I, 4.0B and 4.5B after implementation of the latest CUM package.11. Many dumps of the following type (becoming increasingly frequent): DBIF_RTAB_TABLE_UNKNOWN
DBIF_RSQL_TABLE_UNKNOWN
DBIF_DSQL2_OBJ_UNKNOWN
In the ABAP short dump missing tables are reported.
for example: Table “ALGRPCUSMG ” unknown
Table “VRSX2 ” unknown.
Table does not exist on the database12. If a first installation of an SAP system is attempted directly after a new operating system installation, then the R3GROUP user may be set up with insufficient authorisation, which can lead to MCH1001 messages from CRTR3SYS at a later point in the installation.13. APYJRNCHGX will fail with message CPF7044 Reason Code 2 ( RC2 ) if journal receiver contains journal code entries F IZ14. Complex queries (often from BW systems) return an SQL0551 error although the user has the necessary authorisation for the access. Deleting the SQL-Package appears to solve the problem for the moment, but it may recur again later.15. Object QLGPGCMA.LOCALE is deleted during sapstart
Other terms
AS/400, i5/os, SQL0189, LCKW, lockwait, OS upgrade
Reason and Prerequisites
7. The CCSID check in the database has been tightened-up in V5R4M0.
8. An upgrade to V5R4M0 has been made from an earlier release. No new
SAP system was implemented since the operating system upgrade.
9. As of V5R4M0, IBM has enabled a plan cache dump to monitor the
database. The memory based monitor will no longer be maintained.
Solution
Points 1-3 : implement note444524
4. The PRPQ OptiMover is no longer supported by IBM. If you use this,
then this is the reason for the problem. Instead you must buy the
product OptiConnect from IBM. This is the licence program 5722SS1,
option 23. You will then be able to access the application server
for the database as before.
5. Correct the report(s) by adding the ‘ORDER BY’ clause to the SELECT
statements. If the clause is not specified then the records may be
returned in a random sequence. Even if the records are usually
returned in primary key sequence, you should not rely on this
happening.
6. SAP recommends recreating the system catalog views. See note 852158
for a description of the procedure to be followed.
7. The following LIB_DBSL patches (or higher) should be implemented on
the system
4.6D: LIB_DBSL Level 2092
6.40: LIB_DBSL Level 85
Starting with release 7.0, the change is always included.
8. See note 976837.
9. Install the PTF’s and patches as listed in SAP Note 1083218 and set
profile parameter as4/dbmon/classic=0 to use the plan cache dump
instead of the database monitor. Refer to SAP Note 1083218 for
further details.
10. The problem should be solved by PTF SI30812, once it is generally
available.
11. Proceed as described inSAP Note 530392.
12. See note 175852 for the solution.
13. Install the latest Infoapar. This will include PTF MF41858, which
solves this problem.
14. The problem is solved by PTFs SI33610 and SI33614
15. The problem is solved by PTF SI35317, which is included in Hiper-
Fixpack 102.