Syntax Eroor in Program SAPLSFES after Applying SAPKB70019

[Former Member]

Dear Experts,

I was Applying SAPKB70019 in our Development Server, after couple of hours i got a message " Syntax Eroor in Program SAPLSFES" and it doesn't allow me to login.

After that i restarted the sever but same error message are comin and not allowing to login.

Please help me out.

Regards,

Ajit

[Former Member · Accepted solution]

Dear Markus,

I am not able to find the solution for database crash except restore of databse. I have already send a mail to SAP.

One question? may i run " tp r3i SAPKB70019 DEV pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8

"

Regards,

Ajit

[markus_doehr2 · Accepted solution]

> I am not able to find the solution for database crash except restore of databse. I have already send a mail to SAP.

All newest patches installed?

> One question? may i run " tp r3i SAPKB70019 DEV pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8

that could be the command, yes, but I'd let that verify by the support first.

Markus

[Former Member · Accepted solution]

Dear Markus,

I have applied the Oracle Current patch Set 10.4.

regards,

Ajit

[markus_doehr2 · Accepted solution]

And you also installed the minipatch on top of that?

Markus

[Former Member · Accepted solution]

Dear Markus,

Yes!, but unfortunately i have not istalled. I thought i would apply later. is this the reason for crash?Just for awareness i am asking.

May i install Mopatches now?

Regards

Ajit

[markus_doehr2 · Accepted solution]

> Yes!, but unfortunately i have not istalled. I thought i would apply later. is this the reason for crash?Just for awareness i am asking.

I don't know if that is the reason. All log you posted was "database crashed". This can have a million reasons.

The cause of the syntax error is not the (missing) database patch but the fact, that the database crashed and hence the import process couldn't finish.

> May i install Mopatches now?

MOPatch is for Unix systems.

Markus

[Former Member · Accepted solution]

Dear Markus,

Cheers!

I am able to login now. but when i am running SPAM it says" Syntax error in program "SAPLSLI1 "

regards,

Ajit

[former_member204746 · Accepted solution]

again, it'S time to open a case with SAP and ask them permission to run:

tp r3i SAPKB70019 DEV pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8

[90070279]

My suggestion is to not do anything!

It's likely installing the BASIS support packs and just needs time to get that component installed. In the meantime you get the SAPLSFES errors when running SAINT, SPAM, SM50, SM66, SM37, SE80, etc.  I think people panic and then cause damage trying to fix something that is not a problem. Go to lunch and come back in an hour and if still not working then you might have a problem but if you haven't waited at least an hour, then you probably are going to do something you might regret by reacting too soon.  I have received this error many times in the past - especially when upgrading solution manager, and I simply wait for 20 or 30 minutes and then all is fine again as the upgrade was still running. Then transactions work again and I didn't do anything except hold my breath during the process.

[markus_doehr2]

> I was Applying SAPKB70019 in our Development Server, after couple of hours i got a message " Syntax Eroor in Program SAPLSFES" and it doesn't allow me to login.

>

> After that i restarted the sever but same error message are comin and not allowing to login.

Was the import of that package successfully finished?

Markus

[Former Member]

Dear Markus,

Thanks for the prompt reply.

TRINT_PROGRESS_INDICATOR error: SYSTEM_FAILURE

ERROR SAPKB70019 DEV I 0012 20091002120314 SAPUSER BASIS SAPECCDEV 20091001160459735

STOP MAIN IMPORT DEV I 20091002120317 BASIS SAPECCDEV 20091001160459735

ERROR: stopping on error 12 during MAIN IMPORT

HALT 20091002120317

ERROR: uncaught internal error: ORA-03114: not connected to ORACLE

ERROR: EXIT(16) -> process ID is: 17405

STOP imp all DEV 0016 20091002120317 BASIS SAPECCDEV 20091001160459735

2EETP000 sap_dext called with msgnr "1":

2EETP000 -

---

db call info -

---

2EETP000 function: db_setget

2EETP000 fcode: RT_GET (0)

2EETP000 tabname: TRBAT

2EETP000 len (char): 0

2EETP000 key:

2EETP000 ok fetches: 0

2EETP000 last entry:

2EETP000 retcode: 1

1AETP000 exit in function texitnow

ERROR: EXIT(16) -> process ID is: 27516

STOP imp all DEV 0016 20091002120321 DDIC SAPECCDEV 20090930165043380

2EETP000 sap_dext called with msgnr "1":

2EETP000 -

---

db call info -

---

2EETP000 function: db_setget

2EETP000 fcode: RT_GET (0)

2EETP000 tabname: TRBAT

2EETP000 len (char): 0

2EETP000 key:

2EETP000 ok fetches: 0

2EETP000 last entry:

2EETP000 retcode: 1

1AETP000 exit in function texitnow

ERROR: EXIT(16) -> process ID is: 3378

STOP imp all DEV 0016 20091002120323 DDIC SAPECCDEV 20091001093452177

-

---

i think it got stopped at Main Import phase.

Regards,

Ajit

[markus_doehr2]

> ERROR: uncaught internal error: ORA-03114: not connected to ORACLE

> ERROR: EXIT(16) -> process ID is: 17405

so your database crashed during the import (did you find out the cause why?)

I would open an OSS call and let the support have a look on the system, they may give you a command line how to import the failed package on command line level.

Markus

[Former Member]

Our OS HP-UX PARISC 11.31

Database is Oracle 10