cancel
Showing results for 
Search instead for 
Did you mean: 

Set Event parameter as per SAP Recomendation

Former Member
0 Kudos

Dear Friends,

In our Early watch report given by SAP, has recomended to set EVENT parameter as below

10191

10027

10028

38068

10162

10183

10629

14532

38087

10891

10091

44951

How can we do that.

In our production system there are some values are alredy set for the same.

If any one has done the same, please share with us ?

Regards

Ganesh Datt Tiwari

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

very helpfull

juanmanuel_naranjo
Discoverer
0 Kudos

I jumped to the same issue, try with a recompile all.

Now what i found iin HP-UX is that sometimes ORACLE works fine for ora<SID> but not for <SID>adm. And the workarround was :

- Shutdown oracle isntance & listener

- umount / mount $ORACLE_HOME filesystem

- restart ORACLE instance & listener

- Wow ! Oracle works fine for ora>SID> & <SID>adm ! Creazy no ?

Best Regards

Juan

fidel_vales
Employee
Employee
0 Kudos

Hi,

I assume that you are in 10g.

first I'd check the note 830576 "Parameter recommendations for Oracle 10g" as it gets changed with higher frequency than the EWA.

That way you will be sure to set it properly. (you can use the script from note 1171650 to get a good recommendation)

Keep in mind that the event is one parameter, you have to set all the values in one sentence with the correct syntax. Check the following note also: 596423 Events and SPFILE

For example (adapt for your system) in 10g you can use:

 
ALTER SYSTEM SET                                       
 EVENT='10027 trace name context forever, level 1',
       '10028 trace name context forever, level 1',
       '10142 trace name context forever, level 1',
       '10183 trace name context forever, level 1',
       '10191 trace name context forever, level 1',
       '10411 trace name context forever, level 1',
       '10629 trace name context forever, level 32',
       '10753 trace name context forever, level 2',
       '14532 trace name context forever, level 1',
       '38068 trace name context forever, level 100',
       '38085 trace name context forever, level 1',
       '38087 trace name context forever, level 1',
       '44951 trace name context forever, level 1024'
 COMMENT='BlaBlaBla, note 830576/210'
 SCOPE=SPFILE;

For Oracle 11g it is "easier". For example:

 
ALTER SYSTEM SET EVENT=
'10027',
'10028',
'10142',
'10183',
'10191',
'38068 level 100',
'38085',
'38087',
'44951 level 1024'
COMMENT='SAP_112011_201007 RECOMMENDED SETTINGS'
SCOPE=SPFILE;

Former Member
0 Kudos

Hi Friends,

Thanks for your valuable and usefull help.

I want to install oracle patches. I have Oracle 10g, 10.2.0.2 and OS HP_UX ECC6.0.

How can we know that what patches have been implemented and whats to be implement.

Regards

Ganesh Datt Tiwari

audunlea_hansen
Active Participant
0 Kudos

Hi!

You can list patches installed with command: opatch lsinventory

Which patches to install are something depend on which patches you choose...

Upgrade from 10.2.0.2 to 10.2.0.4 -> one 'patch' you install using Oracle Installer

SBP 012011 adds reccomended missing patches.

Then it's up to you if you need to install other oracle patches (always download patches from SAP, not Oracle)

Regards

Audun

DBA

markus_doehr2
Active Contributor
0 Kudos

I would start with the appropriate notes:

Note 871735 - Current patch set for Oracle 10.2.0

Note 1431752 - Oracle 10.2.0: Patches/Patch Collections for 10.2.0.5

Markus

Former Member
0 Kudos

Hi,

Your comment helped me to set evenr parameters.

Also SAP Note: 596423 - Events and SPFILE is also helpful.

Thanks & Regards,

Ishan

audunlea_hansen
Active Participant
0 Kudos

Hi!

You can set it by log in to SQL*Plus as e.g system or sys.

The syntax is like this:

alter system set event='10027 trace name context forever, level 1','10028 trace name context forever, level 1','10091 trace name context forever, level 1' scope=spfile;

Check out which level you should set those events to.

Since you write only to pfile, you need to bounce the database to activate the parameter.

Regards

Audun

DBA