Medrec pointbase orace RDBMS migration (Cannot set auto-commit mode)

For proof-of-concept purposes, I'm trying to install the MEDREC application on an Oracle database. I've migrated the schema using the demo.ddl found on the base install image. However, when I update the JDBC connect string to point to the oracle rdbms, I rec'v the message below. Has anyone discovered a workaround?
After the jdbc connect string is updated to point to Oracle, I see the app server connected successfully to the database.
javax.ejb.EJBTransactionRolledbackException: EJB Exception: ; nested exception is: <openjpa-1.1.0-r422266:657916 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: Cannot set auto-commit mode when using distributed transactions
     at weblogic.ejb.container.internal.BaseLocalObject.handleSystemException(BaseLocalObject.java:794)
     at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:486)
     at weblogic.ejb.container.internal.BaseLocalObject.postInvokeTxRetry(BaseLocalObject.java:424)

Similar Messages

Oracle.xml.sql.OracleXMLSQLException:Cannot enable auto commit within JTS transaction

Hi All,
OracleXMLSave class in the Oracle XDK is being used to load XML data into an 8170 database. The Java code is running in IBM WebSphere with container-managed transactions. When JTA is enabled with the Merant JDBC driver for Oracle, we get the following error when the XML is loaded:
oracle.xml.sql.OracleXMLSQLException: Cannot enable auto commit within JTS
transaction
     at java.lang.Throwable.fillInStackTrace(Native Method)
     at oracle.xml.sql.dml.OracleXMLSave.saveXML(OracleXMLSave.java:2213)
     at oracle.xml.sql.dml.OracleXMLSave.insertXML(Compiled Code)
This suggests the OracleXMLSave class is not aware of the fact that it is now operating in a JTS transaction where control is managed elsewhere. i.e. should also not attempt to commit or rollback, as this is the responsibility of the container.
Is there a property which needs to set to prevent the above or does the XDK not work with J2EE (JTS) transactions?.
If you have any useful comments, let me know. Testing the above presents me with a number of problems so if this is easily explained , let me know.
Thanks,
Malcolm

Clearly , there does seem to be something a bit odd with the above stack.
<Bug:1917808> mentions OracleXMLSave in context of plsql equivalent : dbms_xmlsave . i.e dbms_xmlsave is a wrapper around OracleXMLSave class.
disabling autocommit on connection as follows should help:
conn = DriverManager.getConnection("connect string","scott","tiger");
conn.setAutoCommit(false);
to disble auto commit and see if this has an effect.
This issue might be <Bug:1497506>. If disabling autocommit does not work then it appears that it could be this issue .
Malcolm
Hi All,
OracleXMLSave class in the Oracle XDK is being used to load XML data into an 8170 database. The Java code is running in IBM WebSphere with container-managed transactions. When JTA is enabled with the Merant JDBC driver for Oracle, we get the following error when the XML is loaded:
oracle.xml.sql.OracleXMLSQLException: Cannot enable auto commit within JTS
transaction
     at java.lang.Throwable.fillInStackTrace(Native Method)
     at oracle.xml.sql.dml.OracleXMLSave.saveXML(OracleXMLSave.java:2213)
     at oracle.xml.sql.dml.OracleXMLSave.insertXML(Compiled Code)
This suggests the OracleXMLSave class is not aware of the fact that it is now operating in a JTS transaction where control is managed elsewhere. i.e. should also not attempt to commit or rollback, as this is the responsibility of the container.
Is there a property which needs to set to prevent the above or does the XDK not work with J2EE (JTS) transactions?.
If you have any useful comments, let me know. Testing the above presents me with a number of problems so if this is easily explained , let me know.
Thanks,
Malcolm

Cannot enable auto commit within JTS using websphere

i suddenly encountered some exceptions like this yet the process seems to be ok. i am pretty new to websphere, help please:
java.lang.IllegalStateException: Cannot enable auto commit within JTS transaction
     at com.ibm.ejs.cm.pool.ConnectO.setAutoCommit(ConnectO.java:2085)
     at com.ibm.ejs.cm.proxy.ConnectionProxy.setAutoCommit(ConnectionProxy.java:594)

