Problem in Exporting OWB Project

Hi all,
I was trying to export an OWB Project.But it gave the following error message in the log file :
<
MDL1256: Error occurred exporting LOCATION with physical name <ODSLOC>, business name <ODSLOC>.
Detailed Error Message:
MDL1255: Error exporting CONNECTOR <UIIDRACONN/UIIDRACONN> for LOCATION <ODSLOC/ODSLOC>.
Error in SQL Statement. Please contact Oracle Support with the stack trace and details on how to reproduce it.
>
I could not understand the problem.I have checked the CONNECTOR and the LOCATION are valid and working fine in the project.
Can anyone help me out of this ?
Thanks in advance.
Azad.

I suggest that you "merge" some jars to make custom one. you have then to import this jar instead.
this way you'll reduce the number of the imported jars and thus avoid the "too many..."
hope it's clear..

Similar Messages

MDSD : Problems in exporting Enhancement Project

Hi Experts,
I am having some problems in exporting the Enhancement MDSD project.... Please see the detailed description below....
Firstly I created a Standard MDSD project from MDSDSRC.zip file, then I created an Enhancement project from MDSD.jar file.. while creating this enhancement project I have included Standard project in it under Java Settings -> Projects & add project..
exporting the project in ..
1st way-
Project Right click -> Export -> Include Enhancement & Standard project under
"select the resources to export" -> choose checkbox - "Export generated class fiels & resources" & "Export java source files & resources" -> Next -> Next -> Select "com.sap.dsd.appctrl.DSDMain" in select the class of the application entry point -> Finish.....
It gives me errors as mentioned below..
1. Problem writing /MDSD_S1/java/ProjectConfig.properties to JAR: duplicate entry :     ProjectConfig.properties
2. Problem writing /MDSD_S1/.classpath to JAR: duplicate entry :    .classpath
3. Problem writing /MDSD_S1/.project to JAR: duplicate entry :    .project
2nd way-
Project Right click -> Export -> Include Enhancement & Standard project under
"select the resources to export" -> choose checkbox - "Export all output folders for checked projects" & "Export java source files & resources" -> Next -> Next -> Select "com.sap.dsd.appctrl.DSDMain" in select the class of the application entry point -> Finish.....
It gets exported properly but then when I replace that MDSD.jar file in
"C:\Program Files\SAP Mobile Infrastructure (C)\lib" folder with the standard MDSD.jar file which comes from SAP & run the MDSD application from mobile client it gives me an error as mentioned below..
java.lang.NoClassDefFoundError: com/sap/mbs/tools/signature/SignCanvas
Here i got some weird thing....
The standard MDSD.jar file based on which the MDSD application works has com->sap->mbs,uxe,tc,sxe,spe,mbs,dsd packages present whereas the enhancement project which I created from this same standard jar file & exported it has only dsd package. So this exported jar file doesnt include above mentioed SignCanvas class and hence its giving me an error.
Pls guide me further in this issue....
Thanks in advance....
Rajesh
Edited by: RAJESH SHINDE on Apr 8, 2009 11:21 AM

Hi Rajesh,
I think you are trying to enhance the MDSD 3.0 application. And the SignCanvas which you are mentioning is present in the mbs folder of the of the standard application jar. As you have told below if the jar you have created doesnot have these packages, the mentioned issue is happening.
Regards,
Vishwanath
Edited by: Vish on Apr 22, 2009 9:09 AM

Have a problem with exporting & importing project.

Hi all,
I have created my web dynpro project in my system. i tried to exported as zip file. and import in to my laptop. unfortunatly it asks, where to import this zip file and i have given my workspace in my laptop. but it doesn't accept it. Any one can help me by step by step. forget about what i have done. please give me your sugisstions.
thank you
Regards
Ravi

Hai,
Right Click on You project select export as -->zip file select location finish.
to import that one.
create new project with same name (the project old name)
file-->import -->zip file Select your zip file --> select the new project nad click finish
regards,
naga
Message was edited by:
Naga Raju Meesala

When I Try To Export My Project, Nothing Happens

