ODAC release 2 problem

Hello everybody
I have installed the new release of the ODAC, and each time we try to do a DataReader.Read() operation a OracleException is thrown without message and with the errorcode -1551.
We can connect to the database, but we cannot perform any other operation over the data.
We previusly use the beta version, with some problems, but we found some workarounds for them.
Any idea about this problem?

could you paste the code and sql statements that generate the error, so that we can try to reproduce the error and find workaround for it.
Regards,
Nur Hidayat

Similar Messages

ODAC Release 4 & 5 - Oracle.DataAccess.dll 4.112.3.0

Has anyone else noticed that ODAC Release 4 & 5 have the same AssemblyVersion 4.112.3.0?
Oracle Data Access Components (ODAC) for Windows
It took me a while to spot the problem. I'm using Entity Framework 5 and hit a machine with Release 4. It threw an completely misleading exception on load.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.TypeInitializationException: The type initializer for 'Oracle.DataAccess.Client.OracleConnectionStringBuilder' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Oracle.DataAccess.Client.RegAndConfigRdr' threw an exception. ---> System.Configuration.ConfigurationErrorsException: MySchema.MyPackage.MyProcedure.RefCursorMetaData.CUROUT.Column.1 is invalid
   at Oracle.DataAccess.Client.RegAndConfigRdr.AddMetadataForRefCursor(String refCursorKey, String metadataInfo, Hashtable& schemaTable)
   at Oracle.DataAccess.Client.RegAndConfigRdr.RetrieveInfoFromConfig(NameValueCollection nvc, Hashtable& schemaTable, Boolean bIsCallFromODT)
   at Oracle.DataAccess.Client.RegAndConfigRdr..cctor()
Since ODAC Release 4 was installed, the machine had Oracle.DataAccess.dll (4.112.3.0) in GAC. Thus, my application could not use my local copy of Oracle.DataAccess.dll (4.112.3.0) from Release 5.
Having the same AssemblyVersion for Release 4 and 5 causes issues. Can we get an additional release with an updated version?

Can you elaborate on the versioning policy for ODAC? What I'm looking for ideally is an incrementing AssemblyVersion with releases as was done previously with Oracle 11 R3, R4, R5. For example,
ODAC 12c Release 1
AssemblyVersion = 4.121.1.0
AssemblyInformationalVersionAttribute = 4.121.1.0 12c R1
ODAC 12c Release 2
AssemblyVersion = 4.121.2.0
AssemblyInformationalVersionAttribute = 4.121.2.0 12c R2
In your post https://forums.oracle.com/message/11264632#11264632 you describe best practice.
The best practice is to install 64-bit ODP.NET following the install instructions. To make sure each application can find its correct unamanged Oracle Client DLLs, I recommend setting the DllPath setting described in Chapter 2 of the ODP.NET Dev Guide. Typically, the problem people run into with multiple ODP.NET versions on the same machine is ensuring each ODP.NET version uses its correct Oracle Client version (i.e. avoiding DLL Hell). Setting DllPath is a straightforward to ensure all your ODP.NET apps will use the right dependent Oracle Client DLLs.
If we are to follow your recommend best practice then we must have different AssemblyVersions with each release. Otherwise, we could load the wrong ODP.NET Oracle.DataAccess.dll from the GAC that doesn't match the unmanaged Oracle Client dlls we specified with the DllPath setting.
If I've missed something, please let me know.

Installing ODAC.Exe Problem - Please Help!

