remove archfiles only when it is applied to DR rm_archfiles.sh
ARCH_DEST=$1 COMFORT_SPACE=$2 ALERT_LOG=$3 NOTIFY_LIST=dbaoracle@1800flowers.com
ARCH_DEST=$1 COMFORT_SPACE=$2 ALERT_LOG=$3 NOTIFY_LIST=dbaoracle@1800flowers.com
/oracle/scripts/rm_archfiles.sh “/db9/archlog” “90” “/oracle/admin/TESTDB/bdump/alert_TESTDB.log” #!/bin/sh RUNNING=`ps -ef|grep rm_archfiles.sh|grep -v grep|wc -l` if [ $RUNNING -gt 2 ] then echo “Exiting !!! Total $RUNNING occurence of rm_archfiles.sh are running at `date`” exit fi
column currdate new_value pvmdt noprint select ‘pvm_comp_’ || to_char(SYSDATE, ‘DDMONRRRR_HH24MI’) || ‘.sql’ currdate from v$instance; spool &pvmdt set lines 120 pages 2000 set head off set feedback off prompt set pages 5000 lines 120 prompt select ‘prompt ‘||a.owner||’.’||a.object_name||’ – ‘||a.object_type|| chr(10)|| prompt ‘alter ‘|| prompt decode(a.object_type,’PACKAGE BODY’,’PACKAGE’,object_type) || ‘ “‘|| prompt a.owner||’”.’||a.object_name||’ compile ‘|| prompt…
Read More “run this before doing any dbchange pvm_pre_change.sql” »
Step:1 ====== Do following steps to implement encrypted listener password. $ lsnrctl LSNRCTL> set current_listener LISTENER LSNRCTL>set save_config_on_stop on LSNRCTL> change_password Old password: New password: e1 Reenter new password: e1 LSNRCTL> set password Password: e1 LSNRCTL> stop Step:2 ====== Check your listener.ora file Entries similar to the following should have been added to your listener.ora…
# Listener Security #
dedicated dial-in number 1 (218) 339-2699 access code 328166
column currdate new_value pvmdt noprint select ‘pvm_comp_’ || to_char(SYSDATE, ‘DDMONRRRR_HH24MI’) || ‘.sql’ currdate from v$instance; spool &pvmdt set lines 120 pages 2000 set head off set feedback off prompt set pages 5000 lines 120 prompt select ‘prompt ‘||a.owner||’.’||a.object_name||’ – ‘||a.object_type|| chr(10)|| prompt ‘alter ‘|| prompt decode(a.object_type,’PACKAGE BODY’,’PACKAGE’,object_type) || ‘ “‘|| prompt a.owner||’”.’||a.object_name||’ compile ‘|| prompt…
Problem Description ——————- You create a database event trigger that fires each time a user connects to the database. For any reason, the login trigger becomes invalid. (The trigger is retrieving information from a table that may be inadvertently dropped.) Who can connect? Solution Description ——————– Connect under a user who owns the following system…
kill all processes from user name atsscript on solaris. pkill -9 -u atsscript