Export/Import Versions

hello Friends
Is it possible to import a table from a 10gr2 database into a 9i DB? both MS Windows 2003 server.
I tryed everything but just got erros.
- I exported from a 9i client and imported through a 9i client.
IMP-00010:
IMP-00000:
- From a 10g export and a 10g import too
IMP-00058:
ORA-06550:
PLS-00302:
ORA-06550:
tks for any help

There is a marvelous article on metalink.
Check metalink note 132904.1
but shortly:
Export the data with the Export utility of the lowest database version involved.
Import the data with the Import utility of the target database.

Similar Messages

How to import/export a version?

Hi,
how to import/export a version?

Not sure what you are asking here. If you are asking how to get data into DRM, then you are talking about the import process. If you are talking about how to get data out to other receiving systems, then you are talking the export process. Both of those processes are documented in the user help that comes with DRM.
If you are talking about an entire version, from say the PROD area to the DEV area, that process is dependent on what the database repository is stored in (ORACLE or SQL).

Exporting and Importing Versions

Hi,
I have created a new DEV system from the QA system. Now I want to export the version database from the exisitng DEV and import it to the new DEV. Any idea how to do it ?
regrads,
hasnain

We had the same problem years ago and could not solve it.
Rob

Datpump Export,Import across lower and higher versions

Versions involved : 10.2.0.4, 11.2.0.3
Operating System : AIX 6.1
+++++++++++++++++++++++++++++++++Lets say I export a schema in a 11.2 Database using 11.2 expdp .
Can I import the above dump (11.2) to a 10.2 Database using 10.2 impdp ?

Setting VERSION=10.2 worked fine for me.
Since I was curious, I tested taking a table level export dump from 11.2.0.3 Schema using 11.2.0.3 expdp without VERSION parameter. I succesfully managed to import those tables to a 10.2.0.2 schema needless to say using 10.2.0.2 impdp.
I don't know how this worked . Maybe export,importing from higher to lower version at schema level might fail. Need to test it when I have time.
This is contrary to Oracle documentation (11.2 DB Utilities guide)
Data Pump Import cannot read dump file sets created by a database release that is
newer than the current database release, unless those dump file sets were created
with the VERSION parameter set to the release of the target database. Therefore,
the best way to perform a downgrade is to perform your Data Pump export with
the VERSION parameter set to the release of the target database
But, anyway I am glad that Oracle's superior coding has enabled me to export,import from higher to lower version.

How to export/import Agenda different versions contacts .

I bought a MacBook Pro Os X version 10.8.2 with Agenda version 7.1 (1167) and I am trying to export contacs to a MacBook OS X version 10.7.4 with Agenda version 6.1.2 (1090).
Using standard procedure export/import menus does not work.
Any suggestions.
THANKS

I bought a MacBook Pro Os X version 10.8.2 with Agenda version 7.1 (1167) and I am trying to export contacs to a MacBook OS X version 10.7.4 with Agenda version 6.1.2 (1090).
Using standard procedure export/import menus does not work.
Any suggestions.
THANKS

Best choice for exporting / importing EUL

Hi all
I have been tasked with migrating an EUL from a R11 to a R12 environment. The Discoverer version on both environments is 10.1.2 and the OS is Solaris on oracle db's.
I am unfortunately not experienced with Discoverer and there seems to be no one available to assist for various reasons. So I have been reading the manual and forum posts and viewing metalink articles.
I tried exporting the entire eul via the wizard and then importing it to the new environment but i was not successfull and experienced the system hanging for many hours with a white screen and the log file just ended.
I assumed this was a memory problem or slow network issues causing this delay. Someone suggested I export import the EUL in pieces and this seemed to be effective but I got missing item warnings when trying to open reports. This piece meal approach also worried me regarding consistency.
So I decided to try do the full import on the server to try negate the first problem I experienced. Due to the clients security policies I am not able to open the source eul and send it to our dev. I was able to get it from their dev 11 system but I dismissed this as the dev reports were not working and the only reliable eul is the Prod one. I managed to get a prod eex file from a client resource but the upload to my server was extremely slow.
I asked the dba to assit with the third option of exporting a db dump of the eul_us and importing this into my r12 dev environment. I managed this but had to export the db file using sys which alleviated a priviledge problem when logging in, I have reports that run and my user can see the reports but there are reports that were not shared to sysadmin in the source enviroment are now prefixed with the version 11 user_id in my desktop and the user cannot see her reports only the sysadmin ones.
I refreshed the BA's using a shell script I made up which uses the java cmd with parameters.
After some re reading I tried selecting all the options in the validate menu and refreshing in the discover admin tool.
If I validate and refresh the BA using the admin tool I get the hanging screen and a lot of warnings that items are missing( so much for my java cmd refresh!) and now the report will not open and I see the substitute missing item dialogue boxes.
My question to the forum is which would be the best approach to migrate the entire eul from a R11 instance to a R12 instance in these circumstances?
Many thanks
Regards
Nick

