ODI file move

Hi..experts..
How to move files from one directory to other directory???
Suppose E:\ODI\FILES directory contains 2000 files and I want to move 1000 files to E:\ODI\FILES_NEW directory.
How to do it???
Please suggest..
Thanks

Please look into OdiFileMove http://docs.oracle.com/cd/E21764_01/integrate.1111/e12643/appendix_a.htm#autoId39
Provide the appropriate Mask for the files to be moved.

Similar Messages

How to use ODI tool (file move etc) and plsql in a ODI procdure step

Hi,
I need your help to uses both plsql code and ODI tolls in a ODI procedure step.
Req:
moving files to different directory Based on the variable value and previous step return code ,
BEGIN
IF #SEQ=1 AND <%=odiRef.getPrevStepLog("RC")%> =0
then OdiFileMove "-FILE=input/#FILE_NAME" "-TOFILE=processed/#V_FILE_NAME" "-OVERWRITE=YES" "-CASESENS=NO" "-RECURSE=YES"
ELSIF #SEQ=1 AND <%=odiRef.getPrevStepLog("RC")%> !=0
then OdiFileMove "-FILE=input/#FILE_NAME" "-TOFILE=reject/#V_FILE_NAME" "-OVERWRITE=YES" "-CASESENS=NO" "-RECURSE=YES"
END IF;
END ;
how do I do that ? which technology I have to use because for plsql I need oracle and ODI file move I need sunopsis
Please help me.
Thanks,

Hello User,
Use below code, it will work fine.
Technology: OdiTools
<@if((<%=odiRef.getPrevStepLog("RC")%>)>0 && #PROJ_FILE.SEQ==1){@>
OdiFileMove "-FILE=input/#FILE_NAME" "-TOFILE=processed/#V_FILE_NAME" "-OVERWRITE=YES" "-CASESENS=NO" "-RECURSE=YES"
<@}else if ((<%=odiRef.getPrevStepLog("RC")%>)>0 && #PROJ_FILE.SEQ==1){@>
OdiFileMove "-FILE=input/#FILE_NAME" "-TOFILE=reject/#V_FILE_NAME" "-OVERWRITE=YES" "-CASESENS=NO" "-RECURSE=YES"
<@}@>
Thank You.

ODI File Datastore

Hi All,
I have a confusion regarding physical and logical length in ODI file datastore.
I have a fixed width file where a col c2 had datatype as string(30).
I defined that column in datastore as string>Physical length 30 >Logical length 30
My interface failed with error as"
ORA-12899: value too large for column "S0_IDM"."C$_0S0_EAGLE_DWHCDC_CHRG_MST"."C2_CHARGE_DESC" (actual: 31, maximum: 30)"
When I increased the logical length to 255,the interface worked fine.
Physical length still being the same 30.
How different is this?
Any help on this will be appreciated.
Thanks and Regards
Reshma

This is not from any official documentation, but here is my take after a few moments thought
Everything you do in the ODI designer is based on the logical architecture. Only at runtime is this manifested into a physical implementation i.e. connection strings are materialized etc. When you perform an integration ODI generally creates a few temporary tables prefixed with C$, I$ etc to be able to perform the necessary data movement and transformations required to, for example, populate a target datastore (table). In your example, your flat file will be materialized into such a temporary table before its contents are manipulated (or not) and loaded to the target datastore. When ODI generates this code it is using the logical length issued in the DDL that generates the temporary table column lengths, the physical column is ignored.
Now in your scenario this is not a problem as constraints such as these do not matter to the physical version of the file i.e. if you were to write back to the file it would not matter if you wrote back 255 characters or 31. This could be a problem if you were using database tables and varying the logical vs. physical lengths but usually you reverse engineer database tables using ODI rather than doing it manually so this mitigates that.
Anyway, in short, I think the logical lengths should be taken as representing what will be manifested in the materialization of the temporary objects used to manged / transform data from the source models (C$tables) and target models (I$tables) whereas the physical lengths indicate what the underlying physical representation of those models actually are.
EDIT: After reading a bit of documentation logical actually represents the length whereas physical is related to the number of bytes required to store the data. Therefore you could have a situation with multi-byte characters where the physical length could be greater than the logical length but not really the other way around.

Getting error 8 during a file move with shortcuts

