cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Language import using SMLT .

Former Member
0 Kudos

Hi,

I was importing japanese language in SAP ERP 6.0 EHP4. import process was started using SMLT and the import process is taking long to get imported.

Below is the observation in SMLT:

1. JOB: SAP-LANGUAGE-IMP JA SAPKLJASR1EH shows status finished.

2. Action log is stuck at:

@5B\QInformation@ Start import (state:initial)
@5B\QInformation@ ... system date: 10.09.2014 system time: 12:40:58
@5B\QInformation@ Version: 701.F.15
@5B\QInformation@ Step INIT ...
@5B\QInformation@ ... system date: 10.09.2014 system time: 12:40:58
@5B\QInformation@ ... configuration "Selective Language Import"
@5B\QInformation@ ... executed successfully
@5B\QInformation@ Step DISASSEMBLE ...
@5B\QInformation@ ... system date: 10.09.2014 system time: 12:40:59
@5B\QInformation@ ... do not overwrite data files and cofiles (settings)
@5B\QInformation@ ... executed successfully
@5B\QInformation@ Step ADD TO BUFFER ...
@5B\QInformation@ ... system date: 10.09.2014 system time: 12:42:22
@5B\QInformation@ ... executed successfully
@5B\QInformation@ Step MAIN IMPORT ...
@5B\QInformation@ ... system date: 10.09.2014 system time: 12:42:28
@5B\QInformation@ ... number of parallel import processes: 1 (settings)
@5B\QInformation@ ... start tp IMPORT SUBSET (TPSTAT = 20140910124228390)
@5B\QInformation@ ... waiting for entry in TPSTAT (12:42:28)
@5B\QInformation@ ====== Control passed to tp/R3trans (see long text) ======

3. At OS level, location: E:\usr\sap\trans\log and file: SLOG1437.RE1 shows the following message:

START imp single RE1 20140910123924 BASIS mb3ap1024 20140910124228390
START DD IMPORT RE1 H 20140910123925 BASIS mb3ap1024 20140910124228390
WARNING: System RE1. Warning. 20140910124154 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910124755 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910125155 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910125255 :
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
Please check that the R/3 system is running.
Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910125556 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910130156 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910130557 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910130657 :
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
Please check that the R/3 system is running.
Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)

i tried abortimp and started the import again but the error messages were the same as first time.

Kindly provide some assistance on this issue.

Regards,

Mamta Bijlani.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi All,

Stopped TP and R3trans services running previoulsy and re imported the language package.

As of now, import process running fine.

Will update once the import is completed successfully.

Thank you.

Regards,

Mamta Bijlani

Former Member
0 Kudos

Hi Mamta,

You may consider the following for more details:

http://scn.sap.com/community/netweaver-administrator/blog/2012/12/10/installation-of-languages-on-sa...

http://scn.sap.com/docs/DOC-33931

and continuously check for OS level logs to see the status.

regards,

Suraj

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Mamta,

Did you check dev_evt ?

Regards,

Former Member
0 Kudos

Hi Divyanshu,

Yes, checked dev_evt. It shows:

Wed Jul 09 12:12:49 2014

Trace File of External Event Raiser (Level=0, Append=1)

EventID: SAP_TRIGGER_RDDIMPDP

SAP message server host: MB3AP1020

SAP message server service (new): 3900

SAP message server service (old): sapmsRE1

Event sent to server MB3AP1020_RE1_00

Wed Jul 09 12:12:53 2014

Trace File of External Event Raiser (Level=0, Append=1)

EventID: SAP_TRIGGER_RDDIMPDP

SAP message server host: MB3AP1020

SAP message server service (new): 3900

SAP message server service (old): sapmsRE1

Event sent to server MB3AP1020_RE1_00

Wed Jul 09 12:14:07 2014

Trace File of External Event Raiser (Level=0, Append=1)

EventID: SAP_TRIGGER_RDDIMPDP

SAP message server host: MB3AP1020

SAP message server service (new): 3900

SAP message server service (old): sapmsRE1

Event sent to server MB3AP1020_RE1_00

Wed Jul 09 12:14:10 2014

Trace File of External Event Raiser (Level=0, Append=1)

EventID: SAP_TRIGGER_RDDIMPDP

SAP message server host: MB3AP1020

SAP message server service (new): 3900

SAP message server service (old): sapmsRE1

Event sent to server MB3AP1020_RE1_00

Wed Jul 09 12:14:26 2014

Trace File of External Event Raiser (Level=0, Append=1)

EventID: SAP_TRIGGER_RDDIMPDP

