Hi,
We have an old small 2.2H SAP system ticking along. We've got plans to incorporate it into our main ECC6 system, but are not currently in a position to do so. However, we've started having significant hardware issues as its current old infrastructure is falling apart. So, as an interim solution, we're moving it to newer hardware which had become available.
To get us out of trouble, there's been a straight copy across to a V880 running SunOS 5.8 (which apparently is the earliest Solaris version it can run i.e. due to firmware compatibility). The 2.2H SAP system basically runs fine on the hardware (much faster actually), however, we're initially getting nasty messages that we'd like to avoid if at all possible.
The errors come about after a system bounce. ABAP runtime errors occur every minute saying START_CALL_SICK. Transaction SICK says: "OS release SunOS 5.8 Generic_Virtual sun4u is not supported with this kernel - Severe inconsistencies were detected - Don't use that system without fixing these problems !". The initial user trying to logon will hang, will messages like "Transaction termination SY002 (Inconsistency with data base)" and "error formatting terminal data". And they won't be able to leave the initial screen. However, logging on again seems to correct it, and all subsequent processing seems ok i.e. functional testing is all fine.
The SAP system is R/3 2.2H with a 21N SAP Kernel. Version compatibility on this kernel (from disp+work -V) states it's only compatible up to SunOS 5.5 i.e. the system is now on SunOS 5.8 which is not recognised by the kernel, which appears to be the source of all our errors.
My questions are:
- is anyone aware of a kernel version we could stick on which would be compatible with a 22H SAP system and SunOS 5.8?
- failing that, is there a way to trick the kernel into thinking SunOS 5.8 is ok e.g. a file or something?
- any other ideas?
Regards,
Tony McLaren