- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: rman and cluster
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2005 10:48 PM
тАО08-11-2005 10:48 PM
rman and cluster
I want to ask about Oracle offline backup
using rman, but in cluster environment.
When I'm trying to stop DB for offline backup using rman,the package monitoring found this and moved/halted the package, where this DB is.
How I could stop the monitoring of the
services /oracle/ so I could stop/start
the DB with rman, without the halting of
package.
Regards,
Stan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2005 10:53 PM
тАО08-11-2005 10:53 PM
Re: rman and cluster
However if you want to shutdown the database without the cluster failing over, you can use a lock file.
eg if before you run your backup you touch a file called /tmp/oraclebackup, then remove it when the backup is finished. You can then change your cluster monitor scripts to only failover if this lock file does not exist.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2005 11:14 PM
тАО08-11-2005 11:14 PM
Re: rman and cluster
As Simon suggetion is the only best way to carry out your offline backup to avoid package to failover.
Similar mechanism I used in one of the clustser solution like.
while [ true ]
do
## Below if-then statement is included for Backup purpose
if [ ! -f /opt/backup/.runtime ]
then
statment1;
....
fi
done
Where /opt/backup/.runtime is a flag file.
There is abrupt way to halt the monitor service using command (not recommended)
# cmhaltserv
But, there is no way to start manually.
Regards,
Rajesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2005 12:03 AM
тАО08-12-2005 12:03 AM
Re: rman and cluster
also allow me to add:
With RMAN it is preferrable that you to an Online backup. No need to shutdown your database.
regards
yogeeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2005 12:10 AM
тАО08-12-2005 12:10 AM
Re: rman and cluster
So let me remark, that the monitoring of Oracle processes in doing by PIDs.
So if I stop/start the Oracle without
halting package, these PIDs will be changed and the monitoring script will check the
wrong array of PIDS. So is there any workarround? May be another changes of the monitoring script?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2005 12:57 AM
тАО08-12-2005 12:57 AM
Re: rman and cluster
Replace the monitor_process with the below. Once you do that, you just need to touch the file /var/tmp/${ORACLE_SID}_MAINT and monitoring is suspended until you remove it.
function monitor_processes
{
typeset -i n=0
for i in ${MONITOR_PROCESSES[@]}
do
MONITOR_PROCESSES_PID[$n]=`ps -fu oracle | awk '/'${i}$'/ { print $2 }'` #JAGad06432
print "Monitored process = ${i}, pid = ${MONITOR_PROCESSES_PID[$n]}"
if [[ ${MONITOR_PROCESSES_PID[$n]} = "" ]]
then
print "\n\n"
ps -ef
print "\n *** ${i} has failed at startup time. Aborting Oracle. ***"
set -m
nohup ${0} fault & # The script calls itself with the fault option.
set +m
sleep 999999
fi
(( n = n + 1 ))
done
sleep ${MONITOR_INTERVAL}
while true
do
#
# Added the following code to allow for the Oracle databases to be
# taken down for maintenance without causing a package failure.
#
# To use, touch the file /var/tmp/${ORACLE_SID}_MAINT (where
# ORACLE_SID is the SID of the database which is to have maintenance).
#
# To resume monitoring, remove this file.
#
# Added 9/11/2002 GLP
#
if [ -f /var/tmp/${ORACLE_SID}_MAINT ]
then
print "Entering Maintenance mode at $(date)"
while [ -f /var/tmp/${ORACLE_SID}_MAINT ]
do
print "Remove /var/tmp/${ORACLE_SID}_MAINT file to resume monitoring"
sleep ${MONITOR_INTERVAL}
done
print "Exiting Maintenance mode at $(date)"
#
# Since Oracle could have been shutdown - the PIDs could have changed.
# The next two statements will reevaluate the PIDs for monitoring.
# Added 9/11/2002 GLP
#
typeset -i n=0
for i in ${MONITOR_PROCESSES[@]}
do
MONITOR_PROCESSES_PID[$n]=`ps -fu oracle | awk '/'${i}$'/ { print $2 }'` #JAGad06432
print "Monitored process = ${i}, pid = ${MONITOR_PROCESSES_PID[$n]}"
if [[ ${MONITOR_PROCESSES_PID[$n]} = "" ]]
then
print "\n\n"
ps -ef
print "\n *** ${i} has failed at startup time. Aborting Oracle. ***"
set -m
nohup ${0} fault & # The script calls itself with the fault option.
set +m
sleep 999999
fi
(( n = n + 1 ))
done
fi
for i in ${MONITOR_PROCESSES_PID[@]}
do
kill -s 0 ${i} > /dev/null
if [[ $? != 0 ]]
then
print "\n\n"
ps -ef
print "\n *** ${i} has failed. Aborting Oracle. ***"
set -m
nohup ${0} fault & # The script calls itself with the fault option.
set +m
sleep 999999
fi
done
sleep ${MONITOR_INTERVAL}
done
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2005 01:28 AM
тАО08-12-2005 01:28 AM
Re: rman and cluster
My thought here to avoid PID changes.
Use the package monitoring script with flag check.
Though you are using RMAN, supports online backup, this you can use.
OR
Just close the database and umount the database before start backup.
Post backup:
mount and open the database, it reduces the startup time of database.
Good luck,
Cheers,
RAjesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2005 01:30 AM
тАО08-12-2005 01:30 AM
Re: rman and cluster
Instead full shutdown of Database, just
> alter database close;
> alter database umount;
wouldn't effect any running oracle pids/services.
Regards,
RAjesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2005 02:12 AM
тАО08-12-2005 02:12 AM
Re: rman and cluster
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2005 05:46 AM
тАО08-12-2005 05:46 AM
Re: rman and cluster
If the file existed then the system didn't monitor the database (this is how we do maintenance, including cold back ups).
When finished just delete/rename the file.
Check your package for this functionality, it may already be in there.