Greetings!
This is the scenario:
1- I have downloaded ODAC Software Release 10.1.0.4.0 to a folder in my Windows 2003 server. (This Worked and the size downloaded is the same as the one shown in the Oracle Website)
2- I double-clicked the .exe file to extract the files. (This worked)
3- The ODAC.Exe created the folder called disk 1(this worked)
4- I double-clicked the Setup.exe to run the Oracle Universal Installer
5- A Command Pronmt windows comes up, it waits around 5 seconds and I get a message saying:
"Error writing to directory "C/Documents~1/Local~1/Temp/ OraInstall .... Please ensure that this directory is writable and it has at least 45MB of free space"
Well, regarding the space, I have more than 30 GB available, so this is not the problem. In addition, I'm logged in as the administrator and I have personally change the folder settings (uncheck the read only box).
Now, the interesting aspect of this is that in the command window, I get a message saying:
C/Document~1/Admin/Locals~1/Temp/OraInstall.../oui/jlib/OraInstaller.jar/ Bad CRC 7f66d50e <should be 335f93a0>
In addition, I searched for the OraInstaller.Jar and I wasn't able to find it.
Please, I need some guidance as at this point i don't know what else to do.
Thank you!
Eduardo

Yes, as the others have said, there's a fair amount of steady force that needs to be applied.
I should be done in one swift, smooth motion. Make sure the MacBook is on a steady soft surfface when you do the ram ejection.
Likewise, when pushing the ram in, follow the instructions (little gap in the pins of the ram to the left), and push firmly and consistently, until it appears that the ram is solidly in.
When you put the L bracket back on, and re-seat the battery then turn on your MacBook, if it boots up correctly, you should be able to open up the 'about this mac' window from the Apple logo menu and see '1GB 667MHz DDR2 SDRAM' listed.
If not, shut down the MacBook, and try again to re-seat the ram, by pressing more firmly, or ejecting the ram and trying again.

Purchase Requisition Release Problem

Hi All,
I have a release procedure set up, and the strategy pulls up correctly when a PR is made. When I view collective release from ME55, the PR's show up, and I am able to release line items from that screen. However, when viewing the PR from ME53N, in the Release Procedure tab there is no green check next to the release code with which to release the line. Also, if I do release the PR from ME55, I cannot go to ME53N and cancel the release from the Release Procedure tab.
I am a user with all security access, so it is not an authorization role problem. The release group is also configured to release by line item, so that is not the problem. I have set up other release procedures which allow the release/cancel release function from ME53N before... what could be the problem this time?
Thanks,
J

hi.
There are two ways of releasing purchase requisitions:
Individual release (Tcode - ME54)
You release items of an individual purchase requisition or - if the requisition has to be released in total - by releasing one item you simultaneously release all the others.
Collective release (Tcode- ME55)
You release all requisition items or complete requisitions that are awaiting processing by your release code. This is the preferred method if you frequently have to effect release.
Display PR -with release status (Tcode-ME53N)
One can only see release status in ME53N & can not change release.
hope it helps to you.
Regards,
Rahul

Purchase Requisition Overall Release problem with several CostCenter

Hello Gurus!!
I need your comments!!!
I define the Purchase requisition as Overall Release, and woks !! but I have a Issue.
I have an entry in the CL24N txn as follow:
AccAssgCat = K
Plant              = CC01
CostCenters = 10001
                        10002
                        10003
totalAmt        = 1USD to 1000US
So when I create my purchase requisition with only 1 Cost Center the release strategy is called and PR can be released.
But When I create the purchase requisition with CC 10001 and 10003, the requisition is not subjet to release!!! (note TotalAmt = 15usd)
I assume that as both are into the release strategy the system will take both CC and ask for release!!
What I can do to fix this situation??

Dear Marco Antonio,
I have never faced your issue, but have an idea of what you can do.
Activate Enhancement M06B0005   EXIT_SAPLEBND_004
Then in the program zxm06u31 put the following code line:
e_ceban = i_ceban.
and also a breakpoint so that it stops automatically upon PR verification or saving.
Activate and then create a PR with the problem you are facing. On saving the program will stop in your breakpoint.
Look at structure i_ceban there you will find the values that your release strategy is getting from the document and with which it will try to determine the strategy based on your classification.
I the standar logic is not what you want maybe you can put some logic of your own based on account assignments in structure C_EBKN.
Well, tell me what happens
Best Regards,
Sebastián Ligueros

