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

Similar Messages

  • (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.

  • 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
    Jo

    If 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

  • 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 more

    SabrinaL 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

  • Is it possible to use Jdeveloper with Other Sql Server using JDBC-ODBC bri

    I have been able to successfully establish connection with Sql server Using JDBC-ODBC bridge, but when i run the application and perform some operations such as insert the following errors occur:
    (oracle.jbo.SQLStmtException) JBO-27122: SQL error during statement preparation. Statement: SELECT ItmUnit.ORG_CODE, ItmUnit.UNIT_CODE, ItmUnit.UNIT_NAME, ItmUnit.ADDRESS1, ItmUnit.ADDRESS2, ItmUnit.ADDRESS3, ItmUnit.CITY_CODE, ItmUnit.USER_ID, ItmUnit.TIME_STAMP FROM ITM_UNIT ItmUnit
    ----- LEVEL 1: DETAIL 0 -----
    (java.sql.SQLException) [DataDirect][ODBC Sybase Wire Protocol driver]Sybase does not allow more than one active statement when retrieving results without a cursor
    (oracle.jbo.DMLException) JBO-26041: Failed to post data to database during "Insert": SQL Statement "INSERT INTO IMMS.HRM_UNIT(UNIT_CODE,UNIT_NAME) VALUES (?,?)".
    ----- LEVEL 1: DETAIL 0 -----
    (java.sql.SQLException) [Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt
    (oracle.jbo.AttrValException) JBO-27014: Attribute DeptCode in HrmUnitDept is required
    (oracle.jbo.SQLStmtException) JBO-27122: SQL error during statement preparation. Statement: SELECT HrmUnit.UNIT_CODE, HrmUnit.UNIT_NAME FROM IMMS.HRM_UNIT HrmUnit
    ----- LEVEL 1: DETAIL 0 -----
    (java.sql.SQLException) [Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt

    Yes, you can do that. For testing purposes you can also create simple files (with mkfile) and add these to ASM. That way you could also experiment with deleting files and see what happens in ASM
    Bjoern

  • Using Unicode with MS-SQL-Server 2000

    Hello,
    i want to migrate my coldfusion application to support
    unicode. for that i read some articles here in the knowledge bas e
    and on the web. So i actually tested with:
    * correct use of cfcontent,cfprocessingdirective
    * storing source-files with UTF8 (BOM)
    * activating Unicode-handling for strings in
    datasource-settings of coldfusion admin
    * using nvarchar instead of varchar on mssql-server
    my firsts test displaying diffrent characters of different
    languages (chinese, japanese, arabic) look good. Tests storing and
    selecting example strings in that languages also look good.
    but now i read, that mssql stores unicode data with the UCS-2
    implementation and cannot handle UTF-8 directly. but my
    coldfusion-application will be converted to UTF-8.
    now my question: Do i have to do special handling storing and
    selecting the application data or does this the mssql jdbc driver
    for me. What about characters in some languages which use 3 Bytes
    in UTF8. How are they handled when MS-SQL-Server 2000 uses UCS-2
    (max 2 Bytes) instead?
    Many regards for your answers
    McD

    mcd wrote:
    > now my question: Do i have to do special handling
    storing and selecting the
    > application data or does this the mssql jdbc driver for
    me. What about
    > characters in some languages which use 3 Bytes in UTF8.
    How are they handled
    > when MS-SQL-Server 2000 uses UCS-2 (max 2 Bytes)
    instead?
    no need to worry, the db driver will handle that for you.
    just make sure your
    encoding is the same end-to-end.
    also a potential gotcha has just been exposed in unicode
    handling for sql server
    related to cfqueryparam under loads, you need to convert
    everything to "N"
    datatypes to avoid this. see jochem's blog:
    http://jochem.vandieten.net/2008/03/22/ms-sql-server-and-the-coldfusion-string-format-sett ing/

  • JSP using BC4J with MS SQL Server

    I use JDevelop to develop my JSP apps with BC4J. When I Run a JSP app, the error happened.
    The error message is [Microsoft][SQLServer 2000 Driver for JDBC]Can't start a cloned connection while in manual transaction mode.
    Who can tell me what the error message means? Or What error might happened to my code?
    What parameter I should setup? Or What code I should change?

    There is a "how to" that addresses this issue
    with SQL*Server:
    http://otn.oracle.com/products/jdev/howtos/bc4j/bc_psqlserverwalkthrough.html
    You need to qualify your jdbc URL: (this is from the howto)
    On the Connection page, enter the Java class name and the URL.
    Java class name: com.microsoft.jdbc.sqlserver.SQLServerDriver
    URL: jdbc:microsoft:sqlserver://<db-host>:1433;SelectMethod=cursor
    Note: There's a semicolon before SelectMethod=cursor.
    Note on Select Method: From the MS SQL Server documentation: SelectMethod={cursor | direct} determines whether or not Microsoft SQL Server "server cursors" are used for SQL queries. Setting SelectMethod to direct allows SQL statements to be executed without incurring server-side overhead for managing a database cursor over the SQL statement. Direct mode is the most efficient for executing Select statements; however, applications are limited to a single active statement while executing inside a transaction. If multiple result sets are required from a single query execution, then the application must set SelectMethod to direct.
    regards, Karl

  • Data modeler cannot connect to non-default sql server instance

    I've just started using DM, it installed and loaded fine, I got the jdbc drivers v2.0 from MS so that I can reverse engineer a couple of SQL-Server 2005 DB's.
    All worked just fine until I tried to connect to a machine with a named-sql-server instance.
    Normal way of doing this for sql-server is to add instance name to end of hostname in the hostname field, like this: "server10\inst01"
    but this gives me a cannot-connect-to-server10 error.
    I copied database over to a different server that has just a default sql-server instance and it worked fine. (both sql-server2005 and 2000!)
    I also tried the older 1.2 jdbc driver from MS against the sql-server 2005 named instance, no luck!
    I tried putting the instance name in front of the port number, that didn't work either.
    Am I just doing something wrong? or does DM need a special way of specifying the instance name on the sql-server host?

    Hello,
    you don't need instance name in order to connect. It's only host and port - probably named instance is not listening on default port. It'll be unfortunate if dynamic port assignment is used - but probably that won't be the case.
    I hope someone can tell you the port number.
    Philip

  • Issues using BitLocker in Windows 8 Emedded with 2012 SQL Server Express

    I was told that this forum may be able to help me with my issues (see original thread here:
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/8c81fde1-e91b-46eb-8d2f-b79426805ddd/using-sql-server-2012-express-with-bitocker?forum=sqlexpress).
    Background:
    To summarize, I have an OS that is partitioned into two volumes: C and D.
    C drive contains the running software, SQL Server install, and the OS.
    D drive is the encrypted partition via BitLocker. The SQL Server files are stored here (logs, backup, and mdf).
    Problem:
    The software cannot connect to the database stored on the encrypted D volume when BitLocker is turned on. The user account that I use to enable BitLocker is the same SQL Server Service account and has is also part of the Local Admin Group. As soon as I disable
    BitLocker, the software works fine and the database connection succeeds. I am currently using the SQL System Admin account to login (SA) and BitLocker is being used with a TPM.
    The error I am experiencing when connecting through the software is 'login
    failed for user sa'.
    Thank you for the suggestions/help.

    Hi HMLunger,
    Did you install the SQL Server instance successfully? If not, please help to post the summary and detail logs for analysis. By default, the logs can be found in: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
    However, if you fail to start SQL Server Express service after successfully installing SQL Server,
    you might have to change the paths of the files by running the following scripts from the command prompt. For more details, please review this similar
    thread.
    NET START MSSQL$SQLEXPRESS /f /T3608
    SQLCMD -S .\SQLEXPRESS
    ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
    ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
    go
    exit;
    ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
    ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
    NET STOP MSSQL$SQLEXPRESS
    In addition, you can follow the steps in this KB article to uninstall SQL Server.
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • Portal 4.0 with MS SQL Server 2000 using CLOBs

    Hello,
    I'm driving Portal 4.0 with MS SQL Server 2000. I have encountered serious
    problems when trying to persist events (e.g. RuleEvent) to database. In my
    application-config.xml file I have JdbcHelper attributes
    ShouldUseClobsForReads & -Writes set to 'false' as they should be or
    mssqlserver4v70 driver.
    It seems that when it is time to write the event to database, Portal4.0
    can't find JdbcHelper MBean configuration values and therefore it uses
    default values (=true) for both attributes.
    Otherwise reading and writing works fine with MS SQL Server 2000 (at least
    DATA_SYNC_ITEMs).
    Any help appreciated.
    Regards,
    JR
    P.S.
    Here are some excerpts from the console output:
    [BufferManager$PersistenceRequest.execute():247]
    PersistenceRequest::execute -> write to database
    [AbstractDatabasePersister.persist():135] Persister::persist -> write the
    events. size=2
    *** com.bea.p13n.util.jdbc.JdbcHelper.getInstance() @ JdbcHelper.java:122
    [JdbcHelper.getInstance():139] No instance found for
    sun.misc.Launcher$AppClassLoader@71732b
    [JdbcHelper.<init>():111] Unable to find JdbcHelper Configuration ...using
    defaults: java.lang.IllegalStateException: Not in application context
    at
    com.bea.p13n.management.ApplicationHelper.getApplicationName(ApplicationHelp
    er.java:119)
    at
    com.bea.p13n.management.ApplicationHelper.getApplicationConfigurationMBean(A
    pplicationHelper.java:440)
    at
    com.bea.p13n.management.ApplicationHelper.getServiceConfigurationMBean(Appli
    cationHelper.java:318)
    at com.bea.p13n.util.jdbc.JdbcHelper.<init>(JdbcHelper.java:102)
    at
    com.bea.p13n.util.jdbc.JdbcHelper.getInstance(JdbcHelper.java:141)
    at
    com.bea.p13n.util.jdbc.JdbcHelper.getConnection(JdbcHelper.java:265)
    at
    com.bea.p13n.tracking.internal.persistence.AbstractDatabasePersister.getConn
    ection(AbstractDatabasePersister.java:202)
    at
    com.bea.p13n.tracking.internal.persistence.AbstractDatabasePersister.persist
    (AbstractDatabasePersister.java:140)
    at
    com.bea.p13n.tracking.internal.persistence.BufferManager$PersistenceRequest.
    execute(BufferManager.java:250)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    *** com.bea.p13n.util.jdbc.JdbcHelper.getInstance() @ JdbcHelper.java:122
    [JdbcHelper.getInstance():131] Got instance for
    sun.misc.Launcher$AppClassLoader@71732b
    [JdbcHelper._setClob():412] ######## JdbcHelper: String length = 496
    [JdbcHelper._setClob():420] ######## JdbcHelper: setting CLOB String with
    setCharacterStream()
    <7.1.2002 14:27:41 GMT+02:00> <Error> <Tracking> <Error persisting event to
    database. java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is not implemented
    at
    weblogic.jdbc.rmi.SerialPreparedStatement.setCharacterStream(SerialPreparedS
    tatement.java:428)
    at com.bea.p13n.util.jdbc.JdbcHelper._setClob(JdbcHelper.java:424)
    at com.bea.p13n.util.jdbc.JdbcHelper.setClob(JdbcHelper.java:404)
    at
    com.bea.p13n.tracking.internal.persistence.BehaviorTrackingPersister.setPrep
    aredStatementData(BehaviorTrackingPersister.java:93)
    at
    com.bea.p13n.tracking.internal.persistence.AbstractDatabasePersister.persist
    (AbstractDatabasePersister.java:157)
    at
    com.bea.p13n.tracking.internal.persistence.BufferManager$PersistenceRequest.
    execute(BufferManager.java:250)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    Hi,
    I would suggest better to have a backup of existing database remove your existing SQL server. Install the  one given by SAP. And restore your previous databases.
    --Ragu

  • Problems configuring Platform Domain with MS Sql Server

    Hi,
    We are having problems configuring a Platform Domain with MS Sql Server 2000.
    We are using Weblogic version 7.0.0.2. These are the steps we followed
    1.We manually created a database called TestDB and created a user account called
    "system", pwd ==>> "weblogic" in SQL server and assigned him as the DB owner for
    the TestDB created.
    2. Changed dbsettings_properties files (Commented pointbase entries and uncommented
    SQL Server entries. I gave the connection parameter as connection=jdbc:weblogic:mssqlserver4:localhost:1433
    in this file.
    3. Modified Config.xml and changed properties for DataSyncPool, WLIPool, CommercePool,WLIPool
    and modified the RDBMS realm properties to point to the database.
    4. ran the create_db script and it seemed to have run fine looking at the log
    file.
    5. I then tried to start the BEA Server instance and I get the following error.
    I am also attaching the config.xml file for reference.
    Appreciate any help/suggestions. Thanks in Advance.
    Vikram
    <Apr 9, 2003 2:57:45 AM EDT> <Error> <RDBMSRealm> <000000> <An error occured cre
    ating a database connection for the realm.
    java.sql.SQLException: Invalid port: weblogic:mssqlserver4:localhost:1433
    at weblogic.jdbc.mssqlserver4.ConnectionInfo.<init>(ConnectionInfo.java:
    193)
    at weblogic.jdbc.mssqlserver4.ConnectDriver.parse(ConnectDriver.java:333
    at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:1
    02)
    at com.bea.p13n.security.realm.RDBMSDelegate.<init>(RDBMSDelegate.java:1
    69)
    at com.bea.p13n.security.realm.RDBMSDelegate$DFactory.getInstance(RDBMSD
    elegate.java:962)
    at com.bea.p13n.security.realm.internal.Pool.<init>(Pool.java:53)
    at com.bea.p13n.security.realm.RDBMSRealm.createPool(RDBMSRealm.java:153
    at com.bea.p13n.security.realm.RDBMSRealm.<init>(RDBMSRealm.java:140)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:232)
    at weblogic.security.acl.Realm.getRealm(Realm.java:87)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    >
    <Apr 9, 2003 2:57:45 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    in
    itialize the server: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    Reason: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    [config.xml]

    Try removing the server section from the SchemaProperties line.
    Preferrably do not use localhost or hostnames in the server
    configuration file.
    <RDBMSRealm
    Name="wlcsRealm"
    DatabaseDriver="weblogic.jdbc.mssqlserver4.Driver"
    DatabasePassword="weblogic"
    DatabaseURL="jdbc:weblogic:mssqlserver4:yourIPAddress:1433"
    RealmClassName="com.bea.p13n.security.realm.RDBMSRealm"
    SchemaProperties="user=system;password=weblogic"/>
    Also consider ...
    If you have a new Portal database created in SQL Server?
    Does the user system have the Portal database as his default database?
    -- Jim
    Vikram wrote:
    Hi,
    We are having problems configuring a Platform Domain with MS Sql Server 2000.
    We are using Weblogic version 7.0.0.2. These are the steps we followed
    1.We manually created a database called TestDB and created a user account called
    "system", pwd ==>> "weblogic" in SQL server and assigned him as the DB owner for
    the TestDB created.
    2. Changed dbsettings_properties files (Commented pointbase entries and uncommented
    SQL Server entries. I gave the connection parameter as connection=jdbc:weblogic:mssqlserver4:localhost:1433
    in this file.
    3. Modified Config.xml and changed properties for DataSyncPool, WLIPool, CommercePool,WLIPool
    and modified the RDBMS realm properties to point to the database.
    4. ran the create_db script and it seemed to have run fine looking at the log
    file.
    5. I then tried to start the BEA Server instance and I get the following error.
    I am also attaching the config.xml file for reference.
    Appreciate any help/suggestions. Thanks in Advance.
    Vikram
    <Apr 9, 2003 2:57:45 AM EDT> <Error> <RDBMSRealm> <000000> <An error occured cre
    ating a database connection for the realm.
    java.sql.SQLException: Invalid port: weblogic:mssqlserver4:localhost:1433
    at weblogic.jdbc.mssqlserver4.ConnectionInfo.<init>(ConnectionInfo.java:
    193)
    at weblogic.jdbc.mssqlserver4.ConnectDriver.parse(ConnectDriver.java:333
    at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:1
    02)
    at com.bea.p13n.security.realm.RDBMSDelegate.<init>(RDBMSDelegate.java:1
    69)
    at com.bea.p13n.security.realm.RDBMSDelegate$DFactory.getInstance(RDBMSD
    elegate.java:962)
    at com.bea.p13n.security.realm.internal.Pool.<init>(Pool.java:53)
    at com.bea.p13n.security.realm.RDBMSRealm.createPool(RDBMSRealm.java:153
    at com.bea.p13n.security.realm.RDBMSRealm.<init>(RDBMSRealm.java:140)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:232)
    at weblogic.security.acl.Realm.getRealm(Realm.java:87)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    <Apr 9, 2003 2:57:45 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    in
    itialize the server: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    Reason: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    <Domain Name="epmsDomain">
    <Log
    FileName="logs/wl-domain.log"
    Name="epmsDomain"
    />
    <!-- Configuration Wizard Cluster and Admin/Managed Node support -->
    <Server
    Name="platformServer"
         ListenAddress="localhost"
    ListenPort="7501"
    NativeIOEnabled="true"
    TransactionLogFilePrefix="logs/"
    >
    <SSL
    Name="platformServer"
    ListenPort="7502"
    Enabled="true"
    ServerCertificateChainFileName="ca.pem"
    ServerCertificateFileName="democert.pem"
    ServerKeyFileName="demokey.pem"
    />
    <Log
    FileName="logs/weblogic.log"
    />
    <WebServer
    DefaultWebApp="splashPage"
    LogFileName="./logs/access.log"
    LoggingEnabled="true"
    Name="platformServer"
    />
    </Server>
    <!-- WLP Pool -->
    <JDBCConnectionPool
    Name="commercePool"
    DriverName="weblogic.jdbc.mssqlserver4.Driver"
    URL="jdbc:weblogic:mssqlserver4:localhost:1433"
    Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Password="weblogic"
    InitialCapacity="20"
    MaxCapacity="20"
    CapacityIncrement="1"
    RefreshMinutes="0"
    ShrinkingEnabled="false"
    Targets="platformServer"
    TestConnectionsOnReserve="false"
    TestTableName="WEBLOGIC_IS_ALIVE"
    />
    <!-- WLI Pool -->
    <JDBCConnectionPool
    CapacityIncrement="2"
    DriverName="weblogic.jdbc.mssqlserver4.Driver"
    InitialCapacity="8"
    LoginDelaySeconds="1"
    MaxCapacity="36"
    Name="wliPool"
    Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Password="weblogic"
    RefreshMinutes="0"
    ShrinkPeriodMinutes="15"
    ShrinkingEnabled="true"
    Targets="platformServer"
    URL="jdbc:weblogic:mssqlserver4:localhost:1433"
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="false"
    JNDIName="weblogic.jdbc.jts.commercePool"
    Name="commercePool"
    PoolName="commercePool"
    Targets="platformServer"
    />
    <JDBCDataSource
    JNDIName="weblogic.jdbc.pool.commercePool"
    Name="commercePool"
    PoolName="commercePool"
    Targets="platformServer"
    />
    <JDBCDataSource
    JNDIName="WLAI_DataSource"
    Name="WLAI_DataSource"
    PoolName="wliPool"
    Targets="platformServer"
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="true"
    JNDIName="com.bea.wlpi.TXDataSource"
    Name="TXDataSource"
    PoolName="wliPool"
    Targets="platformServer"
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="true"
    JNDIName="WLCHub.DS"
    Name="WLCHub.DS"
    PoolName="wliPool"
    Targets="platformServer"/>
    />
    <!-- Configure WebLogic Workshop to run in Platform domain -->
    <JDBCTxDataSource
         EnableTwoPhaseCommit="true"
    JNDIName="cgDataSource"
    Name="cgDataSource"
    PoolName="commercePool"
    Targets="platformServer"/>
    <JDBCTxDataSource
    EnableTwoPhaseCommit="true"
    JNDIName="cgSampleDataSource"
    Name="cgSampleDataSource"
    PoolName="commercePool"
    Targets="platformServer"/>
    <JMSConnectionFactory JNDIName="weblogic.jws.jms.QueueConnectionFactory"
    Name="cgQueue" Targets="platformServer"/>
    <JMSJDBCStore ConnectionPool="commercePool" Name="cgJDBCStore" PrefixName="WEBLOGIC"/>
    <JMSServer Name="cgJMSServer" Store="cgJDBCStore" Targets="platformServer">
    <JMSQueue JNDIName="jws.queue" Name="cgJWSQueue" StoreEnabled="default"/>
    </JMSServer>
    <JTA Name="epmsDomain" TimeoutSeconds="3600"/>
    <!-- End: Configure WebLogic Workshop to run in Platform domain -->
    <!-- WLP DATASYNC -->
    <JDBCConnectionPool
    Name="dataSyncPool"
    DriverName="weblogic.jdbc.mssqlserver4.Driver"
    URL="jdbc:weblogic:mssqlserver4:localhost:1433"
    Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Password="WEBLOGIC"
    InitialCapacity="1"
    MaxCapacity="5"
    CapacityIncrement="1"
    RefreshMinutes="0"
    ShrinkingEnabled="false"
    TestConnectionsOnReserve="false"
    TestTableName="WEBLOGIC_IS_ALIVE"
    Targets="platformServer"/>
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="false"
    JNDIName="weblogic.jdbc.jts.dataSyncPool"
    Name="dataSyncPool"
    PoolName="dataSyncPool"
    Targets="platformServer"/>
    />
    <!-- General Config -->
    <Security
    GuestDisabled="false"
    Name="epmsDomain"
    PasswordPolicy="wl_default_password_policy"
    Realm="wl_default_realm"
    CompatibilityMode="true"
    />
    <PasswordPolicy
    Name="wl_default_password_policy"
    />
    <Realm
    Name="wl_default_realm"
    CachingRealm="wlcsCachingRealm"
    FileRealm="wl_default_file_realm"
    />
    <CachingRealm
    BasicRealm="wlcsRealm"
    CacheCaseSensitive="true"
    Name="wlcsCachingRealm"
    />
    <RDBMSRealm DatabaseDriver="weblogic.jdbc.mssqlserver4.Driver"
    DatabasePassword="weblogic"
    DatabaseURL="jdbc:weblogic:mssqlserver4:localhost:1433"
    SchemaProperties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Name="wlcsRealm"
    RealmClassName="com.bea.p13n.security.realm.RDBMSRealm"/>
    <FileRealm
    Name="wl_default_file_realm"
    />
    <StartupClass
    ClassName="com.beasys.commerce.ebusiness.security.KeyBootstrap"
    FailureIsFatal="false"
    Name="KeyBootstrap"
    Targets="platformServer"
    />
    <!-- WLI configuraion for Platform -->
    <JMSConnectionFactory Name="WLI_B2B_TopicFactory"
    JNDIName="com.bea.wli.b2b.server.TopicConnectionFactory"
    AllowCloseInOnMessage="true"
    UserTransactionsEnabled="true"
    Targets="platformServer"
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="true"
    JNDIName="com.bea.wli.b2b.rosettanet.QueueConnectionFactory"
    Name="RNQueueFactory"
    Targets="platformServer"
    UserTransactionsEnabled="true"
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="false"
    DefaultDeliveryMode="Persistent"
    DefaultPriority="4"
    DefaultTimeToLive="0"
    JNDIName="com.bea.wlai.JMSConnectionFactory"
    MessagesMaximum="10"
    Name="WLAI_JMSConnectionFactory"
    OverrunPolicy="KeepOld"
    UserTransactionsEnabled="true"
    Targets="platformServer"/>
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="true"
    JNDIName="com.bea.wlpi.TopicConnectionFactory"
    Name="wlpiFactory"
    Targets="platformServer"
    UserTransactionsEnabled="true"
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="true"
    JNDIName="com.bea.wlpi.QueueConnectionFactory"
    Name="wlpiQueueFactory"
    Targets="platformServer"
    UserTransactionsEnabled="true"
    />
    <JMSJDBCStore
    ConnectionPool="wliPool"
    Name="JMSWLIStore"
    PrefixName="PBPUBLIC"
    />
    <JMSServer Name="WLIJMSServer"
    Targets="platformServer"
    TemporaryTemplate="TemporaryTemplate"
    Store="JMSWLIStore">
    <JMSTemplate Name="TemporaryTemplate"/>
    <!-- B2B -->
    <JMSQueue Name="WLI_B2B_RNEncoderQueue"
    JNDIName="com.bea.wli.b2b.rosettanet.EncoderQueue"/>
    <JMSTopic Name="WLI_B2B_Topic"
    JNDIName="com.bea.wli.b2b.server.B2BTopic"/>
    <JMSQueue Name="WLI_B2B_OutboundQueue"
    JNDIName="com.bea.b2b.OutboundQueue"/>
    <!-- BPM -->
    <JMSTopic Name="wlpiEvent"
    JNDIName="com.bea.wlpi.EventTopic"/>
    <JMSQueue Name="WLI_BPM_Timer"
    JNDIName="com.bea.wli.bpm.TimerQueue"
    StoreEnabled="true"
    Template="WLI_JMSTemplate"/>
    <JMSQueue Name="WLI_BPM_Event"
    JNDIName="com.bea.wli.bpm.EventQueue"
    StoreEnabled="true"
    Template="WLI_JMSTemplate"/>
    <JMSQueue Name="WLI_BPM_ValidatingEvent"
    JNDIName="com.bea.wli.bpm.ValidatingEventQueue"
    StoreEnabled="true"
    Template="WLI_JMSTemplate"/>
    <JMSTopic Name="WLI_BPM_Error"
    JNDIName="com.bea.wli.bpm.ErrorTopic"/>
    <JMSTopic Name="WLI_BPM_Audit"
    JNDIName="com.bea.wli.bpm.AuditTopic"/>
    <JMSTopic Name="WLI_BPM_Notify"
    JNDIName="com.bea.wli.bpm.NotifyTopic"/>
    <!-- AI -->
    <JMSQueue Name="WLAI_ASYNC_REQUEST_QUEUE"
    JNDIName="com.bea.wlai.ASYNC_REQUEST_QUEUE"/>
    <JMSQueue Name="WLAI_ASYNC_RESPONSE_QUEUE"
    JNDIName="com.bea.wlai.ASYNC_RESPONSE_QUEUE"/>
    <JMSQueue Name="WLAI_EVENT_QUEUE"
    JNDIName="com.bea.wlai.EVENT_QUEUE"/>
    <JMSTopic Name="WLAI_EVENT_TOPIC"
    JNDIName="com.bea.wlai.EVENT_TOPIC"/>
         <!-- App View control -->
         <JMSQueue JNDIName="com.bea.wlai.WORKSHOP_ASYNC_RESPONSE_QUEUE" Name="WLAI_WORKSHOP_ASYNC_RESPONSE_QUEUE"/>
         <JMSQueue JNDIName="com.bea.wlai.WORKSHOP_EVENT_QUEUE" Name="WLAI_WORKSHOP_EVENT_QUEUE"/>
    <!-- WLI -->
    <JMSQueue Name="WLI_FailedEvent"
    JNDIName="com.bea.wli.FailedEventQueue"
    StoreEnabled="true"/>
    <JMSTemplate Name="WLI_JMSTemplate"
    ErrorDestination="WLI_FailedEvent"
    RedeliveryDelayOverride="60000"
    RedeliveryLimit="10"/>
    </JMSServer>
    <JMSJDBCStore Name="JMSWLIStore"
    ConnectionPool="wliPool"
    PrefixName="platformServer"/>
    <!-- Distributed queue/topic configuration for WLI components -->
    <!-- End WLI configuraion for Platform -->
    <!--===========================================================================-->
    <!-- Configure the J2EE enterprise applications supporting the Platform -->
    <!--===========================================================================-->
    <!-- The enterprise application containing the WLS-based Tax and Payment WebService -->
    <Application
    Deployed="true"
    Name="taxWSApp"
    Path="C:/bea/user_projects/epmsDomain/beaApps/taxWSApp"
    TwoPhase="true"
    >
    <EJBComponent
    Name="tax"
    URI="tax.jar"
    Targets="platformServer"
    />
    <WebAppComponent
    Name="tax-webservice"
    URI="tax-ws"
    Targets="platformServer"
    />
    </Application>
    <Application
    Deployed="true"
    Name="paymentWSApp"
    Path="C:/bea/user_projects/epmsDomain/beaApps/paymentWSApp"
    TwoPhase="true"
    >
    <EJBComponent
    Name="payment"
    URI="payment.jar"
    Targets="platformServer"
    />
    <WebAppComponent
    Name="payment-edit webservice"
    URI="pay-ws"
    Targets="platformServer"
    />
    </Application>
    <!-- The enterprise application containing the installed/online links documentation -->
    <Application
    Deployed="true"
    Name="wlpDocsApp"
    Notes=""
    Path="C:/bea/weblogic700/portal/lib"
    TwoPhase="true"
    >
    <WebAppComponent
    IndexDirectoryEnabled="false"
    Name="wlpDocs"
    Targets="platformServer"
    URI="wlpDocs.war"
    ServletReloadCheckSecs="300"
    />
    </Application>
    <!-- The enterprise application containing the WLP components -->
    <Application
    Deployed="true"
    Name="portalApp"
    Notes=""
    Path="C:/bea/user_projects/epmsDomain/beaApps/portalApp"
    TwoPhase="true"
    >
    <ApplicationConfiguration
    Name="portalApp"
    Targets="platformServer"
    URI="META-INF/application-config.xml"
    />
    <EJBComponent
    Name="events"
    Targets="platformServer"
    URI="events.jar"
    />
    <EJBComponent
    Name="pipeline"
    Targets="platformServer"
    URI="pipeline.jar"
    />
    <EJBComponent
    Name="property"
    Targets="platformServer"
    URI="property.jar"
    />
    <EJBComponent
    Name="rules"
    Targets="platformServer"
    URI="rules.jar"
    />
    <EJBComponent
    Name="usermgmt"
    Targets="platformServer"
    URI="usermgmt.jar"
    />
    <EJBComponent
    Name="customer"
    Targets="platformServer"
    URI="customer.jar"
    />
    <EJBComponent
    Name="ebusiness"
    Targets="platformServer"
    URI="ebusiness.jar"
    />
    <EJBComponent
    Name="portal"
    Targets="platformServer"
    URI="portal.jar"
    />
    <EJBComponent
    Name="campaign"
    Targets="platformServer"
    URI="campaign.jar"
    />
    <EJBComponent
    Name="catalogws"
    Targets="platformServer"
    URI="catalogws.jar"
    />
    <EJBComponent
    Name="document"
    Targets="platformServer"
    URI="document.jar"
    />
    <EJBComponent
    Name="ejbadvisor"
    Targets="platformServer"
    URI="ejbadvisor.jar"
    />
    <EJBComponent
    Name="mail"
    Targets="platformServer"
    URI="mail.jar"
    />
    <EJBComponent
    Name="placeholder"
    Targets="platformServer"
    URI="placeholder.jar"
    />
    <WebAppComponent
    Name="toolSupport"
    Targets="platformServer"
    URI="toolSupport"
    ServletReloadCheckSecs="300"
    />
    <WebAppComponent
    Name="tools"
    Targets="platformServer"
    URI="tools"
    ServletReloadCheckSecs="300"
    />
    <WebAppComponent
    Name="datasync"
    Targets="platformServer"
    URI="datasync"
    ServletReloadCheckSecs="300"
    />
    <WebAppComponent
    Name="splashPage"
    Targets="platformServer"
    URI="splashPage"
    ServletReloadCheckSecs="300"
    />
    <!-- The enterprise application containing the WLP P13N Console components -->
    </Application>
    <Application
    Deployed="true"
    TwoPhase="true"
    StagedTargets="platformServer"
    Name="p13nConsoleApp"
    Path="C:/bea/weblogic700/portal/lib"
    >
    <WebAppComponent
    Name="p13nConsole"
    ServletReloadCheckSecs="300"
    Targets="platformServer"
    URI="p13nConsole.war"
    />
    </Application>
    <!-- The enterprise application containing the WLI components -->
    <Application Deployed="true" LoadOrder="900" Name="EAI" Path="C:/bea/weblogic700/samples/workshop/wlai/ear/" TwoPhase="true">
    <EJBComponent
    DeploymentOrder="100"
    Name="repository-ejb.jar"
         Targets="platformServer"
    URI="repository-ejb.jar"/>
    <EJBComponent Name="WLI-B2B Startup"
    DeploymentOrder="200"
    Targets="platformServer"
    URI="b2b-startup.jar"/>
    <EJBComponent DeploymentOrder="300" Name="b2b-rosettanet.jar" Targets="platformServer" URI="b2b-rosettanet.jar"/>
    <WebAppComponent DeploymentOrder="400" Name="b2b.war" Targets="platformServer" URI="b2b.war"/>
    <WebAppComponent DeploymentOrder="500" Name="b2bconsole.war" Targets="platformServer" URI="b2bconsole.war"/>
    <EJBComponent DeploymentOrder="600" Name="WLI-AI Server" Targets="platformServer" URI="wlai-server-ejb.jar"/>
    <WebAppComponent DeploymentOrder="700" Name="wlai" Targets="platformServer" URI="wlai.war"/>
    <EJBComponent DeploymentOrder="800" Name="WLI-AI Async Processor" Targets="platformServer" URI="wlai-asyncprocessor-ejb.jar"/>
    <EJBComponent DeploymentOrder="900" Name="WLI-AI Event Processor" Targets="platformServer" URI="wlai-eventprocessor-ejb.jar"/>
    <EJBComponent DeploymentOrder="1000" Name="wlpi-ejb.jar" Targets="platformServer" URI="wlpi-ejb.jar"/>
    <EJBComponent DeploymentOrder="1100" Name="wlpi-master-ejb.jar" Targets="platformServer" URI="wlpi-master-ejb.jar"/>
    <EJBComponent DeploymentOrder="1200" Name="wlpi-mdb-ejb.jar" Targets="platformServer" URI="wlpi-mdb-ejb.jar"/>
    <EJBComponent DeploymentOrder="1300" Name="WLXTEJB.jar" Targets="platformServer" URI="WLXTEJB.jar"/>

  • Problem with NW04s SR2 installation with MS SQL Server 2000 SP4

    I’m struggling with the NW04s installation with MS SQL Server 2000.
    The installation stops at the step “Create/modify database schema SAPJ2EDB”.
    The following error/info from log file,
    INFO       2007-06-06 12:02:33 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doConfiguration of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|NW_MSS_SRVCFG|ind|ind|ind|ind|6|0.
    INFO       2007-06-06 12:02:35 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doTempdb of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:02:36 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doSwitch of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:02:36 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doTempDBAnalyze of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:02:37 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doTempDBBeforeRestart of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:02:38 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doRestartServer of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:02:58 [ianxbservi.cpp:697]
               CIaNtServices::stop(const map<iastring,iastring>&)
    The service 'MSSQLSERVER' stopped successfully on host 'GBCZ672C'.
    INFO       2007-06-06 12:03:10 [ianxbservi.cpp:632]
               CIaNtServices::start(const map<iastring,iastring>&)
    The service 'MSSQLSERVER' started successfully on host 'GBCZ672C'.
    INFO       2007-06-06 12:03:21 [ianxbservi.cpp:632]
               CIaNtServices::start(const map<iastring,iastring>&)
    The service 'SQLSERVERAGENT' started successfully on host 'GBCZ672C'.
    INFO       2007-06-06 12:03:21 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doTempDBAfterRestart of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:03:22 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doChangeTempSetNewSize of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:03:39 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step CheckParameters of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
    INFO       2007-06-06 12:03:39 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step CreateDirectories of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
    INFO       2007-06-06 12:03:40 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step CreateDatabase of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
    ERROR      2007-06-06 12:03:40 [iaxxgenimp.cpp:731]
               showDialog()
    FCO-00011  The step CreateDatabase with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase was executed with status ERROR .
    ERROR      2007-06-06 12:03:40
               lib=iamodmssql module=CIaNtMssDmo
    MDB-05053  Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.
    INFO       2007-06-06 12:04:04 [iaxxgenimp.cpp:774]
               showDialog()
    An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase".
    ERROR      2007-06-06 12:04:05 [iaxxgenimp.cpp:731]
               showDialog()
    FCO-00011  The step CreateDatabase with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase was executed with status ERROR .
    Please let me know if you can help or if there is any other way around.
    Many Thanks in advance.
    Ritin Jain

    Hi All,
    I was not able to solve the problem with MS SQL 2000, but I was able to resolve the issue with MS SQL 2005.
    You have to chhose the following settings while instalation,
    Service Account - Select one of the following options:
    1) Use the built-in System account for each service and choose Local system or Network Service.
    2) Use a domain user account, and enter the user name and password.
    Under Start services at the end of setup make sure that SQL Server and SQL Server Agent are selected.
    Authentication Mode      
    1) Select Mixed Mode (Windows Authentication and SQL Server Authentication).
    This mode is required for a Java or ABAP+Java system.
    If you choose this mode, you have to set the password for the sa login.
    Note: The password for the sa login must comply with the Windows password policy.
    Collation Settings      
    1) Select SQL collations (used for compatibility with previous versions of SQL Server).
    2) From the drop-down list select Binary order based on code point comparison, for use with the 850 (Multilingual) Character Set.
    I hope this helps!

  • I want make use of SQL Server Instance, while connecting

    hi,
    i have developed Code using normal conditions,Like i have not checked for SQL Server Instances, my client need to b use Instances of the SQL Server, so i need to change the code.
    can any one help Regarding SQL Server Instances Connection coding.
    Ex: jdbc:JSQLConnect://servername\Instance_Name
    can any one help out me, it would be grate help for me,
    thanks.

    Read the JDBC tutorial and read the SQL Server JDBC driver documentation.
    http://www.google.com/search?q=jdbc+tutorial+site:sun.com
    http://www.google.com/search?q=sql+server+jdbc+driver+site:microsoft.com

  • URGENT ! Using Sun's J2EE RI Server with MS SQL Server 2000

    I'm using the J2EE Server that comes with the J2EE 1.3.1 package from Sun. I'm trying to load a datasource using the free MS SQL Server 2000 Driver for JDBC, but I'm always getting this error (I've run out of ideas so maybe someone in this forum can help):
    java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.RemoteException: nested exception is: javax.ejb.EJBException: Unable to connect to database. No suitable driver; nested exception is: javax.ejb.EJBException: Unable to connect to database. No suitable driver ...
    I'm using MS SQL Server 2000 Driver for JDBC, my classpath setting is:
    CLASSPATH=D:\j2sdk1.4.0_01\jre\lib\ext\mysql-connector-j-2.0.14;D:\MS-JDBC-Driver\lib\msbase.jar;D:\MS-JDBC-Driver\lib\mssqlserver.jar;D:\MS-JDBC-Driver\lib\msutil.jar;E:\Installers\Java Related\jdbc dirvers\JSQLConnect3_27\JSQLConnect.jar
    I have the same J2EE_CLASSPATH setting in my userconfig.bat file.
    I've loaded this driver class in deploytool:
    com.microsoft.jdbc.sqlserver.SQLServerDriver
    and my connection url is:
    jdbc:microsoft:sqlserver://localhost:1433;databasename=test
    What's weird is that I've also tested these settings with a simple Java Application and they worked fine, but when I try to use the same for the j2ee server from sun, I always get the annoying "no suitable driver" error.
    If anyone has ever come up with a solution that works, please help. You may post you reply here or better yet, email me at [email protected]
    Thanks a lot in advance !

    Hi,
    The error "no suitable driver" occurs when something goes wrong with the connection URL.so make sure that u are using the correct URL format (check if any of the info is case sensitive etc) or atleast try other URL alternatives (for MS jdbc driver).
    try these changes only through deployment tool->tools->server configuration->datasources->standard.(instead of editing resource.properties directly).
    last not the least - make sure that there is NO "rem" keyword before "set J2EE_CLASSPATH" in the userconfig.bat file :)
    HTH,
    - asharafkk

  • Problems creating the Master Repository with MS SQL Server 2000

    Hello guys!
    I can't create the Master Repository with MS SQL Server 2000 database.
    Wath is the correct adress in the URL?
    I select the Driver: com.microsoft.jdbc.sqlserver.SQLServerDriver and the URL: *jdbc:microsoft:sqlserver://<host>:<port>;SelectMethod=cursor[;<property>=<value>...]*
    Thanks
    Maurício
    Edited by: user857262 on 03/10/2008 10:05

    Hi Maurício,
    For MS SQL Server the following drivers should avaliable in /drivers folder (http://www.inetsoftware.de/),
    * msutil.jar
    * mssqlserver.jar
    * msbase.jar
    JDBC Driver is:
    com.microsoft.jdbc.sqlserver.SQLServerDriver
    JDBC URL is:
    jdbc:sqlserver://serverName\instance:port;property=value[;property=value]
    Example,
    jdbc:sqlserver://myHost:1433;selectMethod=cursor;databaseName=myDB
    Thanks,
    G

Maybe you are looking for

  • Garageband wont open after install

    I installed garageband from iLife 06 on a 500mz imac G3 running 10.3.9 with my machine in target disk mode with a friend having the install DVD run from his powerbook G4. installed only Garageband for space reasons and the install appeared to be succ

  • Problem creating Header Condition in BAPI_PO_CREATE1

    Hello Gurus,    I am having problems with creating a header conditions using the BAPI BAPI_PO_CREATE1. I am filling up table such as: POCONDHEADER, POCONDHEADERX. It creates a PO document but the header conditions I supplied is not included. How do I

  • Return Component flag in Good Receipt

    Hello, I'm creating a report which need to know which one is a Good Receipt and a Return Component from Production Order. I've tried to look at the table, but can't find which is the flag for Return Component and the other (Good Receipt). Does anyone

  • The email links in websites do not activate MS Outlook in Windows XP Pro.

    I'm running Windows XP Pro and using Firefox 5.x. I used to be able to have MS Outlook pop up when clicked on email links in various websites. But lately, maybe since I did the most recent update for v5, clicking on the links does not bring open up a

  • Install 10g on RH Linux AS

    I am trying to install the 10g DB on Linux and I got the following: Checking installer requirements... Checking operating system version: must be redhat-2.1, UnitedLinux-1.0 or redhat-3 The Oracle Version :10g Release 1(10.1.0) for Linux x86 The Linu