Home » RDBMS Server » Backup & Recovery » ORA-01180: can not create datafile 1
ORA-01180: can not create datafile 1 [message #256027] Thu, 02 August 2007 16:02 Go to next message
Lemuel
Messages: 6
Registered: August 2007
Junior Member
Hi, need aasistance please...

i've create a compressed backup set using rman with the script below but during restoration it fails. please advice what seems to be the problem.

BACKUP
run {
allocate channel d1 type disk format '/backup/01/sing_%d_%s_%p.bus';
allocate channel d2 type disk format '/backup/02/sing_%d_%s_%p.bus';
allocate channel d3 type disk format '/backup/03/sing_%d_%s_%p.bus';
allocate channel d4 type disk format '/backup/04/sing_%d_%s_%p.bus';
setlimit channel d1 kbytes 4000000;
setlimit channel d2 kbytes 4000000;
setlimit channel d3 kbytes 4000000;
setlimit channel d4 kbytes 4000000;
backup as compressed backupset database filesperset 4;
copy current controlfile for standby to '/backup/01/ctl/singprd.ctl';
release channel d1;
release channel d2;
release channel d3;
release channel d4;
}

RESTORATION LOG
Starting restore at 03-AUG-07
Starting implicit crosscheck backup at 03-AUG-07
Crosschecked 259 objects
Finished implicit crosscheck backup at 03-AUG-07

Starting implicit crosscheck copy at 03-AUG-07
Crosschecked 4 objects
Finished implicit crosscheck copy at 03-AUG-07

searching for all files in the recovery area
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: +datadg/SINGPRD/TEMPFILE/TEMP.362.579900843
File Name: +datadg/SINGPRD/TEMPFILE/TEMP.368.580249283
File Name: +datadg/SINGPRD/TEMPFILE/TEMP.313.586219857
File Name: +datadg/SINGPRD/TEMPFILE/TEMP.344.613839985
File Name: +datadg/SINGPRD/DATAFILE/PPCSGMW_ACCOUNTS_IDX_TS2.346.586217177
File Name: +datadg/SINGPRD/DATAFILE/PPCSG_TOPUPS_IDX_TS1.336.586217185
File Name: +datadg/SINGPRD/DATAFILE/PPCSG_CALLDED_IDX_TS2.310.586217187
File Name: +datadg/SINGPRD/DATAFILE/PPCSG_NUMPORT.308.586217187
File Name: +datadg/SINGPRD/DATAFILE/PPCSGMW_ACCOUNTS_IDX_TS1.278.586217187
File Name: +datadg/SINGPRD/DATAFILE/PPCSG_DATA2.279.586217193
File Name: +datadg/SINGPRD/DATAFILE/PPCSG_LOGS_TS1.307.586217193


creating datafile fno=1 name=+DATADG/singprd/datafile/system.259.579798133
released channel: d1
released channel: d2
released channel: d3
released channel: d4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/03/2007 04:44:40
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '+DATADG/singprd/datafile/system.259.579798133'

Report message to a moderator

Re: ORA-01180: can not create datafile 1 [message #256028 is a reply to message #256027] Thu, 02 August 2007 16:12 Go to previous messageGo to next message
DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland
Senior Member
VALIDATE your backup,wheather its good for restore.

For SYSTEM tablespace.
RESTORE DATAFILE 1 VALIDATE;

Report message to a moderator

Re: ORA-01180: can not create datafile 1 [message #256030 is a reply to message #256028] Thu, 02 August 2007 16:17 Go to previous messageGo to next message
Lemuel
Messages: 6
Registered: August 2007
Junior Member
yep, here's the output:

Starting restore at 03-AUG-07
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1080 devtype=DISK

data file 1 will be created automatically during restore operation
restore not done; all files readonly, offline, or already restored
Finished restore at 03-AUG-07

BTW, im running in ASM.

Report message to a moderator

Re: ORA-01180: can not create datafile 1 [message #256032 is a reply to message #256030] Thu, 02 August 2007 16:23 Go to previous messageGo to next message
DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland
Senior Member
I have few question.
You restoring it on same Machine?
Your Backup was finshed Successfuly?
Paths are same?
permissions on DISKGROUPS?


Post your restore database command.

Report message to a moderator

Re: ORA-01180: can not create datafile 1 [message #256034 is a reply to message #256032] Thu, 02 August 2007 16:25 Go to previous messageGo to next message
Lemuel
Messages: 6
Registered: August 2007
Junior Member

You restoring it on same Machine? - Nope, im restoring a standby db
Your Backup was finshed Successfuly? - yep
Paths are same? - nope
permissions on DISKGROUPS? - all are in set.

Report message to a moderator

Re: ORA-01180: can not create datafile 1 [message #256035 is a reply to message #256034] Thu, 02 August 2007 16:29 Go to previous messageGo to next message
DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland
Senior Member
Did You create Standby Controlfile or just moved the same controlfile??
Check the file size on both server (CHECKSUM).
Did you used DB_FILE_NAME_CONVERT Parameter??

[Updated on: Thu, 02 August 2007 16:29]

Report message to a moderator

Re: ORA-01180: can not create datafile 1 [message #256036 is a reply to message #256035] Thu, 02 August 2007 16:33 Go to previous messageGo to next message
Lemuel
Messages: 6
Registered: August 2007
Junior Member
Did You create Standby Controlfile or just moved the same controlfile?? - i've created a new stdby controlfile coz its included in my backup script.

Check the file size on both server (CHECKSUM). - how?

Did you used DB_FILE_NAME_CONVERT Parameter?? - nope, i use the set newname

i was using almost the same script before as what i've using before it's just that i added the as compressed backupset in the backup script. then this happens.

Report message to a moderator

Re: ORA-01180: can not create datafile 1 [message #256038 is a reply to message #256036] Thu, 02 August 2007 16:44 Go to previous messageGo to next message
DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland
Senior Member

Quote:
as compressed backupset



Its not a problem.
Can you Post Restore script?

[Updated on: Thu, 02 August 2007 16:44]

Report message to a moderator

Re: ORA-01180: can not create datafile 1 [message #256040 is a reply to message #256038] Thu, 02 August 2007 16:46 Go to previous messageGo to next message
Lemuel
Messages: 6
Registered: August 2007
Junior Member
here's the restore script: do i have to specify something if the backupset is compressed?

run {
allocate channel d1 type disk format '/oracle_old/archive/lem/backup/01/sing_%d_%s_%p.bus';
allocate channel d2 type disk format '/oracle_old/archive/lem/backup/02/sing_%d_%s_%p.bus';
allocate channel d3 type disk format '/oracle_old/archive/lem/backup/03/sing_%d_%s_%p.bus';
allocate channel d4 type disk format '/oracle_old/archive/lem/backup/04/sing_%d_%s_%p.bus';
set newname for datafile 1 to '+DATADG/singprd/datafile/system.259.579798133';
set newname for datafile 2 to '+DATADG/singprd/datafile/undotbs1.260.579798177';
set newname for datafile 3 to '+DATADG/singprd/datafile/sysaux.261.579798205';
set newname for datafile 4 to '+DATADG/singprd/datafile/undotbs2.263.579798225';
set newname for datafile 5 to '+DATADG/singprd/datafile/users.264.579798253';
set newname for datafile 6 to '+DATADG/singprd/datafile/ppcsg_data.266.579803891';
set newname for datafile 7 to '+DATADG/singprd/datafile/ppcsg_data2.267.579803919';
set newname for datafile 8 to '+DATADG/singprd/datafile/sms_data2.268.579803947';
set newname for datafile 9 to '+DATADG/singprd/datafile/ppcsg_idx2.269.579803975';
set newname for datafile 10 to '+DATADG/singprd/datafile/ppcsg_idx.270.579803989';
set newname for datafile 11 to '+DATADG/singprd/datafile/ppcsg_logs_ts1.271.579804005';
set newname for datafile 12 to '+DATADG/singprd/datafile/ppcsg_logs_ts1_idx.272.579804019';
set newname for datafile 13 to '+DATADG/singprd/datafile/imsi.273.579804035';
set newname for datafile 14 to '+DATADG/singprd/datafile/imsi_idx.274.579804049';
set newname for datafile 15 to '+DATADG/singprd/datafile/ppcsg_numport.275.579804065';
set newname for datafile 16 to '+DATADG/singprd/datafile/ppcsg_numport_idx.276.579804079';
set newname for datafile 17 to '+DATADG/singprd/datafile/ppcsg_alert_logs_idx_ts1.277.579804093';
set newname for datafile 18 to '+DATADG/singprd/datafile/ppcsg_alert_logs_ts1.278.579804109';
set newname for datafile 19 to '+DATADG/singprd/datafile/ppcsg_audit_logs_idx_ts1.279.579804125';
set newname for datafile 20 to '+DATADG/singprd/datafile/ppcsg_audit_logs_ts1.280.579804139';
set newname for datafile 21 to '+DATADG/singprd/datafile/ppcsg_mw_accounts_ts1.281.579804153';
set newname for datafile 22 to '+DATADG/singprd/datafile/ppcsg_mw_accounts_ts2.282.579804169';
set newname for datafile 23 to '+DATADG/singprd/datafile/ppcsg_mw_accounts_ts3.283.579804185';
set newname for datafile 24 to '+DATADG/singprd/datafile/ppcsg_mw_accounts_ts4.284.579804201';
set newname for datafile 25 to '+DATADG/singprd/datafile/ppcsg_mw_accounts_idx_ts1.285.579804217';
set newname for datafile 26 to '+DATADG/singprd/datafile/ppcsg_mw_accounts_idx_ts2.286.579804231';
set newname for datafile 27 to '+DATADG/singprd/datafile/ppcsg_mw_accounts_idx_ts3.287.579804245';
set newname for datafile 28 to '+DATADG/singprd/datafile/ppcsg_mw_accounts_idx_ts4.288.579804261';
set newname for datafile 29 to '+DATADG/singprd/datafile/ppcsg_mw_accounts_idx_ts5.289.579804275';
set newname for datafile 30 to '+DATADG/singprd/datafile/ppcsgmw_accounts_ts1.290.579804289';
set newname for datafile 31 to '+DATADG/singprd/datafile/ppcsgmw_accounts_ts2.291.579804305';
set newname for datafile 32 to '+DATADG/singprd/datafile/ppcsgmw_accounts_ts3.292.579804321';
set newname for datafile 33 to '+DATADG/singprd/datafile/ppcsgmw_accounts_ts4.293.579804337';
set newname for datafile 34 to '+DATADG/singprd/datafile/ppcsgmw_accounts_idx_ts1.294.579804351';
set newname for datafile 35 to '+DATADG/singprd/datafile/ppcsgmw_accounts_idx_ts2.295.579804367';
set newname for datafile 36 to '+DATADG/singprd/datafile/ppcsgmw_accounts_idx_ts3.296.579804381';
set newname for datafile 37 to '+DATADG/singprd/datafile/ppcsgmw_accounts_idx_ts4.297.579804397';
set newname for datafile 38 to '+DATADG/singprd/datafile/ppcsgmw_accounts_idx_ts5.298.579804411';
set newname for datafile 39 to '+DATADG/singprd/datafile/ppcsg_mw_acc_info_ts1.299.579804425';
set newname for datafile 40 to '+DATADG/singprd/datafile/ppcsg_mw_acc_info_ts2.300.579804441';
set newname for datafile 41 to '+DATADG/singprd/datafile/ppcsg_mw_acc_info_ts3.301.579804457';
set newname for datafile 42 to '+DATADG/singprd/datafile/sgmvno_acc_idx.302.579804471';
set newname for datafile 43 to '+DATADG/singprd/datafile/ppcsg_mw_credits_ts1.303.579804485';
set newname for datafile 44 to '+DATADG/singprd/datafile/ppcsg_mw_credits_ts2.304.579804515';
set newname for datafile 45 to '+DATADG/singprd/datafile/ppcsg_mw_credits_ts3.305.579804541';
set newname for datafile 46 to '+DATADG/singprd/datafile/ppcsg_mw_credits_ts4.306.579804571';
set newname for datafile 47 to '+DATADG/singprd/datafile/ppcsg_mw_credits_ts5.307.579804599';
set newname for datafile 48 to '+DATADG/singprd/datafile/ppcsg_mw_credits_ts6.308.579804629';
set newname for datafile 49 to '+DATADG/singprd/datafile/ppcsg_mw_credits_idx_ts1.309.579804657';
set newname for datafile 50 to '+DATADG/singprd/datafile/ppcsg_mw_credits_idx_ts2.310.579804697';
set newname for datafile 51 to '+DATADG/singprd/datafile/ppcsg_mw_debits_ts1.311.579804735';
set newname for datafile 52 to '+DATADG/singprd/datafile/ppcsg_mw_debits_ts2.312.579804765';
set newname for datafile 53 to '+DATADG/singprd/datafile/ppcsg_mw_debits_ts3.313.579804921';
set newname for datafile 54 to '+DATADG/singprd/datafile/ppcsg_mw_debits_ts4.314.579804949';
set newname for datafile 55 to '+DATADG/singprd/datafile/ppcsg_mw_debits_ts5.315.579804975';
set newname for datafile 56 to '+DATADG/singprd/datafile/ppcsg_mw_debits_ts6.316.579805001';
set newname for datafile 57 to '+DATADG/singprd/datafile/ppcsg_mw_debits_idx_ts1.317.579805029';
set newname for datafile 58 to '+DATADG/singprd/datafile/ppcsg_mw_debits_idx_ts2.318.579805069';
set newname for datafile 59 to '+DATADG/singprd/datafile/ppcsg_ppcards_ts1.319.579805105';
set newname for datafile 60 to '+DATADG/singprd/datafile/ppcsg_ppcards_ts2.320.579805121';
set newname for datafile 61 to '+DATADG/singprd/datafile/ppcsg_ppcards_ts3.321.579805135';
set newname for datafile 62 to '+DATADG/singprd/datafile/ppcsg_ppcards_ts4.322.579805149';
set newname for datafile 63 to '+DATADG/singprd/datafile/ppcsg_ppcards_idx_ts1.323.579805163';
set newname for datafile 64 to '+DATADG/singprd/datafile/ppcsg_ppcards_idx_ts2.324.579805177';
set newname for datafile 65 to '+DATADG/singprd/datafile/ppcsg_topups_ts1.325.579805193';
set newname for datafile 66 to '+DATADG/singprd/datafile/ppcsg_topups_ts2.326.579805207';
set newname for datafile 67 to '+DATADG/singprd/datafile/ppcsg_topups_ts3.327.579805223';
set newname for datafile 68 to '+DATADG/singprd/datafile/ppcsg_topups_ts4.328.579805237';
set newname for datafile 69 to '+DATADG/singprd/datafile/ppcsg_topups_ts5.329.579805253';
set newname for datafile 70 to '+DATADG/singprd/datafile/ppcsg_topups_ts6.330.579805269';
set newname for datafile 71 to '+DATADG/singprd/datafile/ppcsg_topups_idx_ts1.331.579805283';
set newname for datafile 72 to '+DATADG/singprd/datafile/ppcsg_topups_idx_ts2.332.579805309';
set newname for datafile 73 to '+DATADG/singprd/datafile/ppcsg_callded_ts1.333.579805335';
set newname for datafile 74 to '+DATADG/singprd/datafile/ppcsg_callded_ts2.334.579805351';
set newname for datafile 75 to '+DATADG/singprd/datafile/ppcsg_callded_ts3.335.579805365';
set newname for datafile 76 to '+DATADG/singprd/datafile/ppcsg_callded_ts4.336.579805379';
set newname for datafile 77 to '+DATADG/singprd/datafile/ppcsg_callded_ts5.337.579805393';
set newname for datafile 78 to '+DATADG/singprd/datafile/ppcsg_callded_ts6.338.579805409';
set newname for datafile 79 to '+DATADG/singprd/datafile/ppcsg_callded_idx_ts1.339.579805423';
set newname for datafile 80 to '+DATADG/singprd/datafile/ppcsg_callded_idx_ts2.340.579805449';
set newname for datafile 81 to '+DATADG/singprd/datafile/ppcsg_smsded_ts1.341.579805475';
set newname for datafile 82 to '+DATADG/singprd/datafile/ppcsg_smsded_ts2.342.579805491';
set newname for datafile 83 to '+DATADG/singprd/datafile/ppcsg_smsded_ts3.343.579805505';
set newname for datafile 84 to '+DATADG/singprd/datafile/ppcsg_smsded_ts4.344.579805521';
set newname for datafile 85 to '+DATADG/singprd/datafile/ppcsg_smsded_ts5.345.579805535';
set newname for datafile 86 to '+DATADG/singprd/datafile/ppcsg_smsded_ts6.346.579805549';
set newname for datafile 87 to '+DATADG/singprd/datafile/ppcsg_smsded_idx_ts1.347.579805563';
set newname for datafile 88 to '+DATADG/singprd/datafile/ppcsg_smsded_idx_ts2.348.579805591';
set newname for datafile 89 to '+DATADG/singprd/datafile/stp_data.349.579805617';
set newname for datafile 90 to '+DATADG/singprd/datafile/stp_idx.350.579805631';
set newname for datafile 91 to '+DATADG/singprd/datafile/srp_data.351.579805643';
set newname for datafile 92 to '+DATADG/singprd/datafile/srp_idx.352.579805659';
set newname for datafile 93 to '+DATADG/singprd/datafile/ppcsg_rsrv_trans_ts1.353.579805671';
set newname for datafile 94 to '+DATADG/singprd/datafile/ppcsg_rsrv_trans_ts2.354.579805801';
set newname for datafile 95 to '+DATADG/singprd/datafile/ppcsg_rsrv_trans_ts3.355.579805817';
set newname for datafile 96 to '+DATADG/singprd/datafile/ppcsg_rsrv_trans_ts4.356.579805831';
set newname for datafile 97 to '+DATADG/singprd/datafile/ppcsg_rsrv_trans_ts5.357.579805845';
set newname for datafile 98 to '+DATADG/singprd/datafile/ppcsg_rsrv_trans_ts6.358.579805859';
set newname for datafile 99 to '+DATADG/singprd/datafile/ppcsg_rsrv_transidx_ts1.359.579805875';
set newname for datafile 100 to '+DATADG/singprd/datafile/ppcsg_rsrv_transidx_ts2.360.579805889';
set newname for datafile 101 to '+DATADG/singprd/datafile/users2.361.579805919';
set newname for datafile 102 to '+DATADG/singprd/datafile/ppcsg_audit_logs_idx_ts2.362.579868697';
set newname for datafile 103 to '+DATADG/singprd/datafile/ppcsg_audit_logs_ts2.363.579868713';
set newname for datafile 104 to '+DATADG/singprd/datafile/accounts_free_minutes_ts.364.605835951';
set newname for datafile 105 to '+DATADG/singprd/datafile/ppcsg_statspack.dbf';
restore database;
}

Report message to a moderator

Re: ORA-01180: can not create datafile 1 [message #256041 is a reply to message #256040] Thu, 02 August 2007 16:52 Go to previous messageGo to next message
DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland
Senior Member
Use
Quote:
Switch Datafile all

after restore database clause.

Report message to a moderator

Re: ORA-01180: can not create datafile 1 [message #256042 is a reply to message #256041] Thu, 02 August 2007 16:58 Go to previous messageGo to next message
Lemuel
Messages: 6
Registered: August 2007
Junior Member
it seems no change in the error...

any other idea?

Report message to a moderator

Re: ORA-01180: can not create datafile 1 [message #256043 is a reply to message #256042] Thu, 02 August 2007 17:01 Go to previous message
DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland
Senior Member
Check this LINK

Quote:
Restore and Recovery of the Database on a New Host

http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov002.htm

Report message to a moderator

Previous Topic: HOW CAN GET SPACE FROM PERCENT_SPACE_RECLAIMABLE COLUMN OF V$Flash_Recovery_Area_Usage
Next Topic: RMAN error
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Wed May 15 03:15:19 CDT 2024
.:: Forum Home :: Blogger Home :: Wiki Home :: Contact :: Privacy ::.