Version parameter in impdp

I want import 11g dump file into 10g database
in version parameter i have to specify 11.1.0 or 10.2.0
thanks

You will need to perform expdp on the 11g database with VERSION set to 10.2.0, then perform the import on 10g.
http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_export.htm#autoId57
http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_overview.htm#CEGFCFFI
HTH
Srini

Similar Messages

Auto versioning parameter

Hi,
I am looking for the Auto Versioning parameter in KM as explaninged in the following help url, http://help.sap.com/saphelp_nw70/helpdata/EN/62/468698a8e611d5993600508b6b8b11/content.htm.
The postal version is EP7 SP16.
I would like to have this enabled in the documents CM repository manager.
Please tell me what I am doing wrong and why I can't see it.
Regards
Dries

Hi Dries,
I can believe that you are confused. I also feel like SAP should note this change at least in a SAP Note, Release Notes, and also update the sap.help.com documentation, but I was not able to find any notes regarding the change.
On the other side, checking through the source code and the other files, I can confirm that the parameter was only renamed, obviously to explain better what it is for.
If you look in the config_audit.0.log you can find the entry:
Property "Auto Check-In/Check-Out" ("autoversioning"): [VALUE NOT SET] -> "false"
Best regards,
Robert

Expdp - VERSION parameter value

In the 11g documentation about expdp, parameter VERSION description :
http://download.oracle.com/docs/cd/B28359_01/server.111/b28319/dp_export.htm#i1007148
+VERSION={COMPATIBLE | LATEST | version_string}+
The legal values for the VERSION parameter are as follows:
COMPATIBLE - This is the default value. The version of the metadata corresponds to the database compatibility level. Database compatibility must be set to 9.2 or higher.
LATEST - The version of the metadata corresponds to the database version.
version_string - A specific database version (for example, 11.1.0). In Oracle Database 11g, this value cannot be lower than *9.2*.
I'm a bit surprise how the version_string can be lower than 10.1 since expdp does not exists in previous Oracle version.
So, how could it be 9.2 ? Does this parameter being set according to the COMPATIBLE parameter of the target db instead of the version of the target db ?
Nicolas.

As stated in the documentation, The VERSION parameter simply allows you to identify the version of the objects being exported. This allows you to create a dump file set that is compatible with a previous release of Oracle Database. Again, as stated in the documentation, this does not mean that Data Pump Export can be used with versions of Oracle Database prior to Oracle Database 10g release 1 (10.1). Data Pump Export only works with Oracle Database 10g release 1 (10.1) or later.
The VERSION parameter can be useful in a downgrade situation, for example. Assume you have a 10.2 database and you export with VERSION=9.2. Only database objects and attributes that are compatible with 9.2 will be exported. You could then import the dump file into a 10.1 database whose compatibility is set to 9.2. A 10.1 database set to 9.2 compatibility could theoretically be downgraded to 9.2.
(Note that setting the compatibility to 9.2 in a 10.1 database means that any attempt to use a feature that is new in 10.1 will fail.)

Weblogic (WLS) / Oracle Forms & Reports (OFR) JRE lowest version parameter?

Hi,
Have WLS 11.3 and OFR 11.2 running within it.
I have adjusted the parameter via the GUI for the JRE. This was to specify what version the client's JRE was in order to run OFR, if it was X version or higher it would run.
I can not find this parameter now, can anyone point me in the right direction on this please
Thanks,
Steve

Hi,
Have WLS 11.3 and OFR 11.2 running within it.
I have adjusted the parameter via the GUI for the JRE. This was to specify what version the client's JRE was in order to run OFR, if it was X version or higher it would run.
I can not find this parameter now, can anyone point me in the right direction on this please
Thanks,
Steve

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.

IMPDP |Possible using Query option

HI PPL,
I wanted to Know whether IMPDP is possible using query option, as i have taken full expdp dump of the mentioned table and want to import only select rows.
impdp arup/arup directory=demo_dir dumpfile=employees.dmp
query=employees:\"where salary\>10000\ order by salary" tables=employees
version:10gR2
platform:UNIX
regards