SAP message server host: MB3AP1020

SAP message server service (new): 3900

SAP message server service (old): sapmsRE1

Event sent to server MB3AP1020_RE1_00.

former_member188883
Active Contributor
0 Kudos

Hi Mamta,

Please use report RDDNEWPP and RDDIMPDP to schedule the SAP_TRIGGER_RDDIMPDP jobs in client 000.

Ensure that these jobs run properly to have the language import done .

Regards,

Deepak Kori

Former Member
0 Kudos

Hi Deepak,

We had tried running the report RDDNEWPP using se38.

output as follows in trans log:

WARNING: (This warning is harmless if no further warnings follow.)
STOP tp_getprots RE1 P 20140910142239 BASIS mb3ap1024 20140909180224937
STOP MOVE NAMETABS RE1 6 20140910142239 BASIS mb3ap1024 20140909180224937
START MAIN IMPORT RE1 I 20140910142239 BASIS mb3ap1024 20140909180224937
WARNING: System RE1. Warning. 20140910142421 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
STOP tp_getprots RE1 P 20140910142431 BASIS mb3ap1024 20140910124228390
START MOVE NAMETABS RE1 6 20140910142431 BASIS mb3ap1024 20140910124228390
WARNING: System RE1. Warning. 20140910142732 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
START tp_getprots RE1 P 20140910142733 BASIS mb3ap1024 20140910124228390
WARNING: System RE1. Warning. 20140910143238 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)

Later we executed RDDIMPDP in se38 and the output is:

STOP tp_getprots RE1 P 20140910143740 BASIS mb3ap1024 20140910124228390
STOP MOVE NAMETABS RE1 6 20140910143740 BASIS mb3ap1024 20140910124228390
START MAIN IMPORT RE1 I 20140910143740 BASIS mb3ap1024 20140910124228390
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F1.RE1 is already in use (10), I'm waiting 1 sec (20140910143806). My name: pid 6896 on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F1.RE1 is already in use (20), I'm waiting 2 sec (20140910143830). My name: pid 6896 on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F1.RE1 is already in use (30), I'm waiting 1 sec (20140910143856). My name: pid 6896 on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F1.RE1 is already in use (40), I'm waiting 5 sec (20140910143920). My name: pid 6896 on mb3ap1024 (APServiceRE1).

Also, Should we explicity schedule the job: SAP_TRIGGER_RDDIMPDP in SM36 and give both the reports?

What about the frequency of scheduling the job.

former_member185239
Active Contributor
0 Kudos

Hi Mamta,

Rename the file SAPKKLJASR1EHP4ERP6F1.RE1 to SAPKKLJASR1EHP4ERP6F1.RE1.old in directory \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F1.RE1

and then continue with the patching.

With Regards

Ashutosh

Former Member
0 Kudos

Hi Ashutosh,

I am not able to rename SAPKKLJASR1EHP4ERP6F1.RE1 file, says- it's in use.

former_member185239
Active Contributor
0 Kudos

Hi Mamta,

1. Stop the language import in SMLT.

2. Rename the file and again start it.

Also do paste the last 50 lines of SLOG

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Ashutosh, i have stopped the import using abortimp in SMLT.
still unable to rename. should i clear the transport logs and entries in TPSTAT?

