Error during Restore Database

Hello everyone!
First of all, i'm sorry for posting another restore problem, but i read all threads related and i still have my problem.
I have a fresh new install of oracleXE, but when i try to restore de database from a backup store in other disk install in the same computer, using the restore database option include with the application, the program show me these steps:
STEP 1:
This operation will shut down and restore the database. Are you sure [Y/N]?
I write 'Y'.
STEP 2:
This operation will shut down and restore the database. Are you sure [Y/N]?y
Restore in progress...
El servicio solicitado ya ha sido iniciado.
Puede obtener más ayuda con el comando NET HELPMSG 2182.
Recovery Manager : Release 10.2.0.1.0 - Production on Vie Ago 31 10:20:45 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
conectado a la base de datos destino: XE (DBID=2513092923)
RMAN> set echo on;
2> startup nomount pfile=C:\DOCUME~1\imgltda\CONFIG~1\Temp\rman_dummy.ora force;
3>
echo activado
instancia Oracle iniciada
Total del ┴rea Global del Sistema 285212672 bytes
Fixed Size 1287016 bytes
Variable Size 92277912 bytes
Database Buffers 188743680 bytes
Redo Buffers 2904064 bytes
Recovery Manager terminado.
Enter the flash recovery area location:
I write this in my flash recovery area, where i have the backup files: D:\Respaldo.
In this path i have de following folders: D:\Respaldo\XE; Inside this folder i have other folders: ARCHIVELOG, AUTOBACKUP, BACKUPSET, ONLINELOG.
STEP 3 This is my problem:
MAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: fallo del comando startup en 08/31/2007 10:24:10
RMAN-04014: fallo al iniciar: ORA-01261: Parameter db_recovery_file_dest destina
tion string cannot be translated
ORA-01263: Name given for file destination directory is invalid
OSD-04018: No se ha podido acceder al directorio o dispositivo especificado.
O/S-Error: (OS 21) El dispositivo no est┐ listo.
Recovery Manager terminado.
==================== ERROR =============================
Restore of the database failed.
RMAN Error - See log for error .
Log file is at C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DATABASE\OX
E_RESTORE.LOG.
==================== ERROR =============================
Presione una tecla para continuar . . .
The OXE_RESTORE file show me this:
Recovery Manager : Release 10.2.0.1.0 - Production on Vie Ago 31 10:23:58 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Windows XP Version V5.1 Service Pack 2
CPU : 2 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1652M/2021M, Ph+PgF:3435M/3914M, VA:2003M/2047M
Starting with debugging turned off
conectado a la base de datos destino: xe (no montada)
RMAN> set echo on;
2> restore (spfile from autobackup db_recovery_file_dest='D:\Respaldo');
3> startup nomount force;
4> restore (controlfile from autobackup);
5> alter database mount;
6> configure controlfile autobackup off;
7> restore database;
8>
echo activado
Iniciando restore en 31/08/07
se utiliza el archivo de control de la base de datos destino en lugar del catálogo de recuperación
canal asignado: ORA_DISK_1
canal ORA_DISK_1: sid=37 devtype=DISK
destino del área de recuperación: D:\Respaldo
nombre de base de datos (o nombre único de base de datos) utilizado para la búsqueda: XE
canal ORA_DISK_1: se ha encontrado una copia de seguridad automática en el área de recuperación
canal ORA_DISK_1: se ha encontrado la copia de seguridad automática: D:\RESPALDO\XE\AUTOBACKUP\2007_08_27\O1_MF_S_631711029_3F5TQOVT_.BKP
canal ORA_DISK_1: restauración de SPFILE a partir de la copia de seguridad automática terminada
restore terminado en 31/08/07
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: fallo del comando startup en 08/31/2007 10:24:10
RMAN-04014: fallo al iniciar: ORA-01261: Parameter db_recovery_file_dest destination string cannot be translated
ORA-01263: Name given for file destination directory is invalid
OSD-04018: No se ha podido acceder al directorio o dispositivo especificado.
O/S-Error: (OS 21) El dispositivo no est¿ listo.
Recovery Manager terminado.
I really do not know what is my problem and how to solve it. I hope you guys can help me. I'm under a big pressure to solve this soon.
My Operating System is: WinXP Pro
I'm using APEX 2.01
When I create the backup I use ARCHIVELOG enable
Things i try:
1. Install fresh oracle XE database, and restore
2. Install fresh oracle XE database, enable archivelog and restore
3. Install fresh oracle XE database, enable archivelog, change path of DB_RECOVERY_FILE_DEST to 'D:\Respaldo'.
4. Install fresh oracle XE database, enable archivelog, change path of DB_RECOVERY_FILE_DEST to 'D:\Respaldo', and execute: @?/sqlplus/admin/movelogs;
5. Install fresh oracle XE database, enable archivelog, change path of DB_RECOVERY_FILE_DEST to 'D:\Respaldo';, and change DB_RECOVERY_FILE_DEST_SIZE to 20G;
NOTE: sorry for my english it is not my native language. and sorry for using a spanish version of the database.
Message was edited by:
Minning

