Below is the error message that i have encountered.

I am using Java version 7.

Also tried installing the previous versions as well.

But when i check the connection using the ODBS data source administrator i was able to connect the server.

!ENTRY com.sap.ndb.studio.navigator 4 1 2014-06-24 00:25:17.142

!MESSAGE HDB skvk.vm.cld.sr 00 (SYSTEM) Error while refreshing system

!SUBENTRY 1 com.sap.ndb.studio.navigator 4 0 2014-06-24 00:25:17.142

!MESSAGE SAPControl request failed

!STACK 0

com.sap.ndb.studio.sapcontrol.SAPControlException: SAPControl request failed

     at com.sap.ndb.studio.sapcontrol.operations.SAPControlOperation.execute(SAPControlOperation.java:118)

     at com.sap.ndb.studio.sapcontrol.SAPControl.getInstanceProperties(SAPControl.java:507)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.executeTrySAPControl(SAPSystemObjectUpdate.java:147)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:79)

     at com.sap.ndb.studio.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:73)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperation.execute(DataModelOperation.java:70)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperationQueue$DataModelOperationThread.run(DataModelOperationQueue.java:99)

Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed

     at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(Unknown Source)

     at com.sap.ndb.studio.sapcontrol.operations.SAPControlOperation.execute(SAPControlOperation.java:94)

     ... 6 more

Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed

     at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post(Unknown Source)

     ... 8 more

Caused by: java.net.SocketException: Connection reset

     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

     at java.lang.reflect.Constructor.newInstance(Unknown Source)

     at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)

     at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)

     at java.security.AccessController.doPrivileged(Native Method)

     at sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source)

     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)

     at java.net.HttpURLConnection.getResponseCode(Unknown Source)

     ... 9 more

Caused by: java.net.SocketException: Connection reset

     at java.net.SocketInputStream.read(Unknown Source)

     at java.net.SocketInputStream.read(Unknown Source)

     at java.io.BufferedInputStream.fill(Unknown Source)

     at java.io.BufferedInputStream.read1(Unknown Source)

     at java.io.BufferedInputStream.read(Unknown Source)

     at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)

     at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)

     at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)

     ... 11 more

!SUBENTRY 1 com.sap.ndb.studio.navigator 4 4 2014-06-24 00:25:17.143

!MESSAGE Database connection is not available. See error log for details.

!STACK 0

com.sap.ndb.studio.jdbc.JDBCConnectionStatus: Database connection is not available. See error log for details.

     at com.sap.ndb.studio.jdbc.JDBCPlugin.createConnection(JDBCPlugin.java:253)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.executeTryJDBC(SAPSystemObjectUpdate.java:268)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:96)

     at com.sap.ndb.studio.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:73)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperation.execute(DataModelOperation.java:70)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperationQueue$DataModelOperationThread.run(DataModelOperationQueue.java:99)

Caused by: com.sap.db.jdbc.exceptions.jdbc40.SQLNonTransientConnectionException: Data receive failed .

     at com.sap.db.jdbc.exceptions.jdbc40.SQLNonTransientConnectionException.createException(SQLNonTransientConnectionException.java:40)

     at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:241)

     at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:203)

     at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateSQLException(SQLExceptionSapDB.java:155)

     at com.sap.db.jdbc.exceptions.ConnectionException.createException(ConnectionException.java:22)

     at com.sap.db.jdbc.ConnectionSapDB.tryReconnect(ConnectionSapDB.java:1631)

     at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:1131)

     at com.sap.db.jdbc.CallableStatementSapDB.sendCommand(CallableStatementSapDB.java:1964)

     at com.sap.db.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:978)

     at com.sap.db.jdbc.CallableStatementSapDB.doParse(CallableStatementSapDB.java:256)

     at com.sap.db.jdbc.CallableStatementSapDB.constructor(CallableStatementSapDB.java:215)

     at com.sap.db.jdbc.CallableStatementSapDB.(CallableStatementSapDBFinalize.java:31)

     at com.sap.db.jdbc.ConnectionSapDB.prepareStatement(ConnectionSapDB.java:1369)

     at com.sap.db.jdbc.trace.log.Connection.prepareStatement(Connection.java:1025)

     at com.sap.db.jdbc.trace.Connection.prepareStatement(Connection.java:413)

     at com.sap.ndb.studio.jdbc.JDBCConnection.initialize(JDBCConnection.java:235)

     at com.sap.ndb.studio.jdbc.JDBCPlugin.createConnection(JDBCPlugin.java:236)

     ... 5 more

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:26:07.869

