Link to home
Start Free TrialLog in
Avatar of tomerikv
tomerikv

asked on

Restore database from backup

Hi!

We might need to restore our database from backup. What I have discovered is that the backup has been made while the database has been open/running. (it was just filecopying of the whole server).

Does anyone have any idea or experience of the chances that this backup will work properly? (it is a 9i database)

Thanks in advance!

Best regards,

Tom-Erik

ASKER CERTIFIED SOLUTION
Avatar of Mark Geerlings
Mark Geerlings
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tomerikv
tomerikv

ASKER

Thanks!

I understand.

The database is quite large, so I also think there is no chance that the backup will work.

I also did a back with this command in DOS (this inn win 2000 server):

set ORACLE_HOME= F:\ora9ias
set ORACLE_SID=iasdb1
SET NLS_LANG = NORWEGIAN_NORWAY.WE8ISO8859P1

exp system/XXXXXX full=Y file=H:\database_bck\juli_infra_bck.dmp log=H:\database_bck\juli_infra_bck.log compress=Y grants=Y rows=Y

The problem is that when I try to import a .dmp file on my local database I get into two problems (depending on if I'm using IGNORE=Y or no).

If I don't use ignore I get:
object alreay exists (or something like that) and no data is imported in those objects/tables

If I use IGNORE=Y all the data are doubled, but as I understand this is solved if there are primary keys on every table. Else the data will be doubled?? I also got a weird error doing this on my local database:
colomn1 1kgepop: no error frame to pop to for error 21500

I import into the same database as I export from.

So I don't really trust this import either.

If you have a tip on what wrong with my import. please let me know!

Best regards,

Tom-Erik







Yes, if you do a full import into the same database the export was from, you will have the two problems you mentioned.  Normally a full import is not done into the same database that created the export.  A full import can be used to create a copy of a production database on a different server for test purposes for example.  Also, import can be used to just recover a particular table (or group of tables) if a table or tables were accidentally dropped or truncated.