DAtapump Import/Export Exit without errors

Hi,
I have cloned a single instacne database into a RAC instance and now here is the problem that am facing.
The EXPDP in the new RAC environment is getting exited without errors . See the error message below.
$ expdp schemas=xxxxdumpfile=SAMP.dmp logfile=SAMP.log directory=DUMPDIR
Export: Release 10.2.0.4.0 - 64bit Production on Monday, 14 February, 2011 18:16:22
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Username: sys as sysdba
Password:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
$
It doesn't throw error nor take backup. It simply quits.
Any suggestions. I googled a lot but now solution.
Please help...

Pl post details of OS and database versions
http://download.oracle.com/docs/cd/E11882_01/server.112/e16536/dp_export.htm#SUTIL2890
HTH
Srini

Similar Messages

Migration Assistent Exits without Error?

Hi all,
My main 3tb iMAC is in the shop getting a new fusion drive as it died. I have to use one of my other iMacs temporarily. This other iMac as a 1tb HD but its mostly empty. I have a Time Machine backup on my NAS drive of my main iMac. I want to copy some of my backup files from the NAS to the 1tb iMAC. But I am having issues trying to copy files.
Basically I launch Migration Assistant, it goes through the steps and I pick the user I want to migrate. It start the process then says that the users files are too large for this iMac and so I have the option to go back and pick specific folders to copy. I unclick enough folders so it fits on the 1tb iMAC, I click next and then the Migration Assistant just exits and I am returned to the login screen.
I see the problem on two different iMacs - the 2014 one with 1tb and an older 2011 iMac with 2tb. No error, it just exits. Not sure what to

A third-party NAS is unsuitable for use with Time Machine, especially if it's your only backup. I know Time Machine accepts the NAS as a backup destination. I know that the manufacturer says the device will work with Time Machine, and I also know that it usually seems to work. Except when you try to restore, and find that you can't.
Apple has published a specification for network devices that work with Time Machine. None of the third-party NAS vendors, as far as I know, meets that specification. They all use the incomplete, obsolete Netatalk implementation of Apple Filing Protocol.
If you want network backup, use as the destination either an Apple Time Capsule or an external storage device connected to another Mac or to an 802.11ac AirPort base station. Only the 802.11ac base stations support Time Machine, not any older model.
Otherwise, don't use Time Machine at all. There are other ways to back up, though none of them is anywhere near as efficient or as well integrated with OS X. I don't have a specific recommendation.
Starting from a clean installation of OS X, set up a new administrator account and log in.
Hold down the option key and select
Browse Other Backup Disks...
from the Time Machine menu in the menu bar. The menu icon looks like a clock running backwards. If you don't have that menu, open the Time Machine preference pane and check the box marked
Show Time Machine in menu bar
You may now be able to restore your user data. I suggest you do this in two stages. Quit all applications except the Finder before you begin.
Restore all the visible items at the top level of the home folder.
Hold down the option key and select Go ▹ Library from the Finder menu bar. Enter Time Machine and restore all items in the Library folder. Log out and log back in as soon as the restore is complete.
Any other invisible folders or files at the top level of the home folder that you want to preserve will have to be restored separately. For most users, that isn't necessary.

ORACLE 10g : Datapump-Import : Error: unknown parameter name 'REMAP_TABLE'

Hi,
I am working on Oracle 10g. When executed import datapump script in the UNIX box with option “RMAP_TABLE” I received the error “unknown parameter name 'REMAP_TABLE' “Can you please give me solution for it?
Scripts :-
impdp eimsexp/xyz TABLES=EIMDBO.DIVISION DIRECTORY=DATAMART_DATA_PUMP_DIR DUMPFILE=expdp_DATAMART_tables_%u_$BATCH_ID.dmp LOGFILE=impdp_DATAMART_tables.log REMAP_TABLE=EIMDBO.DIVISION:EIM2DBO:YR2009_DIM_DIVISION
Note :- The YR2009_DIM_DIVISION table is available in the target database. It is without partition table. The EIMDBO.DIVISION is partition table.
Thanks,

See your post here
ORACLE 10g : Datapump-Import : Error: unknown parameter name 'REMAP_TABLE'
Srini

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Getting an error while importing/exporting the universe from my BO Designer

Hi,
   I am facing a issue while importing/exporting the universe from my BO Designer to the Server.The error is mentioned below.
   'File Repository Server Input is down'
   Once I click the OK button on this error message, it displays the message
   'Could not import the Universe'.
