cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

database connection issue while exporting data

Go to solution
Former Member

on ‎02-13-2009 9:51 PM

0 Kudos

Hello ,

We are trying to export the portal databse which is on MSCS clustor environment. Database is on MSSQL server 2000. But we have trouble in the initial phase itself while connecting to database using sapinst installer SR3 version. Actully the problem is only on clustor environments. We have exported the in standalone environments it works fine ..

does any one come across this situation in sqlserver clustor environment, please find the log..

<!LOGHEADERSTART/>

<!HELPManual modification of the header may cause parsing problem!/>

<!LOGGINGVERSIONhttp://1.5.3.7185 - 630/>

<!NAMEhttp://UTL_load_usages.log/>

<!PATTERNhttp://UTL_load_usages.log/>

<!FORMATTERcom.sap.tc.logging.TraceFormatter(%24d %7s: %m)/>

<!ENCODINGCp1252/>

<!LOGHEADEREND/>

Feb 12, 2009 4:41:37 PM Info : Successfully parsed!

Feb 12, 2009 4:41:37 PM Info : Executing command Export...

Feb 12, 2009 4:41:37 PM Info : Establishing DB connection...

Feb 12, 2009 4:41:39 PM Path : Exception : The DataBase is down or the connection parameters are wrong: -sid=TP1 -dsn=jdbc/pool/TP1 -ssprops=R:/usr/sap/TP1/SYS/global/security/data/SecStore.properties -ssk=R:/usr/sap/TP1/SYS/global/security/data/SecStore.key -keyphrase=null

java.lang.Exception

at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1141)

at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:413)

at com.sap.exception.BaseException.<init>(BaseException.java:302)

at com.sap.sl.ut.infoprovider.exceptions.UTInfoException.<init>(UTInfoException.java:96)

at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:215)

at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.constructSystemInfo(DataBaseInfoFactory.java:624)

at com.sap.sl.ut.manager.command.Export.executeExportKDB(Export.java:56)

at com.sap.sl.ut.manager.command.Export.execute(Export.java:80)

at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)

at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:60)

at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Caused by: com.sap.sql.log.OpenSQLException: Could not load class com.sap.nwmss.jdbc.sqlserver.SQLServerDriver.

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)

at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:143)

at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)

at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)

at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)

at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:213)

at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.constructSystemInfo(DataBaseInfoFactory.java:624)

at com.sap.sl.ut.manager.command.Export.executeExportKDB(Export.java:56)

at com.sap.sl.ut.manager.command.Export.execute(Export.java:80)

at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)

at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:60)

at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Caused by: java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver

at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)

at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)

at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)

at java.lang.ClassLoader.loadClassInternal(Unknown Source)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Unknown Source)

at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)

... 16 more

caused by

java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver

at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)

at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)

at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)

at java.lang.ClassLoader.loadClassInternal(Unknown Source)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Unknown Source)

at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)

at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)

at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)

at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)

at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:213)

at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.constructSystemInfo(DataBaseInfoFactory.java:624)

at com.sap.sl.ut.manager.command.Export.executeExportKDB(Export.java:56)

at com.sap.sl.ut.manager.command.Export.execute(Export.java:80)

at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)

at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:60)

at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Feb 12, 2009 4:41:39 PM Info : Severe (database) error. Return code: 64

Thanks in Advance..

Surendra

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎02-13-2009 10:15 PM
0 Kudos

The DataBase is down or the connection parameters are wrong: -sid=TP1

1. Check whether all database service is up and running.

2. Check whether correct parameters about the database has been defined in the secure store of the config tool.

3. Make sure all the database resources(datafiles and logfiles) are available. Check it from Cluster Administrator.

Rgds,

SK.

Show replies
Show replies
Former Member
‎02-15-2009 3:44 AM
0 Kudos

Hi Subhadip Kumar

Thank you for ur quick response.

1. Check whether all database service is up and running.

All database service are up and running. Because SAP is working fine I am just performing export for migrating the database to different platform.

2. Check whether correct parameters about the database has been defined in the secure store of the config tool.

All Sec store parameters are fine, other portal wont work. Its a productive system. System is working fine.

3. Make sure all the database resources (datafiles and logfiles) are available. Check it from Cluster Administrator.

All database resources (datafiles and logfiles) are available. Donu2019t have any issue with database or with the cluster.

Thanks,

Surendra

Former Member
‎02-15-2009 4:11 AM
0 Kudos

If you are performing the export operation using SAPInst from node 1....and if any resources resides in node 2....bring them in node1.....and let me know the result.

Rgds,

SK

Former Member
‎02-19-2009 4:59 PM
0 Kudos

Upgraded the jdbc connector from com.sap.nwmss.jdbc.sqlserver.SQLServerDriver

to com.microsoft.sqlserver.jdbc.SQLServerDriver.

And while running sapinst in HA environment we have to use sapinst sapinst_use_hostname=<hostname in CAPS>

Solved the issue exported the portal database from MSSQL server to Oracle. Migration completed.

Thank you for all your valuble suggestions.

Regards,

Surendra

Former Member
‎08-27-2009 4:15 PM
0 Kudos

Hi,

were did you change the jdbc connector?

I am experiencing the same issues.

Regards,

Sebastian

Former Member
‎07-08-2012 4:30 AM
0 Kudos

SAP Note 1145221 provides steps to exchange JDBC Drivers to Microsoft JDBC Drivers.

Answers (0)

Ask a Question