Transport Error....

RDDIMPDP / RDDNEWPP
Erich asked Jul 28, 2005 | Replies (16)

Transporting a file into a system and I'm getting this error:

ERROR: Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP. ERROR: I'm waiting 100 sec (Count: 0). ERROR: Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.

I'm importing to client 800.

Any suggestions....been working on this for sometime now with no results.

-Erich
Popular White Paper On This Topic

Transforming an Industry with Big Data, a Telco Example

16 Replies
0

TET PABLO replied Jul 28, 2005

Log in to client 00 using user ID DDIC and run RDDNEWPP.

0

Robert Jessie replied Jul 28, 2005

Make sure DDIC user is not locked in 000 or 800. Cancel any RDD* jobs that are running. Then Start RDDNEWPP.

BJ
0

soyman replied Jul 28, 2005

Did you try to run report RDDNEWPP? Use se38..

0

david.caddick replied Jul 28, 2005

You must run RDDNEWPP in all clients

David Caddick

+44 (0)20 7082 7332 (W) +44 (0)780 806 2993 (Cell) email@removed

White Papers and Webcasts

Popular

Windows 8 Release to Market Related Virtual Patching: A Proven Cost Savings Strategy Hosted CRM: Your Secret Weapon to Success The Keys to the Kingdom: Limiting Active Directory ... More White Papers 0

Erich replied Jul 29, 2005

I've checked that DDIC is not locked. I logged in as DDIC client 000. There are no RDD processes running. I've ran tcode se38 and ran the RDDNEWPP program.

After I run RDDNEWPP and do the transport....I get a new error:

sapparam(1c): No Profile used. ERROR: System L2Z. Error detected 20050729093758 : ERROR: Background job is aborted. Function: P Jobcount: 15230501 Status: A. Please check the system. Use transactions SM21, SM37, SM50. Check that background job RDDIMPDP is scheduled.

When I saw this error, I went back to tcode se38 and ran the RDDIMPDP program. The transport still gave the same error. I then tried canceling it and restarting it...same error.

Any other ideas?

0

Marcelo Bitencourt replied Jul 29, 2005

Eric the process is right however you should logon to all clients with DDIC and run RDDNEWPP with HIGH priority. After that go to SM37 look for RDDIMPDP jobs with statuses scheduled. Also check SM21 and SM50, are there free Background WP in your system???

> # 88% of those surveyed detected spyware on their corporate network. > # Learn how it was removed http://www.ITtoolbox.com/i/rd.asp?i=3D10734 > > # View Group Archive: http://ITtoolbox.com/hrd.asp?i=3D849 > > I've checked that DDIC is not locked. > I logged in as DDIC client 000. > There are no RDD processes running. > I've ran tcode se38 and ran the RDDNEWPP program. > > After I run RDDNEWPP and do the transport....I get a new error: > > sapparam(1c): No Profile used. > ERROR: System L2Z. Error detected 20050729093758 : > ERROR: Background job is aborted. Function: P Jobcount: 15230501 Status: A. > Please check the system. Use transactions SM21, SM37, SM50. > Check that background job RDDIMPDP is scheduled. > > When I saw this error, I went back to tcode se38 and ran the RDDIMPDP program. The transport still gave the same error. I then tried canceling it and restarting it...same error. > > Any other ideas? > > > *FAQ: http://wiki.ittoolbox.com/faq.php?l=3Dsap-r3-basis > *Archives: http://Groups.ITtoolbox.com/g/sap-r3-basis.asp > *Manage Subscriptions: http://My.ITtoolbox.com > *Leave Group: mailto:email@removed > *Need Subscription Help? mailto:email@removed > *Terms of Use: http://www.ittoolbox.com/help/termsofuse.htm > *Copyright (c) ITtoolbox and message author. No redistribution. > > -------------------

Marcelo Bitencourt Administra=E7=E3o SAP R/3 BASIS Database & SAP Management
0

soyman replied Jul 29, 2005

Please check the System log. (use SM21) If possible, send it. Also run tp as below ;

tp connect pf=3DTP_DOMAIN_L2Z.PFL L2Z

And check the errors if there are..

0

Carol Cockayne replied Jul 29, 2005

Was there anything in the log files in SM21, SM37 or SM50?

Carol.
0

Erich replied Jul 29, 2005

Thansk for the all the help....I appreciate it!

I checked sm50 and there are BGD jobs available.

I ran tp connect pf=TP_DOMAIN_L2Z.PFL L2Z and the database is connected: "This is tp version 320.56.89 (release 620) Connection to Database of L2Z was successful. This is R3trans.exe version 6.09 (release 620 - 05.04.04 - 14:45:00). R3trans.exe finished (0000). tp finished with return code: 0 meaning: Everything OK"

There is about 20+ clients on this system....so I'd like to avoid running RDDNEWPP on all the clients.

tcode sm21 shows the following (during time frame of transport attempt):

