Client failover troubles

Question

Hello again
I configured Client failover to OCI Clients as follow:
tnsnames on app client:
DATAGUARDOCI =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = PRIMARY)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = STANDBY)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA=
(SERVICE_NAME=DATAGUARD)
Service name on Primary:
begin
dbms_service.create_service
service_name => 'service',
network_name => 'service',
FAILOVER_METHOD => 'BASIC',
FAILOVER_TYPE => 'SELECT',
FAILOVER_RETRIES => 200,
FAILOVER_DELAY => 1);
end;
Trigger as Uwe Hesse shows us:
create trigger myapptrigg after startup on database
declare
v_role varchar(30);
begin
select database_role into v_role from v$database;
if v_role = 'PRIMARY' then
DBMS_SERVICE.START_SERVICE('myapp');
else
DBMS_SERVICE.STOP_SERVICE('myapp');
end if;
end;
I shutdown standby and start it up.
I make many connections using DATAGUARDOCI tnsnames entry and sometimes I connect to primary and sometimes to standby. I don't know why trigger doesn't work on standby.
Thanks for helping

Answer 1

When you do
lsnrctl statuson your Standby System, does the service DATAGUARD show up? It shouldn't while the DB there is in Standby Role.
BTW the name is a little misleading, don't you think? The service is supposed to be offered on the respective Primary for productive usage by applications.
All I can say is that the setup described in the posting works exactly as listed there - because I followed our documentation :-)
LOAD_BALANCE should play no role here, because only one (the Primary) Database is supposed to offer the service. That seems to be exactly your problem here:
You offer the service on the Standby also. Stop doing that :-)
Kind regards
Uwe Hesse
http://uhesse.wordpress.com