cancel
Showing results for 
Search instead for 
Did you mean: 

database parameters for 600 usertasks?

Former Member
0 Kudos

Hello Everybody

I have a maxdb-database version 7.6.0034 on a linux server with 16 Giga memory with

Cache_size 800000

MaxUsertasks 500

Cat_Cache_Supply 64064

MaxCPU 4

The data aera is 50 Giga (perm 35 Giga)

The Data Cache Hit Rate = 100%

I have to increase the MaxUsertasks to 600.

Are ther any other parameters i have to change! (Cache_size,Cat_Cache_Supply)

Any help welcomed.

Best regards

Albert

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

> I have a maxdb-database version 7.6.0034 on a linux server with 16 Giga memory with

Any reason why you use that ancient build?

Is this 64bit?

> Are ther any other parameters i have to change! (Cache_size,Cat_Cache_Supply)

Run a param_checkall after you changed the parameter.

Markus

Former Member
0 Kudos

Hello Marks

Yes! 64 bit

Need time and knowhow to update to a newer version. (produktion database on an linux cluster installed from a software company,test and development server have to be updatet also,...)

More then 500 users yesterday(first time ever), need to change maxusertasks quickly.

Best regards

Albert

lbreddemann
Active Contributor
0 Kudos

> More then 500 users yesterday(first time ever), need to change maxusertasks quickly.

You are aware that your 500 frontend users don't match 500 database sessions, are you?

Usually you will have much less SAP workprocesses (=> this number determines how many database sessions must be allowed) than frontend users.

regards,

Lars

Former Member
0 Kudos

Hello Lars

This is not our SAP System, wich is running with MaxDB 7.6 under HP-UX.

The system i have to change has more then 500 named database users.

Any help with the parameters ?

Best regards

Albert

lbreddemann
Active Contributor
0 Kudos

> This is not our SAP System, wich is running with MaxDB 7.6 under HP-UX.

I see.

> The system i have to change has more then 500 named database users.

> Any help with the parameters ?

I wouldn't care too much about the caches for this.

Instead concurrency will be one of the major issues to deal with.

Therefore I'd make double sure not to run into lock escalations ever (MAXLOCKS parameter is a good start for that).

Also checking whether you can increase MAXCPU surely won't be bad to the overall performance impression...

Hope you've got the DBAnalyzer running all the time to get a good picture of the MaxDB workload.

regards,

Lars