Thinkpad A31 Ultrabay Plus release problem

I have a Thinkpad A31 that I'm repairing - I removed the Ultrabay enclosure that the CD-ROM fits into.
I've reinserted it and have issues with the eject lever.
The release mechanism allows the eject lever to come out, but there is no resistance on the eject lever (when pushing it in) with a CD-ROM in the _Ultrabay Plus_. This means that the only way to eject the CD-ROM is to manually pull it out, which requires the keyboard and plastic palm area to be removed.
I have checked the springs and they are present on the eject lever mechanism.
I have a copy of the A31 manual and have read up on the Ultrabay sections.
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-39796
http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/92p1902.pdf
I will work on getting images of the parts/pieces for further information.
Thanks,
Mike
Solved!
Go to Solution.

I've only had to do it once, and that was a while ago, but I believe there's a post by Ray Kawakami on TPF dealing with this problem, I'm just way too tired to look for it now......
With no intention to insult you whatsoever, two bays exibiting the same problem sound like a human error to me...of course, being a human myself, I may very well be wrong...
Good luck.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

[iPhone] AppStore release problem

Hi Guys,
I've got a little problem when I come to release an app.
I've watched the video regarding AppStore releases on iTunes and read all the other stuff, I think my xcode is all setup fine.
When I come to build the app using my release profile, it all builds fine. However when it comes to install the app on the phone, i get the error:
Your mobile device has encountered an unexpected error (0xE800003A) during the install phase: Verifying application
How can I fix this? To me it looks like the phone doesnt have the correct key install so it cant validate the app? I'm going to do a vanilla install of iPhone OS, any thoughts?

Hey, I'm having a somewhat similar problem in that my development builds all work fine, my app is debugged and ready for distribution build so i can upload to itunes connect but for some reason the distribution prov. profile is not showing up as an option under 'Code Signing Provisioning Profile' in project info (i have 'Code Signing Identity' set to 'iPhone Distribution: MYNAME').
I created a distribution certificate and distribution profile. I have both certificates in keychain access (development and distribution) as well as the WWDC certificate. i have a private/public key pair for each cert. i have the distribution provision file in the 'provision profiles' directory and it shows up under provisioning area under each device i have in 'organizer' (even tho i can't select it since it's distribution).
I have spent like three hours no trying to figure this out. (i even deleted/revoked both development and distribution certificates and prov. profiles and started over to no avail) Anyone have any idea???

Billing releasing problem in vf02

Hi
At the time of releasing the billling document below error will appeared
Delivered/invoiced quantities cannot be updated in CO
This is the error messege
Delivered/invoiced quantities cannot be updated in CO
Message no. KI137
Diagnosis
For account assignment object WBS CP.0065.2, the delivered or billed quantity is to be updated in the unit of measure EA for material number 1025697.
The system has found a totals record (COSL) that already exists for the account assignment object WBS CP.0065.2 with unit of measure KG. However, you cannot convert the quantity from EA to KG.
System Response
The quantity cannot be updated in the totals record, which means that the quantity is missing for the receiver after the settlement of WBS CP.0065.2 (for example in CO-PA). Only the posted quantity is saved in the CO line item (COEPL table).
Procedure
Change the material KG and define KG in the master data record as an additional unit of measure.
If you can have the quantity in EA in the COSL totals record without it causing any problems, you can deactivate this error message in customizing, or change it to a warning or information message.
To do this, see the implementation guide (IMG) for "General Controlling" under the following activity: Change Message Control (work area KI, message no. 137).
If you have any questions, contact your CO consultant.

Solution is any of these.
1. Change Units of measure of WBS element from EA to KG - PS
2.Change the material unit of measure from KG to EA -MM
3. Define conversion rules between UOM EA and KG - MM

WS2000077 (Purchase Requisition Release) problem

Dear all
workflow task WS2000077 (Purchase Requisition Release) causes the following problem:
While executing an approval release (ME54N) through workflow, the result is always 'requisition release refused'.
Does anyone know why?
I appreciate your help in advance