So during editing in Final Cut Pro X I noticed that there were a couple of hiccups in my movie, but scrolling over these events didn't reveal a problem. I decided to see if it was a processing problem by exporting my project. I went up to File, clicked on Share, clicked on Apple Devices 720p, clicked on Next in the window that came up, titled the project, set it to save to the desktop, clicked Save... And then nothing happened. I checked my desktop for the file but there was nothing there. I've tried saving the file to several different places but when I click Save nothing happens and the file isn't in the place it should be if it had been saved. FCPX is working fine in all other regards but it's just not exporting this project. I've checked and I don't have any broken pieces of footage. The only possible thing I can think of is the song I'm using is one I purchased off of iTunes, so maybe it won't let me export if the song is protected by iTunes, but that seems like a stretch. Any help is appreciated.

Nevermind, I solved the problem. FCPX isn't showing me that it's rendering or whatever it's doing, but after about ten minutes the files show up. Still, any idea why it gives no indication that it's working?

I can not export my Project (vers. 10.0.8)

I have a Problem to export my Project to for instance "Apple Devices 1080p" or any other option. My Mac says it's working in the Background when I want to switch it off, but the Projct is stil 0% after hours. Length of the Project 8'54". Other Projects some Weeks ago, I think before the last update worked with no Problems.

Take a look at the list below and se whether something fixes your problem. Many reports of export issues.
Russ
Russ H Boston MA
Re: How do I find a certain frame that is causing an error when sharing project
May 31, 2013 5:22 PM (in response to PapaSnowSmurf)
If it doesn't export you could copy the project to a new project and/or use the replace edit to replace the guilty clip.
Magic Feather posted a few other export fixes recently. Let me look for them.
Russ
Magic Feather Los Angeles, CA
Re: Quicktime error: -50
May 30, 2013 7:30 PM (in response to Russ H)
Hey Russ,
Just to throw it out there but we encounter this bug every day (literally) and the easist solution we've found is:
1. Turn off background rendering when you want to export.
2. Quit FCPX
3. Delete the "Renders" folders from both the Event and Project.
4. Empty Trash
5. Open FCPX, export.
I only mention it because sometimes changing a clip in the edit can cause problems with clients if your forget to change it back.

PREMIERE PRO CS5.5 Gamma problem while exporting project to mjpeg A or B

Dear Sir,
I'm in a big ****. I've directed and edited 1h documentary for Finnish television, also, the technical specs requested by the TV Channel is all production Broadcast masters must be encoded with Apple ProRES codec or MJPEG A or B.
As i'm working on PC (win7), the ProRES codec doesn't exist on PC system, so i've done the export to MJPEG. The problem is i have a different gamma level when i watch the final export with Quicktime or VLC. Of course i can adjust the level in those players, but it doesnt effect the file. When i import the Qt file into a Premiere sequence, the gamma level is still **** and different from my original level i have from my timeline and preview window. If i export the project to H264 1920x1080p25, then the gamma is perfect with Qt, VLC and WinMedia player. But the TV station don't wanna work with H264. Deadline is on next monday, and i can't send a Qt MJPEG file with wrong gamma !!!Any chance to find a solution to fix it ??? After reading different forum, i can see this problem exist since many years and never been solved.
What can i do ??
Denis.

Things is my prpject includ few effect plugins i bought, so what ever i could find a mac, not your i could export xml project to finalcut with plugins it dont have
Denis
Sent from my iPad.
Le 31 mai 2013 à 15:20, Fuzzy Barsik <[email protected]> a écrit :
Re: PREMIERE PRO CS5.5 Gamma problem while exporting project to mjpeg A or B
created by Fuzzy Barsik in Premiere Pro - View the full discussion
If it were me, I wouldn't encode to MJPEG.
So as to encode to ProRes on Windows you can utilise any solution based on ffmpeg/ffmbc or better yet find a Mac with Final Cut or Compressor installed for delivering critical work.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5368019#5368019
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5368019#5368019
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5368019#5368019. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Premiere Pro by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Export Problem: imovie 06 - HD project to Quick Time in wrong aspect ratio

When I export a project from imovie 06 that is in HD 16x9 aspect ratio, (simple export using "High Quality") the resultant QT movie is not in the correct aspect ratio - it's in "regular TV" format.
Is there a simple fix for this?

david,
did you ever find a solution? i have the same problem....
thanks,
marc

WIll I have duplicate problems when I Export / Import Project?