!MESSAGE Connection on HDB:SKVK.VM.CLD.SR:00:SYSTEM is forced to close. (csns.backup.BackupConnectionHandler$1.call(BackupConnectionHandler.java:116);csns.backup.BackupConnectionHandler$1.call(BackupConnectionHandler.java:1);)

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:26:07.871

!MESSAGE Connection on HDB:SKVK.VM.CLD.SR:00:SYSTEM is forced to close. (csns.catalog.internal.Catalog.isHasPrivilegesForSchemasAvailable(Catalog.java:143);csns.catalog.internal.Catalog.fetchCatalogObjects(Catalog.java:73);csns.catalog.internal.CatalogFolder.fetchChildren(CatalogFolder.java:175);csns.catalog.CatalogWorkbenchAdapter$1.run(CatalogWorkbenchAdapter.java:98);org.eclipse.core.internal.jobs.Worker.run(Worker.java:53);)

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:26:07.873

!MESSAGE Connection on HDB:SKVK.VM.CLD.SR:00:SYSTEM is forced to close. (csns.catalog.command.handlers.CatalogRefresh.execute(CatalogRefresh.java:36);org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290);org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90);org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56);org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243);org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224);org.eclipse.e4.core.contexts.Context)

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:26:07.875

!MESSAGE Connection on HDB:SKVK.VM.CLD.SR:00:SYSTEM is forced to close. (csns.catalog.internal.Catalog.isHasPrivilegesForSchemasAvailable(Catalog.java:143);csns.catalog.internal.Catalog.fetchCatalogObjects(Catalog.java:73);csns.catalog.internal.CatalogFolder.fetchChildren(CatalogFolder.java:175);csns.catalog.CatalogWorkbenchAdapter$1.run(CatalogWorkbenchAdapter.java:98);org.eclipse.core.internal.jobs.Worker.run(Worker.java:53);)

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:26:07.894

!MESSAGE Connection on HDB:SKVK.VM.CLD.SR:00:SYSTEM is forced to close. (csns.modeler.base.NavigatorRepositoryInput.getConnection(NavigatorRepositoryInput.java:28);csns.sdk.repository.provider.newdbrepository.NewDBRepositoryProxyFactory.getRepositoryProxy(NewDBRepositoryProxyFactory.java:21);csns.sdk.repository.provider.newdbrepository.impl.NewDBRepositoryProvider.getProxy(NewDBRepositoryProvider.java:197);csns.sdk.repository.provider.newdbrepository.impl.NewDBRepositoryProvider.checkRepositoryAccessAuthorization(NewDBRepositoryProvider.java:214);csns.sdk.repository.newdbreposi)

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:26:07.896

!MESSAGE Connection on HDB:SKVK.VM.CLD.SR:00:SYSTEM is forced to close. (csns.catalog.internal.Catalog.isHasPrivilegesForSchemasAvailable(Catalog.java:143);csns.catalog.internal.Catalog.fetchCatalogObjects(Catalog.java:73);csns.catalog.internal.CatalogFolder.fetchChildren(CatalogFolder.java:175);csns.catalog.CatalogWorkbenchAdapter$1.run(CatalogWorkbenchAdapter.java:98);org.eclipse.core.internal.jobs.Worker.run(Worker.java:53);)

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:26:07.899

!MESSAGE Connection on HDB:SKVK.VM.CLD.SR:00:SYSTEM is forced to close. (csns.catalog.internal.Catalog.isHasPrivilegesForSchemasAvailable(Catalog.java:143);csns.catalog.internal.Catalog.fetchCatalogObjects(Catalog.java:73);csns.catalog.internal.CatalogFolder.fetchChildren(CatalogFolder.java:175);csns.catalog.CatalogWorkbenchAdapter$1.run(CatalogWorkbenchAdapter.java:98);org.eclipse.core.internal.jobs.Worker.run(Worker.java:53);)

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:26:07.901

