CLOBs corrupting on import

Would anyone be able to help me with this one. I'm trying to import from a .dmp file and I'm getting this message ...
Export file created by EXPORT:V09.00.01 via conventional path
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
export client uses US7ASCII character set (possible charset conversion)
The import is successful but the CLOBs are messed up, displaying question marks ('???')
I've tried changing NLS_LANG a couple of times, but just get variations on the same error
Export file created by EXPORT:V09.00.01 via conventional path
import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses WE8MSWIN1252 character set (possible charset conversion)
Does the import server refer to the character set of the database? If so, do I have to convert my entire database to import this data? If that's the case, I understand from documentation that I can't use the ALTER .... CHARACTERSET to do this and have to do a full export/import .... not clear on this .... how do I convert character set before re-importing? Is there any easier way of importing this .dmp file?
Any help hugely appreciated,
Mary

This is what I got on my Linux test machine :
[ora102 mvdemo db102]$ imp mvdemo/mvdemo file=mvdemo.dmp full=y ignore=y
Import: Release 10.2.0.1.0 - Production on Mon Dec 18 18:29:32 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V09.00.01 via conventional path
import done in WE8ISO8859P15 character set and AL16UTF16 NCHAR character set
export client uses US7ASCII character set (possible charset conversion)
. importing MVDEMO's objects into MVDEMO
. importing MVDEMO's objects into MVDEMO
. . importing table                       "STYLES"        274 rows imported
. . importing table                       "THEMES"          9 rows imported
. . importing table                         "MAPS"          4 rows imported
. . importing table                       "CITIES"        195 rows imported
. . importing table                     "COUNTIES"       3230 rows imported
. . importing table                    "EMPLOYEES"         14 rows imported
. . importing table                  "INTERSTATES"        239 rows imported
. . importing table                       "STATES"         56 rows imported
. . importing table                  "TERRITORIES"          9 rows imported
. . importing table                "TERR_COUNTIES"       3230 rows imported
Import terminated successfully without warnings.
[ora102 mvdemo db102]$ sqlplus mvdemo/mvdemo
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Dec 18 18:30:37 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
MVDEMO@db102 SQL> select definition from mvdemo.styles where rownum <= 1;
DEFINITION
<?xml version="1.0" standalone="yes"?>
<svg width="1in" height="1in">
<desc></desc>
<g class="color" style="stroke:#003333;fill:#2a00ff">
<rect width="50" height="50"/></g>
</svg>
MVDEMO@db102 SQL>                                                                    BTW, did you try the readme file's suggestion ?
you may need to
set the NLS_LANG environment variable to American_America.WE8ISO8859P1
temporarily. For instance, on Windows you can type the following in
the DOS window before issuing the above imp command again:
set NLS_LANG=American_America.WE8ISO8859P1

Similar Messages

Premiere Pro CC v7.0 - MP3s corrupted during import with "Write XMP ID to Files on Import"

Premiere Pro CC v7.0 - original MP3s corrupted during import with default "Write XMP ID to Files on Import" option
I have just started using a Trial version of Premiere.
I have a folder full of corrupted MP3 files after attempting to import them into Premiere.
After searching these forums I found that some other people have had corruption issues during import of media and it was related to the Preferences->Media->"Write XMP ID to Files on Import" option.
I attempted to import additional MP3s (this time making backups first) with and without the Write XMP ID option, and have found that this is where the issue is.
While the MP3 files still fail to be imported, the files are not corrupted in the process when the Write XMP ID option is unchecked.
Writing to files that are being imported seems to me like unexpected behaviour for any software.
Adobe please advise!
Is there any way to recover my original MP3 collection?

What exactly is wrong with them?

Imported images from my iPhone became corrupted after importing.

I Imported images from my iPhone and they became corrupted after importing. They appeared fine just after import, so I unfortunately erased my phone. When I reopened the aperture project where they were stored they had streaks, some were only partially visible, and others had no image just an exclaimation point with the words "incompatible file". thanks in advance for any suggestions or help.

