ORA-1113 signalled during: alter database open...

Hello,
Today when I was unable to logon to my Oracle 9i database on Windows machine, I referred to the Alter.log file.
This file showed me the above error.
And when I try to logon to database with normal user, I get the error as "Database initialization or shutdown is in progress"
When I tried to log on using the DBA privileges, I can see that my Database is MOUNTED.
What should I do next? Do I bring the database down forcefully using the "Shutdown abort" command? and then at the startup when some datafile is shown as required to recovery then, recover the datafile using following command:
RECOVER AUTOMATIC DATAFILE 'file_Path';
Please guide
Thanks in advance
Himanshu

ORA-01113 file string needs media recovery
Cause: An attempt was made to open a datafile that is in need of media recovery.
Action: First apply media recovery to the datafile identified in the message, then retry the operation.
media recovery for datafile is required
log as sys user.
shutdown the database
startup mount
recover datafile <filename>
alter database open

Similar Messages

ORA-1092 signalled during: alter database open...

When trying to startup the db runnint into following error:
SMON: enabling cache recovery
Sat May 16 10:35:12 2009
Successfully onlined Undo Tablespace 1.
Sat May 16 10:35:12 2009
SMON: enabling tx recovery
Sat May 16 10:35:12 2009
Database Characterset is UTF8
Sat May 16 10:35:13 2009
Errors in file d:\oracle\visdb\9.2.0\admin\vis_apps\udump\vis_ora_2200.trc:
ORA-00600: internal error code, arguments: [4193], [2391], [2395], [], [], [], [], []
Doing block recovery for fno: 10 blk: 159
Sat May 16 10:35:17 2009
Recovery of Online Redo Log: Thread 1 Group 2 Seq 3 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\VISDATA\LOG2.DBF
Doing block recovery for fno: 10 blk: 153
Sat May 16 10:35:18 2009
Recovery of Online Redo Log: Thread 1 Group 2 Seq 3 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\VISDATA\LOG2.DBF
Sat May 16 10:35:18 2009
Errors in file d:\oracle\visdb\9.2.0\admin\vis_apps\udump\vis_ora_2200.trc:
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4193], [2391], [2395], [], [], [], [], []
Error 607 happened during db open, shutting down database
USER: terminating instance due to error 607
Sat May 16 10:35:19 2009
Errors in file d:\oracle\visdb\9.2.0\admin\vis_apps\bdump\vis_pmon_2288.trc:
ORA-00607: Internal error occurred while making a change to a data block
Instance terminated by USER, pid = 2200
ORA-1092 signalled during: alter database open...
Pl. advice to recover from this suitation. New to recovery/bkup.
Thanks,
Sashi.

00607, 00000, "Internal error occurred while making a change to a data block"
// *Cause: An internal error or memory exception occurred while Oracle was
// applying redo to a data block.
// *Action: call Oracle Support

ORA1589 signalled during alter database open...

Hello
Im running database Oracle9i Enterprise Edition Release 9.0.1.1.1 on windows XP
Im getting this error when i open. the database is in no archive mode. Please see the following extract from the alert log extract
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
Sat Feb 05 10:08:06 2011
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Sat Feb 05 10:08:29 2011
alter database mount exclusive
Sat Feb 05 10:08:53 2011
Successful mount of redo thread 1, with mount id 2728236189.
Sat Feb 05 10:08:53 2011
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Sat Feb 05 10:08:54 2011
alter database open
Sat Feb 05 10:09:08 2011
ORA-1589 signalled during: alter database open...
Thanks for your kind help
Edited by: user1115482 on Feb 5, 2011 1:03 AM

Go through your alert.log for the last few messages relating to Log Sequence#1572. It may well still be an Online Redo Log.
However, you started this thread without explaining what actions had been performed before the startup attempt that returned ORA-1589. That wasn't very professional of you.
A doctor doesn't go ask other doctors for assistance with "my patient's heart is failing, what do I do" without saying "I had attempted open heart surgery and, during the course of surgery, found that his heart beat was irregular, however, I had already cut open his chest ... now what do I do ?"
We do not know if
a. You had restored a control file
b. You had attempted a RESTORE and/or RECOVER database
c. There had been an instance failure / server crash / corruption / error relating to a control file
d. Some error had occurred before the STARTUP attempt that you posted
e. Any other messages were posted to the alert.log
Hemant K Chitale
Edited by: Hemant K Chitale on Feb 5, 2011 10:31 PM

ORA-301 Signalled during: ALTER DATABASE ...

Hi,
I tried to add 4 standby redologs to our standby setup, and first file went well.
theothers already got error ORA-301:
ALTER DATABASE ADD STANDBY LOGFILE GROUP 8 '/export/home/oracle/logs/redo8.log' SIZE 2G
Fri May 31 15:31:22 2013
Completed: ALTER DATABASE ADD STANDBY LOGFILE GROUP 8 '/export/home/oracle/logs/redo8.log' SIZE 2G
ALTER DATABASE ADD STANDBY LOGFILE GROUP 9 '/export/home/oracle/logs/redo9.log' SIZE 2G
ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 9 '/export/home/oracle/logs/redo9.log' SIZE 2G...
ALTER DATABASE ADD STANDBY LOGFILE GROUP 10 '/export/home/oracle/logs/redo10.log' SIZE 2G
ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 10 '/export/home/oracle/logs/redo10.log' SIZE 2G...
ALTER DATABASE ADD STANDBY LOGFILE GROUP 11 '/export/home/oracle/logs/redo11.log' SIZE 2G
ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 11 '/export/home/oracle/logs/redo11.log' SIZE 2G...
Fri May 31 16:33:39 2013
I tried to track any info in the web and metalink, but it's the first time I encounter an ORA error with no documentation... :(
Some facts:
The oracle is 11.2.0 on Linux
There is no space issue on disk
Thanks for any help/ideas...

thanks for the reply.
first one I stated in the original post. there is tons of storage :)
for the others 2 -
user has priviledge... he created the first file succesfully...
those files do not exist on the disk already.
Thanks

