Export import mandotary patches

hi,
there is a note on metalink :Oracle Support Master Note for Portal Export/Import.
Doc ID: Note:263995.1
it says that there are mandotary patches required for a successfull export - import.
For example:
10.1.2.0.2 (**)
Patch:5064459 : EXPORT/IMPORT CONSOLIDATED PATCH FOR 10.1.2.0.2 - VERSION 1
Note:
To install the Export/Import patch you need to install the latest version of opatch released with Patch:2617419.
Latest opatch version is 1.0.0.0.55. It was re-released on April 25, 2006.
10.1.2.0.1 (*) (**)
There are no patches available for this release.
10.1.2.0.0 (*) (**)
Patch:4405137 : EXPORT/IMPORT CONSOLIDATED PATCH FOR 10.1.2.0 - VERSION 1
Note:
To install the Export/Import patch you need to install the latest version of opatch released with Patch:2617419.
Latest opatch version is 1.0.0.0.55. It was re-released on April 25, 2006.
i didnt understand that.
my question is do i have to apply these patches to make a successfull export-import between the same version.
assume that i have exactly the same version 10.2.0.0.0 is it mandatory then?

i cant beleive that no one has done a export or import on version 10.1.2.0.0
i am just asking if you have to apply the patch for export between same version (10.1.2.0.0)
please share your experiences about this issue!

Similar Messages

Can i do client export import between systems with different patch levels

we want to do a client export import between two systems. As I understand the patch levels should be the same in both for this to happen..
But right now I am in a situation where time is a big constrant. The basis patch level is on par. But the rest are not. Can I do client import successfully at this stage.

The only thing that may stop it working could be additional functionality between the systems.
I work on XI and there is a huge difference between SP12 and SP15. We were able to do the transports between systems, but as Dev was patched before QA, and the transport was reliant on standard settings not being available, it still went though, but we had to transport it again after applying SP15 to QA.
Again, it probably depends on what System you have running on Netweaver...