Well,
After a lot of reading, i try this using rman:
SQL
1. SQL> connect xx/xx as sysdba
2. SQL> shutdown immediate
RMAN
1. RMAN> connect target XE
2. RMAN> startup nomount;
3. RMAN> restore spfile to 'C:\xe.ora' from 'D:\Respaldo\XE\AUTOBACKUP\2007_08_27\O
1_MF_S_631711029_3F5TQOVT_.BKP';
4. RMAN> alter database mount;
5. RMAN> restore database;
in point n°5 i have the following problem:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: fallo del comando restore en 09/06/2007 16:27:09
RMAN-06026: no se han encontrado algunos destinos - abortando la restauraci¾n
RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
e datos 4 para restaurar
RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
e datos 3 para restaurar
RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
e datos 2 para restaurar
RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
e datos 1 para restaurar
I try this command to find what's going on:
RMAN> list backup;
with this result:
Lista de Juegos de Copias de Seguridad
===================
Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
inalizaci¾n
15 Full 736.04M DISK 00:00:19 24/08/07
Clave BP: 15 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T12
4938
Nombre de Parte: E:\RESPALDO\XE\BACKUPSET\2007_08_24\O1_MF_NNNDF_TAG2007
0824T124938_3DY3143F_.BKP
Lista de Archivos de Datos en el juego de copias de seguridad 15
Tipo de Archivo LV SCN Pto. Ctrl. Hora de Punto de Control Nombre
1 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSTEM
.DBF
2 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\UNDO.D
BF
3 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSAUX
.DBF
4 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\USERS.
DBF
Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
inalizaci¾n
16 Full 6.83M DISK 00:00:01 24/08/07
Clave BP: 16 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T12
5005
Nombre de Parte: E:\RESPALDO\XE\AUTOBACKUP\2007_08_24\O1_MF_S_631457405_
3DY31Y0H_.BKP
Archivo de Control Incluido: SCN de Punto de Control: 2747446 Hora de Pun
to de Control: 24/08/07
SPFILE Incluido: Hora de Modificaci¾n: 24/08/07
Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
inalizaci¾n
17 Full 736.04M DISK 00:00:20 24/08/07
Clave BP: 17 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T17
0028
Nombre de Parte: E:\RESPALDO\XE\BACKUPSET\2007_08_24\O1_MF_NNNDF_TAG2007
0824T170028_3DYKQGTC_.BKP
Lista de Archivos de Datos en el juego de copias de seguridad 17
Tipo de Archivo LV SCN Pto. Ctrl. Hora de Punto de Control Nombre
1 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSTEM
.DBF
2 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\UNDO.D
BF
3 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSAUX
.DBF
4 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\USERS.
DBF
Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
inalizaci¾n
18 Full 6.83M DISK 00:00:02 24/08/07
Clave BP: 18 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T17
0054
Nombre de Parte: E:\RESPALDO\XE\AUTOBACKUP\2007_08_24\O1_MF_S_631472454_
3DYKR7OZ_.BKP
Archivo de Control Incluido: SCN de Punto de Control: 2773741 Hora de Pun
to de Control: 24/08/07
SPFILE Incluido: Hora de Modificaci¾n: 24/08/07
Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
inalizaci¾n
19 Full 740.95M DISK 00:00:20 27/08/07
Clave BP: 19 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070827T11
1642
Nombre de Parte: E:\RESPALDO\XE\BACKUPSET\2007_08_27\O1_MF_NNNDF_TAG2007
0827T111642_3F5TPWHN_.BKP
Lista de Archivos de Datos en el juego de copias de seguridad 19
Tipo de Archivo LV SCN Pto. Ctrl. Hora de Punto de Control Nombre
1 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\SYSTEM
.DBF
2 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\UNDO.D
BF
3 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\SYSAUX
.DBF
4 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\USERS.
DBF
Where it says 'Estado' (Status in english) I found this: 'EXPIRED', it seems that my 4 dbf files have some problem, right now i'm looking for a way to solve this, but with no luck.
I think i need a little help again...

