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

Similar Messages

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

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

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 statement in anonymous pl/sql block

Is it possible to include an alter database statement in an anonymous pl/sql block?
When I execute this code to query user_tables for all table names, disable their constraints and drop the table, I got the following error:
***MY CODE
-- DECLARE VARIABLE(S)
DECLARE
     v_TABLE_NAME TABLE_NAME.USER_TABLE%TYPE;
-- DECLARE AND DEFINE CURSOR
CURSOR c_GETTABLES is
     SELECT TABLE_NAME from USER_TABLES;
BEGIN
OPEN c_GETTABLES;
LOOP
FETCH c_GETTABLES into v_TABLE_NAME;
EXIT when c_GETTABLES%notfound;
ALTER TABLE v_TABLE_NAME DISABLE PRIMARY KEY CASCADE;
DROP TABLE v_TABLE_NAME;
END LOOP;
CLOSE c_GETTABLES;
END;
***RESPONSE FROM SERVER
ALTER TABLE v_TABLE_NAME DISABLE PRIMARY KEY CASCADE;
ERROR at line 15:
ORA-06550: line 15, column 1:
PLS-00103: Encountered the symbol "ALTER" when expecting one of the following:
begin case declare exit for goto if loop mod null pragma
raise return select update while with <an identifier>
<a double-quoted delimited-identifier> <a bind variable> <<
close current delete fetch lock insert open rollback
savepoint set sql execute commit forall merge
<a single-quoted SQL string> pipe
Thanks

When you want to perform ddl statements in a (anonymous) PL/SQL block, you have to use dynamic SQL because ddl is not possible in pl/sql.
Dynamic sql means that you sort of execute ddl statements in a sql manner. To use dynamic sql, two options exist:
- dbms_sql package : for oracle before 8i. To use this package is not always easy. Read about it carefully first before using.
- Native Dynamic SQL : implemented in 8i and very easy to use. An example would be :
declare
lv_statement varchar2(32676);
begin
lv_statement := 'ALTER TABLE MY_TABLE DISABLE CONSTRAINT MY_TABLE_CK1';
execute immediate lv_statement;
lv_statement := 'ALTER TABLE MY_TABLE ENABLE CONSTRAINT MY_TABLE_CK1';
execute immediate lv_statement;
end;
Good luck.
Edwin van Hattem

ALTER DATABASE COMMAND ON OFFLINE SQL SERVER

My server is not ciming up as it doesnot have tempdb files on the drive correctly. I nned to use ALTER database command to rectify the files. How can I do this on offline sql server???

As Prashanth mentioned, use SQLCMD. Problem with SSMS is that the object explorer grabs the first and the only connection that is available in single user mode. However, if you still want to use SSMS (many are comfortable with GUI), right click the
SQL instance name and select "disconnect" and also close all other query windows and open File menu --> New --> "Query with Current Connection" menu item and this should now take the one and only available connection in single user
mode
Satish Kartan www.sqlfood.com

Alter database begin backup; missing keyword error

Hi all,
I am trying to put my database in backup mode using the command "alter database begin backup", but it is giving error shown below:
$ sqlplus '/as sysdba'
SQL*Plus: Release 9.2.0.5.0 - Production on Wed Nov 25 16:52:58 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
N05PCS07 READ WRITE
SQL> alter database begin backup;
alter database begin backup
ERROR at line 1:
ORA-00905: missing keyword
NE one can tell why the command is failing??
pls...
Thanks in advance.
SHAILESH

Hello,
All the former posts are right, alter database begin backup; doesn't exists in 9.2 althought
you already have in this release the alter database end backup;.
So as to put all the tablespaces in backup mode in one command I suggest you to create a
stored procedure as follows:
CREATE OR REPLACE PROCEDURE begin_backup IS
TYPE RefCurTyp IS REF CURSOR;
cv RefCurTyp;
sql_cv VARCHAR2(400);
tbs VARCHAR2(128);
sql_stmt VARCHAR2(200);
BEGIN
-- Mise en BEGIN BACKUP des TABLESPACES
sql_cv := 'SELECT distinct (A.name) FROM sys.v_$tablespace A, sys.v_$datafile B, sys.v_$backup C where A.TS# = B.TS# and B.FILE# = C.FILE# and C.STATUS = ''NOT ACTIVE''';
OPEN cv FOR sql_cv;
LOOP
FETCH cv INTO tbs;
EXIT WHEN cv%NOTFOUND;
sql_stmt := 'ALTER TABLESPACE '||tbs||' BEGIN BACKUP';
EXECUTE IMMEDIATE sql_stmt;
END LOOP;
CLOSE cv;
END;
Then, I just have to call the Procedure like that:
execute <schema>.begin_backup; and all the tablespaces are in backup mode.
This procedure must be created on a User/Schema with the following privileges:
alter tablespace
select on sys.v_$tablespace
select on sys.v_$datafile
select on sys.v_$backupHope it can help.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Nov 25, 2009 9:44 PM