System copy using SAPInst(Export Import database Independent prcoess failed

Hello ,
I am doing a System copy using SAPInst export/import process .
Source system : SAP Netweaver'04( BW 3.5 , Kernel : UC 640 ,Patch level 196 )
Export process fails at Phase 2 - Database Export at R3load jobs running 1,waiting 0 . Below is the log details
SAPSDIC.log
(EXP) INFO: entry for BAPICONTEN                        in DDNTT is newer than in DDNTT_CONV_UC: 20040211101817 > 20000621155733
(EXP) INFO: entry for BAPICONTENT255                    in DDNTT is newer than in DDNTT_CONV_UC: 20040211101817 > 20031127161249
(EXP) INFO: entry for BAPICONVRS                        in DDNTT is newer than in DDNTT_CONV_UC: 20040211101817 > 20010131174038
(EXP) INFO: entry for BAPICREATORDATA                   in DDNTT is newer than in DDNTT_CONV_UC: 20040211101817 > 20000621155733
(EXP) INFO: entry for BAPICRMDH1                        in DDNTT is newer than in DDNTT_CONV_UC: 20051229175654 > 20031211120714
(EXP) INFO: entry for BAPICRMDH2                        in DDNTT is newer than in DDNTT_CONV_UC: 20051229175654 > 20031211120714
(EXP) INFO: entry for BAPICRMEXP                        in DDNTT is newer than in DDNTT_CONV_UC: 20051229175513 > 20031211120627
(EXP) INFO: entry for BAPICRMEXT                        in DDNTT is newer than in DDNTT_CONV_UC: 20051229175514 > 20031211120627
(EXP) INFO: entry for BAPICRMKEY                        in DDNTT is newer than in DDNTT_CONV_UC: 20051229175654 > 20031211120714
(EXP) INFO: entry for BAPICRMKEY_T                      in DDNTT is newer than in DDNTT_CONV_UC: 20051229175835 > 20031211120803
(EXP) INFO: entry for BAPICRMMSG                        in DDNTT is newer than in DDNTT_CONV_UC: 20051229175654 > 20031211120714
(EXP) INFO: entry for BAPICRMMSG_T                      in DDNTT is newer than in DDNTT_CONV_UC: 20051229175835 > 20031211120803
(EXP) INFO: entry for BAPICRMOBJ                        in DDNTT is newer than in DDNTT_CONV_UC: 20051229175514 > 20031211120628
(EXP) INFO: entry for BAPICRMPAREX_T                    in DDNTT is newer than in DDNTT_CONV_UC: 20051229175452 > 20031211120305
(EXP) INFO: limit reached, 5000 tables in DDNTT are newer than in DDNTT_CONV_UC
(EXP) INFO: NameTab check finished. Result=2 #20100113131216
(EXP) INFO: check for inactive NameTab entries: Ok.
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(DB) INFO: disconnected from DB
D:\usr\sap\B35\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\B35\SYS\exe\run/R3load.exe: END OF LOG: 20100113131216
***SAPCLUST.log ****
(NT) Warn: EDIDOC: normal NameTab from 20040211095029 younger than alternate NameTab from 20000621155733!
(EXP) TABLE: "EDIDOC"
(NT) Warn: PCDCLS: normal NameTab from 20040211095029 younger than alternate NameTab from 20000621155733!
(EXP) TABLE: "PCDCLS"
(NT) Warn: SFHOA: normal NameTab from 20040211095029 younger than alternate NameTab from 20000621155733!
(EXP) TABLE: "SFHOA"
(NT) Warn: SFHYT: normal NameTab from 20040211095029 younger than alternate NameTab from 20000621155733!
(EXP) TABLE: "SFHYT"
(NT) Warn: UMG_TEST_C: normal NameTab from 20040211095029 younger than alternate NameTab from 20031113150115!
(EXP) TABLE: "UMG_TEST_C"
myCluster (55.22.Exp): 712: error when retrieving alternate nametab description for physical table UMG_TEST_F.
myCluster (55.22.Exp): 713: return code received from nametab is 32
myCluster (55.22.Exp): 299: error when retrieving physical nametab for table UMG_TEST_F.
(CNV) ERROR: data conversion failed. rc = 2
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(DB) INFO: disconnected from DB
D:\usr\sap\B35\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\B35\SYS\exe\run/R3load.exe: END OF LOG: 2010011312563
Please suggest.
Thanks & Regards
Ganesh

Is your DB unicode? If so, did you select the unicode flag in sapinst?
This [thread|System Copy Error while exporting ABAP; might offer some help.
-Zach

Unit Tester: Bug in Export/Import of Suites

I was moving my Unit Test repository from one schema to another, so I first exported all of my suites and then imported them into a new repository.
But, when I imported them into their new repository, all of the tests forgot what specific function/procedure name within a package they were actually calling. For example, the test that used to be for "pccdb.rotat_maintenance.parseRotatKey", now says it's going to call "pccdb.rotat" (i.e. the specific function name it's supposed to be calling within that package disappeared).
I went looking and found that in the UT_TEST table, the "object_call" column was null for all of my tests, but because all of my tests call methods within packages, I'm thinking that column shouldn't be NULL. So, I filled in the appropriate function name for one of them, and the test started working....
So, something in the import or export of unit suites (or their tests) isn't working quite right in populating the ut_tests.object_call column, I'm guessing - please take a look at it.

This was originally reported in SQL Developer 2.1: Problem exporting and importing unit tests thread. It was logged as
Bug 9236694 - 2.1: OTN: UT_TEST.OBJECT_CALL COLUMN NOT EXPORTED/IMPORTED
It has been fixed and will be available in the next patch release.
Brian Jeffries
SQL Developer Team

OWB - issue in export import

hi,
When i do an export – import from one OWB repository to another of an OWB mapping having a MERGE statement some of the columns are missing in the MERGE. I am using OWB 10g R2.
Eg: if the MERGE is based on columns c1, c2, c3 after the export-import the mapping to a different environment the imported mapping is having the MERGE based on only c1
Thanks

There is Bug 5705198: LOADING PROPERTIES CHANGED AFTER MDL EXPORT/IMPORT (fixed in 10.2.0.4 OWB patchset), similar problem with lost MATCH COLUMN WHEN UPDATING ROW property during MDL import.
Maybe it is your case.
There is not workaround for this problem, only patching to OWB 10.2.0.4
Regards,
Oleg

Export/Import scripts not working

We're trying to move a portal from one server to another server (different hardware). We haven't been able to successfully complete this process--are there any updated scripts out there from Oracle that make this possible?

2 questions
1. Have you tried using the Portal export/import utilities ?
2. Have you installed Portal and Login server in the target database before attempting 1 above ?
3. Have you patched the Portal repository to the same patch level as that of the source database Portal Repository?

Portal Export Import with DB on different OS

Hi All,
I have a quick question about exporting the OracleAS Portal Metadata Repository database. Our source DB is on a different OS to our target DB.
We are going to apply the 10.1.2.3 patch and associated portal export/import patches to both nodes (from note 263995.1).
Our understanding was that we would use the method described in Chapter 10 of the Portal 10.1.4 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/portal.1014/b19305/cg_imex.htm).
However, according to metalink note#276620.1, because our source and target OS are different, we should use the database export/import methodology that is described in Chapter 11 of the Application Server 10.1.2 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/core.1012/b13995/prodtest.htm).
Could anyone tell me which way is better, we would prefer to use the database export/import method, has anyone tried this and what are their experiences.
Regards,
Tim.

