Please post the output of the following:
1 person found this helpful
It is very important to perform post clone activities after PROD clone to TEST or other environments.
1. did you resize SGA/PGA and other DB parameters after clone? it will set default as per template.
2. have you put all schedule CM/other jobs on hold after clone? Most of the time this cause performance problem after clone. Basically check CM for Schedule/Running jobs, Check DB for any DBA_JOBS
3. Scale down CM workers
4. Check any integration link which clone instance trying to access
5. Check profiles are changed from PROD -> TEST
Mostly it is CM or SGA which cause performance problem after clone.
Besides, check the following items also.
Make sure to run Purge concurrent Request on the Target system and check again.
Make sure there is no runaway process on database/application tier.
Runaway process is process taking unexceptionally long time with high CPU or Memory usages.
Guys am really sorry for the delayed reply. I had rebuild the entire Server as we experienced some air conditioning issues, that caused OS level crash.
I have done following
Changed the YUM repositories for the RHEL 5 with Oracle public yum repos
Upgraded the OS to 5.8
Installed R12 pre-requisites through add-on repo
Clone the instance with a cold backup
Once the instance was up, I did a schema gathering and the performance is as expected. I think, I had ignored the kernel parameters earlier which were configured against the PRODUCTION server hardware resources, that was causing the delays and crash downs earlier.
Thank you all for your kind inputs
I'm not a qualified DBA, however, during the absence of the DBA, I am capable of doing meaky tasks like cloning the Production to a TEST instance. If you please, detail me about the following point
"Check profiles are changed from PROD -> TEST"
Before cloning you should always make sure that you meet all the requirment for the installation on specific platform relvant to your installation from note Oracle E-Business Suite Release 12 Installation Guidelines (Doc ID 405565.1)
Basically you follow Note Cloning Oracle Applications Release 12 with Rapid Clone (Doc ID 406982.1)
There are many profile options which needs to be changed to reflect test environment, for example there is a profile "Site Name" users will see on forms titile bar, you may want to change that to "test" after cloning your production to test.
I thought Amit was making some other references. Well, we do change the site name to TEST
1 person found this helpful
Yes, Site Name is one of them. There are multiple places you might need to change the profiles after clone
default printers personal user's profiles
Site SSO profiles if you have Single Sign-on Implementations
Site timeout settings
Thank you very much Amit. Though I stated I am not a qualified DBA, I was involved in most of the DBA activities from last 5-6 years. I think I found the main culprit(s) for the degraded performances. I had a vision instance and I lifted up the sysctl.conf and limits.conf files from the same and replaced the source system files with them.
Once after the restart, I can say, the performance of the TEST instance is much better than the PRODUCTION instance
Thank you guys for the suggestions and advices. I've noted them down and will always try to take precautions in future.