Hi Srini
The os and db details are as follows:
Source:
eBus 11.5.2
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
SunOS 5.10 Generic_142900-11 sun4u sparc SUNW,Sun-Fire-V890
Target:
ebus 12.1.2
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production DEV12
SunOS 5.10 Generic_142900-11 sun4u sparc SUNW,Sun-Fire-V890
Yes the DBA initially did an exp for me using EUL_US as the owner but a strange thing happened with privileges and also, some of the imported tables appeared in the target environment under the apps schema(21 tables) even though the eul_us exp had been 48 tables.
I also had a problem on the db with "eul_us has insufficient privileges on table space discoverer" type errors.
I checked the eul_us db privileges and was unable to resolve this initial privilege error even though the privileges were granted to eul_us.
The dba managed to exp as system and then import it with the full=y flag in the import command which seems to bring in the privileges.
Then I ran the eul5_id.sql and then made up a list of the business areas and made a sh script to refresh the business areas as follows:
java -jar eulbuilder.jar -connect sysadmin/oracle1@dev -apps_user -apps_responsibility "System Administrator" -refresh_business_area "ABM Activities" -log refresh.log
This runs successfully and I can log in select business area and grant access to the users. The reports return data.
Then one of the users said she can't see all her reports. I noticed some if I opened desktop that were sitting there prefixed with a hash and her version 11 user id.
So back to the manuals and in the disco admin help the instructions are to first go to view > validate > select all options then go to the business area and click file refresh. This gives me a lot of warnings about items that are missing. I assume this is because the item identifiers brought across in the db dump are the version 11 ones and thus not found in the new system.
Any suggestions?
Many thanks
Nick

Upgrade from 8.1.6 to 9.2.0.7 via export/import

Has anyone done this or know if it's possible to simply build a 9.2.0.7 instance, then use export/import to perform the upgrade from 8.1.6 to 9.2.0.7 since a direct manual upgrade from 8.1.6 is not supported??
TIA

Yes, building a database in a new release and then exporting the existing database using its version of the exp utility, performing a binary copy of the exp file to the new server, and then running the new version imp utility using the transferred dmp file was the standard method of moving databases to new platforms/versions for many years. The same process could always be used on the same server between equal or from a current to a new release.
HTH -- Mark D Powell --

Client Copy Export/Import on large system. 1.5 TB

Hi,
We have a 3 tier landscape. DEV, TST, PRD.
Database size in PRD is 1.5 TB (1500 GB)
Our developers need fresh master and trans data in TST and DEV.
We are thinking about making a
PRD --> TST (1.5 TB) we do a system copy.
TST --> DEV (1.5 TB) we can't do a system copy. (Company policy says not to touch repository objects, version management what so ever in DEV....)
1. How long will a client export / import take from TST --> DEV, lets say we have "good HW" ? Will it work ?
2. I've read about TDMS but its toooo expensive.....is there maybe any 3 party tool that is good for this purpose ? Transfering 1.5 TB of data ...
Br,
Martin