I'm setting autoCommit to false in some of my code and it works. Here is the example:
//This code works for the Oracle Thin Driver
               conn.setAutoCommit(false); // <- required!
             // initialize LOB reference
             GDate curDate = new GDate();
             ps = conn.prepareStatement("insert into Calculated_Rate_Import values (empty_clob(), ?)");
             //conn.createStatement().executeUpdate("insert into Calculated_Rate_Import values (empty_clob(), TO_DATE('" + GDate.getSafeSqlDate(curDate) + "'))");
             ps.setTimestamp(1, GDate.getSafeTimestamp(curDate));
             ps.executeUpdate();
             ps = conn.prepareStatement("select Calculated_Rate_Import from Calculated_Rate_Import where Import_Date = ? for update");
             ps.setTimestamp(1, GDate.getSafeTimestamp(curDate));
               results = ps.executeQuery();
             results.next();
             // get lob reference from write lock
                 //oracle.sql.CLOB clob = ((oracle.jdbc.driver.OracleResultSet)results).getCLOB(1);
               oracle.sql.CLOB clob = (oracle.sql.CLOB)results.getClob("Calculated_Rate_Import");
             // create statement for update
             ps = conn.prepareStatement("update Calculated_Rate_Import set Calculated_Rate_Import = ? where Import_Date = ?");
             // stream data into lob
             java.io.OutputStream os = ((oracle.sql.CLOB)clob).getAsciiOutputStream();
             try{
                  os.write(fileContents.getBytes());
                       os.close();
             }catch(IOException e){
                  e.printStackTrace();
             // execute update
             //((oracle.jdbc.driver.OraclePreparedStatement)ps3).setCLOB(1, clob);
             ps.setClob(1, clob);
             ps.setTimestamp(2, GDate.getSafeTimestamp(curDate));
             ps.executeUpdate();
             // close lock
             results.close();
             conn.commit();
             //finished inserting CLOB
             //set the auto commit back to true, required!
               conn.setAutoCommit(true);

Exchange 2013 OWA: Cannot set auto reply in shared mailbox

We use Exchange 2013 and Outlook 2010. We have 3 users tha connect to a shared mailbox. We would like to have an auto-reply on this mailbox but cannot set it with the OWA. We get the following error:
Client Information
User Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; InfoPath.3)
CPU Class: x86
Platform: Win32
System Language: nl-NL
User Language: nl-NL
CookieEnabled: true
Exception Details
Date: Fri Jul 11 11:31:40 UTC+0200 2014
Message: Kan de eigenschap _events van een niet-gedefinieerde verwijzing of een verwijzing naar een lege waarde niet ophalen
Url:
https://owa.'domainname'.nl/ecp/15.0.712.22/scripts/microsoftajax.js
Line: 5
Call Stack
Dump Event
errorMessage = Kan de eigenschap _events van een niet-gedefinieerde verwijzing of een verwijzing naar een lege waarde niet ophalen
errorUrl =
https://owa.'domainname'.nl/ecp/15.0.712.22/scripts/microsoftajax.js
errorLine = 5
errorCharacter = 57312
errorCode = 0
actionURL =
altKey = false
altLeft = false
behaviorCookie = 0
behaviorPart = 0
bookmarks = null
boundElements = [object HTMLCollection]
button = 0
buttonID = 0
cancelBubble = false
clientX = 1187
clientY = 72
contentOverflow = false
ctrlKey = false
ctrlLeft = false
data =
dataFld =
dataTransfer = null
fromElement = null
keyCode = 0
nextPage =
offsetX = 0
offsetY = 0
origin =
propertyName =
qualifier =
reason = 0
recordset = null
repeat = false
returnValue = true
screenX = 2373
screenY = 343
shiftKey = false
shiftLeft = false
source = null
srcElement = null
srcFilter = null
srcUrn =
toElement = null
type = error
url =
wheelDelta = 0
x = 0
y = 0
getAttribute =
function getAttribute() {
    [native code]
removeAttribute =
function removeAttribute() {
    [native code]
setAttribute =
function setAttribute() {
    [native code]
Detailed Call Stack

Hi,
Error information is quite important. In order to solve your issue effectively, please take your time to describe the error in English for my research.
Best regards,
Amy Wang
TechNet Community Support

Setting auto-commit inside a transaction

I am trying Kodo 2.4 RC3 with JBoss 3.0.4 and Hypersonic SQL DB
1.7.1b (in server mode) on Mac OS X 10.2.2 and get the exception listed
below. I understand that the autocommit property of the database
connections should be off in order to avoid this error, but how can I
achieve this?
[java] java.sql.SQLException: You cannot set autocommit during a
managed transaction!
[java] at
org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.setJdbcAutoCommit(LocalManagedConnection.java:447)
[java] at
org.jboss.resource.adapter.jdbc.local.LocalConnection.setAutoCommit(LocalConnection.java:426)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.getConnection(SQLExecutionManagerImpl.java:149)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.prepareStatementInternal(SQLExecutionManagerImpl.java:805)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedQueryInternal(SQLExecutionManagerImpl.java:760)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQueryInternal(SQLExecutionManagerImpl.java:692)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQuery(SQLExecutionManagerImpl.java:373)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQuery(SQLExecutionManagerImpl.java:357)
[java] at
com.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl.getSubclasses(SubclassProviderImpl.java:231)
[java] at
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.getPrimaryMappingFields(ClassMapping.java:1093)
[java] at
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.loadByPK(ClassMapping.java:931)
[java] at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.initialize(JDBCStoreManager.java:263)
[java] at
com.solarmetric.kodo.runtime.StateManagerImpl.loadInitialState(StateManagerImpl.java:174)
[java] at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.getObjectByIdFilter(PersistenceManagerImpl.java:986)
[java] at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.getObjectById(PersistenceManagerImpl.java:888)
[java] at
im.jdo.JDOWorker$IssueWorker.getIssue(JDOWorker.java:952)
[java] at
im.jdo.JDOWorker$IssueWorker.getIssue(JDOWorker.java:810)
[java] at
im.jdo.JDOWorker$IssueWorker.access$2400(JDOWorker.java:789)
[java] at im.jdo.JDOWorker.getIssue(JDOWorker.java:1089)
[java] at im.jdo.JDOWorker.getIssue(JDOWorker.java:1079)
[java] at
im.ejb.impl.MeisterSessionBean.getIssue(MeisterSessionBean.java:280)
[java] at java.lang.reflect.Method.invoke(Native Method)
[java] at
org.jboss.ejb.StatefulSessionContainer$ContainerInterceptor.invoke(StatefulSessionContainer.java:817)
[java] at
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130)
[java] at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:186)
[java] at
org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(StatefulSessionInstanceInterceptor.java:268)
[java] at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:107)
[java] at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:178)
[java] at
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60)
[java] at
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:204)
[java] at
org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContainer.java:380)
[java] at org.jboss.ejb.Container.invoke(Container.java:712)
[java] at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
[java] at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:382)
[java] at java.lang.reflect.Method.invoke(Native Method)
[java] at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:236)
[java] at sun.rmi.transport.Transport$1.run(Transport.java:147)
[java] at java.security.AccessController.doPrivileged(Native
Method)
[java] at
sun.rmi.transport.Transport.serviceCall(Transport.java:143)
[java] at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
[java] at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
[java] at java.lang.Thread.run(Thread.java:491)