!MESSAGE Connection on HDB:SKVK.VM.CLD.SR:00:SYSTEM is forced to close. (csns.navigator.operations.SAPSystemObjectUpdate.executeTryJDBC(SAPSystemObjectUpdate.java:268);csns.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:96);csns.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:73);csns.datamodel.controler.DataModelOperation.execute(DataModelOperation.java:70);csns.datamodel.controler.DataModelOperationQueue$DataModelOperationThread.run(DataModelOperationQueue.java:99);)

!ENTRY com.sap.ndb.studio.backup 4 4 2014-06-24 00:27:01.078

!MESSAGE Could not open connection to 'HDB skvk.vm.cld.sr 00'

!STACK 0

java.util.concurrent.TimeoutException

     at java.util.concurrent.FutureTask.get(Unknown Source)

     at com.sap.ndb.studio.backup.BackupConnectionHandler.openConnection(BackupConnectionHandler.java:122)

     at com.sap.ndb.studio.backup.BackupConnectionHandler.getConnection(BackupConnectionHandler.java:88)

     at com.sap.ndb.studio.backup.BackupWorkbenchAdapter$2.call(BackupWorkbenchAdapter.java:151)

     at com.sap.ndb.studio.backup.BackupWorkbenchAdapter$2.call(BackupWorkbenchAdapter.java:1)

     at java.util.concurrent.FutureTask.run(Unknown Source)

     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

     at java.lang.Thread.run(Unknown Source)

!ENTRY com.sap.ndb.studio.navigator 4 1 2014-06-24 00:27:31.615

!MESSAGE HDB skvk.vm.cld.sr 00 (SYSTEM) Error while refreshing system

!SUBENTRY 1 com.sap.ndb.studio.navigator 4 0 2014-06-24 00:27:31.615

!MESSAGE SAPControl request failed

!STACK 0

com.sap.ndb.studio.sapcontrol.SAPControlException: SAPControl request failed

     at com.sap.ndb.studio.sapcontrol.operations.SAPControlOperation.execute(SAPControlOperation.java:118)

     at com.sap.ndb.studio.sapcontrol.SAPControl.getInstanceProperties(SAPControl.java:507)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.executeTrySAPControl(SAPSystemObjectUpdate.java:147)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:79)

     at com.sap.ndb.studio.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:73)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperation.execute(DataModelOperation.java:70)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperationQueue$DataModelOperationThread.run(DataModelOperationQueue.java:99)

Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed

     at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(Unknown Source)

     at com.sap.ndb.studio.sapcontrol.operations.SAPControlOperation.execute(SAPControlOperation.java:94)

     ... 6 more

Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed

     at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post(Unknown Source)

     ... 8 more

Caused by: java.net.SocketException: Connection reset

     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

     at java.lang.reflect.Constructor.newInstance(Unknown Source)

     at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)

     at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)

     at java.security.AccessController.doPrivileged(Native Method)

     at sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source)

     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)

     at java.net.HttpURLConnection.getResponseCode(Unknown Source)

     ... 9 more

Caused by: java.net.SocketException: Connection reset

     at java.net.SocketInputStream.read(Unknown Source)

     at java.net.SocketInputStream.read(Unknown Source)

     at java.io.BufferedInputStream.fill(Unknown Source)

     at java.io.BufferedInputStream.read1(Unknown Source)

     at java.io.BufferedInputStream.read(Unknown Source)

     at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)

     at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)

     at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)

     ... 11 more

!SUBENTRY 1 com.sap.ndb.studio.navigator 4 4 2014-06-24 00:27:31.616

!MESSAGE Database connection is not available. See error log for details.

!STACK 0

com.sap.ndb.studio.jdbc.JDBCConnectionStatus: Database connection is not available. See error log for details.

     at com.sap.ndb.studio.jdbc.JDBCPlugin.createConnection(JDBCPlugin.java:253)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.executeTryJDBC(SAPSystemObjectUpdate.java:268)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:96)

     at com.sap.ndb.studio.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:73)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperation.execute(DataModelOperation.java:70)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperationQueue$DataModelOperationThread.run(DataModelOperationQueue.java:99)

