Skip to Main Content
Forums

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

any one have RMAN active datbase cloning steps ?

Chetan YadavJul 12 2021 — edited Jul 13 2021

we are tried much time to clone DB, but we are not able to restore it,
Now are planning to do Active DB cloning.
please if someone has steps for cloning please share with us.

thanks in advance.
Chetan yadav
This post has been answered by User_0IK0L on Jul 16 2021
Jump to Answer

Comments

EdStevens
948744 wrote:
Hi, 

I have been experimenting on exception handling in oracle plsql. During my experimentation I made the following anonymous plsql block.

<snip>

Did you notice the name of this particular forum?

Please close this thread and ask your question in 3077
BluShadow
Question now moved to Oracle Discussion Forums » Oracle Database » SQL and PL/SQL
BluShadow
Answer
The problem in your block 2 code is that you've not just used the same exception name, but you've assigned them with the same exception code. If the code is different then it will work...
SQL> set serverout on
SQL> ed
Wrote file afiedt.buf

  1  <<outer_block>>
  2  declare
  3      exc exception;
  4      pragma exception_init(exc,-20001);
  5  begin
  6      <<inner_block>>
  7      declare
  8          exc exception;
  9          pragma exception_init(exc,-20002);
 10      begin
 11          raise_application_error(-20002,'Error raised');
 12      exception
 13          when outer_block.exc then
 14              dbms_output.put_line('outer Exception caught ' );
 15          when inner_block.exc then
 16              dbms_output.put_line('Inner Exception caught ' );
 17      end;
 18* end;
SQL> /
Inner Exception caught

PL/SQL procedure successfully completed.

SQL> ed
Wrote file afiedt.buf

  1  <<outer_block>>
  2  declare
  3      exc exception;
  4      pragma exception_init(exc,-20001);
  5  begin
  6      <<inner_block>>
  7      declare
  8          exc exception;
  9          pragma exception_init(exc,-20002);
 10      begin
 11          raise_application_error(-20001,'Error raised');
 12      exception
 13          when outer_block.exc then
 14              dbms_output.put_line('outer Exception caught ' );
 15          when inner_block.exc then
 16              dbms_output.put_line('Inner Exception caught ' );
 17      end;
 18* end;
SQL> /
outer Exception caught

PL/SQL procedure successfully completed.
Marked as Answer by sudher · Sep 27 2020
BluShadow
Oh, and the reason for that is described here...

http://docs.oracle.com/cd/B19306_01/appdev.102/b14261/errors.htm#sthref2000

PRAGMA is a compiler directive, not a run time directive, so you can't re-assign the same code to different exceptions on-the-fly during execution of your code, hence why the code was complaining because it was considering your outer EXC and inner EXC to be the same code and hence you were effectively testing for the same exception value twice, regardless of you prefixing the name with the outer/inner labels.

You can certainly re-use exception names at run time and that follows standard variable scoping rules, but if you assign exception names to actual error code values, those need to be either unique or, if you've assigned multiple exception names to the same code you need to ensure you only test for one of them within your exception handlers.
1 person found this helpful
1 - 4

Post Details

Added on Jul 12 2021
#database, #performance-availability, #recovery-manager-rman, #rman
11 comments
114 views