Hello,
Yes you can use QUERY parameter with IMPDP.
But the syntax may be a little bit different than with the old IMP utility:
QUERY
Default: There is no default
Purpose
Allows you to specify a query clause that filters the data that gets imported.
Syntax and Description
QUERY=[[schema_name.]table_name:]query_clauseYou may have more examples on the following link:
http://download.oracle.com/docs/cd/E11882_01/server.112/e10701/dp_import.htm#BEHFGIGF
Hope this help.
Best regards,
Jean-Valentin

Exp imp issue from higher version to lower version

Hi,
I have an export dump file which was taken from 11g database(11.2.0.2.0) and trying to import into lower version of the database 9i(9.2.0.6.0), unable to complete the process.
Two ways i have found and tested in my test db
1)TNS entry of 9i database has been put into 11g database
a)Export dump was successfuly taken from 11g db
b)Getting below error,while import into 9i database
IMP-00058: ORACLE error 6550 encountered
ORA-06550: line 1, column 33:
PLS-00302: component 'SET_NO_OUTLINES' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignoredIMP-00000: Import terminated unsuccessfully
2)TNS entry of 11g database put into 9i database version.
a)During export (trying to take exp dump from 11g db in 9i exp utility),getting below error
EXP-00008: ORACLE error 1455 encountered
ORA-01455: converting column overflows integer datatype
EXP-00000: Export terminated unsuccessfully
Kindly advice me to overcome from this issue.
Regards,
Faiz

lkm_thedba wrote:
you can use VERSION parameter in datapump and make this workable.
Cheers,
lkmYou cannot, since 9.x does not use datapump. The VERSION parameter can only be used if the target is 10.x or above
http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_export.htm#autoId57
http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_overview.htm#CEGFCFFI
HTH
Srini

Trigger-Body isnt remaped during IMPDP and REMAP_SCHEMA in Oracle 10g

Hello,
we are facing the following problem:
During an IMPDP we are remaping the schema. The schema includes triggers. The trigger bodys are of normal syntax without a relation to the schema/user.
If we start the import with datapump using the remap_schema option the triggers are remap to the new schema. But the trigger bodys point to the old schema.
For example:
CREATE OR REPLACE TRIGGER "OLD_SCHEMA".NAME_OF_TRIGGER
BEFORE INSERT ON "OLD_SCHEMA"."TABLE_NAME" REFERENCING OLD AS OLD NEW AS NEW FOR EACH ROW BEGIN
END;
After using the REMAP_SCHEMA option:
CREATE OR REPLACE TRIGGER "NEW_SCHEMA".NAME_OF_TRIGGER
BEFORE INSERT ON "OLD_SCHEMA"."TABLE_NAME" REFERENCING OLD AS OLD NEW AS NEW FOR EACH ROW BEGIN
END;
So the Trigger Body in the NEW_SCHEMA uses a link to the OLD_SCHEMA and the trigger doesn't work. We wrote the trigger without referencing to a schema. So the OLD_SCHEMA resp. NEW_SCHEMA syntax must be added by datapump.
The question: Is there a way to remap the triggers correctly in the new schema or is this behavior "normal" to Oracle 10g Datapump?
We are using Oracle 10g Database 10.2.0.4 with the latest Patches on Windows Server 2003 SP2.
Thank you for you attention.

Hello,
I had the same problem and you can't fix it by changing a parameter of impdp. You really need to change the source of those triggers so they don't use hard-code schema references.
Solution would be to change the source code of those triggers. Or to use the "script" parameter of impdp and recreate the triggers yourself after the impdp has finished.
For more info check Metalink note: 750783.1
I hope this helps.
Regards,
Michiel.

Data Pump between differnt oracle versions