Hi,
>1. How long will a client export / import take from TST --> DEV, lets say we have "good HW" ? Will it >work ?
In my opinion, a 1.5 TB database is much too big for a client copy.
It will work but may last a full week and would degrade the production system performance.
We have 1.3 TB databases and stopped using client copies since the system was 300 GB...
We only use database restores and renaming for system refresh even for the dev system.
There is procedure to keep the versionning of sources.
Regards,
Olivier

Export/Import Project still buggy in v2.1.3

After seeing the update notes for v2.1.3 and noticing references to project importing, I started to get excited that maybe the bugs have been ironed out. Unfortunately my longstanding bug still remains.
If anyone can think of any workarounds I'd be extremely grateful...
I have a 2.16GHz Intel Core Duo MacBook Pro with 2GB RAM, running OS X 10.5.6 and now Aperture 2.1.3
I have a project with many images, arranged into stacks, a pick in each stack with many adjustment and a 62-page book created from these picks. There are also some smart albums and a light-table.
Now I export the project (i.e. in the Project Inspector I right-click the project and choose Export > Project) to a file on the desktop and rename the existing project in Aperture. I now import the saved .approject file and I find that all my Picks are no longer Picks and my book is therefore no longer made up of my desired images. (I've tried this many times now and ruled out the possibility of a corrupt export file).
As a result, when I select the Book I get the "Non-Pick Images" dialog with the dreaded "One or more placed items are no longer the pick of a stack." message. "Use Current Pick" ruins the book - I have to go through and work out all the picks again (and also re-pan all the images within the Photo Boxes as this data has also been lost). "Create new Version" appears to preserve my book's original look, but my project now contains a couple of hundred more images than it used to and my other albums and light-table still have incorrect images shown as the Picks.
Does anybody have any ideas of what I can do to ensure the stack-picks are preserved during the export/import process?
(By the way, the reason I'm exporting and then re-importing is because I actually want to do the export from my laptop where the project is and then the import on my main work machine where the rest of my Aperture library lives, but that fails for the same reason, so I'm doing the export+import on my laptop for now to reduce the number of variables in the problem.)

I go with the assumption that you now know how to create transport sets. After having created a transport set containing the objects you want to be exported, go to the administer tab under the main page of portal. There you will find the Export/Import portlet. Here you need to choose your transport set from the first LOV and then click EDIT to choose the "Security Option". Now you export out the stuff. This will export all the user page customizations for you.
Thanks.

PC suite export/import breaks SMS messages

Nokia PC suite 6.85.14.1
Windows XP SP2
Phone 6500 classic connected either by Bluetooth or USB
just updated 6500c to 4.84 firmware
an sms message is received and is viewable fine in Inbox
using the phone I move it to Archive, it is still OK
I then export it to PC (drag-n-drop to a folder)
I delete the message in the phone and import (drag-n-drop) back to Archive
The message is there but it does not show sender name (instead I see the date in the header)
When I open the message and click message details, I can see that
To: field contains the actual sender, while Sender: has (no address)
I tried various things including messing with vmg content (putting same TEL: field to both VCARD entries), but on the import to 6500c, it is the same story - as if the import swaps the sender with receiver and clears the sender field
Please also note that at all times, when I view the messages in PC Suite (phone browser) they show correct sender field, I just need to see the same on the actual phone
Is there something I am missing?
Generally I just need to copy old sms messages from 7260, but when importing them they break as described above. I then tried to export a "6500" message and import it back - with same result. So it appears to be a PC Suite issue rather than anything

al_lea, thanks, I already thought about that, but as I said to exlucde any incompatibility issues within vmg I tried a export/import of a "native" sms freshly received on the 6500, and it gives the same problem.
I also tried changing versions to 3.0 manually in the vmg with no luck.
I'm starting to think the message is actually ok, but it's probably the 6500c software that doesn't display them right. When I try to reply to "broken" message, it does go to sender, even though he is not displayed as one
it looks like PC suite export or import strips the empty to: VCARD from inside the vmg, which is fine by the standards but 6500c doesnt like

Migrate Database- Export/Import

Hi,
I need to migrate an Oracle database 9i from Sun Solaris to Linux. The final target database version would be 11g.
Since this is a 9i database, I see that we have only option of export and database. We have around 15 schemas.
I have some queries related to it.
1. If I perform a export with full=y rows=y, Does it export Sys, System Schema objects also?
2. Can we perform export in Oracle 9i and use datapump import on targert 11g?
3. What is the ebst approach - a) to perform schema by schema export or b) to perform a full database export with exp / file=xxx.dmp log=xxxx.log full=y?
Since there is a database version different I dont want to touch sys, system schema objects.
Appreciate your thoughts.
Regards
Cherrish Vaidiyan