"11:16:33 BTC 15 000 SAPSYS F60 TemSe object file name is too long 11:16:33 BTC 14 000 SAPSYS ECF Failed to create log for job EMAIL_SEND_771 11:16:33 BTC 16 000 SAPSYS F60 TemSe object file name is too long 11:16:33 BTC 15 000 SAPSYS ECF Failed to create log for job EMAIL_SEND_730 11:16:33 BTC 16 000 SAPSYS ECF Failed to create log for job EMAIL_SEND_760 11:16:43 BTC 13 000 SAPSYS F60 TemSe object file name is too long 11:16:43 BTC 13 000 SAPSYS ECF Failed to create log for job RDDIMPDP 11:16:53 BTC 13 000 SAPSYS F60 TemSe object file name is too long 11:16:53 BTC 14 000 SAPSYS F60 TemSe object file name is too long 11:16:53 BTC 13 000 SAPSYS ECF Failed to create log for job SWWDHEX 11:16:53 BTC 14 000 SAPSYS ECF Failed to create log for job EMAIL_SEND_750 11:16:53 BTC 15 000 SAPSYS F60 TemSe object file name is too long 11:16:53 BTC 15 000 SAPSYS ECF Failed to create log for job EMAIL_SEND_800 11:17:03 BTC 13 000 SAPSYS F60 TemSe object file name is too long 11:17:03 BTC 13 000 SAPSYS ECF Failed to create log for job SAP_CFX_NOTIFICATIONREPORTEMAIL 11:17:03 BTC 14 000 SAPSYS F60 TemSe object file name is too long 11:17:03 BTC 14 000 SAPSYS ECF Failed to create log for job EMAIL_SEND_781 11:17:05 BTC 13 000 SAPSYS F60 TemSe object file name is too long 11:17:05 BTC 13 000 SAPSYS ECF Failed to create log for job RDDIMPDP 11:17:23 BTC 13 000 SAPSYS F60 TemSe object file name is too long 11:17:23 BTC 13 000 SAPSYS ECF Failed to create log for job CHECK_SM50 11:17:23 BTC 14 000 SAPSYS F60 TemSe object file name is too long 11:17:23 BTC 15 000 SAPSYS F60 TemSe object file name is too long 11:17:23 BTC 16 000 SAPSYS F60 TemSe object file name is too long 11:17:23 BTC 14 000 SAPSYS ECF Failed to create log for job EMAIL_SEND_740 11:17:23 BTC 15 000 SAPSYS ECF Failed to create log for job EMAIL_SEND_771 11:17:23 BTC 16 000 SAPSYS ECF Failed to create log for job EMAIL_SEND_753 11:17:33 BTC 13 000 SAPSYS F60 TemSe object file name is too long 11:17:33 BTC 14 000 SAPSYS F60 TemSe object file name is too long 11:17:33 BTC 13 000 SAPSYS ECF Failed to create log for job SWWDHEX"

Keep in mind...I'm certainly not the only one on this box. Any help would be greatly appreciated!

-Erich
0

soyman replied Jul 29, 2005

What's your kernel patch level.

0

Erich replied Jul 29, 2005

Here is all the info you might need:

Component I Release Level Highest SP

SAP_BASIS 620 0038 SAPKB62038 SAP_ABA 620 0038 SAPKA62038 BBPCRM 400 0006 SAPKU40006 ABA_PLUS 100 0003 SAPKGPBA03 PI_BASIS 2004_1_620 0003 SAPKIPYI53 WP-PI 600_620 0000 APPINT 200_620 0005 SAPK-20005IN.. CPROJECTS 310_620 0001 SAPK-31201IN.. WFMCORE 110_620 0002 SAPK-11202IN.. ST-A/PI 01C_CRM400 0000 ST-PI 003C_620 0001 SAPKITLPR1
0

soyman replied Jul 29, 2005

Please goto sm51 select instance and click the release Notes button and send the information of kernel patch number.
0

Erich replied Jul 29, 2005

SAP R/3 Kernel information

SAP R/3 Kernel 620

Database Client Library SQL_Server_7.00

created in NT 5.0 2195 Service Pack 2 x86 MS VC++ 12.00

created on Mar 14 2004 22:07:17

Support Level 0

Kernel Patch number 1393

Source ID 0.1393

DBSL Patch No. 1388

ICU Version Library Could Not Be Loaded

0

soyman replied Jul 29, 2005

I think you should upgrade the kernel. I saw some errors on system log(TemSe issues the following error: F60)

Please read OSS note 749150. I hope, it helps you...

Symptom You create a file on the file system and TemSe issues the following error: F60

Reason and Prerequisites The maximum length for the file name is 72 characters (including all characters).

Solution The RSTS/FILES/ROOT/x profile parameter can only have a maximum of 42 characters. This is due to the fact that TemSe creates file names in an independent way, for example, the names for the job logs. You must bear this in mind during the installation.

By using one of the following kernel patches, you can achieve a maximum

length of 255 characters:

4.6D - 1883

6.20 - 1574

6.40 - 27
0

Erich replied Jul 29, 2005

Thanks! I'm updating the kernel right now...I'll post and update later if it works or not.

-Erich
0

Erich replied Aug 8, 2005

Soyman, Thanks for all your help. Upgrading the kernel fixed the problem.