Caused by: com.sap.db.jdbc.exceptions.jdbc40.SQLNonTransientConnectionException: Data receive failed .

     at com.sap.db.jdbc.exceptions.jdbc40.SQLNonTransientConnectionException.createException(SQLNonTransientConnectionException.java:40)

     at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:241)

     at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:203)

     at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateSQLException(SQLExceptionSapDB.java:155)

     at com.sap.db.jdbc.exceptions.ConnectionException.createException(ConnectionException.java:22)

     at com.sap.db.jdbc.ConnectionSapDB.tryReconnect(ConnectionSapDB.java:1631)

     at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:1131)

     at com.sap.db.jdbc.CallableStatementSapDB.sendCommand(CallableStatementSapDB.java:1964)

     at com.sap.db.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:978)

     at com.sap.db.jdbc.CallableStatementSapDB.doParse(CallableStatementSapDB.java:256)

     at com.sap.db.jdbc.CallableStatementSapDB.constructor(CallableStatementSapDB.java:215)

     at com.sap.db.jdbc.CallableStatementSapDB.(CallableStatementSapDBFinalize.java:31)

     at com.sap.db.jdbc.ConnectionSapDB.prepareStatement(ConnectionSapDB.java:1369)

     at com.sap.db.jdbc.trace.log.Connection.prepareStatement(Connection.java:1025)

     at com.sap.db.jdbc.trace.Connection.prepareStatement(Connection.java:413)

     at com.sap.ndb.studio.jdbc.JDBCConnection.initialize(JDBCConnection.java:235)

     at com.sap.ndb.studio.jdbc.JDBCPlugin.createConnection(JDBCPlugin.java:236)

     ... 5 more

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:38:11.748

!MESSAGE Connection on HDB:SKVK.VM.CLD.SR:00:SYSTEM is forced to close. (csns.navigator.commands.OpenSAPSystemHandler$1$1.call(OpenSAPSystemHandler.java:238);csns.navigator.commands.OpenSAPSystemHandler$1$1.call(OpenSAPSystemHandler.java:1);)

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:38:11.749

!MESSAGE Connection on HDB:SKVK.VM.CLD.SR:00:SYSTEM is forced to close. (csns.backup.BackupConnectionHandler$1.call(BackupConnectionHandler.java:116);csns.backup.BackupConnectionHandler$1.call(BackupConnectionHandler.java:1);)

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:38:11.750

!MESSAGE Connection on HDB:SKVK.VM.CLD.SR:00:SYSTEM is forced to close. (csns.navigator.operations.SAPSystemObjectUpdate.executeTryJDBC(SAPSystemObjectUpdate.java:268);csns.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:96);csns.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:73);csns.datamodel.controler.DataModelOperation.execute(DataModelOperation.java:70);csns.datamodel.controler.DataModelOperationQueue$DataModelOperationThread.run(DataModelOperationQueue.java:99);)

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:38:15.378

!MESSAGE Connection on HDB:BRSL.VM.CLD.SR:00:SYSTEM is forced to close. (csns.backup.BackupConnectionHandler$1.call(BackupConnectionHandler.java:116);csns.backup.BackupConnectionHandler$1.call(BackupConnectionHandler.java:1);)

!ENTRY com.sap.ndb.studio.jdbc 4 4 2014-06-24 00:38:15.384

!MESSAGE Connection on HDB:BRSL.VM.CLD.SR:00:SYSTEM is forced to close. (csns.navigator.operations.SAPSystemObjectUpdate.executeTryJDBC(SAPSystemObjectUpdate.java:268);csns.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:96);csns.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:73);csns.datamodel.controler.DataModelOperationJob.run(DataModelOperationJob.java:70);org.eclipse.core.internal.jobs.Worker.run(Worker.java:53);)

!ENTRY com.sap.ndb.studio.backup 4 4 2014-06-24 00:39:08.472

!MESSAGE Could not open connection to 'HDB skvk.vm.cld.sr 00'

!STACK 0

java.util.concurrent.TimeoutException

     at java.util.concurrent.FutureTask.get(Unknown Source)

     at com.sap.ndb.studio.backup.BackupConnectionHandler.openConnection(BackupConnectionHandler.java:122)

     at com.sap.ndb.studio.backup.BackupConnectionHandler.getConnection(BackupConnectionHandler.java:88)

     at com.sap.ndb.studio.backup.BackupWorkbenchAdapter$2.call(BackupWorkbenchAdapter.java:151)

     at com.sap.ndb.studio.backup.BackupWorkbenchAdapter$2.call(BackupWorkbenchAdapter.java:1)

     at java.util.concurrent.FutureTask.run(Unknown Source)

     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

     at java.lang.Thread.run(Unknown Source)