Jakob,
That's a good question. I don't have much experience with HSQLDB and
JBoss, but I imagine that there's a configuration option somewhere
that's setting autocommit to true. We only try to set autocommit to
false if we see that it's set to true (by invoking conn.getAutoCommit()).
What do your HSQL properties look like? Do you get any hits when running
'grep -ri autocommit /path/to/jboss' from a terminal window?
-Patrick
Jakob Spies wrote:
I am trying Kodo 2.4 RC3 with JBoss 3.0.4 and Hypersonic SQL DB
1.7.1b (in server mode) on Mac OS X 10.2.2 and get the exception listed
below. I understand that the autocommit property of the database
connections should be off in order to avoid this error, but how can I
achieve this?
[java] java.sql.SQLException: You cannot set autocommit during a
managed transaction!
[java] at
org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.setJdbcAutoCommit(LocalManagedConnection.java:447)
[java] at
org.jboss.resource.adapter.jdbc.local.LocalConnection.setAutoCommit(LocalConnection.java:426)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.getConnection(SQLExecutionManagerImpl.java:149)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.prepareStatementInternal(SQLExecutionManagerImpl.java:805)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedQueryInternal(SQLExecutionManagerImpl.java:760)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQueryInternal(SQLExecutionManagerImpl.java:692)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQuery(SQLExecutionManagerImpl.java:373)
[java] at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQuery(SQLExecutionManagerImpl.java:357)
[java] at
com.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl.getSubclasses(SubclassProviderImpl.java:231)
[java] at
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.getPrimaryMappingFields(ClassMapping.java:1093)
[java] at
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.loadByPK(ClassMapping.java:931)
[java] at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.initialize(JDBCStoreManager.java:263)
[java] at
com.solarmetric.kodo.runtime.StateManagerImpl.loadInitialState(StateManagerImpl.java:174)
[java] at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.getObjectByIdFilter(PersistenceManagerImpl.java:986)
[java] at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.getObjectById(PersistenceManagerImpl.java:888)
[java] at
im.jdo.JDOWorker$IssueWorker.getIssue(JDOWorker.java:952)
[java] at
im.jdo.JDOWorker$IssueWorker.getIssue(JDOWorker.java:810)
[java] at
im.jdo.JDOWorker$IssueWorker.access$2400(JDOWorker.java:789)
[java] at im.jdo.JDOWorker.getIssue(JDOWorker.java:1089)
[java] at im.jdo.JDOWorker.getIssue(JDOWorker.java:1079)
[java] at
im.ejb.impl.MeisterSessionBean.getIssue(MeisterSessionBean.java:280)
[java] at java.lang.reflect.Method.invoke(Native Method)
[java] at
org.jboss.ejb.StatefulSessionContainer$ContainerInterceptor.invoke(StatefulSessionContainer.java:817)
[java] at
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130)
[java] at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:186)
[java] at
org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(StatefulSessionInstanceInterceptor.java:268)
[java] at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:107)
[java] at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:178)
[java] at
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60)
[java] at
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:204)
[java] at
org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContainer.java:380)
[java] at org.jboss.ejb.Container.invoke(Container.java:712)
[java] at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
[java] at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:382)
[java] at java.lang.reflect.Method.invoke(Native Method)
[java] at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:236)
[java] at sun.rmi.transport.Transport$1.run(Transport.java:147)
[java] at java.security.AccessController.doPrivileged(Native
Method)
[java] at
sun.rmi.transport.Transport.serviceCall(Transport.java:143)
[java] at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
[java] at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
[java] at java.lang.Thread.run(Thread.java:491)
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com