Hi,
Go through the below links it may help you...
Workflow Definition WS20000077 and sequence of the events, significantly...
po release workflow issue/problem
PR Workflow problem
std workflow ; user to role agent assignment ?
Regards,
Udaya.

PO Cancel release problem

Hi, experts:
I am a beginer of SAP workflow, I've got a problem when testing customized PO cancel release workflow.
My workflow is quite simple, just test whether the event 'SIGNIFICANTLYCHANGED' was trigered when cancel PO. I will receive information in my SAP Business workplace.
Here is the configuration of PO release Strategies:
RGroup Rcode Workflow Agent
PO     C1     1     Blank
PO     C2     1     Blank
PO     C3     1     Blank
PO     C4     1     Blank
In my customized workflow template, I use the event 'SIGNIFICANTLYCHANGED' to deal with PO cancel release.
But I find that this event will not be triggered from Level C4 cancel to C3.
Here is my test result:
Cancel        Result
C4->C3       Not triggered
C3->C2       Trigered
C2->C1       Trigered
I can get the result from my Business workplace except cancel PO from C4 to C3.
Does anyone come across with this problem?
Please tell me why and how to handle it, thanks a lot!
Best regards!

Hi,Swaminathan PJ
Appreciate for your reply!
So, shall we change another event or even customize our own event?
My requirement is that send e-mail with PO item detail (*.xls file) to specified users when final release or cancel final release.
Thank you for any good advice.
Best regards!

Purchase Requistion : Overall Release Problem

Hi everybody,
Have a peculiar problem where Item Level release seems to be working fine. And the first time we want to use release at header level and its not working.
The OverReqRel (overall requisition release) is 'checked' [at release group level].
There is just one class, one characteristic within that class (document type).
There is just one group, release code, release indicator and release strategy.
The classification has 'NB' as the document type to be controlled.
The simulation works fine.
The 'Check Release Strategies' shows 'all green' with no errors.
But when we create a PR (txn ME51N) for document type NB, this procedure does not kick in (hence i dont see a new tab at the header level asking for a release).
We have been using item wise release before and are testing the viability of release at header level.
FYI. This is a test system (sandbox) where we have NO configuration for release procedure. This is the first strategy that has been created for testing.
Any help in getting this to work is most welcome.

Hi,
For the document type NB, did you flaged as PR header level release.
Regards,
Ramakrishna

PO releasing problem through ME28

Hi,
When i release the PO from ME28, system showing the following message : - No suitable purchasing documents found..
Note: - I define the new number range for the another plant. also created the new document type for it. PO makes succesfully, but when i m releasing this, showing that message.
What should be the problem here or we should define the release streatgy for New document type / number range.
Plz help...

Check following things
1. You have correctly considered document types in classification
2. All plants have been taken into account in classification
3. Also check the PO value
And also see whether charachterstics, classes has been created and there has been proper assignment of both.
Regards,
SS

Transport request main task releasing problem

Hi friends,
Environment is Linux, ECC5.0, Two system landscape,
I have problem with Transport Request task releasing when I am going to release the subtask that willbe released success fully when I am trying to releasing the main task that task is not released and at that time the system wil hang( mesg on the status bar is tp is connected success fully) thats it we wait for long time then also that looks thats only no log will be generating in usr/sap/trans/log there will be a log on this one that log is
WARNING:/usr/sap/trans/tmp/<username.LOS>is already in use (10), I'm waiting 3 sec(20070326124305). My name:pid 7265 on test(sd1adm)
after saw the this mesg I kill the 7265 pid then also same proablem.
I change the ownet of the request then the request is released but not uppeard in the import que. whn i am trying to import in que as manually that will appear in que but not importing when i press the import button the error is tp error 0203.
I check the both users authorizations also bothe authorizations also same then why it wil happening ???
then I check the nfc also that service also running ok the six services are 1.off 2.off 3.on 4. on 5.on 6.off.
I mount the trans dir also the mounting points also ok tms configuration is also ok
wt can i do plz help me with ur valuable suggessions
Thankyou
Ranjith

