| RMAN resotre/clone to new server [message #685641] |
Sun, 27 February 2022 13:40  |
patdev
Messages: 74
Registered: August 2008
|
Member |
|
|
Hello all,
I am trying to restore the RMAN backup to new server.
I have done following steps:
1- created pfile from spfile (from target) copied ($/dbs) folder with change file location for adump, and ctl files
2- took source backup with current control file ( copied to new location for restore)
3- started db with no mount on the new server
issue happens in this steps
4-- RMAN prompt i connect -- rman target /
it says (connected to target database (not started))
How should i proceed? Please guide
|
|
|
|
|
|
| Re: RMAN resotre/clone to new server [message #685643 is a reply to message #685642] |
Sun, 27 February 2022 14:23  |
patdev
Messages: 74
Registered: August 2008
|
Member |
|
|
Hi,
yes i did set ORACLE_HOME and ORACLE_SID, export ORACLE_SID
---------------
set ORACLE_SID DBNAME
echo $ORACLE_SID --> DBNAME
then rman target /
still get same message connected to target database (not started)
On the SQL side:
sqlplus / as sysdba
startup nomount
SQL> startup nomount
ORACLE instance started.
Total System Global Area 3.8655E+10 bytes
Fixed Size 3720600 bytes
Variable Size 2.0670E+10 bytes
Database Buffers 1.7851E+10 bytes
Redo Buffers 130494464 bytes
thanks
Paresh
|
|
|
|
|
|
|
|
| Re: RMAN resotre/clone to new server [message #685646 is a reply to message #685645] |
Sun, 27 February 2022 15:49 |
patdev
Messages: 74
Registered: August 2008
|
Member |
|
|
hello all,
I tried killing all the processes of DBNAME and then
tried startup nomount from RMAN i get as followed:
Oracle instance started
RMAN-00571: ===========================================================
RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS=========
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 02/27/2022 15:48:38
RMAN-06194: target database instance not started
|
|
|
|
|
|
| Re: RMAN resotre/clone to new server [message #685658 is a reply to message #685655] |
Tue, 01 March 2022 07:29 |
patdev
Messages: 74
Registered: August 2008
|
Member |
|
|
Hello,
I get bellow message in alert log when the db starts nomount:
Supported system pagesize(s):
Mon Feb 28 17:29:36 2022
PAGESIZE AVAILABLE_PAGES EXPECTED_PAGES ALLOCATED_PAGES ERROR(s)
Mon Feb 28 17:29:36 2022
4K Configured 9437190 9437190 NONE
Mon Feb 28 17:29:36 2022
Reason for not supporting certain system pagesizes:
Mon Feb 28 17:29:36 2022
2048K - Dynamic allocate and free memory regions
but there is not error/warning message when i try to restore control file.
Thanks
|
|
|
|
|
|
| Re: RMAN resotre/clone to new server [message #685660 is a reply to message #685659] |
Tue, 01 March 2022 07:57 |
patdev
Messages: 74
Registered: August 2008
|
Member |
|
|
this is the new log:
Tue Mar 01 07:48:29 2022
Starting ORACLE instance (normal) (OS id: 3552)
Tue Mar 01 07:48:29 2022
CLI notifier numLatches:13 maxDescs:853
Tue Mar 01 07:48:29 2022
**********************************************************************
Tue Mar 01 07:48:29 2022
Dump of system resources acquired for SHARED GLOBAL AREA (SGA)
Tue Mar 01 07:48:29 2022
Per process system memlock (soft) limit = 30G
Tue Mar 01 07:48:29 2022
Expected per process system memlock (soft) limit to lock
SHARED GLOBAL AREA (SGA) into memory: 36G
Tue Mar 01 07:48:29 2022
Available system pagesizes:
4K, 2048K
Tue Mar 01 07:48:29 2022
Supported system pagesize(s):
Tue Mar 01 07:48:29 2022
PAGESIZE AVAILABLE_PAGES EXPECTED_PAGES ALLOCATED_PAGES ERROR(s)
Tue Mar 01 07:48:29 2022
4K Configured 9437190 9437190 NONE
Tue Mar 01 07:48:29 2022
Reason for not supporting certain system pagesizes:
Tue Mar 01 07:48:29 2022
2048K - Dynamic allocate and free memory regions
Tue Mar 01 07:48:29 2022
RECOMMENDATION:
Tue Mar 01 07:48:29 2022
1. Increase per process memlock (soft) limit to at least 36GB
to lock 100% of SHARED GLOBAL AREA (SGA) pages into physical memory
Tue Mar 01 07:48:29 2022
**********************************************************************
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 8
Number of processor cores in the system is 8
Number of processor sockets in the system is 8
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =85
LICENSE_MAX_USERS = 0
SYS auditing is enabled
NOTE: remote asm mode is local (mode 0x1; from cluster type)
NOTE: Using default ASM root directory ASM
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options.
ORACLE_HOME = /u02/app/oracle/product/12.1.0/dbhome_1
System name: Linux
Node name: SERVERNAME
Release: 3.10.0-1160.el7.x86_64
Version: #1 SMP Tue Aug 18 14:50:17 EDT 2020
Machine: x86_64
Using parameter settings in client-side pfile $ORACLE_HOME/dbs/initDBNAME.ora on machine SERVERNAME
System parameters with non-default values:
processes = 500
memory_target = 36G
control_files = "/location1/DBNAME/control01.ctl"
control_files = "/location2/DBNAME/control02.ctl"
db_block_size = 8192
compatible = "12.1.0.2.0"
db_recovery_file_dest = "/location/DBNAME/"
db_recovery_file_dest_size= 300G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=DBNAMEXDB)"
audit_file_dest = "/location/adump/"
audit_trail = "DB"
db_name = "DBNAME"
open_cursors = 5000
_ash_size = 96M
diagnostic_dest = "/u02/app/oracle/"
NOTE: remote asm mode is local (mode 0x1; from cluster type)
Starting background process PMON
Starting background process PSP0
Tue Mar 01 07:48:29 2022
PMON started with pid=2, OS id=3557
Starting background process VKTM
Tue Mar 01 07:48:29 2022
PSP0 started with pid=3, OS id=3559
Tue Mar 01 07:48:30 2022
VKTM started with pid=4, OS id=3562 at elevated (RT) priority
Starting background process GEN0
Tue Mar 01 07:48:30 2022
VKTM running at (1)millisec precision with DBRM quantum (100)ms
Starting background process MMAN
Tue Mar 01 07:48:30 2022
GEN0 started with pid=5, OS id=3566
Tue Mar 01 07:48:30 2022
MMAN started with pid=6, OS id=3568
Starting background process DIAG
Starting background process DBRM
Tue Mar 01 07:48:30 2022
DIAG started with pid=8, OS id=3572
Starting background process VKRM
Tue Mar 01 07:48:30 2022
DBRM started with pid=9, OS id=3574
Tue Mar 01 07:48:30 2022
VKRM started with pid=10, OS id=3576
Starting background process DIA0
Tue Mar 01 07:48:30 2022
DIA0 started with pid=11, OS id=3578
Starting background process DBW0
Tue Mar 01 07:48:30 2022
DBW0 started with pid=12, OS id=3580
Starting background process LGWR
Starting background process CKPT
Tue Mar 01 07:48:30 2022
LGWR started with pid=13, OS id=3582
Tue Mar 01 07:48:30 2022
CKPT started with pid=14, OS id=3584
Starting background process SMON
Tue Mar 01 07:48:30 2022
SMON started with pid=16, OS id=3588
Starting background process RECO
Starting background process LREG
Tue Mar 01 07:48:30 2022
RECO started with pid=18, OS id=3592
Starting background process PXMN
Tue Mar 01 07:48:30 2022
LREG started with pid=19, OS id=3594
Tue Mar 01 07:48:30 2022
PXMN started with pid=20, OS id=3596
Starting background process MMON
Starting background process MMNL
Tue Mar 01 07:48:30 2022
MMON started with pid=21, OS id=3598
Tue Mar 01 07:48:30 2022
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Mar 01 07:48:30 2022
MMNL started with pid=22, OS id=3600
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /u02/app/oracle
Tue Mar 01 07:48:33 2022
Using default pga_aggregate_limit of 29696 MB
|
|
|
|
|
|
| Re: RMAN resotre/clone to new server [message #685662 is a reply to message #685661] |
Tue, 01 March 2022 08:50 |
patdev
Messages: 74
Registered: August 2008
|
Member |
|
|
Hello thanks
Oracle instance started
Total System Global Area 38654705664 bytes
Fixed Size 3720600 bytes
Variable Size 20669532776 bytes
Database Buffers 17850957824 bytes
Redo Buffers 130494464 bytes
RMAN> restore controlfile from 'backuplocation/dbnamecontrol22822.bcp';
Starting restore at 01-MAR-22
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
ORA-03114: not connected to ORACLE
RMAN-03002: failure of restore command at 03/01/2022 07:49:23
ORA-03114: not connected to ORACLE
[server ~]$
|
|
|
|
| Re: RMAN resotre/clone to new server [message #685672 is a reply to message #685662] |
Wed, 02 March 2022 11:45 |
John Watson
Messages: 8962
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
I think you are getting the 601 error when RMAN tries to launch the channel. That is not good. The only obvious thing wrong is that this Quote:'backuplocation/dbnamecontrol22822.bcp' is not a valid path, but that would not cause a 601. You could try re-creating the spfile you are using. You could relink the Oracle Home.
I can't think of anything else, other than raise a TAR. The soul destroying process of engaging with Oracle Support.....
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
