Solved: SAP Server slow after DR configuration

Former Member · ‎08-23-2011

Hi,

Our PRD server has become very slow after DR configuration.

We have increased only Sessions parameter in SPFILE from 96 to 120 as SAP MMC was not starting and was giving error

ERROR => CONNECT failed with sql error '604'

No other parameter either from SAP or Oracle level changed, but still our primary server has become very slow.

Lot of work processes in SM50 occupying by SAPSYS, SAPJSF and DDIC running background job

ARFC:C0A8D8B413484E537FB5021C job running automatically and taking lot of time and work processes.

Ours is SAP ECC 6.0,

Oracle 10.2.0.2,

Windows 2003 - RAM=8GB

2MBPS link between Primary and DR site and around 35 archive logs generates daily

Pls suggest

Edited by: james bond on Aug 23, 2011 6:58 PM

Former Member · ‎08-23-2011

Hi,

We need to check the items first, below;

1) Do you face with the performance problem, even standby system is down?

2) Did you try to copy offline redolog files manually with the copy and paste? What about the file copy performance?

3) Could you execute ping <DR host> on primary and provide the results here?

4) Could you execute tnsping <DR TNS name> on primary and provide the results here?

5) Could you check and provide event column on long running statements, by ST04 -> Performace -> Wait Event Analysis -> Session Monitor?

Best regards,

Orkun Gedik

Former Member · ‎08-24-2011

One more hint - 8G of RAM is too small for Production instance (I am not sure on your load and no. of users), just compare the load and increase

Former Member · ‎08-24-2011

I don't think your DR is playing a role here.

Just try to find out the cause at performance of database, application and then network.

What is the memory allocation to your DB and what are the parameters configured?

Is it DB+CI?

*Oracle 10G is out of support, plan your DB upgrade

Regards,

Nick Loy

SAP Server slow after DR configuration