能否用srvctl 修改service 的设置

phigon

/opt/app/oracle/product/10.2.0/crs/bin@edb3=>urpdb1$./crs_stat -p ora.urpdb.test1.cs |grep AUTO_START
AUTO_START=always
/opt/app/oracle/product/10.2.0/crs/bin@edb3=>urpdb1$./crs_stat -p ora.urpdb.test1.urpdb1.srv|grep AUTO_START
AUTO_START=always
/opt/app/oracle/product/10.2.0/crs/bin@edb3=>urpdb1$./crs_stat -p ora.urpdb.test1.urpdb2.srv|grep AUTO_START
AUTO_START=always

Thanks,
Phigon

phigon

有类似案例的朋友吗？

phigon

Oracle 确认是bug 4134280。到现在还没有补丁包出来。估计12g会修复吧。
谢谢huang的支持。

Yong Huang

Bug 4134280 is unpublished. I can only see the header part of it. Looks like it's a bug for 10gR1? Can you ask Oracle more details? I doubt they'll give you the full bug report because it's unpublished.

Yong Huang

phigon

QUESTION
=========

I have created some service using the command "srvctl add service " in database of RAC 10.2.0.3.
I have set the service to auto_starting using the command "srvctl enable service -d database -d sev
icename.
just as the following
/opt/app/oracle/product/10.2.0/crs/bin@edb3=>urpdb1$srvctl start database -d urpdb
/opt/app/oracle/product/10.2.0/crs/bin@edb3=>urpdb1$./crs_stat -p ora.urpdb.test1.cs |grep AUTO_START
AUTO_START=always
/opt/app/oracle/product/10.2.0/crs/bin@edb3=>urpdb1$srvctl status service -d urpdb -v

Service gxsj is not running.
Service qjsj is not running.
Service test1 is not running.


ANSWER
=======

What you are seeing is an expected and normal behaviour.

User defined services do not startup automatically after Instance re-start.

It should be understood that AUTO_START=always means services will start automatically after reboot and doesn't means
they will start automatically after database re-start.

However, enhancement request is already in place for this and is reviewed by Development as a possible enahancement for a future release.

<<Bug 4134280 >>
Status: Code Resolution
PREFERRED SERVICES LEFT 'OFFLINE' WHEN DATABASE IS SHUTDOWN / RESTARTED.

This enhancement request is internal and as such cannot be viewed by customer.

To explain in a bit more detail, let me try to give you some examples:

1. when you cleanly shutdown the database, whether using SRVCTL or SQLPlus, we change the TARGET state of the database, the database in
stances and the services to OFFLINE. The TARGET of OFFLINE, means that we des
ire these 'resources' to be offline, and we do not want CRS to attempt to resta
rt them.

2. When we start the database back up, whether using SRVCTL or SQLPlus, we set the TARGET value back to ONLINE for the database amd the database ins
tances. This way, CRS knows that the desired state of the instances is to be ONL
INE, and if CRS detects a failure, it will restart the instance(s).

3)It should be understood that Oracle intentionally do NOT set the services back to ONLINE,
because the services are meant as a way to do workload balancing. The reasonin
g behind this is that Oracle cannot know what services you want running, and whe
re you want them to be running after the restart, because some services may be s
et as PREFERRED for a node/instance, and some may be set as AVAILABLE. If we s
tart the services back up automatically on all instances, services may be starte
d on a node where it is not desired. Therefore, the decision was made to leave
the starting of the services up to the user - after a database is cleanly shutdo
wn and restarted, the DBA needs to decide which services to restart, based on th
e load-balancing requirements.

The enhancement request is to at least start up PREFERRED services - so that is being discussed as to how feasible/desirable tha
t is.

Until the enhancement is fixed, you need to manually start the services after instance re-start.

Yong Huang

原帖由 phigon 于 2008-4-2 20:23 发表
...
3)It should be understood that Oracle intentionally do NOT set the services back to ONLINE,
because the services are meant as a way to do workload balancing. The reasonin
...
The enhancement request is to at least start up PREFERRED services - so that is being discussed as to how feasible/desirable that is.

Until the enhancement is fixed, you need to manually start the services after instance re-start.

Thank you, phigon. That was a very sensible note. I was scratching my head a lot on this, until I read that note.

I think they should say CRS restart when they say reboot. I.e., even if the server is not rebooted, as long as CRS is stopped and restarted, the auto_start setting for the *services* will take effect.

Yong Huang

phigon

hehe,welcome.

Your understanding are same with mine.

phigon

Yong Huang

Correction for some of my misunderstandings. (1) TARGET value OFFLINE doesn't necessarily mean the service is disabled. In fact, most of the time it's because the service or some other resources (such as DB) were cleanly stopped. (2) Bug 4134280 says cleanly shutting down *database* causes TARGET value to be set to OFFLINE. We tested it and confirmed it, running Oracle 10.2.0.4. We also tested cleanly stopping database *instances*, and the TARGET value is *not* set to OFFLINE, even if the instance was the only one that was up.

Yong Huang