(new?) performance problem using jDriver after a Sql Server 6.5 to 2000 conversion
Hi,
This is similar - yet different - to a few of the old postings about performance
problems with using jdbc drivers against Sql Server 7 & 2000.
Here's the situation:
I am running a standalone java application on a Solaris box using BEA's jdbc driver
to connect to a Sql Server database on another network. The application retrieves
data from the database through joins on several tables for approximately 40,000
unique ids. It then processes all of this data and produces a file. We tuned
the app so that the execution time for a single run through the application was
24 minutes running against Sql Server 6.5 with BEA's jdbc driver. After performing
a DBMS conversion to upgrade it to Sql Server 2000 I switched the jDriver to the
Sql Server 2000 version. I ran the app and got an alarming execution time of
5hrs 32 min. After some research, I found the problem with unicode and nvarchar/varchar
and set the "useVarChars" property to "true" on the driver. The execution time
for a single run through the application is now 56 minutes.
56 minutes compared to 5 1/2 hrs is an amazing improvement. However, it is still
over twice the execution time that I was seeing against the 6.5 database. Theoretically,
I should be able to switch out my jdbc driver and the DBMS conversion should be
invisible to my application. That would also mean that I should be seeing the
same execution times with both versions of the DBMS. Has anybody else seen a
simlar situation? Are there any other settings or fixes that I can put into place
to get my performance back down to what I was seeing with 6.5? I would rather
not have to go through and perform another round of performance tuning after having
already done this when the app was originally built.
thanks,
mike
Mike wrote:
Joe,
This was actually my next step. I replaced the BEA driver with
the MS driver and let it run through with out making any
configuration changes, just to see what happened. I got an
execution time of about 7 1/2 hrs (which was shocking). So,
(comparing apples to apples) while leaving the default unicode
property on, BEA ran faster than MS, 5 1/2 hrs to 7 1/2 hrs.
I then set the 'SendStringParametersAsUnicode' to 'false' on the
MS driver and ran another test. This time the application
executed in just over 24 minutes. The actual runtime was 24 min
16 sec, which is still ever so slightly above the actual runtime
against SS 6.5 which was 23 min 35 sec, but is twice as fast as the
56 minutes that BEA's driver was giving me.
I think that this is very interesting. I checked to make sure that
there were no outside factors that may have been influencing the
runtimes in either case, and there were none. Just to make sure,
I ran each driver again and got the same results. It sounds like
there are no known issues regarding this?
We have people looking into things on the DBMS side and I'm still
looking into things on my end, but so far none of us have found
anything. We'd like to continue using BEA's driver for the
support and the fact that we use Weblogic Server for all of our
online applications, but this new data might mean that I have to
switch drivers for this particular application.Thanks. No, there is no known issue, and if you put a packet sniffer
between the client and DBMS, you will probably not see any appreciable
difference in the content of the SQL sent be either driver. My suspicion is
that it involves the historical backward compatibility built in to the DBMS.
It must still handle several iterations of older applications, speaking obsolete
versions of the DBMS protocol, and expecting different DBMS behavior!
Our driver presents itself as a SQL7-level application, and may well be treated
differently than a newer one. This may include different query processing.
Because our driver is deprecated, it is unlikely that it will be changed in
future. We will certainly support you using the MS driver, and if you look
in the MS JDBC newsgroup, you'll see more answers from BEA folks than
from MS people!
Joe
>
>
Mike
The next test you should do, to isolate the issue, is to try another
JDBC driver.
MS provides a type-4 driver now, for free. If it is significantly faster,
it would be
interesting. However, it would still not isolate the problem, because
we still would
need to know what query plan is created by the DBMS, and why.
Joe Weinstein at BEA
PS: I can only tell you that our driver has not changed in it's semantic
function.
It essentially send SQL to the DBMS. It doesn't alter it.
Similar Messages
-
Licensing problems installing JDriver for MS SQL Server
I've been having problems for some time now creating a connection pool in WL 5.1 using the MS SQLServer4v70 JDriver. I am at wits end and haven't been able to find a solution or find anybody that could give me a solution. Below is a better description of the problem including exact error messages and configuration.
There's some simple problem here, but I'm not an
installation expert. Would you please post this to
the support.install group? If you don't get help
quickly from there, let me know.
JoeAt 09:54 AM 10/31/00 -0800, you wrote:
Here's the exact error message:
Tue Oct 31 09:52:09 PST 2000:<I> <WebLogicServer> IIOP subsystem enabled.
weblogic.common.LicenseNotFoundException: Could not find licensing file:
Your WebLogic license file, named either WebLogicLicense.xml or
WebLogicLicense.class must be located in a directory that is
in your CLASSPATH. By default, your license file is located in the
/license directory located in your WebLogic home directory
(the root directory of your WebLogic installation).
As of version 4.0 of WebLogic, a new XML-format license file has
replaced the older, compiled class format license file.
The WebLogic Server will recognize either format.
For additional information on WebLogic licenses or on setting your
classpath, see the i
stallation instructions in the WebLogic Server documentation, available at
http://e-docs.bea.com/
my weblogic class path looks like:
CLASSPATH Prefix c:\weblogic\mssqlserver4v70\classes
CLASSPATH
c:\weblogic\mssqlserver4v70\classes;c:\jdk1.3\lib\tools.jar;c:\jdk1.3\jre\li
b\rt.jar;c:\jdk1.3\jre\lib\i18n.jar;C:\weblogic\license;C:\weblogic\classes\
boot;C:\weblogic\cla
sses;C:\weblogic\lib\weblogicaux.jar;C:\weblogic\eval\cloudscape\lib\cloudsc
ape.jar
JAVA_HOME c:\jdk1.3
WEBLOGIC_LICENSEDIR C:\weblogic\license
WEBLOGIC_HOME C:\weblogic
system properties:
java.security.manager
java.security.policy==C:\weblogic\weblogic.policy
weblogic.system.home=C:\weblogic
java.compiler=symcjit
weblogic.class.path=C:\weblogic\license;C:\weblogic\classes;C:\weblogic\myse
rver\serverclasses;C:\weblogic\lib\weblogicaux.jar
INITIAL_HEAP 64 MB
MAX_HEAP 64 MB
SERVERCLASSPATH
c:\weblogic\mssqlserver4v70\classes;c:\jdk1.3\jre\lib\rt.jar;c:\jdk1.3\jre\l
ib\i18n.jar;C:\weblogic\classes\boot;C:\weblogic\eval\cloudscape\lib\cloudsc
ape.jar
Type "wlconfig -help" for program usage.
The license file is attached:
-Matt
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Tuesday, October 31, 2000 8:41 AM
To: Matthew Heaton
Subject: RE: Problems creating connection pool
At 04:35 PM 10/30/00 -0800, you wrote:
Still having problems with it not finding the licenseOk, what is the exact failure message? Does the server start fine?
Then it's finding the server license in the weblogiclicense.xml file.
Is it then failing to find the driver license? If so, show me your
editted xml license file.
Joe
Currently nothing related to the driver is in my classpath and
c:\weblogic\mssqlserver4v70\classes is in my weblogic classpath. I deleted
the license folder for the driver after moving the guts of it into the main
weblogic license file.
-Matt
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, October 30, 2000 3:46 PM
To: Matthew Heaton
Subject: Re: Problems creating connection pool
Hi Matt.
You did the right thing adding the driver to the weblogic.class.path.
That's where it should be, not in the java.class.path. The current
licensing issue is that the weblogic server has(had?) it's own copy of
WebLogicLicense.xml, containing the server licenses. The one from thedriver
is now in the path. It contains the driver license, but not the server
stuff. Edit the server one, adding the guts of the driver one, and
delete the driver xml license file from your path.
Joe
Matt Heaton wrote:
This is a problem that has been a roadblock for me for a while, I'm usingWL 5.1 and trying to create a connection pool with the MS SQL server 4v70
JDriver.
Here is the code to create the connection pool:
weblogic.jdbc.connectionPool.SQLPool=\
url=jdbc:weblogic:mssqlserver4:MATTHEWH1:1433,\
driver=weblogic.jdbc.mssqlserver4.Driver,\
initialCapacity=1,\
maxCapacity=2,\
capacityIncrement=1,\
props=user=AceUser;password=AceUser;server=MATTHEWH1
I've addedc:\weblogic\mssqlserver4v70\classes;c:\weblogic\mssqlserver4v70\license to
my class path, but I was getting a class not found exception when Weblogic
tried to make the connection pool. I then added
c:\weblogicmssqlserver4v70\classes to my Weblogic classpath and got the
following error:
weblogic.common.LicenseNotFoundException: Could not find licensing file:
Your WebLogic license file, named either WebLogicLicense.xml or
WebLogicLicense.class must be located in a directory that is
in your CLASSPATH. By default, your license file is located in
the
/license directory located in your WebLogic home directory
(the root directory of your WebLogic installation).
As of version 4.0 of WebLogic, a new XML-format license file has
replaced the older, compiled class format license file.
The WebLogic Server will recognize either format.
For additional information on WebLogic licenses or on settingyour
classpath, see the in
stallation instructions in the WebLogic Server documentation, available
at
http://e-docs.bea.com/
So I tried adding c:\weblogic\mssqlserver4v70\license to the weblogicclasspath and got yet a different error:
$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
Loaded License : C:/weblogic/license/WebLogicLicense.xml
However Unable to start because :
No License found for WebLogic
As well as the fact that: No License found for Tengah
As well as the fact that: No License found for WebLogic/JDBC
As well as the fact that: No License found for Tengah/JDBC
As well as the fact that: No License found for jdbcKona/T3
WebLogic Server terminated with an abnormal condition of 1
What do I do? I've tried everything I can think of, I was able to getthis to work the first time that I tried to do it but everytime I've tried
since then this happens.
-Matt--
PS: Folks: BEA WebLogic is in S.F. with both entry and advanced positions
for
people who want to work with Java and E-Commerce infrastructure products.
Send
resumes to [email protected]
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web Application Server
Java Developer's Journal Editor's Choice Award: Best Web Application
Server
Crossroads A-List Award: Rapid Application Development Tools for Java
Intelligent Enterprise RealWare: Best Application Using a Component
Architecture
http://www.bea.com/press/awards_weblogic.html
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web Application Server
Java Developer's Journal Editor's Choice Award: Best Web Application
Server
Crossroads A-List Award: Rapid Application Development Tools for Java
Intelligent Enterprise RealWare: Best Application Using a Component
Architecture
http://www.bea.com/press/awards_weblogic.html
Attachment Converted: "c:\eudora\attach\WebLogicLicense11.xml"
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web Application Server
Java Developer's Journal Editor's Choice Award: Best Web Application Server
Crossroads A-List Award: Rapid Application Development Tools for Java
Intelligent Enterprise RealWare: Best Application Using a Component Architecture
http://www.bea.com/press/awards_weblogic.htmlEric Ma wrote:
Joe:
Connection is a LOCAL variable declared in each method. DataSource is an instance
variable.That sounds fine... let me see your code (main block plus finally block). How long does this
take to reproduce? Show me your pool definition.
thanks,
Joe
>
>
Eric
Joseph Weinstein <[email protected]> wrote:
Eric Ma wrote:
I was given the unfortunate task :-) of getting data out of M$FT SQL6.5. I set
up a JDBC connection pool using jDriver in mssqlserver4v65.jar, andcreated a
JDBCDataSource for the pool. I am using a stateless session bean +JDBC (with
the DAO pattern) to get data. In the DAO class I have an instancevariable for
the datasource, which I look up in the constructor. In the DAO's businessmethod
I RELIGIOUSLY call datasource.getConnect() first, and ALWAYS call connection.close()
in the finally block. Now the initial requests are fine, but aftera while I
got a weblogic.common.ResourceException telling me there were no moreconnection
available in the pool. Is this a jDriver bug? I never run into sucha problem
with an Oracle connection pool using the thin driver.
Any insight will be greatly appreciated.
Eric MaHi. Is the connection object an instance variable? That would be a problem.
The connection object has to be a method variable to be safe from multithreading
issues.
Joe -
Problem using production version of SQL Server 2005 JDBC drivers
A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
Regards,
Sabrina
at ourpackage.OurMDB.onMessage(OurMDB.java:184)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)
... 11 more
Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
at ourpackage.OurMDB.onMessage(OurMDB.java:184)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
at ourpackage.OurMDB.onMessage(OurMDB.java:184)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
... 12 moreSabrinaL wrote:
A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
Regards,
SabrinaHi. Have you done all the XA-related install for the new MS driver? (put the XA
dll in the DBMS environment etc)? Is your DBMS on a 32-bit machine or 64-bit machine?
Does the driver present a dll for each of those? You can also get good JDBC help
from MS via their microsoft.public.sqlserver.jdbcdriver newsgroup.
Joe Weinstein at BEA
>
at ourpackage.OurMDB.onMessage(OurMDB.java:184)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)
... 11 more
Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
at ourpackage.OurMDB.onMessage(OurMDB.java:184)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
at ourpackage.OurMDB.onMessage(OurMDB.java:184)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
... 12 more -
Problem using DG4ODBC with named SQL Server instance
I am running DG4ODBC on a 64 bit LINUX machine with the Microsoft SQL Server driver installed. I have successfully tested this with a SQL Server instance that was not named (GENERALI_DSN).The named instance gives the following when trying to query:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[unixODBC][Microsoft][SQL Server Native Client 11.0]Login timeout expired {HYT00}[unixODBC][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. {08001,NativeErr = -1}[unixODBC][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. {08001,NativeErr = -1}
ORA-02063: preceding 2 lines from DEVMISC
odbc.ini
[GENERALI_DSN]
Driver = SQL Server Native Client 11.0
Server = CLTDMJCWBYZ.eu.scor.local
User = everest
Password = everest
Database = Everest_Generali
[DEVMISC_DSN]
Driver = SQL Server Native Client 11.0
Server = [USVCLTDEVSQL02\DEVMISC]
User = link_user
Password = password1
Database = DBA
initDG4ODBC2.ora
# HS init parameters
HS_FDS_CONNECT_INFO = DEVMISC_DSN
HS_FDS_TRACE_LEVEL = DEBUG
HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so
# ODBC specific environment variables
set ODBCINI=/home/oracle/.odbc.ini
listener.ora
SID_LIST_LISTENER_GW =
(SID_LIST =
(SID_DESC =
(SID_NAME=DG4ODBC)
(ORACLE_HOME=/home/oracle/product/11.2.0)
(ENV=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micro
soft/sqlncli/lib)
(PROGRAM=dg4odbc)
(SID_DESC =
(SID_NAME=DG4ODBC2)
(ORACLE_HOME=/home/oracle/product/11.2.0)
(ENVS=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micr
osoft/sqlncli/lib)
(PROGRAM=dg4odbc)
LISTENER_GW =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = usvcltprdoragw)(PORT = 1521))
tnsnames.ora
DG4ODBC =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
(CONNECT_DATA=(SID=DG4ODBC))
(HS=OK)
DG4ODBC2 =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
(CONNECT_DATA=(SID=DG4ODBC2))
(HS=OK)
I can't figure out why the named instance does not work but the other one does. Any help would be greatly appreciated!Did you check with the ODBC test utility isql (it is installed by default when you install the unixODBC Driver manager) if your ODBC driver can connect at all to that named instance? I have some doubts that it will work either as there was a blog commented by a MS engineer:
Introducing the new Microsoft ODBC Drivers for SQL Server - Microsoft SQLNCli team blog - Site Home - MSDN Blogs
who states that named instance connections are not supported using that driver.
- Klaus -
Problem using JDBC and MS SQL Server
I got a problem trying to acces a database on my SQL Server. I created the table and my connection seems ok, but when i try to get some data from a table, this happens (see below).
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'players'.
at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6879)
at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7036)
at sun.jdbc.odbc.JdbcOdbc.SQLExecDirect(JdbcOdbc.java:3065)
at sun.jdbc.odbc.JdbcOdbcStatement.execute (JdbcOdbcStatement.java:338)
at sun.jdbc.odbc.JdbcOdbcStatement.executeQuery(JdbcOdbcStatement.java:253)
at Team.<init>(Team.java:18)
at Simulator.main(Simulator.java:5)
here's the code that i used to access the db with:
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection conn = DriverManager.getConnection
("jdbc:odbc:BRAIN2WINXPPJH","sm","sm");
Statement stm = conn.createStatement();
String query = "Select * from players where teamnr = " + nr +
" order by squadnr";
ResultSet rs = stm.executeQuery(query);
any help is more than welcome
tnx
JoIf all the tables are in the same database, you can use
Connection.setCatalog("db-name")
to change the current database. But the suggestion to include the database name in the SQL statement is safer, because you do not need to worry about changing the database at the right point.
Thomas -
Performance problem using OBJECT tag
I have a performance problem using the java plugin and was wondering if anyone else was has seen the same thing. I have a rather complex applet that interacts with java script in a web page using the LiveConnect API. The applet both calls javascript in the page and is called by java script.
Im using IE6 with the java plugin that ships with the 1.4.2_06 JVM. I have noticed that if I deploy the applet using the OBJECT tags, the application seems the trash everytime I call a java method on the applet from javascript. When I deplot the same applet using the APPLET tag the perfomance is much better. I would like to use the OBJECT tag because it applet bahaves better and I have more control over the caching.
This problem seems to be on the boundaries of IE6, JScript, the JVM and my Applet (and I suppose any could be the real culprit). My application is IE5+ specific so I can not test the applet in isolation from the surround HTML/JavaScript (for example in another browser).
Does anyone have any idea?
thanks in advance.
dennis.I have a performance problem using the java plugin and was wondering if anyone else was has seen the same thing. I have a rather complex applet that interacts with java script in a web page using the LiveConnect API. The applet both calls javascript in the page and is called by java script.
Im using IE6 with the java plugin that ships with the 1.4.2_06 JVM. I have noticed that if I deploy the applet using the OBJECT tags, the application seems the trash everytime I call a java method on the applet from javascript. When I deplot the same applet using the APPLET tag the perfomance is much better. I would like to use the OBJECT tag because it applet bahaves better and I have more control over the caching.
This problem seems to be on the boundaries of IE6, JScript, the JVM and my Applet (and I suppose any could be the real culprit). My application is IE5+ specific so I can not test the applet in isolation from the surround HTML/JavaScript (for example in another browser).
Does anyone have any idea?
thanks in advance.
dennis. -
BEA WebLogic jDriver for Microsoft SQL Server
Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future product development direction.
Thank you for your attention regarding this matter.Actually, this driver is already documented as deprecated. We intended to remove it from a future
release (most likely, the release after WLS 8.1).
The plan is to ship another driver out-of-the-box. We have been evaluating various drivers
for features, quality, and performance. We are pushing very hard to have this replacement
driver available in 8.1SP01, which will also ship with the WLI/Portal/WLW GA (announced to
ship in July). The most likely candidate is already in testing both at the WLS level and
with the layered products. It also did quite well in an internal performance comparison.
"Joseph Weinstein" <[email protected]_this> wrote in message news:[email protected]_this...
>
>
Peter Foskaris wrote:
Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though
BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future
product development direction.
>>
Thank you for your attention regarding this matter.Hi. We intend to deprecate it. We may or may not fix bugs that are found in it in future, and will likely
not do any more development on it, such as implementing any JDBC 2.0 methods. It will be in
our next major release (8), but may not be in future ones.
Joe Weinstein at BEA -
SQL Server 2005 performance decreases with DB size while SQL Server 2012 is fine
Hi,
We have a C# windows service running that polls some files and inserts/updates some fields in database.
The service was tested on a local dev machine with SQL Server 2012 running and performance was quite decent with any number of records. Later on the service was moved to a test stage environment where SQL Server 2005 is installed. At that point database
was still empty and service was running just fine but later on, after some 500k records were written, performance problems came to light. After some more tests we've founds out that, basically, database operation performance in SQL Server 2005 decreases with
a direct correlation with the database size. Here are some testing results:
Run#
1
2
3
4
5
DB size (records)
520k
620k
720k
820k
920k
SQL Server 2005
TotalRunTime
25:25.1
32:25.4
38:27.3
42:50.5
43:51.8
Get1
00:18.3
00:18.9
00:20.1
00:20.1
00:19.3
Get2
01:13.4
01:17.9
01:21.0
01:21.2
01:17.5
Get3
01:19.5
01:24.6
01:28.4
01:29.3
01:24.8
Count1
00:19.9
00:18.7
00:17.9
00:18.7
00:19.1
Count2
00:44.5
00:45.7
00:45.9
00:47.0
00:46.0
Count3
00:21.7
00:21.7
00:21.7
00:22.3
00:22.3
Count4
00:23.6
00:23.9
00:23.9
00:24.9
00:24.5
Process1
03:10.6
03:15.4
03:14.7
03:21.5
03:19.6
Process2
17:08.7
23:35.7
28:53.8
32:58.3
34:46.9
Count5
00:02.3
00:02.3
00:02.3
00:02.3
00:02.1
Count6
00:01.6
00:01.6
00:01.6
00:01.7
00:01.7
Count7
00:01.9
00:01.9
00:01.7
00:02.0
00:02.0
Process3
00:02.0
00:01.8
00:01.8
00:01.8
00:01.8
SQL Server 2012
TotalRunTime
12:51.6
13:38.7
13:20.4
13:38.0
12:38.8
Get1
00:21.6
00:21.7
00:20.7
00:22.7
00:21.4
Get2
01:38.3
01:37.2
01:31.6
01:39.2
01:37.3
Get3
01:41.7
01:42.1
01:35.9
01:44.5
01:41.7
Count1
00:20.3
00:19.9
00:19.9
00:21.5
00:17.3
Count2
01:04.5
01:04.8
01:05.3
01:10.0
01:01.0
Count3
00:24.5
00:24.1
00:23.7
00:26.0
00:21.7
Count4
00:26.3
00:24.6
00:25.1
00:27.5
00:23.7
Process1
03:52.3
03:57.7
03:59.4
04:21.2
03:41.4
Process2
03:05.4
03:06.2
02:53.2
03:10.3
03:06.5
Count5
00:02.8
00:02.7
00:02.6
00:02.8
00:02.7
Count6
00:02.3
00:03.0
00:02.8
00:03.4
00:02.4
Count7
00:02.5
00:02.9
00:02.8
00:03.4
00:02.5
Process3
00:21.7
00:21.0
00:20.4
00:22.8
00:21.5
One more thing is that it's not Process2 table that constantly grows in size but is Process1 table, that gets almost 100k records each run.
After that SQL Server 2005 has also been installed on a dev machine just to test things and we got exactly the same results. Both SQL Server 2005 and 2012 instances are installed using default settings with no changes at all. The same goes for databases
created for the service.
So the question is - why are there such huge differences between performance of SQL Server 2005 and 2012? Maybe there are some settings that are set by default in SQL Server 2012 database that need to be set manually in 2005?
What else can I try to test? The main problem is that production SQL Server will be updated god-knows-when and we can't just wait for that.
Any suggestions/advices are more than welcome....One more thing is that it's not Process2 table that constantly grows in size but is
Process1 table, that gets almost 100k records each run....
Hi,
It is not clear to me what is that you are doing, but now we have a better understanding on ONE of your tables an it is obviously you will get worse result as the data become bigger. Actually your table look like a automatic build table by ORM like Entity
Framework, and it's DDL probably do not much your needs. For example if your select query is using a filter on the other column that [setID] then you have no index and the server probably have to scan the entire table in order to find the records that you
need.
Forum is a suitable place to seek advice about a specific system (as I mentioned before we are not familiar with your system), and it is more suitable for general questions. For example the fact that you have no index except the index on the column [setID]
can indicate a problem. Ultimately to optimize the system will need to investigate it more thoroughly (as it is no longer appropriate forum ... but we're not there yet). Another point is that now we can see that you are using [timestamp] column, an this
implies that your are using this column as a filter for selecting the data. If so, then maybe a better DDL will be to use clustered index on this column and if needed a nonclustered index on the [setID] if it is needed at all...
what is obviously is that next is to check if this DDL fit
your specific needs (as i mentioned before).
Next step is to understand what action do you do with this table. (1) what is your query which become slowly in a bigger data set. (2) Are you using ORM (object relational mapping, like Entity Framework
code first), and if so then which one.
[Personal Site] [Blog] [Facebook] -
I am using Reporting Service Integration mode with SharePoint. SSRS is installed on separated machine of SharePoint stacks in Integration Mode. Everything was working properly and I could create/edit/modify RDL reports(parameters, Datasource, Subscription)
inside SharePoint and Document Libraries.
But after installing SQL Server 2012 Service Pack 2, on opening RDL reports inside SharePoint I receive this error message.
The permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation
I should mention that SSRS is installed in the SharePoint integration Mode and there is no SSRS management console.Hi Hedayat-Abedijoo,
According to your description, you are using Reporting Services in SharePoint Integrated mode, and everything worked fine before you install SQL Server 2012 Service Pack 2. After the package is installed, when you open RDL reports, the error occurred: The
permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation.
According to my search, there may be two reasons for the problem:
This is caused when the application pool account that runs the SharePoint Web application you are on in IIS and the application pool account that SharePoint believes is running the site differ. This happens if the application pool account is changed directly
in IIS instead of through SharePoint (using the approved method).
This error can be caused when Kerberos authentication has been set up correctly and delegation in a double hop scenario will succeed, but Reporting Services integration has been set up for Trusted Account rather than Windows Authentication. This causes
SharePoint to continue to impersonate the logged-on user when contacting Reporting Services; when Reporting Services compares the application pool account to the user account making the request, they are not equal.
In this case, we can solve the problem by changing the application pool account in IIS back to the previous account and set AuthenticationTypes to RSWindowsNTLM only. For detail information, please refer to 8.3 “The permissions granted to user 'Domain\User'
are insufficient for performing this operation” in the document:http://msdn.microsoft.com/en-us/library/ee384252(SQL.100).aspx
If you have any questions, please feel free to let me know.
Thanks,
Wendy Fu -
JDriver for microsoft sql server 2000
"Hi, Currently, I am using your JDriver for microsoft SQL server 2000 for evaluation purposes and confront the following problem: (1) using utils.dbping C:\student\work>java utils.dbping mssqlserver4 sa "" ywu**** Success!!! ****You can connect to the database in your app using: java.util.Properties props = new java.util.Properties(); props.put("user", "sa"); props.put("password", ""); java.sql.Driver d = (java.sql.Driver)Class.forName("weblogic.jdbc.mssqlserver.Driver").newInstance(); java.sql.Connection conn = d.connect("jdbc:weblogic:mssqlserver4:ywu", props) // This mode is superior, especially in serverside classes because // it avoids DriverManager calls are class synchronized, and will // bottleneck any other JDBC in the server, even already-running // connections, because all JDBC drivers use DriverManager.println() // to log info and exceptions, and that call is also class synchronized. // For repeated connecting, a single driver instance can be re-used.**** or **** Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance(); java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4:ywu", "sa", "");**** or **** java.util.Properties props = new java.util.Properties(); props.put("user", "sa"); props.put("password", ""); props.put("server", "ywu"); Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance(); java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4", props);It seems that everything is fine, but(2) set up connection pool to MS SQL server, the weblogic server prints out error messages during the server goes up:<Jun 18, 2001 5:51:22 PM EDT> <Error> <JDBC Connection Pool> <Cannot startup connection pool "newSQLconn" weblogic.common.ResourceException:Could not create pool connection. The DBMS driver exception was:Driver
Hi,
I was having the same problem and to solve it u have to point your classpath to
mssqlserver4v65.jar in the lib directory of your wl installation, in my case i
did:
set classpath=%classpath%;%WL_HOME%\lib\mssqlserver4v65.jar
I hope it helps.
Yuanqing Wu <[email protected]> wrote:
"Hi, Currently, I am using your JDriver for microsoft SQL server 2000
for evaluation purposes and confront the following problem: (1)
using utils.dbping C:\student\work>java utils.dbping
mssqlserver4 sa "" ywu**** Success!!! ****You can connect to the database
in your app using: java.util.Properties props = new java.util.Properties();
props.put("user", "sa"); props.put("password", ""); java.sql.Driver
d = (java.sql.Driver)Class.forName("weblogic.jdbc.mssqlserver.Driver").newInstance();
java.sql.Connection conn = d.connect("jdbc:weblogic:mssqlserver4:ywu",
props) // This mode is superior, especially in serverside classes because
// it avoids DriverManager calls are class synchronized, and will
// bottleneck any other JDBC in the server, even already-running //
connections, because all JDBC drivers use DriverManager.println() //
to log info and exceptions, and that call is also class synchronized.
// For repeated connecting, a single driver instance can be re-used.****
or
**** Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance();
java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4:ywu",
"sa", "");**** or **** java.util.Properties props = new java.util.Properties();
props.put("user", "sa"); props.put("password", ""); props.put("server",
"ywu"); Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance();
java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4",
props);It
seems that everything is fine, but(2) set up connection pool to MS SQL
server, the weblogic server prints out error messages during the server
goes up:<Jun 18, 2001 5:51:22 PM EDT> <Error> <JDBC Connection Pool>
<Cannot startup connection pool "newSQLconn" weblogic.common.ResourceException:Could
not create pool connection. The DBMS driver exception was:Driver -
Error when using Oracle Migration WorkBench (Sql Server 2k to Oracle 8i)
I'm trying to migrate a Sql Server 2k database to an Oracle 8i schema using OMWB. After using BCP to collect metadata information on the source database, I tried to capture the source data model and got a "Capture aborted" message on the progress screen (even though then it appears a dialog window reporting "0 errors and 0 warnings", funny!). Down there is the error log OMWB generated. After reading some posts, I changed some columns of the OMWB dictionary that holds the source database name, but still got the same error. If someone can enlighten me on this toppic, I'd greatly appreciated it.
Here's the error log of OMWB:
** Oracle Migration Workbench
** Production
** ( Build 20050629 )
** OMWB_HOME: D:\Datos\Download\Oracle\Oracle Migration Workbench\omwb
** user language: es
** user region: null
** user timezone:
** file encoding: Cp1252
** java version: 1.4.2_04
** java vendor: Sun Microsystems Inc.
** o.s. arch: x86
** o.s. name: Windows 2000
** o.s. version: 5.0
** Classpath:
..\lib\boot.jar
** Started : Fri Feb 23 17:18:48 GMT-03:00 2007
** Workbench Repository : Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
Repository Connection URL: jdbc:oracle:thin:@ServerCms:1521:sigcewbc
** The following plugins are installed:
** Microsoft Access 2.0/95/97/2000/2002/2003 Plugin, Production Release 10.1.0.4.0
** Microsoft SQLServer 2000 Plugin, Production Release 10.1.0.4.0
** Microsoft SQLServer 6.5 Plugin, Production Release 10.1.0.4.0
** Microsoft SQLServer 7.0 Plugin, Production Release 10.1.0.4.0
** Active Plugin : SQLServer2K
EXCEPTION :SQLServer2KDisconnSourceModelLoad.loadSourceModel(): oracle.mtg.migration.MigrationStopException: java.lang.IndexOutOfBoundsException: Index: 15, Size: 15
** Shutdown : Fri Feb 23 18:00:50 GMT-03:00 2007Duplicate thread
Error when using Oracle Migration WorkBench (Sql Server 2k to Oracle 8i) -
À PROBLEM IN THE INSTALLATION OF SQL SERVER
I HAVE À PROBLEM IN THE INSTALLATION OF SQL SERVER ,I HAVE WINDOWS 8 64 BITS LENOVO ,I TRIED MANY VERSIONS, BUT IT DOESN'T WORK YET :(
PLEASE HELP ME !I HAVE À PROBLEM IN THE INSTALLATION OF SQL SERVER ,I HAVE WINDOWS 8 64 BITS LENOVO ,I TRIED MANY VERSIONS, BUT IT DOESN'T WORK YET :(
PLEASE HELP ME !
Without the exact error message wwe will just hit arrow in the bush.Please post summary.txt which was generated due to failed installation.Below link will help you locate it
http://technet.microsoft.com/en-us/library/ms143702.aspx
Below link will give useful info about how to proceed with installing SQL server on win 8
Considerations before installing SQL server on win 8
Hardware and software requirement for installing SQL server 2012
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
Using Ranking on MS SQL Server 2005
Hello,
We are on BOXI3.1 base version and have a universe on top of MS SQL Server 2005.
My question is regarding use of rank functions. BO guides state that
You can perform a database ranking only if your database supports
it. If this is not the case, the Add a database ranking button is disabled on
the Query Panel toolbar. Databases that support ranking are Oracle, DB2,
Terradata and Redbrick.
So SQL Server is not in the list. However the add database ranking button is enabled on
my report panel. If i add a ranking the query runs for a long time and times-out.
Is there any universe parameter i need to enable to use ranking? Has any-one mangaged to
use ranking functionality with SQL Server 2005.
Thanks in advance.Hi Bashir Awan,
When we create this Object (using your example) at Universe level is the ranking hardcoded ?
My questions is, say i have Product object (with values A, B, C, D, E), and sales aggregated (10, 20, 30, 40, 50, 60, 70, 80, 90, 100)
Say the table is as follows
Product; sales
A; 10
A; 70*
B; 50
B; 20*
C; 30
C; 60*
D; 40
D; 90
E; 80
E; 100
Note: * represents Oversees sales outside US
Case 1: Now when we rank whole data to select top 3 we should get (E, D, C in Desc order)
Case 2: Now if I apply prompt on Country of sales as US will I get (E, B, D) or is it still (E, D, C as earlier).
Case 3: Similarly if I apply prompt on Product (no prompt on Country) in the filter pane and select (A, D, E) will my results show (E, D, A) or (E, D) as the value of A may be restricted due to ranking formula based on sales at Universe level.
I am sorry I may be asking a very basic question. Thanks
Sudhir. -
Can we use different Databases (Oracle & SQL Server) in one report?
Post Author: venki5star
CA Forum: .NET
Hi there.
Can we use different databases (Oracle & SQL Server) in a same report?
If possible how?
Another question,
Can we change the Provider Name at runtime of the given report. If so the above question is useless...
Thanks in Advance.I tried this using Oracle Provider for OLEDB (the one that supplied by Oracle Client) and Crystal Reports 9. you can drag the column into designer but the image does not appear in preview.
I guess it's because CR does not recognized it as image, and there are no information that the blob data is an image at all. -
How To Use Reporting Services On SQL Server 2000 ?
Hi all .
Today , I has a issue .
Normal , if the customer use SQl Server 2005 , it is no proplem , so if use SQL Server 2000 , Now , I want to use Reporting services on SQL Server 2000 , but , I am searching on Internet , so I know , if I want to use SQL 2000 reporting server , I must have license of SQL server 2000 .
is Every body idea for this issue ? .
Please help me .
Thanks alot .Ok ,anyway thanks alot ,.
Maybe you are looking for
-
Need help with Boot Camp dual booting
I'm trying to install windows 7 on a separate partition but after the mac book pro restarts to start the installation it says windows can't be installed because it needs to be NTFS format but the mac partition is Mac OS Extended(journaled) but gives
-
APP ERROR 523 Model Pearl 9105
Hi Team, Since yesterday my phone is showing APP Error 523, and it showing reset, if i click reset also it restarting but again it is showing the same error. Could you please help on this and resolve this issue at earliest. Regards, prashanth
-
Cannot get my "attach" to work on my email program. I press it but it is not allowing to open window to browsw files that I want to attach to email
-
Epson 635 printer won't install via wireless with Mountain Lion
I am helping a friend with the upgrade to Mountain Lion and She has a giant desktop which I think is a MacPro but I'm not sure. Anyway everything works fine except now her Epson 635 printer won't see the wireless network. To me this seems like a rout
-
60GB 5g iPod Audio Problems on VIDEOS only
I've been looking all over the web for a solution but haven't found anything acceptable. I'm using the latest version of iTunes, G5 iMac, 1 GIG RAM, System 10.4.5. While my Music sounds great, my videos do not. Volume on Videos is adequate but not lo