Troca de senhas do SYSTEM e SYS em ambiente de cluster

[vieriParticipante]

Na verdade acho que ambos utilizam os 2 usuários.

Para descobrir se terá problemas,
com a mudança de senha vc pode criar uma trigger de auditoria de logon ai ficará quem e quando se conecta na sua base.

cfrme a abaixo:

CREATE TABLE "SYSTEM"."AUDIT_TABLE"
( "INSTANCE_NAME" VARCHAR2(100 BYTE),
"USERNAME" VARCHAR2(100 BYTE),
"COMMAND" VARCHAR2(100 BYTE),
"OSUSER" VARCHAR2(100 BYTE),
"PROCESS" VARCHAR2(100 BYTE),
"MACHINE" VARCHAR2(100 BYTE),
"TERMINAL" VARCHAR2(100 BYTE),
"PROGRAM" VARCHAR2(100 BYTE),
"ACTION" VARCHAR2(100 BYTE),
"CLIENT_INFO" VARCHAR2(100 BYTE),
"LOGON_TIME" VARCHAR2(100 BYTE),
"CLIENT_IDENTIFIER" VARCHAR2(100 BYTE)
) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 81920 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS" ;

create or replace trigger system.trg_audit_logon
after logon
on database
declare
begin
if ( user 'SYS' and user 'SYSTEM' and user 'SYSMAN')
then
insert into system.audit_table
(
INSTANCE_NAME
, USERNAME
, COMMAND
, OSUSER
, PROCESS
, MACHINE
, TERMINAL
, PROGRAM
, ACTION
, CLIENT_INFO
, LOGON_TIME
, CLIENT_IDENTIFIER
)
select
i.INSTANCE_NAME
,s.USERNAME
,s.COMMAND
,s.OSUSER
,s.PROCESS
,s.MACHINE
,s.TERMINAL
,s.PROGRAM
,s.ACTION
,s.CLIENT_INFO
,s.LOGON_TIME
,s.CLIENT_IDENTIFIER
from v$session s, v$instance i
where s.sid = (select sid from v$mystat where rownum = 1 );
end if;
commit;
exception
when others then
NULL;
end trg_audit_audit_logon;