NW2004S Basis and ABA Component SP Level 10 - 14

[Former Member]

We are on the verge of updating the OCS packages of components Basis and ABA. We started the patching activity last Friday, 10:00 PM but until now, the patching

activity is still on-going. Upon viewing the logs, it is currently on the Import Phase

of the Basis Component Level 12. Furthermore, I've tried logging in to the system as a new login session but we cannot log in, a message indicating that "Status 0020 of the user interface SAPMSYST missing". In addition to that, since i have two open transaction codes (one for ongoing transaction, and one for viewing the logs for import), i've tried accessing other transaction codes via executing /oXXXX transaction and to my surprise, i cannot access any transaction code! The only exception is the SPAM transaction code since i can access it if i use /nXXXX.

The situation now is more complicated. Due to a power outage

on where my PC resides (workstation which is running the Support Packages, we cannot check the status of the SP Upgrade since we cannot view the

logs. Furthermore, i have no idea whether the Support Package

activity was terminated or not. We encounter a message

indicating "Status 0020 of the user interface SAPMSYST

missing", whenever i try to login to the SAP System using any

other client aside 000 thus, we are unable to login to the

system. We can only login to the SAP System by using other

accounts except SAP* only in client 000. However, even though

we are able to login, we encounter a runtime error as soon as

logging in. Then, same as indicated in the prior message, all

transaction codes are inaccessible. Upon trying to access

transaction code SPAM, we are directed as a debugger.

Furthermore, we encounter the message, not authorized as a

debugger. PLEASE HELP US! WE ARE IN GREAT NEED OF HELP!

[Former Member · Accepted solution]

Hi Jett,

Try to connect and check SPAM, Is there any change in the patch no? like from 10 to 11..12?, look for the file "slog"( give a serch) and check when is the last trace is written to this file?

If nothing is working, just give a reboot to the system. It may help in solving the problem.

Regards,

Hari.

[Former Member · Accepted solution]

As indicated in the main message of this trail, all the transaction codes cannot be accessed now. With that, i cannot check SPAM and view the logs. How does rebooting a system help solve this problem? Kindly elaborate so as to validate your theory. Thanks.

[Former Member]

Hello,

I had the same problem while implementing SAP Basis Support Packs.

I found the problem to be related to some format or code change with the User Menu items on the top row of SAPGUI interface, causing the User Menu items not loading properly....and creating a short dump as you indicated.

I was able to login after I went to Start/All Programs/SAP Front End/SAP GUI Configuration and UNSELECTED "Use New Visual Design" option.

I found out that the SPAM process was hung, so I restarted the server and restarted the deployment of SAP Basis Support Pack deployment which was in an "error stop" state. I selected to ignore test import and generation errors from the "Extras" menu before I restarted the deployment. This made the deployment to finish successfully.

Another tip: If you are using SQL Server for the database, for the duration of SP implementations please switch the database recovery mode to "Simple". This speeds up the process since the import/update transactions don't get logged. After you are done, you can switch it back to "Full".

Yet another tip: If your database files are getting close to their size limits, please manually extend them prior to deploying Support Packs. You wait a much longer time if SAP tries to automatically extend them for you.

I hope this helps.

[Former Member]

It seems that patience is the only answer for the error being encountered in the application of the SP Level 10 up to SP Level 12. The resolution for the inaccessible system and transaction codes are all in the SP Level 13.

However, now, the situation is similar to what occurred in SP Level 10 because the system is inaccessible again and all the transaction codes are not inaccessible again due to syntax error. I am hoping that after the importing stage of the SP Level 14, the syntax error will no longer be occurring. The importing phase is still on-going as of the moment. However, i just find it weird since I can't decipher what is being used in the SP Application (specifically in the importing phase) since i can't find any background work process being used. Also, i can't find any background job running, etc. The only thing that i do to check whether the SP Application is running is through the command tp showbuffer, as well as viewing the log file if it still being updated regularly and consistently. The SP Level 11 and 12 application took about 2 days each and the SP Level 13 took about a day and now, the SP Level 14 seems to eat up a lot of time as well. I am assumming that the importing phase of SP Level 14 will be completed by April 5.

[Former Member]

What is the Kernel level.

My be you can try this, Stop the Instance, upgrade your kernel if required. and run SPAM again.

Check PAT01 and PAT03 tables

[Former Member]

Prior to performing the Patching activity, the kernel level was upgraded and is now level 133. How can i check tables PAT01 and PAT03 without having SE16 or any transaction codes? If I check it in the Database level, what exactly will i look for and check?

[Former Member]

Check at the database level in PAT03, the patches applied for far.

What is in SLOG and ALOG

[Former Member]

Did you started applying the Support pack in the Dialog Mode from your PC or in background Mode? If its in Dialog Mode it might have terminated when the powe went off.

Did you managed to check the logs in /usr/sap/trans/log corresponding to thi support pack?

Can you see any tp process currently active in the system?

Regards,

Sam

[Former Member]

Actually, it was ran in Dialog Mode. Upon viewing the task manager in the application server, there are no Tp process existing. The SLOG contains:

INFO: Export of BI1K900002. No buffer entry created for logical system (BI1,251) since it is the logical source system.

START INFORM SAP-SYSTEM OF BI1 Q 20080328143822 10005570 MDCSAP08 20080328143816

START tp_getprots BI1 Q 20080328143823 10005570 MDCSAP08 20080328143816

STOP tp_getprots BI1 Q 20080328143833 10005570 MDCSAP08 20080328143816

STOP INFORM SAP-SYSTEM OF BI1 Q 20080328143833 10005570 MDCSAP08 20080328143816

START CMDIMPORT BI1 L 20080328161719 10334952 MDCSAP08 20080328161718

STOP CMDIMPORT BI1 L 20080328161720 10334952 MDCSAP08 20080328161718

START imp all BI1 20080328161721 10334952 MDCSAP08 20080328161720

INFO: event SAP_IMPORT_START triggered successfully

START DD IMPORT BI1 H 20080328161721 10334952 MDCSAP08 20080328161720

STOP DD IMPORT BI1 H 20080328161727 10334952 MDCSAP08 20080328161720

START DD ACTIVATION BI1 A 20080328161728 10334952 MDCSAP08 20080328161720

START tp_getprots BI1 J 20080328161728 10334952 MDCSAP08 20080328161720

STOP tp_getprots BI1 J 20080328161748 10334952 MDCSAP08 20080328161720

STOP DD ACTIVATION BI1 A 20080328161748 10334952 MDCSAP08 20080328161720

START DISTRIBUTION OF DD-O BI1 S 20080328161748 10334952 MDCSAP08 20080328161720

START tp_getprots BI1 S 20080328161748 10334952 MDCSAP08 20080328161720

STOP tp_getprots BI1 S 20080328161758 10334952 MDCSAP08 20080328161720

STOP DISTRIBUTION OF DD-O BI1 S 20080328161758 10334952 MDCSAP08 20080328161720

INFO TBATG CONVERSION OF BI1 N not needed 10334952 MDCSAP08 20080328161720

START MOVE NAMETABS BI1 6 20080328161758 10334952 MDCSAP08 20080328161720

START tp_getprots BI1 P 20080328161758 10334952 MDCSAP08 20080328161720

STOP tp_getprots BI1 P 20080328161808 10334952 MDCSAP08 20080328161720

STOP MOVE NAMETABS BI1 6 20080328161808 10334952 MDCSAP08 20080328161720

START MAIN IMPORT BI1 I 20080328161808 10334952 MDCSAP08 20080328161720

STOP MAIN IMPORT BI1 I 20080328162116 10334952 MDCSAP08 20080328161720

START TBATG CONVERSION OF BI1 n 20080328162116 10334952 MDCSAP08 20080328161720

START tp_getprots BI1 Y 20080328162117 10334952 MDCSAP08 20080328161720

STOP tp_getprots BI1 Y 20080328163057 10334952 MDCSAP08 20080328161720

STOP TBATG CONVERSION OF BI1 n 20080328163057 10334952 MDCSAP08 20080328161720

START EXECUTION OF REPORTS BI1 R 20080328163057 10334952 MDCSAP08 20080328161720

START tp_getprots BI1 R 20080328163057 10334952 MDCSAP08 20080328161720

STOP tp_getprots BI1 R 20080328163107 10334952 MDCSAP08 20080328161720

STOP EXECUTION OF REPORTS BI1 R 20080328163107 10334952 MDCSAP08 20080328161720

INFO: event SAP_IMPORT_STOP triggered successfully

STOP imp all BI1 0004 20080328163107 10334952 MDCSAP08 20080328161720

START CMDIMPORT BI1 L 20080328181513 10334952 MDCSAP08 20080328181513

STOP CMDIMPORT BI1 L 20080328181514 10334952 MDCSAP08 20080328181513

START imp all BI1 20080328181516 10334952 MDCSAP08 20080328181515

INFO: event SAP_IMPORT_START triggered successfully

START DD IMPORT BI1 H 20080328181516 10334952 MDCSAP08 20080328181515

STOP DD IMPORT BI1 H 20080328181518 10334952 MDCSAP08 20080328181515

START DD ACTIVATION BI1 A 20080328181518 10334952 MDCSAP08 20080328181515

START tp_getprots BI1 J 20080328181518 10334952 MDCSAP08 20080328181515

STOP tp_getprots BI1 J 20080328181528 10334952 MDCSAP08 20080328181515

STOP DD ACTIVATION BI1 A 20080328181528 10334952 MDCSAP08 20080328181515

START DISTRIBUTION OF DD-O BI1 S 20080328181528 10334952 MDCSAP08 20080328181515

START tp_getprots BI1 S 20080328181528 10334952 MDCSAP08 20080328181515

STOP tp_getprots BI1 S 20080328181539 10334952 MDCSAP08 20080328181515

STOP DISTRIBUTION OF DD-O BI1 S 20080328181539 10334952 MDCSAP08 20080328181515

INFO TBATG CONVERSION OF BI1 N not needed 10334952 MDCSAP08 20080328181515

START MOVE NAMETABS BI1 6 20080328181539 10334952 MDCSAP08 20080328181515

START tp_getprots BI1 P 20080328181539 10334952 MDCSAP08 20080328181515

STOP tp_getprots BI1 P 20080328181549 10334952 MDCSAP08 20080328181515

STOP MOVE NAMETABS BI1 6 20080328181549 10334952 MDCSAP08 20080328181515

START MAIN IMPORT BI1 I 20080328181549 10334952 MDCSAP08 20080328181515

STOP MAIN IMPORT BI1 I 20080328181610 10334952 MDCSAP08 20080328181515

START TBATG CONVERSION OF BI1 n 20080328181610 10334952 MDCSAP08 20080328181515

START tp_getprots BI1 Y 20080328181610 10334952 MDCSAP08 20080328181515

STOP tp_getprots BI1 Y 20080328182700 10334952 MDCSAP08 20080328181515

STOP TBATG CONVERSION OF BI1 n 20080328182700 10334952 MDCSAP08 20080328181515

START EXECUTION OF REPORTS BI1 R 20080328182700 10334952 MDCSAP08 20080328181515

START tp_getprots BI1 R 20080328182700 10334952 MDCSAP08 20080328181515

STOP tp_getprots BI1 R 20080328182710 10334952 MDCSAP08 20080328181515

STOP EXECUTION OF REPORTS BI1 R 20080328182710 10334952 MDCSAP08 20080328181515

INFO: event SAP_IMPORT_STOP triggered successfully

STOP imp all BI1 0004 20080328182710 10334952 MDCSAP08 20080328181515

START CMDIMPORT BI1 L 20080328213323 10334952 MDCSAP08 20080328213323

STOP CMDIMPORT BI1 L 20080328213504 10334952 MDCSAP08 20080328213323

START DD IMPORT BI1 H 20080328215312 10334952 MDCSAP08 20080328215312

STOP DD IMPORT BI1 H 20080328220021 10334952 MDCSAP08 20080328215312

START DD ACTIVATION BI1 A 20080328220026 10334952 MDCSAP08

START tp_getprots BI1 J 20080328220026 10334952 MDCSAP08

STOP tp_getprots BI1 J 20080329011224 10334952 MDCSAP08

STOP DD ACTIVATION BI1 A 20080329011224 10334952 MDCSAP08

START imp all BI1 20080329011225 10334952 MDCSAP08 20080329011225

INFO: event SAP_IMPORT_START triggered successfully

START DISTRIBUTION OF DD-O BI1 S 20080329011225 10334952 MDCSAP08 20080329011225

START tp_getprots BI1 S 20080329011225 10334952 MDCSAP08 20080329011225

STOP tp_getprots BI1 S 20080329011330 10334952 MDCSAP08 20080329011225

STOP DISTRIBUTION OF DD-O BI1 S 20080329011330 10334952 MDCSAP08 20080329011225

START TBATG CONVERSION OF BI1 N 20080329011330 10334952 MDCSAP08 20080329011225

START tp_getprots BI1 N 20080329011330 10334952 MDCSAP08 20080329011225

STOP tp_getprots BI1 N 20080329011336 10334952 MDCSAP08 20080329011225

STOP TBATG CONVERSION OF BI1 N 20080329011336 10334952 MDCSAP08 20080329011225

START MOVE NAMETABS BI1 6 20080329011336 10334952 MDCSAP08 20080329011225

START tp_getprots BI1 P 20080329011336 10334952 MDCSAP08 20080329011225

STOP tp_getprots BI1 P 20080329012242 10334952 MDCSAP08 20080329011225

STOP MOVE NAMETABS BI1 6 20080329012242 10334952 MDCSAP08 20080329011225

START MAIN IMPORT BI1 I 20080329012242 10334952 MDCSAP08 20080329011225

In conclusion, is there a way to reset it back to its working status so that i could reimport it again, without having to perform recovery?