What you describe are very typical symptoms: You import; the images look to be o.k.; you go ahead and delete them. The problem is that during the import you only see the previews created by your camera, not the actual images you are importing. When you afterwards try to edit or to enlarge the images Aperture will recreate its own, better previews and needs to access the original master image files. If Aperture cannot find the master image files or cannot open them, you may see warnings (unsupported) or corrupted thumbnails. Only then you will notice if the images have been imported correctly, and that may be too late, if you deleted the images from your camera.
How did you import? Are the imported master image files managed or referenced, i.e. included in the Aperture Library or referenced outside?
I'd suggest you look directly at the master image files to check if they are o.k. and can be read by other applications.
If your master image files are managed you'll find the images in the Aperture Library by right-clicking the Aperture Library package and selecting "Show Package Contents". Then Browse the folder "Masters". The master image files are stored in subfolders organized by the date of the import session.
If your master image files are referenced, open the folder where you told Aperture to move them to.
Check for two things:
Have all your images really been imported?
What is the format and the state of the images? Try to open the images with Preview, or any other image editor you have and check if they really are corrupted, or if only Aperture has a problem to access them.
If all your images are there, but Aperture cannot access them, your Aperture library may need fixing.
Back up your Aperture library (just a precaution) and use the Aperture Library First Aid Tools to repair the permissions or/and to repair the database; see this section of the Aperture 3 User Manual on how to do that: Repairing and Rebuilding Your Aperture Library
If repairing and rebuilding did not help, but you found the original masters and can read them, then copy them to a location outside Aperture and try to convert them to another file format with Preview or another application that can read them. Then try again to import those files to Aperture.
Post back, if you have more questions.
Good Luck
Léonie

LR4.1RC - 5DmkIII CR2 corrupted on import

I just had a few RAW files from my 5D mk III get corrupted on import. Either half of the image horizontally, or the bottom right quarter is severly corrupted.
I tried converting these same files with the DNG converter, then importing, and they work fine. Thankfully I checked before wiping the card!
Screenshot attached - any help would be greatly appreciated.
Edit: Update: I also tried re-importing the files directly from the card into LR 4.1RC and they are fine the second time around.
Just thought I should still mention this happening. Let me know if you need more info.

Ug. Intermittent issues are such a PITA to troubleshoot.
So, it just a coincidence that the first time I ever have seen this in 2
years on this system, is the first import I tried after installing the 4.1
RC?
I'll check all my cables and see if it comes up again.
Thank you for the quick reply.

Files get corrupted after import-export

Hi
After exporting images from HTML DB 2.0 and importing them some of the files are corrupted after import.
This has happened with one .js file and with one .pdf file.
All the other (including some PDF-s) are correct.
The "File Character Set" specified on import is correct and there are no other parameters I can change.
If I look the contents of corrupted files it seems that another file has been pasted at the end of the original file.
What could be wrong?

Hello,
Any news on this ? I have the same (reproducable) problem with a .js file.
Uploading works fine, but when I try to download it again, the contents of another file seems to have been appended at the end. The file also doesn't work when I try to include it using #WORKSPACE_IMAGES#...js
Matthias

Corrupted cd imports

How do I correct corrupted tracks imported from cd?

ianfromedenbridge wrote:
The cd plays perfectly on a separate cd player .It is a problem I have had with just a very few individual tracks both with my current PC and the previous one. So it is not a new problem, but is confined to three or four tracks among some 50 cds.
I have two suggestions to make, which are worth considering.
I realise you state that the CDs play on a different player, but even so...
First of all, have you checked the playing side of the CD to ensure that it's not dirty or very marked. It may sound obvious, but when does anyone actually check a CD? (Those of us old enough to remember the inrtoduction of CDs will recall that we were told that you could spread jam onto a CD and it would still play. We also remember that such a claim was complete rubbish!)
The other thing to check is a bit more involved, I'm looking for any common thing between the CDs which give you problems:
1. Are they all old CDs, say from the 1980's?
2. Is it usually or always the last track on a CD which gives the problem (or even the first one)? If it frequently the last track. If so, examine the CD, has it become discoloured, a sort of bronze colour on the outside edge of the CD?
3. Something else?
Phil