This is a follow on to the posting from yesterday. We have a customer database that is at 10.2.N, which we currently do not support. So they are planning on buying a new server and installing oracle at the supported version of 10.1.0.5. We are then planning on exporting the data from the 10.2 database using the schema option and then importing back into the 10.1.05 database
I thought I could use the data pump and specify the version parameter as 10.1.0.5 during the export, but according to the help that option/parameter is only valid for NETWORK_LINK and SQLFILE. I was not planning on using those options but just the default dmp file.
Am I better off just using the old export/import utilites. The schema owner has tables that contain lob elements so how does that work with SQLFILE?
Any advice is appreaciated!
thanks!

I don't think it is not supported:
C:\Documents and Settings\ATorelli>expdp system/xxxxx version=*10.1.0.1* schemas=pippo
Export: Release *10.2.0.4.0* - Production on Mercoledý, 29 Giugno, 2011 18:42:19
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connesso a: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Avvio di "SYSTEM"."SYS_EXPORT_SCHEMA_01": system/******** version=10.1.0.1 schemas=pippo
Stima in corso con il metodo BLOCKS...
Elaborazione dell'object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Stima totale con il metodo BLOCKS: 0 KB
Elaborazione dell'object type SCHEMA_EXPORT/USER
Elaborazione dell'object type SCHEMA_EXPORT/DEFAULT_ROLE
Elaborazione dell'object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Caricamento/Scaricamento della tabella principale "SYSTEM"."SYS_EXPORT_SCHEMA_01" completato
File di dump impostato per SYSTEM.SYS_EXPORT_SCHEMA_01 is:
C:\ORA\ATORELLI\APP\PRODUCT\ADMIN\MRMANREP\DPDUMP\EXPDAT.DMP
Job "SYSTEM"."SYS_EXPORT_SCHEMA_01" completato in 18:42:23
Regards

Oracle Parameter _FIX_CONTROL: EWA vs SAP Note Recommendation?

We have Oracle 11.2.0.2 on RedHat Linux
cat /$ORACLE_HOME/sapbundle/version.txt
SAP Bundle Patch 11.2.0.2.3 - 201108
For FIXCONTROL '6055658:OFF' what recommendation should I take the SAP Note or EWA?
1) SAP NOTE
In the SAP Note 1431798 "Oracle 11_2_0 Database Parameter Settings" ...
                May 12, 2011:
                added FIXCONTROL '6055658:OFF' for UNIX
                FIXCONTROL
                '6055658:OFF'    UNIX SBP 11201x_date ( date >= 201105 )
So the SAP Note looks like FIXCONTROL should contain '6055658:OFF'
2) EWA
Settings defined but not recommended
                6055658:OFF
Thanks in advance.

Hello Bill,
You should always check and go with the recommendation from the parameter note.
10g - 830576
11g -1431798
For the fixcontrol parameters, these were introduced to allow enabling and disabling of optimizer fixes . The corresponding patch therefore needs to be installed to enable you to you set the required parameter. With EWA, this report usually flags any parameter which may require further checking, (ie because a note exists that details behaviour of setting this parameter for example a performance behaviour in OLTP versus OLAP). EWA is doing this to ensure that the DBA is aware that there is some additional step, info regarding the parameter. The Colleagues above have already mentioned to run the parameter script which checks it's result against the Oracle version parameter note and flags any incorrect setting and also provides the setting that is recommended. Before you do this you should check the relevant parameter note for these recommendations.
Hope this helps
Best Regards
Rachel
Edited by: Rachel Holloway on Mar 4, 2012 2:18 PM

What To Do When Upgrading Version of The App

I' ve a BB App based on QNX. While upgrading version, BB World gave the following warning, although i' ve upgraded the version parameter in bar-descriptor.xml and in the name of bar file:
File bundle (udts_sistek-2_0_3_1.bar) has been rejected. Package ID is required for all .bar file. If this is an upgrade, Package ID must match Package ID in original file bundle.
Because of i haven' t got any keys which i used them to sign the previous release, i suppose that the only way is uploading new release as new application. Am i right?
In addition what do i need for the next upgrade? Is backup file ('Preferences > Signing' in Momentics Ide) enough?
PS : I' ve read the following tag which is not reply to my question.
http://supportforums.blackberry.com/t5/Adobe-AIR-Development/File-bundle-has-been-rejected-Package-I...

Apple supply Samsung, Hynix, Nanya and Micron (which is Crucial) as standard, so any of these should work as if supplied by Apple. Samsung ram usually has a lifetime warranty - but it is always possible to get a faulty chip from any manufacturer. Shop around and work out the cost/benefit of buying from a 3rd party. Sometimes it pays to upgrade from 512mb to a single 1gb from Apple, sometimes it's cheaper to buy 2gb elsewhere and factor in the resale value of the original chip.
The 1gb Samsung chip is M470T2953CZ3-CE6
Good luck.
PS - FYI this question has been answered hundreds of times already in this forum.

How to replace all objects while using IMPDP

I have exported a schema using EXPDP, now I am trying to import (IMPDP) that into another database as different schema, which already contains some of the objects (like tables, procedures, sequence etc). I using the option of REPLACE for TABLE_EXISTS_ACTION, but that doesn't replace if any existing procedures, sequences etc. Please let me know what option I should to replace every objects.
And also I am getting this error
ORA-39083: Object type JOB failed to create with error:
ORA-00001: unique constraint (SYS.I_JOB_JOB) violated
Failing sql is:
BEGIN SYS.DBMS_IJOB.SUBMIT( JOB=> 6, LUSER=> 'WILLIAMS_DESIGN', PUSER=> 'WILLIAMS_DESIGN', CUSER=> 'WILLIAMS_DESIGN', NEXT_DATE=> TO_DATE('2010-05-17 14:00:00', 'YYYY-MM-DD:HH24:MI:SS'), INTERVAL=> 'trunc(sysdate+1/24,''HH'')', BROKEN=> FALSE, WHAT=> 'ol_update_query_result_stats();', NLSENV=> 'NLS_LANGUAGE=''AMERICAN'' NLS_TERRITORY=''AMERICA'' NLS_CURRENCY=''$'' NLS_ISO_CURRENC
Job "WILLIAMS_CLEAN"."SYS_IMPORT_FULL_01" completed with 10678 error(s) a
Thanks

Hi,
There is no way to do what you want using datapump. Datapump does not have an 'OBJECT_EXISTS_ACTION = REPLACE'. All it has is the TABLE_EXISTS_ACTION. Can you get around this by dropping the schema? If not, then the only way I can think of is by using the sqlfile parameter on impdp.
sqlfile allows you to write all of the ddl that is going to be executed during a datapump job to a .sql file. You can then edit that file and either attempt a drop before the create or change the 'create' to 'create or replace'. Then run the .sql file.
You would then have to run the datapump import job with content=data_only to load the tables with their data.
Dean

Restricting powershell version in script

Stupid question probably, but just want to make sure.
Does Set-StrictMode -Version 2.0 actually prevent the script from processing functionality that exists in Powershell 3 or 4 or does it just implement "strictMode" rules that existed in version 2?
Thanks.

No.
If the objective is to make sure your script works in PS2, I recommend you test it in a system running PS2 (ONLY).
Set-StrictMode instructs the parser to not do a bunch of 'nice' things for us including:
If it comes across a variable that has not been initialized, it give it a value of zero instead of generating a terminating error.
If it comes across a reference to non-existing property, it returns $null instead of generating a terminating error
Now, these 'nice' things are nice and helpful most of the time. But sometimes they make debugging harder.
For example:
$VMName = 'VM1','VM2','VM3'
foreach ($VM in $VMName) {
"Processing '$VM'"
This returns output like:
Processing 'VM1'
Processing 'VM2'
Processing 'VM3'
Now, imagine that we made a typo like:
$VMName = 'VM1','VM2','VM3'
foreach ($VM in $VNName) {
"Processing '$VM'"
Can you spot the typo?
All we can see at first glance, is that we have no output, and NO ERROR message:
On second look you may notice $VMName has been misspelled in the foreach line.
However, if that was a several hundred line complex script block, you may spend hours or days trying to figure out why you're getting no output, while the error is simply a hard to spot typo.
The reason we got no error message is that PS did us a favor and ASSUMED we meant to declare $VNName as a new variable and assigned it an initial value of zero.
Now, Set-StrictMode can help debugging by giving out errors when the parser comes across things like uninitialized variables or reference to object properties that don't exist. In our example:
Set-StrictMode -Version 4
$VMName = 'VM1','VM2','VM3'
foreach ($VM in $VNName) {
"Processing '$VM'"
will return an error:
The morale of the story is that Set-StrictMode is a scoped debugging tool, not to enforce script backward compatibility.
I'll let you lookup the difference between the different values you can select with the -Version parameter of Set-StrictMode..
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx

Exporting schema from 11.1.0.7 to 10.2.0.4

I am working on Oracle Database version 11.1.0.7 on Solaris 10. I need to export a schema from this version and import into 10.2.0.4 version i Windows 2003.
So should I install 10.2.0.4 client on Solaris and run exp to create a 10.2.0.4 dump file.
Should I run any specific scripts before running 10.2.0.4 exp on 11.1.0.7 database?
IN case of datapump will using version parameter solve the issue like
expdp version=10.2.0.4
Let me know if I'm wrong and any other suggestions are welcome?

I the exp optons will take quite some time as I dont have 10g software installed on the machine and it is 40G export so by network it is going to take a while.
I think datapump verion=10.2.0.4 is something to consider here?
expdp system/..... schemas=hr directory=sample_dir dumpfile=hr.dmp logfile=hr.log version=10.2.0.4
is the previous command correct way of doing it ?
Once done while importing think so I dont need to do anything extra there
impdp system/.... directory=sample1_dir dumpfile=hr.dmp logfile=hr.log
Also should I run any scripts before doing expdp at source or impdp at target?

Error importing 11.2.0.1 export to 11.2.0.3

Hi all,
we have two machines. let's call them db_1 and db_2.
db_1 has version 11.2.0.1, db_2 is a clone of db_! and has been updated by our dba to 11.2.0.3.
Now I need move a schema with its data from db_1 to db_2.
I used datapump for creating the export using the following command:
expdp DIRECTORY=DATA_PUMP_DIR DUMPFILE=XY_11.2.0.1_20130110_1217.expdp LOGFILE=XY_11.2.0.1_20130110_1217.expdp.log SCHEMAS=XY
I can see no errors in the logfile.
The exp-Log says: Master-Tabelle "XY"."SYS_EXPORT_SCHEMA_01" erfolgreich geladen/entladen -> so, everything is fine.
Now I tried to import the dump to db_2 by using this command:
impdp LOGFILE=XY_11.2.0.1_20130110_1217.expdp.log REMAP_TABLESPACE='XY_PERM':'XYZ_PERM', REMAP_SCHEMA='XY':'XYZ' SCHEMAS='XY' DIRECTORY=DATA_PUMP_DIR DUMPFILE=XY_11.2.0.1_20130110_1217.expdp
I got the following errors (sorry, I only have German error messages):
Import: Release 11.2.0.3.0 - Production on Thu Jan 10 12:46:22 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Username: XYZ
Password:
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORA-39006: Interner Fehler
ORA-39068: Ungultige Master-Tabellendaten in Zeile mit PROCESS_ORDER=-4 -> now I got an error with the master table, which was fine in the export
ORA-01536: Speicherplatz-Zuteilung fur Tablespace 'XYZ_PERM' uberschritten
ORA-39097: Bei Data Pump-Job ist ein unerwarteter Fehler -1536 aufgetreten
Can anyone help?
Thanks in advance,
Andreas

I should have added that you are essentially downgrading so you need to tell Data Pump on 11.2.0.3 that you want to be able to import into 11.2.0.1. To do this, use the version parameter during the export command.
You could also do this over the network link (if you have one defined on the target pointing to the source). In this case, no version is necessary since the Data Pump code on the source will negotiate the version with the Data Pump code on the target.
Hope this helps.
Dean

Version parameter in impdp

Similar Messages

Maybe you are looking for