ALTER DATABASE/MODIFY FILE issue

Greetings to all --
We are running SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64), and running into what seems like a bug. One of the largest tables was moved to a separate file group a while ago, and now a large percentage of the rows from that table (about 50GB) , need to
be removed.
We wanted to reduce the amount of transaction log growth and the duration required for the delete. Recovery model was set to BULK_LOGGED before executing the following steps:
1. create a new filegroup
2. create a new file in that filegroup
3. set the new filegroup to be the DEFAULT filegroup
4. SELECT INTO new_table from original_table WHERE filter_condition
5. drop original_table
6. rename new_table to original_table
7. remove original file from original filegroup
8. remove original filegroup
9. MODIFY the logical name of the new file to be the same as the logical name of the original logical name.
ALTER DATABASE myDB
MODIFY FILE ( NAME = new_logicalname, NEWNAME = original_logicalname)
This fails:
Msg 1828, Level 16, State 3, Line 1
The logical file name "original_logicalname" is already in use. Choose a different name.
I noticed that the original filegroup still persisted until I did a transaction log backup, but after that , there is no entry for that file in sys.databasefiles for that database.
Checking sp_helpdb for that database shows only the new logical file name.
Any thoughts would be much appreciated.

This scenario is easily reproduced, and seems not to be "by design".
I put my bets on Sean and say "by design".
I can't put my finger on it, but it has to with doing restores, and particularly log restores. It does not seem to happen with a database in simple recovery. But for a database in full (or bulk_logged) recovery, there lingers a row in sysfiles1 and sysprufiles
for the dropped file.
sys.database_files is a view over sys.sysprufiles and it does not display the deleted file, but it is there with a certain status.
In any case, I can't see that this is the end of the world. It is not likely that you refer to the name of that fill all around the house. But the next time you do this manouvre, you may want to rename the existing file before you drop it and create
the new one.
Erland Sommarskog, SQL Server MVP, [email protected]

Similar Messages

Alter Database Remove File : Partition Files on different folders

I need to remove partition files, once I switch the partition with staging table and empty/truncate the partition.
When I was running the code on my local machine I was passing variable @partition_file_name to following statement:
Declare @partition_file_name varchar(128)='table_abc_201202',
@database_name varchar(128)='test'
Alter Database @database_name Remove File @partition_file_name
Note @partition_file_name is the logical name of the partition file.
I found out partitions are saved in different folders in my Dev env...They are stored in 12 different folders which are named like 1-12.
E.g:
C:\DATA\2\table_abc_201202.ndf
C:\DATA\3\table_abc_201203.ndf
C:\DATA\4\table_abc_201204.ndf
C:\DATA\5\table_abc_201205.ndf
C:\DATA\2\table_abc_201302.ndf
C:\DATA\3\table_abc_201303.ndf
C:\DATA\4\table_abc_201304.ndf
C:\DATA\5\table_abc_201305.ndf
I am wondering , is SQL server with Alter statement is capable of getting the right path for each partition files and remove them accordingly? Or do I need to pass the physical path to the alter statement to get it removed. Though I tried doing that and
got the error.
ZK

I am wondering , is SQL server with Alter statement is capable of getting the right path for each partition files and remove them accordingly? Or do I need to pass the physical path to the alter statement to get it removed. Though I tried doing that and
got the error.
Yes, SQL Server knows which physical file goes with which logical filename. (To see that SQL does know this, do a SELECT * FROM sys.sysfiles - you'll see SQL has a row for every logical filename and that row has the corresponding physical file name.)
And when you do the ALTER DATABASE REMOVE FILE, you must specify the logical filename. You will get an error if you give the physical path.
Tom

During daily refresh/clone alter database rename file genrating logs under $ORACLE_HOME/dbs with name c-1437102747-20130920-16

Did anyone have seen this behavior?
DB version : 11.1.0.7
OS : HP-UX Itanum
EBS -11.5.10.2
We are doing daily refresh/clone of a database instance from production. Recently we are seeing the growth of $ORACLE_HOME/dbs directory during this
refresh.   During investigation we find out that
1) When we rename the database files after database restoration. Each below command genrating the 24MB of log file under $ORACLE_HOME/dbs.
Command :
alter database rename file '/db02/prod/XDB.dbf' to '/db02/test/XDB.dbf';
alter database rename file '/db02/prod/a_archive01.dbf' to '/db02/test/a_archive01.dbf';
Logfiles under $ORACLE_HOME/dbs on target :
-rw-r----- xxxxx 24379392 Sep 20 05:30 ./dbs/c-1437102747-20130920-02
-rw-r----- xxxxx 24379392 Sep 20 05:30 ./dbs/c-1437102747-20130920-03
2) After few minutes, these logs got removed from the directory.
3) Did not find anything unusual in the alert log.