Problem on CLOB datatype after import

I got problem and call to Oracle support and they use DUL for extract data from datafile to dump file and I import everything is done and no error but when I check in CLOB datatype that have space(blank character) separate each character see below
Original
Oracle
After Import
O R A C L E
So the application cannot execute those data.
Anyone have solution how to fix this problem?
Thanks,
Taohiko

if you use a direct insert you are restricted to 4000 characters.
You can put your value in a varchar2 variable and that allows you to insert up to 32767 characters.
declare
my_clob_variable := rpad('x','X',25000);
begin
insert into my_table(my_clob_column)
values(my_clob_variable);
end;

Audio corrupted while importing

Hi,
I always used my Mac connected firewire with my videocamera Samsung VDP-something to import my DV tapes to iMovie. I never had problem.
Now, after 10-15 min. importing, audio results corrupted (sudden short silences interrupt speaking and sounds). I turn off everything, wait for the devices to cool down, then I turn everything on, rewind the tape and the problem disappeared: audio ok.
That makes me think that the problem is due to overheating of systems (Mac? Videocam? Both?). Is it true? Is there something I can do to avoid this problem and import the entire tape in one shot (like good-ole-days...) instead of 15min. at a time with long cooling pauses inbetween?
Has free space on disk (at the moment <10Gb) something to do with this problem?
Thankz<br>
PowerBook G4 15'' Mac OS X (10.4.2)

Hi Fredrico
Yes I think You nailed the problem down. <10Gb free doesn't sound good.
Recomondation is to keep the hard disk with at least 10 % free space and
a full miniDV tape (about 62 min) will need more than 13 Gb.
In iMovie I haven't seen any recomondation about size of work-area (free
hard disk space) but with FinalCutExpress it's said to be about 4 to 5 times
more than Captured.
This will rersult in about 50Gb free + 10% of hard disk space for everything to run
smoothly.
Sparce space will result in:
- hard work for hard disk to download (choppy imports)
- hard work for hard disk to manage virtual memory
- + of course more heat and secondary heat problematics ???? may be
- more wear and tear
I agree with FCE-recomodation.
Yours Bengt W

IPhoto Corruption On Import

My wife and I share an iPhoto library by placing it in the Shared user folder. We are using iPhoto 9.1.5 on an intel iMac with the latest system software. When I inport new photos to the library, thumbnails for all of them appear fine. However, the larger view does not work for the landscape oriented photos. When I try to expand them, I get an exclamation point inside of a triangle. Interestingly, the photos with a portrait orientation are fine. When my wife downloads when she is logged in, everything works fine. But many of the landscape photos she imported get corrupted when I download photos under my log in.
This has been an ongoing problem. Are we doing something wrong?
Thanks in advance for any help you may offer.
Kevin

Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Chose to check and repair Library permissions. You may need to do this from both accounts.
I see quite a few reports of this in the last while. A more lasting solution might be to move the Library to a disk formatted Mac OS Extended (Journaled) and set to ignore ownership and permissions.
Regards
TD

CR2 Files Corrupting on Import

Hi
I have an issue with importing CR2 RAW and JPEG files into Windows 7. This isn't an Adobe issue but I'm hoping someone just might be able to put me on the right track
A percentage of the files are being corrupted. I've tried importing directly from the camera (Canon 5D MkII), via a CF card reader and from an external HDD - all with the same result
The odd thing is that if I re-import the same batch of files I don't always get the same result. Some that were corrupted aren't, some that weren't are and some of those that were still are and some that weren't still aren't
It's definitely isn't the camera, the CF cards, or the card reader that's at fault. Windows 7 - and its USB system - is the only common denominator here
the only part Lightroom, Bridge, Photoshop or Canon DPP plays is that they all display the same result so they're out of the equation too
Bizzare