Hi,
Let me try to answer some of these questions you queried for:
1. If I perform a export with full=y rows=y, Does it export Sys, System Schema objects also?Export won't export sys objects. For example, there are tables in sys, like obj$ that contain information for other metadata objects, like scott.emp, etc. This is not exported becuase when scott.emp is exported, the data from obj$ is essentially exported that way. When the dumpfile is imported and scott.emp is recreated, the data in sys.obj$ will be restored through the create table statement. As far as the SYSTEM schema is concerned, some objects are exported and some are not. There are tables in system that contain information about queues, jobs, etc. These will probably not make any sense on the target system so those types of tables are excluded from the export job. Other objects make sense to export/import so those are done. This is all figured out in the internals of export/import. Thre are other schemas that are not exproted. Some that I can think of are DMSYS, ORDSYS, etc. This would be for the same reason as SYS.
2. Can we perform export in Oracle 9i and use datapump import on targert 11g?No, the dumpfiles are formatted differently. If you use exp, then you must use imp. If you use expdp, then you must use impdp. You can do exp on 9i and imp on 11g with the dumfile that was created on 9i.
3. What is the ebst approach - a) to perform schema by schema export or b) to perform a full database export with exp / file=xxx.dmp log=xxxx.log full=y?This is case by case decision. It depends on what you want. If you want the complete database moved, then I would personally think that a full=y is what you would want to do. If you just did schema exports, then you would never export the tablespaces. This would mean that you would have to create the tablespaces on the source system before you ran imp. There are other objects that are not exported when a schema level export is performed that are exproted when a full is performed. This information can be seen in the utilities guide. Look to see what is exported when in user/schema mode vs full/database mode.
Since there is a database version different I dont want to touch sys, system schema objects.This is all done for you with the internal workings of exp/imp.
Dean
Edited by: Dean Gagne on Jul 29, 2009 8:38 AM

Export Import to Maintain Test and Production Environments

