BDLS crashed in the midaway - Urgent help needed

[Former Member]

Hello All,

After refresh from production into test system, we ran BDLS in the test system for logical system name coneversion in background.

But the job got aborted throwing some database error (as some other activity was going on and due to which rollback segments were not sufficient)

Now when we try to execute the BDLS again, it is giving error telling that a conversion is already going on!!!( even after 3 days from the cancellation of BDLS job)

The error is :

Another Process is Running for Conversion LOG500 -> TRICLNT500

Message no. B1668

Diagnosis

While a conversion is running, you cannot start any further processes for the test run. Depending on the size of the dataset in the system, this process can last a long time.

Procedure

Check whether all the conversion processes in the corresponding system are complete (online or background processing), or whether they have terminated due to a program error. If a process has terminated abnormally, first solve the error and delete the conversion log, then restart the process

Please let me know in case of any pointers? Can we rerun the BDLS? What needs to be done for that?? Any notes??

Best Regards,

Arun

[Former Member]

Hello Babu,

I hope you have checked for obsolute "lock entries"

Regards,

Ammey Kesarkar

[Former Member]

Check SM50, SM21 and SM37.

Also check ST22.

There should be some more information about reason for termination in one of these transactions. Then we can help with the fix so you can run the job again.

[Former Member]

Hi Barry,

We had already checked sm37 and got confirmed that the job is cancelled.

On further analysis of syslogs(sm21) and st22, the job cancelled giving database error ORA-01555: snapshot too old: rollback segment number too small.

This resulted in SAP program termination with dump ABAP/4 processor: DBIF_RSQL_SQL_ERROR .

This happended as some client copy was also going on. But now there is no other activities going on , nothing in SM50 also.

But if we try to run the BDLS in test mode it is giving the error "Another Process is Running for Conversion LOG500 -> TRICLNT500"

Any more information on why this is happening?

Regds,

Arun

[Former Member]

Have you tried stopping and starting the instance to release the "Zombie job"?

[Former Member]

No, I haven't tried restarting the instance.

Also I am not aware of th ejob you have mentioned.

Could you pls give more details.

Regards,

Arun

[Former Member]

The "Zombie job" is the one running that is stopping you from completing the function you wish to do. You try and start it, but it says it is already running. By restarting the instance, it should flush the buffers and remove this job, therefore you'd be able to restart it again.

[Former Member]

No need to restart the instance. The readson is th e log entry is still there, and after you remove the log entry you shluld be able to g ahead.

Please check the log as the follows

This process is recorded in the application log (in Releases as of 4.5A). To display the log, call Transaction SLG1 with object CALE and subobject LOGSYSNAME.

Hope this helps

Jason

[Former Member]

Hi Jason,

Thanks for the valuable information.

I could see some log entries in SLG1 related to BDLS.

Could you please let me know how can we remove/delete these logs and proceed?

Can it be done at application level or it is possible onl at DB level.

Best Regards,

Arun

[Former Member]

Look at note 962674. There are log files in tables bdlshdr, bdlspos and bdlslog. The logfiles can be deleted with program RBDLSMAP_RESET, than you can restart BDLS.

Kind regards, Erik

[Former Member]

Hi,

This is due to the ROLLBACK SEGMENTS.If a large import or export is going on ur system, Rollbacksegments shud be large. .

The rollback segments are used by the oracle to

1. save before images of uncommitted transactions

2. provide read consistency during the runtime of a query

If rows of a table are modified, the before images of the data are copied to a rollback segment. After the commit this information is no longer needed, and the rollback segment is freed by the process.

If a table is modified b/w the time a query is issued and when the records are delivered by the query, the data is read from the rollback segments. However, rollback segments are overwritten or shrunk in a cycle and are not locked for queries. If a query is not finished until the rollback segment is overwritten or shrunk, the query does not receive the data.

When this occurs, oracle issues error 1555 snapshot too old and the query is aborted. A short dump then occurs and the entry in the R/3 system log is generated

can refer the note

Note 648701 - Extending Rollback segments for ORACLE

Note 60233 - Oracle rollback segments, more information

Note 185822 - ora-1555 - cause and action

Regards

Umesh K