I tried the check the status of the File Repository Server (Ouput and Input) and also the of the Root Directory on the Physical Server and also my machine.They all have read-write access.
Installed Version of the Universe Designer Client: Business Object XI Release 2 SP3
Installed Version of the BO Enterprise Server: Business Object XI Release 2 SP2
Can you please help me to resolve the issue

Hi,
   The step you have mentioned may not be applicable to my issue as one of my colleagues can import/export the universe from the same server
The second thing is that a DB2 Client v9 is installed on both mine and my colleagues system.The Designer software can recognise the DB2 drivers on his system but it cannot recognise the same drivers on my system.I even checked the versions of the BO software installed on his and my system and they are same.
The only difference is that his machine is a Windows XP Machine and mine is a Network Desktop.
Will any of the above two things will affect the operation of the BO Designer.
Thanks
Prabhakar Korada

Export and Import of master repository - error snpuser not found

We had installed ODI on a windows server and created physicla and logical topologies etc and developed some models and projects.
But we had sone all of this while still pointing to the demo master repository using the HypersonicSQL. This means we always have to have the 'Start Demo Agent' running etc.
So we wanted to move to an Oracle based master repository. I have used the 'Create Master Repository' function to create a new repository using ORacle thinnet driver and this is all OK and I can sign in to the SUPERVISOR user.
But when I export our existing repository from the 'HypersonocSQL' demo one to a ZIP file and then use the 'Import Master Repository' to create a master repository in the Oracle using thinnet driver etc - firstly it removes the repository details that I originally created - fair enough - then creates it all again but from the ZIP file.
The SNP_ tables all exist in the oracle database user and I can see that in SNP_USER there is the record for SUPERVISOR etc.
But when I try to sign in to this through topology manager or security manager - as SUPERVISOR I immediately get the error 'SNPUser does not exist'
Am I doing something wrong with exporting my 'demo' master repository and trying to import it in to the new Oracle repository ?

thanks - but that is effectivley what I did - used the repository import from my exported ZIP file - and it all imported OK - but the error on login to topology manager afterwards is that the snp user does not exist.
Although I initially used the 'Master Repository Creation' I then adaondoned this - dropped and recreated my Oracle user 'snpm' that owns the master repository and used the import repository approach.
I am trying to sign in as the standard SUPERVISOR user (that existed OK in the Hypersonic master repository that was exported to the ZIP file) and also trying other users that I know existed in the Hypersonic reporitory that I exported - same problem. I can see in Oracle SQL*Plus that in the SNP_USERS table the SUPERVISOR user exists.
If I do instead carry out a standard 'Create Master Repository' and do NOT try to import anything then it works OK and I can sign in to the Topology Manager as SUPERVISOR.

Error import / export in console standalone

hai all,
error import / export in console standalone
iam logged in 9i console standalone pc not connected any other pc.
unable to import or export or load any database
because the error shows that
only on OMS mode is possible
how can import or export or load?
any help?
thanks in advance
rcs
------

I have no idea what you are asking or in what environment you are work.
Lets start with the need for a version number ... 9i is not a version ... it is a marketing label. Do you mean 9.0.? or 9.2.0.1 or 9.2.0.8 no one knows.
Second I have no idea what a you intend to convey with the statement "console standalone pc."
Third "unable" means what? That the pc crashed and burned and is a smoldering cinder or you received some error message you thought too unimportant to post? Again ... you've given us no useful information.
Finally what do you mean by OMS? Is this OMS as in the Java application running as part of the Grid Control or something else?
Finally what are you trying to import? How? A clear explanation is required.
If someone reading what you post can not understand or duplicate what you did because of lack of information you will not receive any help.

Can I import binary in Flash CS5 and export swf, without AS code likes "Embed" ?

Can I import binary in Flash CS5 and export swf, without AS code likes "Embed" ?
I know I can use AS code,likes "[Embed]" metadata to embed binary in swf. But , how can I do that in Flash CS5 ?

Have a look at this: http://stackoverflow.com/questions/7816231/how-to-use-as3-to-load-binary-data-from-web-ser ver

LR panels on left and right not appearing. "an error occured while attempting to change modules" no import/export options

Installed CC trial and opened LR, panels on left and right not appearing. keep getting an error message "an error occured while attempting to change modules" plus no import/export options.

