Imp utility hanging

Hi there,
I have successfully exported a schema using the oracle exp utility, and I am trying to import the export file into another schema, is runs fine, upto a point, and then just hangs on a particular table, the table in question uses the standard data types, and was exported successfully. Anybody know how I can find out what the problem is? Thanks... Anil

aparm wrote:
Hi,
Sorry for the delayed response, the contents of my param files are as follows
fromuser=MY_SCHEMA
touser=DEST_SCHEMA
file=MY_SCHEMA.dmp
commit=Y
ignore=Y
log=MY_SCHEMA.log
I didn't see anything in the alert log.
The import table has 33867 rows and no long datatypes.
I haven't used impdp because there are some tables that contain long fields.
Any further insight would be useful, thanks...If it were a big table I would suggest trying it without the indices, but that is a pretty small table. You should have an alert file somewhere that you should look at to see if it is giving any errors like you've run out of space or something. I'm not on windows but I would guess the file would be named something like app\oracle\admin\<SID>\bdump\alert_<SID>.log where <SID> is your instance name. Also set the feedback parameter, that might tell you if it is really hung.

Similar Messages

Using Imp utility to Import a database on 10g release 2

I am using the Imp Utility on 10g release 2 to import from a 10g release 1 database. I have created a new tablesapce and need the dmp to be imported to the new tablespace. But it goes and imports to the system tablespace. The command i use is
imp <User name>/<password> file=<file_name> log =<log name> full=Yes
the user name and password i use is the username and password i gave in the installation for system tables. When i specify the tablespace imp <User name>/<password>@<tablespace> it comes with "ORACLE error 12154 encountered".
Do i need to create a new user to get the import done. How do i create it?

The contents of the dump will be imported to the tablespace under which you run the import.
If your dump from Oracle 10G R1 is a complete database dump and you need to import the data of a specific user in the dump, then you can use fromuser= touser= options in the import command.
If your Oracle 10GR2 database is blank, then you need to create the user in which you can import the data. You can use a command like this.
CREATE USER sidney
IDENTIFIED BY out_standing1
DEFAULT TABLESPACE example
QUOTA 10M ON example
TEMPORARY TABLESPACE temp;
Note: sidnye, out_standing1, example, temp are all arbitrary names. You need to match these with your environment.

Disk utility hangs MAC G4?

Why does Disk Utility hang when starting? ~ Doug

Hi, Doug.
A little more detail on how you are launching Disk Utility on the stated "G4" would help. Some more details about the specific G4, and the problems that may have led to you attempting to run Disk Utility on it would also be useful.
Try running steps 1-2 of the Procedure specified in my "Resolving Disk, Permission, and Cache Corruption" FAQ.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Disk Utility hangs ("not responding") when attempting to Repair Disk on Time Capsule sparsebundle. Help.

