OraFAQ Forum: Server Administration » ORA-01507: database not mounted

Home » RDBMS Server » Server Administration » ORA-01507: database not mounted (10.2.0.4.0,Linux 2.6)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

ORA-01507: database not mounted [message #626718]

Sat, 01 November 2014 00:42

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi,

When i try to query database i see following error.

[oracle@server01 ~]$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.4.0 - Production on Sat Nov 1 06:33:40 2014

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select open_mode from v$database;
select open_mode from v$database
                      *
ERROR at line 1:
ORA-01507: database not mounted

This is standalone server having 2 databases and problem is with one database DB02.The other database DB01 is in read write mode.
And i see both databases are up and running on server as below.

[oracle@server01 ~]$ ps -ef|grep pmon
oracle   11483 11394  0 07:20 pts/1    00:00:00 grep pmon
oracle   13864     1  0 Oct27 ?        00:00:01 ora_pmon_DB01
oracle   19046     1  0 Oct28 ?        00:00:01 ora_pmon_DB02

Thanks,

[Updated on: Sat, 01 November 2014 01:27]

Report message to a moderator

Re: ORA-01507: database not mounted [message #626719 is a reply to message #626718]

Sat, 01 November 2014 01:44

Michel Cadot
Messages: 68737
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

alter database mount;
alter database open;

Report message to a moderator

Re: ORA-01507: database not mounted [message #626720 is a reply to message #626719]

Sat, 01 November 2014 01:50

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi Michel,

SQL> alter database mount;
alter database mount
*
ERROR at line 1:
ORA-00205: error in identifying control file, check alert log for more info

I found the following in the alert log file.
Quote:

Sat Nov 1 07:47:35 2014
ORA-00202: control file: '/sagscm/redo1/control01.ctl,/sagscm/redo2/control02.ctl'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Nov 1 07:47:35 2014
ORA-205 signalled during: alter database mount...

Request you to help me in fixing the error.

Thanks

Report message to a moderator

Re: ORA-01507: database not mounted [message #626724 is a reply to message #626720]

Sat, 01 November 2014 02:21

Michel Cadot
Messages: 68737
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Oracle is unable to reach the control file.
Either it does not exist or Oracle has not the rights to access it.
Check.

Report message to a moderator

Re: ORA-01507: database not mounted [message #626725 is a reply to message #626720]

Sat, 01 November 2014 02:24

John Watson
Messages: 8966
Registered: January 2010
Location: Global Village

Senior Member

Quote:

ORA-00202: control file: '/sagscm/redo1/control01.ctl,/sagscm/redo2/control02.ctl'

You need to enclose each file name in quotes, not the entire string.

Report message to a moderator

Re: ORA-01507: database not mounted [message #626727 is a reply to message #626720]

Sat, 01 November 2014 02:31

Michel Cadot
Messages: 68737
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Also post the result of

show parameter control

It seems you misplaced the quote around the file names.

[Edit: oops, John already mentioned it, I should refresh the page before posting]

[Updated on: Sat, 01 November 2014 02:32]

Report message to a moderator

Re: ORA-01507: database not mounted [message #626728 is a reply to message #626727]

Sat, 01 November 2014 02:41

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi Michel/John,

Here is the output of control file

SQL> select name,value from v$spparameter where name='control_files';

NAME
--------------------
VALUE
----------------------------------------------------------------------
control_files
/sagscm/redo1/control01.ctl,/sagscm/redo2/control02.ctl


SQL> SQL> sho parameter control

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
control_file_record_keep_time        integer     30
control_files                        string      /sagscm/redo1/control01.ctl,/s
                                                 agscm/redo2/control02.ctl

I still see the same entries in the alert log file.

Regards,

Report message to a moderator

Re: ORA-01507: database not mounted [message #626729 is a reply to message #626728]

Sat, 01 November 2014 02:53

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

>I still see the same entries in the alert log file.
You are consistent & wrong.
EACH control file needs to individually be enclosed is single quote marks separately.

Notice the difference between your & mine.

SQL> select name,value from v$spparameter where name='control_files';

NAME
--------------------------------------------------------------------------------
VALUE
--------------------------------------------------------------------------------
control_files
/home/oracle/app/oracle/oradata/orcl/control01.ctl

control_files
/home/oracle/app/oracle/flash_recovery_area/orcl/control02.ctl

Report message to a moderator

Re: ORA-01507: database not mounted [message #626730 is a reply to message #626729]

Sat, 01 November 2014 03:08

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi Blackswan,

Quote:

EACH control file needs to individually be enclosed is single quote marks separately.

Can you tell me how to change my control file as per yours?

Regards,

[Updated on: Sat, 01 November 2014 03:55]

Report message to a moderator

Re: ORA-01507: database not mounted [message #626733 is a reply to message #626730]

Sat, 01 November 2014 06:12

John Watson
Messages: 8966
Registered: January 2010
Location: Global Village

Senior Member

You do not need to change the controlfile. You need to change the control_files parameter. That you do with an ALTER SYSTEM command.

Report message to a moderator

Re: ORA-01507: database not mounted [message #626736 is a reply to message #626733]

Sat, 01 November 2014 10:55

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi John,

Thanks for your suggestions.

alter system set control_files='/sagscm/redo1/control01.ctl','/sagscm/redo2/control02.ctl' scope=spfile;
shutdown 
startup

Can you confirm the above command is correct ?

Regards,

[Updated on: Sat, 01 November 2014 10:58]

Report message to a moderator

Re: ORA-01507: database not mounted [message #626737 is a reply to message #626736]

Sat, 01 November 2014 10:57

EdStevens
Messages: 1376
Registered: September 2013

Senior Member

oracle11 wrote on Sat, 01 November 2014 10:55

Can you confirm the above command is correct ?

Regards,

Why don't you confirm it yourself by simply TRYING it!?!?!?! What's the worst that could happen????

Report message to a moderator

Re: ORA-01507: database not mounted [message #626738 is a reply to message #626737]

Sat, 01 November 2014 10:59

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi Stevens,
Quote:

Why don't you confirm it yourself by simply TRYING it!?!?!?! What's the worst that could happen????

The change is in production database so don't want to take any risk without confirmation.

Regards,

Report message to a moderator

Re: ORA-01507: database not mounted [message #626739 is a reply to message #626738]

Sat, 01 November 2014 11:11

Michel Cadot
Messages: 68737
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

As your production is currently down until you fix it, what is the risk? The worst thing that can happen is that you can't start it like what you have now.

[Updated on: Sat, 01 November 2014 12:34]

Report message to a moderator

Re: ORA-01507: database not mounted [message #626740 is a reply to message #626738]

Sat, 01 November 2014 11:41

EdStevens
Messages: 1376
Registered: September 2013

Senior Member

oracle11 wrote on Sat, 01 November 2014 10:59

Hi Stevens,

The change is in production database so don't want to take any risk without confirmation.

Your current situation is that you cannot open your production database. And why can't you open it? Because your control_files parameter is mis-configured. So what is the proposed solution? Re-configure your control_files parameter. And if that is wrong, what would be your situation?

And given that this is a production database, what changes were made to get you in this situation? And why were those changes made?

Report message to a moderator

Re: ORA-01507: database not mounted [message #626744 is a reply to message #626738]

Sat, 01 November 2014 14:49

John Watson
Messages: 8966
Registered: January 2010
Location: Global Village

Senior Member

oracle11 wrote on Sat, 01 November 2014 15:59

Hi Stevens,
The change is in production database so don't want to take any risk without confirmation.

Regards,

According to your first post, the database has been in this state since at least October 28. It is now November 1. I do wonder what sort of production is going on.

Report message to a moderator

Re: ORA-01507: database not mounted [message #626752 is a reply to message #626744]

Sat, 01 November 2014 21:31

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi John/Michel/Blackswan,

I followed below steps but ended with error. Could you help me to fix this error.

SQL> alter system set control_files='/sagscm/redo1/control01.ctl','/sagscm/redo2/control02.ctl' scope=spfile;

System altered.

SQL> shutdown immediate;
ORA-01507: database not mounted


ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area 3.4360E+10 bytes
Fixed Size                  2147040 bytes
Variable Size             905973024 bytes
Database Buffers         3.3437E+10 bytes
Redo Buffers               14626816 bytes
Database mounted.
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo2/redo04.log'
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo3/redo04.log'
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo1/redo04.log'

Regards

[Updated on: Sat, 01 November 2014 23:04]

Report message to a moderator

Re: ORA-01507: database not mounted [message #626753 is a reply to message #626752]

Sat, 01 November 2014 23:23

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi All,

Good news is that database is in read write mode.Not sure how it came to read write mode.

SQL> select name,instance_name,OPEN_MODE,TO_CHAR(STARTUP_TIME,'DD-MON-YYYY HH24:MI:SS') "STARTUP_TIME" ,STATUS,LOGINS,database_role from v$instance,v$database;

NAME       INSTANCE_N OPEN_MODE  STARTUP_TIME         STATU LOGINS     DATABASE_ROLE
---------- ---------- ---------- -------------------- ----- ---------- --------------------
CO_DB02   DB02       [b]READ WRITE[/b] 02-NOV-2014 03:29:26 OPEN  ALLOWED    PRIMARY

Now i could see the output of control_files parameter as below

SQL> select name,value from v$spparameter where name='control_files';

NAME            VALUE
--------------- ------------------------------
control_files   /sagscm/redo1/control01.ctl
control_files   /sagscm/redo2/control02.ctl

SQL> show parameter control

NAME                                 TYPE                              VALUE
------------------------------------ --------------------------------- ------------------------------
control_file_record_keep_time        integer                           30
control_files                        string                            /sagscm/redo1/control01.ctl, /
                                                                       sagscm/redo2/control02.ctl
SQL>

Here is the alert log entries during database open.

Sun Nov  2 03:28:56 2014
ALTER SYSTEM SET control_files='/sagscm/redo1/control01.ctl','/sagscm/redo2/control02.ctl' SCOPE=SPFILE;
Sun Nov  2 03:29:12 2014
Shutting down instance: further logons disabled
Sun Nov  2 03:29:12 2014
Stopping background process CJQ0
Sun Nov  2 03:29:12 2014
Stopping background process MMNL
Sun Nov  2 03:29:13 2014
Stopping background process MMON
Sun Nov  2 03:29:14 2014
Shutting down instance (immediate)
License high water mark = 3
Sun Nov  2 03:29:14 2014
Stopping Job queue slave processes, flags = 7
Sun Nov  2 03:29:14 2014
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
Waiting for dispatcher 'D001' to shutdown
Waiting for dispatcher 'D002' to shutdown
Waiting for dispatcher 'D003' to shutdown
Waiting for dispatcher 'D004' to shutdown
All dispatchers and shared servers shutdown
Sun Nov  2 03:29:16 2014
ALTER DATABASE CLOSE NORMAL
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Shutting down Data Guard Broker processes
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Sun Nov  2 03:29:26 2014
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 =154
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.4.0.
System parameters with non-default values:
PMON started with pid=2, OS id=29292
PSP0 started with pid=3, OS id=29294
MMAN started with pid=4, OS id=29296
DBW0 started with pid=5, OS id=29298
DBW1 started with pid=6, OS id=29300
LGWR started with pid=7, OS id=29302
CKPT started with pid=8, OS id=29304
SMON started with pid=9, OS id=29306
RECO started with pid=10, OS id=29308
CJQ0 started with pid=11, OS id=29310
MMON started with pid=12, OS id=29312
Sun Nov  2 03:29:27 2014
starting up 5 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=13, OS id=29314
Sun Nov  2 03:29:27 2014
starting up 12 shared server(s) ...
DMON started with pid=31, OS id=29350
Sun Nov  2 03:29:27 2014
ALTER DATABASE   MOUNT
Sun Nov  2 03:29:34 2014
Setting recovery target incarnation to 11
Sun Nov  2 03:29:34 2014
Successful mount of redo thread 1, with mount id 3194398938
Sun Nov  2 03:29:34 2014
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Sun Nov  2 03:29:34 2014
ALTER DATABASE OPEN
Sun Nov  2 03:29:35 2014
Starting Data Guard Broker (DMON)
NSV1 started with pid=33, OS id=30070
Sun Nov  2 03:29:37 2014
Beginning crash recovery of 1 threads
 parallel recovery started with 15 processes
Archivelog destination LOG_ARCHIVE_DEST_3 validated for no-data-loss recovery
Sun Nov  2 03:29:38 2014
Errors in file /opt/oracle/admin/GSCM/udump/gscm_ora_30062.trc:
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo2/redo04.log'
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo3/redo04.log'
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo1/redo04.log'
Sun Nov  2 03:29:38 2014
Aborting crash recovery due to error 338
Sun Nov  2 03:29:38 2014
Errors in file /opt/oracle/admin/GSCM/udump/gscm_ora_30062.trc:
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo2/redo04.log'
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo3/redo04.log'
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo1/redo04.log'

Regards,

Report message to a moderator

Re: ORA-01507: database not mounted [message #626755 is a reply to message #626753]

Sun, 02 November 2014 01:35

Michel Cadot
Messages: 68737
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Your environment is a total mess. Where did you find this control file? This is not the current one.
From your alert.log unless you didn't post the last lines, the database is not open.
So OPEN_MODE and STATUS should be MOUNTED.

Report message to a moderator

Re: ORA-01507: database not mounted [message #626757 is a reply to message #626755]

Sun, 02 November 2014 01:03

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi Michel,

Here is the content of the alert log.Please tell me if you need further contents of it for your analyze and help me to fix the issue.

ORA-00202: control file: '/sagscm/redo1/control01.ctl,/sagscm/redo2/control02.ctl'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Nov  1 07:47:35 2014
ORA-205 signalled during: alter database mount...
Sun Nov  2 03:28:56 2014
ALTER SYSTEM SET control_files='/sagscm/redo1/control01.ctl','/sagscm/redo2/control02.ctl' SCOPE=SPFILE;
Sun Nov  2 03:29:12 2014
Shutting down instance: further logons disabled
Sun Nov  2 03:29:12 2014
Stopping background process CJQ0
Sun Nov  2 03:29:12 2014
Stopping background process MMNL
Sun Nov  2 03:29:13 2014
Stopping background process MMON
Sun Nov  2 03:29:14 2014
Shutting down instance (immediate)
License high water mark = 3
Sun Nov  2 03:29:14 2014
Stopping Job queue slave processes, flags = 7
Sun Nov  2 03:29:14 2014
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
Waiting for dispatcher 'D001' to shutdown
Waiting for dispatcher 'D003' to shutdown
Waiting for dispatcher 'D004' to shutdown
All dispatchers and shared servers shutdown
Sun Nov  2 03:29:16 2014
ALTER DATABASE CLOSE NORMAL
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Shutting down Data Guard Broker processes
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Sun Nov  2 03:29:26 2014
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 =154
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.4.0.
PMON started with pid=2, OS id=29292
PSP0 started with pid=3, OS id=29294
MMAN started with pid=4, OS id=29296
DBW0 started with pid=5, OS id=29298
DBW1 started with pid=6, OS id=29300
LGWR started with pid=7, OS id=29302
CKPT started with pid=8, OS id=29304
SMON started with pid=9, OS id=29306
RECO started with pid=10, OS id=29308
CJQ0 started with pid=11, OS id=29310
MMON started with pid=12, OS id=29312
Sun Nov  2 03:29:27 2014
starting up 5 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=13, OS id=29314
Sun Nov  2 03:29:27 2014
starting up 12 shared server(s) ...
DMON started with pid=31, OS id=29350
Sun Nov  2 03:29:27 2014
ALTER DATABASE   MOUNT
Sun Nov  2 03:29:34 2014
Setting recovery target incarnation to 11
Sun Nov  2 03:29:34 2014
Successful mount of redo thread 1, with mount id 3194398938
Sun Nov  2 03:29:34 2014
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Sun Nov  2 03:29:34 2014
ALTER DATABASE OPEN
Sun Nov  2 03:29:35 2014
Starting Data Guard Broker (DMON)NSV1 started with pid=33, OS id=30070
Sun Nov  2 03:29:37 2014
Beginning crash recovery of 1 threads
 parallel recovery started with 15 processes
Archivelog destination LOG_ARCHIVE_DEST_3 validated for no-data-loss recovery
Sun Nov  2 03:29:38 2014
Errors in file /opt/oracle/admin/DB02/udump/DB02_ora_30062.trc:
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo2/redo04.log'
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo3/redo04.log'
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo1/redo04.log'
Sun Nov  2 03:29:38 2014
Aborting crash recovery due to error 338
Sun Nov  2 03:29:38 2014
Errors in file /opt/oracle/admin/DB02/udump/DB02_ora_30062.trc:
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo2/redo04.log'
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo3/redo04.log'
ORA-00338: log 4 of thread 1 is more recent than control file
ORA-00312: online log 4 thread 1: '/sagscm/redo1/redo04.log'
ORA-338 signalled during: ALTER DATABASE OPEN...
INSV started with pid=49, OS id=30120
RSM0 started with pid=50, OS id=2251
INSV started with pid=49, OS id=30120
RSM0 started with pid=50, OS id=2251
Sun Nov  2 03:33:00 2014
ALTER SYSTEM SET log_archive_dest_3='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=oudwhdb01.europe.nokia.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=DB02_OULU_XPT.nokia.com)(INSTANCE_NAME=DB02)(SERVER=dedicated)))"','   LGWR SYNC AFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="DB02_OULU" register net_timeout=180  valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Sun Nov  2 03:33:00 2014
ALTER SYSTEM SET log_archive_dest_state_3='ENABLE' SCOPE=BOTH;
Sun Nov  2 03:33:00 2014
ALTER DATABASE OPEN
Sun Nov  2 03:33:00 2014
Beginning crash recovery of 1 threads
 parallel recovery started with 15 processes
Archivelog destination LOG_ARCHIVE_DEST_3 validated for no-data-loss recovery
ARCH: Standby redo logfile selected for thread 1 sequence 69236 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 03:33:00 2014
Started redo scan
Sun Nov  2 03:33:08 2014
Completed redo scan
 1852300 redo blocks read, 99390 data blocks need recovery
Sun Nov  2 03:33:43 2014
Started redo application at
 Thread 1: logseq 69234, block 184004
Sun Nov  2 03:33:46 2014
Recovery of Online Redo Log: Thread 1 Group 2 Seq 69234 Reading mem 0
  Mem# 0: /sagscm/redo1/redo02.log
  Mem# 1: /sagscm/redo3/redo02.log
  Mem# 2: /sagscm/redo2/redo02.log
Sun Nov  2 03:33:49 2014
Recovery of Online Redo Log: Thread 1 Group 3 Seq 69235 Reading mem 0

Regards,

[Updated on: Sun, 02 November 2014 01:14]

Report message to a moderator

Re: ORA-01507: database not mounted [message #626758 is a reply to message #626757]

Sun, 02 November 2014 01:16

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi Michel,

Here is some more contents of the alert log file i copied from bottom of the alert log file.

Private strand flush not complete
  Current log# 5 seq# 69237 mem# 0: /sagscm/redo1/redo05.log
  Current log# 5 seq# 69237 mem# 1: /sagscm/redo3/redo05.log
  Current log# 5 seq# 69237 mem# 2: /sagscm/redo2/redo05.log
LGWR: Standby redo logfile selected to archive thread 1 sequence 69238
LGWR: Standby redo logfile selected for thread 1 sequence 69238 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 03:34:36 2014
Thread 1 advanced to log sequence 69238 (LGWR switch)
Sun Nov  2 03:34:36 2014
  Current log# 6 seq# 69238 mem# 0: /sagscm/redo1/redo06.log
  Current log# 6 seq# 69238 mem# 1: /sagscm/redo3/redo06.log
  Current log# 6 seq# 69238 mem# 2: /sagscm/redo2/redo06.log
Sun Nov  2 03:34:36 2014
Shutting down archive processes
Sun Nov  2 03:34:41 2014
ARCH shutting down
ARC6: Archival stopped
Sun Nov  2 03:34:41 2014
ALTER SYSTEM SET log_archive_dest_3='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=oudwhdb01.europe.nokia.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=GSCM_OULU_XPT.nokia.com)(INSTANCE_NAME=GSCM)(SERVER=dedicated)))"','   LGWR SYNC AFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="GSCM_OULU" register net_timeout=180  valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Sun Nov  2 03:34:41 2014
ALTER SYSTEM SET log_archive_dest_state_3='ENABLE' SCOPE=BOTH;
Sun Nov  2 03:34:41 2014
ALTER SYSTEM ARCHIVE LOG
Sun Nov  2 03:34:41 2014
Thread 1 cannot allocate new log, sequence 69239
Private strand flush not complete
  Current log# 6 seq# 69238 mem# 0: /sagscm/redo1/redo06.log
  Current log# 6 seq# 69238 mem# 1: /sagscm/redo3/redo06.log
  Current log# 6 seq# 69238 mem# 2: /sagscm/redo2/redo06.log
******************************************************************
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_3
******************************************************************
LNSc started with pid=57, OS id=4757
Sun Nov  2 03:34:50 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69239
LGWR: Standby redo logfile selected for thread 1 sequence 69239 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 03:34:51 2014
Thread 1 advanced to log sequence 69239 (LGWR switch)
  Current log# 7 seq# 69239 mem# 0: /sagscm/redo1/redo07.log
  Current log# 7 seq# 69239 mem# 1: /sagscm/redo3/redo07.log
  Current log# 7 seq# 69239 mem# 2: /sagscm/redo2/redo07.log
Sun Nov  2 03:41:24 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69240
LGWR: Standby redo logfile selected for thread 1 sequence 69240 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 03:41:24 2014
Thread 1 advanced to log sequence 69240 (LGWR switch)
  Current log# 8 seq# 69240 mem# 0: /sagscm/redo1/redo08.log
  Current log# 8 seq# 69240 mem# 1: /sagscm/redo3/redo08.log
  Current log# 8 seq# 69240 mem# 2: /sagscm/redo2/redo08.log
Sun Nov  2 03:47:29 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69241
LGWR: Standby redo logfile selected for thread 1 sequence 69241 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 03:47:29 2014
Thread 1 advanced to log sequence 69241 (LGWR switch)
  Current log# 1 seq# 69241 mem# 0: /sagscm/redo1/redo01.log
  Current log# 1 seq# 69241 mem# 1: /sagscm/redo3/redo01.log
  Current log# 1 seq# 69241 mem# 2: /sagscm/redo2/redo01.log
Sun Nov  2 03:51:18 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69242
LGWR: Standby redo logfile selected for thread 1 sequence 69242 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 03:51:19 2014
Thread 1 advanced to log sequence 69242 (LGWR switch)
  Current log# 2 seq# 69242 mem# 0: /sagscm/redo1/redo02.log
  Current log# 2 seq# 69242 mem# 1: /sagscm/redo3/redo02.log
  Current log# 2 seq# 69242 mem# 2: /sagscm/redo2/redo02.log
Sun Nov  2 03:53:38 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69243
LGWR: Standby redo logfile selected for thread 1 sequence 69243 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 03:53:38 2014
Thread 1 advanced to log sequence 69243 (LGWR switch)
  Current log# 3 seq# 69243 mem# 0: /sagscm/redo1/redo03.log
  Current log# 3 seq# 69243 mem# 1: /sagscm/redo3/redo03.log
  Current log# 3 seq# 69243 mem# 2: /sagscm/redo2/redo03.log
Sun Nov  2 03:55:49 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69244
LGWR: Standby redo logfile selected for thread 1 sequence 69244 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 03:55:50 2014
Thread 1 advanced to log sequence 69244 (LGWR switch)
  Current log# 4 seq# 69244 mem# 0: /sagscm/redo1/redo04.log
  Current log# 4 seq# 69244 mem# 1: /sagscm/redo3/redo04.log
  Current log# 4 seq# 69244 mem# 2: /sagscm/redo2/redo04.log
Sun Nov  2 03:56:17 2014
SMON: Parallel transaction recovery tried
Sun Nov  2 03:59:06 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69245
LGWR: Standby redo logfile selected for thread 1 sequence 69245 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 03:59:09 2014
Thread 1 advanced to log sequence 69245 (LGWR switch)
  Current log# 5 seq# 69245 mem# 0: /sagscm/redo1/redo05.log
  Current log# 5 seq# 69245 mem# 1: /sagscm/redo3/redo05.log
  Current log# 5 seq# 69245 mem# 2: /sagscm/redo2/redo05.log
Sun Nov  2 04:00:02 2014
ALTER SYSTEM ARCHIVE LOG
Sun Nov  2 04:00:03 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69246
LGWR: Standby redo logfile selected for thread 1 sequence 69246 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:00:04 2014
Thread 1 advanced to log sequence 69246 (LGWR switch)
  Current log# 6 seq# 69246 mem# 0: /sagscm/redo1/redo06.log
  Current log# 6 seq# 69246 mem# 1: /sagscm/redo3/redo06.log
  Current log# 6 seq# 69246 mem# 2: /sagscm/redo2/redo06.log
Sun Nov  2 04:00:13 2014
alter database begin backup
Sun Nov  2 04:00:33 2014
Completed: alter database begin backup
Sun Nov  2 04:00:41 2014
alter database end backup
Completed: alter database end backup
Sun Nov  2 04:00:44 2014
ALTER SYSTEM ARCHIVE LOG
Sun Nov  2 04:00:45 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69247
LGWR: Standby redo logfile selected for thread 1 sequence 69247 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:00:46 2014
Thread 1 advanced to log sequence 69247 (LGWR switch)
  Current log# 7 seq# 69247 mem# 0: /sagscm/redo1/redo07.log
  Current log# 7 seq# 69247 mem# 1: /sagscm/redo3/redo07.log
  Current log# 7 seq# 69247 mem# 2: /sagscm/redo2/redo07.log
Sun Nov  2 04:02:30 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69248
LGWR: Standby redo logfile selected for thread 1 sequence 69248 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:02:31 2014
Thread 1 advanced to log sequence 69248 (LGWR switch)
  Current log# 8 seq# 69248 mem# 0: /sagscm/redo1/redo08.log
  Current log# 8 seq# 69248 mem# 1: /sagscm/redo3/redo08.log
  Current log# 8 seq# 69248 mem# 2: /sagscm/redo2/redo08.log
Sun Nov  2 04:04:09 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69249
LGWR: Standby redo logfile selected for thread 1 sequence 69249 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:04:09 2014
Thread 1 advanced to log sequence 69249 (LGWR switch)
  Current log# 1 seq# 69249 mem# 0: /sagscm/redo1/redo01.log
  Current log# 1 seq# 69249 mem# 1: /sagscm/redo3/redo01.log
  Current log# 1 seq# 69249 mem# 2: /sagscm/redo2/redo01.log
Sun Nov  2 04:06:02 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69250
LGWR: Standby redo logfile selected to archive thread 1 sequence 69251
LGWR: Standby redo logfile selected for thread 1 sequence 69251 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:08:19 2014
Thread 1 advanced to log sequence 69251 (LGWR switch)
  Current log# 3 seq# 69251 mem# 0: /sagscm/redo1/redo03.log
  Current log# 3 seq# 69251 mem# 1: /sagscm/redo3/redo03.log
  Current log# 3 seq# 69251 mem# 2: /sagscm/redo2/redo03.log
Sun Nov  2 04:10:13 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69252
LGWR: Standby redo logfile selected for thread 1 sequence 69252 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:10:14 2014
Thread 1 advanced to log sequence 69252 (LGWR switch)
  Current log# 4 seq# 69252 mem# 0: /sagscm/redo1/redo04.log
  Current log# 4 seq# 69252 mem# 1: /sagscm/redo3/redo04.log
  Current log# 4 seq# 69252 mem# 2: /sagscm/redo2/redo04.log
Sun Nov  2 04:12:08 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69253
LGWR: Standby redo logfile selected for thread 1 sequence 69253 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:12:08 2014
Thread 1 advanced to log sequence 69253 (LGWR switch)
  Current log# 5 seq# 69253 mem# 0: /sagscm/redo1/redo05.log
  Current log# 5 seq# 69253 mem# 1: /sagscm/redo3/redo05.log
  Current log# 5 seq# 69253 mem# 2: /sagscm/redo2/redo05.log
Sun Nov  2 04:15:51 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69254
LGWR: Standby redo logfile selected for thread 1 sequence 69254 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:15:52 2014
Thread 1 advanced to log sequence 69254 (LGWR switch)
  Current log# 6 seq# 69254 mem# 0: /sagscm/redo1/redo06.log
  Current log# 6 seq# 69254 mem# 1: /sagscm/redo3/redo06.log
  Current log# 6 seq# 69254 mem# 2: /sagscm/redo2/redo06.log
Sun Nov  2 04:19:21 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69255
LGWR: Standby redo logfile selected for thread 1 sequence 69255 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:19:22 2014
Thread 1 advanced to log sequence 69255 (LGWR switch)
  Current log# 7 seq# 69255 mem# 0: /sagscm/redo1/redo07.log
  Current log# 7 seq# 69255 mem# 1: /sagscm/redo3/redo07.log
Thread 1 advanced to log sequence 69257 (LGWR switch)
  Current log# 1 seq# 69257 mem# 0: /sagscm/redo1/redo01.log
  Current log# 1 seq# 69257 mem# 1: /sagscm/redo3/redo01.log
  Current log# 1 seq# 69257 mem# 2: /sagscm/redo2/redo01.log
Sun Nov  2 04:28:05 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69258
LGWR: Standby redo logfile selected for thread 1 sequence 69258 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:28:05 2014
Thread 1 advanced to log sequence 69258 (LGWR switch)
  Current log# 2 seq# 69258 mem# 0: /sagscm/redo1/redo02.log
  Current log# 2 seq# 69258 mem# 1: /sagscm/redo3/redo02.log
  Current log# 2 seq# 69258 mem# 2: /sagscm/redo2/redo02.log
Sun Nov  2 04:30:54 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69259
LGWR: Standby redo logfile selected for thread 1 sequence 69259 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:30:54 2014
Thread 1 advanced to log sequence 69259 (LGWR switch)
  Current log# 3 seq# 69259 mem# 0: /sagscm/redo1/redo03.log
  Current log# 3 seq# 69259 mem# 1: /sagscm/redo3/redo03.log
  Current log# 3 seq# 69259 mem# 2: /sagscm/redo2/redo03.log
Sun Nov  2 04:34:03 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69260
LGWR: Standby redo logfile selected for thread 1 sequence 69260 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:34:03 2014
Thread 1 advanced to log sequence 69260 (LGWR switch)
  Current log# 4 seq# 69260 mem# 0: /sagscm/redo1/redo04.log
  Current log# 4 seq# 69260 mem# 1: /sagscm/redo3/redo04.log
  Current log# 4 seq# 69260 mem# 2: /sagscm/redo2/redo04.log
Sun Nov  2 04:36:49 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69261
LGWR: Standby redo logfile selected for thread 1 sequence 69261 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 04:36:50 2014
Thread 1 advanced to log sequence 69261 (LGWR switch)
  Current log# 5 seq# 69261 mem# 0: /sagscm/redo1/redo05.log
  Current log# 5 seq# 69261 mem# 1: /sagscm/redo3/redo05.log
  Current log# 5 seq# 69261 mem# 2: /sagscm/redo2/redo05.log
Sun Nov  2 04:39:24 2014
 Current log# 3 seq# 69267 mem# 1: /sagscm/redo3/redo03.log
  Current log# 3 seq# 69267 mem# 2: /sagscm/redo2/redo03.log
Sun Nov  2 05:01:06 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69268
LGWR: Standby redo logfile selected for thread 1 sequence 69268 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 05:01:06 2014
Thread 1 advanced to log sequence 69268 (LGWR switch)
  Current log# 4 seq# 69268 mem# 0: /sagscm/redo1/redo04.log
  Current log# 4 seq# 69268 mem# 1: /sagscm/redo3/redo04.log
  Current log# 4 seq# 69268 mem# 2: /sagscm/redo2/redo04.log
Sun Nov  2 05:03:39 2014
Starting control autobackup
Sun Nov  2 05:04:47 2014
Control autobackup written to DISK device
        handle '/sagscm/arch2/temp/cntc-2884734964-20141102-00'
Sun Nov  2 05:05:12 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69269
LGWR: Standby redo logfile selected for thread 1 sequence 69269 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 05:05:13 2014
Thread 1 advanced to log sequence 69269 (LGWR switch)
  Current log# 5 seq# 69269 mem# 0: /sagscm/redo1/redo05.log
  Current log# 5 seq# 69269 mem# 1: /sagscm/redo3/redo05.log
  Current log# 5 seq# 69269 mem# 2: /sagscm/redo2/redo05.log
Sun Nov  2 05:09:12 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69270
LGWR: Standby redo logfile selected for thread 1 sequence 69270 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 05:09:13 2014
Thread 1 advanced to log sequence 69270 (LGWR switch)
  Current log# 6 seq# 69270 mem# 0: /sagscm/redo1/redo06.log
  Current log# 6 seq# 69270 mem# 1: /sagscm/redo3/redo06.log
  Current log# 6 seq# 69270 mem# 2: /sagscm/redo2/redo06.log
Sun Nov  2 05:12:31 2014
LGWR: Standby redo logfile selected to archive thread 1 sequence 69271
LGWR: Standby redo logfile selected for thread 1 sequence 69271 for destination LOG_ARCHIVE_DEST_3
Sun Nov  2 05:12:31 2014
Thread 1 advanced to log sequence 69271 (LGWR switch)
  Current log# 7 seq# 69271 mem# 0: /sagscm/redo1/redo07.log
  Current log# 7 seq# 69271 mem# 1: /sagscm/redo3/redo07.log
  Current log# 7 seq# 69271 mem# 2: /sagscm/redo2/redo07.log

Regards,

Report message to a moderator

Re: ORA-01507: database not mounted [message #626759 is a reply to message #626758]

Sun, 02 November 2014 01:39

Michel Cadot
Messages: 68737
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

So your database is up and running, no more problem.
However, make your client double-check their data.

[Updated on: Sun, 02 November 2014 01:39]

Report message to a moderator

Re: ORA-01507: database not mounted [message #626760 is a reply to message #626759]

Sun, 02 November 2014 02:00

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi Michel,
Quote:

So your database is up and running, no more problem.

I am happy to hear that my database is fine.However i have a query.
In this thread you said below one,but my database is in read write mode.Is that not an issue?Can you confirm ?
Quote:

So OPEN_MODE and STATUS should be MOUNTED.

Regards,

Report message to a moderator

Re: ORA-01507: database not mounted [message #626762 is a reply to message #626760]

Sun, 02 November 2014 02:24

Michel Cadot
Messages: 68737
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

This was said based of the truncated alert.log you posted and let me think the database was not open.
Ignore it.

Report message to a moderator

Re: ORA-01507: database not mounted [message #626763 is a reply to message #626760]

Sun, 02 November 2014 02:25

John Watson
Messages: 8966
Registered: January 2010
Location: Global Village

Senior Member

oracle11 wrote on Sun, 02 November 2014 08:00

Hi Michel,
Quote:
So your database is up and running, no more problem.

I am happy to hear that my database is fine.However i have a query.
In this thread you said below one,but my database is in read write mode.Is that not an issue?Can you confirm ?
Quote:
So OPEN_MODE and STATUS should be MOUNTED.

Regards,

Perhaps the problem comes with that you were not telling the truth (presumably, by accident?) You posted this:
Quote:

SQL> select name,instance_name,OPEN_MODE,TO_CHAR(STARTUP_TIME,'DD-MON-YYYY HH24:MI:SS') "STARTUP_TIME" ,STATUS,LOGINS,database_role from v$instance,v$database; NAME INSTANCE_N OPEN_MODE STARTUP_TIME STATU LOGINS DATABASE_ROLE ---------- ---------- ---------- -------------------- ----- ---------- -------------------- CO_DB02 DB02 READ WRITE 02-NOV-2014 03:29:26 OPEN ALLOWED PRIMARY

Note the time.
Then you posted sections of an alert log that overlapped this time, and show that the query was impossible.

Report message to a moderator

Re: ORA-01507: database not mounted [message #626764 is a reply to message #626763]

Sun, 02 November 2014 03:17

oracle11
Messages: 29
Registered: October 2014
Location: India

Junior Member

Hi Michel/John,

Let me don't confuse you all.As of now database is fine and i am happy that my database is back with normal mode.

Thank you Michel/John and Blackswan for your support in making things happen. Smile

[Updated on: Sun, 02 November 2014 03:18]

Report message to a moderator

Previous Topic:	ORA-00060: deadlock detected while waiting for resource
Next Topic:	license of oracle 11g

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Mar 04 20:53:09 CST 2025