Hello,
I am using the file move vi to move files and shortcuts from one folder to another. This works file when I am trying to move files. but when I try to move a shortcut (a file with a extension of *.lnk) the move vi fails and gets a error 8 (permission error). Why is this happening? I am assuming that a shortcut is a file, so I am treating it as a file and therefore expecting the move vi to move the shortcut from one folder to another.
Regards,
Kaspar

It could be that this is related to a bug that has already been discovered and reported. Our R&D deparment is working on it. When LabVIEW copies or moves a shortcut, it actually makes a copy of the file that is the target of the shortcut. However, it adds the ".lnk" extension to the end of the file name. This causes the new file to show up like a shortcut in Windows, but it is not a shortcut. If you rename the file and remove the ".lnk", then the file (the target of the original shortcut) will open without problem.
One workaround it to use the System Exec VI to copy the file from the Windows command line. See the attached VIs.
Jeremy P.
Applications Engineer
National Instruments
Attachments:
Move with Command Line for LNK.vi ‏16 KB
Copy with Command Line for LNK.vi ‏36 KB

Photoshop Elements 11 Organizer failed during folder / file move

I have a large image collection, in excess of 40,000. I'm running on a PC with Windows 7 and all updates installed. I just purchased PSE 11 to replace PSE 10. After installing PSE 11 I converted my catalog. That seemed to go OK. At that point I discovered that my C: drive was almost full so I decided to move my image collection from its C: drive location to an external hard drive that had sufficient capacity. In order to ensure the integrity of the catalog I decided that I should use the PSE 11 Organizer to move the files. This would allow the Organizer to update the location information for the files as it moved them, although it was clear that this would take many hours to complete. So, using Organizer I did a "drag and drop" of my image collection's root file from the C: location to the external drive which happened to be the J: drive. Organizer appeared to be running properly so I left it to continue overnight. The next morning I discovered that only about 2/3 of the files had been moved. There was a very cryptic message that said the opertion could not be completed because of "...possibly unsupported files types, files with read only attributes.." etc. I did not write down the actual message and it did not tell me where in the transfer the failure occurred. After doing some detective work I discovered that many folders and files had been copied to the J: drive that were not appearing in the Organizer catalog and consequently were not being displayed. Some folders had only a portion of their files copied. Fortunately, the files were still visible and cataloged on the C: drive. I did look at my files on the C: drive and there were some that for what ever reason had read only attributes.
I don't have a good guess as to what was actually the root cause of the problem, but here's how I think the file movement should happen. The selected file, files, or folders should be copied to the specified destination. At that point they should be added to the catalog, then the files should be deleted from their original location and the catalog updated accordingly. If an original file is read only then it can't be deleted but the attempt to delete it should be reported as an inability to delete with no consequences imposed on the files that have been placed in their new location. The "problem" should not be promoted to the status of a serious or fatal error that causes only partial completion of the overall operation.

Bill Junk wrote:
I've seen a couple postings in the forum that related to catalog conversion failures and suggested that they could be avoided by running in administrative mode. When I did my conversion is was not in administrative mode and it's certainly possible that there were files with restrictive permission settings that screwed things up. It's also fairly likely that the catalog itself had some issues that were not detected or fixed by running a catalog repair.
That's something I had the opportunity to test today : after a fresh install of my second copy of PSE11 on another computer (Vista), I first restored without problem a PSE11 backup from the other computer (XP). Then I tried a restore for a catalog from a PSE6 version on the second computer. The conversion failed the first time and worked the second time when run as administrator. This time, I don't think there were file types problems, since that PSE6 catalog had been restored successfully on a PSE10 version some months ago. I really don't understand that 'administrator' problem, since all my files are situated in a second internal 1 Tb drive with full access for my account ?
I am not sure about the details of your case, but I understand you have restored exactly the same tree structure in a new J: drive. Your catalog is always accessible in its original location.
In that case it's possible to simply create a copy of your catalog (a simple copy of the folder containing the database catalog.pseXXdb - to be found in the help menu, system info). Then you need a sqlite database management tool (I use the add-on sqlite manager in Firefox) to simply edit a single record in a table containing the identification of all drives known to the catalog. You simply edit the letter and the serial number of the drive (DOS command VOL:).
I had a case where I had a catalog and all the media on an external drive. That external drive was assigned a different letter in different computers. Either I used the above solution, or I had to reassign drive letters in one of the computers.

Odd file move behavior