These are controlfile autobackups.   Every time you make a physical change to the database structure, an autobackup is created. In 11.2, the frequency is reduced -- for example if you make 5 changes in quick succession, one autobackup is created.
CONTROLFILE AUTOBACKUP ON    would be visible when you do a SHOW ALL in rman.
Hemant K Chitale

Diff btw "recover datafile file#" & "alter database recover datafile file#"

What is the difference between
"recover datafile file#"
"alter database recover datafile file#"
Thanks
Naveen

I don't mean to be rude, but the statement that "There is no difference in both the commands" is facile in the extreme. Sounds like more off-the-cuff instant advice than the considered thoughts of someone who's actually bothered to try both commands out.
The "alter database recover..." command is a disaster waiting to happen and should never be used by anyone who actually wants to achieve a successful database recovery. It has the effect of suppressing most of the interactive dialogue you get when you submit the shorter "recover..." command, and indeed causes spurious errors to be displayed because the non-interactive recovery process gets it wrong.
For example, here's me recovering my database using the "alter database" syntax:
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\WIN10\USERS01.DBF'
SQL> alter database recover datafile 4;
alter database recover datafile 4
ERROR at line 1:
ORA-00279: change 642359 generated at 07/04/2008 09:03:18 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_9_%U_.ARC
ORA-00280: change 642359 for thread 1 is in sequence #9Note the slightly alarming report of an 'error at line 1'. What's difficult to convey in mere text, however, is that at the end of that output, the thing just sits there, and you've no idea what on Earth is happening on the database. The text tells you it's making a suggestion, but there's no indication of how you accept the suggestion, of what's happening when you do accept it or where anything is up to.
I've interrupted one of those once (fortunately only in a training room) and lost the entire database as a result (because a half-complete, interrupted recovery is worse than no recovery at all).
Compare that with the plain "recover..." syntax example:
SQL> recover datafile 4;
ORA-00279: change 642359 generated at 07/04/2008 09:03:18 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_9_%U_.ARC
ORA-00280: change 642359 for thread 1 is in sequence #9
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 642571 generated at 07/04/2008 09:06:26 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_10_%U_.ARC
ORA-00280: change 642571 for thread 1 is in sequence #10
ORA-00278: log file
'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_9_46TPVL2G_.ARC' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 642576 generated at 07/04/2008 09:06:32 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_12_%U_.ARC
ORA-00280: change 642576 for thread 1 is in sequence #12
ORA-00278: log file
'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_11_46TPVRMK_.ARC' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
Media recovery complete.There are no weird error messages reported here. The suggestion is accompanied by a prompt that tells you how to accept it. Every time a new log is required, a new prompt is given. You can cleanly cancel at any time by typing 'cancel'. You are kept informed throughout and are in charge throughout.
Anyone that uses "alter database" syntax during a recovery is, therefore, either brave or foolhardy. In either case, there is a very profound difference between the two.
Your parting shot that 'alter database' is a SQL command and 'recover' can be an RMAN command misses the point by a wide mile, too. RMAN can issue pretty much any piece of SQL you like, so long as you wrap it in the SQL command:
RMAN> sql 'alter database recover datafile 4';
using target database control file instead of recovery catalog
sql statement: alter database recover datafile 4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 07/04/2008 09:23:16
ORA-00279: change generated at needed for thread
RMAN-11003: failure during parse/execution of SQL statement: alter database recover datafile 4
ORA-00279: change 642359 generated at 07/04/2008 09:03:18 needed for thread 1
ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WIN10\ARCHIVELOG\2008_07_04\O1_MF_1_9_%U_.ARC
ORA-00280: change 642359 for thread 1 is in sequence #9We don't get much further in RMAN with this dodgy form of the recovery command than we did in SQL*Plus, it's true -but that's just because it's a silly command to use in the first place, wherever you thought to use it. The distinction you seek to draw between 'SQL commands' and 'RMAN commands' is false in this case, in other words.