We have developed an application using Locally built Database Providers in Oracle Portal 9.0.2.6 which is installed to 2 schemas, has 5 different providers, and over 100 Portal major components (Forms, Reports, and Calendars) and over 200 minor components (LOV's and Links). We have used export/import transport sets with some luck, but it is a struggle becuase the import procedures are not very robust. Many things (such as missing LOV's, corrupt components, preexisting versions, etc, etc.) can cause an import to fail. And the cleanup necessary to finally achieve a successful import can be very time-consuming.
Having a robust import mechanism is very important to our strategy for keeping installed (our own and clients') portal instances up-to-date with our latest release. Some of the enhancements that would make it much easier to develop and maintain Portal applications include:
Within the Portal:
1. Ability to copy an entire provider within the same portal (rather than one component at a time).
2. Ability to change the schema to which a Provider is associated.
3. When copying a component from one provider to another, the dependent items (i.e. LOVs and Links) should be copied to new second provider as well. (i.e. rather rebuilding each LOV in each provider and then editing each form to point to the new LOVs)
Transport Sets:
4. Should allow for changing provider names and provider schema, and global component name changes, and resetting unqiue id's on import (to create copy rather than overwrite).
5. Should allow the option to ignore errors and import all components which pass pre-check (rather than failing all components if all items do not pass pre-check).
How are other Portal Developers dealing with installing and then rolling out new sets of Locally built Database Providers from Development environments to Production? Are there any whitepapers on the best practices for replicating/installing a portal application to a new portal instance and then keeping it updated?
Oracle, are any of my wish-list items above on the future enhancement lists? Or have others figured out workarounds?
Thanks,
Trenton

There are a couple of references which can be found on Portalstudio.oracle.com that are of some use:
1. A FAQ for Portal 9.0.2.6 Export/Import http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/OTN_CONTENT/MAINPAGE/DEPLOY_PERFORM/9026_EXPORT_IMPORT_FAQ_0308.HTM
2. Migration Instructions by Larry Boussard (BRUSARDL)
3. Migrating Oracle Portal from Dev Systems to Production Systems bt Dheeraj Kataria.
These are all useful documents for a successful first-time Export-Import. However, the limitations and lack of robustness I listed in my first post, make the process so time-consuming and error fraught as to not be a practical development strategy.

Export/Import in Oracle8i to Oracle10g

Hi,
We have an Oracle8i Enterprise Edition Release 8.1.6.0.0(32 Bit) running on AIX4.3.3,we are planning to upgrade/migrate it to[b] Oracle10g running on AIX5.3.If i do an export from oracle8i whether i can import it in Oracle 10g without any issues.
Regards,
Cherry

Dear All,
Thanks for your efforts.
I have solved this problem and running the db in windows 2000 server without any problem.
Solution:
A tablespace should be created in the same name, size as in the solaris server. we cant transfer a tablespace created by solaris to windows. Before importing the data we need to create a tablespace and assign to the user (empuser).
here is the method that works for me.
1.GENERAL STEPS TO FOLLOW:
WINDOWS 2000 Server:
Install Oracle 9i release 1 (9.0.1.1.1) in windows 2000 server.
Create a database with following parameters;
1. Select 'General Database'
2. Global Database Name: EMP
3. SID: EMP
4. All default Options and click finish to create and start the oracle instance.
5. Login to SQL-PLUS (username: scott, Password: tiger, Hoststring: <empty>)
6. Connect as sys/change_on_install as sysdba;
7. CREATE TABLESPACE empdeploy DATAFILE 'C:\oracle\oradata\EMP\emp_data_new.dbf' SIZE 1000m AUTOEXTEND ON NEXT 100m MAXSIZE 2048m EXTENT MANAGEMENT LOCAL;
8. CREATE USER empuser IDENTIFIED BY emppass DEFAULT TABLESPACE EMPDEPLOY TEMPORARY TABLESPACE TEMP;
9. GRANT DBA TO EMPUSER (Im not sure whether i given this command or not, dont use this unless u get error during import)
10. disconnect
References:
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_8003.htm
http://www.adp-gmbh.ch/ora/sql/create_tablespace.html
SUN-SOLARIS 5.6 (SPARC):
It is running Oracle Enterprise edition 8.1.6.
Get the informations below,
INSTANCE NAME
SID
USER HAVING CONTROL TO THAT INSTANCE (like here it was EMPUSER)
TABLESPACES USED
TABLESPACE NAME
DATAFILE NAME and PATH
ORACLE VERSION
2.EXPORT/IMPORT PROCEDURE:
I) Exporting Database from SOLARIS SERVER:
option-1:
exp empuser/emppass
leave all default options
Select Entire database to export (option 1)
YOU SHOULD GET 'Export terminated successfully without warnings'. (Failure causes may be low disk space, ensure that u have enough disk space)
Option-2:
exp empuser/emppass
leave all default options
Enter the user name whose tables to be exported: EMPUSER
Enter the user name whose tables to be exported: <Enter-to-quit>
YOU SHOULD GET 'Export terminated successfully without warnings'.
Option-3:
exp TRIGGERS=y CONSTRAINTS=y GRANTS=y FILE=expdat.dmp
Username: EMPUSER as sysdba
Password: emppass
leave all default options
Select Entire database to export (option 1)
YOU SHOULD GET 'Export terminated successfully without warnings'.
Option-4 (99% wont Work, RISKY):
EXPORT THE TRANSPORTABLE TABLE SPACE (This is different from exporting tables/data, so if all the above fails then export the Transportable table space and import into windows probably it will fail due to platform issue and CHARACTER SET Conversion)
Now import the expdat.dmp file again and see.
Change the required TABLESPACES READ ONLY.
exp TRANSPORT_TABLESPACE=y TABLESPACES=PMTDEPLOY TRIGGERS=y CONSTRAINTS=y GRANTS=y FILE=expdat.dmp
Username: EMPUSER as sysdba
Password: emppass
YOU SHOULD GET 'Export terminated successfully without warnings'.
Now Again Change the TABLESPACES to READ WRITE. (If you forgot this production server cant able to write to the database, the database will be left in read-only mode.)
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
II) TRANSFERRING EXPORTED DATA FROM SOLARIS TO WINDOWS 2000 Server.
Now from windows system,
Open command prompt.
connect to SOLARIS SERVER USING FTP.
( cd /user1/home/oracle)change to the Path where you have exported the expdat.dmp file.
set the transfer mode to binary (dont use the default ASCII Transfer Mode)
get expdat.dmp
close
quit
Now the database was successfully exported from solaris and transferred to Windows 2000 server.
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
III) Importing the Database in Windows 2000 server:
Open a Command prompt,
imp FULL=y IGNORE=n
Enter User Name : empuser
Password : emppass
You should get the same messages what you got during export, with out any other warnings or big messages running in the screen.
After completion you will get,
'Import terminated successfully without warnings'.
+++++++++Now Login thru SQLPLUS using username: empuser, password: emppass++++++++++
#the following query should return the total number of tables (142 here), this should be same as what you get in solaris. If you get 'no rows selected' then the import was failed, may be take a look at creating tablespaces, or around tablespaces)
select * from tab;
142 rows selected.
A kind request:
if you got your problem solved, please update the forum / usergroup and write how you solved the problem. this might be helpful for others who may face the same trouble. for me also there was some old postings that having similar problem. but they haven't given the solution. after their problem solved just left this forums.
Thanks & Regards,
Sakthivel