Since LR doesn’t touch or write to the files have you tried copying from the CF card to a folder on your internal C drive and then bringing into LR using:
Import >> Add
What happens if you move from Library to develop. Does the image display correctly?
It’s really a process of elimination along the hardware chain although purging the camera raw and preview caches may help. See this similar thread:
http://www.lightroomforums.net/showthread.php?19246-Corrupt-CR2-files-after-importing-from -Compact-Flash-to-HDD-using-Lightroom

Image Corrupted After Import into LR4?

Several times now I've imported images into LR4 from my External HD and and a few the files are corrupted. (See attached image)
I realize that LR is not suppose to do anything to the files on the disk when importing... but I've checked the RAW images from back-ups and they are not corrupted prior to import into LR. AFTER import into LR the actual file (on the external HD) IS corrupted in both LR and then on the External HD.
My workflow has been to copy files from my CF Card to the External HD (Western Digital 3 TB) ino the appropriate file... then go to LR4 and import.
Can anyone suggest what the problem is? I replaced the Card Reader... same problem occurs. I've checked numerous RAW files in Bridge... none are shown as corrupted (prior to LR4 import)

The corruption may or may not be “sudden”. If things look ok in Library then it happened sometime between initial preview building during import and you’re viewing the image in Develop.   If the last place things looked ok was in the Import thumbnail grid, then that is only showing the camera-embedded previews, so the images may be corrupted on the card, already.
The most important thing is to determine what the problem is, where the corruption comes from, so you can fix it. It could be the camera, the card, the camera-to-computer USB cable, the card-reader, the usb-slot, the computer-memory, the computer hard-drive, the USB-drivers, LR, itself, or some other software, like Microsoft Security Essentials has caused problems for some people in the past, although why is not really understood.
If the corruption is still occurring with the latest images, then you can experiment by changing one or more of the components mention above, and see if things are ok or still corrupted.
As far as recovery, if part of the image data is missing or zeroed out overwritten with random junk, there’s no way to get that bad data, back, from the existing file because the files, themselves, only have one copy of the data.
The three things I can think of to suggest are:
1)      If the preview in Library doesn’t show the corruption then there are ways to retrieve the previews from the LR preview cache as JPGs. This isn’t the same as the RAW data, but is better than nothing.
2)      If the camera-embedded preview has not been damaged—it is typically stored in front of the raw data so depending on where the damage is, it could be intact, then there are ways to extract the camera-embedded preview from the raw file, which again is better than nothing.
3)      The best thing is if you have a backup of the images that don’t show the corruption, either because the images are still on the card, or because you made a backup during import and the corruption happened sometime after import, then you could copy those over the top of the corrupted files and be ok.
These things may or may not be possible depending on your situation, though. If you don’t have any backups that are ok, and LR’s previews are bad, and the in-camera preview is tiny or also damaged, then you’ll entirely out of luck for those images. And things maybe really bad if it’s the hard-drive that’s failing and you have no backups of your images, there, either. It is important to determine what is wrong, and with the least effect on the images that are still good.

Fonts corrupted when import the Outlook Vcard

I have tried to exported the Outlook contacts to VCard format (.vcf) before importing into Mac Address Book, but the characters were all corrupted (messy)!
do i need to find a tool/converter to convert the character after importing the contacts? pls help. thx.

Sir, sorry that I would like to remind you that the Fonts (should be all the Chinese ones) are corrupted, but the digits and English fonts are correct.
Wrong encoding normally only corrupts Chinese and other languages, not English.
so could you pls help to tell me how to solve it? Thx!
Make sure your TextEdit app is set to Plain Text everywhere in its Preferences.
Open your .vcf file with TextEdit via File > Open.
If the Chinese displays correctly, then do Save As and change the encoding to UTF-16. Set the name of the file as 16test.vcf.
Try to import into Address Book.

File Corrupted? Import Backup Project file?