This is my first try at Exporting / Importing a Project to benefit from having Aperture on the road on a MacBook.
I run a secondary instance of Aperture on my MacBook with a managed library. I used it last week to rate, and adjust 40 images from a shoot while on the road. Those images are in Project ABC. My objective is to not lose all the adjustment work done while away now that I wish to re-locate these images to my primary instance of Aperture which runs on an iMac. I won't need them any longer on the MacBook.
I've exported Project ABC, and it's now sitting on the desktop of the iMac ready for import into Aperture where the library is also managed.
Between the shoot and today, however, I had uploaded the same images from my CF card to the iMac's Aperture library into Project XYZ. No work has been performed on any of them, but the image names are identical to those in Project ABC waiting to be imported.
My plan is to import Project ABC, and, assuming everything comes over in good shape, to delete the unadjusted masters/versions in Project XYZ one by one.
Question 1: When image GEN_1234.nef with all its adjustments, etc., contained in Project ABC, is imported, will Aperture have a problem that GEN_1234.nef (unadjusted) already is in the library in Project XYZ?
Question 2: I've checked the MacBook after exporting, and Project ABC looks as though nothing ever happened. Does this sound right? I'd expected the Masters to be gone, but "M" toggles between the master and the adjusted version.
Thanks.
Terry

Problem #2 is not a problem. We have been able to somewhat install Oracle when those warnings appear. The client install works fine with those warning messages in the terminal window. NOTE: They are just warnings...

Export/Import Project problems

I have two machines: a PowerMac (G5) and a MacBook Pro (Intel Dual Core). Both 2GB RAM, running OS X v10.5.6 and Aperture 2.1.2. (More tech spec info available if anyone thinks it relevant).
I have built up a project on the MacBook Pro, creating albums, creating stacks and making picks within the stacks, making adjustments to each of the picks and then creating a book.
I now want the project on the PowerMac G5, which is my master machine and contains all my other projects.
On the MacBook Pro I exported the project and then copied the resulting .approject file to the PowerMac. I then imported the project into Aperture from there. On a cursory scan, everything seems fine and in the Projects Inspector it shows 1376 images against the project on both machines. However, if I look more closely, I've lost all my picks. I.e. I need to go through every stack again and reselect my picks (very boring).
It gets worse when I look at the Book within the project - it's lost the positionings (i.e. I double clicked on the image and moved it around slightly to get the best crop for the selected box shape). And then I did a Close All Stacks and it deleted every picture from the book so all 60 pages were empty again and the images were all back down in the film strip!
At this point, my immediate thought was the .approject file got corrupted during the copy, but I've done a recursive diff (diff -qr fileA fileB) between the file on the MacBook Pro and the file on the PowerMac and it reported no differences at all.
Has anybody else had similar problems? Is the project import/export known to be flakey? Better yet, anybody know of any workarounds?
Thanks in advance for any help anyone can offer.
Darren

OK - I've tried eliminating some of the variables and it turns out the two-machines-issue is a bit of a red herring and this is a straightforward Export/Import bug in Aperture.
On a single machine (2.16GHz Intel Core Duo MacBook Pro with 2GB RAM, running OS X 10.5.6 and Aperture 2.1.2 (build 3G13)) I have a project with many images. I create versions of these images and apply adjustments (Sharpness, Monochrome Mixer, Exposure, Enhance, etc.). I then make the adjusted version the Pick and I've created a 62 page book from these Picks.
Now I export the project (i.e. in the Project Inspector I right-click the project and choose Export > Project). I export the project to a file on the desktop and rename the existing project in Aperture. I now import the saved .approject file and I find that all my (long and carefully chosen) Picks are no longer Picks. (I've tried this a few times and ruled out the possibility of a corrupt export file).
As a result, when I select the Book I get the "Non-Pick Images" dialog with the dreaded "One or more placed items are no longer the pick of a stack." message.
I have two options at this point: "Use Current Pick" ruins the book - I have to go through and work out all the picks again (and also re-pan all the images within the Photo Boxes as this data has also been lost).
Or I can choose "Create new Version", which appears to preserve my book's original look (I haven't looked in too much detail yet), but my project now contains a couple of hundred more images than it used to (or at least extra versions which, whilst I know these are relatively 'cheap', are still unnecessary) and this still doesn't help with my other albums and light tables, which still have incorrect images shown as the Picks.
I'm finding this quite a worry - I originally hesitated to move my photo library into Aperture due to the thought of losing the metadata one day if I moved from Aperture to something else, but in the end I decided to trust that something as simple-to-test as Export/Import would get properly implemented - now I'm beginning to fear that it doesn't even within the same version of Aperture, never mind different versions of Aperture or (heaven forbid) different applications altogether