Export - Import in Oracle Application Database

The export in Oracle Applications Database works fine.
But the import always show some issue and sometimes never completes.
Even if it completes it complete with error , how to ensure an error free export/import ?
How to handle a table movement if the table consists of a LONG column ?

The errors are cannot import this tables..
Also mostly are of Long tables..Any IMP-XXXXX or ORA-XXXXX messages?
Can you explain how long objects are exported and imported ?What type of objects?
What is the database version?
Are you doing a full database import?
Also sometimes import hangs for 2/3 days?Does it hang when importing a specific object?
Did you follow the steps outlined in the following notes when you did the Export/Import?
Note: 362205.1 - 10g Release 2 Export/Import Process for Oracle Applications Release 11i
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=362205.1
Note: 230627.1 - 9i Export/Import Process for Oracle Applications Release 11i
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=230627.1

Export/import in 904 versus 10.1.2

We have two 10G AS 904 installs (dev and prod - same O/S too). From time to time we move our production portal content to the dev server. We sometimes get corruption and have to use the Schema validation Utility scripts to fix the import to the dev server. Not a show stopper but this adds another manual step to the process.
I see the 10.1.2 version has improved import/export checks. Can anyone give feedback on the improvements in the export/import process?
Thanks
Kevin

Kevin,
Careful with this approach. Passing from DEV to PROD is ok, but then to DEV back again, what I suggest you is that you have a clean start on DEV, ie, clean the DEV machine and later do the same to the PROD. Portal Export / Import works only in one-way and not both ways (this basically has to do with the checks we do make and with possible conflicts with the objects on both sides). Also check the available documentation... which is all compiled in Metalink Note:263995.1 - Master Note for OracleAS Portal Export / Import Issues
As to the improvement of the process, please give it a check on the New Features papers (make a find on "export" - it is easier to pick the references):-
10.1.2 -- http://www.oracle.com/technology/products/ias/pdf/1012_nf_paper.pdf
10.1.4 -- http://www.oracle.com/technology/products/ias/portal/pdf/portal_1014_new_features.pdf
I hope it helps...
Cheers,
Pedro.

Export/Import Versions

Similar Messages

Maybe you are looking for