ORA-279 signalled during: ALTER DATABASE RECOVER automatic standby databas

Hi,
oracle server:8.1.7.0.0
os:solaris 5.9
we created standby server by taking coldbackup of primary server and we are using rsync to syschronize the archive log files between production and standby servers but every over we recover the standby server by executing
sql>recover automatic standby database:
but in alert log file i am getting the following error :
but when i googled for ora-279 error some people says it is default behaviour and can it be ignored and why it is asking next logfile.
Media Recovery Log /oratranslog/arch_1_1701118.arc
Wed Mar 26 21:35:34 2008
Media Recovery Log /oratranslog/arch_1_1701119.arc
Wed Mar 26 21:35:54 2008
Media Recovery Log /oratranslog/arch_1_1701120.arc
ORA-279 signalled during: ALTER DATABASE RECOVER automatic standby database...
Wed Mar 26 21:36:24 2008
ALTER DATABASE RECOVER CANCEL
Wed Mar 26 21:36:24 2008
Media Recovery Cancelled
Completed: ALTER DATABASE RECOVER CANCEL
Thanks and Regards
Prakash
juniour oracle dba

damorgan,
He is running 8.1.7.0. "DataGuard" scripts were initially available for 9i and then
backported (and available as a seperate download) for 8i. Many 8i implementations
did not and do not use DataGuard.
Even if it is "Jurassic" {which it certainly is NOT}, they obviously do have a good
reason for setting up a standby -- they DO have data of value. So, maybe they have
not upgraded to 9i or 10g. There could be a dozen reasons
1. Server HW/OS doesn't support 9i/10g, not budgetting for Server upgrade
2. Application using Forms 2.x or 4.5 and not tested on 9i / 10g (4.5 not certified
on 9i)
3. Low end client PCs working perfectly with Character-mode forms, not powerful
enought to run Jinitiator and Forms 6i / 9i
Just because someone hasn't upgraded to 10g doesn't mean that they are at fault
when you do NOT know the reason why they have not upgraded.
Surely, they do know that 8i is desupported. Don't you think that their management
has undertaken due diligence / cost-benefit analysis in considering whether they
should upgrade to 10g ?
Maybe they have another project implementing 10g in parallel and will be able
to shutdown this environment soon. Maybe they don't need to do so.
Do understand that people are intelligent enough to make their own decisions
considering their particular circumstances and don't go shooting off with your
assumption that anyone not running 10g is a dinosaur.

ORA-1109 signalled during: alter database close

Hi
i have found the following error in alert log after i shut down my database for cold backup
alter database close
ORA-1109 signalled during: alter database close...
Please advice is there any threat because of this error and whats the reason for the occurence of this error.
Version of DB: 10.2.0.4.0
I have DR configured for this db also..
Regards,
Arun Kumar

Thats not the command i am using..
I just use shutdown immediate.. when i use that command i get the sequnce of steps logged in alert log..
there i find the error.. see below..(a part of alert log content)
Shutting down instance: further logons disabled
Sun Aug 9 19:12:39 2009
Stopping background process CJQ0
Sun Aug 9 19:12:39 2009
Stopping background process MMNL
Sun Aug 9 19:12:40 2009
Stopping background process MMON
Sun Aug 9 19:12:41 2009
Shutting down instance (immediate)
License high water mark = 5
Sun Aug 9 19:12:41 2009
Stopping Job queue slave processes, flags = 7
Sun Aug 9 19:12:41 2009
Job queue slave processes stopped
Sun Aug 9 19:12:41 2009
alter database close
ORA-1109 signalled during: alter database close...*
Sun Aug 9 19:12:41 2009
alter database dismount
Completed: alter database dismount
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes

ORA-1624 signalled during: ALTER DATABASE CLEAR....

Hi,
I get this error in my alert file what it means?
ORA-1624 signalled during: ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 1...
Thanks
Edited by: vittel on Sep 3, 2008 1:28 PM
Edited by: vittel on Sep 3, 2008 1:29 PM

Hi,
First thanks for your quick response.
The only thing that we have running in the database is a scheduled program how run every 3 min to switch the current log and he applied the archive log to the standby database!!!
It can be a session how is trying to do this "Alter database clear unarchived logfile...." ?
Thanks

ORA-604 signalled during: ALTER TABLESPACE...

Oracle 10.2.0.4 EE, Server 2003...
Today I wanted to add new datafile…
First I restart the instance and then used EM to add datafile… After 5 minutes process failed and in AlertSID.ora I get this message:
===========================================================
Mon Feb 08 10:23:04 2010
ALTER TABLESPACE "R1" ADD DATAFILE 'D:\Datafile\R03.DBF' SIZE 15000M AUTOEXTEND ON NEXT 512M MAXSIZE 32767M
Mon Feb 08 10:28:08 2010
ORA-604 signalled during: ALTER TABLESPACE "R1" ADD DATAFILE 'D:\Datafile\R03.DBF' SIZE 15000M AUTOEXTEND ON NEXT 512M MA…
===========================================================
Then I create datafile with command prompt and everything was fine, new datafile was added.
Any Ideas why does this happen?
Thanks!

Error message was only:
Mon Feb 08 10:28:08 2010
ORA-604 signalled during: ALTER TABLESPACE "R1" ADD DATAFILE 'D:\Datafile\R03.DBF' SIZE 15000M AUTOEXTEND ON NEXT 512M MAXSIZE 32767M
As I said, I used EM and after 5 minutes EM connection failed. Then I re-connect and EM don’t show me any errors, everything was fine but new datafile was not added. Only I get error message in AlertSID.ora…

Oracle hands for 12 min during "alter database open"