Set auto commit to false

Hi
I have problems with multiple updates causing a Block in the database.In order to solve this I am trying to set commits to false and true explicitly before and after updates.Since I am performing updates within a loop I would like to know if I need to explicitly inside the loop.
For eg can i do something like this
for (int i = 0;i < part_Vect.size() ;i++) {
conn.setCommit(false);
sql = Update stmt;
stmt.executeUpdate(sql);
conn.setCommit(true);
} // end loop
or should i set the commits outside the loop
Thanks
Arn

Most of the time I'd put the commit related stuff outside of the loop to reduce the number of database calls and guarantee data integrity. There are a couple of factors to consider though.
1. Whether you want all the updates to be committed in one transaction. If there is a failure in the middle of your operation, is it ok if some updates have been performed and others have not. Can you restart and recover correctly? If you need a single transaction, then the commit code should be outside of the loop.
2. The number of updates. The more updates there are in a transaction, the more database locks will be required and the greater the performance hit. The limit depends on your configuration and access needs. If there are several thousand updates and many other users who need to read the data, a different design may be required.

Forms 6i / Auto-Commit-Mode

How can i make Forms 6i to do an automatic commit after entering a value into a database-item?
null

Thank you very much!
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Sandeep Biswas ([email protected]):
Write a key-exit trigger with the following code:
if :system.form_status = 'CHANGED' then
commit_form;
/* if commit failure */
if :system.form_status <> 'QUERY' then
/* display error */
raise form_trigger_failure;
end if;
end if;
exit_form;<HR></BLOCKQUOTE>
null

