Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Best laid plans... HELP!!!
Ok ,
there are some dirty solutions it depends on how desperate you are.
You can create a control file and ignore your datafile.
This will then start your database.
Here is a script that you can cook to your own desire.
This I you to copy databases and rename them.
The principal is the same.
#!/bin/ksh # # Installation de U100N0D3 #
mv ./ORA_DB/U100N0D2 ./ORA_DB/U100N0D3 mv ./ORA_DB/U100N0D2/arch ./ORA_DB/U100N0D3/arch mv ./ORA_DB/U100N0D2/audit ./ORA_DB/U100N0D3/audit mv ./ORA_DB/U100N0D2/audit/ora_9839.aud ./ORA_DB/U100N0D3/audit/ora_9839.aud mv ./ORA_DB/U100N0D2/audit/ora_10883.aud ./ORA_DB/U100N0D3/audit/ora_10883.aud mv ./ORA_DB/U100N0D2/audit/ora_3066.aud ./ORA_DB/U100N0D3/audit/ora_3066.aud mv ./ORA_DB/U100N0D2/audit/ora_3138.aud ./ORA_DB/U100N0D3/audit/ora_3138.aud mv ./ORA_DB/U100N0D2/audit/ora_3315.aud ./ORA_DB/U100N0D3/audit/ora_3315.aud mv ./ORA_DB/U100N0D2/audit/ora_3338.aud ./ORA_DB/U100N0D3/audit/ora_3338.aud mv ./ORA_DB/U100N0D2/audit/ora_3522.aud ./ORA_DB/U100N0D3/audit/ora_3522.aud mv ./ORA_DB/U100N0D2/audit/ora_3826.aud ./ORA_DB/U100N0D3/audit/ora_3826.aud mv ./ORA_DB/U100N0D2/bdump ./ORA_DB/U100N0D3/bdump mv ./ORA_DB/U100N0D2/bdump/alert_U100N0D2.log
mv ./ORA_DB/U100N0D2/bdump/pmon_3069.trc ./ORA_DB/U100N0D3/bdump/pmon_3069.trc mv ./ORA_DB/U100N0D2/cdump ./ORA_DB/U100N0D3/cdump mv ./ORA_DB/U100N0D2/pfile ./ORA_DB/U100N0D3/pfile mv ./ORA_DB/U100N0D2/pfile/cnfgU100N0D2.ora
mv ./ORA_DB/U100N0D2/temp ./ORA_DB/U100N0D3/temp mv ./ORA_DB/U100N0D2/udump ./ORA_DB/U100N0D3/udump mv ./ORA_DB/U100N0D2/udump/ora_3066.trc ./ORA_DB/U100N0D3/udump/ora_3066.trc mv ./ORA_DB/U100N0D2/udump/ora_3315.trc ./ORA_DB/U100N0D3/udump/ora_3315.trc mv ./ORA_DB/U100N0D2/udump/ora_3522.trc ./ORA_DB/U100N0D3/udump/ora_3522.trc mv ./ORA_DB/U100N0D2/U100N0D2_CTL_01.dbf ./ORA_DB/U100N0D3/U100N0D3_CTL_01.dbf mv ./ORA_DB/U100N0D2/U100N0D2_CTL_02.dbf ./ORA_DB/U100N0D3/U100N0D3_CTL_02.dbf mv ./ORA_DB/U100N0D2/U100N0D2_CTL_03.dbf ./ORA_DB/U100N0D3/U100N0D3_CTL_03.dbf mv ./ORA_DB/U100N0D2/U100N0D2_REDO_11.dbf ./ORA_DB/U100N0D3/U100N0D3_REDO_11.dbf
mv ./ORA_DB/U100N0D2/U100N0D2_REDO_12.dbf ./ORA_DB/U100N0D3/U100N0D3_REDO_12.dbf
mv ./ORA_DB/U100N0D2/U100N0D2_REDO_13.dbf ./ORA_DB/U100N0D3/U100N0D3_REDO_13.dbf
mv ./ORA_DB/U100N0D2/U100N0D2_REDO_21.dbf ./ORA_DB/U100N0D3/U100N0D3_REDO_21.dbf
mv ./ORA_DB/U100N0D2/U100N0D2_RBS_01.dbf ./ORA_DB/U100N0D3/U100N0D3_RBS_01.dbf mv ./ORA_DB/U100N0D2/U100N0D2_REDO_22.dbf ./ORA_DB/U100N0D3/U100N0D3_REDO_22.dbf
mv ./ORA_DB/U100N0D2/U100N0D2_REDO_23.dbf ./ORA_DB/U100N0D3/U100N0D3_REDO_23.dbf
mv ./ORA_DB/U100N0D2/U100N0D2_SYSTEM_01.dbf
./ORA_DB/U100N0D3/U100N0D3_SYSTEM_01.dbf
mv ./ORA_DB/U100N0D2/U100N0D2_TEMP_01.dbf ./ORA_DB/U100N0D3/U100N0D3_TEMP_01.dbf
mv ./ORA_DB/U100N0D2/U100N0D2_TOOLS_01.dbf
./ORA_DB/U100N0D3/U100N0D3_TOOLS_01.dbf
mv ./ORA_DB/U100N0D2/U100N0D2_CHK_TB_01.dbf
./ORA_DB/U100N0D3/U100N0D3_CHK_TB_01.dbf
mv ./ORA_DB/U100N0D2/U100N0D2_USERS_01.dbf
./ORA_DB/U100N0D3/U100N0D3_USERS_01.dbf
mv ./ORA_DB/U100N0D2/U100N0D2_VOL_SIC_01.dbf
./ORA_DB/U100N0D3/U100N0D3_VOL_SIC_01.dbf
mv /u01/initU100N0D3.ora /u01/pfile/
mv /u01/pfile/initU100N0D3.ora /u01/pfile/initU100N0D3.ora.old
cat /u01/pfile/initU100N0D3.ora.old | sed -e s!/u112!/u01!g -e
s/U100N0D2/U100N0D3/g > /u01/pfile/initU100N0D3.ora
ln -s /u01/pfile/initU100N0D3.ora ${ORACLE_HOME}/dbs/initU100N0D3.ora
mv /u01/ORA_DB/U100N0D3/pfile/cnfgU100N0D3.ora
/u01/ORA_DB/U100N0D3/pfile/mtsU100N0D3.ora /u01/ORA_DB/U100N0D3/pfile/cnfgU100N0D3.ora /u01/ORA_DB/U100N0D3/pfile/mtsU100N0D3.ora.oldcat /u01/ORA_DB/U100N0D3/pfile/cnfgU100N0D3.ora
/u01/ORA_DB/U100N0D3/pfile/mtsU100N0D3.ora.old | sed -e s!/u112!/u01!g -e s/U100N0D2/U100N0D3/g > /u01/ORA_DB/U100N0D3/pfile/cnfgU100N0D3.ora /u01/ORA_DB/U100N0D3/pfile/mtsU100N0D3.orarunning=`ps -ef | grep dbwr_U100N0D2 | grep -v grep | wc -l` if [ $running -ne 0 ]
connect internal shutdown immediate exit
connect internal
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE SET DATABASE "U100N0D3" RESETLOGS NOARCHIVELOG
MAXLOGFILES 20
MAXLOGMEMBERS 4
MAXDATAFILES 250
MAXINSTANCES 1
MAXLOGHISTORY 100
LOGFILE
GROUP 1 (
'/u01/ORA_DB/U100N0D3/U100N0D3_REDO_11.dbf', '/u01/ORA_DB/U100N0D3/U100N0D3_REDO_12.dbf', '/u01/ORA_DB/U100N0D3/U100N0D3_REDO_13.dbf') SIZE 2M,
'/u01/ORA_DB/U100N0D3/U100N0D3_REDO_21.dbf', '/u01/ORA_DB/U100N0D3/U100N0D3_REDO_22.dbf', '/u01/ORA_DB/U100N0D3/U100N0D3_REDO_23.dbf') SIZE 2M
'/u01/ORA_DB/U100N0D3/U100N0D3_SYSTEM_01.dbf', '/u01/ORA_DB/U100N0D3/U100N0D3_TEMP_01.dbf', '/u01/ORA_DB/U100N0D3/U100N0D3_RBS_01.dbf', '/u01/ORA_DB/U100N0D3/U100N0D3_TOOLS_01.dbf', '/u01/ORA_DB/U100N0D3/U100N0D3_CHK_TB_01.dbf', '/u01/ORA_DB/U100N0D3/U100N0D3_USERS_01.dbf', '/u01/ORA_DB/U100N0D3/U100N0D3_VOL_SIC_01.dbf';
alter user SYSADM identified by U100N0D3; exit
connect internal startup exit
Any other questions ask aunt_augusta_at_oriolecorp.com Cheers Peter
Rick Carroll wrote:
> I wanted to roll my database back using a cold backup. The problem is that > one of my (we're using unix cooked filesystems) filesystems was missed in > the backup... I have already restored everything except the one file system > (the tablespace contains 26 small tables). now when I try to start, the > systems complains about the control file being older than the "data3" (My > filesystem) and won't open the database. > we have tried recovering, we have tried using the recover until option... > What can we do to get this thing sane again?? > > Rick CarrollReceived on Thu Sep 03 1998 - 13:39:18 CDT
![]() |
![]() |