ORA-02231 error when issue ALTER DATABASE FORCE LOGGING

Hi,
Does everybody know why I faced ORA-02231 when issue below command in oracle,
SQL> ALTER DATABASE FORCE LOGGING;
ALTER DATABASE FORCE LOGGING
ERROR at line 1:
ORA-02231: missing or invalid option to ALTER DATABASE
SQL> ALTER DATABASE FORCE LOGGING ;
ALTER DATABASE FORCE LOGGING
ERROR at line 1:
ORA-02231: missing or invalid option to ALTER DATABASE
SQL> ALTER DATABASE FORCE LOGGING
2
SQL> ALTER TABLESPACE BIIS FORCE LOGGING
2 ;
ALTER TABLESPACE BIIS FORCE LOGGING
ERROR at line 1:
ORA-02142: missing or invalid ALTER TABLESPACE option
I use this oracle version:
Oracle9i Enterprise Edition Release 9.0.1.1.1 - Production
PL/SQL Release 9.0.1.1.1 - Production
CORE 9.0.1.1.1 Production
TNS for 32-bit Windows: Version 9.0.1.1.0 - Production
NLSRTL Version 9.0.1.1.1 - Production
Thanks.

Hi Jaffar,
After I checked that you are correct.
I can issue the command without problem in oracle 9i Rel.2.
Thanks for your information.
Tarman.

IS BT CLOUD ALTERING THE "MODIFIED DATE" ON MY FIL...

Hi
I have BT Cloud 2GB Free running as both the downloaded "auto sync" software and also using the Chrome Browser Interface. I am on Windows XP.
I only use Cloud to backup word / excel documents and family photos - basic things I just dont want to risk losing.
I recently noticed something odd, when I sorted my BT Cloud View by "Date Modified" about twenty very 'old' files suddenly appeared at the top of the view - files I hadnt used in about 5 or 6 years.
I definitely had not accessed these files yet when I went to look at them in "My Computer" and clicked on "Properties" I could see that the "Modified Date" had changed. In fact it seems that about a dozen or so files had been "modified" over night while my PC was left on in the next room. No other dates had changed on the files - it did not look like they had been "Re-Saved" I dont think since the original author had not changed.
I started to monitor this and noticed about half a dozen files having their "modified dates" changed every day for the last three or four days. Its only Documents (Word Powerpoint Excel Text etc) that are being modified.
And heres the thing - I ran a search on my computer of files modified in the last week and the only ones where I could not explain the change were files that are being backed up by "BT CLOUD" so its slightly possible there is a link. Of course this could be coincidence but I thought this might be a good initial avenue to explore since without BT Cloud's interface view of my files I would never have even noticed the problem in the first place.
I'm pretty sure its not a Virus - I run my own Scanner every few days, its always up to date and I have Real Time Scanning enabled. I also ran a couple of online scans last night (Norton etc) and they found nothing.
Its a recent development because I use Cloud every week and would have noticed before if things were changing.
So a couple of questions really:
Firstly has anyone else experienced this problem - I read somewhere that Some Virus Scanners can alter the Modified Date on your files unintentionally but the MS hotfix says this only happens in Vista/Win 7 I think and I am on XP. Could it be that when BT Cloud Scans the file it affects its modified date on your PC ?
Secondly Could anyone else access my files in BT Cloud and modify them, and if so would that change to the 'online file' be represented back on my own PC when I "Synced" my backup
Many thanks in advance for any help anyone can offer.

I assume your raws are in DNG format? If xmp is in sidecar, it won't change raw file date.
Anyway, saving xmp does not change any dates in Lightroom, so you should still be able to sort by edit time or capture time...
But if you want control, you have to save manually instead of automatically.
Two things that might help:
1. Filter based on metadata status.
2. robcole.com - DNGPreviewUpdater
Rob

Drop or alter database link question...

