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

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

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-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-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

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-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…

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]

What is the use of 'ALTER DATABASE CLOSE'?

Hello Everybody,
SQL*Plus: Release 10.1.0.2.0 - Production on Ma Aug 15 21:28:30 2005
Copyright © 1982, 2004, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> conn / as sysdba
Connected.
SQL> startup force
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145750508 bytes
Database Buffers 25165824 bytes
Redo Buffers 262144 bytes
Database mounted.
Database opened.
SQL> select status from v$instance;
STATUS
OPEN
SQL> alter database close;
Database altered.
SQL> select status from v$instance;
STATUS
MOUNTED
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-16196: database has been previously opened and closed
If i have to shutdown the instance and database then
WHAT IS THE USE OF 'ALTER DATABASE CLOSE' ?
I need explanation. Why should i shutdown?
Dont give me this answer.
ORA-16196: database has been previously opened and closed
Cause: The instance has already opened and closed the database, which is allowed only once in its lifetime.
Action: Shut down the instance.

If you read the documentation you will see that there is no ALTER DATABASE CLOSE command.
This is an undocumented Oracle command, which we are not supposed to use. Consequently we are not allowed to complain about the way that it works. Instead we're supposed to use SHUTDOWN IMMEDIATE.
Cheers, APC

Reg : alter database close

Hi,
How to bring the database to open,
After issuing alter database close;
SQL> alter database close;
Database altered.
SQL> select status from v$instance;
STATUS
MOUNTED
SQL> startup open;
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-16196: database has been previously opened and closed
It is not opening the database.
Help me out pls.
With Regards
V.S.Anand

Searching metalink knowledge base for the error code gives :-
Error:     ORA-16196 (ORA-16196)
Text:     database has been previously opened and closed
Cause:     The instance has already opened and closed the database, which is
     allowed only once in its lifetime.
Action:     Shut down the instance.
You will have to shut the database down then open it.
regards,
graham

ORA-604 signalled during: create tablespace

Hello,
While creating the my_idx_tablespace tablespace. I am getting ORA-604 error.
=====================================================================
Wed Mar 10 18:16:32 2010
create tablespace my_idx_tablespace
datafile 'E:\Oracle\Database\my_idx.dbf' size 1024m reuse
blocksize 8192
extent management local
segment space management auto
online
Wed Mar 10 18:18:13 2010
ORA-604 signalled during: create tablespace my_idx_tablespace
datafile 'E:\Oracle\Database\my_idx.dbf' size 1024m reuse
blocksize 8192
extent management local
segment space management auto
online...
Wed Mar 10 18:21:31 2010
drop tablespace log1_tablespace including contents and datafiles
ORA-959 signalled during: drop tablespace log1_tablespace including contents and datafile
=====================================================================
Any suggestion ?
OS: Windows 2003 32 bit machine.
Oracle: Oracle 10g enterprise edition 10.2.0.3
Thanks
With Regards
Hemant.

Hi,
Thanks for your response.
I will upload the log ASAP.
Can you please let me know some pointer for this error.
Thanks
With Regards
Hemant.

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

ORA-1543 signalled during: create tablespace TSP222_TBL

Can someone please tell me what this error means... What things should I check? Oracle 10g

http://www.oracle.com/pls/db102/print_hit_summary?search_string=ORA-01543

Ora 00364,ora 00305 ora 00312 errors in standby database

