Home » RDBMS Server » Backup & Recovery » RMAN restore - only DB backup ( no SF\CF\archivelog backup ) (Oracle 19c. Windows server 2019 )
| RMAN restore - only DB backup ( no SF\CF\archivelog backup ) [message #687865] |
Thu, 06 July 2023 07:01  |
Andrey_R
Messages: 441
Registered: January 2012
Location: Israel
|
Senior Member |
|
|
Hi DBAs,
I'm trying to test a scenario when I want to restore a table MYUSER.T1 from a previous date.
I have no archive log backups, no SPFILE/CTL file backups.
I only have a backup of the database from a time I want to restore the table to.
I do have a SPFILE/Control file of the database from some later point in time.
My database is called MYDB, in ARCHIVELOG mode
SQL> select name,log_mode from v$database;
NAME LOG_MODE
--------- ------------
MYDB ARCHIVELOG
SQ
RMAN> backup database format 'G:\BACKUP\BACKUP_MYDB\MYDB_BKP.RMAN';
Starting backup at 06-JUL-23
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=266 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=E:\ORACLE\ORADATA\MYDB\SYSTEM01.DBF
input datafile file number=00003 name=E:\ORACLE\ORADATA\MYDB\SYSAUX01.DBF
input datafile file number=00004 name=E:\ORACLE\ORADATA\MYDB\UNDOTBS01.DBF
input datafile file number=00007 name=E:\ORACLE\ORADATA\MYDB\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 06-JUL-23
channel ORA_DISK_1: finished piece 1 at 06-JUL-23
piece handle=G:\BACKUP\BACKUP_MYDB\MYDB_BKP.RMAN tag=TAG20230706T114528 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
Finished backup at 06-JUL-23
SQL> select * from myuser.t1;
COL1
----------
1
SQL> select to_char ( sysdate,'dd.mm.yyyy hh24:mi:ss') as date1 from dual;
DATE1
-------------------
06.07.2023 11:47:00
I minute or so after, I am dropping my table:
SQL> select to_char ( sysdate,'dd.mm.yyyy hh24:mi:ss') as date1 from dual;
DATE1
-------------------
06.07.2023 11:48:42
SQL> drop table myuser.t1 purge;
Table dropped.
RMAN> RUN {
2> RECOVER TABLE "MYUSER"."T1"
3> UNTIL TIME "TO_DATE('06.07.2023 11:47:00', 'DD-MM-YYYY HH24:MI:SS')"
4> AUXILIARY DESTINATION 'G:\MYAUX'
5> REMAP TABLE 'MYUSER'.'T1':'T1_RECOVERED';
6> };
Starting recover at 06-JUL-23
current log archived
using channel ORA_DISK_1
RMAN-05026: warning: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1
Creating automatic instance, with SID='Buww'
initialization parameters used for automatic instance:
db_name=MYDB
db_unique_name=Buww_pitr_MYDB
compatible=19.0.0
db_block_size=8192
db_files=200
diagnostic_dest=D:\ORACLE
_system_trig_enabled=FALSE
sga_target=2000M
processes=200
db_create_file_dest=G:\MYAUX
log_archive_dest_1='location=G:\MYAUX'
#No auxiliary parameter file used
starting up automatic instance MYDB
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/06/2023 11:54:59
RMAN-04006: error from auxiliary database: ORA-28056: Writing audit records to Windows Event Log failed
ORA-28056: Writing audit records to Windows Event Log failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "advise, allocate, alter, analyze, associate statistics, audit, backup, begin, @, call, catalog, change, comment, commit, configure, connect, convert, copy, create, create catalog, create global, create or replace global, create or replace script, create script, crosscheck, declare, delete, delete from, describe, describe catalog, disassociate statistics, drop, drop catalog, drop database, duplicate, exit, explain plan, flashback, flashback table, grant, grant catalog, grant register, host, import, insert, list, lock, merge, mount, noaudit, open, print, purge, quit, recover, register, release"
RMAN-01007: at line 0 column 2 file: standard input
RMAN>
What am I hitting here ?
How can I restore the table from the backup per point in time ( or just the state it was in the backup piece )
Regards,
Andrey
|
|
|
|
|
|
| Re: RMAN restore - only DB backup ( no SF\CF\archivelog backup ) [message #687867 is a reply to message #687865] |
Thu, 06 July 2023 07:54  |
John Watson
Messages: 8931
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
You may be hitting a problem with the Windows service under which the instance will run. Did it get created successfully?
It's a long time since I tried this on Windows, but I vaguely remember having to pre-create the service and then specify the instance_name in an auxiliary parameter file. Or something like that. It may well be different in the current release.
|
|
|
|
| Re: RMAN restore - only DB backup ( no SF\CF\archivelog backup ) [message #687868 is a reply to message #687866] |
Thu, 06 July 2023 07:57 |
Andrey_R
Messages: 441
Registered: January 2012
Location: Israel
|
Senior Member |
|
|
Mahesh Rajendran wrote on Thu, 06 July 2023 15:27>> ORA-28056: Writing audit records to Windows Event Log failed
I would first address this.
Edit:
check the logfile size/clear events. The exact path to navigate might have changed.
Control Panel --> Administrative Tools --> Event Viewer --> Clear All Events
Thanks for the reply.
I tried to follow the recommendation and went into the event viewer, and cleared all Application\Security\Setup\System\Forwarded Events log data.
Then tried again - got the exact same result
RMAN> RECOVER TABLE "MYUSER"."T1"
2> UNTIL TIME "TO_DATE('06.07.2023 11:47:00', 'DD-MM-YYYY HH24:MI:SS')"
3> AUXILIARY DESTINATION 'G:\MYAUX'
4> REMAP TABLE 'MYUSER'.'T1':'T1_RECOVERED';
Starting recover at 06-JUL-23
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=268 device type=DISK
RMAN-05026: warning: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1
Creating automatic instance, with SID='fpdv'
initialization parameters used for automatic instance:
db_name=MYDB
db_unique_name=fpdv_pitr_MYDB
compatible=19.0.0
db_block_size=8192
db_files=200
diagnostic_dest=D:\ORACLE
_system_trig_enabled=FALSE
sga_target=2000M
processes=200
db_create_file_dest=G:\MYAUX
log_archive_dest_1='location=G:\MYAUX'
#No auxiliary parameter file used
starting up automatic instance MYDB
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/06/2023 12:53:43
RMAN-04006: error from auxiliary database: ORA-28056: Writing audit records to Windows Event Log failed
ORA-28056: Writing audit records to Windows Event Log failed
RMAN> };
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "}": expecting one of: "advise, allocate, alter, analyze, associate statistics, audit, backup, begin, @, call, catalog, change, comment, commit, configure, connect, convert, copy, create, create catalog, create global, create or replace global, create or replace script, create script, crosscheck, declare, delete, delete from, describe, describe catalog, disassociate statistics, drop, drop catalog, drop database, duplicate, exit, explain plan, flashback, flashback table, grant, grant catalog, grant register, host, import, insert, list, lock, merge, mount, noaudit, open, print, purge, quit, recover, register, release"
RMAN-01007: at line 1 column 1 file: standard input
Audit trail: LENGTH: '509' ACTION :[211] 'begin sys.dbms_backup_restore.createRmanOutputRow( l0row_id => :l0row_id, l0row_stamp => :l0row_stamp, row_id => :row_id, row_stamp => :row_stamp, txt => :txt, sameline => :i_sameline); end;' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[26] 'ORCL-PRIMARY\Administrator' CLIENT TERMINAL:[12] 'ORCL-PRIMARY' STATUS:[1] '0' DBID:[10] '3056464049' SESSIONID:[10] '4294967295' USERHOST:[22] 'WORKGROUP\ORCL-PRIMARY' CLIENT ADDRESS:[0] '' ACTION NUMBER:[2] '47' . Audit trail: LENGTH: '373' ACTION :[77] 'select decode(open_mode, 'READ WRITE', 1, 0) into :read_write from v$database' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[26] 'ORCL-PRIMARY\Administrator' CLIENT TERMINAL:[12] 'ORCL-PRIMARY' STATUS:[1] '0' DBID:[10] '3056464049' SESSIONID:[10] '4294967295' USERHOST:[22] 'WORKGROUP\ORCL-PRIMARY' CLIENT ADDRESS:[0] '' ACTION NUMBER:[1] '3' .
However, not to sure what to make of it.
Any further ideas ? What else can I check to understand what's wrong.. I did uninstall and re-install oracle just in case..
Regards,
Andrey
|
|
|
|
| Re: RMAN restore - only DB backup ( no SF\CF\archivelog backup ) [message #687869 is a reply to message #687867] |
Thu, 06 July 2023 09:41 |
Andrey_R
Messages: 441
Registered: January 2012
Location: Israel
|
Senior Member |
|
|
John Watson wrote on Thu, 06 July 2023 15:54You may be hitting a problem with the Windows service under which the instance will run. Did it get created successfully?
It's a long time since I tried this on Windows, but I vaguely remember having to pre-create the service and then specify the instance_name in an auxiliary parameter file. Or something like that. It may well be different in the current release.
Thanks John.
I tried to do something similar, but wasn't sure it made sense, and also was hitting some errors, possibly doing other stuff wrong..
So trying now with some more awareness this time :
C:\Users\Administrator>oradim -new -sid MYDB2
Instance created.
SQL> create pfile from spfile;
File created.
But when I tried to set the following as PFILE for MYDB2 ( creating it to 'D:\oracle\product\19.0.0\dbhome_1\database\INITMYDB2.ORA' ) I could not start the instance in nomount:
DB_NAME=MYDB2
CONTROL_FILES=(E:\ORACLE\ORADATA\MYDB2\CONTROL01.CTL,
E:\ORACLE\ORADATA\MYDB2\CONTROL02.CTL)
DB_FILE_NAME_CONVERT=(E:\ORACLE\ORADATA\MYDB\,E:\ORACLE\ORADATA\MYDB2\)
LOG_FILE_NAME_CONVERT=(E:\ORACLE\ORADATA\MYDB,E:\ORACLE\ORADATA\MYDB2)
C:\Users\Administrator>SET ORACLE_SID=MYDB2
C:\Users\Administrator>sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Thu Jul 6 14:06:45 2023
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup nomount pfile='G:\BACKUP\BACKUP_MYDB\INITMYDB2.ORA';
LRM-00116: syntax error at 'LOG_FILE_NAME_CO' following 'E:\ORACLE\ORADAT'
ORA-01078: failure in processing system parameters
So I just created PFILE from spfile in MYDB and copied over and modified to INITMYDB2.ORA as:
( also created the folders that had MYDB as MYDB2 accordingly )
mydb2.__data_transfer_cache_size=0
mydb2.__db_cache_size=1509949440
mydb2.__inmemory_ext_roarea=0
mydb2.__inmemory_ext_rwarea=0
mydb2.__java_pool_size=0
mydb2.__large_pool_size=16777216
mydb2.__oracle_base='D:\oracle'#ORACLE_BASE set from environment
mydb2.__pga_aggregate_target=1107296256
mydb2.__sga_target=2097152000
mydb2.__shared_io_pool_size=100663296
mydb2.__shared_pool_size=452984832
mydb2.__streams_pool_size=0
mydb2.__unified_pga_pool_size=0
*.audit_file_dest='D:\oracle\admin\mydb2\adump'
*.audit_trail='db'
*.compatible='19.0.0'
*.control_files='E:\oracle\oradata\MYDB2\control01.ctl','E:\oracle\oradata\MYDB2\control02.ctl'
*.db_block_size=8192
*.db_name='mydb2'
*.diagnostic_dest='D:\oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=mydb2XDB)'
*.local_listener='LISTENER_MYDB'
*.nls_language='AMERICAN'
*.nls_territory='AMERICA'
*.open_cursors=300
*.pga_aggregate_limit=2096M
*.pga_aggregate_target=1048M
*.processes=300
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_max_size=2000M
*.sga_target=2000M
*.undo_tablespace='UNDOTBS1'
C:\Users\Administrator>sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Thu Jul 6 14:12:55 2023
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 2097150616 bytes
Fixed Size 9030296 bytes
Variable Size 469762048 bytes
Database Buffers 1610612736 bytes
Redo Buffers 7745536 bytes
SQL>
SQL> show parameter db_name
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_name string mydb2
SQL>
C:\Users\Administrator>lsnrctl
LSNRCTL for 64-bit Windows: Version 19.0.0.0.0 - Production on 06-JUL-2023 14:18:05
Copyright (c) 1991, 2019, Oracle. All rights reserved.
Welcome to LSNRCTL, type "help" for information.
LSNRCTL> stat
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=***.**.**.***)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for 64-bit Windows: Version 19.0.0.0.0 - Production
Start Date 06-JUL-2023 10:22:25
Uptime 0 days 3 hr. 55 min. 42 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File D:\oracle\product\19.0.0\dbhome_1\network\admin\listener.ora
Listener Log File D:\oracle\diag\tnslsnr\ORCL-PRIMARY\listener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=***.**.**.***)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=ORCL-PRIMARY)(PORT=5500))(Security=(my_wallet_directory=D:\ORACLE\admin\mydb\xdb_wallet))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "mydb" has 1 instance(s).
Instance "mydb", status READY, has 1 handler(s) for this service...
Service "mydb2" has 1 instance(s).
Instance "mydb2", status BLOCKED, has 1 handler(s) for this service...
Service "mydbXDB" has 1 instance(s).
Instance "mydb", status READY, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL>
that I can allow SYS connections to tnsnames entry that has (UR=A) to it next to the service name indicator, so I could connect to mydb2
( this is basically a preparation to connect to it as an auxiliary later in my restore test):
C:\Users\Administrator>sqlplus sys/123@mydb2 as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Thu Jul 6 14:35:37 2023
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
SQL> show parameter db_na
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_name string mydb2
SQL>
C:\Users\Administrator>rman target sys/123@mydb auxiliary sys/123@mydb2
Recovery Manager: Release 19.0.0.0.0 - Production on Thu Jul 6 14:37:33 2023
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
connected to target database: MYDB (DBID=3056464049)
connected to auxiliary database: MYDB2 (not mounted)
RMAN> RUN {
2> RESTORE TABLE "MYUSER"."T1";
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "table": expecting one of: "allforeign, application, archivelog, asdecrypted, asencrypted, backupset, channel, check, controlfile, database, database root, datafile, device, dump, farsync, file_name_convert, force, foreign, from, frompreplugin, from service, high, pluggable, preview, primary, section, skip preplugin, skip readonly, spfile, standby, tablespace, to restore point, until restore point, until, using, validate, ("
RMAN-01007: at line 2 column 9 file: standard input
RMAN> RECOVER TABLE "MYUSER"."T1"
2> UNTIL TIME "TO_DATE('06.07.2023 11:47:00', 'DD-MM-YYYY HH24:MI:SS')"
3> AUXILIARY DESTINATION 'G:\MYAUX'
4> REMAP TABLE 'MYUSER'.'T1':'T1_RECOVERED';
Starting recover at 06-JUL-23
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/06/2023 14:37:38
RMAN-05053: AUXILIARY DESTINATION is only valid when using a RMAN-managed auxiliary instance
RMAN> };
Regards,
Andrey
|
|
|
|
| Re: RMAN restore - only DB backup ( no SF\CF\archivelog backup ) [message #687870 is a reply to message #687869] |
Thu, 06 July 2023 11:25 |
John Watson
Messages: 8931
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
The pfile file should be %ORACLE_HOME%\rdbms\admin\params_auxinst.ora and if the instance_name you specify in it matches the service you have created and started then (perhaps) it will work. RMAN will start the instance and connect to it, you shouldn't be doing that. I would think that instance_name is the only parameter you need so that it can find the service, but that's guessing.
|
|
|
|
| Re: RMAN restore - only DB backup ( no SF\CF\archivelog backup ) [message #687872 is a reply to message #687870] |
Fri, 07 July 2023 05:28 |
Andrey_R
Messages: 441
Registered: January 2012
Location: Israel
|
Senior Member |
|
|
John Watson wrote on Thu, 06 July 2023 19:25The pfile file should be %ORACLE_HOME%\rdbms\admin\params_auxinst.ora and if the instance_name you specify in it matches the service you have created and started then (perhaps) it will work. RMAN will start the instance and connect to it, you shouldn't be doing that. I would think that instance_name is the only parameter you need so that it can find the service, but that's guessing.
I'll try that and post the results.
So far, I've tried to restore it manually into a new instance MYDB2..
What I did in this attempt was
- Create a new instance MYDB2 with oradim
- Set it with a new copy-PFILE with new db_name MYDB2
- Startup nomount
- Create controlfile using ammended to MYDB2 trace controlfile script
* The control file creation and restore part required playing around with data files and log files,
as in order to create the controlfile - they had to exist,
but in order to restore the database they had to be absent..
- Catalog and Restore from the backup piece into MYDB2
- Got the error ORA-00279 and ORA-00280
- After I could not open the database anyway I tried, I used the "ALTER SYSTEM SET “_allow_resetlogs_corruption”= TRUE SCOPE = SPFILE;" Option to open it
- Database MYDB2 opened ! And I was surprised to see that my table MYUSER.T1 was missing from it! 8o ..
I wonder whether it's the corruption in the files I "allowed" or something in my technique that caused this..
But I did expect that I could at least restore the data in the table to some extent, the way it was initially created at least :?
[Updated on: Fri, 07 July 2023 06:20] Report message to a moderator |
|
|
|
| Re: RMAN restore - only DB backup ( no SF\CF\archivelog backup ) [message #687875 is a reply to message #687872] |
Sat, 08 July 2023 02:18 |
John Watson
Messages: 8931
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
I think I understand part of what you saw: why when you run a CREATE CONTROLFILE, the datafiles and online logs have to exist. The issue is that the CREATE CONTROLFILE command does not let you specify the DBID (I have often wondered abut this, it could be included in the generated trace) so it needs to look at the files in order to extract it and put it in the new controlfile.
Did you run any sort of RECOVER command? If so, what was it?
|
|
|
|
| Re: RMAN restore - only DB backup ( no SF\CF\archivelog backup ) [message #687889 is a reply to message #687875] |
Wed, 12 July 2023 10:29 |
Andrey_R
Messages: 441
Registered: January 2012
Location: Israel
|
Senior Member |
|
|
John Watson wrote on Sat, 08 July 2023 10:18I think I understand part of what you saw: why when you run a CREATE CONTROLFILE, the datafiles and online logs have to exist. The issue is that the CREATE CONTROLFILE command does not let you specify the DBID (I have often wondered abut this, it could be included in the generated trace) so it needs to look at the files in order to extract it and put it in the new controlfile.
Did you run any sort of RECOVER command? If so, what was it?
I had to. Because Oracle won't open with resetlogs, it says that data file No. 1 needs recovery..
So I try in another test
( with SQL*Plus ) to do "recover database using backup controlfile;"
And then get the "ORA-00279"
Or I tried to restore with rman "Restore Database" and just "Recover database" and got
RMAN-08187: warning: media recovery until SCN 2462425437 complete
Finished recover at
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of sql statement command at 07/12/2023 17:35:08
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '**:\....MYDB3\SYSTEM01.DBF'
RMAN> quit
SQL> alter system set undo_management=manual scope=spfile;
System altered.
SQL> ALTER SYSTEM SET "_allow_resetlogs_corruption"= TRUE SCOPE = SPFILE;
System altered.
SQL> shutdown immediate;
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> startup force;
ORACLE instance started.
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-00603: ORACLE server session terminated by fatal error
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-00704: bootstrap process failure
ORA-00604: error occurred at recursive SQL level 1
ORA-01555: snapshot too old: rollback segment number 6 with name
"_SYSSMU6_2576551637$" too small
Process ID: 16448
Session ID: 906 Serial number: 2811
If I try t open with resetlogs I get
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
The main difference between what I did then and now is ( except for a different backup and database ) is that I set undo_management=manual
[Updated on: Wed, 12 July 2023 10:30] Report message to a moderator |
|
|
|
Goto Forum:
Current Time: Sat Apr 27 12:10:40 CDT 2024
|
] 
Blog
Search
Help
Members
Register
Login
Home
