Import Running for a long time on ECC 6.0

[Former Member]

Hi,

Environment: ECC 6.0, Oracle, Windows 2003.

When trying to import an object in ECC 6.0, it is running for a very long time.

Its been running for more than 12hrs. The size of the import is about 8kb.

The background job RDDIMPDP is running on client 000 as well as the relevant client.

Below is the TP System Log:

WARNING: System CC6. Warning. 20090914042136 :

WARNING: Background job not running properly. Function: G Jobcount: 04512801 Status: S.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

As per NOTE: 26966, it could be b'cause the background job process slots are occupied,

but in our system we have two background processes defined and both are free. There are no background jobs running.

This is the current tp version 370.00.09.

I have looked up on sdn to find a solution, but unable to resolve the issue.

Any help would be greatly appreciated.

Regards,

vishnu.

Edited by: vishnuarigela on Sep 16, 2009 10:55 AM

[Former Member · Accepted solution]

Hi Vishnu,

You mention you only have 2 background processes configured. Are you sure that the current operation mode does not reserve both processes for class A jobs? Please check this with txn RZ04. Also try scheduling a small test job in the standard queue (C) with immediate start. Does that job actually start running?

Regards,

Mark

[Former Member · Accepted solution]

Hi Mark,

In RZ04, we have not configured operation modes,

since we use this system is only for development activities based on client requirements,

there is very little activity. So there was never a need to configure operation modes.

As you had suggested I have run job of type C, it started immediately.

Rgds,

vishnu

Edited by: vishnuarigela on Sep 21, 2009 6:36 AM

[Former Member · Accepted solution]

Hi,

To continue this thread further,

The issue still has not been resolved, In CCMS monitoring under background processes, this is the error message

that I found for SystemWideQueueLength: 349,800000 Jobs > 4,000000 Jobs Current value over threshold value

I think this could be the problem, why the imports are taking so long to complete. Please correct me if I am wrong.

What I have done is I have deleted all the background jobs that were running which are not necessary anymore.

How do I set this right?

Any suggestions.

Rgrds,

vishnu.

[Former Member · Accepted solution]

Hi Vishnu,

Can you check the following:

SM51 -> select the instance -> Goto -> Server name -> Information -> Queue information

What do you see in the row "BTC"? Is the "Requests waiting" value for BTC frequently > 0? Click "Refresh" a few times: do the values of "Requests written" and "Requests read" increase constantly?

Regards,

Mark

[Former Member · Accepted solution]

Hi Mark,

As you had suggested,

Requests waiting value is 0, still "Requests written" and "Requests read" values are increasing constantly.

BTC 0 1 4.000 419 419

Rgds,

vishnu

Edited by: vishnuarigela on Oct 13, 2009 1:31 PM

[Former Member · Accepted solution]

Hi Vishnu,

You say that the values are increasing constantly but the total count that you sent me is only 419. Is this correct and by how much does the counter change on average?

Can you also do the following:

SM37 ->

Job name = RDD*

User name = DDIC

Status = Finished and Cancelled

Time interval = any recent interval during which transports were imported

Do you see jobs with either very long runtimes or (more likely) high values in the "Delay" column? Is the "Delay" systematically greater than zero?

Rgds,

Mark

[Former Member · Accepted solution]

Hi Mark,

The total count now is at 491, the counter changes by 1 and sometimes by 2

BTC 0 1 4.000 491 491

In sm37, using the selection criteria suggested by you,

as there are no transports happening, there are no jobs running.

Rgds,

vishnu

Edited by: vishnuarigela on Oct 13, 2009 2:02 PM

Edited by: vishnuarigela on Oct 13, 2009 2:05 PM

Edited by: vishnuarigela on Oct 13, 2009 2:07 PM

[anindya_bose · Accepted solution]

Vishnu

From your productive client check the TRBAT entries. You can clear two entries there ( one is header information and other is Tr number) from SM30 and then save.

Then login to 000 client. Run RDDNEWPP in dialog mode and give it a Priority A.

Then come back to the productive client and reimport the request. When reimporting, please check TRBAT table again ( it should contain the current request only)

Let's see what happens

[Former Member · Accepted solution]

Hi Anindya,

Thank you very much.

The transports are working now.

Thanks again,

vishnu

Edited by: vishnuarigela on Oct 14, 2009 7:01 AM

[Former Member · Accepted solution]

Hi Mark,

Thank you very much for you time and effort on this.

I have learned a few new things through your posts.

Thanks,

vishnu

[Former Member]

Hi Vishnu,

Can you check for the tablespace???

Regards

Gangadhar

[Former Member]

Hi all,

I did not mention that the version of ECC 6 we have currently installed is a IDES version.

And also we have both ECC 6 and ECC 5 installed on the same server.

ECC 5 is configured as a domain controller and both versions of SAP share the same Transport directory.

However, the databases are different for both the systems.

The imports in ECC 5 are working fine, but the imports into ECC 6 are running for a long time.

I apologize for not explaining my system landscape completely.

Rgds,

vishnu

[JPReyes]

Can you see any errors on SM21?, also check the import monitor.

Regards

Juan

[Former Member]

Hi Juan,

There are no errors in sm21. The import monitor shows the last activity time, target client,

maximum return code:0000 -tp running, start of action imp single.

Any Ideas..

Regards,

vishnu

Edited by: vishnuarigela on Sep 16, 2009 11:52 AM

Edited by: vishnuarigela on Sep 16, 2009 11:54 AM

Edited by: vishnuarigela on Sep 16, 2009 1:42 PM

[Former Member]

did u check the Trans directory space..please check..once

-Srini

[Former Member]

HI Srinivas,

Yes I have checked for space in Trans directory. There is free space.

Rgds,

vishnu

[Former Member]

Hi ,

Did you run update statistics before starting the import.Its always better to run to speed up th import processes in SAP.

Hope this will solve your issue.

Thankls..

Mohit

[Former Member]

Hi Mohit,

No, Import statistics were run before the import.

Should import statistics be run for the concerned tables or for all the tables?

Can you users still work when running the import statistics?

Thanks,

vishnu.

[Former Member]

Yes its always recommended.

However try to run this in when system load is less .You can run it anytime however its recommnded to when users not using the system.

Thanks..

Mohit