!ENTRY com.sap.ndb.studio.navigator 4 1 2014-06-24 00:39:38.422

!MESSAGE HDB skvk.vm.cld.sr 00 (SYSTEM) Error while refreshing system

!SUBENTRY 1 com.sap.ndb.studio.navigator 4 0 2014-06-24 00:39:38.422

!MESSAGE SAPControl request failed

!STACK 0

com.sap.ndb.studio.sapcontrol.SAPControlException: SAPControl request failed

     at com.sap.ndb.studio.sapcontrol.operations.SAPControlOperation.execute(SAPControlOperation.java:118)

     at com.sap.ndb.studio.sapcontrol.SAPControl.getInstanceProperties(SAPControl.java:507)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.executeTrySAPControl(SAPSystemObjectUpdate.java:147)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:79)

     at com.sap.ndb.studio.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:73)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperation.execute(DataModelOperation.java:70)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperationQueue$DataModelOperationThread.run(DataModelOperationQueue.java:99)

Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed

     at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(Unknown Source)

     at com.sap.ndb.studio.sapcontrol.operations.SAPControlOperation.execute(SAPControlOperation.java:94)

     ... 6 more

Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed

     at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post(Unknown Source)

     ... 8 more

Caused by: java.net.SocketException: Connection reset

     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

     at java.lang.reflect.Constructor.newInstance(Unknown Source)

     at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)

     at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)

     at java.security.AccessController.doPrivileged(Native Method)

     at sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source)

     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)

     at java.net.HttpURLConnection.getResponseCode(Unknown Source)

     ... 9 more

Caused by: java.net.SocketException: Connection reset

     at java.net.SocketInputStream.read(Unknown Source)

     at java.net.SocketInputStream.read(Unknown Source)

     at java.io.BufferedInputStream.fill(Unknown Source)

     at java.io.BufferedInputStream.read1(Unknown Source)

     at java.io.BufferedInputStream.read(Unknown Source)

     at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)

     at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)

     at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)

     ... 11 more

!SUBENTRY 1 com.sap.ndb.studio.navigator 4 4 2014-06-24 00:39:38.422

!MESSAGE Database connection is not available. See error log for details.

!STACK 0

com.sap.ndb.studio.jdbc.JDBCConnectionStatus: Database connection is not available. See error log for details.

     at com.sap.ndb.studio.jdbc.JDBCPlugin.createConnection(JDBCPlugin.java:253)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.executeTryJDBC(SAPSystemObjectUpdate.java:268)

     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:96)

     at com.sap.ndb.studio.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:73)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperation.execute(DataModelOperation.java:70)

     at com.sap.ndb.studio.datamodel.controler.DataModelOperationQueue$DataModelOperationThread.run(DataModelOperationQueue.java:99)

Caused by: com.sap.db.jdbc.exceptions.jdbc40.SQLNonTransientConnectionException: Data receive failed .

     at com.sap.db.jdbc.exceptions.jdbc40.SQLNonTransientConnectionException.createException(SQLNonTransientConnectionException.java:40)

     at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:241)

     at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:203)

     at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateSQLException(SQLExceptionSapDB.java:155)

     at com.sap.db.jdbc.exceptions.ConnectionException.createException(ConnectionException.java:22)

     at com.sap.db.jdbc.ConnectionSapDB.tryReconnect(ConnectionSapDB.java:1631)

     at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:1131)

     at com.sap.db.jdbc.CallableStatementSapDB.sendCommand(CallableStatementSapDB.java:1964)

     at com.sap.db.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:978)

     at com.sap.db.jdbc.CallableStatementSapDB.doParse(CallableStatementSapDB.java:256)

     at com.sap.db.jdbc.CallableStatementSapDB.constructor(CallableStatementSapDB.java:215)

     at com.sap.db.jdbc.CallableStatementSapDB.(CallableStatementSapDBFinalize.java:31)

     at com.sap.db.jdbc.ConnectionSapDB.prepareStatement(ConnectionSapDB.java:1369)

     at com.sap.db.jdbc.trace.log.Connection.prepareStatement(Connection.java:1025)

     at com.sap.db.jdbc.trace.Connection.prepareStatement(Connection.java:413)

     at com.sap.ndb.studio.jdbc.JDBCConnection.initialize(JDBCConnection.java:235)

     at com.sap.ndb.studio.jdbc.JDBCPlugin.createConnection(JDBCPlugin.java:236)

     ... 5 more