Dear all,
After a disk failure/replacement in a SAN disk array that we are using for storage, we had to restore our Oracle database. After the restore the database does not start properly: It takes around 12 min to move from the state "Mount" to the state "Open". It finally opens but even after this, when I start SAP, only 5 workprocesses connect and logging into SAP is not possible, the gui just hangs
There are no errors in the alert_RSP.log. I attach an extract here to show the time difference between the mount state and the open state
Thu Apr 19 11:16:07 2007
Starting ORACLE instance (normal)
Thu Apr 19 11:16:29 2007
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 3
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.7.0.
System parameters with non-default values:
processes                = 240
sessions                 = 288
timed_statistics         = TRUE
event                    = 38068 trace name context forever, level 100
shared_pool_size         = 620756992
sga_max_size             = 1159695232
shared_pool_reserved_size= 20401094
java_pool_size           = 167772160
enqueue_resources        = 8000
filesystemio_options     = SETALL
control_files            = /oracle/RSP/sapdata1/cntrl/cntrlRSP.dbf, /oracle/RSP/origlogA/cntrl/cntrlRSP.dbf, /oracle/RSP/sa
parch/cntrl/cntrlRSP.dbf
db_block_checksum        = FALSE
db_block_size            = 8192
compatible               = 9.2.0
log_archive_start        = TRUE
log_archive_dest         = /oracle/RSP/saparch/RSParch
log_buffer               = 1048576
log_checkpoint_interval = 0
log_checkpoint_timeout   = 0
db_files                 = 254
db_file_multiblock_read_count= 8
log_checkpoints_to_alert = TRUE
control_file_record_keep_time= 30
dml_locks                = 5000
replication_dependency_tracking= FALSE
transaction_auditing     = FALSE
undo_management          = AUTO
undo_tablespace          = PSAPUNDO
undo_suppress_errors     = TRUE
undo_retention           = 43200
remote_os_authent        = TRUE
db_domain                = WORLD
session_cached_cursors   = 800
hash_join_enabled        = FALSE
background_dump_dest     = /oracle/RSP/saptrace/background
user_dump_dest           = /oracle/RSP/saptrace/usertrace
max_dump_file_size       = 20000
core_dump_dest           = /oracle/RSP/saptrace/background
optimizer_features_enable= 9.2.0
sort_area_size           = 2097152
sort_area_retained_size = 0
db_name                  = RSP
open_cursors             = 800
optimizer_mode           = choose
sortelimination_cost_ratio= 10
btree_bitmap_plans     = FALSE
pushjoin_predicate     = FALSE
optimizerjoin_sel_sanity_check= TRUE
optimizer_index_cost_adj = 10
optimpeek_user_binds   = FALSE
optimizeror_expansion = DEPTH
PMON started with pid=2
DBW0 started with pid=3
DBW1 started with pid=4
DBW2 started with pid=5
DBW3 started with pid=6
LGWR started with pid=7
CKPT started with pid=8
SMON started with pid=9
RECO started with pid=10
Thu Apr 19 11:16:31 2007
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=11
ARC0: Archival started
ARC1 started with pid=12
ARC1: Archival started
Thu Apr 19 11:16:31 2007
ARCH: STARTING ARCH PROCESSES COMPLETE
Thu Apr 19 11:16:31 2007
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no FAL' ARCHARC0: Thread not mounted
Thu Apr 19 11:16:31 2007
ARC1: Becoming the heartbeat ARCH
ARC1: Becoming the heartbeat ARCHARC1: Thread not mounted
Thu Apr 19 11:16:31 2007
ALTER DATABASE   MOUNT
Thu Apr 19 11:16:36 2007
Successful mount of redo thread 1, with mount id 1209727119
Thu Apr 19 11:16:36 2007
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE   MOUNT
Thu Apr 19 11:16:36 2007
ALTER DATABASE OPEN
Thu Apr 19 11:16:37 2007
LGWR: Primary database is in CLUSTER CONSISTENT mode
Thread 1 opened at log sequence 6727
Current log# 12 seq# 6727 mem# 0: /oracle/RSP/origlogB/log_g12m1.dbf
Current log# 12 seq# 6727 mem# 1: /oracle/RSP/mirrlogB/log_g12m2.dbf
Successful open of redo thread 1
Thu Apr 19 11:16:37 2007
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Apr 19 11:16:38 2007
SMON: enabling cache recovery
Thu Apr 19 11:16:49 2007
Successfully onlined Undo Tablespace 27.
Thu Apr 19 11:16:49 2007
SMON: enabling tx recovery
Thu Apr 19 11:16:50 2007
Database Characterset is WE8DEC
Thu Apr 19 11:29:09 2007
Completed: ALTER DATABASE OPEN
Please note the time difference between 11:16:50 and 11:29:09, when the database is mounted and we are just waiting for it to open
I run dbverify, all ok
I reviewed note 521264 and my issue is described in case 2c. However, after reviewing all 127 datafiles and online redologs, I do not have any files with an "S" in their permissions
We run Solaris 10, Oracle 9.2.0.7 and WAS 6.40 SP16
Any help will be very much appreciated
Many thanks
Andreas

