JMS Store Exception with MS SQL Server in Win2K
Hello,
All my messages are persisted in some PTP queues within JMSStore and JMSState
in MSSQL Server.
When WLS is restarted, I have the following exception, any idea?
<07-Oct-02 16:28:05 BST> <Info> <JMS> <JMSServer "JMSServer", Opening JDBC store
tables "JMSStore" and "JMSState" using connection
pool "MyCMSDBConnectionPool".>
<07-Oct-02 16:28:06 BST> <Alert> <JMS> <JMSServer "JMSServer", store failed to
open, java.io.IOException: JMS JDBC store, connecti
on pool = <MyCMSDBConnectionPool>, prefix = <null>: recover
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
not re-read row data for column 1.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseResultSet.validateColumnIndex(Unknown Source)
at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
at weblogic.jms.store.JDBCIOStream.doRecoverBodies(JDBCIOStream.java:800)
at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:706)
at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:915)
at weblogic.jms.store.JMSStore.recover(JMSStore.java:138)
at weblogic.jms.backend.BEStore.open(BEStore.java:182)
at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy0.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy53.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:48
0)
at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
Hmmm. Is this a new driver version, or just coincidence? -- The same problem
was posted in this newsgroup last week. I'm beginning to suspect
there is a bug in the MS driver.
Anyhow, please contact BEA customer support. Meanwhile, the work-around is
to use WebLogic's driver.
Tom, BEA
Thierry wrote:
> Hello,
>
> All my messages are persisted in some PTP queues within JMSStore and JMSState
> in MSSQL Server.
>
> When WLS is restarted, I have the following exception, any idea?
>
> <07-Oct-02 16:28:05 BST> <Info> <JMS> <JMSServer "JMSServer", Opening JDBC store
> tables "JMSStore" and "JMSState" using connection
> pool "MyCMSDBConnectionPool".>
> <07-Oct-02 16:28:06 BST> <Alert> <JMS> <JMSServer "JMSServer", store failed to
> open, java.io.IOException: JMS JDBC store, connecti
> on pool = <MyCMSDBConnectionPool>, prefix = <null>: recover
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
> not re-read row data for column 1.
> at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
> at com.microsoft.jdbc.base.BaseResultSet.validateColumnIndex(Unknown Source)
> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
> at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
> at weblogic.jms.store.JDBCIOStream.doRecoverBodies(JDBCIOStream.java:800)
> at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:706)
> at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:915)
> at weblogic.jms.store.JMSStore.recover(JMSStore.java:138)
> at weblogic.jms.backend.BEStore.open(BEStore.java:182)
> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
> at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
> at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
> at java.lang.reflect.Method.invoke(Native Method)
> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> at $Proxy0.updateDeployments(Unknown Source)
> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
> at java.lang.reflect.Method.invoke(Native Method)
> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> at $Proxy53.start(Unknown Source)
> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:48
> 0)
> at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
> at weblogic.management.Admin.finish(Admin.java:644)
> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
> at weblogic.Server.main(Server.java:35)
Similar Messages
-
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"/> -
How to get JDev 10.1.2/ADF working with MS SQL Server Identity Column
Hello JDevTeam & JDevelopers,
I want to use JDev/ADF with a MS SQL Server 2005 database that contains tables employing IDENTITY Columns.
Using JDev/ADF and DBSequence with an Oracle database employing before triggers/sequences accomplishes what I am trying to do except I want to accomplish the same thing using a MSSQL Server 2005 database. Unfortunately I cannot change the database.
I have been able to select records but I am unable to insert records (due to my lack of knowledge) when using MS/SQL Server Identity Columns with JDev/ADF.
The following are the steps taken thus far.
Step1: Create table named test in the 2005 MSSQL Server (see script below).
Step2: Register 3rd Party JDBC Driver with JDeveloper; Using use Tools/Manage Libraries. Create a new entry in User Libraries with the following;
Library Name = Ms2005Jdbc
Class Path = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu\sqljdbc.jar
(note: Latest TYPE 4 JDBC driver for Microsoft SQL Server 2005 - free at http://msdn.microsoft.com/data/ref/jdbc/)
Step3:Create New Database Connection;
Connection Name = testconn1
Type = Third Party JDBC Driver
Authentication Username = sa, Password = password, Check Deploy Password
Connection
Driver Class = com.microsoft.sqlserver.jdbc.SQLServerDriver
Library = Ms2005Jdbc
Classpath = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu
URL = jdbc:sqlserver://192.168.1.151:1433;instanceName=sqlexpress;databaseName=test
Test Connection = Success!
Step5: Create a new application workspace using Web Application default template
Step6: In Model project, Create new Business Components Diagram.
Step7: Create new Entity Object. Goto to connections/testconn1, open tables and drag table test onto the diagram.
Step8: Generate Default Data Model Components by right-clicking on Entity Object. Except all the defaults.
When I test the Appmodule I select the view object and can scroll through all the records without error. If I try to insert a record, I get JBO-27014: Attribute testid in test is required.
Going back to the EntityObject I deselect the Mandatory attribute and re-run the test. Now when I try to insert it accepts the value for testname but it does not update the PK testid like it would using an "JDev/ADF/DBSequence/Oracle database/before trigger/sequence" solution.
Going back to the EntityObject and selecting refresh on insert does not solve this problem either. Changing the URL connection string and adding "SelectMethod=cursor" did not help and changing the SQl Flavor to SQLServer produced errors in the Business Components Browser. I've tried overriding isAttributeChanged() and other things as well.
I am totally stuck! Can anyone provide a solution?
Thanks for you help,
BG...
Create table named test
use [testdb]
go
set ansi_nulls on
go
set quoted_identifier on
go
create table [test](
[testid] [int] identity(0,1) not null,
[testname] [nvarchar](50) collate sql_latin1_general_cp1_ci_as not null,
constraint [pk_test] primary key nonclustered
[testid] asc
)with (pad_index = off, ignore_dup_key = off) on [primary]
) on [primary]Figured it out!
When using the MS SQL Server 2000 Database with the MS JDBC 2000 Driver you specify the SQL Flavor to SQLServer. However setting the SQL Flavor to SQLServer with MS SQL Server 2005 Database and the MS JDBC 2005 Driver will *** fail ***.
When working with the MS SQL Server 2005 Database and the MS JDBC 2005 Driver you set the SQL Flavor to SQL92 and the Type Map to Java.
If using a named instance like I am you would specify the URL = jdbc:sqlserver://<db host ip address>:<listening port>;instanceName=<your instance name>;selectMethod=cursor;databaseName=<your database name> (note: leave out the < >)
The 2005 Driver Class is different then the 2000 and is specified as com.microsoft.sqlserver.jdbc.SQLServerDriver
Note: In a default MS SQL Server 2005 installation the listening port will change *** everytime *** the host is restarted! You can override this though.
For the primary key you need to deselect the Mandatory attribute in the EntityObject editor.
Set Refresh on insert/update = no.
Set Updateable = never.
Now my Primary Keys which get their values from the Identity Column are working with ADF in a predictable way.
Simple enough but I have been away from this stuff for awhile.
BG... -
Problem Running SSIS Package with a SQL Server Agent
SQL Server: SQL Server 2012
VS: Visual Studio 2012
Hello,
I have been having a problem running SSIS packages by using a SQL Server Agent job. I first created these SSIS packages in a separate IS project in Visual Studio. I imported the packages to the Integration Services (Package
Store) instance on my SQL Server and tried to create a job that would run them from there.
At first I read around about needing a proxy account to allow the agent/packages to access the file system since these packages are importing data from a flat file in the SQL database. So I created a temporary admin user to
use as the user for the agent. I did this by going to Services.msc on the server and linked the account the agent's "logon as". Then arose another issue where I am getting an error about using the incorrect type for my connection managers.
The connection manager "TestFile" is an incorrect type. The type required is "OLEDB". The type available to the component is "FLATFILE". Source: Data Flow Task Flat File Destination [2] Description:
Cannot open the datafile "O:\*****\Success.txt"
I am not sure what this even means as I am getting this error even with a test package that doesn't do anything with the database. I have just two flat file connection managers in this test project one for grabbing the source file and one for
creating the new test file.
I am not sure what to do.
Thanks in advance,
MattI accidently created two posts. The newest one has the details.
I did not mean to.
SQL Server: SQL Server 2012
VS: Visual Studio 2012
Hello,
I have been having a problem running SSIS packages by using a SQL Server Agent job. I first created these SSIS packages in a separate IS project in Visual Studio. I imported the packages to the Integration Services (Package
Store) instance on my SQL Server and tried to create a job that would run them from there.
At first I read around about needing a proxy account to allow the agent/packages to access the file system since these packages are importing data from a flat file in the SQL database. So I created a temporary admin user to
use as the user for the agent. I did this by going to Services.msc on the server and linked the account the agent's "logon as". Then arose another issue where I am getting an error about using the incorrect type for my connection managers.
The connection manager "TestFile" is an incorrect type. The type required is "OLEDB". The type available to the component is "FLATFILE". Source: Data Flow Task Flat File Destination [2] Description:
Cannot open the datafile "O:\*****\Success.txt"
I am not sure what this even means as I am getting this error even with a test package that doesn't do anything with the database. I have just two flat file connection managers in this test project one for grabbing the source file and one for
creating the new test file.
I am not sure what to do.
Thanks in advance,
Matt -
Anyone successfully set up connection pool in s1as with ms sql server 2000?
As subject. Since I have seen a lot of posts about the NoSuchMethodException issue with various dbms providers, and the only "official information" I found thru different forums, google, different sun/javasoft sites and forums are this:
http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsunone%2F8172&zone_32=NoSuchMethodException&wholewords=on
Which is wonderfully vague and provide not-so-much useful information...
As for the information and suggestion posted by other forum members, most or all of them have experience with setting up Oracle, DB2, mySQL, etc., not aimed for MS SQL Server 2000 (you may think, I am just asking for it running MS SQL server with Java... oh well, not my choice)
I still haven't seen any positive feedbacks on how this exception was caused and how to resolve it. I have literally exhausted all leads on how to fix this issue, so right now I'm only interested to know whether anyone in the forum actually have a successful connection pool set up with MS SQL server 2000.
My platform:
w2k sp3
SunOne app server, update1, JDK 1.4.1
latest MS SQL 2000 JDBC driver
This fails with the NoSuchMethodException error:
try {
InitialContext ic = new InitialContext();
DataSource ds = (DataSource) ic.lookup("test_db");
con = ds.getConnection();
System.out.println( "con is created -> " + con );
} catch (Exception ex) {
System.out.println( "failed -> " + ex.getMessage() );
This works just fine:
try {
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
con = DriverManager.getConnection("jdbc:microsoft:sqlserver://xxx.xxx.xxx.xxx:1433;DatabaseName=testdb;SelectMethod=cursor", "username", "password");
System.out.println( "con is created -> " + con );
} catch (Exception ex) {
System.out.println( "failed is fucked -> " + ex.getMessage() );
thanks,
--kuanHi,
Thanks for pointing out that article, I did not find it previously. After following the directions in the artile and your advise, now dbping seems to be able to connect to SQL server.
Thank you very much.
--kuan -
How to store 999999999.00000000 in sql server through ssis package?
I have a field with 999999999.00000000 value of datatype double ?
How to store it in ms sql server 2005 db through ssis package ?
give me details if I have to use derived columns and what to write over there.
please write in details as I am new to SSIS.
Thanks in Advance.The value is coming from informix db .
Can u please suggest hw to write it in my package :
I have taken a OLE DB Source and wrote the follwing command :
" select CASE WHEN T1.t_maxs IS NULL THEN 0.00 ELSE T1.t_maxs END as max_inv
from ttiitm001010 T1 ".
Please give details, as i am new ... -
Connect webdynpro callable object with ms sql server 2000
Hi all
how connect webdynpro callable object with ms sql server 2000?
How can I register on the portal as an additional connection?
thank you very much!Thanks for your answers, Now I have the following problem, to develop this code:
try {
InitialContext iC = new InitialContext();
DataSource dataSource = (DataSource)iC.lookup("jdbc/ConnectionAlias");
Connection con = dataSource.getConnection();
java.sql.Statement stmt = con.createStatement();
ResultSet rs = stmt.executeQuery("select * from ejemplo");
while (rs.next()){
com.sap.test.sql.testsql.wdp.IPrivateTestIViewView.IDatosElement
DatosElement =
wdContext.nodeDatos()
.createDatosElement();
DatosElement.setId(rs.getString("id"));
DatosElement.setNom(rs.getString("nom"));
DatosElement.setNum(rs.getInt("num"));
}catch (SQLException e) {
wdContext.currentContextElement().setB(e.getMessage());
}catch (Exception e){
wdContext.currentContextElement().setB(e.getMessage());
and shows me the following exception
ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
the data that you place in the visual administrator were:
Drivers: com.sap.aii.af.jmsproviderlib (msutil.jar , mssqlserver.jar , msbase.jar)
DataSources: sap.com/JDBCConnector_MyDatasource.xml
Name: MyDatasource
Alias: ConnectionAlias
DriverName: com.sap.aii.af.jmsproviderlib
JDBC Version: 1.x
Driver Class: com.microsoft.jdbc.sqlserver.SQLServerDriver
Database URL: jdbc:microsoft:sqlserver://181.42.101.219:1433;DatabaseName=test
User: sa
Password: abcd1234
did not know the cause of the problem
thanks! -
Exception :DBD, [Microsoft][SQL server] ..State: 42000
Hi All,
I have this technical environment:
-BOXIR3.1.
-DB: SQL server 2005.
-OS: Windows server 2003.
When i try to create a report under Deski, with 2 objects, i get this error:
"Exception: DBD, [ ODBC SQL Server Driver][SQL Server]Impossible
de préparer les insctruction.state:42000"
Note : I have tried all the tests(under the server, with administrator account.. ) but i get the same problem under Deski, but under Webi when i create the same Query nothings happen, in other words it works.
I have copied the SQL query:
SELECT
count (distinct (convert(char
(10),dbo.Tbld_CLI_PMSI_RSS.CLI_Donn_NoAbsEpisode)'_'convert(char
(10),dbo.Tbld_CLI_PMSI_RSS.CLI_Donn_NoRSS))),
year(( dbo.Tbld_CLI_PMSI_RSS.CLI_Date_Entree ))
FROM
dbo.Tbld_CLI_PMSI_RSS
*I activated the log, and i send you the 3 *
interesting line:
1- 2009/04/23 16:23:46.449|==| | | 3296|3924| |||||||||||||||BOCSHelper::DoRealCSDescribe( SELECT count (distinct (convert(char(10),dbo.Tbld_CLI_PMSI_RSS.CLI_Donn_NoAbsEpisode)'_'convert(char(10),dbo.Tbld_CLI_PMSI_RSS.CLI_Donn_NoRSS))), year(( dbo.Tbld_CLI_PMSI_RSS.CLI_Date_Entree )) FROM dbo.Tbld_CLI_PMSI_RSS )
2- sqlboAsyncNet.cpp:83:void __cdecl job_thread::Describe|E| | 3296|2044| |||||||||||||||job_thread::Describe : DBD:[Microsoft][ODBC SQL Server Driver][SQL Server]Impossible de préparer les instructions.
Thank you for any suggestion.
Regards,
Aimen
Edited by: Aimen Akriche on Apr 24, 2009 10:35 AM
Edited by: Aimen Akriche on Apr 24, 2009 10:36 AMHi Aimen,
Following solution might be helpful in resolving the issue.
SQL statement is case sensitive in Business Objects.
Follow these steps:
Test the connection in your universe and click Details.
From Details, copy and run the path for the PRM file used by your connection which will open the relevant PRM file in Notepad.
Modify the following parameter (or add to the PRM file if it does not exist) as follows:
<Parameter Name="CASE_SENSITIVE">N</Parameter>
Save the PRM file.
Close and relaunch Designer.
Regards,
Sarbhjeet Kaur -
How to build a report in web Intelligence using Store procedure under Microsoft SQL Server 2000
Post Author: ltkin
CA Forum: WebIntelligence Reporting
Hi,
How to build a report in web Intelligence using Store procedure under Microsoft SQL Server 2000 ?
Regards,Hi ltkin,
Unfortunately, it is not possible in Xir2 to create Webi reports from stored procedures.
Webi reports can only be created from Universe. So in Business Objects XIR3 we can create a special universe that enables Web Intelligence user's to access stored procedures residing in the database. This is the only way that Web Intelligence user's can access stored procedures.
Please let me know if the above information helps.
Regards,
Pavan -
Hi,
how can I deploy a SSIS package with a SQL SERVER identity to the catalog in SQL Server 2012 programmly?
I tried to use the [SSISDB].[catalog].[deploy_project], but the error said that it could only be used with a WINDOWS identity.
This question has worried me for days.
Is there any way to make the catalog.deploy_project available for a SQL SERVER identity ?
Or just an new solution instead of using the catalog.deploy_project?
best wishes from Qingyuan Lee.Sorry, my description may be confusable.
I use EXECUTE AS , not EXECUTE WITH, to solve the problem.
In fact, I don't care about the authority.
I want to execute the stored procedure using a SQL SERVER Authentication Account , since my codes run on a linux OS and it is hard to connect to SSIS using a Windows Authentication Account.
so, using EXECUTE AS to change the execution context is accaptable.
The requirement for a Windows Authentication Account makes sense.
I consider that the SSIS executes outside the context of SQL Server and as part of an OS process, which means that a Windows account is necessary in order to deploy a package.
Thanks very much for your help. -
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 -
Please tell how to store jpeg images in SQL Server using NI Database Connectivity Toolset.
http://www.w3schools.com/sql/sql_datatypes.asp
You setup a field as BLOB and store the binary of the picture there. Depending on the database it can be called differently as you can see in the link, in SQL server there's even a Image datatype.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV -
MCTS 70-466 Implementing Data Models and Reports with Microsoft SQL Server 2012
I am searching for training kit for Exam 70-466 (Implementing Data Models and Reports with Microsoft SQL Server 2012) but I think is not published yet. I was expecting its release in Jan or Feb 2014. Would any one can tell me its release date or any place
where I can find this book.
Thanks
Hi Azhar lqbal Gondal,
According to your description, since the issue regards training and certification,
I suggest you post the question in the Learning forums at
http://social.technet.microsoft.com/Forums/en-US/home?category=learning. It is appropriate and more experts will assist you. If you have a specific technical question about Microsoft SQL Server,
you can visit and post your question on the SQL Server Forum.
There is some detail about Exam 70-466 Implementing Data Models and Reports with Microsoft SQL Server 2012, you can review the following articles.
Exam content can be found here:
http://www.microsoft.com/learning/en-us/exam-70-466.aspx
http://borntolearn.mslearn.net/certification/database/w/wiki/525.466-implementing-data-models-and-reports-with-microsoft-sql-server-2012.aspx#fbid=Mn-t6aRhs-H
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support -
Problem with NW04s SR2 installation with MS SQL Server 2000 SP4
Im 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 JainHi 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! -
Oracle Connectivity with MS SQL Server. ORA-00972: identifier is too long
I have linked Oracle Database with MS SQL Server using HS and DB Link.
DB Link Script:
CREATE DATABASE LINK "FCHH"
CONNECT TO SA
IDENTIFIED BY <PWD>
USING 'LISTENER_FCHH';
Links tested successfully.
Now "SA" user in Microsoft SQL Server has multiple databases i.e. Master,SecurePerfect,SecurePerfectHistory. when I try following command
select * from "SecurePerfectHistory.DBO.BadgeHistoryTable"@FCHH
ORA-00972: identifier is too longORA-00972: identifier is too long
Cause: An identifier with more than 30 characters was specified.
Action: Specify at most 30 charactersAman....
Maybe you are looking for
-
How do I access notes on an iPod Touch with a broken home button?
Hey guy, I have an older iPod Touch, and I am trying to gain access to about 800 quotes I had in the notes. The iPod let me get the first (latest) four, then blacked and exited the notes app. Now, it will no longer work, unless I try to add a new no
-
Ok i work at a military base and there were iPod touch's given out to some units and I have found one and would like to return it but don't know the owner so is there a way to track a name with the serial number? Or how can I find out who owns it?
-
Need drivers for Labveiw 8.6 for compumotor 6k8 controllor
I need a compumotor 6k8 driver for labveiw 8.6. The parker Hannifin website offers a Labview driver, but it dates to Labview 5.1. There are instructions on the National Instruments website for converting the driver to the form required for LV 6.1, bu
-
Add RAC database as a target for EMC 12c
Hello, I have installed Enterprise manager 12c on Host 1 Redhat linux 5.5 We have already installed a RAC database 2 nodes on Host 2 and Host 3 ; RAC version 11.2.0.3 on Redhat linux 5.5. I am planning to add the RAC database to be monitored by Enter
-
Running FCP 5.0.4 on Intel MacBook Pro??
I'm working with a partner across the continent on an HDV project. He is working on a G5 with FCP 5.0.4. I'm on Intel machines here. We are working with identical (media) drives. He sends me his work project. When I run it on my Intel system it looks