Tag Info

New answers tagged

1

Probably best to: Import the entire CSV to a table using Import and Export Wizard. Run the query to pull the data you want from the table. Use the Import and Export Wizard to import to the other database. Clean up the CSV import, probably by truncating or deleting the table. Unless you want to use SSIS? Then you can design a package to do it easily ...


1

First, just to be certain we're covering our basis, this piece of code: EXP FILE = B.DMP OWNER(B) won't work. That's not a properly formatted EXP command. But assuming that you're using a properly formatted command, all that a user really needs is the EXP_FULL_DATABASE role, and they should be able to export any object in the database: SQL> create ...


0

Yeah, I found the solution. It is because my oracle database is located on another computer on the network. So, when I try to export to like 'c:\' directory, oracle is trying to export to its own C:\ directory not mine. I used network address of the folder as export directory and the problem was solved. Use for example \\OSMAN\dump_directory


1

Firstly, the oracle docs are VERY clear that you shouldn't use data pump as SYS: http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_export.htm#SUTIL824: Do not invoke Export as SYSDBA, except at the request of Oracle technical support The problem will almost certainly be permissions related. The user that is running the Oracle database is ...


1

check the file permissions because the export is done by oracle user whereas the directory belongs to osman user


1

Grant EXP_FULL_DATABASE privilege to user A and then export. SQL> grant EXP_FULL_DATABASE to A;


1

http://docs.oracle.com/cd/E11882_01/server.112/e22490/original_export.htm#SUTIL2641 If you do not have the system privileges contained in the EXP_FULL_DATABASE role, then you cannot export objects contained in another user's schema.



Top 50 recent answers are included