Hello,
Here are the details:
R3trans -d returns 0000 instantly. I am not including trans.log here as the connection to the database works . I have no space issues neither, have around 70GB left under /oracle
The startup log is as follows
Trace of system startup/check of SAP System RSP on Fri Apr 20 08:38:10 BST 2007
Called command: /usr/sap/RSP/SYS/exe/run/startsap
Starting SAP Instance DVEBMGS00
SAP-R/3-Startup Program Rel 640 V1.8 (2003/04/24)
Starting at 2007/04/20 08:38:10
Startup Profile: "/usr/sap/RSP/SYS/profile/START_DVEBMGS00_rspda002"
Execute Pre-Startup Commands
(6285) Local: /usr/sap/RSP/SYS/exe/run/sapmscsa -n pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
/usr/sap/RSP/SYS/exe/run/sapmscsa: SCSA is attached and useable.
/usr/sap/RSP/SYS/exe/run/sapmscsa: finished.
(6285) Local: rm -f ms.sapRSP_DVEBMGS00
(6285) Local: ln -s -f /usr/sap/RSP/SYS/exe/run/msg_server ms.sapRSP_DVEBMGS00
(6285) Local: rm -f dw.sapRSP_DVEBMGS00
(6285) Local: ln -s -f /usr/sap/RSP/SYS/exe/run/disp+work dw.sapRSP_DVEBMGS00
(6285) Local: rm -f co.sapRSP_DVEBMGS00
(6285) Local: ln -s -f /usr/sap/RSP/SYS/exe/run/rslgcoll co.sapRSP_DVEBMGS00
(6285) Local: rm -f se.sapRSP_DVEBMGS00
(6285) Local: ln -s -f /usr/sap/RSP/SYS/exe/run/rslgsend se.sapRSP_DVEBMGS00
Starting Programs
(6304) Starting: local ms.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
(6305) Starting: local dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
(6306) Starting: local co.sapRSP_DVEBMGS00 -F pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
(6307) Starting: local se.sapRSP_DVEBMGS00 -F pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
(6285) Waiting for Child Processes to terminate.
Instance on host rspda002 started
ps -ef | grep dw is shown below: It only starts 5 -6 dialog processes. All the other processes are not started (normally I have around 40 )
rspda002:rspadm 33% ps -ef | grep dw
rspadm 6317 6305   0 08:38:17 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6310 6305   0 08:38:16 ?           0:01 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6311 6305   0 08:38:16 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6624 5523   0 08:43:35 pts/1       0:00 grep dw
rspadm 6305 6285   0 08:38:11 ?           0:04 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6312 6305   0 08:38:17 ?           0:01 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6313 6305   0 08:38:17 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
That is ps -ef | grep sap
rspda002:rspadm 32% ps -ef | grep sap
rspadm 6317 6305   0 08:38:17 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6310 6305   0 08:38:16 ?           0:01 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
    root 12375   650   0 11:15:58 ?           3:56 /usr/sap/RSP/SYS/exe/run/saposcol
rspadm 6311 6305   0 08:38:16 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6309 6305   0 08:38:16 ?           0:01 icman -attach pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6306 6285   0 08:38:11 ?           0:00 co.sapRSP_DVEBMGS00 -F pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6307 6285   0 08:38:11 ?           0:00 se.sapRSP_DVEBMGS00 -F pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6304 6285   0 08:38:11 ?           0:00 ms.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6308 6305   0 08:38:16 ?           0:02 gwrd -dp pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6622 5523   0 08:43:29 pts/1       0:00 grep sap
rspadm 6305 6285   0 08:38:11 ?           0:04 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 20243   650   0 15:11:34 ?          13:11 sapccm4x -DCCMS pf==/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6285   650   0 08:38:11 ?           0:00 /usr/sap/RSP/SYS/exe/run/sapstart pf=/usr/sap/RSP/SYS/profile/START_DVEBMGS00_r
rspadm 6312 6305   0 08:38:17 ?           0:01 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
rspadm 6313 6305   0 08:38:17 ?           0:00 dw.sapRSP_DVEBMGS00 pf=/usr/sap/RSP/SYS/profile/RSP_DVEBMGS00_rspda002
Many thanks
Andreas

Standby database errors - Alter database open read only