I have a database that uses a dblink to connect to a remote database to use a sequence for id's. The remote database is a 12 node rac cluster and when the database link was initially created the admin that created it only specified one of the nodes in the rac cluster in the comnnection description for the database link.
We want to change the link to include both rac nodes but we have a bunch of synonyms that point to the database link and I do not want to invalidate the synonyms.
If I alter the dblink as opposed to drop and recreate then will the synonyms become unusable or invaildated?
Thanks.

First, you cannot change the connection information for a database link using the ALTER DATABASE LINK statement. You'll need to drop and recreate the database link to do so. From the documentation
You cannot use this statement to change the connection or authentication user associated with the database link. To change user, you must re-create the database link.Second, are you saying that the TNS entry was specified explicitly in the CREATE DATABASE LINK statement rather than specifying a TNS alias (i.e. an entry in a tnsnames.ora file)? Normally, you'd specify a TNS alias when you create the database link in which case you could simply modify that alias rather than changing the database link.
Third, synonyms do not become unusable or invalid just because the underlying object does not exist
SQL> create synonym invalid_synonym
2 for not_a_user.not_a_table@not_a_link;
Synonym created.
SQL> select status from dba_objects where object_name = 'INVALID_SYNONYM';
STATUS
VALIDYou'll get an error if you try to use the synonym, of course, but it won't be invalid. As long as you fix the database link before someone tries to use the synonym, there is no issue.
Justin

Alter database OR alter system?? what is the logic?

Hi,
this is just a general question not related to any particular issue. I seem to be missing the logic behind when we need to use the "alter system ... " statements and when we need to use the "alter database ..." statements. Is there a logic I can use to guess ? Or we only need to remember them (or look up for them)?
Let's take an example.
alter database archivelog; & alter system checkpoint;
OR
alter database add logfile; & alter system set undo_retention=800;
If you have a key that can be generally applied please let me know as I am not able to find it. Thank you,
enrico

I am not sure if there is a general rule but this is what I use:
alter database is about modifying the database architecture, like data files, archived log files etc.
alter system is about modifying the instance. so, you are modifying the way oracle runs. Remember that all parameters should be done with alter system (like undo_retention)
hope this will help you.

Crystal Report Server Database Log File Growth Out Of Control?

We are hosting Crystal Report Server 11.5 on Microsoft SQL Server 2005 Enterprise. Our Crystal Report Server SQL 2005 database file size = 6,272 KB, and the log file that goes with the database has a size = 23,839,552.
I have been reviewing the Application Logs and this log file size is auto-increasing about 3-times a week.
We backup the database each night, and run maintenance routines to Check Database Integrity, re-organize index, rebuild index, update statistics, and backup the database.
Is it "Normal" to have such a large LOG file compared to the DATABASE file?
Can you tell me if there is a recommended way to SHRINK the log file?
Some Technical Documents suggest frist truncating the log, and the using the DBCC SHRINKFILE command:
USE CRS
GO
--Truncate the log by changing the database recovery model to SIMPLE
ALTER DATABASE CRS
SET RECOVERY SIMPLE;
--Shrink the truncated log file to 1 gigabyte
DBCC SHRINKFILE (CRS_log, 1000);
GO
--Reset the database recovery model.
ALTER DATABASE CRS
SET RECOVERY FULL;
GO
Do you think this approach would help?
Do you think this approach would cause any problems?

my bad you didn't put the K on the 2nd number.
Looking at my SQL server that's crazy big my logs are in the k's like 4-8.
I think someone enabled some type of debugging on your SQL server, it's more of a Microsoft issue, as our product doesn't require it from looking at my SQL DB's
Regards,
Tim

Problems editing with iPhoto 6 - modified file has a mind of its own. Help!

I have been working through info posted re difficulties storing edits. My modified file (once I eventually found it) appears to simply duplicate originals. Recent attempts show that edits are now being stored as ThumbJPGSegment data. Attempts to open these show 'unreadable file'. 'Could not be imported as the file is in the iPhoto library folder'. What on earth does this mean, and am I doing wrong? I have wasted a day trying to sort this out.
eMac Mac OS X (10.4.7) iLife 06