I am trying to improve the performance of my Time Machine backup and retrievals via my 2nd Gen. Time Capsule from my iMac Core 2 Duo hard drive with SL 10.6.8. The incremental backups generally take 20 - 40 minutes each hour generally with fewer than 100 MB of data being backed up. I have read through numerous threads on these forums about Time Capsule and Time Machine issues as well as the very helpful Pondini site (http://web.me.com/pondini/Time_Machine/Home.html) and have tried many other suggestions (listed below), but have been unable to attempt a Disk Utility repair disk on the Time Capsule sparsebundle file.
After locating the sparsebundle 'file' in the finder under Shared/TC/Data, I am only sometimes able to drag the sparsebundle into the Disk Utility volumes and disk window. About fifty percent of the time, Disk Utility hangs when attempting to drag in the sparsebundle. If I am able to get it listed and click on "repair disk", then the beach ball begins to spin and nothing happens. This occurs whether or not I first use AirPort Utility to "Disconnect All Users" from the Time Capsule. I have given it over one hour to attempt the repair disk, but nothing happens, i.e., not a single message shows up in the detail window. The beach ball just spins, and Disk Utility shows up in red as "not responding" under the Force Quit menu.
Also note that on my new Macbook Air, Time Machine runs quite quickly via this same Time Capsule from my new Macbook Air using OS X Lion (which seems to indicate that the Time Capsule drive itself is OK).
I would appreciate any tips on getting Disk Utility to run "repair disk" on my sparsebundle, as I seem to have exhausted most other options (see below) for improving Time Capsule performance -- aside of course, from wiping the Time Capsule clean and starting all over.... (which I really don't want to do, and from what I've read, has not helped some people who've tried this anyway).
Many thanks!
Although I would like to focus this thread on the Disk Utility / sparsebundle "Repair Disk" problem, I should mention that I have tried the following other things:
1. Repaired disk permissions on my hard drive
2. Used Disk Utility to run "repair disk" on my hard drive after starting up from a SuperDuper external backup
3. Run DiskWarrior on my hard drive, again, from a separate startup disk
4. Did the "full reset of Time Machine", a la Pondini Troubleshooting #A4
5. Changed my computer and Time Capsule names to simple short names with only alphanumeric characters and no spaces
6. Ensured that my Time Capsule is being accessed only via ethernet
7. Relaunched the finder
8. And finally, attempting to use Disk Utility to repair the sparsebundle - thus the nature of this post

OK, no takers out there, but I answered my own question (sort of).
The answer is that even though Disk Utility shows up as "not responding" under the Force Quit menu and appears to hang, it is actually still working. A bit of patience shows that after about an hour, my Disk Utility was able to show the 1.44 TB Time Machine sparsebundle from Time Capsule in the disk window on the left hand side. Once this appeared, I was able to click on "Repair Disk" (note that prior to doing this, I had to "Disconnect All Users" from my Time Capsule using the Airport Utility program; otherwise you will get a "could not unmount disk" error). Again, the Repair Disk function appeared to hang Disk Utility as it showed up as "not responding" under the Force Quit menu. However, after about 8 hours, Disk Utility did run the entire Repair Disk protocol on the sparsebundle. The results DO NOT show up in the Disk Utility details window - so even if you are patient enough to let it complete, you will not see anything and may think that nothing happened. However, you can find the familiar results of the Repair Disk function by looking on Console - find the "DiskUtility.log" under Files: ˜/Library/Logs.
Unfortunately, I was hoping to find a problem that would have been subsequently repaired which would result in dramatically increased Time Capsule speed, but this was not the case. Disk Utility showed everything to be "OK" and I am stuck with a very slow Time Capsule....
(And of note, my new Macbook Air (OS Lion) Time Machine functions blazingly fast on both backup and retrieval to and from the very same Time Capsule - even though, these are occuring wirelessly via AirPort -- granted the size of this sparsebundle is an order of magnitude smaller at this point, i.e., only 10 GB right now)
Would still be happy to hear of any similar experiences or tips on getting Time Capsule to work more quickly.

Disk Utility Hangs during format

Yes, I've seen a hundred other posts on this but all have been archived with no solution.
It seems very likely there is a 10.4 problem. When I try to format a 160GB drive connected via USB Disk Utility hangs and never completes. I have tried to partition it as well with no luck.
Is there a fix? Is Apple working on the problem? Is there a workaround? Even a commandline fix would be acceptable.

This is ridiculous. I have tried 4 different physical drives in 4 different physical enclosures (3 different brands) and it still hangs Disk Utility.
I know I'm not the only one with this problem. What the **** is going on? I can't format a disk and therefore I can't use it. This is absolutely unacceptable.
Sometimes my machine hangs in such a way that I can't even reboot it, it requires a physical power down.
I have been forced to format these on a Windows machine with FAT32 (using a 3rd party app to get past the GB limitation MS sets). I don't want FAT32, I want HFS+. But I can find no other way to do this in Tiger as it ALWAYS hangs regardless of drive, enclosure, filesystem type, size, number of partitions, etc, etc.
Is OS X truly this bad that it can't even format a drive properly? Am I really going to have to rely on Windows and FAT32 whenever I want to format?

Disk utility hangs during disk verify

Initially 'disk verify' registered errors on exit - minor error/issue it said,some kind of header problem, so I ran disk utility off the install disk. Now the machine's native version of disk utility hangs during disk verify, blue & white spirals forever.
This coincidentally straight after my gmail/google address/account was hacked a couple of days ago.

Have you tried booting in SafeBoot mode (shift key held on start
until login screen appears) then launch Disk Utility and then run
its 'repair disk permissions' item, selecting the Macintosh HD;
and then note the repair window. It should fix something.
And when Disk Utility is done, quit it, and restart the Mac normally.
{...It is unlikely something from gmail affected your computer unless
you open up unknown sourced emails or go to odd web sites where
something may be downloaded from there, which you would almost
have to install (as admin, etc) for malware to work. You can get and
try ClamXAV for free to see if it sees any malware virus content.}
If you use Gmail, and do not log in using the https:// (secure http)
you should change the habit and bookmark the secure login site.
And when booted from the Installer disk and running Disk Utility
from there, see about running "repair disk" and not verify. The
repair choice will verify; but verify will not repair. Could be if
you cannot use the Utility to Repair the issues, and the other
SafeBoot mode and the computer's Disk Utility to get it working
you may need to further troubleshoot and/or get third-party tools.
In any event...
Good luck & happy computing!

Disk Utility hangs up

Running a G5 IMac with 10.5.1. Tried to repair permissions and Disk Utility hangs up at about 25% of the way through the process. Ran Disk Warrior. Still hangs up. Started up form Leopard Install and tried to repair permissions. Still hangs up. Otherwise the system seems to be running OK. Any help or thoughts would be appreciated.

Disk Warrior is NOT compatible with Leopard at this time.
I would not use my Disk Warrior.
Permissions take from 10 to 30 minutes with 10.5.1
Give it time.
It seems like it just sits there on "Less than 1 minute" but it will eventually finish.
Again, give it time.

Disk Utility hangs attempting to erase SimpleTech 100gb external USB disk

I'm attempting to erase and format a SimpleTech 100gb external USB disk. Disk Utility hangs. The system error log says:
"AppleUSBEHCI[0x1d59000]::Found a transaction past the completion deadline on bus 91, timing out!
Jul 21 17:30:35 Kari-Hohnbaums-Computer-2 kernel[0]: USBF:"
The console log (and Disk Utility log) shows:
Preparing to erase : “PBEX1”
Creating Partition Map
error writing partition map: Device not configured (6)
Disk Erase failed with the error:
What is the problem? This disk is recognized by Tiger but only as read-only as it ships as an NTFS volume and must be erased and reformatted before it can be used by a MAC.
All help appreciated.

I tried the partition approach and it unfortunately failed as well. The same "hung" symptoms as before. The green light (disk activity) on the disk flashed several times at the initial request, but that was all. I eventually interrupted it after a hourn which generated the same system log message: AppleUSBEHCI[0x1d59000]::Found a transaction past the completion deadline on bus 91, timing out!
The disk utility log says:
Preparing to partition disk: “SAMSUNG HM100JC Media”
Partition Scheme: Apple Partition Scheme
Mac OS 9 Disk Drivers installed
1 partitions will be created
Partition 1
Name : “PBEX1”
Size : 93.2 GB
Filesystem : Mac OS Extended (Journaled)
Creating Partition Map
Partition failed for disk SAMSUNG HM100JC Media Device not configured
Partition complete.
I don't have easy access to a Window's box. I do have access to a Linux system. Perhaps I can configure it there and it will work on my PB.

Disk Utility hangs when erasing external disk

In Time Machine I wasn't able to figure out how to attach an external drive via USB. I guessed that it probably wouldn't work on a MS-DOS filesystem, so I started Disk Utility, which I never have used before. I have formatted disks before on Linux and on Windows, so it's nice to see a great app for this.
In the Time Machine brief help text, there is not mentioned what kind of filesystem that is required or if it work with any filesystem. So I searched, and it seems as if HFS+ journaled case-insensitive is the filesystem that one should choose. Can anyone confirm this?
When I click erase then the Disk Utility program hangs and I see the spinning beachball. The Activity Monitor program shows that disk activity stops after a few seconds. There is no more activity, so after 5 minutes I stop the program.
I have tried several times, and I see the same behavior. I even tried restarting the computer. But no luck.
Now my external disk no longer shows that it's a MS-DOS filesystem, but shows that it's HFS+ journaled case-insensitive. Probably not ok so far. I try creating a single patition, with format: HFS+ journaled case-insensitive, without OS 9 drivers installed. When I click apply then spinning beachball again and diskactivity stops after a few seconds, and I stop the program after some minutes where it has been inactive.
My guess is that the disk-erasing task failed and has left the disk in a broken state. During this task Disk Utility began to hang for a reason that I don't know.
My second guess to why the create-partition task failed, is that the disk is in a broken state, and thus the partition cannot be created, and Disk Utility hangs.
How do I format the external disk from the command line?

In Disk Utility, select the drive mechanism (not the volume on it) and click the Partition button. Use the Options button to choose the GUID partition scheme, then make one HFS+ (Journaled) volume.
There is no point in using the command line for this task, because if Disk Utility cannot deal properly with the disk, Mac OS X will not either. Disk Utility is using diskutil to do the partitioning and formatting.

ORA-01435: user does not exist when using imp utility

I installed Oracle 8.1.7.0.0 successfully on WINDOWS 2000 and created a database TEST using DBCA. Then I used a script to creat a tablespace and a user in TEST databse. I could use the imp utility to import the data (a dmp file) to the TEST database without any problem. But after I applied a patch to bring up the version to Oracle 8.1.7.4.1, I got the following error when I tried to use the imp utility again to import the data (a dmp file) to the TEST database.
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
IMP-00000: Import terminated unsuccessfully
I checked that I created the same user test (as it is in dmp file I wanted to import) on TEST, and I could login to TEST using:
sqlplus test/test@TEST
The command I used is:
imp system/password@TEST file=test.dmp full=y log=importTEST.TEST.tmp
I also tried to use the following command:
imp system/password@TEST file=test.dmp fromuser=test touser=test log=importTEST.TEST.tmp
and got the same error as before.
Anyone has any clues what could go wrong? The only difference for me to import the data on TEST is that the
previous successful import was done in Oracle 8.1.7.0.0.
Is it possible that I missed something during the applying of the patch 8.1.7.4.1?
Thanks, and your help is greatly appreciated.
Jane

Ther is a set of instruction to be followed after installing the patch set 8.1.7.4.1 after running it thru OUI.They are as follows. Please complete these steps and u should not have problems any more.
When applying this patchset on Windows NT and Windows 2000, you must log onto the system as a user with Administrative privileges (e.g., as a user which is a member of the local Administrators group).
1.Disabling system triggers.
Before performing the next step, you must first set SYSTEMTRIG_ENABLED = FALSE in the initialization parameter file. To do this add the following line to your init<sid>.ora file and restart the database (see Note 149948.1 in Metalink for more information on this issue).
systemtrig_enabled=false
2.Invoke SQL*Plus (sqlplus), connect as internal and run the following:
select * from duc$ where PACK='JIS$INTERCEPTOR$' ;
If no rows were returned go to the next step. If a row was returned delete it using the following:
delete from duc$ where PACK='JIS$INTERCEPTOR$' ;
commit;
3.Invoke SQL*Plus (sqlplus), connect as internal and run the following SQL scripts with event 10520 set. NOTE: This event is not intended for regular database operation and when turned on below by the 'ALTER SESSION' command will automatically be turned off by the subsequent 'CONNECT' command.
ALTER SESSION SET EVENTS '10520 TRACE NAME CONTEXT FOREVER, LEVEL 10';
?/rdbms/admin/catalog.sql
?/rdbms/admin/catproc.sql
?/rdbms/admin/catrep.sql (This only needs to be run if you are using symmetric/advanced replication. This is not necessary for sites using dblinks and read-only snapshots if symmetric/advanced replication is not installed)
CONNECT / AS SYSDBA;
update obj$ set status=5 where type#=29 and owner#!=0;
commit;
4.You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install.
If Java has previously been loaded into the database, invoke SQL*Plus (sqlplus), connect as internal and run the following SQL DDL command(* Note:If Java has not previously been loaded into the database, skip this step).:
SQL> create or replace java system
2 /
(Note that the / (slash) is important to ensure the execution of the command).
To ensure the correct installation of the XDK in the database run the following 2 scripts (Bug 2115227):
$ORACLE_HOME/oracore/admin/initxml.sql
$ORACLE_HOME/rdbms/admin/catxsu.sql
* To determine whether Java has previously been loaded into the database:
invoke SQL*Plus (sqlplus), connect as internal and run the following:
SQL> select count(*) from all_objects where object_type like 'JAVA%';
Java is installed if you get a non zero result returned from the query.
5.You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install:
If Java has previously been loaded into the database, invoke SQL*Plus (sqlplus), connect as internal and run the following scripts which are located in $ORACLE_HOME/javavm/install ( Note: If Java has not previously been loaded into the database, you can skip this step):
load_jis.sql
jisja.sql
initjsp.sql
jspja.sql
Notes:
When running the $ORACLE_HOME/javavm/install/jisja.sql script the following error may be reported and can be ignored:
call jis_exit_java_session(0)
ERROR at line 1:
ORA-29515: exit called from Java code with status 0
Bug 1459233 was filed against this problem which is fixed in 9i.
6.If you deleted a row from duc$ in step 8 then reinsert it again. Invoke SQL*Plus (sqlplus), connect as internal and run the following SQL:
insert into duc$ (OWNER, PACK, PROC, FIELD1, OPERATION#, SEQ) values ('SYS', 'JIS$INTERCEPTOR$', 'USER_DROPPED', 0, 1, 1);
commit;
7.Enabling system triggers.
You must either remove SYSTEMTRIG_ENABLED from the initialization parameter file or explicitly set it to TRUE before attempting any other patch set post-install steps. Restart the database.
8.This step is optional - it will recompile all invalid PL/SQL packages now rather than when accessed for the first time - you can also use utlrcmp.sql to parallelize this. Invoke SQL*Plus (sqlplus), connect as internal and run the following SQL script:
?/rdbms/admin/utlrp.sql
9.Execute the following steps only if you have installed Oracle interMedia Text in the database you are attempting to modify:
If you have not previously unlocked the ctxsys account and supplied a password for that account, you need to do so. (If you have needed to use Oracle Text in any way prior to applying the patchset, you will have already performed this step, and you can skip this.) Do so by issuing the following statement:
ALTER USER ctxsys IDENTIFIED BY <passwd> ACCOUNT UNLOCK;
If you have already installed 8.1.7.2 or 8.1.7.3, go directly to step 7 below.
If you have already installed 8.1.7.1, go directly to step 5 below.
CONNECT ctxsys/<passwd>;
@?/ctx/admin/upgrade/u0801071.sql
CONNECT ctxsys/<passwd>;
@?/ctx/admin/upgrade/u0801072.sql
CONNECT / AS SYSDBA;
@?/ctx/admin/upgrade/s0801074.sql
CONNECT ctxsys/<passwd>
@?/ctx/admin/dr0pkh.sql
@?/ctx/admin/dr0plb.sql
@?/ctx/admin/dr0type.plb
@?/ctx/admin/dr0typec.plb
9.You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install:
The installation of this patch set fixes a potential security hole in the XSQL Servlet - see here for more detail. The patchset installation does not, however, modify any of the Oracle HTTP Server configuration files to reflect changes to the XSQL Servlet installation. If you have previously installed the Oracle HTTP Server, you will need to update one of the configuration files manually after the patchset installation is complete. If you do not do so, the XSQL Servlet may not work in the context of the Oracle HTTP Server after the patchset is installed. To update your Oracle HTTP Server configuration, perform the following steps:
1) Edit the file: $ORACLE_HOME/Apache/Jserv/conf/jserv.properties
2) Search for the string: "XSQLConfig.xml File location"
3) Modify the parameter wrapper.classpath on the line immediately following the above string to read: $ORACLE_HOME/oracore/admin
4) Save the file.
10.You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install:
The installation of this patch set fixes a potential security hole in the PL/SQL XML parser - see here for more detail. To load the new XML parser in to the database, run the following script as user SYS:
? /xdk/plsql/parser/bin/load.sql
11.If you are using the RMAN catalog then upgrade it as follows:
rman catalog <user/passwd@alias>
upgrade catalog;
upgrade catalog;
The post install actions are now complete and the database is now ready for use.

