Dialogue WP cannot be Killed,License for DR test in sap

Q-:
Dialogue WP cannot be Killed
dp mon , sm50 -> cancel with core , cancel without core , kill from OS with pid.
OS : Linux
SAP : SAP ECC 6.0
Ans-:
user associated with the work process you want to kill (in sm50). If so try sm04 - select the user - user drop down menu - log off user.
get the PID and kill it from OS level .

check the ps -ef |greap PID. is it there

Go to SM50, select the DIA process you want to kill and in menu line select "Administration -> Process -> Restart After Error -> No"
Then kill the PID from OS.
If it works, you can switch the process back to "Restart After Error -> Yes".

Q-:
When Error License Check problem accur? how to solve this problem it could happen we use temperarily licence key.

Break the mirrored disks and mount them to another AIX Unix server for a DR test
Ans-:
You should get a permanent license key. Then you will not have additional things to remember in a DR situation
yes you can also use the temporarily license key for DR but in future you need permanent

Q-:
When this type of error occur
Database error -55555 at OPC
> dsql_db6_open: Unable to find initial entry as expected
SAP system with backend DB2, operating system AIX IBM

ans-:
it just happened in one application server (happens to be the CI), so I performed a buffer reset with "/$SYNC" transaction.

Additionally, it might be worthy to check if the logs always points to the same work processes, in which case is advisable to kill them.


Q-: question regarding BDLS. I did a db refresh last month on a BW system and when I run the BDLS it took nearly 20k seconds to complete the conversion. This is normal. However recently I did a db refresh on the same system, and the bdls only run for 800 seconds. I checked the log slg1 and compare it to the previous month it is the same. So my question is, why the significant time decrease? The only change that I know was it used to be no application server, but now there are additional two. Although I dont think this can solve as bdls run using only one dialog process from the central instance and during the bdls running the application servers were down.
sol-:
you 100% that you chose the exact same source and destination logical system names?

You know that you have to at least convert ECC and BW logical systems names? so, this means running this twice on your BW system?

Are you sure that you have not forgotten to uncheck option "TEST run"?
Also read http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4796 for a very godd strategy to make BDLS run much faster.