alter database open read only
AUDIT_TRAIL initialization parameter is changed to OS, as DB is NOT compatible for database opened with read-only access
Signalling error 1152 for datafile 1!
Beginning standby crash recovery.
Serial Media Recovery started
Managed Standby Recovery starting Real Time Apply
Media Recovery Waiting for thread 1 sequence 216
Mon Dec 20 11:58:18 2010
Standby crash recovery need archive log for thread 1 sequence 216 to continue.
Please verify that primary database is transporting redo logs to the standby database.
Wait timeout: thread 1 sequence 216
Standby crash recovery aborted due to error 16016.
Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
ORA-16016: archived log for thread 1 sequence# 216 unavailable
Recovery interrupted!
Completed standby crash recovery.
Signalling error 1152 for datafile 1!
Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
ORA-10458 signalled during: alter database open read only...
Mon Dec 20 12:13:46 2010
ALTER DATABASE RECOVER managed standby database using current logfile disconnect
Attempt to start background Managed Standby Recovery process (MDM2)
Mon Dec 20 12:13:46 2010
MRP0 started with pid=23, OS id=18974
MRP0: Background Managed Standby Recovery process started (MDM2)
started logmerger process
Mon Dec 20 12:13:51 2010
Managed Standby Recovery starting Real Time Apply
Parallel Media Recovery started with 2 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 216
Completed: ALTER DATABASE RECOVER managed standby database using current logfile disconnect
The above lines are from alert log of standby database.
Standby standbase
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
Parameters set on primary are
log_archive_dest_1 LOCATION=+MDMDG3/MDM1/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLE ) DB_UNIQUE_NAME=MDM1
log_archive_dest_state_1 ENABLE
log_archive_dest_2 SERVICE=MDM2 SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM2
log_archive_dest_state_2 ENABLE
dg_broker_config_file1 +MDMDG2/mdm/dg_config/dgconfig1_mdm.dat
dg_broker_config_file2 +MDMDG2/mdm/dg_config/dgconfig2_mdm.dat
fal_server MDM2
standby_file_management AUTO
log_archive_config dg_config=(MDM1,MDM2)
db_file_name_convert MDM2, MDM1
ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE availability ;
Standby pfile
*.archive_lag_target=900
*.audit_file_dest='/u01/app/oracle/admin/MDM2/adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl','+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl'
*.db_block_size=8192
*.db_create_file_dest='+MDMDG1'
*.db_domain=''
*.db_file_name_convert='MDM1','MDM2'
*.db_name='MDM'
*.db_recovery_file_dest='+MDMDG2'
*.db_recovery_file_dest_size=10485760000
*.db_unique_name='MDM2'
*.dg_broker_config_file1='+MDMDG2/MDM/DG_CONFIG/dgconfig1_MDM.dat'
*.dg_broker_config_file2='+MDMDG2/MDM/DG_CONFIG/dgconfig2_MDM.dat'
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=MDM2XDB)'
*.fal_server='MDM11','MDM12'
*.instance_name='MDM2'
*.log_archive_config='dg_config=(MDM1,MDM2)'
*.log_archive_dest_1='LOCATION=+MDMDG3/MDM2/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=MDM2'
*.log_archive_dest_2='SERVICE=MDM1 ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM1'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='MDM_%t_%s_%r.arc'
*.log_file_name_convert='MDM1','MDM2'
*.memory_target=838860800
*.nls_language='ENGLISH'
*.nls_territory='UNITED KINGDOM'
*.open_cursors=300
*.processes=500
*.remote_login_passwordfile='exclusive'
*.sessions=555
*.standby_file_management='AUTO'
*.undo_tablespace='UNDOTBS1'
On standby ASM
ASMCMD [+] > find * *
+MDMDG1/ASM/
+MDMDG1/ASM/ASMPARAMETERFILE/
+MDMDG1/ASM/ASMPARAMETERFILE/REGISTRY.253.737811541
+MDMDG1/MDM/
+MDMDG1/MDM2/
+MDMDG1/MDM2/CONTROLFILE/
+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl
+MDMDG1/MDM2/CONTROLFILE/current.265.738243333
+MDMDG1/MDM2/DATAFILE/
+MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_DATA.264.738243343
+MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_IDX.277.738243343
+MDMDG1/MDM2/DATAFILE/MDM_SRC_DATA.282.738243343
+MDMDG1/MDM2/DATAFILE/MDM_SRC_IDX.275.738243343
+MDMDG1/MDM2/DATAFILE/MIPS_MDM_DATA.283.738243341
+MDMDG1/MDM2/DATAFILE/MIPS_MDM_IDX.276.738243343
+MDMDG1/MDM2/DATAFILE/SYSAUX.281.738243341
+MDMDG1/MDM2/DATAFILE/SYSTEM.280.738243341
+MDMDG1/MDM2/DATAFILE/TEST_TBSP1.273.738243345
+MDMDG1/MDM2/DATAFILE/TEST_TBSP2.272.738243345
+MDMDG1/MDM2/DATAFILE/UNDOTBS1.256.738243343
+MDMDG1/MDM2/DATAFILE/UNDOTBS2.279.738243343
+MDMDG1/MDM2/DATAFILE/USERS.278.738243347
+MDMDG1/MDM2/ONLINELOG/
+MDMDG1/MDM2/ONLINELOG/group_1.259.738243429
+MDMDG1/MDM2/ONLINELOG/group_2.257.738243431
+MDMDG1/MDM2/ONLINELOG/group_21.284.738243505
+MDMDG1/MDM2/ONLINELOG/group_22.261.738243505
+MDMDG1/MDM2/ONLINELOG/group_23.274.738243505
+MDMDG1/MDM2/ONLINELOG/group_3.258.738243431
+MDMDG1/MDM2/ONLINELOG/group_31.262.738243513
+MDMDG1/MDM2/ONLINELOG/group_32.270.738243513
+MDMDG1/MDM2/ONLINELOG/group_33.263.738243513
+MDMDG1/MDM2/ONLINELOG/group_4.260.738243431
+MDMDG2/MDM/
+MDMDG2/MDM/DG_CONFIG/
+MDMDG2/MDM2/
+MDMDG2/MDM2/AUTOBACKUP/
+MDMDG2/MDM2/AUTOBACKUP/2010_12_20/
+MDMDG2/MDM2/AUTOBACKUP/2010_12_20/s_738242861.263.738244155
+MDMDG2/MDM2/CONTROLFILE/
+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl
+MDMDG2/MDM2/CONTROLFILE/current.271.738243335
+MDMDG2/MDM2/ONLINELOG/
+MDMDG2/MDM2/ONLINELOG/group_1.270.738243429
+MDMDG2/MDM2/ONLINELOG/group_2.269.738243431
+MDMDG2/MDM2/ONLINELOG/group_21.268.738243505
+MDMDG2/MDM2/ONLINELOG/group_22.272.738243505
+MDMDG2/MDM2/ONLINELOG/group_23.262.738243505
+MDMDG2/MDM2/ONLINELOG/group_3.273.738243431
+MDMDG2/MDM2/ONLINELOG/group_31.266.738243513
+MDMDG2/MDM2/ONLINELOG/group_32.265.738243513
+MDMDG2/MDM2/ONLINELOG/group_33.264.738243513
+MDMDG2/MDM2/ONLINELOG/group_4.261.738243431
+MDMDG3/MDM/
+MDMDG3/MDM/ARCH/
+MDMDG3/MDM2/
+MDMDG3/MDM2/ARCH/
-- Please can I know how to open read only standby database.

user5846399 wrote:
ORA-16016: archived log for thread 1 sequence# 216 unavailable
Recovery interrupted!archived log for thread 1 sequence# 216
This file is needed for recovery, Find it and move it to the standby database side.

Alter database open

Hi,
I try to start a database with the commands
startup mount
alter database noarchivelog
everything is ok up to now
When I give the command
alter database open
I obtain
ERROR at line 1
ORA-01092 Oracle instance terminated Disconnection forced.
Why?
Thank you,
Mihaela