The imp utility fails to import triggers

After making a complet export of a user of Oracle 10g Database, data, procedures and triggers, when trying to import the user to a other database ,with the imp utility, all go fine except the triggers and some procedures. Â¿Why? Because ,in anyway, the imp or the exp utility, I dont know, append the character '"' at the end of the lines.
I think that maybe it can be by the NLS, because the imp utility say me, 'the export was done in USS7ASC and ALFT16.. and the import is weiso8859...'. But I dont know.
Â¿Any Help?.
Thanks in advanced.

Hi,
. . importing partition "BERICHTSWERTE":"BRW IMP-00058: ORACLE error 1502 encountered
ORA-01502: index 'ODS.BRW_PK' or partition of such index is in unusable state
Import terminated successfully with warnings
It seems u have some indexes on this partitioned which got disabled becuase of your above DDL .
The solution would be to DROP the specified index, or REBUILD the specified index, or REBUILD the unusable index partition.

Disk Warrior/Disk Utility Hangs with External HD

okay, so i will try to make this as quick as possible.
last year, i had an external hard drive that i had been saving all my audio work on. one day i had to restart (i was having a lot of problems with my then IBook G4) so i did, and the drive was no where to be found. made sure there was no connection problems (ie my USB ports) and everything seemed fine. let it sit for a while, thinking maybe it was just tired or something. tried again, same story, and it also made disk utility hang. tried it on a friends mac, same issue.
i also had a a lot of video/music that i watched with my xbox 360. i could still access those files with the xbox, which was weird.
so then my ibook eventually died, and here i am with a newer G5 quad. i tried it again, and still the disk utility hangs, and ive also tried Disk warrior 4. this also hangs.
also, i have tried switching the enclosure to no avail.
its not the end of the world if i cant get the data back, but i would REALLY like to.
any suggestions?