SHUTDOWN: Active sessions prevent database close operation

Hi
Yesterday morning, our Oracle Apps Database did not shutdown and throws the following error.
Fri May 11 06:57:18 2012
Active call for process 2031784 user 'xxxl' program 'oracleyyy@zzz'
SHUTDOWN: waiting for active calls to complete.
Fri May 11 07:04:01 2012
Incremental checkpoint up to RBA [0x165b.1b2b21.0], current log tail at RBA [0x165b.1b2b21.0]
Fri May 11 07:11:14 2012
MMNL absent for 1203 secs; Foregrounds taking over
Fri May 11 07:24:05 2012
Incremental checkpoint up to RBA [0x165b.1b2b42.0], current log tail at RBA [0x165b.1b2b4a.0]
Fri May 11 07:44:10 2012
Incremental checkpoint up to RBA [0x165b.1b2b6f.0], current log tail at RBA [0x165b.1b2b7d.0]
Fri May 11 07:52:18 2012
SHUTDOWN: Active sessions prevent database close operation
Fri May 11 08:04:39 2012
Since last 3 years, we never faced such a situation even though many modules (oracle Apps) were implemented from time to time. This time OTL module is going live and consultants were running some procedure during backup start time.
Even after issuing 'addbctl.sh stop immediate', how come oracle did not close all the database sessions? How to prevent such situation in future?
Any help is highly appreciated.
Regards
Arizuddin

you can first do a alter system checkpoint and then try to shutdown the database.
You can also kill all the active user sessions from v$session and then shutdown the database.

Alter database archieving;

hi,
while alter the database to nonarchieving mode to archieving mode i am getting the followuing error
pls give the solution for this
SQL> startup mount
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size 1348508 bytes
Variable Size 255855716 bytes
Database Buffers 272629760 bytes
Redo Buffers 5828608 bytes
Database mounted.
SQL> select log_mode from v$database;
LOG_MODE
NOARCHIVELOG
SQL> shutdown;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup mount exclusive;
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size 1348508 bytes
Variable Size 255855716 bytes
Database Buffers 272629760 bytes
Redo Buffers 5828608 bytes
Database mounted.
SQL> alter database archivelog;
alter database archivelog
ERROR at line 1:
ORA-00265: instance recovery required, cannot set ARCHIVELOG mode

Hi;
As Aman mention your db is not closed normaly, you are using abort option which mean you say you db cjust close wihtout any checking. Follow
1. shutdown immediate;
2. startup mount exclusive;
3. alter database archivelog;
4. alter database open;
5. SELECT LOG_MODE FROM SYS.V$DATABASE;
While you are doing all those process also check alert.log for any error message
Regard
Helios

Errors in alert log and listener log and "alter database mount exclusive"

Hello!
I need a help.
Database 11R2 works under MS Windows Server.
Whwn I start it using Services, according alert log it is started by command "alter database mount exclusive".
Next - alter database open.
After this, it seams that program, which should put data into database, can not work with it, because I see errors in alert log: ora-12537, 12560, 12535, 12570, 12547.
What does itmean and what to do?
This is extract from alert_log
ORACLE_BASE from environment = C:\Oracle
Mon Feb 04 14:54:53 2013
alter database mount exclusive
Successful mount of redo thread 1, with mount id 1458539517
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Thread 1 opened at log sequence 3105
Current log# 3 seq# 3105 mem# 0: C:\ORACLE\ORADATA\xxx\REDO03.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
No Resource Manager plan active
Mon Feb 04 14:55:04 2013
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Mon Feb 04 14:55:06 2013
QMNC started with pid=20, OS id=2860
Completed: alter database open
Mon Feb 04 14:55:11 2013
Starting background process CJQ0
Mon Feb 04 14:55:11 2013
CJQ0 started with pid=25, OS id=2000
Mon Feb 04 14:55:11 2013
db_recovery_file_dest_size of 4977 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Feb 04 15:00:29 2013
Starting background process SMCO
Mon Feb 04 15:00:29 2013
SMCO started with pid=32, OS id=3212
Edited by: kogotok1 on Feb 4, 2013 4:54 PM

