26.03.2013-WebSphere diary

http://www-01.ibm.com/support/docview.wss?uid=swg21569953 увеличил время таймаута на медийке To resolve the issue increase the was.notification.timeout to 1200 (seconds) in WP DeploymentService either from WebSphere Admin Console or Dmgr. If the property is not listed under custom properties, please add the above property.

Убиваем каскадно по SQL_ID

Убиваем в цикле по SQL_ID:   begin for sessions in ( SELECT sid, serial# FROM v$session WHERE username is not null AND sql_id =’ fq2pu19x934vn’) loop execute immediate ‘ alter system kill session ‘ ‘ ‘ ||sessions.sid|| ‘ , ‘ ||sessions.serial#|| ‘ ‘ ‘ ‘ ; end loop; end;   только кавычки правим на адекватные

Hot create stanbdy

DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE DORECOVER SPFILE SET DB_UNIQUE_NAME=»st_mjidb» comment «Is a duplicate» SET LOG_ARCHIVE_DEST_2=»service=st_mjidb ASYNC REGISTER VALID_FOR=(online_logfile,primary_role)» set audit_file_dest=»/u01/app/oracle/admin/mjidb/adump» set control_files=»/Data/oradata/mjidb/control01.ctl»,»/Data/oradata/fast_recovery_area/mjidb/control02.ctl» set DB_FILE_NAME_CONVERT=’mjidb’,’st_mjidb’ set LOG_FILE_NAME_CONVERT=’mjidb’,’st_mjidb’ SET FAL_CLIENT=»st_mjidb» COMMENT «Is standby» SET FAL_SERVER=»mjidb» COMMENT «Is primary» NOFILENAMECHECK; чтоб стендбай накатил логи(на нем): ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;