System Profiler shows the same thing: "Manufacturer: PI-236" for each of these HDs. I'm not sure how to rename these drives (I'm not talking about the partitions on them, which I've given descriptive names).
The strange thing is that on my MacBook Air (upgraded to Lion) one of these HDs (now connected via USB) shows up in Disk Utility as "Ext Hard Disk Media" instead of "PI-236". Still not a whole lot of information, you'll notice.
Another external HD (partitioned earlier under Snow Leopard) is shown correctly as "SAMSUNG HD501LJ Media" on both computers.

Disk Utility hanging on all user accounts

Hi,
I suspect that my son applied new permissions to enclosed items somewhere and that this is the reason that Disk Utility hangs (doesn't respond) when I start it. As a remedy I repaired permissions while started from an external disk and then applied some command lines that I learned for resetting user account permission (http://discussions.apple.com/thread.jspa?threadID=1655174&tstart=0). But still DU is unresponsive and must be force quit. Additionally I cannot open the DVD tray and Firefox tells me "...update available but you do not have the systems permissions required to install it....".
So I think my user permissions reset was not successful. My question is: did the command line language change from Leopard to SnowLeopard because Terminal gave me some feedback that "-H makes sense only with R" or something to that effect.
Do you have any idea about these things? What's the best way to proceed? Thanks.

Has command line language changed in SnowLeo compared to Leopard?
There are a few changes that reflect the differences between the two OS versions but the vast majority of commands are the same. There are hundreds of commands. Including the flags, switches, & options available for them there are thousands of variations. Plus, characters like spaces, slashes, dashes, & quote marks have special meaning depending on where they appear in the command line so even a minor typo can dramatically change a command into something other than what you want.
Because of this, you should not use a command unless it is specifically recommended for an issue you have explained completely or you have at least a fundamental understanding of command line syntax & the options for a command you are going to use. Each command has a manual page ("man page" for short) that you can access in Terminal by typing the word "man" followed by a space followed by the command name. For example, try "man man" to see the manual page explaining that command.
It would help greatly if you could provide the exact command & flags you used, plus any error messages they generated. Also, "standard procedures" doesn't tell us much since different users consider different things standard.
I suspect your problem is not caused by mis-set permissions, although they may have lead to the condition that caused it. But without more info it is hard to say what the problem is or how to fix it. It might be simplest just to reinstall the OS (which for Snow Leopard is not that big a deal), let Software Update bring it up to current versions, & then deal with any remaining user level permission issues separately.

Disk Utility hangs during DMG file creation

I use disk utility to create DMG files from folders (with the corresponding command from the File -> New menu). Every now and then (and quite often, really), Disk Utility will not complete this process, but instead hang forever. It seems that something in the kernel gets stuck, because the machine can get increasingly unresponsive after the hang has started (for instance, I wanted to look in the system log right now, but running less on /var/log/system.log would create long hangs on the whole UI). The only way out is a reboot.
The machine is otherwise very stable.
(Ah, and Time Machine started at the same time now, and doesn't seem to be able to run - maybe disk utility and time machine are creating some deadlock situation?)
Anyone who has seen similar behaviour?

I haven't had this issue this since upgrading to Snow Leopard, so I assume it has been fixed.

Disk Utility hangs

My drive is partitioned into 3 logical drives.
1 - boot and appliactions (Disk Utility repairs permissions OK)
2 - CD scratch disk - Disk Utility verifies the disk OK
3 - data - Disk utility displays Verifying Disk Data but then hangs with no activity. Error log says that D cannot be unmounted.

Sounds like there's some file that's being used on the third volume. Try this. Restart, launch Disk Utility, select that volume, and click on the unmount button. If that works, then select the volume, select File->Mount Volume, and repair the volume.

Imp utility hanging

Similar Messages

Maybe you are looking for