I post the last 120 lines of alert_log:
Mon Jul 24 12:57:31 2006
alter database noarchivelog
Mon Jul 24 12:57:31 2006
Completed: alter database noarchivelog
Mon Jul 24 12:57:44 2006
alter database open
Mon Jul 24 12:57:47 2006
Thread 1 opened at log sequence 1281
Current log# 3 seq# 1281 mem# 0: /web/oradata/simmer/redo03_A.log
Current log# 3 seq# 1281 mem# 1: /web/oradata/simmer/redo03_B.log
Successful open of redo thread 1
Mon Jul 24 12:57:47 2006
SMON: enabling cache recovery
Mon Jul 24 12:57:50 2006
Successfully onlined Undo Tablespace 1.
Mon Jul 24 12:57:50 2006
SMON: enabling tx recovery
Mon Jul 24 12:57:50 2006
Errors in file /web/bin/oracle/9206/admin/simmer/udump/simmer_ora_1636.trc:
ORA-12701: CREATE DATABASE character set is not known
Mon Jul 24 12:57:50 2006
Error 12701 happened during db open, shutting down database
USER: terminating instance due to error 12701
Instance terminated by USER, pid = 1636
ORA-1092 signalled during: alter database open
Tue Jul 25 09:52:36 2006
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 3
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.6.0.
System parameters with non-default values:
processes = 300
timed_statistics = TRUE
shared_pool_size = 117440512
large_pool_size = 16777216
java_pool_size = 117440512
control_files = /web/oradata/simmer/control01.ctl, /web/arhive/ctl/control02.ctl, /web/bin/oracle/9206/ctl/control03.ctl
db_block_size = 8192
db_cache_size = 33554432
compatible = 9.2.0.0.0
db_file_multiblock_read_count= 16
fast_start_mttr_target = 300
undo_management = AUTO
undo_tablespace = UNDOTBS1
undo_retention = 10800
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = SIMMER
job_queue_processes = 10
hash_join_enabled = TRUE
background_dump_dest = /web/bin/oracle/9206/admin/simmer/bdump
user_dump_dest = /web/bin/oracle/9206/admin/simmer/udump
core_dump_dest = /web/bin/oracle/9206/admin/simmer/cdump
sort_area_size = 1048576
db_name = SIMMER
open_cursors = 300
optimizer_mode = rule
star_transformation_enabled= FALSE
query_rewrite_enabled = FALSE
pga_aggregate_target = 25165824
aq_tm_processes = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
CJQ0 started with pid=8
QMN0 started with pid=9
Tue Jul 25 09:52:44 2006
ALTER DATABASE MOUNT
Tue Jul 25 09:52:49 2006
Successful mount of redo thread 1, with mount id 535276268
Tue Jul 25 09:52:49 2006
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Tue Jul 25 09:52:50 2006
ALTER DATABASE OPEN
Tue Jul 25 09:52:51 2006
Beginning crash recovery of 1 threads
Tue Jul 25 09:52:52 2006
Started redo scan
Tue Jul 25 09:52:53 2006
Completed redo scan
21 redo blocks read, 5 data blocks need recovery
Tue Jul 25 09:52:53 2006
Started recovery at
Thread 1: logseq 1281, block 1240, scn 0.28883578
Tue Jul 25 09:52:53 2006
Recovery of Online Redo Log: Thread 1 Group 3 Seq 1281 Reading mem 0
Mem# 0 errs 0: /web/oradata/simmer/redo03_A.log
Mem# 1 errs 0: /web/oradata/simmer/redo03_B.log
Tue Jul 25 09:52:53 2006
Completed redo application
Tue Jul 25 09:52:53 2006
Ended recovery at
Thread 1: logseq 1281, block 1261, scn 0.28903619
5 data blocks read, 5 data blocks written, 21 redo blocks read
Crash recovery completed successfully
Tue Jul 25 09:52:54 2006
Thread 1 advanced to log sequence 1282
Thread 1 opened at log sequence 1282
Current log# 1 seq# 1282 mem# 0: /web/oradata/simmer/redo01_A.log
Current log# 1 seq# 1282 mem# 1: /web/oradata/simmer/redo01_B.log
Successful open of redo thread 1
Tue Jul 25 09:52:56 2006
SMON: enabling cache recovery
Tue Jul 25 09:52:59 2006
Successfully onlined Undo Tablespace 1.
Tue Jul 25 09:52:59 2006
SMON: enabling tx recovery
Tue Jul 25 09:52:59 2006
Database Characterset is US7ASCII
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: ALTER DATABASE OPEN
openes.hq.fdeb.ro>
Thank you,
Mihaela

ORA-279 signalled during recovery of standby database

Hi All,
I am preparing standby database after taking hot backup and copying those datafiles to standby,
taken controlfile standby controlfile backup from primary
mounted the standby database using standby controlfile using
startup nomount pfile='/u01/stand.ora'
alter database mount standby database;
Now I have started applying archives on standby database after copying all archives from primary to standby box the archives generated during backup using..
recover standby database;
But I am getting the below warning on the recovery screen...
ORA-00279: change 51667629050 generated at 07/02/2009 00:59:43 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55118_652209172.arc
ORA-00280: change 51667629050 for thread 1 is in sequence #55118
ORA-00278: log file '/nodal-archive/archive/1_55117_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667703096 generated at 07/02/2009 01:06:04 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55119_652209172.arc
ORA-00280: change 51667703096 for thread 1 is in sequence #55119
ORA-00278: log file '/nodal-archive/archive/1_55118_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667767649 generated at 07/02/2009 01:12:28 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55120_652209172.arc
ORA-00280: change 51667767649 for thread 1 is in sequence #55120
ORA-00278: log file '/nodal-archive/archive/1_55119_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc
ORA-00280: change 51667831821 for thread 1 is in sequence #55121
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer
needed for this recovery
and I am getting the below warning on the alert log..........
Sun Jul 5 18:37:36 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:37:36 2009
Media Recovery Log /nodal-archive/archive/1_55256_652209172.arc
Sun Jul 5 18:40:31 2009
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Sun Jul 5 18:40:31 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:40:31 2009
Media Recovery Log /nodal-archive/archive/1_55257_652209172.arc
Please suggest what to do now.............
Thanks in Advance,
Sukanta Paul.

