on 02-12-2015 9:39 AM
Hi Experts,
We are upgrading our Solman stack from SP04 to SP12 using Sum Tool.
In 5.5 Pre-processing phase MAIN_SHDIMP/RUN_RSCPINTS_PUTTBREST_STD is running for a long time Approx . 5 hours.
The job is Active in SM37
Can you please let us know is there any issue or will the phase takes long time to complete.
Thanks in Advance..
Regards,
Krishna.M
Hi,
Could you share complete dump from ST22 ? If possible could you check with table space sizes and try to extend if required.
Issue generated could be because of shortage of resources (Space as well as memory). Addition to it please share failed job log from SM37.
Hope this will help you.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As long as the Job is active it s fine though it has been running too long .
Check the job status in SM37 and also monitor it in SM66 .
Also make sure that you have sufficient space in all the filesystems .
Dont want the job to fail so take all the above precautions . If possible can you send the db2diag file from the central system
Also take a trace using ST05 or ST12
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manu,
For this we have checked in TX:ST22,got run
timeerror for every 6minites.In log file shows like below ,
What happened?
Error Text of the Database: "SAPLSPOABP in R3DS102100 type *SQLPKG not
found.
MSGID= Job=071806/DS1ADM/WP42"
We have attached all logs and screen shots related.
Can you please suggest us.
Thanks
Krishna
Hi Krishna ,
Please check the CPU stats in the Central server where the DB is running .
Check whether there is any filesystem bottleneck
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manu,
Please check below job status(attached),In job log i can not find any thing and i have checked in file system also there is no bottleneck in central system.I have planed to increase our RAM also,it is god or not please confirm once.
Please confirm is there any issue or generally this phase will take log time.Please give me you contact no or Skype ID i will reach you once.That is helpful for me.
Thank you
Krishna
Hi Krishna ,
You can check whether the archiving is on with the following command
db2 get db cfg for < SID > | grep LOGARCHMETH1
1 ) Can you paste the last 200 lines of your db2diag file
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Krishna,
One can check the /abap/tmp & /log folder for current status and update on the jobs status and also if the DB is ORacle check for the waiting sql statments.
Which can help you to get more insight on the processing happening in SUM.
Regards,
ram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Krishna ,
Sorry for the typo .
What is your DB ? is the archive log turned on for the DB
Also share your CPU stats
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
What is the CPU usage and memory usage in the server .
Have you turned on Archiving?
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think here would be any issues,as i already said due to low hardware configurations job is taking time to complete.If possible could you share complete hardware details & job log from SM37.
Regards,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
Still from yesterday onwards, the Pre-processing phase is going on. The job is active in SM37.
Can you please let us know is there any issues..
Regards,
Krishna.M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You should provide more information about the system details (OS and DB)
Secondly check the logs at the OS level <SUM>/abap/log and <SUM>/abap/tmp directories.
Perform a "Check Status" for the job in Tx SM37 and see if the status of the job changes.
Cheers
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Hardware details :
Harddisk : 350 Gb
Ram : 8 Gb
With this configuration you surely need to wait more.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
Thanks for your quick response..
Hardware details :
Harddisk : 350 Gb
Ram : 8 Gb
Sure, i will wait until the job to complete.
Regards,
Krishna.M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Krishna ,
As long as the Job is running in the system , you dont have to worry . The amount of time it will take to run depends on your CPU , MEMORY and no of process you have configured .
Check the job process in SM66 and SM50 . Also check whether any wait situation is there in the system say like shortage of workprocess etc . Also check SM21 and ST22 .
You should be fine , wait till the job completes
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Could you share system hardware configurations,as you're aware upgrade also depends on the hardware and system parameters on which process is going on.
I don't think here you need to worry about the long running of job until n unless any issue comes,and let the job to be completed successfully.
Regards,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.