hii friends i got a problem in my standby database yesterday i performed database restoration activity, restoration is done and database is in MRM modemout stage, archive gap sequence is completed and is in synchronize with primary but suddenly after some time i got in alertlog media recovery waiting for thread one and from there its is showing nothing in alert log after stoping mrm and restarting database i got few errors please check them and suggest me some solution
alert log file
RFS[87]: Assigned to RFS process 7912
RFS[87]: Identified database type as 'physical standby'
Tue Jan 4 17:12:14 2011
RFS[87]: Archived Log: '/backup/standby_archivelogs/1_87532_622555682.dbf'
Tue Jan 4 17:12:17 2011
Media Recovery Log /backup/standby_archivelogs/1_87532_622555682.dbf
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:55:35 2011
alter database recover managed standby database cancel
Tue Jan 4 17:55:38 2011
MRP0: Background Media Recovery cancelled with status 16037
Tue Jan 4 17:55:38 2011
Errors in file /oracle/app/oracle/admin/****/bdump/*******mrp03017.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Tue Jan 4 17:55:39 2011
Waiting for MRP0 pid 3017 to terminate
Tue Jan 4 17:55:39 2011
Errors in file /oracle/app/oracle/admin/****/bdump/****mrp03017.trc:
ORA-16037: user requested cancel of managed recovery operation
Tue Jan 4 17:55:39 2011
MRP0: Background Media Recovery process shutdown (****)
Tue Jan 4 17:55:40 2011
Managed Standby Recovery Canceled (****)
Completed: alter database recover managed standby database cancel
Tue Jan 4 17:55:56 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:55:56 2011
Attempt to start background Managed Standby Recovery process (****)
MRP0 started with pid=16, OS id=9300
Tue Jan 4 17:55:56 2011
MRP0: Background Managed Standby Recovery process started (****)
Managed Standby Recovery not using Real Time Apply
Tue Jan 4 17:56:01 2011
Errors in file /oracle/app/oracle/admin/****/bdump/****mrp09300.trc:
ORA-00367: checksum error in log file header
ORA-00305: log 2 of thread 1 inconsistent; belongs to another database
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 /dev/vg04/rREDOR21
Clearing online log 2 of thread 1 sequence number 87533
Tue Jan 4 17:56:01 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09300.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 complete
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:56:02 2011
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:57:56 2011
alter database recover managed standby database cancel
Tue Jan 4 17:57:56 2011
MRP0: Background Media Recovery cancelled with status 16037
Tue Jan 4 17:57:56 2011
Errors in file /oracle/app/oracle/admin/APMBDRDB/bdump/apmbdrdb_mrp0_9300.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Tue Jan 4 17:57:57 2011
Waiting for MRP0 pid 9300 to terminate
Tue Jan 4 17:57:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09300.trc:
ORA-16037: user requested cancel of managed recovery operation
Tue Jan 4 17:57:57 2011
MRP0: Background Media Recovery process shutdown (*****)
Tue Jan 4 17:57:58 2011
Managed Standby Recovery Canceled (*****)
Completed: alter database recover managed standby database cancel
Tue Jan 4 17:58:10 2011
Shutting down instance: further logons disabled
Tue Jan 4 17:58:10 2011
Stopping background process CJQ0
Tue Jan 4 17:58:10 2011
Stopping background process MMNL
Tue Jan 4 17:58:11 2011
Stopping background process MMON
Tue Jan 4 17:58:12 2011
Shutting down instance (immediate)
License high water mark = 3
Tue Jan 4 17:58:12 2011
Stopping Job queue slave processes
Tue Jan 4 17:58:12 2011
Job queue slave processes stopped
Tue Jan 4 17:58:12 2011
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Tue Jan 4 17:58:12 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Tue Jan 4 17:58:17 2011
ARCH shutting down
ARC1: Archival stopped
Tue Jan 4 17:58:22 2011
ARCH shutting down
ARC0: Archival stopped
Tue Jan 4 17:58:24 2011
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Tue Jan 4 17:58:33 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =242
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 2000
sga_max_size = 3221225472
__shared_pool_size = 1006632960
shared_pool_size = 637534208
__large_pool_size = 503316480
large_pool_size = 503316480
__java_pool_size = 16777216
__streams_pool_size = 0
sga_target = 3221225472
control_files = /dev/vg01/rCTRLR1, /dev/vg01/rCTRLR2, /dev/vg01/rCTRLR3
db_block_size = 8192
__db_cache_size = 1677721600
db_cache_size = 637534208
compatible = 10.2.0.1.0
log_archive_config = DG_CONFIG=(APMBPROD,APMBDRDB)
log_archive_dest_1 = LOCATION=/archive/archivelogs/ valid_for=(ONLINE_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=APMBDRDB
log_archive_dest_2 =
log_archive_dest_4 = service=APMBPROD LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=APMBPROD
log_archive_max_processes= 2
standby_archive_dest = /backup/standby_archivelogs
fal_client = APMBDRDB
fal_server = APMBPROD
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
job_queue_processes = 10
background_dump_dest = /oracle/app/oracle/admin/APMBDRDB/bdump
user_dump_dest = /oracle/app/oracle/admin/APMBDRDB/udump
core_dump_dest = /oracle/app/oracle/admin/APMBDRDB/cdump
audit_file_dest = /oracle/app/oracle/admin/APMBDRDB/adump
db_name = APMBPROD
db_unique_name = APMBDRDB
open_cursors = 300
pga_aggregate_target = 1703936000
PMON started with pid=2, OS id=9371
PSP0 started with pid=3, OS id=9373
MMAN started with pid=4, OS id=9375
DBW0 started with pid=5, OS id=9377
LGWR started with pid=6, OS id=9380
CKPT started with pid=7, OS id=9382
SMON started with pid=8, OS id=9384
RECO started with pid=9, OS id=9386
CJQ0 started with pid=10, OS id=9388
MMON started with pid=11, OS id=9390
MMNL started with pid=12, OS id=9392
Tue Jan 4 17:58:35 2011
ALTER DATABASE MOUNT
Tue Jan 4 17:58:39 2011
Setting recovery target incarnation to 2
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=14, OS id=9395
Tue Jan 4 17:58:39 2011
ARC0: Archival started
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Tue Jan 4 17:58:39 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Thread not mounted
ARC1 started with pid=15, OS id=9397
ARC1: Becoming the heartbeat ARCH
ARC1: Thread not mounted
Tue Jan 4 17:58:39 2011
Successful mount of redo thread 1, with mount id 3471861451
Tue Jan 4 17:58:39 2011
Physical Standby Database mounted.
Completed: ALTER DATABASE MOUNT
Tue Jan 4 17:58:51 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:58:51 2011
Attempt to start background Managed Standby Recovery process ()
MRP0 started with pid=16, OS id=9400
Tue Jan 4 17:58:51 2011
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
Tue Jan 4 17:58:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09400.trc:
ORA-00367: checksum error in log file header
ORA-00305: log 2 of thread 1 inconsistent; belongs to another database
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 /dev/vg04/rREDOR21
Clearing online log 2 of thread 1 sequence number 87533
Tue Jan 4 17:58:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09400.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 complete
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:58:57 2011
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 19:37:24 2011
alter database register logfile '/backup/standby_archivelogs/1_87533_622555682.dbf'
Tue Jan 4 19:37:24 2011
There are 1 logfiles specified.
ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
Completed: alter database register logfile '/backup/standby_archivelogs/1_87533_622555682.dbf'
Tue Jan 4 19:37:27 2011
Media Recovery Log /backup/standby_archivelogs/1_87533_622555682.dbf
Tue Jan 4 19:37:43 2011
Media Recovery Waiting for thread 1 sequence 87534
from here it is showing no errors or nothing in my alert log file from yesterday evening

No version number, no definition of what you mean by "standby database" and not a clue as to what you mean by "restore" or why you did it.
No help is possible at this time.
PS: We do not guess at what someone means by "MRM modemout stage" ... you need to define your terms.

ORA-1109 signalled during: alter database close

Similar Messages

Maybe you are looking for