SID Take Precedence Over *

Today was changing parameters in a RAC, as applied to all three instances, I used the option SID = ‘*’ in the command alter system set. He problem has come to start the first instance, as it needed to bounce him to take the change. I look at the parameter after started to confirm and I see this change as before. After a little research I see the spfile.ora has defined the SIDs of the three request for parameters, ie

  • sieb1.memory_max_target
  • sieb2.memory_max_target
  • sieb3.memory_max_target
  • *.memory_max_target

As I changed the parameter to *, you have not changed the values for sieb1, sieb2 and sieb3. Using RTFM I see;

The SID clause lets you specify the SID of the instance where the value will take effect.

Specify SID = ‘*’ if you want Oracle Database to change the value of the parameter for all instances that do not already have an explicit setting for this parameter.

Specify SID = ‘sid’ if you want Oracle Database to change the value of the parameter only for the instance sid. This setting takes precedence over previous and subsequent ALTER SYSTEM SET statements that specify SID = ‘*’.

In my case it is already defined. The solution is to set up one by one sieb1, sieb2 and sieb3 (this is the chosen one) or erase all three.

HTH – Antonio NAVARRO

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s