Error changing modules | Lightroom
Mylenium

"ActiveX Error, Unknown Error" when trying to Import/Export Properties

Hi,
When I try to "Import/Export Properties…" Testand returnig this error:
Attacing a max report of my system.
Have someone seen this problem?
BR Are
Attachments:
max_report.zip ‏7 KB

Hi,
MAX gives useful information for debugging. TestStand version, operation system, cpu, memory….
I am not sure that I have “TestStand Version Selector” since only one version of TestStand is installed.( NI TestStand 4.5.1).
Are you using the PropertyLoader? My intention is to use the PropertyLoader. But after I click on "Import/Export Properties…" from the dropdown menu, TastStand return the error.
Thank
Are

Import/Export xls Error

Hi,
I'm facing a problem with import/export xls files.
Once I selected the file the system doesn't return any response even if the file has very small size (about 70 KB).
It happens both from workbench and web.
Furthermore I can't to export something to Excel (I.e. the categories)
Any suggestion about it?
Thank you

Import XLS:
Make sure the ups* range in your XLS workbook is defined to include all rows you want to import, including the two header rows.
Please also be aware that XLS Import only adds records and does not update/overwrite what's already in there. If you want to change mappings/periods etc., you need to delete these records first and then add them again.
Export to XLS:
Your settings for export sound ok. Maybe there's an issue with the MIME Types on the web server - but I'm not too familiar with that, maybe someone else has an idea on this.
If you export to XLS a file should be created in Outbox\Excel (not during import, just want to make sure I'm clear on this).
Regards,
Matt

Reader XI installation exits without any error on XP

Hello,
I'm trying to upgrade Adobe Reader XI on Windows XP SP3 but the installer just exits without any messages after unpacking installation files. I tried both net and full installer (AdbeRdr11000_xxx.exe). Uninstalling Reader X didn't help, but I am able to reinstall it.
Any ideas what might be going on?

Try AdbeRdr11000_en_US.msi fromftp://ftp.adobe.com/pub/adobe/reader/win/11.x/11.0.00/en_US/
Make sure you are using .msi
After installation, select Help\Check for updates, and let Updater to install latest updates.

FIM multivalue attribute export to SQL - error 0x80230808

Hi,
Running FIM Synchronization Service v 4.0.3531.2 - Update1.
This instance is a simple setup, import from AD, export to SQL. I'm trying to export two multivalue attributes, one is a normal multivalue string, second is a reference attribute (member). My anchor is the GUID from AD in string format, perfectly fitting
into uniqueidentifier sql datatype.
Since I wanted to have the member values in the multivalue table also stored in a uniqueidentifier column (for further linking) I had to create two columns, one as "uniqueidentifier" and second as "text". FIM configuration went smoothly,
I defined a member multivalue reference attribute and selected the uniqueidentifier column as "String attribute column", and the other multivalue string attribute had to be linked as "Large string attribute column" and I pointed it to the
text datatype column.
Synchronization completed without errors, export step properly exported all multivalue string attributes to the text column, BUT when it came to exporting the GUID reference attribute to the uniqueidentifier column it exported only the first value showing
a "dn-attribute-failure" error. From the FIM GUI it was only showing the error number = 0x80230808.
I did a SQL trace to see what's going on. I re-run the export and saw FIM trying to delete all the values for this attribute multiple times with:
DELETE from [tblAD_Multivalue] WHERE [objectGUID] = N'{B011B424-5B2F-43A9-84C5-8605A570487B}' AND [attributeName] = N'member'
followed by doing cursor magic with the first value that was already added:
exec sp_cursor 180150007,4,0,N'tblAD_Multivalue',@objectGUID='B011B424-5B2F-43A9-84C5-8605A570487B',@attributeName='member',@guidValue='2E52A484-C7F6-49C0-AAC8-0A30C732A385'
After repeating the above for over 10 times it added a export_error_detail:
update [mms_connectorspace] set [export_error_detail] = N'<export-status>
<cd-error>
<error-code>0x80230808</error-code><error-literal>[Modify] Failed operation</error-literal>
</cd-error>
</export-status>
',[count_export_error_retries] = 0,[is_export_error] = 1,[initial_export_error_date] = '2011-02-12 21:36:08.995',[last_export_error_date] = '2011-02-12 21:36:08.995',[export_error_code] = -2145189885,[unapplied_export_batch_number] = 1,[unapplied_export_sequencer_number] = 2162572,[original_export_batch_number] = 1,[original_export_sequencer_number] = 2162572,[current_export_batch_number] = 4,[current_export_sequence_number] = 2216213 where ([object_id] = '6F5C98E3-38FF-4F32-95F6-B5A315B71D7A')
I tried manually adding one of the following values directly to SQL and it worked, so I'm not really sure what's wrong here.
Any ideas?
Piotr

Hi Markus,
yes, I know all about the architecture to allow multi-value attributes to be exported to SQL.
Everything works when I have just one string value column in my tblAD_Multivalue. The problem is that my anchor in the primary table is a GUID in a uniqueidentifier SQL column type (in FIM MV it's a string), so when I'm exporting multivalue reference attributes
to SQL I would like the GUID values also to go to a uniqueidentifier type column. That's why I set up the secondary column in the multi-value table with text datatype, so FIM recognizes it as a "large string column". I think I did everything within
the guidelines, so I was puzzled when I saw that error.
Consider this simple example, you're exporting users and groups from AD, you're anchor data type is uniqueidentifier, and you need to export the member attribute and the proxyAddresses attribute. What would you do to allow future SQL joins to calculate membership?
hope this explains a bit more this scenario, would appreciate any suggestions.
Piotr

Using XML Import/Export in Transport Connection

Hi, I was investigating the feasibility of copying a query definition from one BW system to another using the XML Import/Export functionality in Transport Connection. This is not to replace our current transport process across the landscape (Dev -> QA -> Prod), but merely just looking at possibilities for end users who develop queries in QA & then recreate them in Prod.
My question is: has anyone worked with the XML Export/Import for types Queries & Query Elements? I was trying this out between a Dev and Sandbox system and only had limited success. I was able to take a small query and perform the Export to a local .xml file without much difficulty. But when I try to do the Import, my query never shows up. The Import function shows a green light, but I get a couple of error messages on the Import such as the following:
==========================================================
SAP object 3WROG4HZ3NKP1PIYHCR1H24CQ () cannot be imported
Diagnosis
You attempted to import SAP object 3WROG4HZ3NKP1PIYHCR1H24CQ of type into the system via the XMI interface. However, you are not allowed to import SAP objects.
System response
The object was ignored during the import.
Note: It can be that the import is incomplete when the required SAP objects are still not active in the system.
Procedure
Install the specified objects from Business Content. Only import the metadata afterwards.
=========================================================
The portion returned for Saving and Activating returns green lights. The two sample objects mentioned appear to just be custom InfoObjects used in my query & don't look to be any different than others that work OK.
Just curious if anyone else has worked with this and could help advise.
Thanks... Jody

This is an old subject, but I think XML import only works for datamodeling objects like InfoObjects, InfoCubes, and ODS objects. If you try to export a query, and open the XML file in a text editor, there is not enough information (in my opinion) to build the query. As an example you don't see how key figures are to be displayed, filter or free characteristics.
However, when an InfoObject is collected, you get all the attributes, texts in all languages.
If anyone has more insight, please enlighten us.
-John

DataPump Import

Hi,
I am facing a small problem with datapump import, i exported a schema using datapump export(expdp) the same dump file i used for import using (impdp), once when the import is over i see all procedures,triggers and etc are all created with double quotes such as CREATE OR REPLACE PROCEDURE "ACCOUNTTRANSFERDETAIL_INSERT". So when doing a DataBase Difference these all comes as mismatch, so is there any way to overcome this error.
When i do a export and import in oracle 9i everthing was ok.
Now our QA team is doing a oracle 10g export and import (EXP & IMP) activities and i am using oracle 10g datapump for export and import (expdp & impdp) this is where we are facing problem. Comparison is between oracle 10g (exp & imp ) and oracle 10g datapump (expdp & impdp).
For their schema there was no double quotes and when i refreshed a schema using impdp objects where are enclosed using double quotes.
I also checked in data dictionary there also i see the object names enclosed with double quotes.
so i anybody has solution please revert back.
Thanks
Regards,
Ganesh R

Somehow I don;t think this is a problem with a download. You'll get a lot more eyeballs on your question if you ask in the right place.
Since Data Pump is part of the database, you might try asking your question in a Database forum (go up 2 levels and take a look at the screen).

DAtapump Import/Export Exit without errors

Similar Messages

Maybe you are looking for