On my startup disk, I have a movie file (.mov) and a folder I want to collect movies in. Straightforward enough.
So I click/drag the .mov file onto the folder. It shows me the green + icon, and when I let go, it COPIES the file into the folder, not by simply MOVING the file from the disktop to the folder. Wha?
When I grab that same file in the folder and move it to the disktop, it works as expected, insisting that it must be DUPLICATED, replacing the disktop, original file.
OK. So instead of doing that, I decide to trash the original file, then move the version out of the folder and back to the disktop.
In order to do that, I use the contextual menu that drops down with Control+mouse click. It now asks me for my administrator password to do the trash move. (???)
Once the original has been tossed, the file will now move from folder to disktop and back to folder with complete impunity. But if I try this with another .mov file, the process starts all over again.
No extra key combo during the original move gets rid of the + icon.
Permissions were repaired. No change.
Log off was cycled, no change.
Obviously somehow this disk has picked up wierdness when Leopard replaced well-tempered Tiger on it, but where is the checkbox that dumps this odd behavior?
No Right-click on the mighty mouse will bring down the contextual menu at all.

Yea! The Mac is back on track!
It took extra innings and a visit to 1 800 APL CARE to get to the bottom of it, but this therapy should be on everyone's A-list: The Install disk's version of Disk Utility is significantly different from any version you can install on your hard drives. Or so it would appear.
Where the Disk Utility can be there for you on two different hard drives connected to the same computer, running it from different drives is not at all the same - in visible results - as running it directly from the OS X Install Disk.
You can have several disks with OS X on them and run Disk Utility on your main startup disk from those, but they won't find all the messy permissions that are gumming up your system.
It took yet another previous back up Restore cycle, an extra clean install, followed immediately by an Install Disk run of Disk Utility's First Aid/Repair Disk Permissions to clear the cobwebs. Frequent re-weedings (after any program installs or upgrades from anybody, including Apple's own) finds more things to fix. Not always, but frequently.
The Install Disk's Disk Utility--it's not just for breakfast any more.

Mistake message with file .mov

In PremierPro CC has a problem with a file .mov says "file has no audio or video streams", but I was working with that file and others, in quicktime error-free reads are not damaged, that I can do? as rescue nearly completed projects?
thanks

Adobe Premier Pro CC is complete reinstall on another computer and check the same problem with the same files, creating new projects and reviewing damage or file does not contain errors, these files if you recognized already had begun as edit them and the program stopped, was closed, and the open left to recognize.

Does File Move work in PSE 7.0?

I have files scattered across two hard drives as a result of having two catalogs. For my primary catalog, I would like to consolidate all of the actual picture files onto a single location on one drive. I tried to use the File > Move command and opted to move the entire catalog. When I tried this and selected the new location, nothing seems to happen. Any ideas?
Thanks,
Paul

The File > Move command does work in 7 (it fixes a serious bug in 6).
I tried to use the File > Move command and opted to move the entire catalog. When I tried this and selected the new location, nothing seems to happen.
Do you mean that you selected all the thumbnails (Edit > Select All or Ctrl-A) and then invoked File > Move? Did you check the Properties pane to see the locations of where PSE thinks the photos are now located?
In general, however, note that File > Move may not be ideal for your purposes. That command will move all the selected photos in the single destination folder you select, not preserving any heirarchy of subfolders you may have. If you want to preserve the folder heirarchy, it will be easier to use Display > Folder Location view. See this FAQ for more details:
http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Move_your_photos

What software do I need to move "file.mov" to dvd?

I'm new to the apple world ... have miDvD and have moved file.avi to a dvd, but can't seem to be able to do the same with a file.mov that my grandgaughter sent me. PLEASE HELP

It lloks like miDVD only supports .mov file that use the H.264 Codec. Do Get Info on your .mov file and see what the codec is. If it's "Motion JPEG OpenDML, Linear PCM", I think you'll need to convert the file to the H.264 codec.
Below from this link

AnyConnect 3.1.01065 error - Failed to install AnyConnect VPN Profile because of file move error. A VPN connection cannot be established.

