RDDIMPDP IS NOT RUNNING

[Former Member]

Dear All,

Transport is not working in production.when i check background job in sm37 RDDNEWPP is running in all client in sap* and ddic also.Bt RDDIMPDP is not showing anywhere in background job.

i run a job FROM se37 rddnewpp from from DDIC nd SAP* also but it dont able to start the job RDDIMPDP.

WHEN i check in sm37 only RDDNEWPP IS running in all client.what i m thinking to stop his job..will it help o start my RDDIMPDP JOB.

I checked slog:

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

WARNING: System MRP. Warning. 20080715130910 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

HOW TO CANCEL THIS RDDNEWPP JOB IN ALL CLIENT.???

PLZ SUGGEST ME WHAT TO DO..

Regard's

[Former Member]

Hi

login into 000 and other clients with user ddic execute se38 run the report RDDNEWPP,

execute this periodically

Regards

Bhaskar

Edited by: bhaskar1818 on Jul 22, 2008 2:45 PM

[Former Member]

Hi,

did you schedule RDDNEWPP as background job ?

regards,

kaushal

[Former Member]

HI Malavia,

Yes i sheduled the RDDNEWPP job through se-38 coz my transport not running.i sheduled as the background job.

There is no RDDIMPDP JOB running in background in sm37.

plz sgges me what to do ?

Regard's

[Former Member]

Hi,

no need to schedule RDDNEWPP.

first delete the schedule and released job from SM37

also manually terminate all running job of RDDNEWPP using cancel job in SM37

then according to sap Note 11677 - Transports with event-controlled RDDIMPDP.

schedule the event-controlled background job RDDIMPDP, log on to the SAP system as user DDIC in client 000 and execute report RDDNEWPP (using Transaction SE38)

also check Note 71353 - Transports hang during background steps as reference.

regards,

kaushal

[andreas_herzog]

and: do not forget to schedule the job also in every client involved!!! only client 000 will not be sufficient....

GreetZ, AH

[Former Member]

Dear Kushal,

Having a doubt regarding my transport issue..

As i told u earlier one of my background job get failure ie

1.CALL_FUNCTION_RECEIVE_ERROR : job is being cancelled twice in an hrs..still not rectified..

THIS is reason transport is not working?

2.DBIF_REPO_SQL_ERROR: PAST THREE DAYS BEFORE I GOT A THIS DUMP.Then i restarted my system.

coz of this runtime error did it hampered my transport system...

plz advice me...

Regard's

[Former Member]

Hi,

CALL_FUNCTION_RECEIVE_ERROR you got for SAP_COLLECTOR_FOR_PERFMONITOR job

which is not related to current issue.

regards,

kaushal

[Former Member]

Dear Mr Malavia,

Thanx for ur suggestion once again.

DBIF_REPO_SQL_ERROR is runtime error which i got once 5 days before i this error never occrs again.After tha i restarted my system also.

its error log is:-

SQL error 3114 occurred when accessing program

What happened?

The system is no longer linked to an ORACLE instance.

No further operations can be performed on the database.

What can you do?

You cannot eliminate this error yourself.

Please inform your database administrator.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

Error analysis

The system attempted to access an ORACLE instance to which

it is no longer linked.

This situation may arise because the ORACLE instance

has been stopped due to an error or an external operation.

How to correct the error

Database error text........: "ORA-03114: not connected to ORACLE"

Triggering SQL statement...: "CX_SY_OPEN_SQL_DB=============CP "

The current status of the ORACLE instance cannot be determined.

It may be still inactive or the database administrator may have

restarted it.

In any case, all systems that have accessed the ORACLE instance

must be restarted after the ORACLE instance has been restarted.

If you were working on a central system, inform

your system administrator.

If you were working on an external local system, inform

the person responsible for this system.

If you were working on your own local system, restart

the system yourself.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DBIF_REPO_SQL_ERROR" " "

"RSRZLLG0_ACTUAL" or "RSRZLLG0_ACTUAL"

"START-OF-SELECTION"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DBIF_REPO_SQL_ERROR" " "

"RSRZLLG0_ACTUAL" or "RSRZLLG0_ACTUAL"

"START-OF-SELECTION"

NOTE : IS THIS THE REASON OF MY TRANSPORT SYSTEM IS NOT WORKING

PLZ SUGEST ME

Regard's

[Former Member]

Hi,

RSRZLLG0_ACTUAL is a logon distribution program which is not related to transport.

regards,

kaushal