Home » RDBMS Server » Backup & Recovery » RMAN duplicate nopen from 11g to 12c fails (oracle 12.1.0, windows server 2008)
RMAN duplicate nopen from 11g to 12c fails [message #667839] Fri, 19 January 2018 10:25 Go to next message
aviana
Messages: 106
Registered: July 2007
Senior Member
Hi I followed procedure to duplicate database from 11.2.0.3.0 to 12.1.0 using RMAN.

Followed the document Oracle support Doc reference-Upgrade to 12c (12.1 /12.2) through RMAN Duplicate using BACKUP LOCATION with NOOPEN clause (Doc ID 2022820.1) as it is similar.

The duplication worked fine until the end and I followed all steps inclusing post upgrade tasks.

But now I am unable to open the database .When trying to open, it comes up with a error (I already did alter database open resetlogs upgrade and it worked but I am unable to connect to any schemas after this, as its warning I can only connect as sysdba.So I shut down the database, mounted& tried alter database open and error is coming)



SQL> alter database open;

SQL> alter database open;

alter database open

*

ERROR at line 1:

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00704: bootstrap process failure

ORA-00604: error occurred at recursive SQL level 2

ORA-00904: "I"."UNUSABLEBEGINNING#": invalid identifier

Process ID: 7488

Session ID: 6 Serial number: 60620



Please can someone see this before?any easy way to fix this? How can I open the newly duplicated 12c database now(its a UAT environment)



RMAN upgrade from one version to other, is a oracle recommended method from 11g to 12c.

I did not try the same version RMAN duplication and then upgrade because we had space issues to install both versions of oracle in UAT

Please help to fix the above.
Re: RMAN duplicate nopen from 11g to 12c fails [message #667840 is a reply to message #667839] Fri, 19 January 2018 10:56 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10690
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
Your ORACLE_HOME is not properly set.
And I assume you did everything as said in the support document.

[Updated on: Fri, 19 January 2018 11:19]

Report message to a moderator

Re: RMAN duplicate nopen from 11g to 12c fails [message #667862 is a reply to message #667840] Mon, 22 January 2018 07:00 Go to previous messageGo to next message
aviana
Messages: 106
Registered: July 2007
Senior Member
Hi oracle_home is set properly and I verified in registry.
I tried to re run the upgrade script and post upgrade tasks again after opening the database in upgrade mode.

The upgrade that I ran using catctl.pl has failed now, posting the results below. Please suggest how to fix?


F:\oracle\product\12.1.0\dbhome_1\RDBMS\ADMIN>%ORACLE_HOME%\perl\bin\perl\catctl.pl
-n 6 -l %ORACLE_HOME%\diagnostics\catupgrd.sql



Argument list for [catctl.pl] SQL
Process Count n = 6

SQL
PDB Process Count N = 0

Input
Directory d = 0

Phase
Logging Table t = 0

Log
Dir l =
F:\oracle\product\12.1.0\dbhome_1\diagnostics

Script s = 0

Serial
Run S = 0

Upgrade
Mode active M = 0

Start
Phase p = 0

End
Phase P = 0

Log
Id i = 0

Run
in c = 0

Do
not run in C = 0

Echo
OFF e = 1

No Post
Upgrade x = 0

Reverse
Order r = 0

Open
Mode Normal o = 0
A.Debug
catcon.pm z = 0
B.Debug
catctl.pl Z = 0

Display
Phases y = 0

Child
Process I = 0


a.catctl.pl
version: 12.1.0.2.0

Oracle
Home = F:\oracle\product\12.1.0\dbhome_1



Analyzing
file catupgrd.sql

Log
files in F:\oracle\product\12.1.0\dbhome_1\diagnostics

catcon:
ALL catcon-related output will be written to F:\oracle\product\12.1.0\db

home_1\diagnostics/catupgrd_catcon_4288.lst

catcon:
See F:\oracle\product\12.1.0\dbhome_1\diagnostics/catupgrd*.log files fo

r
output generated by scripts

catcon:
See F:\oracle\product\12.1.0\dbhome_1\diagnostics/catupgrd_*.lst files f

or
spool files, if any

Number
of Cpus = 4

SQL
Process Count = 6



------------------------------------------------------

Phases
[0-73]

Serial Phase #: 0 Files: 1 Time: 65s

Serial Phase #: 1 Files: 5 Time: 71s

Restart Phase #: 2 Files: 1 Time: 0s

Parallel
Phase #: 3 Files: 18 Time: 13s

Restart Phase #: 4 Files: 1 Time: 0s

Serial Phase #: 5 Files: 5 Time: 33s

Serial Phase #: 6 Files: 1 Time: 16s

Serial Phase #: 7 Files: 4 Time: 13s

Restart Phase #: 8 Files: 1 Time: 0s

Parallel
Phase #: 9 Files: 62 Time: 52s

Restart Phase #:10 Files: 1 Time: 0s

Serial Phase #:11 Files: 1 Time: 20s

Restart Phase #:12 Files: 1 Time: 0s

Parallel
Phase #:13 Files: 91 Time: 21s

Restart Phase #:14 Files: 1 Time: 0s

Parallel
Phase #:15 Files: 111 Time: 26s

Restart Phase #:16 Files: 1 Time: 0s

Serial Phase #:17 Files: 3 Time: 4s

Restart Phase #:18 Files: 1 Time: 0s

Parallel
Phase #:19 Files: 32 Time: 17s

Restart Phase #:20 Files: 1 Time: 0s

Serial Phase #:21 Files: 3 Time: 9s

Restart Phase #:22 Files: 1 Time: 0s

Parallel
Phase #:23 Files: 23 Time: 86s

Restart Phase #:24 Files: 1 Time: 0s

Parallel
Phase #:25 Files: 11 Time: 39s

Restart Phase #:26 Files: 1 Time: 0s

Serial Phase #:27 Files: 1 Time: 2s

Restart Phase #:28 Files: 1 Time: 0s

Serial Phase #:30 Files: 1 Time: 0s

Serial Phase #:31 Files: 257 Time: 27s

Serial Phase #:32 Files: 1 Time: 0s

Restart Phase #:33 Files: 1 Time: 1s

Serial Phase #:34 Files: 1 Time: 6s

Restart Phase #:35 Files: 1 Time: 1s

Restart Phase #:36 Files: 1 Time: 0s

Serial Phase #:37 Files: 4 Time: 75s

Restart Phase #:38 Files: 1 Time: 1s

Parallel
Phase #:39 Files: 13 Time: 131s

Restart Phase #:40 Files: 1 Time: 1s

Parallel
Phase #:41 Files: 10 Time: 4s

Restart Phase #:42 Files: 1 Time: 0s

Serial Phase #:43 Files: 1 Time: 9s

Restart Phase #:44 Files: 1 Time: 0s

Serial Phase #:45 Files: 1 Time: 9s

Serial Phase #:46 Files: 1 Time: 2s

Restart Phase #:47 Files: 1 Time: 1s

Serial Phase #:48 Files: 1 Time: 2s

Restart Phase #:49 Files: 1 Time: 1s

Serial Phase #:50 Files: 1 Time: 2s

Restart Phase #:51 Files: 1 Time: 0s

Serial Phase #:52 Files: 1 Time: 3s

Restart Phase #:53 Files: 1 Time: 0s

Serial Phase #:54 Files: 1 Time: 3s

Restart Phase #:55 Files: 1 Time: 0s

Serial Phase #:56 Files: 1 Time: 3s

Restart Phase #:57 Files: 1 Time: 0s

Serial Phase #:58 Files: 1 Time: 2s

Restart Phase #:59 Files: 1 Time: 0s

Serial Phase #:60 Files: 1 Time: 414s

Restart Phase #:61 Files: 1 Time: 0s

Serial Phase #:62 Files: 1 Time: 2150s

Restart Phase #:63 Files: 1 Time: 0s

Serial Phase #:64 Files: 1 Time: 4s

Serial Phase #:65 Files: 1 Calling sqlpatch with
F:\oracle\product\12.1.0\dbho

me_1\perl\bin\perl.exe
-I F:\oracle\product\12.1.0\dbhome_1\RDBMS\ADMIN -I F:\or

acle\product\12.1.0\dbhome_1\sqlpatch
F:\oracle\product\12.1.0\dbhome_1\sqlpatch

\sqlpatch.pl
-verbose -upgrade_mode_only > F:\oracle\product\12.1.0\dbhome_1\dia

gnostics/catupgrd_datapatch_upgrade.log
2> F:\oracle\product\12.1.0\dbhome_1\dia

gnostics/catupgrd_datapatch_upgrade.err

returned
from sqlpatch

A
subdirectory or file F:\oracle\product\12.1.0\dbhome_1\cfgtoollogs\GEOP\upgrade
already exists.

Time: 59s

Serial Phase #:66 Files: 1 Time: 76s

Serial Phase #:67 Files: 1 Time: 1s

Serial Phase #:68 Files: 1 Time: 0s

Serial Phase #:69 Files: 1 Time: 35s



Grand
Total Time: 3537s







***
WARNING: ERRORS FOUND DURING UPGRADE ***



Due
to errors found during the upgrade process, the post upgrade actions in catuppst.sql have not been automatically run.



***
THEREFORE THE DATABASE UPGRADE IS NOT YET COMPLETE ***



1. Evaluate the errors found in the upgrade
logs

and determine the proper action.

2. Execute the post upgrade script as described in Chapter 3 of the Database Upgrade Guide.





REASON:
a.catuppst.sql
unable to run in Database: GEOP Id: 0

ERRORS FOUND: during upgrade CATCTL
ERROR COUNT=2

------------------------------------------------------

Identifier
APEX 18-01-22 12:04:10 Script = F:\oracle\product\12.1.0\dbhome_1/ape

x/a

ERROR
= [ORA-39705: component 'APEX' not found in registry ORA-06512: at "SYS.DBMS_SYS_ERROR",
line 86

ORA-06512:
at "SYS.DBMS_REGISTRY", line 2237

ORA-06512:
at line 3

]

STATEMENT
= [begin

if :script_name != '?/apex/core/null1.sql'
then -- update registry progress


dbms_registry.set_progress_value('APEX','APEX_UPGRADE','APEX_040200');

end if;

end;]

------------------------------------------------------

------------------------------------------------------

Identifier
APEX 18-01-22 12:04:10 Script = F:\oracle\product\12.1.0\dbhome_1/ape

x/a

ERROR
= [ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86 ORA-06512: at
"SYS.DBMS_REG

ISTRY",
line 2237

ORA-06512:
at line 3

]

STATEMENT
= [as above]

------------------------------------------------------

------------------------------------------------------

Identifier
APEX 18-01-22 12:04:10 Script = F:\oracle\product\12.1.0\dbhome_1/ape

x/a

ERROR
= [ORA-06512: at "SYS.DBMS_REGISTRY", line 2237 ORA-06512: at line 3

]

STATEMENT
= [as above]

------------------------------------------------------

------------------------------------------------------

Identifier
APEX 18-01-22 12:04:10 Script = F:\oracle\product\12.1.0\dbhome_1/ape

x/a

ERROR
= [ORA-06512: at line 3]

STATEMENT
= [as above]

------------------------------------------------------



LOG
FILES: (catupgrd*.log)


Upgrade
Summary Report Located in:

F:\oracle\product\12.1.0\dbhome_1\cfgtoollogs\GEOP\upgrade\upg_summary.log



Grand Total Upgrade Time: [0d:0h:58m:57s]
Re: RMAN duplicate nopen from 11g to 12c fails [message #667863 is a reply to message #667862] Mon, 22 January 2018 09:52 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10690
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
Looks like certain options (APEX , TEXT etc) where used in Older version.
In newer version, ORACLE_HOME used is not installed with those options.
Using RMAN to upgrade assumes a lot. Look into other options if this is not working for you.
I would take a step back and look into these.
* Analyze what components need to upgraded (from source).
* 12C is way different. Analyze the CDB/PDB requirements. In most cases, you no need PDB options.
* How big are the schema to be upgraded? How much downtime can you afford? Again, In most cases, a simple export/import would do the job.
* If simple / direct methods does not suit you, look further.
Re: RMAN duplicate nopen from 11g to 12c fails [message #667864 is a reply to message #667863] Mon, 22 January 2018 10:22 Go to previous message
aviana
Messages: 106
Registered: July 2007
Senior Member
Thanks a lot Mahesh for those suggestions. You are right. RMAN upgrade is not so straight forward as I thought. Only benefit was that I didn't have to install 2 versions of oracle in the new host. I re-examined pre upgrade and post upgrade fixup suggestions and re executed all suggestions.Luckily now I am able to open the database and apex is also showing as newer version in the dba_registry.
Since this was 12c UAT, I had plenty of time to experiment and now happy that I tried this new RMAN NOOPEN option anyway and recorded everything I did.
Thanks a lot

[Updated on: Mon, 22 January 2018 10:24]

Report message to a moderator

Previous Topic: transportable database windows to linux
Next Topic: Restore 10.2.0.4 RAC Backup to 11.2.0.4 dbhome
Goto Forum:
  


Current Time: Mon Nov 19 23:27:17 CST 2018