I have a project in Final Cut X, and both the event and the project folders are on an external HD.
My mac crashed while working in Final Cut.   WHen I reopen final cut, the current Project doesn not appear in the library.
(The matching event is there in the EVent Library.)
When I go to Finder, I can find the correct final cut project file. It doesn't open, saying it might be corrupt. There is a BACKUP folder, and several of those backups seem to work.... Sort of.
They open the correct video in the preview screen. It plays correctly.   But.... I cannot export or make changes as there still is no "project" in the project library.
How can I import this "backup" file into Final Cut X so that I can work on it, export it, etc?
(And in a related note, the crashing is sudden and weird and only happens in FInal Cut X. It just goes black, and then a message appears saying something like, "Your computer shutdown because of a problem..." )
MacBook Pro. 8GB ram.
Can you help?
Brad in Denver.
PS.   I'm freaking out. Such a headache..on a deadline and lost 5 or 6 hours of work.
PPS. THe import function doesn't seem to work for project files. (greyed out.)
Fingers crossed!! : )

Something bad has been done in your project library. There should not a waveform caceh folder in there. Some of the other folders look every strange. Have you been moving things arounds inside the projects folder or into or out of the projects folder at the Finder level?
The project appears to be called Backups. Where was that located? I don't understand how a project would appear in the viewer and not be selected in the project library, while nothing appears in inspector.

Corruption on import

I have been running Lightroom since LRv1. We base our entire workflow around importing individual catalogs, convert to DNG, backup 3x and work from the original import. It has been going well. Howver we are recently having some import corruption issues that seem to be most prevelent on LRv 3.0.
I have read that there are the same problems on 3.2, so I don't know where to go from here.
Today wasn't as much as a panic as in the past. Usually we are dealing with wedding images. Today was (only) some vacation images from Zion, Utah. I don't want to lose them, but it won't be the end of our business if I did.
Here are the events:
1. Imported to LR 3.0, convert to DNG
>result: images and preview thumbnail were coming in visually corrupted
>> stopped the import
2. Imported to LR 3.0, set to "move images to new folder and import to catalog". Set up new catalog and folder
>result: previews looked ok, however when you clicked on the image to enlarge or get a closer look, they showed the corruption in the high-res view which then showed up in the preview thumbnail.
3. Imported to LR v2.6, convert to DNG in a new folder and newly named catalog.
>result: import worked fine. No issues with any of the images.
4. Went to LR 3.0, browsed to open LR2.6 catalog created in step 3.
>result: LR 3.0 prompted to "upgrade catalog to 3.0" clicked OK. Everything is working and viewing normally.
I hope this is helpful to anyone in distress.
In any case, if there are any other hints, tips, tricks or words of advice, bring 'em on!
Thanks.

Q:Are you using a card reader or going directly from the camera?
A:Using an internal card reader.
Q:Do you get the same results copying the images to a local disk and adding/moving from there?
A: (took a while to find time to set this up) No. Didn't appear to have the same corruption issues after copying the images from the CF card to the hard drive and then importing them to a new catalog. - Settings were set to convert to DNG.
Q:Apart from your report that Lr 2 does not have this problem (this is the part that has me concerned), how sure are you the CF card is sound?
A: Not sure how to be absolutely certain that the card is sound. I don't think I have ever felt 100% certain about any CF card. Are there tests?
Send this file link with corrupted DNG (good for 3 days)
https://www.sendthisfile.com/7b6v4T321GU4fA4HGiNnbCug

Raw photos are corrupted on import

some of my raw photos are coming in completely corrupted
the original files in aperture are fine and have a backup elsewhere but am wondering if there's anything that can be done to prevent the problem?

There are so many possible problems here, that we'll need much more information.
1. What camera? What file type? Is the camera fully supported?
2. How are you importing? Direct from the Camera? Via a USB Card Reader?
3. What's the nature of the corruption? What's the difference between the corruption in Aperture and the problem in iPhoto?
Any more info you can add will help.
Regards
TD

CLOBs corrupting on import

Similar Messages

Maybe you are looking for