Failed to start SAP R3 System

[Former Member]

Hi

When we are trying to start our BW system, we are getting the error

message

"Failed to start the R/3 System .

Appliaction error. SAP0899 unmonitored by CMDMAIN at statement

0000000041, instruction X'0000'.

Function Check. CEE9901 unmonitored by R3MNUOPT at statement

0000029700, instruction X'0000'."

We are logged in as <SID>OFR and are going via the main logon menu for

sidofr option 1--> option 1 again and start the SAP system.

We also tried updatiing our STARTSAP to patch level 3(the latest one

for our release)as per the note 679600. We were able to do the

APYR3FIX...but after that when we do the APYR3KRN.. Its gives us the

message :

"Kernel Library R3620<SID> applied. Configuration data not updated.

Failed to apply R/3 Kernel.

Appliaction Error. SAP0899 unmonitored by CMDMAIN at statement

00000000038, instruction X'0000'."

I would appreciate any help on this issue...

Thanks

Abhi

[Former Member · Accepted solution]

Hi Abhi,

If the kernel patch failed, anything could happen...

Do you have a copy of the last running kernel?

If yes, you can try

CPYLIB (copy it back, or RSTLIB)

FIXR3OWNS

APYR3KRN

If not, you still have a few options:

1. fix the patches, by yourself or through OSS/consulting

2. rebuild the kernel from the last kernel stack (R3OPT) then patch it if you like

3. buy a kernel CD with service from www.4soi.de

Good luck,

Victor

[Former Member · Accepted solution]

Hi Victor,

The kernel looks fine to me now..

The APYR3Fix completed and everthing looks fine from the kernel prespective..

But still when we are trying to start our BW system, we are getting the error

message

"Failed to start the R/3 System .

Appliaction error. SAP0899 unmonitored by CMDMAIN at statement

0000000041, instruction X'0000'.

Function Check. CEE9901 unmonitored by R3MNUOPT at statement

0000029700, instruction X'0000'."

We are logged in as <SID>OFR and are going via the main logon menu for

sidofr option 1--> option 1 again and start the SAP system.

Any Ideas....

Thanks

Abhinav

[Former Member · Accepted solution]

Hi Abhinav,

It is good to know that the kernel patch works now. But the issue seems more complicated than what a regular customer, like myself, could handle.

It looks like the WRKJOBLOG doesn't provide much information.

A few SAP Notes mention that SAP0899 associated with 6.20 kernel when "startsap instance(*all)". Probably not relevant to your case, but it doesn't hurt to apply all the patches related to the startup procedure.

If any job has started under R3_xx subsystem, I would check the trace files under the /usr/sap/SID/Dxxx/work directory and the spool files owned by <SID><##>.

Other folks may have some other ideas. I would go straight to OSS support if nothing suspicious has been found.

Good luck,

Victor

[Former Member]

Thanks everyone...

I was able to bring the system up after I discovered that the /usr/sap/trans was still pointing to the old /usr/sap/trans(of another system), which it was unable to get to..since it was on a isolated LAN.

removed the symbolic link between them and it worked for me...

Thank you very much..