Thank you.
But in the same time - when I see in alert log those error messages ora -12560, 12537,12535,12570 and so on - clients programs, whiie try to connect, hang up.
For sql plus takes 20 minutes to connect.
lsnrctl status gives the following
LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 04-FEB-2013 16:01
:46
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxx-BD.mosxxx
.elektra.net)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Produ
ction
Start Date 01-FEB-2013 10:22:48
Uptime 3 days 5 hr. 39 min. 54 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File C:\Oracle\listener.ora
Listener Log File c:\oracle\diag\tnslsnr\xxx-BD\listener\alert\l
og.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=xxx-BD.mosxxx.elektra.net)
(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "XXX" has 2 instance(s).
Instance "XXX", status UNKNOWN, has 1 handler(s) for this service...
Instance "xxx", status READY, has 1 handler(s) for this service...
Service "XXXDB" has 1 instance(s).
Instance "xxx", status READY, has 1 handler(s) for this service...
The command completed successfully
To tell the truth I am confuse - I thought I have only 1 service "XXXDB" and 1 instance - "xxx".
May be I have wrong entries in tnslsnr.ora?

'alter database open resetlogs' didn't reset one of the datafiles

I've spent the last three and a half weeks recovering an oracle database (11g 64-bit linux) because of a corrupt block in an online redo log (which I thought was being written to multiple locations). I restored the files, moving some of them around in the process; recovered to the latest possible point; moved files back to their proper location; ran 'alter database open resetlogs'; and one of the datafiles (from a bigfile tablespace) didn't get reset. I checked afterward, and it was marked offline. I do not remember placing the file offline, and cannot find such a statement in my last 300 sqlplus commands, which includes commands well before I renamed this file and the commands surrounding the rename.
Restoring/recovering the database again will take too long, and is a remarkably poor option. Even if the database had opened correctly, the affected tablespace would not have been touched in the two or three minutes the database was open. Is there any way to force oracle to reset the logs again or otherwise fix this one file to mark it with the same date? Only allowing the resetlogs option after an incomplete recovery seems a poor restriction, especially, if files can slip through like this. I'm suspecting there is someway to just fix the checkpoint values for the tablespace, but I don't know where to begin. This particular file is <5% of the database, so if I have to do some sort of backup/restore with just it, that is probably doable.

0: 11.1.0.6.0 on SUSE Linux Enterprise Server 10 SP2
1: rman
backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_datafiles_%p' (database);
backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_archivelogs_%p' archivelog all delete input;
backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_control_%p' current controlfile spfile;
2:
restore database; --not sure what datafiles were restored with this
restore datafile X; --several files were restored individually
recover database until scn 1137554504; -- I verified that all datafiles were on the same checkpoint after this finished. Not having placed any files offline, I didn't bother checking that.
3:
SQL> alter database open resetlogs;
Database altered.
Elapsed: 00:04:20.34
SQL> quit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
4: Nothing in the tablespace has been touched since I ran 'alter database open resetlogs;'. It also appears that oracle placed the file offline (without me telling it to do so) and left it that way through the resetlogs, leaving the tablespace unusable during the time it was opened. The only things that would be out of date are the 'RESETLOGS_CHANGE#', the 'CHECKPOINT_CHANGE#', and associated values. It's still at the last scn before the resetlogs, and the system has been in archivelog mode the entire time. This is all information that Oracle could be tracking, and from a program logic standpoint there is no reason why Oracle cannot tie together the changes before the resetlogs, the resetlogs command and the changes after the resetlogs into a new, continuous string of changes. I assume there is some such feature in a high-caliber program because I'm actually a programmer (who would have included such advanced tracking features), and I've become a DBA out of necessity. I admit to not knowing all of the oracle DBA commands, hence me posting here before doing the work of submitting a request to metalink.
5: I consider it a poor restriction because it doesn't always reset the logs on all files, and as far as my knowledge goes it has rendered my 3.5 week recovery process WORTHLESS. I suppose it could cause numerous errors, especially if the database wasn't cleanly shut down, but having the ability to do something equivalent to datafiles that oracle skipped the process on seems quite useful in my situation. I guess the more fundamental problem to complain about is that it would apply such changes to only some of the files, while leaving others unusable, instead of just giving me an error that some files weren't going to be reset, but I think I'm done venting my Oracle frustrations for now.
Am I stuck with a tablespace that I cannot bring online with the database open, or is there some sort of 'alter database datafile' command (or anything else) that I know nothing of that will fix the straggling file?
Edited by: jbo5112 on Oct 5, 2009 3:33 PM -- obfuscated some file names to secure identity.

RMAN-11001: alter database mount standby database

I'm doing a duplicate for a standby database and I'm getting this error
Oracle 8i Tru64
RMAN-03002: failure during compilation of command
RMAN-03013: command type: Duplicate Db
RMAN-03015: error occurred in stored script Memory Script
RMAN-03006: non-retryable error occurred during execution of command: sql
RMAN-07004: unhandled exception during command execution on channel clone_defaul
t
RMAN-20000: abnormal termination of job step
RMAN-11003: failure during parse/execution of SQL statement: alter database moun
t standby database
RMAN-11001: Oracle Error: ORA-03113: end-of-file on communication channel
Recovery Manager complete.
Any help please

Check for parameter mismatches between parameter file and control file.
Check your parameter file. Check db_name paramter in paramter file used in the standby database.

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

Reg : alter database close

Similar Messages

Maybe you are looking for