Auto commit in apex

Hello Sir,
how can i set auto commit on/off using apex in application builder, auto commit is there in sql command but not in application builder,it is possible to set auto commit using coding in apex processes or PL/SQL Block.
please help me.
Thanks in Advance,
Regards,
Jack R.

Hi Varad,
Thanks for your quick reply,
I want to manually handle commit and rollback on DML.
can you explain about a stateless transaction model and span requests in apex?
Thanks & Regards,
Jack R.

Auto-Commit and Pooled JDBC Connections

Forum Members,
If I am using Oracle Pooled JDBC Connections in the OC4J container is auto-commit set to "true" by default?
If I set auto-commit to "false" and then close the logical connection, when that connection is handed out again on a later call to getConnection(), is auto-commit automatically set back to "true"?
Thanks,
Richard

Richard,
Pardon me if I am stating the obvious, but you could test that in your code by invoking the getAutoCommit() method in interface java.sql.Connection.
My experience (with OC4J stand-alone versions up to -- and including -- 10.1.2) is that the behaviour depends on which data source you have configured. For example, if you have defined an "ejb-location" attribute in your "data-sources.xml" file, and you use that as your JNDI lookup for your data source, then OC4J handles transactions and you shouldn't deal with "auto-commit" at all. See the following post for more details:
Re: OC4J 10.1.3 Preview 4 - Global transaction active
But if you have defined a "location" attribute and use that, then you do need to handle transactions explicitly.
Hope this helps.
Good Luck,
Avi.

Auto Commit from PL/SQL

Hello All,
Is this possible to set Auto Commit on/off
between DM statements in a PL/SQL block
Please suggest me.
Thanks in advance.

No, you will have to explicitly issue a COMMIT or ROLLBACK when it makes sense to do it.
The autocommit feature of SQL*Plus (a client application) is not available inside PL/SQL.
However, an entire PL/SQL block when run from SQL*Plus would be considered as one statement (unit) and autocomit (if enabled) will commit all DML statements performed inside the PL/SQL block (and any blocks called from it).
Generally, its not a good idea to use this autocommit feature (even if available) since you lose all the control over your transactions. Your transaction never spans one single statement at a time.

What does the setting "auto increment column templates"

I have noticed that there is now a setting "auto increment column templates" but I cannot find out what this setting does.
There are no sequences generated nor triggers.
Version 3.0.
Thanks, Joep

There are no sequences generated nor triggersYou need to set column as "auto increment". Then sequence and trigger will be generated for Oracle.
You can set template for generated sequences and triggers and can override these settings at column level setting explicitly the name of sequence and trigger.
The sequence and related trigger are not created as objects in physical model, however if there are such objects defined then definition from physical model is used for generated DDL.
Philip

APP-10367: You cannot set up your Payables ...

Hello Everyone,
I'm migrating some forms from 11.5.9 to 12.1.3...
I'ts a complete customized module called SP.
In two forms. when I enter them, I get the message:
"APP-10367: You cannot set up your Payables options without first setting up your financials options.
Set up your financials options in the FInancials Options window."
Coincidentally, these 2 forms have account combinations fields, and they are not working.
Anyone had this problem?
Coudn't find anything on My Oracle Support or Google itself.
Thank You all in advance

