Oracle 10g support
Oracle 10g support windows#
Oracle 10g support 64 Bit#
Oracle Developer Suite 10g is not officially certified to be installed on Windows’10 64 bit desktop client, But still it can be installed on Windows 10 64 bit by following the below workaround. You have tried changing the compatibility of the setup.exe to Windows XP and running as an Administrator, But no luck. Assuming you can get this work, you need not concern yourself with transaction enlistment, propagation and flow because when configured correctly the framework will transparently handle this for you.When installing the certified version of Oracle Developer Suite 10g (10.1.2.0.2) for custom forms/reports development in E-Business Release 12 on windows 10+64 bit client desktop, The command prompt shows up, then gracefully exists the Oracle Universal Installer never shows up.
Oracle 10g support code#
In my opinion, you would be better to pursue your first code example which uses TransactionScope. Note that it is generally poor design to pass around the connection/transaction pair outside of you data access code. Therefore, explicitly creating the transaction may not be necessary (check documentation). On your operation contract is the TransactionFlowOption set to Mandatory or Allowed? In other words, do you intend to always flow a transaction into your service operation? If so, do you really want to create a nested transaction inside of your service operation? If not, do you want to create a new transaction if none exists? I believe that if TransactionScopeRequired=true and the caller does not flow a transaction, the service operation will automatically create and execute within a new transaction scope. To be honest, I’m not entirely sure what behaviour you are trying to achieve. Without actually trying it, I’m not sure if your code samples above will work. Subsequent databases within the transaction may be Oracle 10g. However, if you have multiple databases participating in the same distributed transaction, the first database to be accessed within the transaction must be Oracle 11g. My tests have shown that an 11.1.0.7.10 client will quite happily participle in a distributed transaction with a single Oracle 10g server. After contacting Oracle Technical Support, I learned that this functionality is only supported in version 11.1.0.7.10. I tried to get promotable distributed transactions working using previous versions of ODP.NET / OraMTS on the client and failed miserably. "Please note that it does not work in any previous versions" I mean exactly that. TransactionOptions oTxOption = new TransactionOptions() oTxOption.IsolationLevel = oTxOption.Timeout = TimeSpan.FromMilliseconds(AppContext.DefaultDBMaxTimeoutMillisec) using (oScope = new TransactionScope(TransactionScopeOption.Required, oTxOption)) Will it work? (This is actually not best example - usually only transaction that span user-think-time gets across WCF boundary - certainly not withdraw-deposit scenario) I already tried: (a) Make sure Transaction isolation level not "Serializable". Sorry it took so long - been really busy. "Make sure to use ReadCommitted, not Serializable transactions." The Oracle Data Access Components for 11.1.0.7.10 beta can be downloaded from here:. Subsequent resource managers can be older than 11g and still be promoted.)" (Or more accurately, the first database that joins the transactions needs to be 11g. "The Oracle Database server requires 11g. "TransactionScopes and promotable transactions are supported in ODP.NET v 11.1.0.7.10 and OracMTS v11.1.0.7.10." ODP.NET releases prior to this beta support transactions that are set up as distributed only or local only at design time."
What hasn't been supported until this recent ODP.NET 11.1.0.7.10 beta is promotable transactions. "TransactionScope has been supported for quite some time.
I contacted Oracle for technical support and received the following response, which I have paraphrased:. Hi Devvvy, I was experiencing similar issues trying to use TransctionScope to perform distributed transaction across WCF Services, with an Oracle 10g database server and ODP.NET 10.2.0.2.21.