Similar Messages

  • File name in msdb.dbo.backupset no longer matches the actual file name on the storage media. Error 3013 Restore Database is terminating abnormally.

    Thanks in advance for taking the time to read this and comment. Platform: Windows Server 2008 R2 Enterprise Edition SP1 (X64) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)Problem Description: The file name recorded in the msdb.dbo.backupset (sans the extension) no longer matches the actual file name written to the backup media which is
    in this case a NETAPP NAS storage share. Example:
    Mohave_backup_2014_03_14_233001_1158878.bak      (from NETAPP NAS filer)
    Mohave_backup_2014_03_16_233001_4167237             (from MSDB.dbo.backupset), as you can see, the last 7 digits (chars) of the file name are different, although the date and time are identical. The
    file names had previously been matching perfectly. The first occurance of this problem occured on 03/13/2014 at 5:00 AM MST. The error generated by the job was:
    Date  3/14/2014 10:29:23 AM
    Log  Job History (Refresh - Restore Mohave_93_DEV AD HOC)
    Step ID  1
    Server  OurDevServer
    Job Name  Refresh - Restore Mohave_93_DEV AD HOC
    Step Name  Restore Mohave_93_DEV
    Duration  00:00:01
    Sql Severity  0
    Sql Message ID  50000
    Operator Emailed  
    Operator Net sent  
    Operator Paged  
    Retries Attempted  0
    Message
    Executed as user: OurDomain\OurNetworkServiceLogin. Restore Mohave Prod to Mohave_93_DEV - ERROR: 3013 RESTORE DATABASE is terminating abnormally. [SQLSTATE 01000] (Message 50000).  The step succeeded.

    Olaf:
    Thanks for your reply. Sorry, my bad. I inadvertently copied wrong [name] form the msdb.dbo.backupset. On 3/13 and 3/14, the two file names did not match. In trying to select another example to show you this morning, I found that the names are now matching!
    What I was doing was to create dynamic t-sql to retrieve the latest prod backup of the database, and then restore it with move to the development server. This is an ad-hoc job that the developers can run by themselves whenever they require a refresh. Unfortunately,
    we only keep 3 days worth of backups for these databases, so the original disk file I was trying to use to restore no longer exists. Researching the original error, one of the error descriptions was that the restore could not find the file requested.
    I thought this very strange since I get the file name directly from the backupset table. Further research did indeed show that the file names were different, but unfortunately, I failed to save the details of the file names. Anyway, in looking for a new example
    to show you this morning, I have found that the file names are indeed matching exactly again. If this error pops up again, I will be sure to save all details and re-post.
    Thanks, regards and best wishes to you and yours, 

  • TS3694 I cannot update my iPhone 3g to iOS 4.2.1 because of iTunes error 1015 ;error during restoring of firmware mode.

    I cannot update my iPhone 3g to iOS 4.2.1 because of iTunes error 1015 ;error during restoring of firmware mode.

    Was you iPhone jailbroken?

  • Was updating iPad to iOS 5. Received unknown error during restore. Didn't sync. Appears to be wiped out. Can anyone help? Thanks!

    Was updating iPad to iOS 5. Got unknown error during restore. Now it appears to be wiped out. Screen just asks to be plugged into iTunes, which doesn't recognize thx iPad. Have rebooted both. Please help! Thanks.

    See if anything on this page helps : http://support.apple.com/kb/ht4097 - it covers update and restore problems

  • Error During restoring a database through RMAN in Oracle 9i

    Hi all,
    I have taken a full backup in oracle 9i through RMAN in one server(Solaris).
    After that moved that backupset to another server. Server Locations are same. I need to restore the backup in the new server.
    I am using pfile.
    Steps I followed:
    1. Using pfile i have started the db in nomount.
    2. Then restored the controlfile from backup and mounted the database.
    3. then tried to restore the database - I have to restore three of my datafiles to different location, hence i used "set new name "
    But RMAN threw an error while restoring.
    RMAN-00558:
    RMAN-01009:
    File not found.
    Can anyone help to resolve this error.
    Thanks in Advance.

    Hi,
    Thanks, but I took the backup of the database using the command:
    backup database;Only this command i issued.
    In the new server, I tried to list the backup using list backup command by putting the db in mount stage.
    I m not able to view the backup information.
    Is there any command to register the backup information using the catalog?
    -

  • Error while restoring database with different name on subscriber

    Hi all,
    I am using merge replication in sql server 2008R2. Yesterday I wanted to create a test environment, so
    I did:
    1. on publisher I restored from backup production db with another name ( lets call it TEST and new files
    .mdf, .ldf and no switch KEEP_REPLICATION). After this step original replication between production
    dbs worked fine.
    2. on subscriber I did the same: restore as new db TEST with new
    files .mdf, .ldf and no switch KEEP_REPLICATION.
    Unfortunately I noticed, that after second step replication stopped. SQL agent replication job on Subscriber
    is gone.
    Why restoring db with new name did affect original replication?
    Finally the most important: replication was set up by external company and I have to bring it to live now
    but I don't know this subject so good. How can I do it?
    Assuming, that there is no data change on subscriber in replicated tables is it enough when I select ‘reinitialize’
    on Publisher and Subscriber?
    Thanks in advance
    Artur

    Hello,
    Sorry for late response, but I was out of the office during last week.
    Regarding problem 1: restoring replication. I contacted guy who made originally our replication and he recreated subscription agent. So this is solved.
    problem 2: why did it happen?
    Lydia, in link which you provided I found only info about restoring db in replication, but I didn't want to restore replication.
    I checked SQL Server and Server Agent logs and there were no entries on that time. The only entries are regarding db restoring. Below:
    09/11/2014 12:45:59,Backup,Unknown,Database was restored: Database: Logik_ATData_TEST<c/> creation date(time): 2012/04/27(13:55:41)<c/> first LSN: 21392:66:267<c/> last LSN: 21392:227:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\MSSQLBackup\Dzienny\Logik_ATData_PROD\Logik_ATData_PROD_backup_2014_09_10_231001_6391536.bak'}). Informational message. No user action required.
    09/11/2014 12:45:59,Backup,Unknown,Restore is complete on database 'Logik_ATData_TEST'. The database is now available.
    09/11/2014 12:45:59,spid72,Unknown,CHECKDB for database 'Logik_ATData_TEST' finished without errors on 2012-04-26 22:50:05.490 (local time). This is an informational message only; no user action is required.
    09/11/2014 12:44:53,spid72,Unknown,Recovery is writing a checkpoint in database 'Logik_ATData_TEST' (13). This is an informational message only. No user action is required.
    09/11/2014 12:44:53,spid72,Unknown,Starting up database 'Logik_ATData_TEST'.
    09/11/2014 12:44:51,spid72,Unknown,The database 'Logik_ATData_TEST' is marked RESTORING and is in a state that does not allow recovery to be run.
    09/11/2014 12:44:51,spid72,Unknown,Starting up database 'Logik_ATData_TEST'.
    In Windows application log there were also no other entries, besides these above.
    I also could not check job history, because the job was gone in SSMS jobs list, while the subscription was present in SSMS Replication with info, that last successful synchronization was at 12:42 (there is a 5 min. sync period).
     I also don't understand how the job was deleted, because according this manual (http://www.mssqltips.com/sqlservertip/1803/auto-alert-for-sql-agent-jobs-when-they-are-enabled-or-disabled/) I have 2 triggers in sysjobs table and every time, when
    job is deleted/disabled I got @ notification. In this case I got no @.
    My SQL Server version:
    Product_Version Product_Level Edition
    10.50.2550.0 SP1 Standard Edition (64-bit)
    Any idea what happened?
    Thanks,
    Artur

  • Error during restore/recovery and 'open resetlogs'

    Hello forum. I'm attempting to restore a database to a new host and have run into an error during the opening of the database (with resetlogs). The renaming of the datafiles, restore, switching of datafiles, and recovery are all done by an rman script, the contents of which are below:
    # Restore production database to DR site using file system
    # instead of ASM
    run {
    set newname for datafile 1 to '/opt/oracle/product/10gR2/oradata/DB01/system.dbf';
    set newname for datafile 2 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf';
    set newname for datafile 3 to '/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf';
    set newname for datafile 4 to '/opt/oracle/product/10gR2/oradata/DB01/users.dbf';
    set newname for datafile 5 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf';
    set newname for datafile 6 to '/opt/oracle/product/10gR2/oradata/DB01/file1.dbf';
    set newname for datafile 7 to '/opt/oracle/product/10gR2/oradata/DB01/file2.dbf';
    restore database;
    switch datafile all;
    recover database;
    I get the following output:
    RMAN> @/home/oracle/scripts/rman_dr.rman
    RMAN> # Restore production database to DR site using file system
    2> # instead of ASM
    3> #
    4> run {
    5> set newname for datafile 1 to '/opt/oracle/product/10gR2/oradata/DB01/system.dbf';
    6> set newname for datafile 2 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf';
    7> set newname for datafile 3 to '/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf';
    8> set newname for datafile 4 to '/opt/oracle/product/10gR2/oradata/DB01/users.dbf';
    9> set newname for datafile 5 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf';
    10> set newname for datafile 6 to '/opt/oracle/product/10gR2/oradata/DB01/file1.dbf';
    11> set newname for datafile 7 to '/opt/oracle/product/10gR2/oradata/DB01/file2.dbf';
    12>
    13> restore database;
    14> switch datafile all;
    15> recover database;
    16> }
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 03-JAN-08
    Starting implicit crosscheck backup at 03-JAN-08
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 651 objects
    Finished implicit crosscheck backup at 03-JAN-08
    Starting implicit crosscheck copy at 03-JAN-08
    using channel ORA_DISK_1
    Crosschecked 1 objects
    Finished implicit crosscheck copy at 03-JAN-08
    searching for all files in the recovery area
    cataloging files...
    no files cataloged
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /opt/oracle/product/10gR2/oradata/DB01/system.dbf
    restoring datafile 00002 to /opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf
    restoring datafile 00003 to /opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf
    restoring datafile 00004 to /opt/oracle/product/10gR2/oradata/DB01/users.dbf
    restoring datafile 00005 to /opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf
    restoring datafile 00006 to /opt/oracle/product/10gR2/oradata/DB01/file1.dbf
    restoring datafile 00007 to /opt/oracle/product/10gR2/oradata/DB01/file2.dbfchannel ORA_DISK_1: reading from backup piece /ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642899284.1.1.bus
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642899284.1.1.bus tag=20080101_LV0_DB
    channel ORA_DISK_1: restore complete, elapsed time: 01:22:28
    Finished restore at 03-JAN-08
    datafile 1 switched to datafile copy
    input datafile copy recid=14 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/system.dbf
    datafile 2 switched to datafile copy
    input datafile copy recid=15 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf
    datafile 3 switched to datafile copy
    input datafile copy recid=16 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf
    datafile 4 switched to datafile copy
    input datafile copy recid=17 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/users.dbf
    datafile 5 switched to datafile copy
    input datafile copy recid=18 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf
    datafile 6 switched to datafile copy
    input datafile copy recid=19 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/file1.dbf
    datafile 7 switched to datafile copy
    input datafile copy recid=20 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/file2.dbf
    Starting recover at 03-JAN-08
    using channel ORA_DISK_1
    starting media recovery
    channel ORA_DISK_1: starting archive log restore to default destination
    channel ORA_DISK_1: restoring archive log
    archive log thread=2 sequence=1005
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=1365
    channel ORA_DISK_1: reading from backup piece /ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642900444.1.1.bus
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642900444.1.1.bus tag=20080101_LV0_DB
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
    archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_1_1365_3qtshnfv_.arc thread=1 sequence=1365
    archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_2_1005_3qtshncz_.arc thread=2 sequence=1005
    channel default: deleting archive log(s)
    archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_1_1365_3qtshnfv_.arc recid=2418 stamp=643049236
    unable to find archive log
    archive log thread=1 sequence=1366
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/03/2008 16:47:22
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 1366 lowscn 181804603
    RMAN> **end-of-file**
    I searched for a decription of the 06054 error, and found that if the archive logs weren't available, then to run "alter database open resetlogs;", which I did. Here's the output:
    RMAN> alter database open resetlogs;
    database opened
    RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
    RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
    ORACLE error from target database:
    ORA-06553: PLS-801: internal error [56319]
    I've done all of this twice now, with the same result. I've googled PLS-801 and found more than a few instances of people getting this code, but not during a database open after a restore. Can anyone shed some light on what might have gone wrong? In the interest of brevity, I left out the rest of the restore process prior to running the database restore, but other than setting "compatible" and "db_recovery_file_dest_size", it was all by the book.
    Thanks in advance.

    Thanks for the reply Pierre.
    I am not using RMAN Duplicate. Yes, the source of the backup is an RAC. The destination is a single server, with the DB on the filesystem. Here's an overview of of the commands I ran and the procedure.
    Copied tar'd backup controlfile and datafiles to destination machine. Untar'd. Install 10.2.0.1.0 on destination machine, patch to 10.2.0.2.0.
    OS> sqlplus /nologin
    SQL> alter system set compatible = '10.2.0.2.0' scope=spfile;
    SQL> alter system set db_recovery_dest_file_size = '8g'; scope spfile;
    SQL> shutdown immediate;
    SQL> startup; (to verify changes took...)
    SQL> shutdown immediate;
    OS> Copy control file from untar'd dir and place in $ORACLE_HOME/dbs/, truncate name to c-DBID-date-00.
    OS> rman target /
    RMAN> startup nomount;
    RMAN> set dbid <dbid from control file>;
    RMAN> restore controlfile from autobackup; (finds control file with no problem...)
    RMAN> alter database mount;
    RMAN> @/home/oracle/rman_dr.rman (script cited in first post, to rename datafiles from ASM to filesystem, restore, switch files, and recover...)
    RMAN> alter database open resetlogs; (as cited before...)
    If I'm not using Duplicate and not specifying dates, the UNTIL/SET UNTIL commands aren't necessary, correct?

  • Error to restoring database through rman

    Hi all,
    I am trying to restore database through rman its showing error. The error is
    RMAN> recover database;
    Starting recover at 13-APR-09
    using channel ORA_DISK_1
    starting media recovery
    unable to find archive log
    archive log thread=1 sequence=5
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 04/13/2009 13:00:44
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 5 lowscn 543566
    Please let me know how to resolved this error;
    Thanks in advance
    Noman

    There's no "full or partial" recovery in Oracle.
    There are :
    1. Database Recovery and Tablespace Point In Time Recovery (aka TSPITR)
    In the former case, it is the database that is recovered.
    In TSPITR, a Tablespace is recovered to an (older) point in time, different from the rest of the database. Since a database must be consistent, a TSPITR is done by using an Auxiliary Instance -- only SYSTEM, UNDO and the required Tablespace are recovered to their own consistent point in time and then the Tablespace data is copied and and plugged back into the Target Database.
    2. Complete Recovery and Incomplete Recovery
    Complete Recovery is right upto the current point in time -- ie upto the last transaction in the online redo logs.
    Incomplete Recovery is upto any point of before the current online redo log (a Timestamp, SCN or LogSequenceNumber) .
    The scenario we are talking of is an Incomplete Recovery -- because we do not have the Online Redo Logs.

  • Phone error during restore

    Hello,
    Today my phone got stuck on "Searching for Signal." After talking with Verizon, I decided to do a restore.  It took several tries to get it to go, and now it keeps getting an error 1669 during "Restoring iPhone firmware."  I haven't dropped it anytime recently and have an otterbox on it.

    Has your phone been jailbroken before you tried to restore? If yes, this is the cause for this error number.

  • Restore database Error when restoring database to a new server

    Hi folks,
    I am oracle 10g on an AIX server (5.3).
    I created an rman backup of a database. I then copied it over to a new server where I am trying to restore it (I just created the backup today). However, I am getting the error below.
    Essentially, I used an initdb.ora file to create an instance of the database, and mounted it, on the new server. And then I ran a simple "restore database" command, the end of which is displayed below, with a "Restore complete. ..."
    I have looked up this error (ora-01152) online and I cannot find a scenario which best provides me with a fix to my problem, about the file not being restored from a sufficiently old backup. Could any one help please?
    piece handle=/ora_backup/prev_0/qconfig/dbf/QCONFIG_18_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_4: restore complete, elapsed time: 00:03:30
    channel ORA_DISK_2: restored backup piece 1
    piece handle=/ora_backup/prev_0/qconfig/dbf/QCONFIG_15_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_2: restore complete, elapsed time: 00:05:00
    Finished restore at 14-JUN-10
    RMAN> alter database open resetlogs;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 06/14/2010 17:48:12
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '+DGROUP1/testdb/datafile/system.751.721679898'Edited by: efachim2 on Jun 15, 2010 2:19 AM

    I ran only as below because I copied over the backup right after it finished, when there were no archivelogs.
    RMAN> restore database;
    Starting restore at 14-JUN-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=651 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=650 devtype=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: sid=649 devtype=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: sid=648 devtype=DISK
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00002 to +DGROUP1/testdb/datafile/undots1.667.721227421
    channel ORA_DISK_1: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_16_1_721669501_2010_06_14_15:44_Mon_full
    channel ORA_DISK_2: starting datafile backupset restore
    channel ORA_DISK_2: specifying datafile(s) to restore from backup set
    restoring datafile 00007 to +DGROUP1/testdb/datafile/a1_x.641.721227553
    restoring datafile 00009 to +DGROUP1/testdb/datafile/ent_sm01_x.659.721227557
    restoring datafile 00013 to +DGROUP1/testdb/datafile/in01_x.657.721227569
    restoring datafile 00015 to +DGROUP1/testdb/datafile/cs01_x.656.721227571
    restoring datafile 00016 to +DGROUP1/testdb/datafile/cs01_d.650.721227559
    restoring datafile 00021 to +DGROUP1/testdb/datafile/h01_x.644.721227575
    restoring datafile 00023 to +DGROUP1/testdb/datafile/doc01_x.647.721227575
    restoring datafile 00025 to +DGROUP1/testdb/datafile/og01_x.645.721227577
    channel ORA_DISK_2: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_19_1_721669509_2010_06_14_15:44_Mon_full
    channel ORA_DISK_3: starting datafile backupset restore
    channel ORA_DISK_3: specifying datafile(s) to restore from backup set
    restoring datafile 00003 to +DGROUP1/testdb/datafile/sysaux.662.721227423
    restoring datafile 00006 to +DGROUP1/testdb/datafile/a01_d.639.721227549
    restoring datafile 00010 to +DGROUP1/testdb/datafile/ent_lg01_d.666.721227423
    restoring datafile 00012 to +DGROUP1/testdb/datafile/in01_d.658.721227511
    restoring datafile 00014 to +DGROUP1/testdb/datafile/cs01_d.661.721227521
    restoring datafile 00019 to +DGROUP1/testdb/datafile/ndata_x.654.721227423
    restoring datafile 00022 to +DGROUP1/testdb/datafile/doc_01_d.660.721227531
    restoring datafile 00029 to +DGROUP1/testdb/datafile/in01_x.642.721227471
    channel ORA_DISK_3: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_17_1_721669501_2010_06_14_15:44_Mon_full
    channel ORA_DISK_4: starting datafile backupset restore
    channel ORA_DISK_4: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to +DGROUP1/testdb/datafile/system.655.721227423
    restoring datafile 00004 to +DGROUP1/testdb/datafile/users.653.721227453
    restoring datafile 00005 to +DGROUP1/testdb/datafile/tools.663.721227423
    restoring datafile 00008 to +DGROUP1/testdb/datafile/en_sm01_d.665.721227473
    restoring datafile 00018 to +DGROUP1/testdb/datafile/n_data_d.664.721227423
    restoring datafile 00020 to +DGROUP1/testdb/datafile/hfig01_d.652.721227527
    restoring datafile 00024 to +DGROUP1/testdb/datafile/og01_d.651.721227535
    restoring datafile 00028 to +DGROUP1/testdb/datafile/in1_d.646.721227469
    channel ORA_DISK_4: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_18_1_721669501_2010_06_14_15:44_Mon_full
    channel ORA_DISK_2: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_19_1_721669509_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_2: restore complete, elapsed time: 00:00:27
    channel ORA_DISK_2: starting datafile backupset restore
    channel ORA_DISK_2: specifying datafile(s) to restore from backup set
    restoring datafile 00017 to +DGROUP1/testdb/datafile/cs_lg01_x.640.721227579
    restoring datafile 00026 to +DGROUP1/testdb/datafile/am1_d.643.721227581
    restoring datafile 00027 to +DGROUP1/testdb/datafile/am1_x.671.721227581
    channel ORA_DISK_2: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_20_1_721669624_2010_06_14_15:44_Mon_full
    channel ORA_DISK_2: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_20_1_721669624_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_2: restore complete, elapsed time: 00:00:07
    channel ORA_DISK_2: starting datafile backupset restore
    channel ORA_DISK_2: specifying datafile(s) to restore from backup set
    restoring datafile 00011 to +DGROUP1/testdb/datafile/ent_lg01_x.648.721227421
    channel ORA_DISK_2: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_15_1_721669501_2010_06_14_15:44_Mon_full
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_16_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_1: restore complete, elapsed time: 00:02:30
    channel ORA_DISK_3: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_17_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_3: restore complete, elapsed time: 00:03:15
    channel ORA_DISK_4: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_18_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_4: restore complete, elapsed time: 00:03:30
    channel ORA_DISK_2: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_15_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_2: restore complete, elapsed time: 00:05:00
    Finished restore at 14-JUN-10
    RMAN>  alter database open resetlogs;

  • ORA-01180 and ORA-01110 error when restoring database by RMAN in 11.1.0.6.0

    I have a new installed database running in ARCIHVELOG mode on SUSE 10SP3. Catalog is not used. When I try to restore the database from a level 0 backup based on SCN, ORA-01180 and ORA-01110 were raised out today. Please help me through this. Thx. The senario follows:
    1. I got the current SCN by "select dbms_flashback.get_system_change_number from dual". Say it's 12345;
    2. I did a level 0 hot backup with current control file, archived logs and parameter files. Everything went well;
    3. Some other DMLs are applied to the database;
    4. I want to do a SCN-based incomplete recovery for this database to SCN 12345. Then I
    1) shutdown immediate;
    2) startup nomount;
    3) restore the control file from backupset;
    5) startup mount;
    6) catalog start with "[backupset path]";
    7) restore database until scn 12345.
    Just at step 4.7, ORA-01180 and ORA-01110 were raised out, saying cannot create data file 1. Note: Backup files are existing and file permissions are all OK.
    Then I issues "list incarnation of database". There is just one record with incarnation id 1.
    So I queried v$log_history, found serveral record there. The most recent one has NEXT_SCN later than 12345, say 12400. Then I tried to restore database until this SCN. It WORKED! The restore and recovery succeeded.
    My questions are:
    1. Why cannot I restore the database to a previous SCN, say 12345, but 12400 is OK?.
    2. If the database was RESETLOG prior to my recovery, should I reset database to the incarnation where I took my backup? What can I do if there is no that incarnation information in my control file?
    Waiting for your suggestion.

    Hi guys. There is one update.
    This issue is caused by the incorrect SCN vs. backup set. I got this SCN before the backup started. According to Oracle docs, it's not allowed for an SCN based recovery.
    Now, I changed the sequence of my operations, so that SCN is got once backup is done, which is exact the "most recent sequence# and least SCN" mentioned by some thread in this forum. It works now.
    Anyone could explain why the SCN got prior to the level 0 backup is not recognized by restore/recovery phase? Thanks.

  • Errors during duplicating database.

    Hello,
    I'm duplicating my database (using RMAN) and I get the following error:
    contents of Memory Script:
    shutdown clone;
    startup clone nomount;
    executing Memory Script
    database dismounted
    Oracle instance shut down
    RMAN-00571(...)
    RMAN-04006:error from auxiliary database: ORA-12514: TNS: listener doesn not currently know of service requested in connect descriptor.
    It's 10.2 database on Linux. Auxiliary database is named 'aux'
    Tnsnames.ora and listener.ora seems to be ok, since I could connect to this instance (while it was in nomount state, before duplicating in RMAN) using
    sqlplus sys/***@aux as sysdba
    After I got the error I connected to aux using Bequeath, and checked it's status. It is shutdown since I got the error:
    ORA-01034: ORACLE not available.
    What can I do?
    Thx. in advance
    Aliq.

    On 9i, Oracle registers itself with the database when the database is opened.
    This means in any other state you need to use SID= in your tnsnames.ora.
    From your post it looks like this still applies to 10g.
    I would try changing my tnsnames.ora.
    You could of course, immediately after receiving the error, run lsnrctl services and check whether the service_name of the aux database is listed.
    Sybrand Bakker
    Senior Oracle DBA

  • Error during duplicate database.

    Hi All,
    db - 9.2.0.8.0
    OS - Win 2003 server
    I was rying to duplicate db on the same server. Please go through the following massage.
    printing stored script: Memory Script
       set until scn  14420521;
       recover
       clone database
        delete archivelog
    executing script: Memory Script
    Note, at this point my database was apperead to hang for long time. it was around 2 hour and then revert back with the following
    executing command: SET until clause
    Starting recover at 18-SEP-08
    starting media recovery
    archive log thread 1 sequence 7 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_7.ARC
    archive log thread 1 sequence 8 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_8.ARC
    archive log thread 1 sequence 9 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_9.ARC
    archive log thread 1 sequence 10 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_10.ARC
    archive log thread 1 sequence 11 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_11.ARC
    archive log thread 1 sequence 12 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_12.ARC
    archive log filename=D:\BCKUP\ARCHIVE\ARCH_7.ARC thread=1 sequence=7
    archive log filename=D:\BCKUP\ARCHIVE\ARCH_8.ARC thread=1 sequence=8
    archive log filename=D:\BCKUP\ARCHIVE\ARCH_9.ARC thread=1 sequence=9
    archive log filename=D:\BCKUP\ARCHIVE\ARCH_10.ARC thread=1 sequence=10
    archive log filename=D:\BCKUP\ARCHIVE\ARCH_11.ARC thread=1 sequence=11
    archive log filename=D:\BCKUP\ARCHIVE\ARCH_12.ARC thread=1 sequence=12
    media recovery complete
    Finished recover at 18-SEP-08
    printing stored script: Memory Script
       shutdown clone;
       startup clone nomount ;
    executing script: Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/18/2008 20:11:45
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current operation
    hare krishna
    Alok                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Alok do you have user that still active at auxiliary instance ,exit from that auxilairy session after doing database in nomount and then retry the duplicate process.
    Khurram

  • ORA-27067 Error while restoring database using RMAN

    Hi All,
    I am trying to restore the backups from my production database to an other server. I was able to restore the spfile and control files but at the step where I restore the datafiles I get the following error:
    RMAN-03002: failure of restore command at 11/03/2008 14:28:16
    ORA-19587: error occurred reading 0 bytes at block number 1
    ORA-27091: skgfqio: unable to queue I/O
    ORA-27067: skgfdisp: size of buffer is invalid
    The OS and the Oracle version on the source server (on which the backups were taken) and the target server (the backups being restored to) are the same. They both are running SUNOS 5.9 and Oracle 9.2. I
    Below are what were reported in the trace files:
    Unix process pid: 12359, image: oracle@ (TNS V1-V3)
    *** SESSION ID:(13.1) 2008-11-03 15:23:26.265
    *** 2008-11-03 15:23:26.275
    corrupt block 1 found during reading backup piece,file=/xxx/xxx/36jucqpe_1_1.bak, corr_type=1
    dump corrupted block
    2F11600 00020000 00000001 00000000 00000101 [................]
    2F11610 00000000 00000000 00000000 00000000 [................]
    Repeat 6 times
    *** 2008-11-03 16:19:29.778
    corrupt block 1 found during reading backup piece,file=/xxx/xxx/36jucqpe_1_1.bak, corr_type=1
    dump corrupted block
    3211C00 00020000 00000001 00000000 00000101 [................]
    3211C10 00000000 00000000 00000000 00000000 [................]
    Repeat 6 times
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 14
    Unix process pid: 12194, image: oracle@ (TNS V1-V3)
    *** SESSION ID:(11.3) 2008-11-03 14:09:42.986
    (blkno = 0x88, size = 276, max = 1, in-use = 1, last-recid= 0)
    (blkno = 0x89, size = 56, max = 145, in-use = 1, last-recid= 1)
    *** 2008-11-03 15:16:40.960
    *** SESSION ID:(13.1) 2008-11-03 15:16:40.951
    =====================
    PARSING IN CURSOR #2 len=68 dep=0 uid=0 oct=42 lid=0 tim=172140509128 hv=287842151 ad='35cd9364'
    alter session set events '10046 trace name context forever, level 8'
    END OF STMT
    EXEC #2:c=0,e=250,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=172140509103
    WAIT #2: nam='SQL*Net message to client' ela= 8 p1=1650815232 p2=1 p3=0
    *** 2008-11-03 15:17:18.666
    WAIT #2: nam='SQL*Net message from client' ela= 36822299 p1=1650815232 p2=1 p3=0
    =====================
    PARSE ERROR #2:len=50 dep=0 uid=0 oct=3 lid=0 tim=172177341974 err=1219
    select /*+ FULL(t) */ count(*) from sys.source$ t
    WAIT #2: nam='SQL*Net break/reset to client' ela= 61 p1=1650815232 p2=1 p3=0
    WAIT #2: nam='SQL*Net break/reset to client' ela= 279 p1=1650815232 p2=0 p3=0
    WAIT #2: nam='SQL*Net message to client' ela= 5 p1=1650815232 p2=1 p3=0
    Unix process pid: 12156, image: oracle@ (TNS V1-V3)
    *** SESSION ID:(11.3) 2008-11-03 14:09:08.687
    Archiving is disabled
    Archiving is disabled
    Can anyone help me resolve this error?
    Thanks,
    Ashok

    Hi,
    We finally got this issue resolved. I think the error was because the source database server was running 64 bit Oracle 9.2.0 and we installed a 32 bit Oracle 9.2.0 database on the target server. We then did a fresh install of 64 bit Oracle 9.2.0 database on the target server and the restoration worked. Also, after copying all the backup files to the target DB server, change the access rights of all those files and the folder containing them to 777.
    Thanks,
    Ashok

  • Facing error during Oracle Database Express Edition Installation

    Hi,
    I'm trying to install Oracle database XE on my system (Windows XP Service Pack 3) and keep getting an error "failed to load dll chkportdl2"" while trying to do so.
    While researching on a fix,I came across a solution that suggested uninstall of XP service pack 3 during installation and reinstall later.
    Now,I dont see an option for "Windows XP Service Pack 3" in "Add/Remove Programs".
    I believe Windows XP OBI comes up pre-loaded with Windows XP Service Pack 3 and am not sure if I can uninstall it.
    I looked up some other methods of removal here -
    http://www.troublefixers.com/uninstall-remove-windows-xp-service-pack-3-working-procedure/
    however,they werent very helpful either.
    Could you suggest how to fix this problem being faced in installing Database XE.
    Thanks and Regards,
    Priya Jetley

    Hi,
    I couldn't locate a chkportdll2 file either on my system.It's no regular dll you have on your system. It's usually unpacked in your temp directory when you execute the installer. The message you receive indicates that the installer either couldn't unpack properly (e.g. lack of free space), but this usually would have resulted in an error message. Or you have some Antivirus solution that treats that dll as malware (well, portscans can be bad) and has moved the file into a quarantine zone or at least blocked the access.
    Another option would be your user lacks execution privileges for network operations.
    The installer fails at the step when you specify a location to install the database.This could mean you don't have enough free (temp) space. How much space is left on the drive that hosts your temp folder?
    -Udo

Maybe you are looking for