kirwantd wrote:
We are going to apply the 10.1.2.3 patch and associated portal export/import patches to both nodes (from note 263995.1).
Our understanding was that we would use the method described in Chapter 10 of the Portal 10.1.4 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/portal.1014/b19305/cg_imex.htm).
However, according to metalink note #276620.1, because our source and target OS are different, we should use the database export/import methodology that is described in Chapter 11 of the Application Server 10.1.2 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/core.1012/b13995/prodtest.htm).
Could anyone tell me which way is better, we would prefer to use the database export/import method, has anyone tried this and what are their experiences.
Regards,
Tim.As far as your referred Metalink note is concerned, it gives you three options to move your repository with if you are working with 10.1.4 Portal.
It's a difference of can, should and must.
- It only shows ability to use three options ( can );
- on the whole, it does not give preferences for any method ( should );
- nor does it put a requirement for any single option ( must ).
( the only requirement/prohibition is for the option 2 which is not supported ).
we have used the first three methods given on the note (yes, we also tried 2; this note came later). 1 is what we use regularly for transports between environments; and 3 we use for environment staging (as given in chap 11 of pt. 3). both can be messy with a large repository (we do so for about ~400 GB) repository. but following that supportability guide (Metalink Note 333867.1), method 1 works too.
hope that helps!
AMN

Export/Import integrator metadata between instances

