cancel
Showing results for 
Search instead for 
Did you mean: 

ECC 6.0 SR2 Installation

0 Kudos

Hello

I am installing ECC 6.0 SR2, before installation checked the pre-requisite for HP-UX 11.31 with ORACLE Database.

It is showing the following OS Kernel parameters to set with values.

dbc_max_pct

dbc_min_pct

nfile

msgmap

msgssz

msgseg

But, when I look into OS Kernel parameters, these all are not there in HP UX 11.31

Can anyone suggest me, how to go ahead with these parameters as well as where these parameter values effect if we omit.

BR

Jayakar

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

I got inf. from HP, Closing this Question

Former Member
0 Kudos

HI Team,

here we also facing the same issue. can u please share the solution for this.??

Former Member
0 Kudos

Hi Jayakar,

When you change any paramenter in profile or add the parameter after save the parameter you have to activate that profile. After activate you have to restart the system then you will get the effet of the changed parameters.

If you have another query pls mentioned here.

Regards,

Anil

0 Kudos

Dear Anil,

Do we can add new parameters to kernel wich are not there in the existing HP UX 11.31? Because I read so many HP forums, which stats that these parameters are required for 11.23 version, not for 11.31.

Please advice

Regards

Jayakar

Former Member
0 Kudos

Hi,

Yes you have to add new parementer with value and check it.

Regards,

Anil

0 Kudos

Dear All,

I got the following information from HP, this is fyi... only

dbc_min_pct and dbc_max_pct have been replaced with filecache_min and filecache_max for HP-UX 11.31.

dbc_min_pct and dbc_max_pct are dynamic kernel parameters for HP-UX 11.23 only.

Tunables msgmax, msgssz, msgmap, msgseg are obsolete in HP-UX 11i v3.

New dynamic tunable msgmbs is added, which indicates the maximum (in megabytes) kernel memory to be used for messages waiting to be received. This new tunable replaces the function of the obsolete msgssz and msgseg tunables. Lowering the tunable value has no effect on any active messages, even if the new tunable value is less than the total number of message bytes currently enqueued. However, no new messages may be queued until the total number of bytes falls below the setting of msgmbs.

Tunables msgmni, msgtql are made dynamic. These tunables can be increased or decreased dynamically with out rebooting the machine. Lowering msgtql has no effect on any queued messages, even if the new tunable value is less than the number of queued messages. However, no new messages may be queued until the number of messages falls below the setting of msgtql. Lowering msgmni has no effect on any active message queues, even if the new tunable value is less than the number of queues created in the system. However, no new queues may be created until the number of active queues falls below the setting of msgmni.

The tunable msgmnb is unchanged.

Dynamic tuning adjustments to msgmbs, msgmni, msgtql may be done using SAM or the kernel configuration command kctune.

Thanks all

Regards

Jayakar Reddy