I have 2 groups of users user_group1, user_group2 and also two different schemas schema_group1,schema_group2 containing the same table names with a different content.

Now, i have to write a stored procedure which takes user name as input and depending on which group the user belongs to, i want to work with table in that user_group schema.  i.e.(if user_group1 then "schema_group1"."table". if user_group2 then "schema_group2"."table" )

i tried to set schema using dynamic sql but it seems that the schema is changing only after the end of the stored procedure.

Hi all,

I recently updated my HANA Studio from SP7 to SP8 and recieve now the following popup message every time I start the IDE:

The problem is, that the SAPJCO3 version is the last one (3.0.11) I can find in service marketplace and the dll file has indeed the 720.612 version. So the question is, where I can find the newer dll? Or is this a bug in the HANA Studio SP8, which has a dependency to a jco version, which is not released yet?

Thanks and best regards,

Artem

HANA experts,

I wanted to pose a question that our developers are pondering here. In summary, does the number of fields defined on a given Analytical View affect overall performance?

Here's a hypothetical scenario to illustrate:

Given a existing columnar HANA table T existing with 100 fields and loaded with 100,000,000 rows of data.

1. Create an analytical view AV1 over the above table T but w/5 high level fields defined (company code, cost center, year, quantity, amount). Create calculation view CV1 over AV1 w/5 fields and 5 calculated measures. In total CV1 has 10 fields total now.

2, Create an analytical view AV2 over entire table T w/100 fields defined. Create calculation view CV2 over AV2 w/100 fields and 5 calculated measures defined the same as the ones in CV1. In total CV2 has 105 fields total now.

Now the question is if query Q1 is run over CV1 with those 10 fields defined and a query Q2 run over CV2 with equivalent same 10 fields as CV1, will the performance of Q1 = Q2, even though CV2 has a much wider definition?

Keep in mind both CVs are ultimately pulling from same base table with 100 fields acros and 100,000,000 rows of data.

From the HANA literature out there, I'm led to believe that above scenario would result in the same performance of Q1 and Q2 due to "pruning/object stripping". However, as sometimes we've seen, theory doesn't necessarily match reality so I wanted to gauge your opinions.

If it turns out Q1=Q2, the thought is to go ahead and define it as AV2 and CV2 to give the most reporting flexibility over the Calculation View.

Best Regards,

Bruce

Hi,

I can successfully execute the following SQL statement within the Hana system SQL console:

alter sequence "MISSIONCONTROL"."hpl.missioncontrol.data::missionCockpitLogId" RESTART WITH 1;

I have an SQL stored procedure that I execute to clear some load tables as I repeatedly perform some tests:

CREATE PROCEDURE reset_missionLogs_sql ( )

  LANGUAGE SQLSCRIPT

  SQL SECURITY INVOKER AS    

  --DEFAULT SCHEMA <schema>

BEGIN

/*****************************

  Write your procedure logic

*****************************/

  delete from "MISSIONCONTROL"."hpl.missioncontrol.data::mission";

  delete from "MISSIONCONTROL"."hpl.missioncontrol.data::missionCockpitLog";

END;

I wish to incorporate the aforementioned ALTER sequence statement within this procedure so that in addition to the table contents being cleared the associated sequences for primary keys are reset to 1.

The issue is that the SQLScript editor is not happy when I place the ALTER SEQUENCE statement, indicating it is "incorrect or or misplaced":

Is ALTER SEQUENCE supported?  Most grateful for pointing out the (probably) obvious to me.  Many thanks.

Hi Gurus

Can we replicate ECC hierarchies in SAP HANA?

As per my understanding it is not possible and have to recreate them in Studio.

If yes, please explain the process..we are using SLT to replicate data from ECC to HANA

Thanks,

Nikhil