Former Member
0 Kudos

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F1.RE1
is already in use (170), I'm waiting 3 sec (20140910144553). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F1.RE1
is already in use (180), I'm waiting 4 sec (20140910144622). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F1.RE1
is already in use (190), I'm waiting 5 sec (20140910144658). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (10), I'm waiting 1 sec (20140910145640). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (20), I'm waiting 2 sec (20140910145703). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (30), I'm waiting 3 sec (20140910145734). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (40), I'm waiting 4 sec (20140910145804). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (50), I'm waiting 1 sec (20140910145836). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (60), I'm waiting 2 sec (20140910145858). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (70), I'm waiting 5 sec (20140910145929). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (80), I'm waiting 4 sec (20140910150002). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (90), I'm waiting 3 sec (20140910150039). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (100), I'm waiting 2 sec (20140910150109). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (110), I'm waiting 3 sec (20140910150142). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (120), I'm waiting 5 sec (20140910150208). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (130), I'm waiting 3 sec (20140910150234). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (140), I'm waiting 4 sec (20140910150312). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (150), I'm waiting 4 sec (20140910150349). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (10), I'm waiting 4 sec (20140910151604). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (20), I'm waiting 1 sec (20140910151635). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (30), I'm waiting 2 sec (20140910151706). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (40), I'm waiting 1 sec (20140910151731). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (50), I'm waiting 3 sec (20140910151804). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (60), I'm waiting 1 sec (20140910151828). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (70), I'm waiting 1 sec (20140910151855). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (80), I'm waiting 5 sec (20140910151929). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (90), I'm waiting 5 sec (20140910151958). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (100), I'm waiting 4 sec (20140910152024). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (110), I'm waiting 2 sec (20140910152105). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (120), I'm waiting 1 sec (20140910152133). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (130), I'm waiting 1 sec (20140910152157). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (140), I'm waiting 4 sec (20140910152234). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (150), I'm waiting 2 sec (20140910152308). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (160), I'm waiting 5 sec (20140910152341). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (170), I'm waiting 4 sec (20140910152419). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (180), I'm waiting 4 sec (20140910152450). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (190), I'm waiting 4 sec (20140910152516). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (200), I'm waiting 1 sec (20140910152544). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (210), I'm waiting 2 sec (20140910152614). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (220), I'm waiting 5 sec (20140910152636). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (230), I'm waiting 4 sec (20140910152715). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (240), I'm waiting 1 sec (20140910152749). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (250), I'm waiting 3 sec (20140910152820). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (260), I'm waiting 2 sec (20140910152854). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (270), I'm waiting 5 sec (20140910152932). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (280), I'm waiting 5 sec (20140910152959). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (290), I'm waiting 1 sec (20140910153025). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (300), I'm waiting 4 sec (20140910153055). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (310), I'm waiting 4 sec (20140910153123). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (320), I'm waiting 3 sec (20140910153156). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (330), I'm waiting 2 sec (20140910153230). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (340), I'm waiting 4 sec (20140910153259). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (350), I'm waiting 4 sec (20140910153326). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (360), I'm waiting 4 sec (20140910153353). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (370), I'm waiting 2 sec (20140910153430). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (380), I'm waiting 1 sec (20140910153456). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (390), I'm waiting 1 sec (20140910153526). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (400), I'm waiting 2 sec (20140910153548). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (410), I'm waiting 3 sec (20140910153615). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (420), I'm waiting 2 sec (20140910153649). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (430), I'm waiting 4 sec (20140910153716). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (440), I'm waiting 1 sec (20140910153748). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (450), I'm waiting 4 sec (20140910153812). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (460), I'm waiting 2 sec (20140910153845). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (470), I'm waiting 5 sec (20140910153917). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (480), I'm waiting 5 sec (20140910153951). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (490), I'm waiting 3 sec (20140910154022). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (500), I'm waiting 1 sec (20140910154051). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (510), I'm waiting 5 sec (20140910154120). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (520), I'm waiting 5 sec (20140910154151). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (530), I'm waiting 5 sec (20140910154223). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (540), I'm waiting 2 sec (20140910154255). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (550), I'm waiting 2 sec (20140910154327). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (560), I'm waiting 5 sec (20140910154358). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (570), I'm waiting 3 sec (20140910154426). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (580), I'm waiting 1 sec (20140910154455). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (590), I'm waiting 4 sec (20140910154525). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (600), I'm waiting 4 sec (20140910154600). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (610), I'm waiting 5 sec (20140910154634). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (620), I'm waiting 4 sec (20140910154710). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (630), I'm waiting 2 sec (20140910154741). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (640), I'm waiting 4 sec (20140910154801). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (650), I'm waiting 2 sec (20140910154830). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (660), I'm waiting 4 sec (20140910154909). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (670), I'm waiting 5 sec (20140910154935). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (680), I'm waiting 4 sec (20140910155007). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (690), I'm waiting 3 sec (20140910155045). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (700), I'm waiting 3 sec (20140910155117). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (710), I'm waiting 3 sec (20140910155149). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (720), I'm waiting 5 sec (20140910155222). My name: pid 6896
on mb3ap1024 (APServiceRE1)

WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (730), I'm waiting 1 sec (20140910155254). My name: pid 6896
on mb3ap1024 (APServiceRE1)

SLOG 50 lines.

former_member185239
Active Contributor
0 Kudos

Hi Mamta,

Can you please  paste the output of

ps -ef|grep R3trans

and

ps -ef|grep tp

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi,

It is a windows system and no services are running related to R3trans n TP.

former_member185239
Active Contributor
0 Kudos

Hi Mamta,

Then log off from the host and then login again to rename the file.

With Regards

Ashutosh

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Mamta,

The file is either open or locked

Check TRBAT and TRJOB. If you find any entry related to above delete it.

ps -ef | grep tp - kill it.

Or Stopsap and rename the file.