Hi all
We have hit recently a situation with some customers who would like to migrate integrator related metadata from one instance to another (integrator, components, mappings, layout, parameter list).
They are doing this using FNDLOAD. For example
Download phase on the source.
FNDLOAD apps/apps 0 Y DOWNLOAD $BNE_TOP/patch/115/import/bneint.lct XXCOHR_Integrators.ldt BNE_INTEGRATORS INTEGRATOR_ASN="XXCOHR" FNDLOAD apps/apps 0 Y DOWNLOAD $BNE_TOP/patch/115/import/bnemap.lct XXCOHR_mapping.ldt BNE_MAPPINGS MAPPING_ASN="XXCOHR" FNDLOAD apps/apps 0 Y DOWNLOAD $BNE_TOP/patch/115/import/bnelay.lct XXCOHR_Layouts.ldt BNE_LAYOUTS LAYOUT_ASN="XXCOHR" FNDLOAD apps/apps 0 Y DOWNLOAD $BNE_TOP/patch/115/import/bnecont.lct XXCOHR_bnecont.ldt BNE_CONTENTS CONTENT_ASN="XXCOHR"
Upload phase on the target.
FNDLOAD apps/apps 0 Y UPLOAD $BNE_TOP/patch/115/import/bneint.lct XXCOHR_Integrators.ldt FNDLOAD apps/apps 0 Y UPLOAD $BNE_TOP/patch/115/import/bnelay.lct XXCOHR_Layouts.ldt FNDLOAD apps/apps 0 Y UPLOAD $BNE_TOP/patch/115/import/bnemap.lct XXCOHR_mapping.ldt FNDLOAD apps/apps 0 Y UPLOAD $BNE_TOP/patch/115/import/bnecont.lct XXCOHR_bnecont.ldt
The problem is that after trying to create a document using the new BNE elements they are getting various errors.
No parameter list definition at parameter list idor No Mappings exist for the specified Content.
I have had a look at some patch delivering integrators via the same LCT files , and the unified driver has for example the following sequence which is executed during the patch
exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinfcmp.ldt &ui_apps 0 Y UPLOAD @BNE:admin/import/bnecomp.lct @PAY:patch/115/import/D/pyinfcmp.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinfcnt.ldt &ui_apps 0 Y UPLOAD @BNE:admin/import/bnecont.lct @PAY:patch/115/import/D/pyinfcnt.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinfint.ldt &ui_apps 0 Y UPLOAD @BNE:admin/import/bneint.lct @PAY:patch/115/import/D/pyinfint.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinflay.ldt &ui_apps 0 Y UPLOAD @BNE:admin/import/bnelay.lct @PAY:patch/115/import/D/pyinflay.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinfmap.ldt &ui_apps 0 YUPLOAD @BNE:admin/import/bnemap.lct @PAY:patch/115/import/D/pyinfmap.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinfpar.ldt &ui_apps 0 Y UPLOAD @BNE:admin/import/bneparamlist.lct @PAY:patch/115/import/D/pyinfpar.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
I couldn' find anywhere this process being documented in an official document or Note.These customers have used some external non-oracle references fordoing so.
Is there anywhere a document giving more information on how this export/import is supposed to work?
Please reply to me directly as I am not part of this mailing list.
Thank you and best regards,
Dan

Looks like you have not transferred your parameter list. Please use following code to download and upload your parameter list.
Download
FNDLOAD apps/$FNDPWD 0 Y DOWNLOAD $ BNE_TOP / admin / import / bneparamlist.lct GENERAL_201.ldt BNE_PARAM_LISTS INTEGRATOR_ASN = "HX" INTEGRATOR_CODE = "GENERAL_201_INTG"
Upload
FNDLOAD apps/$FNDPWD 0 Y UPLOAD $BNE_TOP/admin/import/bneparamlist.lct GENERAL_201.ldt
For mapping there is a possibility that you might have migrated wrong content. You need to migrate content which is none instead 'text'
HTH

Any successfull Export-Import in portal 9.0.2?!?!?!?!

Hi all.
Has anybody been able to export/import ANYTHING in the new portal?????? I tried and tried in portal 9.0.2.2.22 on Win 200 and nothing happened. We got no errors but nothing was imported.
Has this worked for anybody on any platform????????? Please give me some hope!!!!!!!!!!
Thanx, Mere.

