Steps to be followed in Export/Import

Can anyone help me out defining the exact steps to be followed in exporting and importing the ODI objects?
I have exported the master and work repository. I created a new master repository by importing the zip file. I can see the architecture neatly imported into the topology. The problem starts when I try to import the work repository. It keeps throwing the integrity constraint error. I export/import folder-wise as the current work repository is pretty huge!!
It will be of great help if some one could explain the steps to be followed while export/import in ODI

Hi there,
It is typical of ODI to throw those errors, as the documentation is not quite comprehensive about how to do it.
Here are a few guidelines:
(i) Topology (master repository) should be exported n imported first. Then the models and finally the projects and the variables. Also, work repository export may not work if you try to export whole work repo at one go using File---->Export---->Work Repository !
So the best thing is File--->Export---->Multiple Export----> then drag all ur objects into the box and check the "zip" checkbox
Create separate zips for Models and separate for Projects and so on
And import Model zip before Project zip in your new repository
OR
(ii) Use database schema export and import. This has worked the best for us.
And I think it is the most flawless way of doing export import because you dont lose any objects and dont get any integrity constraint errors etc
Just export the master repository & work repository schemas and then import them in you new database

Similar Messages

Error when exporting/importing

I am using MDM 7.1
When I export the schema from my Dev system to import into QA I get the following Error:
"This repository requires additional steps before transport. See the MDS log for details.
In the log my issue is that I am trying to export an Assignment that includes an expression that uses "look-ups".
In my Dev system I removed the expression to confirm if this is the issue, once I no longer have expressions with look-ups then it allows me to export the schema. I then tries to import it to QA (since the expressions are not changing I planned on excluding them from the import as a temporary workaround.
however I get the same error message when trying to import. It seems that I can not export or import with a system that has an assignment with an expression that uses look-ups.
Is there some config I am missing?

Hi Brad,
assignments/validations are a general problem when it comes to Schema exports/imports! What you can do in case there are not too many assignments - is to delete the assignments and create them new (manually) after you have imported the schema.
Hope this helps a little.
Regards,
Erdal

Error during export & import of rules in RAR 5.2

Hi all,
We followed the steps mentioned in exporting & importing the rules as per the Config guide. But we
are receiving the below error during the import of rules. Can anybody please throw a limelight on why this error message is appearing?
"Error in Table Data ==> VIRSA_CC_CRPROF
SQL==>Insert into VIRSA_CC_CRPROF(VSYSKEY,PROFILE,RULESETID,RISKLEVEL,STATUS)Values(??????)
Record==>D VIRSA_CC_CRPROF null"
We also ensured that the downloaded file is not truncated and saved it in a separate folder. Does the file needs to saved in ANSI or Unicode text? We saved in ANSI
Also the background ground job is not getting scheduled automatically during the import of ruels. Is that due to the above error?
Thanks and Best Regards,
Srihari.K

Hello Sri,
background job for generating the rules won`t be scheduled before you upload the file successfully.
The most obvious reason for this error message is that you have line in your file - in table VIRSA_CC_CRPROF that is corrupted. Make sure all lines from table VIRSA_CC_CRPROF have all predefined fields - (VSYSKEY,PROFILE,RULESETID,RISKLEVEL,STATUS).
If you keep hiting this problem just delete this table, after the upload you`ll add the critical profiles manually - I bet you don`t have many of them.
Also from my experience I always choose to save the downloaded file in UNICODE UTF-8 format.
Once the file is saved in other format, there`s no use of it, download it again and save directly in Unicode.
Make sure you don`t have empty fields, even in the fields where you don`t have values, you must leave space, otherwise you`ll keep hitting the same issue.
Regards,
Iliya

SLD Export / import Technical and Business systems

Dear all,
I am new to SLD administration.
We have task to update the local SLD on the Production PI system PPI ( Target ) with the business systems ZEC, ZSC from the Production Master SLD on Production solution manager system
PSM ( source ) using Export/Import on the necessary technical and business systems.
Please confirm whether i am following correct steps :
Go to SLD Administration on PPI target system
ALL Instances
Instances by Class
Model
( which one of this option need to be selected , please let me know ?? )
Go to SLD Administration on PSM source system.
select Export button ->
Select business systems one by one and perform Export which will create .ZIP file
at local machine.
Go to SLD Administration on PPI target system
select Import button ->
Select Export ZIP file which created in previous steps from PSM and provide location from desktop
Start Import button ( only if you get Continue import option )
Please let me know if above procedure is correct for business systems
if yes then what need to be done for Technical system ??...do they require Export/import also ?
If yes when i go to technical system option i get Export option disabled...but same way when i go to
business systems option i get Export button enable and able to perform the export.
Do i need to only Export / Import business systems ?
Plese help me.
Regards,
RR

Manoj,
It seems entries are added manually .... should we remove and run Import for the same ...
or just try to overwrite .... in case of overwrite option ( as we have open OSS message ) SAP has suggested through OSS message that If you end up with problems when trying to overwrite, then the PPI SLD is broken and will have to be re-built because someone made a manual change to it and got the GUIDs out of synch with the master.
I do not understand if target system PPI SLD gets broken during overwriting operation as mentioned by SAP ... whats is the way / steps / procedure to Re-build SLD .
In rebuilt - process do i need to Import ( Export -> Export lines -> ALL ) the export backup created before start of this activity ? please let me know SLD rebuilt steps and about Remove - reimport issue.
Appreciate you time on this. thanks in advance.

Transfer Foreign Trade Export Import values in Purchase Order

Hello SRM brothers and sisters,
I have a question regarding the transfer of the Import/Export data (Foreign Trade) in the PO from SRM to ECC in the Classic Extended Scenario.
Basically, in the SRM BBP_ECS_PO_OUT_BADI -> BBP_B46B_PO_OUTBOUND method where we map all the values, I try to fill in the CT_BAPI_POEXPIMPITEM table with the item's Import/Export values.
The way this is done is:
if nothing exists in this CT_BAPI_POEXPIMPITEM table for the PO item, add an empty line and assign the following fields ( PO_ITEM, EXPORT_IMPORT_PROCEDURE, COUNTRYORI and COMM_CODE).
This is then sent to ECC via the RFC BBP_PO_INBOUND function module - and inside I know that it assigns the X-structure of Export/Import Item. It then calls the BAPI_PO_CREATE / BAPI_PO_CHANGE and in the debugger the values seem to be correct.
This all seems to be very nice, however when I take a look at the PO in ME23n, the values of the Import/Export data are not there! In table EIPO there is also nothing... As for error messages, nothing comes up either.
So, has this happened to anyone? Am I doing something wrong? Is there an extra step I should do (ie, fill another structure/table/field)?
Cheers,
Adi

Hi Kishor,
Thanks for your reply.I need to some more inputs if you can...
As you mention :-You need to enter the special UOM according to the specifications in the index of goods or foreign trade statistics: can you give a example to get more clarification.and how Qtys. are converted to this unit for the export declaration.
You mentionwd : (FOr each item, you have to enter the amount of the unit of measure determined
in the index of goods. Eg: number of units) -can u explain with example. what is index of Goods.
Thanks in adavance.
Thank you.
Regards
Amar

Using export/import to migrate data from 8i to 9i

We are trying to migrate all data from 8i database to 9i database. We plan to migrate the data using export/import utility so that we can have the current 8i database intact. And also the 8i and 9i database will reside on the same machine. Our 8i database size is around 300GB.
We plan to follow below steps :
Export data from 8i
Install 9i
Create tablespaces
Create schema and tables
create user (user used for exporting data)
Import data in 9i
Please let me know if below par file is correct for the export :
BUFFER=560000
COMPRESS=y
CONSISTENT=y
CONSTRAINTS=y
DIRECT=y
FEEDBACK=1000
FILE=dat1.dmp, dat2.dmp, dat3.dmp (more filenames here)
FILESIZE=2048GB
FULL=y
GRANTS=y
INDEXES=y
LOG=export.log
OBJECT_CONSISTENT=y
PARFILE=exp.par
ROWS=y
STATISTICS=ESTIMATE
TRIGGERS=y
TTS_FULL_CHECK=TRUE
Thanks,
Vinod Bhansali

I recommend you to change some parameters and remove
others:
BUFFER=560000
COMPRESS=y -- This will increase better storage
structure ( It is good )
CONSISTENT=y
CONSTRAINTS=y
DIRECT=n -- if you set that parameter in yes you
can have problems with some objects
FEEDBACK=1000
FILE=dat1.dmp, dat2.dmp, dat3.dmp (more filenames here)
FILESIZE=2048GB
FULL=y
GRANTS=y -- this value is the default ( It is
not necesary )
INDEXES=y
LOG=export.log
OBJECT_CONSISTENT=y -- ( start the database in restrict
mode and do not set this param )
PARFILE=exp.par
ROWS=y
STATISTICS=ESTIMATE -- this value is the default ( It is
not necesary )
TRIGGERS=y -- this value is the default ( It is
not necesary )
TTS_FULL_CHECK=TRUE
you can see what parameters are not needed if you apply
this command:
[oracle@ozawa oracle]$ exp help=y
Export: Release 9.2.0.1.0 - Production on Sun Dec 28 16:37:37 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
You can let Export prompt you for parameters by entering the EXP
command followed by your username/password:
Example: EXP SCOTT/TIGER
Or, you can control how Export runs by entering the EXP command followed
by various arguments. To specify parameters, you use keywords:
Format: EXP KEYWORD=value or KEYWORD=(value1,value2,...,valueN)
Example: EXP SCOTT/TIGER GRANTS=Y TABLES=(EMP,DEPT,MGR)
or TABLES=(T1:P1,T1:P2), if T1 is partitioned table
USERID must be the first parameter on the command line.
Keyword Description (Default) Keyword Description (Default)
USERID username/password FULL export entire file (N)
BUFFER size of data buffer OWNER list of owner usernames
FILE output files (EXPDAT.DMP) TABLES list of table names
COMPRESS import into one extent (Y) RECORDLENGTH length of IO record
GRANTS export grants (Y) INCTYPE incremental export type
INDEXES export indexes (Y) RECORD track incr. export (Y)
DIRECT direct path (N) TRIGGERS export triggers (Y)
LOG log file of screen output STATISTICS analyze objects (ESTIMATE)
ROWS export data rows (Y) PARFILE parameter filename
CONSISTENT cross-table consistency(N) CONSTRAINTS export constraints (Y)
OBJECT_CONSISTENT transaction set to read only during object export (N)
FEEDBACK display progress every x rows (0)
FILESIZE maximum size of each dump file
FLASHBACK_SCN SCN used to set session snapshot back to
FLASHBACK_TIME time used to get the SCN closest to the specified time
QUERY select clause used to export a subset of a table
RESUMABLE suspend when a space related error is encountered(N)
RESUMABLE_NAME text string used to identify resumable statement
RESUMABLE_TIMEOUT wait time for RESUMABLE
TTS_FULL_CHECK perform full or partial dependency check for TTS
VOLSIZE number of bytes to write to each tape volume
TABLESPACES list of tablespaces to export
TRANSPORT_TABLESPACE export transportable tablespace metadata (N)
TEMPLATE template name which invokes iAS mode export
Export terminated successfully without warnings.
[oracle@ozawa oracle]$
Joel P�rez

Export/import to clone database -- please advise

Hi All,
Need help especially from exports that are strong in export/import.
can someone advise me how to use export/import to clone a database?
I know how to clone database using cold backup and hot backup.
But wish to know the full steps in using export/import to do cloning.
I'm going to do a full export on my "TEST" database, drop the database, create a database and import using the full export.
After doing a full database export, full=y. What are the steps to follow. Have a few doubts about it.
1) export the database (full=y)
2) drop the database
3) re-create the database, will be using the same name "TEST".
4) create the users (IDs created by DBA, eg: schemas), tablespace and datafiles. --> import doesn't do it right?
5) do a full import (full=y). In this step, will i encounter any problems? As in understand that all the oracle-owned objects (example SYSTEM, SYS, AUX) are already in the newly created database, will import full=y cause any problems?
6) do i have to re-create the roles, SYNONYMS and grant role,sys,obj privileges to IDs not created by oracle. (example schema owner)
in short i would like to know what EXPORT will export and not export
what IMPORT will import and not import.
Please advise.

Hi zetabouy,
thanks for ur input, definately helpful for me.
just to confirm. am i right to say that only a full database level (full=y) export/import will export/import out roles as well as public synonyms? because i have tried also exporting a user from the database, and imported that user into a different database, but public synonyms and roles were not imported.
one more question:
For example we are going to do port data from production to uat database using export and import for only the schema.
After exporting from production with such syntax (owner=OWNER01),
is is better to drop all objects beloging to the schema owner in UAT before importing it (touser=OWNER01, ignore=y) using the production dumpfile?
I'm asking this question as I'm afraid that if we did not drop all the pl/sql objects in UAT database, the updated procedures/fuctions/triggers exported from the production database will not get imported to the UAT database as UAT database have the same procedures/fuctions/triggers names (but not updated code) .
will profiles be exported and imported too duing full database level exp/imp?
please kindly advise.
thanks
Message was edited by:
chew

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 single table...

Gurus...
I am working on this single table which needs to be exported from prod and import into test.
As I understand I need to follow below steps:
1. Test - export table abc dump as backup
2. Prod - Export single table abc
3. Test - Drop table abc cascade constraints
4. Test - Import abc into test
Export par file:
Directory= dbpump
dumpfile= expdp_abc.dmp
logfile= expdp_abc.log
content= all
tables=user.abc
exclude=statistics,object_grant, tablespace_quota
flashback_time= systimestamp
Import par file:
Directory= dbpump
dumpfile= expdp_abc.dmp
logfile= impdp_abc.log
content= all
tables=user.abc
table_exist_action=replace
transform=segment_attributes:N
my doubts:
1. Is my process flow correct?
2. Export & Import file correct? or missing parameters?
3. What happens to all objects connected to the table, will that also imported?
4. Do I need to lock user during this process?
5. Any script to check whether all objects connected to table does exist in test after import?

Hi,
Process for table export & import.
+1. Create database directory in test as well as production:-+
--> create or replace directory directory_name as 'physical_path';
--> grant acsess on that directory to user.
+2. Backp table in test environment (in case if you need old data in your test env):-+
--> Create table BKP_table_name as select * from table_name; (table_name u want to import)
+3. Take Export backup in Production database:-+
--> expdp dumpfile=file_name.dmp logfile=file_name.log directory=directory_name tables=Owner.table_name
+4. On test server do the following actvity:-+
a. Just check for dependencies on that table using DBA_DEPENDENCIES.
b. Truncate table which u want to import
c. import table-
impdp dumpfile=file_name.dmp tables=owner.table_name logfile=file_name_imp.log directory=directory_name table_exists_action=APPEND
d. Just check for dependencies on that table using DBA_DEPENDENCIES.
And also you can use table_exists_action=replace
This will also import all depedent objects to the table..
Regards,
Edited by: XBOX on Dec 14, 2012 10:15 PM

Export / import tablespace with all objects (datas, users, roles)

Hi, i have a problem or question to the topic export / import tablespace.
On the one hand, i have a database 10g (A) and on the other hand, a database 11g (B).
On A there is a tablespace called PRO.
Furthermore 3 Users:
PRO_Main - contains the datas - Tablespace PRO
PRO_Users1 with a role PRO_UROLE - Tablespace PRO
PRO_Users2 with a role PRO_UROLE - Tablespace PRO
Now, i want to transfer the whole tablespace PRO (included users PRO_MAIN, PRO_USER1, PRO_User2 and the role PRO_UROLE) from A to B.
On B, I 've created the user PRO_Main and the tablespace PRO.
On A , i execute following statement:
expdp PRO_Main/XXX TABLESPACES=PRO DIRECTORY=backup_datapump DUMPFILE=TSpro.dmp LOGFILE=TSpro.log
On B:
impdp PRO_Main/XXX TABLESPACES=PRO DIRECTORY=backup_datapump DUMPFILE=TSpro.dmp LOGFILE=TSpro.log
Result:
The User PRO_Main was imported with all the datas.
But i 'm missing PRO_USER1, PRO_User2 and the role PRO_UROLE...
I assume, i 've used wrong parameters in my expd and / or impdp.
It would be nice, if anybody can give me a hint.
Thanks in advance.
Best Regards,
Frank

When you do a TABLESPACE mode export by specifying just the tablespaces, then all that gets exported are the tables and their dependent objects. The users, roles, and the tablespace definitions themselves don't get exported.
When you do a SCHEMA mode export by specifying the schemas, you will get the schema definitions (if the schema running the export is privied) and all of the objects that the schema owns. The schema does not own roles or tablespace definitions.
In your case, you want to move
1. schemas - which you already created 1 on your target database
2. roles
3. everything in the tablespaces owned by multiple schemas.
There is no 1 export/import command that will do this. This is how i would do this:
1 - move the schema definitions
a. you can either create these manually or
b1. expdp schemas=<your list of schemas> include=user
b2 impdp the results from b1.
2. move the roles
expdp full=y include=role ...
remember, this will include all roles. If you want to limit what gets exported, then use:
include=role:"in ('ROLE1', 'ROLE2', ETC.)
impdo the roles just exported
3. move the user information
a. If you want to move all of the schema's objects like functions, packages, etc, then you need to use a schema mode
export
expdp user/password schemas=a,b,c ...
b. If you want to move only the objects in those tablespaces, then use the tablespace export
expdp user/password tablespaces=tbs1, tbs2, ...
c. import the dumpfile generated in step 3
impdp user/password ...
Hope this helps.
Dean

How to use lodercli for export import

Hello,
I want to migrate my content server data , that is on SAPDB version 7.3 (32 bit) to new server with MAX DB 7.6. (64 bit) .
I wanted to know:
1) how to do export an d import using lodercli. i wanted to use loder of my new server i.e. MAXDB loder to do the export immport. Can any one tell me the steps and the command to do this ?
2) I have refered SAP note 962019, but need some more help on the steps that is given in this note for hetrageneous copy.
Note : i dont have any SAP system on the server i have only content server and hence i dont have user SAPR3 on database.
Regards,
Bhavesh

> Please check the following (point 7) in note 962019:
Ok...
> 7. The procedure described in this note supports the following migrations:
> and I am dealing with the same situation hence choose the export import rather than normal backup recovery.
Well. it says: the procedure supports these migrations, which is true.
It does not say: "please do use the export/import migration in these situations".
Please do read the note point 1 where it says;
"Homogeneous system copies (backup/recovery) can be executed only in
systems that fulfill the following conditions:
a) The database versions in the source system and the target system
do not differ.
b) The processor uses the same byte sorting sequence (Little Endian
-> Little Endian; Big Endian -> Big Endian).
*If the specified operating system prerequisites are met in the
source and target system, you MUST use the homogeneous system copy
and not the heterogeneous system copy.*"
So in your case export import is not even supported!
> 2) I know the Cs 6.10 is out of support and it need to upgrade to new CS version that is 6.4 , but if i am already installing the new server for content server with CS 6.4 and MAXDB 7.6 why then why cant i use the export import from older server to new server??
> Other wise i need to upgrade the MAXDB then upgrade CS and then take the backup and restore, isnt it more logivcal to do export import using loder as we have all prerequisites available??
1. you don't meet the prerquesites (see above) - you can use backup/restore, so you have to !
2. export/import is a terribly slow and clumsy procedure
3. backup/restore is a easy, safe and fast method to perform the system copy
If you still really, really want to stick with export/import, feel free to try it out.
The note contain all required steps and the documentation for MaxDB even includes tutorials for the loader.
regards,
Lars

Export & import of query (SQ01/SQ02/SQ03)

Hi,
How to export/import SAP Query (SQ01/SQ02/SQ03) without any transport request.
waiting for ur reply.
Thanks in Advance,
Pranab

Hi,
If you dont want to create any transport request number then you need to download/upload the query instead of import/export.
Please follow the below steps for downloading/uploading the query
(Go to the system from where you wnat to export the query)
1. Goto transaction SQ02.
2. Click on ' Transports' icon (CTRL+F3).
3. In 'Transport action' select 'Download'.
4. Select 4th radio button 'Transport Queris'.
5. Enter the name your user group and query and click on execute.
6. Give the file name and location where you want to save the query backup and click on save.
(Now goto the system where you want to import your query)
1. Goto SQ02 and click on 'Transports' .
2. In 'Transport action' select 'Upload' and click on execute.
3. Enter/select the name of the file which you have downloaded before and click open.
Please let me know if this is helpful.
Regards,
Priya Bhat

Full Database Export/Import

I was attempting to export a full database from one server (DB files on the N: drive) and import it into a freshly created new database with the same instance name on a new server (DB files on the D: drive).
I was told to:
1) Export the full database as sys using full=y
2) Pre-create all of the tablespaces on the target database that do not exist on the target database
3) Import the full database as sys using full=y
=========================================================
Here are the steps I had to follow:
1) Export the full database as sys using full=y
2) Pre-create all of the tablespaces on the target database
3) Import the full database as sys using full=y - Result: over 1900 invalid objects and thousands of errors
4) Run Utlrp.sql - Result: 8 to 10 invalid objects
5) Manually attempt to compile or rebuild objects. Several grants were required to get most of these to work. - Result: After quite a bit of hand crafting, two objects are still invalid.
6) After spending almost two hours in a Collaborative Conference with an analyst who is working very hard to sold this, there are still two objects that are invalid.
Note: From my perspective this is not a straight forward process
=========================================================
Questions:
1) Has anyone successfully moved a database as described without all of these annoying steps?
2) Is there a document that details the full database export/import?
Thanks, RJZ

Hello RJZ,
There is not sufficient information to reply accurately to your queries,
1. Could you post the error message that you're getting when you compile these two programs? Do they compile okay on the old server?
2. What was the reason you choose exp and imp, to move your db to the new server and different disk? Were you migrating to a different version, or was it because of the db-reorg? It would have been possible to simple copy the db-files to the new location, and then rename the datafiles in mount-state. It would be more simpler I believe unless as stated above
Did you check the import logs? While importing were there any errors? Actually it should have been pretty straight forward (no reason why you need documentation for exp / imp). Grants should have automatically come, unless you have select grants=n option
I think because of the changes you have done for step-5, you might have changed some stuff somewhere. Please post the error message, and tell us if you have migrated the db to a higher version
Regards
Sudhanshu

Export/import content area

Hi,
I'm trying to import/export the content area using the contexp.cmd and the contimp.cmd. When I run the import I receive the error '
WWUTL_API_SiteTransport.GetImportSites: Import table WWUTL_SBR_TX_SITES$ is empty
Rolling back transaction'
The first thing the export does is truncate this table so it is always going to be empty. Any ideas how to get round this??
I am running version 3.0.7.6.2 on NT 2000
Thanks

The import truncates the table to remove any old data that might be left from previous export/ import.
Following this step, the Oracle Import utility imp is run. One reason why you are getting the error could be due to different versions of the 9iAS client utilities (which are 8.1.7 based in your case) and the database server. If the database server is 8.1.6 then you need to set the ORACLE_HOME to the database home prior to running the import. Once the import is complete you can reset the ORACLE HOME back to the 9iAS Home.

Steps to be followed in Export/Import

Similar Messages

Maybe you are looking for