I am new to SAP and HANA Studio, can anyone please guide me on how to implement standard cost center/profit center hierarchy in HANA Studio database using SETLEAF,SETNODE AND SETHEADER? I will need to implement this in attribute view and connect it to GLPCA for GR55 profit and Loss statement report.

Hi Experts,

I need more clarity before entering into HANA development. pls answer my questions

What is HANA Application development?

What is the use of build and deploy the next-generation real-time applications on top of HANA and Why it's so needed today?

What HANA application development road map says for now and future?

Where i can find out HANA development architecture?

What makes it different than existing?

What are the language does it support?

Does it support only web based application?

What are the basic skill required to build an Application?

Regards,

VasanthS

Hello,

I am trying to get data from HANA Virtual Data Model (VDM) from MDX connection in MS Excel. The VDM Views and models are visitble after the connection is successfully made.

But when I try to fetch the data, I get the following error:

"Creation of Temporary Table "BIMC_SETS" is not possible".

Can someone let me know how to resolve this?

Best regards,

Akhil

Dear collegues,

I am running SAP HANA 1.00.72.00.388670 in HANA Cloud. I am trying to migrate the data from SQL Server to SAP HANA.

The IDENTITY value support is enabled. I am trying to import data from csv file to a table.

The table has such structure:

     CREATE COLUMN TABLE "TEST_IMPORT" ("ID" integer  NOT NULL primary key  generated always as IDENTITY, "VALUE" real NULL);

The peace of data has such view:

ID,VALUE

1,1

2,2

3,3

4,4

5,5

6,6

7,7

8,8

When I start an import process it asks me to define the dependences, as it requires to point the columns from my datafile to columns in the table. Certainly I cannot link a "ID" field because it is generated automatically.

I`ve tried another example.

Created a table:

     CREATE COLUMN TABLE "TEST_IMPORT" ("ID" integer  NOT NULL primary key, "VALUE" real NULL);

Imported data from previous example.

After I tried to alter the table to asign the IDENTITY property. However I`ve got an error:

     "Could not execute 'alter table "TEST_IMPORT" ALTER ("ID" integer NOT NULL primary key generated always as IDENTITY)' in 45 ms 753 µs .

     SAP DBTech JDBC: [7] (at 34): feature not supported: cannot modify column to identity column: ID: line 1 col 35 (at pos 34) "

How can I make that import?

Peeps,

I 'm looking at my data and I'm finding something a bit strange with how NOT NULL is treated in HANA.

I run this qry:

select *, 'x'||tcode||'x', length(tcode)

from hanadb.jcds

where objnr = 'NV000115159400000017' and tcode is not null

But you can see that tcode must have something in it ... but I'm not seeing anything there.

I also see in the definition of jcds that is slt'ed from ecc that tcode is defined as not null ... in fact most all the fields slt'ed are defined as not null.

Can someone explain?

Mike

Hi,

I already have the SAP HANA Rev 72 installed in my AWS instance (instance type m2.4xlarge). It was installed using CAL. How do I upgrade to SAP HANA Rev 80 or to newer versions by using CAL and by using the same AWS instance (if the requirement is the same instance size)? I don't want to lose what I have already created (views, etc.) in previous SAP HANA versions.

Thanks for your help.

Hi ,

I have created a report on HANA. When we execute this report, I observed that there are more than 500 threads running parallely for SQL statement.

HANA is generating lot of JobWorker(plan executor) threads and it is using 99% CPU and all the Memory present in HANA

Can anyone let me know how to limit the runnable threads in HANA for a given SQL statement?

Is there a way to know more about these Threads and as to on what basis does HANA create these threads?

I will be very grateful for your help and advice.

Thanks and Regards,

Shreepad Patil

I could not find documentation on the configuration settings idle_connection_timeout available under Configuration->indexserver.ini->session in hana studio. If someone know where to find such documentation please post back.

I have a situation where this settings is causing issue and would like to know how safe it is to disable it (to set it at -1 like idle_connection_time_application_hdbstudio I guess).

The scenario is that I have an appliation that connect to multiple schemas using only 1 database user. After a connection to the database, I set the current schema to the target schema and expect the connection to stay in that schema. The database connection stay open but sometimes it won't be used for a while. What happened is that hana closed the connection or put it in archive after the idle time so when the connection is to be used, even if it is recreated, it is not in the correct schema and the sql query will fail.