Posey:
Welcome to the Apple Discussions. The library6.iPhoto file is just the database that keeps track of the photos, edits, books, etc. that is in the library. You edited version of that photo will be located in the Modified folder's subfolder for the roll that the photo is in. The thumbs file is the thumbnail version data base. Those are all library overhead files.
As PhillyPhan warned: Don't tamper with files in the iPhoto Library folder from the Finder. We can emphasize that too much.
If you're doing sharpening it's a know issues that it's nearly impossible to see the effects of sharpening unless you in the separate edit window and viewing at 100%. Otherwise the antialiasing that iPhoto does on the images will smooth out the sharpening that you've applied. If it's other types of edits, i.e. crops, red eye removal then find one of the files you've done that to in the Modified folder and open it with Preview or drag into an open Safari window to view the photo and see if the edit was actually saved.
Do you Twango?
G5 Dual Core 2GHz, 2G RAM, 250G HD; G4 Dual 1Ghz, 1.5G RAM, 80G HD, Mac OS X (10.4.7) 22 LCD Display, 200G & 160G FW HDs, Canon S400, i850 & LIDE 50, Epson R200

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

What if "ALTER DATABASE OPEN" WORKS WHEN DB IS INCONSISTENT???

Hello Everyone,
I heard from couple of friends that in the case of recovery , oracle database opens despite the fact that some of the data files are inconsistent.
Is this really true? If it is, then i think its a bug with specific Oracle patch or release.
Is there anyone who has experienced a similar situation in the past? Please share.
Thanks.
sapguy

Appreciate your response. I ran into a situation where we are not sure of what time choose to choose recovery (point in time) and ended up recovering file by file and its been 100 files .. .none of those files helped with "Media recovery complete" message . This is database refresh from production backup.
Then when i am trying to issue ALTER DATABASE OPEN RESETLOGS one of main guy says do not issue OPEN command as it may corrupt the database.
I came across one of friend who ran into similar situation and he was able open the database , but LATER database started issuing ora 600 due to corrupted files or whatever which never happened. Forgive me .. if my text is confusing.
Thanks.

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

Whenever I modify a photo in Iphoto it puts it in a "modified" subfolder. Why can't I move this modified file (I changed name) back to the Iphoto main file so I can see it when I open my photos?

Whenever I modify a photo in Iphoto it puts it in a "modified" subfolder. Why can't I move this modified file (I changed and saved file name) back to the Iphoto main file so I can see it when I open my photos?

A good general step for strange issues is to renew the iPhoto preference file - quit iPhoto and go to "your user name" ==> library ==> preferences ==> com.apple.iPhoto.plist and trash it - launch iPhoto which creates a fresh new default preference file and reset any personal preferences you have changed and if you have moved the iPhoto library repoint to it. This may help
This does not affect your photos or any database information (keywords, faces, places, ratings, etc) in any way - they are stored in the iPhoto library - the iPhoto preference file simply controls how iPhoto works - which is why renewing it is a good first step.
If that does not cure it backup up your iPhoto library and rebuild it - depress the option and command keys and launch iphoto and use the options there - exact option depends on teh version you have
And always remember - NEVER make any changes of any sort to the structure or content of the iPhoto library - nothing - no deletions - no name changes - nothing
LN

Alter database open resetlogs

Hi,
when I try to duplicate my database by RMAN I have :
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 1452 scn 252730 found to restore
I connect to duplicate database in sqlplus , it is not open.
Than I do :
alter database open resetlogs;
And the database would be open.
Is it bad ? Will we lose the data ? If yes what solution do you propose ?
Effectively I do not know how to use this informations :
log thread 1 seq 1452 scn 252730 found to restore
Please help me to use this informations if helplfull.
Many thanks.

From Oracle Error documentation:
RMAN-06025: no backup of log thread number seq number lowscn string found to restore
Cause: An archive log restore restore could not proceed because no backup of the indicated archived log was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user"s restore operands.
Action: None - this is an informational message. See message 6026 for further details.
RMAN-06026: some targets not found - aborting restore
Cause: Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged.
Action: The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list.
It seems you do not have some of the files required for recover operation. Could you post how this database is backed up using RMAN?

ALTER DATABASE/MODIFY FILE issue

Similar Messages

Maybe you are looking for