Project manager - problem exporting a project with AE compositions.

I have a problem exporting my project to another disk, this is what happens:
I needed to move the project from the windows partition of my Mac to the Mac partition, in order to be able to continue my edit under MacOS, my sequences include a series of After Effects compositions of footage that has been stabilized in warp stabilizer using the option "replace with AE composition" from the timeline.
Using the project manager I started my backup operation, with these options:
Source: all sequences selected
Resulting Project: Collect files and copy to new location
Include Audio conform files
Destination: a folder in the Mac partition
The resulting project had a message popping up saying that AE rpject file is missing (it was, I had to manually copy and paste it from ithe win partition to the mac) and once copied obviously AE couldn't find the source video clips of its compositions, so I had to manually re-link them all (quite difficult job to do among almost two years of footage).
What have I done wrong ?
Why AE lose the connection with the fils?
Thanks

Thanks Jim,
I understand that Adobe Anywhere solves this, but there should be this fairly basic functionality (which exists in Avid and FCP) in a non-enterprise edition of the software. I have submitted a couple different feature requests about this, going back to CS5, so hopefully enough people make similar requests for a fix to be implemented. Adobe Anywhere is really not a solution for our small shop as currently configured/priced, especially when we can have editors working remotely with very affordable USB 3 drives. The only hangup is the markers, which just isn't worth a 5 figure fix. As such it's hard to consider the problem solved for either us or any small shop or post crew.
Best,
Jon

Problem in exporting library files with project(Classpath in manifest file)

I've developed a J2EE application client using Eclipse 3.3.1.1, now I want to export my project as a executable jar file but there is a lot of external jar files so when I put their name in Class-Path variable of project's Manifest, I see "Too long" error because there are too many external jar files.
How I can export required jar files with executable file of my project?
In my idea, the process of application client exporting is so foolishly and silly! why there isn't any standard and easy-to-use utility for this reason?!

Nazi wrote:
I've developed a J2EE application client using Eclipse 3.3.1.1, now I want to export my project as a executable jar file but there is a lot of external jar files so when I put their name in Class-Path variable of project's Manifest, I see "Too long" error because there are too many external jar files.
How I can export required jar files with executable file of my project?
In my idea, the process of application client exporting is so foolishly and silly! why there isn't any standard and easy-to-use utility for this reason?!Probably a Jewish Bolshevik conspiracy...
Abuse reported

Problem when exporting and importing project from odi 10g to odi 11g

Hi,
I want to migrate my project from odi 10g to odi 11g.
But when i am importing the interface then it is giving the error of mising references .
I have exported the project(without its child component),models
(including my datastore),KM's,folder (without its child component),packages(with child components),interaces(with child components),procedures(with child components),variables from odi 10g.
After exporting all these objects i imported all the objects with import type set as "Synonym mode insert" into odi 11g but when i imported the interface it is giving the error of missing references.
Source technolgy is Oracle and target technolgy is Postgres.
Topologies have been made in the ODI 11g same as in ODI 10g.
Please help.

You dont need to migrate the complete repository. You can migrate a project at a time into ODI 11.1.1.5.x
You have to be careful while importing. You have to follow a sequence when importing.
Empty Project -> KMs -> Models (with DB Stores) -> Variable -> Empty Folders -> Interfaces -> Procedures -> Packages ---- All in SYNONYM mode insert (no exceptions)
And your repository id in 11g MUST be different from the one in 10g.

Problem exporting my projections

exporting the projection of my photos, Lightroom 5 always stops at 10% of the process. I've tried numerous times and always stops at this 10% progress of the process. What can I be doing wrong?

There is a difference between capture sharpening and output sharpening. The general idea is to get the image just sharp in Develop (but not over sharp) and then apply output sharpening as you export the photo (click image below).
Try exporting a jpeg or tiff from your raw file and use the type of sharpening depending on your purpose e.g. for printing choose the paper type and level of sharpening. If the image is to be used on a website, blog or for sending by email; use screen sharpening.

OWB Project Management, Versioning

