Mushfique Khan
asked on
Moving DB using expdp/impd
Need to move data from one db to another, but have to use export/import (expdp/impdp), and selected schemas too, question is that what is the best possible way to make sure that I don't skip or missed anything at the source db.
Source: 11203 - AIX 6.1
Target: 11204 - AIX 6.1
Please assist/guide ... thanks in advance.
Source: 11203 - AIX 6.1
Target: 11204 - AIX 6.1
Please assist/guide ... thanks in advance.
ASKER
Can not do FULL=Y due to some configuration issues, moving from HSM to Oracle Wallet and just can't export/import SYS schema, means have to do it on schema basis.
Do advise, what the best options to avoid any misses, we do have FGAC (fine grained access control) implemented too + TDE (encryption), also what should be best possible way to copy PUBLIC synonyms too?
Do advise, what the best options to avoid any misses, we do have FGAC (fine grained access control) implemented too + TDE (encryption), also what should be best possible way to copy PUBLIC synonyms too?
Hi,
Other than import/export to move the DB schema, you also need to re-create DB user account/privileges.
Other than import/export to move the DB schema, you also need to re-create DB user account/privileges.
ASKER
Plan is to create a brand new db (11204) and then export/import into this new one, but not Oracle stuff, only application data/schemas.
Questions is how to make sure that ... we don't miss anything?
Questions is how to make sure that ... we don't miss anything?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes tablespaces will be identical as source, will import schemas one by one, complete, without stats, what I did on test db, while importing, monitoring the log file and if it raises any error, go and fix and and the import again, using TABLE_EXISTS_ACTION=REPLAC
Had encounter only issue and that was of PUBLIC synonym, at least 3/4 that was missed, rest was all good, but this was test, just would like to be more cautious for PROD, not to skip anything.
for the FGAC, will be using, while exporting:
INCLUDE=FGA_POLICY
INCLUDE=RLS_POLICY
this is the plan, do share, if you have any other/better idea.
And thanks a lot for all your assistance & guidance.
Had encounter only issue and that was of PUBLIC synonym, at least 3/4 that was missed, rest was all good, but this was test, just would like to be more cautious for PROD, not to skip anything.
for the FGAC, will be using, while exporting:
INCLUDE=FGA_POLICY
INCLUDE=RLS_POLICY
this is the plan, do share, if you have any other/better idea.
And thanks a lot for all your assistance & guidance.
Start with a FULL=Y and then remove what you don't want later in the target.
This will of course be slower and take up more space but is lowest risk.
If you're simply trying to move schemas, then just specify the schemas. That's what those options are for and they'll grab everything in them. If something goes wrong you should see an error in the logs.