Posts

Showing posts from July, 2016

You know what? How to debug RMAN !!

Most of cases of RMAN might be critical situation except daily or regular backup operation. Ok let's look at when you need to use RMAN for restore or recover data from backup. We can guess that RMAN seems not doing anything but ..... you don't know the inside of RMAN command execution. Then there is a way to check it out. DEBUG or TRACE for RMAN process or command. Let's give it a go for it. First of all, there are 2 ways of generating log file from RMAN command. From RMAN prompt; RMAN> spool log to '/tmp/rman_logtest.log'; RMAN> "run-rman-command" RMAN> spool log off; From the command prompt; $ rman target catalog log=/tmp/rman_logtest.log RMAN> "run-rman-command" RMAN> exit; In cases of RMAN operation failure, debug trace is good to collect debugging information that can help troubleshoot the underlying causes. You can use below syntax to generate debug trace: $ rman taret / catalog debug trace=/tmp/rm

You know what? How to debug RMAN !!

Most of cases of RMAN might be critical situation except daily or regular backup operation. Ok let's look at when you need to use RMAN for restore or recover data from backup. We can guess that RMAN seems not doing anything but ..... you don't know the inside of RMAN command execution. Then there is a way to check it out. DEBUG or TRACE for RMAN process or command. Let's give it a go for it. First of all, there are 2 ways of generating log file from RMAN command. From RMAN prompt; RMAN> spool log to '/tmp/rman_logtest.log'; RMAN> "run-rman-command" RMAN> spool log off; From the command prompt; $ rman target catalog log=/tmp/rman_logtest.log RMAN> "run-rman-command" RMAN> exit; In cases of RMAN operation failure, debug trace is good to collect debugging information that can help troubleshoot the underlying causes. You can use below syntax to generate debug trace: $ rman taret / catalog debug trace=/tmp/rm