Hello Ranjith,
This is usually because the tp transport buffer lock file remains locked by the
operating system (OS).
You should be able to move or delete this file from the DIR_TRANS/tmp dir.
After that the tp should run fine after.
Thanks,
George

MM Service Entry Sheet Release Problem - Plant Not Considered

Dear Experts,
I have a problem in Service Entry Sheet Release as it does not consider plant although it is maintained in Release Strategy.
I have created 1 Class for Service Entry Sheet Release.
This class contains 3 Characteristics, 1st for Plant, 2nd for Value of Services and 3rd for Purchasing Group.
Now the problem is that during the Entry Sheet Release, system does not consider the Plant in deciding the Release Strategy.
It considers the first Release Strategy found for Purchase Group and Value of Service combination, thus ignoring the Plant Characteristic.
Characteristic for Plant is having 'Released' Status
Please suggest what to do so that the Plant is also considered in Release Strategy.

Dear Charlie,
Thanks for your reply.
When I go to CL40N and check then system gives correct Release Strategy as it considers plant there.
But when actually the Entry Sheet is created/saved then system gives wrong release strategy as it does not consider Plant.
Let me tell you that my Release Strategies do contain common Purchase Groups but the Plants are different. So each Release Strategy is unique in this way.
But during Service Entry Sheet Creation system does not consider Plant in determining Release Strategy.
Please Help.

STMS change request release problem

Hi
I am not able to release change requests, sab task able to release, but problem in main request, when I press , release directly, on the bottom it shows u2026tp successfully connected / check writeability of buffers finished with return cod 0. Then screen hangs u2026 manually I have to stop the transition.
I have configured STMS 4,5 times but same problem, in SM59 all retaliated RFCs working fine.
Our System is ERP 6.0, HPUX with DB2
Kindly give me a solution.
But in Tcode STMS >>Monitor>>TMS Alerts>>TMS Alert viewer showers following error:
Date       Time       User           Function      Message                                            System   Clt
23.05.10   17:29:07   TMSADM         TMS_TS_GET_TRLIST    NO_LOG                SID      000
23.05.10   16:58:25   TMSADM         TMS_PS_READ_PROFILE_FROM_DISK                               READ_PROFILE_FAILED                                            SID      000
23.05.10   16:57:30   TMSADM         TMS_PS_READ_PROFILE_FROM_DISK                                 READ_PROFILE_FAILED                                            SID      000
23.05.10   15:55:59   TMSADM         TMS_TP_MAINTAIN_BUFFER                                        RFC_SYSTEM_FAILURE                                             SID      200
23.05.10   15:05:36   TMSADM         TMS_TS_GET_TRLIST                                             NO_LOG                                                         SID     000
23.05.10   15:01:29   TMSADM         TMS_TS_GET_TRLIST                                             NO_LOG                                                         SID     000
23.05.10   14:53:00   TMSADM         TMS_TS_GET_TRLIST                                             NO_LOG                                                         SID    000
23.05.10   14:51:38   TMSADM         TMS_TS_GET_TRLIST                                             NO_LOG                                                         SID      000
Regards
Sunny

Hi Sunny,
Its hard to tell what might be the problem.
I would recommend that you:
- update kernel to the latest patch level for your release
- update your transport tools, tp and R3trans to the latest available for your release
- go into STMS - system pverview and do the 3 checks: Connection test, transport directory, transport tool
check if they all pass.
- try to release a transport and then if it still freezes after all of the above, stop it and check the system log, trans.log, the latest logs in usr/sap/trans/tmp and usr/sap/trans/log to see what was the action it was doing before it froze. That will give a clue as to where the issue may be.
regards,
Paul

ODAC release 2 problem

Similar Messages

Maybe you are looking for