I've got a user running:
AnyConnect 3.1.01065
on
Windows 7 64bit.
Several weeks ago she started encountering the following error:
-after logging into Windows and launching the AnyConnect client, she enters her username and password and successfully authenticates.
-the connection is not established and she's presented with the following message: "Failed to install AnyConnect VPN Profile because of file move error. A VPN connection cannot be established."
After doing some troubleshooting, inlcuding uninstalling/reinstalling the anyconnect client, it seems the culprit is the following file:
C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Profile\<filename>.xml. When the problem occurs (which is not regularly, sometimes it occurs daily, sometimes just once a week) examining that file indicates it has no security or permissions set. Quitting the AnyConnect software, modifying the file so that the user has full control of it, then relaunching AnyConnect fixes the problem (until it happens again). Uninstalling, and making sure to move C:\ProgramData\Cisco to the trash, then reinstalling did not seem to help.
The closest match in these forums is the following thread, https://supportforums.cisco.com/message/3760446 - though no clear resolution was given.
Has anyone else encountered this, and been able to fix it?
Thanks much.

Just FYI, it seems at least in this case, purging all the previous system restore points seems to have resolved this issue...

I cannot import a Quicktime file (.mov) which I generated from a slide show out of iPhoto8 in iMovie8 (filename is grey); what did I wrong?

I cannot import a Quicktime file (.mov) which I generated from a slide show out of iPhoto8 in iMovie8 (filename is grey); what did I wrong?

iMovie 08 will only import files that contain codecs that it can edit. It will generally import audio and video codecs that iPhoto generates. However, if your iPhoto slideshow contains a manual advance track, iMovie cannot edit this and therefore will not import. In iPhoto, check to see if you can do a timed advance rather than a manual advance. Then it should import.

Make a audio controller file move with a pan and zoom.

I am using a few folio overlays for a digital publication.
I have an image that uses the pan and zoom overlay.
I would like to add several play buttons for audio that are linked to the image so when you pan the image the audio files move with it.
So far I can only get the audio controller file to be static and the image move under it.

Here's a little trick for you. Before creating a scrolling frame, group the
text frame with a small no fill/no stroke frame. Now you have group in the
frame, you can drag additional objects in using the layers panel.

Atomic Rename using Files.move

Hi,
I want to rename file atomically:
Path source = Paths.get(pathOfFile);
Path dest = Paths.get(pathOfFile + ".txt");
Files.move(source, dest, StandardCopyOption.ATOMIC_MOVE);
It is documented that "AtomicMoveNotSupportedException" is thrown if the move cannot be performed as an atomic file system operation.
Is it dependent on the operating system to throw this exception or not (e.g. in Windows it is always thrown, but in linux based systems it is never thrown).
Or it may be thrown in both of the operating systems only in some special cases (e.g. when the target location is on a different FileStore and would require that the file be copied, or target location is associated with a different provider to this object. - javadoc of the method)
If i always use valid relative path names, then may i be sure that i will never get this exception in both linux and windows based operating systems when renaming?
Thanks
Erdem

921451 wrote:
Is it dependent on the operating system to throw this exception or not (e.g. in Windows it is always thrown, but in linux based systems it is never thrown).
Or it may be thrown in both of the operating systems only in some special cases (e.g. when the target location is on a different FileStore and would require that the file be copied, or target location is associated with a different provider to this object. - javadoc of the method)On any given OS, the atomic move may succeed in some cases and may give that exception in others. The example of same vs. different disk and therefore not requiring a copy vs. requiring it is a good example. Although I don't see any reason why any particular OS/FS wouldn't be allowed to throw it even for a simple non-copy move. The whole point is, "what happened on this particular attempt?" I don't think it's meant to be an indicator of overall OS/FS policy.
If i always use valid relative path names, then may i be sure that i will never get this exception in both linux and windows based operating systems when renaming?No.
But take a step back a minute. Any time you're doing FS operations, there's a chance they may fail for any of a number of reasons, and you have to be prepared to handle those failures. So even in cases where the underlying FS is guaranteed to support an atomic move, the move could still fail for other reasons. You have to handle a failure no matter what. The only reason you care if it's this particular exception is if you're going to handle it differently than other exceptions.
But at the end of the day, if the method declares that it throws it, then your code has to be able to handle it.

HT3775 How to open an .AVI file (movie) with my new Mac

I'm not able to open an AVI file (movie) with my new iMac, any good advice? thanks gnogno

Down load from the Internet VLC media player. That should solve your problem.
Ciao.

HT3775 is there a player that will play a 2.flv file movie on my macbook pro with system os x lion 10.7.5

Is there a player that will play a 2.flv file movie on my macbook pro with os x lion 10.7.5

http://www.videolan.org/ 's VLC

ODI file move

Similar Messages

Maybe you are looking for