Before you do anything, go to Help | Check For Updates and install v3.6.16. There was a security breach at Comodo which is an SSL certificate provider whereby a number of fraudulent certificates were inadvertently issued. This allows a hacker to impersonate any site including online banking and your browser will not display a warning. The latest update in the 3.6.x series blacklists those certificates.
On the subject of the homepage you asked about, it's probably this add-on: https://addons.mozilla.org/en-US/firefox/addon/homepage-randomizer/

P6N SLI Platinum- Cannot set Memory Speed -Manual/Linked

It doesn't seem to matter whether I have the memory set to Linked or Manual- I get the Linked setting in any OC setup. ??? At stock AUTO, it puts it at the rated 800mhz (pc6400), though.
So for a 1520FSB setting (=380), it sets the memory to 760 in both the Linked setting and the Manual setting. Sounds like something in the bios, but I have tried the 1.0, 1.1, and 1.22b bioses with the same result!
Unfortunately, I recorded my OC settings but not the output on my first numerous attempts. But I want to say that originally, when I started the OC's, when I set the memory to Manual it ended up being Linked. And vice versa. So that at 1400FSB (350) --Linked, it gave me the 800 Memory setting and at 1400 (350) --Manual, it gave me 700 on the memory. But I'm not positive now (about a hundred OC settings later --and yes now I've been writing it down) that it ever worked right.
Any help or thoughts? Anyone else with this problem? Any fixes?

Quote from: Maesus on 02-May-07, 22:57:14
MSI BIOS is not flexible in overclocking or changing DDR RAM Timing settings. Please live with it and trial and error with the RAM timing setting that yields the best result.
I'm just supposed to accept the fact that you cannot set the ram to a manual timing, that it will always run as linked..... then why have the option to select it in the bios if it's not going to be functional. That's just unacceptable! live with it......right ! That's shoddy at best.!
Didn't have this problem with any Asus board (which has been several) or Abit board that I've owned!
And why is noone reporting this same behavior from their board and bios in this forum or over in hardforum or in the anandtech threads????

In FrameMaker 9.0.3 and 9.0.4, I cannot set tab stops for a style in the Paragraph Designer.

In FrameMaker 9.0.3 and 9.0.4, I cannot set tab stops for a style in the paragraph designer. Here are the steps to dysfunction:
1. In Paragraph Designer, for Tab Stops, click Edit. Edit Tab Stop dialog box opens, and the Paragraph Designer dialog box closes.
2. Type value in New Position box.
3. Click Continue. The Edit Tab Stop box closes.
4. Open Paragraph Designer. No tabs are recorded.
Discussion of a similar problem occured on this forum in June 2010. At that time, the resolution seemed to be to upgrade to 9.0.3. Has anyone else encountered this problem with these versions?
Thanks.

Hi, Arnis,
Brilliant! Thanks so much. I only looked at the later discussions of that thread, which seemed to indicate the problem would be solved by an upgrade to 9.0.3.
-Trish

When I click the iCloud button I get a browser with check boxes, not slider buttons and it does not have a "backup and storage" button. So I cannot set up backup.

When I open my iCloud browser it looks different than "normal." It shows the list with check boxes, not slider on-off buttons. It dos not show a "storage and backup" button so I cannot set up my backup. What is wrong?

If see something like the image below it's because you are looking at the iCloud settings on your Mac, not on an iOS device (which has sliders). Storage & Backup isn't in the Mac settings because you cannot back up your Mac to iCloud. Only iOS devices can back up to iCloud. On a Mac, you can get information about your iCloud account storage by looking at the green usage bar at the bottom and by clicking the "Manage..." button on the bottom right.

Medrec pointbase orace RDBMS migration (Cannot set auto-commit mode)

Similar Messages

Maybe you are looking for