Regards,

Divyanshu

0 Kudos

Hi srivastava,

with the help of your guidence we were able to procede with the import process but we ended up with a very diffrent status in SMLT, even after importing all the requests in STMS sucessfully.

please find the sanap shot attached.

Please suggest.

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Shashank,

Did you stopped the import from SMLT before remove the entries and processes, and resuming the import again?

Also, share the logs.

Better you raise it with SAP and take the solution from there.

Reagrds

Former Member
0 Kudos


Hi Divyanshu,

Yes, we had stopped the previous imports n porcesses and tried importing again.

0 Kudos

Hi,

we have stoped import process in SMLT, killed TP and r3trans process at os level and renamed the files in tmp folder.

SLOG is below:

ERROR SAPKLJASR1EHP4ERP6F4 RE1 I 0014 20140910161401 D038005      BASIS        mb3ap1024 20140910124228390  

STOP  MAIN IMPORT          RE1 I      20140910161402              BASIS        mb3ap1024 20140910124228390  

ERROR: stopping on error 14 during MAIN IMPORT

START INFORM SAP-SYSTEM OF RE1 Q      20140910161402              BASIS        mb3ap1024 20140910124228390  

START imp single           RE1        20140910162502              BASIS        MB3AP1020 20140910162501421  

START DD IMPORT            RE1 H      20140910162502              BASIS        MB3AP1020 20140910162501421  

STOP  DD IMPORT            RE1 H      20140910171423              BASIS        MB3AP1020 20140910162501421  

INFO  TBATG CONVERSION OF  RE1 N      not needed                  BASIS        MB3AP1020 20140910162501421  

START MOVE NAMETABS        RE1 6      20140910171423              BASIS        MB3AP1020 20140910162501421  

START tp_getprots          RE1 P      20140910171423              BASIS        MB3AP1020 20140910162501421  

STOP  tp_getprots          RE1 P      20140910171427              BASIS        MB3AP1020 20140910162501421  

STOP  MOVE NAMETABS        RE1 6      20140910171427              BASIS        MB3AP1020 20140910162501421  

START MAIN IMPORT          RE1 I      20140910171427              BASIS        MB3AP1020 20140910162501421  

STOP  MAIN IMPORT          RE1 I      20140910224511              BASIS        MB3AP1020 20140910162501421  

INFO  TBATG CREATION OF EN RE1 n      not needed                  BASIS        MB3AP1020 20140910162501421  

START EXECUTION OF REPORTS RE1 R      20140910224512              BASIS        MB3AP1020 20140910162501421  

START tp_getprots          RE1 R      20140910224512              BASIS        MB3AP1020 20140910162501421  

STOP  tp_getprots          RE1 R      20140910224710              BASIS        MB3AP1020 20140910162501421  

STOP  EXECUTION OF REPORTS RE1 R      20140910224710              BASIS        MB3AP1020 20140910162501421  

STOP  imp single           RE1   0008 20140910224710              BASIS        MB3AP1020 20140910162501421  

START tp_getprots          RE1 Q      20140910224710              BASIS        MB3AP1020 20140910162501421  

STOP  tp_getprots          RE1 Q      20140910224710              BASIS        MB3AP1020 20140910162501421  

START INFORM SAP-SYSTEM OF RE1 Q      20140910224710              BASIS        MB3AP1020 20140910162501421  

START tp_getprots          RE1 Q      20140910224710              BASIS        MB3AP1020 20140910162501421  

STOP  tp_getprots          RE1 Q      20140910224711              BASIS        MB3AP1020 20140910162501421  

STOP  INFORM SAP-SYSTEM OF RE1 Q      20140910224711              BASIS        MB3AP1020 20140910162501421

Please help us understand the status of the language import.

we found that one import is canceled in STMS.

Please suggest if we can re-import this Transport.

0 Kudos

this is the status in STMS import overview.

the RC status is yellow with return code 14-canceled and the status is green-already imported.

Please suggest if this is the reason for the overall language import status.

divyanshu_srivastava3
Active Contributor
0 Kudos

I believe you should check with sap on this.

The reason could be your multiple attempts and those entries still existed in tables.

0 Kudos

just now i was able to get some info related to the status.

its " Transfer Data After Import"

can you suggest what can be checkt.

divyanshu_srivastava3
Active Contributor
0 Kudos

That is the status on green arrow.

I believe reimport can be done but you should raise message with sap on how to fix this.

0 Kudos

Transfer Data After Import:

The import is active. The transport control program is running. The language transport is waiting until the language data has been imported, and will then continue.