I have a NEW server for Servoy (dual 3.6 GHz!, four gigs of ram!) . I want to move by db’s especially my repositoy db to the new server.
How does one do this safely? (Moving one out and the other in to the db folder is not the answer).
Thanks in advance!
Providence1:
Moving one out and the other in to the db folder is not the answer.
Eh…why not ?
Yes, you only have to copy your servoy folder! (and make sure java sdk installed) and your done! 
I’m trying to just move the repository and it’s not working…
I get the cannot connect error… (I dump the log too so it’s rebuilt!)…
Move the original repository back (the one from the fresh install)…
And it’s fine…
I need that production server repository and all the juicy info it has inside it’s belly…
moving the repository only, does’nt make sense!
you have to move your other tables too.
and also, you sybase.config file (where all the started databases are in)
and the servoy.properties file, (where all database entries are in)
or else you get mixed up!
And, don’t forget the .log files (if any)
Can’t I just rebuild the sybase.config file from scratch, let the servoy.properties build itself after I add all the database connections and the actual databases themselves, and have the .log files rebuld themselves after launch the first time?
To let Sybase create a new .log file you need to launch Sybase with the -f parameter. (See Sybase manual for more info on this option)
If you don’t do this first then the database won’t open because it expects a log file and the Sybase process will ‘fail’ on startup.
Ofcourse you can change the database setting (with Sybase Central) so that it won’t use a log file but that is not recommended unless you don’t care about possible data loss.
Next is to make sure your custom databases are added to the sybase.config file or else they won’t be opened when the Sybase process launches.
Servoy.properties holds not only your database connections but also your license information (and more). So yes you can set it all again but when you already have a working properties file what is easier than copying it over to the new machine ?
So in short. Nothing is ‘rebuild’ by itself.
Copying over the working files is the easiest way.
Hope this explains things.
If Servoy doesn’t launch after you move then most probably you moved the sybase files while sybase was still running. Sybase does not like this as a transactional database and will refuse to startup until you tell it which transactions should be committed or rolled back. To move your servoy install to another follow the following three steps:
Optional
2.1 delete .log files in database folder
2.2 install servoy/sybase as a service (see docs for details)
Tried both ways. Prefer the clean install better. Still getting can’t connect to a database that easily connects on the other server. (Yes, all services are disabled on the other server).
Getting a 1067 error when trying to start the Servoy service under services in Winblows Administration Tools.
If you are connecting to a database that is sybase based and you get an error: check the sybase logfile.
If you are connecting to a different database: is the driver installed?
What does your servoy logfile say?
Sybase log file:
I. 01/01 08:02:21. Cache size adjusted to 39436K
I. 01/01 08:31:57. Cache size adjusted to 41016K
I. 01/01 08:40:07. Cache size adjusted to 40524K
I. 01/01 09:06:40. Cache size adjusted to 36668K
I. 01/01 20:15:26. Cache size adjusted to 28868K
I. 01/01 20:16:27. Cache size adjusted to 28868K
I. 01/01 20:17:29. Cache size adjusted to 28868K
I. 01/01 20:18:30. Cache size adjusted to 28868K
I. 01/01 20:19:31. Cache size adjusted to 28868K
I. 01/01 20:20:33. Cache size adjusted to 28868K
I. 01/01 20:21:34. Cache size adjusted to 28868K
I. 01/01 20:22:35. Cache size adjusted to 28872K
I. 01/03 10:24:23. Cache size adjusted to 46584K
I. 01/03 10:25:23. Cache size adjusted to 50964K
I. 01/03 10:27:23. Cache size adjusted to 42808K
I. 01/03 10:28:23. Cache size adjusted to 40752K
I. 01/03 10:29:23. Cache size adjusted to 40452K
I. 01/03 10:33:24. Cache size adjusted to 39024K
I. 01/03 10:34:24. Cache size adjusted to 39972K
I. 01/03 10:35:24. Cache size adjusted to 39964K
I. 01/03 10:36:24. Cache size adjusted to 32108K
I. 01/03 10:41:24. Cache size adjusted to 30304K
I. 01/03 10:51:25. Cache size adjusted to 37268K
I. 01/03 11:02:25. Cache size adjusted to 37108K
I. 01/03 11:03:26. Cache size adjusted to 36060K
I. 01/03 11:11:26. Cache size adjusted to 33028K
I. 01/03 11:14:28. Cache size adjusted to 32292K
I. 01/03 12:39:45. Cache size adjusted to 26076K
I. 01/03 12:40:45. Cache size adjusted to 23896K
I. 01/04 00:44:40. Cache size adjusted to 19532K
I. 01/04 00:45:41. Cache size adjusted to 19524K
I. 01/04 00:47:41. Cache size adjusted to 19528K
I. 01/04 00:48:42. Cache size adjusted to 19524K
I. 01/04 06:20:08. Connection terminated abnormally; client socket shut down
I. 01/04 06:20:08. Connection terminated abnormally; client socket shut down
I. 01/04 06:20:08. Connection terminated abnormally; client socket shut down
I. 01/04 06:20:08. Connection terminated abnormally; client socket shut down
I. 01/04 06:20:08. Connection terminated abnormally; client socket shut down
I. 01/04 06:20:08. Connection terminated abnormally; client socket shut down
I. 01/04 06:20:08. Connection terminated abnormally; client socket shut down
I. 01/04 06:20:09. Connection terminated abnormally; client socket shut down
I. 01/04 06:20:09. Connection terminated abnormally; client socket shut down
Servoy log file:
2006-01-04 07:23 : Loading servoy.properties from C:\Program Files\Servoy\servoy.properties
2006-01-04 07:23 : Loading - Done
2006-01-04 07:23 : Final get connection failure for server repository_server in 6 times
2006-01-04 07:23 : org.apache.commons.dbcp.DbcpException: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:85)
at com.servoy.j2db.persistence.datasource.n.createConnection(Unknown Source)
at com.servoy.j2db.persistence.datasource.r.makeObject(Unknown Source)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:816)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:110)
at com.servoy.j2db.persistence.datasource.i.getConnection(Unknown Source)
at com.servoy.j2db.persistence.Server.getConnection(Unknown Source)
at com.servoy.j2db.persistence.Server.testConnection(Unknown Source)
at com.servoy.j2db.develop.J2DBDeveloper.cx(Unknown Source)
at com.servoy.j2db.develop.J2DBDeveloper.dataBaseInit(Unknown Source)
at com.servoy.j2db.develop.J2DBDeveloper.for(Unknown Source)
at com.servoy.j2db.develop.J2DBDeveloper.main(Unknown Source)
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.servoy.j2db.startup.Bootstrap.main(Bootstrap.java:119)
at Servoy.main(Servoy.java:28)
Caused by: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:487)
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:723)
at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3071)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:394)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:218)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:195)
at com.sybase.jdbc2.jdbc.SybConnection.(SybConnection.java:174)
at com.sybase.jdbc2.jdbc.SybConnection.(SybConnection.java:126)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:83)
… 17 more
2006-01-04 07:23 : Final get connection failure for server contact_mgmt in 1 times
2006-01-04 07:23 : org.apache.commons.dbcp.DbcpException: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:85)
at com.servoy.j2db.persistence.datasource.n.createConnection(Unknown Source)
at com.servoy.j2db.persistence.datasource.r.makeObject(Unknown Source)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:816)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:110)
at com.servoy.j2db.persistence.datasource.i.getConnection(Unknown Source)
at com.servoy.j2db.persistence.Server.getConnection(Unknown Source)
at com.servoy.j2db.persistence.Server.testConnection(Unknown Source)
at com.servoy.j2db.develop.q$2.run(Unknown Source)
at com.servoy.j2db.util.ap.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:487)
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:723)
at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3071)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:394)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:218)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:195)
at com.sybase.jdbc2.jdbc.SybConnection.(SybConnection.java:174)
at com.sybase.jdbc2.jdbc.SybConnection.(SybConnection.java:126)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:83)
… 10 more
2006-01-04 07:24 : Final get connection failure for server contact_mgmt in 1 times
2006-01-04 07:24 : org.apache.commons.dbcp.DbcpException: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:85)
at com.servoy.j2db.persistence.datasource.n.createConnection(Unknown Source)
at com.servoy.j2db.persistence.datasource.r.makeObject(Unknown Source)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:816)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:110)
at com.servoy.j2db.persistence.datasource.i.getConnection(Unknown Source)
at com.servoy.j2db.persistence.Server.getConnection(Unknown Source)
at com.servoy.j2db.persistence.Server.testConnection(Unknown Source)
at com.servoy.j2db.develop.q$2.run(Unknown Source)
at com.servoy.j2db.util.ap.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:487)
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:723)
at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3071)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:394)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:218)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:195)
at com.sybase.jdbc2.jdbc.SybConnection.(SybConnection.java:174)
at com.sybase.jdbc2.jdbc.SybConnection.(SybConnection.java:126)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:83)
… 10 more
log says it can’t connect to the repository server, this means that the repository connection as defined in your preferences is not running or can’t be connected.
I know, but the fresh install of Servoy sees the repository.
When I copy the entire servoy development folder over (as I have done about forty times in the past) I’m getting that error. Yet the very same Servoy Dev folder works on my other servers, just not on the one I’m trying to set up as the new servoy server.
The dbsrv9 does launch and says, servoy_repository.
What am I not understanding here?
Are you sure there was no sybase running when launched the copied over version? Is there maybe a firewall blocking the sybase port?