I want to export a table 'ACCOUNTS on a daily basis, with export dump file name ACCOUNTS_ddmmyyyy.dmp. I may need to re-import this table at a later date so that I can compare balances between any two days.
At the moment, when I do the import I need to import the table into a different schema as I dont want to overwrite the live ACCOUNTS table.
(The import tries to 'CREATE TABLE ACCOUNTS')
I would like to import the table into the same schema with table name
Is there any option that I can specify at the export stage that can, in effect, rename the table to the same name as the dump file?
Thanks for the swift replies.
DaPi, I had used a method similar to yours to get around the problem.
ie import ACCOUNTS to different schema, create ACCOUNTS_ddmmyy in my schema as select from different schema.
ACCOUNTS is very large table so I was just trying to see I could find a quicker way of doing things.
to a different schema obviously you can do it but under same schema impossible, even you change your create table statement in the dump file are you gonna change all INSERT statements in the dump risking of corrupting the dump file? guess not
"great minds . . " Looks like your decison has to be when to spend the extra time (you need the extra disk space no matter what).
Taking extra time after the import minimizes the total time lost (since you do this rarely) BUT it's when the **** hits the fan that you need to act fast, so there might be an argument to make the export job "slow" to enable you to do an import at top speed.
"The power of instruction is seldom of much efficacy except in those happy dispositions where it is almost superfluous" - Gibbon, quoted by R.P.Feynman