Hi Sukanta,
I didn't really understand what the problem is...
Let me explain, hope it will be clear.
You created a standby control file, and backed up the database (it doesn't matter in which order). Now, you have a standby database that is ready to apply logs. It will be able to apply log forever, until we will stop it.
The messages you see say the following:
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for thread 1 {color:blue} - this says that the recovery process is now at scn 51667831821 {color}
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc {color:blue} - the information needed for the recover is in this file (this is only the default name, you can choose other name if the file is called differently) {color}
ORA-00280: change 51667831821 for thread 1 is in sequence #55121 {color:blue} - same here, the needed archive is sequence 55121 {color}
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer needed for this recovery {color:blue} - this message is after Oracle has applied the log, and it means that this log is no longer needed {color}
Now it will wait for the next log. Again, this process is endless, this is how it is made to allow the standby database to be always synched with the primary.
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

Alter Database Open Mystery

We have a script that issued the Startup command this morning. In the .trc logs we are able to see that the Startup command got as far as the Alter Database Mount command. So we know this command completed successfully. But the next command we expect to see is the Alter Database Open command. This was mysteriously absent from the .trc file.
We lack a full time DBA on our project so we are wondering if there is a logical explanation for this failure? Are there any places we can look to see why the Alter Database Open command was never issued and didn't appear in the .trc log?
Any suggestions or probably causes would be greatly appreciated.

DB version 9.2.0.6.0 on Solaris 8
Just noticed that our /UNDO file system is a 99% and that our UNDO tablespace is using 'auto extend' option. Could this be a potential cause?
/dev/vx/dsk/rootdg/undo
11796416 10490922 125853 99% /undo
The alert log just stopped and didn't show anything regarding the Alter Database Open command. Then it jumps to this morning when one of our guys started the database manually. You can see this where May 3rd entries stop:
ALTER DATABASE MOUNT
Thu May 3 23:18:24 2007
Successful mount of redo thread 1, with mount id 1534972155
Thu May 3 23:18:24 2007
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Fri May 4 07:10:07 2007
Starting ORACLE instance (normal)
Fri May 4 07:12:57 2007
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 3
Fri May 4 07:12:57 2007
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Fri May 4 07:12:57 2007
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Fri May 4 07:13:07 2007
Starting ORACLE instance (normal)
Disable cache advisory with old cache parameters
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 3
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.6.0.
System parameters with non-default values:
processes = 200
timed_statistics = TRUE
shared_pool_size = 150994944
java_pool_size = 50331648
nls_date_format = DD-MON-RR
control_files = /oracle_data/oradata1/FC/control01.ctl, /oracle_dat
a/oradata2/FC/control02.ctl, /oracle_data/oradata3/FC/control03.ctl
db_block_buffers = 22000
db_block_size = 2048
db_writer_processes = 2
dbhandles_cached = 0
compatible = 9.0.0.0.0
log_buffer = 524288
log_checkpoint_interval = 10000
db_files = 38
db_file_multiblock_read_count= 32
dml_locks = 1500
undo_management = AUTO
undo_tablespace = undotbs_01
max_enabled_roles = 100
remote_login_passwordfile= EXCLUSIVE
db_domain = .WORLD
service_names = FC
utl_file_dir = /apps/oracle9i/admin/FC/script
job_queue_processes = 1
systemtrig_enabled = TRUE
background_dump_dest = /apps/oracle9i/admin/FC/bdump
user_dump_dest = /apps/oracle9i/admin/FC/udump
max_dump_file_size = 10240
core_dump_dest = /apps/oracle9i/admin/FC/cdump
audit_trail = DB
sort_area_size = 1500000
db_name = FC
open_cursors = 200
optimizer_mode = choose
PMON started with pid=2
DBW0 started with pid=3
DBW1 started with pid=4
LGWR started with pid=5
CKPT started with pid=6
SMON started with pid=7
RECO started with pid=8
CJQ0 started with pid=9
Fri May 4 07:13:09 2007
ALTER DATABASE MOUNT
Fri May 4 07:13:14 2007
Successful mount of redo thread 1, with mount id 1534971461
Fri May 4 07:13:14 2007
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Fri May 4 07:13:14 2007
ALTER DATABASE OPEN
Fri May 4 07:13:15 2007
Thread 1 opened at log sequence 272984
Current log# 4 seq# 272984 mem# 0: /rollback_logs/FC/redo04.log
Successful open of redo thread 1
Fri May 4 07:13:15 2007
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri May 4 07:13:15 2007
SMON: enabling cache recovery
Fri May 4 07:13:17 2007
Successfully onlined Undo Tablespace 17.
Fri May 4 07:13:17 2007
SMON: enabling tx recovery
Fri May 4 07:13:17 2007
Database Characterset is US7ASCII
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
Completed: ALTER DATABASE OPEN
Fri May 4 07:15:05 2007
Thread 1 advanced to log sequence 272985
Current log# 5 seq# 272985 mem# 0: /rollback_logs/FC/redoFC05.log
Fri May 4 07:15:28 2007
Thread 1 advanced to log sequence 272986
Current log# 6 seq# 272986 mem# 0: /rollback_logs/FC/redoFC06.log
Fri May 4 07:15:53 2007
Thread 1 advanced to log sequence 272987
Current log# 7 seq# 272987 mem# 0: /rollback_logs/FC/redoFC07.log
Fri May 4 07:16:18 2007
Thread 1 advanced to log sequence 272988
Current log# 8 seq# 272988 mem# 0: /rollback_logs/FC/redoFC08.log
Fri May 4 07:20:20 2007
Thread 1 advanced to log sequence 272989
Current log# 9 seq# 272989 mem# 0: /rollback_logs/FC/redoFC09.log
Fri May 4 07:20:45 2007
Thread 1 advanced to log sequence 272990
Current log# 10 seq# 272990 mem# 0: /rollback_logs/FC/redoFC10.log
Fri May 4 07:21:09 2007
Thread 1 advanced to log sequence 272991
Current log# 11 seq# 272991 mem# 0: /rollback_logs/FC/redoFC11.log
Fri May 4 07:25:21 2007
Thread 1 advanced to log sequence 272992
Current log# 2 seq# 272992 mem# 0: /rollback_logs/FC/redo02.log
Fri May 4 07:25:45 2007
more

ORA-16196 on Alter Database open.

Hi
Why when we close a database with ALTER DATABASE CLOSE
it's impossible to open immediately after with ALTER DATABASE OPEN?
How to do this without dismount the database ?
Regards
Den

Seems illogical but thats the way it has been defined by Oracle.
The instance can mount/dismount a database any number of times but it can open or close the database only once.
The only reason I can think of is this is the way it is required in RAC. Any instance can open a database but it can do it only once. May be in order to preserve the integrity of the database structures.

Alter database open resetlogs upgrade ;         throwing error

Recently i have cloned a database from 11.2.0.2 to 11.2.0.3 on a new server.... I got the error as fowwos,
contents of Memory Script:
Alter clone database open resetlogs;
executing Memory Script
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
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 07/12/2012 16:19:24
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Process ID: 29247
Session ID: 200 Serial number: 5
So i have tried
SQL> alter database open resetlogs upgrade;
alter database open resetlogs upgrade
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> alter database open upgrade;
alter database open upgrade
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '+DATA_CMX/cmx/datafile/system.270.788451975'
Any help ?

Hi,
Duplicate is not supported using different version of database, so I recommend you don't use duplicate.
Because RMAN "duplicate" attempts to automatically rename (rename required recover) and open the database you may not use RMAN duplicate for this case, only RMAN restore.
Perform this work using normal restore database.
See this example.
On prod database with db_name/db_unique_name dbupg:
Recovery Manager: Release 11.2.0.2.0 - Production on Fri Jul 13 15:15:59 2012
RMAN> backup database plus archivelog delete input;
Starting backup at 13-JUL-12
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=52 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=17 RECID=1 STAMP=788540852
input archived log thread=1 sequence=18 RECID=2 STAMP=788541371
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_annnn_TAG20120713T151612_800shf7w_.bkp tag=TAG20120713T151612 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_17_800rz40y_.arc RECID=1 STAMP=788540852
archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_18_800shcsd_.arc RECID=2 STAMP=788541371
Finished backup at 13-JUL-12
Starting backup at 13-JUL-12
using channel ORA_DISK_1
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=+DS8000_DG/dbupg/datafile/system.271.788537119
input datafile file number=00002 name=+DS8000_DG/dbupg/datafile/sysaux.272.788537167
input datafile file number=00003 name=+DS8000_DG/dbupg/datafile/undotbs1.273.788537199
input datafile file number=00004 name=+DS8000_DG/dbupg/datafile/users.275.788537229
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp tag=TAG20120713T151614 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncsnf_TAG20120713T151614_800sjm29_.bkp tag=TAG20120713T151614 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 13-JUL-12
Starting backup at 13-JUL-12
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=19 RECID=3 STAMP=788541412
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_annnn_TAG20120713T151652_800sjnf7_.bkp tag=TAG20120713T151652 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_19_800sjn5q_.arc RECID=3 STAMP=788541412
Finished backup at 13-JUL-12
RMAN> backup current controlfile;
Starting backup at 13-JUL-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncnnf_TAG20120713T153435_800tkwl2_.bkp tag=TAG20120713T153435 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 13-JUL-12I used same server to do this work... I really dont recommend that, if yes you must be aware about location of restore... you should use new server:
Create a spfile:
*.control_files='+DS8000_DG/dbclone/controlfile/Current.277.788541913'
*.db_name='dbupg'
*.db_unique_name='dbclone'
*.audit_file_dest='/u01/app/oracle/admin/dbclone/adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.db_block_size=8192
*.db_create_file_dest='+MMC'
*.db_domain=''
*.db_recovery_file_dest_size=107374182400
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area01'
*.diagnostic_dest='/u01/app/oracle'
*.log_file_name_convert='+DS8000_DG','+MMC'
*.memory_target=1031798784
*.open_cursors=300Make backup available on new server:
and:
SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 15:33:24 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 1027182592 bytes
Fixed Size                  2227936 bytes
Variable Size             599785760 bytes
Database Buffers          419430400 bytes
Redo Buffers                5738496 bytes
SQL> show parameter db_n
NAME                                 TYPE        VALUE
db_name                              string      dbupg
SQL> show parameter db_un
NAME                                 TYPE        VALUE
db_unique_name                       string      dbclone
RMAN> restore controlfile from '/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncnnf_TAG20120713T153435_800tkwl2_.bkp';
Starting restore at 13-JUL-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=290 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
output file name=+DS8000_DG/dbclone/controlfile/current.277.788541913
Finished restore at 13-JUL-12
RMAN> startup mount
database is already started
database mounted
released channel: ORA_DISK_1
RMAN> run {
2> SET NEWNAME FOR DATABASE TO '+MMC';
3> restore database ;
4> }
executing command: SET NEWNAME
Starting restore at 13-JUL-12
Starting implicit crosscheck backup at 13-JUL-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=290 device type=DISK
Crosschecked 4 objects
Finished implicit crosscheck backup at 13-JUL-12
Starting implicit crosscheck copy at 13-JUL-12
using channel ORA_DISK_1
Crosschecked 2 objects
Finished implicit crosscheck copy at 13-JUL-12
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to +MMC
channel ORA_DISK_1: restoring datafile 00002 to +MMC
channel ORA_DISK_1: restoring datafile 00003 to +MMC
channel ORA_DISK_1: restoring datafile 00004 to +MMC
channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp
channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp tag=TAG20120713T151614
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
Finished restore at 13-JUL-12
RMAN> recover database;
Starting recover at 13-JUL-12
using channel ORA_DISK_1
starting media recovery
media recovery complete, elapsed time: 00:00:01
Finished recover at 13-JUL-12So, just startup with upgrade option.
SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 15:39:31 2012
SQL> alter database open resetlogs upgrade; Now you can upgrade your database.
After upgrade database you can change the database name using NID:
$ nid
DBNEWID: Release 11.2.0.3.0 - Production on Fri Jul 13 15:50:23 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Keyword     Description                    (Default)
TARGET      Username/Password              (NONE)
DBNAME      New database name              (NONE)
LOGFILE     Output Log                     (NONE)
REVERT      Revert failed change           NO
SETNAME     Set a new database name only   NO
APPEND      Append to output log           NO
HELP        Displays these messages        NOHTH,
Levi Pereira
Edited by: Levi Pereira on Jul 13, 2012 4:04 PM

ORA-1113 signalled during: alter database open...

Similar Messages

Maybe you are looking for