We had similar problem. After a few consultations with support we decided to first export everything but the pages (templates, styles, ...). It worked ok (no problems or errors). Then we devided pages into two groups - contents and body (decision based on page design - had nothing to do with oracle). We exported one by one (not by bulk actions because we recived errors but every page by hand - it took as some time but at least we got clean export). Import - we first imported the first export (templates, styles,..) then the body and then the contents. With the first export we encountered no problems. But the other two get us the problems with page id`s and no data was imported. Support told us to instll patch no. 2472140. After this install we got "Import of Item failed." in the import log for both. But data was there and we reimpoerted the templates. We needed to publish some portlets and change the page ids (wich we would have in any case).
Best,
Primoz Kumse
K&S Consulting, Slovenia

Procedure names in lowercase (export/import)

After an export/import into a new schema all package/procedure/function names are written in uppercase and within ". The rule in our norms and standards defines to write object names in lowercase. Is there a solution to keep object names in lowercase and without "?
We work with Oracle 10gR2 and developer tool Toad!
Example:
before import --> CREATE OR REPLACE PROCEDURE p_to_bk_trans_multiversa
after import --> CREATE OR REPLACE PROCEDURE "P_TO_BK_TRANS_MULTIVERSA"
The name of the object is now written in uppercase.
Edited by: user7535259 on Apr 13, 2010 11:36 PM

Hi,
I remember an issue where DataPump was no preserving the spacing and <cr> in functions, procedures, and packages, but I don't remember an issue where it was upcasing the name. I just checked with 11.2 and it seems to work fine. I created 2 functions:
create function foo (a number) return number is
begin
if a > 0 then
return 10;
else
return 100;
end if;
end;
create or replace function "foo" (a number) return number is
begin
if a > 0 then
return 10;
else
return 100;
end if;
end;
Then ran export/import to sqlfile and got this:
CREATE function foo (a number) return number is
begin
if a > 0 then
return 10;
else
return 100;
end if;
end;
CREATE function "foo" (a number) return number is
begin
if a > 0 then
return 10;
else
return 100;
end if;
end;
So, it looks like it has been fixed in 11.2. I'm not sure if there is a patch available for your release, but you could contact Oracle Support to see.
Dean

Client copy error - Export/Import

Hello Folks,
With a certain business requirement we have small scale implementation planned every quarter and as per the requirement we are performing a client copy into one of our SANDBOX(SDX) client (201) every quarter from our Production ECC system (cleint-600).
*The SANDBOX is used for POC and new enhancement testing and also for training purposes.
Cleint copy (export/import method)
============================
PRD (600) ==> SDX (201)
Both Sanbox and production are with same SAP version, patch, OS and database versions.
The client copy(client export-import method) is successfull when the client is new (SDX-201), but when we did the client next time on the same client, the client copy finished with many inconsistencies.
We have also tried deleting the client 201 and then recreating client 201 in SDX and copy from our PRD-600. But the result is same, the client copy finished with many inconsistencies.
Now we are not able to figure out the problem why this problem is occuring. The whole point of client copy from PRD is not helping project. As a workaround at the moment we are copying onto a new client every quarter.
We have to get a solution. Please suggest.
PS: We can not do the system refresh, because there are other clients on the Sandbox systems and we do not want them to be disturbed.
Lookign forward for your suggestions.
Thanks
James

Hello James,
The client copy(client export-import method) is successfull when the client is new (SDX-201), but when we did the client next time on the same client, the client copy finished with many inconsistencies.
What inconsistencies ? Can you please post the error log ?
Regards,
Subhash

Export / Import UDM Metrics

Hi I would like to know is there a way you can export / import UDM (User-Defined) metrics from one EMGC (Enterprise Manager Grid Control) repository to another EMGC repository.
I found a patch:
5369264 SUPPORT FOR EXPORT/IMPORT OF METRICS AND THRESHOLDS
which indicates that EMGC supports export/import of metrics and thresholds. However, after applying this patch what additional steps is required to exporting/importing the metrics?
Does this also support the export/import of UDM as well?
Kindest Regards
Tam

This is an old thread but since it comes up in google lets add to it.
search for Deploying User-Defined Metrics Across Many Targets Using Monitoring Templates
http://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10954/udm2.htm
to see how to create the monitoring template
then to export and import a monitoring template
http://www.borndba.com/index.php/2011/07/export-template-across-oms-servers-using-emcli/
You can only do it when the source and destination are the same version. I've only done it on 10.2.0.4 and 10.2.0.5 versions of OMS.

Official oracle stance on portal 9.0.2 migrate/export/import

i have been working with oracle support, scouring the forums and deja and metalink, applying patches, standing on my head... trying to export my 9.0.2 portal applications, reports, pages and such from a 9.0.2 implementation into an exact same 9.0.2 implementation. i have run into issues with the reports, issues with the pages, corrupt objects that can't be deleted, most everything stated on this forum, plus more. i have asked oracle time and again when the migrate scripts [the FAQ still posted at technet and portalcenter STILL says the scripts will be available august/september] will be ready and have gotten no meaningful response. surely oracle cannot pretend that this export/import works and I NEED A REPLY FROM ORACLE AS TO THEIR OFFICIAL STANCE on this and as to when we can expect a working solution. i am going to have to recommend against oracle portal because we cannot get from our development environment into a testing one.

thanks... i do hope they can give us some expectation of when this will be ready for primetime. i couldn't get my pages across because i get a region not found error, so i tried just to import my provider applications that include rwreps with parameters. i figured worst case i could manually recreate the pages. the export indicates no errors, the import check mode indicates no errors, but the actual import gives me a warning on every portlet parameter and none of my reports come across:
sample warning i receive:
Importing portlet preferences ..........
Importing category/perspective info ..........
---------- Before Importing Pronto Tables ----------
*** Warning: no corresponding portlet parameter ID found on target for 295 for BUSINESS_UNIT
so i applied patch 2617359 per oracle support but no luck. apparently this is another bug being worked on by support [Bug:2644937 Abstract: IMPORT:PAGE:PRONTO:REPORT:SECURITY:PORTLET PARAMETER ID NOT FOUND IN LOG] but in the meantime i face the prospect of having to manually recreate 40 plus reports on each instance. this may or may not be related to bug 2426089 from version 3.0.9.x [Bug 2426089 Abstract: PARAMETERS ARE NOT VISIBLE AFTER REGISTERING THE REPORTS ON PORTAL]. i am still trying to come up with some way to get my reports across. i'm going to try exporting/importing just a report with nothing else and see what happens.

Problems Export/Import on Windows x64 with SQL2005 x64

Hi All:
After successful export with R3Load of a ECC5.00 (Kernel 6.40 Patch level 171) when we import the data into SQL2005 SP1 and after successful import into the target database, we have some inconsistencies in several DYNPROS, we got errors like this when we run several transactions:
BZW Error 2 during compression/decompression ( UNPAC)
AB0 Run-time error "DYNPRO_SYNTAX_ERROR" occurred
and in the trace files we found:
Fri Feb 23 16:12:35 2007
***LOG BZW=> error 2          on compression/decompression using UNPACK     [dbdynp#1 @ 842] [dbdynp 0842 ]
ERROR => Involved dynpro: SAPMF02D                                 - 0101
dbdynp.c     842]
ERROR => DY-SRC_READ BUFFER: any error 4 [dgdynp.c     1225]
It seems the DYNPROSOURCE table contains bad entries, but the export/import procedure was successful, we also execute "Tools for MS SQL" successfully.
Any help will be greatly appreciated...!!!
Regards,
Federico

Hi Federico
Seems there is some problem in kernals.I would suggest a solution :Solution: Copy <putdir>\exe to $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
and repeat phase.
Let me know if it works.
Also check the numbers in instance problem,it should not be more than 20 for windows.
Reward points

Parameter Export/Import is getting too high

Hi Experts,
In our production system the parameter Export/Import is too high currently shown as 95.31 while there is no swaps occured.Please guide us how can I manage this .
We are using ECC 5.0 + oracle 9i with patch level 7
Thanks in advance.

Hi,
The hit ratio is above 95% which means it is good. You should not worry about that.
Rgds,
Suman

Export import mandotary patches

Similar Messages

Maybe you are looking for