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.

Similar Messages

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

SAP ECC error:'Migration Monitor' exits with error code 103.

Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha das

Hello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish.

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

Migration assistant + time machine error

Hi,
I just bought a new iMac 24" and was trying to migrate my data over. Upon starting the iMac, I chose the option of restoring using "time machine" backup. Migration assistant found my backup and I chose that and after a "calculation space" screen it started transferring the data over but it never ends. At the end of the whole process, the "progress" screen (with the progress bar) and the statement saying "Less than 1 minute to completion" (or something to that extant), it just stays there. Nothing happens, it says it is "moving files to link applications". I've done this 3 times, and the last was with a clean install of Leopard using the restore disc. All of them gave the same problem, at first I thought it was a time calculation error but after leaving the 3rd installation alone for 3 hours and it was still stuck on that screen, I think the system hung.
What is wrong?
The backup is on a partitioned 1TB firewire 800 HDD.
Any help would be appreciated.
Desmond

The exact error message when I select the Time Machine backup (which is displayed with yellow triangle on the hard disk) is 'Volume contains an OS X installation which may be damaged.'
The older iMac has the system on the built-in SSD and the applications and files on the internal hard disk whereas the new iMac is a fusion drive. I wonder if this is what the problem is, but I seem to recall reading somewhere that someone in a similar situation was able to use the migration assistant without any problem (can't find it now, though).

Migration Assistant says Network Error

I have a PowerMac G5 with 2 hard drives installed. I have 10.4 on drive A, and just installed 10.5 on drive B because it was a larger hard drive. I have done all updates after installation, and repaired permissions. When trying to use Migration Assistant, I keep getting an error which says: "There might be a problam with your network. The other Mac is not responding. Make sure that all of your network devices are connected and turned on. Also, make sure that your Ethernet cables are still connected properly to your computer and to the network, or if usign AirPort, that the base station is in range and turned on." I then have the option to Cancel Transfer or Continue. When hitting Continue, it runs a few minutes, and I keep getting the same error. Does anyone have any ideas?

I failed to mention that Drive B is partitioned. Might this be an issue? I would post a screenshot of setup if I knew how!

Forms migration assistant error

Hello,
I receive the following error when I run the forms migration assistant (f90plsqlconv.sh):
ERROR opening test.fmb :oracle.forms.jdapi.JdapiException: jniinitialize: Failed to create new forms context
I'm running 9iAS R2 on Redhat 7.3. Any help would be greatly appreciated.

Hi
1.Pls Copy all pll files & object Libray ,forms to a specific path e.g. c:\xyz
2.Add (c:\xyz ) to FORMS_PATH in the registry
3.Close/Open Forms Builder
4. Open the form
if not working..
Recompile the forms and re-attached the Library & Re-check the paths
Hope this helps...
Regards,
Abdetu...

HT4796 Trying to transfer files PC to Mac - when I press continue on PC Migration Assistant it states an error has occurred & quit button appears. I have disabled anti virus software & run chkdsk. Other methods also failed transferring data from iTunes et

New & frustrated Mac user - trying to transfer files PC to Mac must be easier than this? After unsuccessfully trying other suggested Help methods of transfering files from old PC to new MacBook Pro (eg iTunes files) tried Migration Assistant - when I press continue on PC, Migration Assistant shows message - error has occured in preparing data for transfer & quit buttion appears. I had already disabled anti virus software & run chkdsk.

Have you tried doing it the other way? Run Migration Assistant on the Mac? I haven't used a PC since 1995, so I can't help at all from the PC side.

Migration Assistant Issues and Tips

So I had to restore my MacBook Pro after it didn't shut down properly and wouldn't start up.
I'm using Lion, latest patches.
I wanted to share what I've learned in the event someone encounters a similar situation like I did.
I tried searching Communities but I couldn't find much that helped me out.
Operating system wouldn't load at all.
I am using a Time Capsule with Time Machine.
If you are trying to restore from Time Machine (and you had to reload the OS) I suggest reloading it after you've logged in.
When you are prompted to create a user account, do not create one with the same name you used before. Create a
temporary account and call it temp.
Use the temp account to restore only the Users first. Do not select any other options like Applications, Settings and Other Files.
(Doing this can leave you in the dreaded 'Transferring files to support applications' hanging forever state - I figured out what causes this which
I will explain later)
The restore of Users from Time Machine/Time Capsule was successful for me.
I then re-started my laptop and pressed the 'Option' key during start up to get in to the recovery drive. I am doing this only to access the disk
utility to 'Verify and Repair permissions'. - Which needed to be done as it reported some permissions needed to be fixed.
I then rebooted back into Lion.
I installed EACH section one by one.
I chose not to restore Applications. I have a list of all the programs I've installed - luckily - and I have the original disks so I can re-install them. I think you can restore Applications successfully despite what some people have reported/suggested.
The reason why I restored each item, Users, Applications, Settings, Other FIles, one by one is because I was running into an issue. I was running into an issue when I tried restoring all 4 options mentioned above.
I found out one of the things that causes the 'Transferring files to support application' status message to hang there forever. It would cause Migration Assistant to run and never completely shut down on its own. I opened up Activity Monitor and found that after Migration Tool and Migration Assistant are done their thing, a program called 'SHOVE' runs. And it runs FOREVER. It won't stop. It sucked up my CPU usage too. I also had my Console open and was watching 'All Messages', and I could see that SHOVE was doing something with temp files, but it was never stopping.
--- I believe restoring the option 'Other Files' is what causes the 'Transferring files to support application' hanging. So don't restore that. Or if you really want to restore it, open up activity monitor and watch for the SHOVE process. I co-related it with the Disk Activity tool, once I saw Disk Activity DROP, either flat line or become really low then that's when I Force Quit the SHOVE process.
If you use Activity Monitor to Force Quit the SHOVE process, then Migration Tool and Migration Assistant will finally say that everything has been restored - BUT BUT BUT. It doesn't do so if you tried to restore everything all at once. Even after I rebooted. You MUST restore each item separately.
After I used Activity Monitor to force quit the SHOVE process, I noticed in my Console/All Messages reported that Migration Assistant exited properly.

BA88 wrote:
Hi,
Hi and welcome to the forums.
What I am trying to do is migrate all of my old stuff, from a hard drive image on an external hard drive (firewire).
How was that made? Is it really an image, or a backup of some sort (Time Machine, CarbonCopyCloner, SuperDuper, the Restore tab of Disk Utility, etc.)?
I get a network error. I have tried migrating whilst still in the boot mode on the OXS DVD
That's via +Setup Assistant+ when it first starts up, per [Using Setup Assistant|http://web.me.com/pondini/AppleTips/SetupAsst.html]?
I don't understand why you're getting a network error if you're migrating from a FireWire drive. Are you sure the connections are snug and secure? Have you tried a different FireWire cable?

Migration assistant won't launch

Hi there,
I recently purchased a new Imac 2.66ghz and want to import all my data off my old eMac 1ghz.
The firewire ports on the eMac don't work, so I was wanting to transfer it over ethernet.
I know I can use Migration Assistant to do that, but when I try to launch it on the old computer, it bounces in the dock a bit, then quits.
I had a look in the package contents within Migration Assistant, and tried to load it from within the MacOs folder. I got a telnet style window with the following text:
Last login: Sun Jun 1 09:25:56 on ttyp1
/Applications/Utilities/Migration\ Assistant.app/Contents/MacOS/Migration\ Assistant; exit
Welcome to Darwin!
Lachlan-Gilberts-Computer:~ lachlangilbert$ /Applications/Utilities/Migration\ Assistant.app/Contents/MacOS/Migration\ Assistant; exit
dyld: /Applications/Utilities/Migration Assistant.app/Contents/MacOS/Migration Assistant can't open library: /System/Library/PrivateFrameworks/Assistant.framework/Versions/A/Assistant (No such file or directory, errno = 2)
Trace/BPT trap
[Process completed]logout
I don't have the knowledge to know what to do next. Can somebody please help?
Many thanks.
Lachlan

Hi Lachlan,
To use the Migration Assistant, you do need a Firewire connection.
ali b

Error "The Connection Failed" in Time Machine, Migration Assistant and Restore From DVD

I am receiving this error when trying to connect to my Time Machine Backup in my Time capsule. I input the proper password to access my Time Capsule and It returns me to the screen with the caption "The connection failed" under the Time Capsule name in the "Select your Disk" screen. What would cause this error. I am connecting via WIFI (AirPort) and have full signal. I am using Mac OSX 10.6.8
I recently had my 1TB hard drive replaced and I am attempting to restore using Time Machine, migration assistant or from the startup dvd (tried multiple ways, no success). The initial setup of mac OSX 10.6 would not let me connect or other attempts after erasing hard drive and reinstalling OSX from disk.
Worked on it all weekend and don't have enough beer to drown the frustration, any help is appreciated.

You are correct TM is not at all easy to do a full restore.
To answer your question: Yes TM disk does show up in finder.
After my initial startup setup I was able to start TM and access all my previous backups. I migrated some files and was able grab the data from finder. Not satisfied with that I tried to do a restore to that previous date, to no success. I then erased the HD and reinstalled OSx and tried again from the setup screen. That didn't work, sulked over some beers. I then tired with Migration assistant...same result (more beer).
In starting TM after trying MA, only one backup was showing in the Star screen (today). None of my previous backups were showing. Since exiting TM it has been "Making Backup Disk Available" ( xGB of 6.29GB). Considering the size, I can only assume that these are my previous backups.
I have reviewed Pondini's posts, FAQs, and tutorials. I am a little scared to try and locate the drives through Terminal as in Pondini's TS #6 guide. If I can get my previous backups to show up, I will be happy with dragging files from Finder to restore my data and slowly work at restoring my settings/applications.

I'm trying to use migration assistant to transfer applications from my imac to macbook. Using either a firewire or network, as I'm waiting to select items to migrate, I receive an error message that "the application quit unexpectedly". My imac is newer.

I'm trying to use migration assistant to transfer applications from my newer imac to an older macbook (10.5.8). I keep getting an error message "application quit unexpectedly" as I'm waiting to select the items to migrate. I've tried using a firewire cable as well as just a network connection.
Thank you.

Here is some information:
http://support.apple.com/kb/HT4889
It mentions that migration is not supported with 10.4; now you said you have 10.5 - it may be the same problem. Besides, migration assistant will recognize an older system and move apps etc. over to a newer system - I'm not sure it will do the same thing in reverse.
And, there are a couple more problems: one is that your newer versions may not be backwards compatible with the old 10.5 and the second is that is you are trying to copy apps so you can use them on both, it most likely violates the SLA (unless you purchased them on MAS).
So, if none of those two apply, I'd simply try target disk mode (without the assistant) and drag over the apps.

Migration Assistant Error Some files from ".journal" could not be transferred?

Hello, world.
A few days ago I replaced my the 97% full 100GB hard drive in my Dad's Core Duo 2.0GHz Macbook Pro with a 500GB but I received an ominous error at the end of the Migration Assistant transfer. Here are the steps I took:
1. Replaced physical drive.
2. Booted up from OS X Snow Leopard disc.
3. Formatted new drive as OS X Journaled using Disk Utility.
4. Installed OS X Snow Leopard on the new drive.
5. When prompted by OS X Installation, I selected transfer data from another volume.
6. Placed the old drive in an enclosure and connected via USB.
7. At this point I let Migration Assistant take over.
It took an hour and a half or more to transfer the data and everything SEEMS fine. However, at the end I received the following error message from Migration Assistant:
Errors and Warnings:
- 2013-11-02 16:15:49 -0400 Some files from ".journal" could not be transferred
- 2013-11-02 16:15:49 -0400 Some files from ".journal_info_block" could not be transferred
I have searched around but I've been unable to find any information on this. In other instances of these warnings, people seemed to be pointing the finger at moving from PowerPC macs to Intel Macs but this was Intel-->Intel.
I did find someone suggest one other thing in another thread:
"My reading of those error messages indicates that there's something wrong with the journaling files on the PB. I suggest that you disable and reenable it on the PB"
However, I do not know how to enable or disable journaling without reformatting the drive from scratch as journaled or non-journaled.
(post found here: https://discussions.apple.com/message/8675337#8675337)
Question: Should I be worried and does anyone know specifically what this error indicates? Is it possible that my dad's old hard drive was NOT formatted for journaling and MA was looking for these journal related files and unable to find them?
Thank you all in advance for your help,
Nick

What options did you select for Migration Assistant to transfer? For instance, did you select network & computer settings?
"Opt" sounds like the name of a folder, not a file type. On your 13" MacBook, do you have any folder by that name, especially in your home folder?
Also, have you run Disk Utility's *verify disk* check on the MacBook's drive?

3008 or 8003 error, migration assistant file deletion

how can i fix getting a 3008 or 8003 error when trying to delete trash can? I deleted files after using migration asistant. I accessed my machintosh hd and clicked users and drug the new username file to the trash when I tried to delete the trash the 3008 error came up. i back up my computer with time machine and have found some posts on this happening when you try to delete a backup file.

The exact error message when I select the Time Machine backup (which is displayed with yellow triangle on the hard disk) is 'Volume contains an OS X installation which may be damaged.'
The older iMac has the system on the built-in SSD and the applications and files on the internal hard disk whereas the new iMac is a fusion drive. I wonder if this is what the problem is, but I seem to recall reading somewhere that someone in a similar situation was able to use the migration assistant without any problem (can't find it now, though).

How do I transfer my home folder to my server without migration assistant?

I am having a hard time migrating my user folder to my mini. My wife is the first user account, but I want to put my account on there as well. Without migration assistant, I am not sure how to do it?
The Apple Genius guy told me to just copy my home folder to the "users" folder on the mini,
then go to "system pref's" and "create a new user that "exactly matches the name on my copied data, especially the short name.
At this point it is supposed to ask me if I want to "link" the accounts and I say yes, however, I can't get to this point.
Everytime I try to copy the home folder over, I can't drop it in the user folder. If I try to copy to the desktop or other folder only some data will transfer. It is obviously a permissions issues. I have selected my user folder, "get info" and I "applied to enclosed items" but I am not familiar with permissions like this. I remember the "ignore permissions" option.
So there ya go? How would you guys do this?

The permissions associated with the Users folder are those of the admin user. I suggest you try using the Terminal in your Utilities folder. You should first boot the computer into the main admin account. The command line would look something like this:
sudo cp -a /Users/useraccount /Volumes/volname/Users/useraccount
Press RETURN. Enter admin password when prompted. It will not be echoed to the screen. Substitute your account name for useraccount, and the name of the mounted drive on the Mini to which you want to copy your user account for volname.
The above command will copy your Home folder into the /Users/ folder on the other computer. Now, there may be a better solution for you, but you haven't told us about the other computer from which you are trying to migrate. If both computers have Firewire ports then there is an easier and faster solution.

Migration Assistent Exits without Error?

Similar Messages

Maybe you are looking for