Hi,
We're using version 9.2.0.3.0 version of OWB. Most of our work has been in the development stage, but we're ready to start moving to Integration, Acceptance and eventually Production.
I've read a lot of OTN and Metalink forum messages on how people are doing this. I'd like to know what it the best way to move these changes to the different levels. Some people mentionned creating different repositories, others have mentionned different projects (All within the same repository), and there is also mention of snapshots.
The snapshot concept is nice, but would incur too much work around if a restore is needed. From a developer point of view, if a restore is needed, then afterward who know what's been restored, what's current,etc...especially if we have about 5-6 developers working in OWB.
I'm kinda leaning towards having separate repositories, so the developers can see the mappings in each level at any time. Having different projects wouls also be feasible.
As a DBA, once we get to production, then I agree that if the code is deployed in a file that I would only have to run, then this would make our lives easier.
I'd like to hear what people (and Oracle) have to say on the subject.
Thanks,
Guy LaBelle
DBA
Atlantic BlueCross Care

There can be several possible solutions of this problem. One would be the snapshots (project versions stored in the database). Today you can create snapshots at different project phases and the snapshot utility will let you see the differences between the various versions in a graphical interface (version reporting)
The problem with snapshots (as you correctly state) might be that you have to restore the versions to work with them, which might be cumbersome if the developers need to have instantaneous access to multiple versions.
Therefore, in your case I would suggest the following:
- create two separate repositories (with two separate run-time environments), one for development, one for production.
- do all the design, development and testing in the development environment. You can have different projects containing different versions of the project in the development repository. This will allow the users almost simultaneous access to multiple versions (what you don't heve here and is present in snapshots are version reporting - project diffs. the users will have to manually compare the versions. If project diffs are more important than fast access to multiple versions, than use snapshots instead of multiple projects).
- Once the design is consolidated and you are ready to go into production, export the project into an mdl file and import it into the production repository. Deploy and run the production environment.
- Now you have two almost identical systems running side by side. The development system also has all the earlier project versions, while the production only has the latest version. If a problem is detected in the production, test and fix in the development and then move the fix into production (mdl export-import + deploy).
Hope this helps.
Regards:
Igor

Unable to Export iMovie project in everyway I have attempted for the past 2 weeks. Please Help! Due date coming up!

I've unable to Export iMovie project in everyway I have attempted for the past 2 weeks.I have a late 2012 iMac with 8gb of RAM and 700 gb of free space on the hard drive. The video I am trying to export is 48 mins long with most of the source footage from a NIkon D3100 and several other cammcorders. I've been exporting with Apple Intermediate codec because that was the only one that has work so far but it only worked once and since then I have had to make changes to the project and now I'm unable to get it to work. For all Quicktime exports in H.264 or AIC (my prefered format for this export since I figured it'd offer the highest quality when I import it into Encore for making a dvd out of it) Which just stops exporting in the last few minutes without explination as to why or it crashes and quits. It either leaves a partial file or nothing at all. When I do "export movie" I get a "not enough memory Heap zone error"
I don't know what to do any help would be greatly appreciated!
By the way I happen to have Adobe CS6 Production Premium but didn't know how to use it as well when starting the project and now really regret not using it because it appears to be 10x more stable and capable of handling all the tasks I want it to do.

Hi
Error -108 memFullErr Ran out of memory [not enough room in heap zone]
Turn off - TimeMachine usually works - re-try.
(the Application down in the Dock - not the Device)
But this can mean many thing's - My first thought is
Free Space on Start-Up hard disk. How much ? (other disks do not count)
AppleMan1958
Are your event clips in h.264? If so, you can solve this by Right clicking on your Event Name and choose "Optimize Media". You can choose Full for 1080P or Large for 960P according to your preference.
After you have optimized your Event, you should be able to Share with no problem.
Lennart Thelander
-108 mean you are running out of (free) RAM.
Try restarting the computer just prior to sharing. That frees up RAM.
from mynameisearl
Final Entry
Ok - after much cutting, trial and error and days of work I have never really established a root cause for the -108 error. Nothing I did resolved the issue to the orginal project.
The only work around I have found is to split the Original Project into two.
What I found was that anything around the 60 mins mark and above just failed to render in HD and showed the -108 error.
What worked for me was creating two project files - one around 57mins long - the other a part 2 - around 17 mins long. All using exactly the same source clips, photo's, music and transitions as the orginal.
This now works. I guess having it split in two makes it a little easier to work with as I wont have to keep rendering the first part which does not change but really wish Apple would throw some light on this.
Anyway - I hope all of the above at least proves useful for others.
Good Luck

Problem in Exporting OWB Project

Similar Messages

Maybe you are looking for