One solution would be to disable this idle connection timeout. I just need the documentation to know if there are other ways to close it.

Tests : I disable the idle_connection_timeout.

If I open the program and it connect to the database then kill it, the connection will be closed in the database.

If I open the program then disconnect the network, will the connection be also killed automatically or the idle_timeout will apply and the connection will stay there stuck for the live of the database ?

I'm following along with the "Create Roles" video in the Native Development Workshop.

After creating the .xsprivileges artifact with the depicted content, the .hdbrole file commits fine, but errors out when trying to activate...

ERROR      PBDemos/MyOData02/data/pbdemoUser.hdbrole

           insufficient privilege: Not authorized at ptime/query/checker/query_check.cc:2547

ERROR      PBDemos/MyOData02/data/pbdemoUser.hdbrole

           A transaction rollback may have left the object in an inconsistent state.

ERROR                 exception 40183:

repository/base/activation/activator.cpp:884

Transaction rollback detected. Activation failed.

Hello,

I am trying to build a VB.Net program to connect to an SAP HANA Server. I have installed SAP HANA Client (both 32-bit and 64-bit) and I am running on a 64-bit Windows 7 OS.

I created a System DSN and wrote a program in VB.Net to access the ODBC Connection and that is failing.

According to page 782 of the SAP HANA Developer Guide (http://help.sap.com/hana/SAP_HANA_Developer_Guide_en.pdf), when you install the SAP HANA Client, the "SAP.Data.HANA" libraries should be installed - but I am not able to see any of these when I try to add a reference in VB.Net.

It would be great if someone with experience of connecting from .Net to SAP HANA could please share the correct approach.

I just want to connect to a certain schema and run some INSERT and SELECT commands on the HANA Database for the moment.

Thanks in advance for your help,

Cheers,

Sudarshan

Peeps,

I ran a query in the hana sql window and it had these processing results:

successfully executed in 101 ms 821 µs  (server processing time: 67 ms 263 µs)

Fetched 1000 row(s) in 250 ms 602 µs (server processing time: 0 ms 982 µs)

I ran another query  and it had these processing results:

successfully executed in 117 ms 168 µs  (server processing time: 80 ms 906 µs)

Fetched 1000 row(s) in 184 ms 352 µs (server processing time: 0 ms 722 µs)

Can it be assumed that the one with the FASTER EXECUTION TIME -> 101 ms is the fastest or is it the one that FETCHED 1000 ROWS FASTER -> 184 ms?

Also, when viewing the Vis Explan Plan, I'm assumming the one with the lowest ESTIMATED COST runs the fastest - TRUE?

Mike

We've some special characters in the fields (like '#' ), and because of this the client side ODataModel /JSON parsing is breaking when ever the data has these characters.

Is there anyway to encode this at the HANA server level while exposing the views?

Hola buenas tardes

AL momento de crear una factura de cliente, me aparece el siguiente mensaje de error:

Could not commit transaction: Error -1 detected during transaction '' (ITR1)

Alguien sabe que es lo que puede estar pasando.

He revisado las determinación de cuentas de mayor, por si falta algún dato. al igual que he revisado que el almacén cuente con todas sus cuentas contables configuradas.

Quiero aclarar que esta empresa creada es de prueba con el plan de cuentas que viene por default, por lo que la cree desde cero y no se si me haga falta alguna configuración.

Cabe aclarar que hice una pruebas en la empresa por default, realizando una factura y viendo si afectaba a la tabla ITR1 pero no afecto a esta tabla, por lo que se me hace mas raro el problema.

Otra cosa importante mencionar es que la base de dats que estoy utilizando es HANA, por lo que crear un backup de una base de datos funcionando y restaurar en otra, queda totalmente descartado, debido a que no podemos actualizar la ultima versión de HANA que al parecer trae la funcionalidad antes mencionada.

Alguno de ustedes tiene una solución referente al mensaje de error.

Agradezco su apoyo .

Hi folks,

I am New to SAP,

I wanted to know how we transport the data in implementation projects from development to quality server?

Is it using SE10, se09 or do we have some other technique?

The same in SAP BI, SAP HANA, SAP ABAP

Thanks

Siddhartha