on 09-06-2011 10:04 AM
Hi,
We are updating our solution manager 7.01 sp25 to sp27.
Ours is windows 2003 srv, db2 database.
I went through the MOPZ and downloaded the files.
I started txn SAINT and pointed the stack.xml file.
The queue is generated and update was started.
Till here everything was fine. SAINT was running more than 24hours.
I checked for logs in the OS level. But I could not find any updated logs. So I started and wanted to reset the queue from command prompt. I have run the command 'tp r3i all <SID> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8'. But this also started running more than an hour and nothing happened. So I terminated this command by Ctl+C. Now the problem started. I could not run any t-code in Solman. It is giving a short dump saying 'Syntax error'. Here I am attaching the logfile for your ref.
Short text |
Syntax error in program "SAPLCRFC ". |
What happened? |
Error in the ABAP Application Program |
The current ABAP program "SAPLSTPA" had to be terminated because it has |
come across a statement that unfortunately cannot be executed. |
The following syntax error occurred in program "SAPLCRFC " in include "LCRFCU04 |
" in |
line 729: |
"The data object "RFCDISPLAZ" does not have a component called "ASSERTI" |
"ON_TICKET"." |
" " |
" " |
The include has been created and last changed by: |
Created by: "SAP " |
Last changed by: "SAP " |
Error in the ABAP Application Program |
The current ABAP program "SAPLSTPA" had to be terminated because it has |
come across a statement that unfortunately cannot be executed. |
-
-
What can you do? |
Please eliminate the error by performing a syntax check |
(or an extended program check) on the program "SAPLCRFC ". |
You can also perform the syntax check from the ABAP Editor. |
If the problem persists, proceed as follows: |
Note down which actions and inputs caused the error. |
To process the problem further, contact you SAP system |
administrator. |
Using Transaction ST22 for ABAP Dump Analysis, you can look |
at and manage termination messages, and you can also |
keep them for a long time. |
-
-
Error analysis |
The following syntax error was found in the program SAPLCRFC : |
"The data object "RFCDISPLAZ" does not have a component called "ASSERTI" |
"ON_TICKET"." |
" " |
" " |
Downloaded files include latest kernal also. But I have not updated kernal.
Please help to resolve this.
Regards
K.Prakash
Hi,
command prompt. I have run the command 'tp r3i all <SID> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8'. But this also started running more than an hour and nothing happened. So I terminated this command by Ctl+C. Now the problem started. I could not run any t-code in Solman. It is giving a short dump
You should not use this command until and unless SAP suggest you to do the same. Now, as suggested by others, your system is inconsistent state. Either restore your system and then start upgrade again. or raise an OSS to SAP.
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Short dump due to Saint stuck in half way. You cannt move further unless you finish off the queue.No luck with the tp at command prompt too.
Right now, if you have offline back up, please restore your system and start saint again.Dont abort in middle. continue. and findout the cause for long running transaction, might be memory problem? or \tmp full situvations? or more than one TP is running at os level.
Make sure above all and proceed again.
Thanks,
Jansi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Most probably the system is not consistent. Usually the 'tp r3i' is not recommended and is used only for non-productive system with minimal risk. As the tp r3i command also was interrupted - the system definitely would have got inconsistent.
During the import process:
- did you check the trans log and tmp directory? log might not get updated but tmp definitely will
- did you check for any aborted jobs in sm37?
- did you check for any dumps or system errors in st22 and sm21? Usually the RDD* jobs might not get scheduled which leads to this situation.
But now that the import process was aborted, I am very unsure if the re-import could help solve the issue. You could give it a try.
Do you have a backup before starting the update?
Regards,
Srikishan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.