Backup and Restore older version of Geoserver 2.6 - postgis

I am currently still running Geoserver version 2.6 and would like to find tools to backup and restore. is there any recommended tools or ways?

Upgraded the geoserver to 2.16 and there is a plugin where I could backup and restore the configuration I did in the Geoserver.

Related

What is the last version of flyway community edition that supported MySQL 5.7

I have been using flyway community edition version 5.2.3 for a while now. We just recently tried to upgrade flyway to version 8.2. After upgrading to version 8.2 the execution against MySQL 5.7 is throwing an error stating
"ERROR: Flyway Teams Edition or MySQL upgrade required: MySQL 5.7 is
no longer supported by Flyway Community Edition, but still supported
by Flyway Teams Edition."
My question is what was the last version of the flyway community edition that supported MySQL 5.7?
Flyway Community Edition 8.0.0-beta1 dropped support for databases older than 5 years, including MySQL 5.7.
The minimum supported version of MySQL was increased from 5.7 to 8.0 in this commit, which was introduced in Flyway 8.0.0-beta1.
Currently, the latest community edition version that supports MySQL 5.7 is Flyway 7.15.0.
Just download old version of flyway manually from the website and install it.
Tried installing it from brew using various method, it doesn't work for flyway.

Where can I download the Sybase ASE 12.5 installer?

I need to test a project working on this version of sybase. I have searched for the installer on the sap website but it seems that it is no longer available for download in the developer version.
Where can I find it?

How to update Oracle DB version from 11.2.0.1.0 to 11.2.0.2.0?

I have installed Oracle Database 11.2.0.1.0 in my Windows 10 desktop PC with the installation files from official site link.
Is it possible to update this to 11.2.0.2.0 ?
I'm asking this because our staging server uses 11.2.0.2.0 so I'd like to match the version.
Thanks.
Normally if you have an Oracle support account you can download a CPU to upgrade. But if you don't, I would suggest to follow this link : http://mydbspace.com/?p=104 ( although is Linux, the operative is more or less the same )
It explains very well the steps, nevertheless, are you aware that 11g is already unsupported. You should try to use a newer version.
Rergards

Configure Liferay 7.0 and WIldfly with Oracle

I have a doubt regarding LIferay 7.0 and Wildfly. I recently found a method to integrate Oracle DB with Liferay but, at least in the example and on my attempts to try it, when I start Wildfly with Liferay it keeps telling me "Unsupported Database Oracle".
The tutorial I followed was this one: https://www.dontesta.it/blog/en/2016/04/13/liferay-7-ce-how-to-add-support-for-oracle-db/
Is that only supported for Tomact? (Like in the example in that tutorial).
Thanks in advance.
The Oracle driver for Liferay 7 CE also works for the bundle with wildfly.
The procedure is very simple:
Build the Oracle Driver for Liferay (by following the guide liferay-portal-oracledb-support)
Download JDBC Oracle driver
Copy JDBC Driver in $LIFERA_HOME/wildfly-10.0.0/modules/com/liferay/portal/main/
Add JDBC Driver ojdbc7.jar as resource in module.xml ($LIFERA_HOME/wildfly-10.0.0/modules/com/liferay/portal/main/)
Copy jar (liferay-portal-oracledb-support-1.0-SNAPSHOT.jar) of the Oracle Driver for Liferay in $LIFERAY_HOME/wildfly-10.0.0/standalone/deployments/ROOT.war/WEB-INF/lib/
Start Liferay
By following the above steps you should be able to install successfully Liferay 7, also you can see this tutorial Liferay 7 Wildfly: How to add support for Oracle DB
I point out the project https://github.com/amusarra/liferay-portal-database-all-in-one-support which groups the support for the three commercial databases for versions 7.0, 7.1 and 7.2 of Liferay.
This project add support to the Oracle Database, SQL Server and IBM DB2 database. Liferay has performed refactorting the code so that it is possible and easy to add support for databases no longer supported OOTB (out-of-the-box). The last version (1.1.4) of the driver works with the Liferay 7.2.1 CE GA2.
You can download the latest version binary jar from Maven Central Repository liferay-portal-database-all-in-one-support (https://search.maven.org/#search%7Cga%7C1%7Cit.dontesta), by doing so you can avoid doing the build.
I invite you to read the article How to build a Docker Liferay 7.2 image with the Oracle Database support (https://www.dontesta.it/en/2019/08/21/how-to-build-a-docker-liferay-7-2-image-with-the-oracle-database-support/) which may be interesting for you.

How do I upgrade the database used by teamcity?

I'm trying to upgrade from teamcity 6.5 to 7.1.4a.
I get into maintenance mode at startup where it helpfully informs me that there is a :
Version mismatch: Configuration version is 544 but Database version is 454.
Data Directory
Directory path: /opt/TeamCity-7.1.4a/.BuildServer exists
Database properties file exists
Internal database file exists
Database
Database type: ORACLE
Database connection URL: **
Server: Oracle Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning and Automatic Storage Management options
Server version: 11.2
Driver: Oracle JDBC driver 11.2.0.1.0
Driver version: 11.2
Versions
Software version: 544
Data directory version: 544
Database version: 454
All handy information, but how do I actually upgrade it. A google seems to indicate I should hit the 'upgrade' button. The problem being there isn't one.
So how do I actually upgrade it?
That issue happens with mismatch version of external database. In my case help update and restore Teamcity:
Upgrading from 8.1.6 to 9.0.1, TeamCity 9.0.1 will ask to upgrade drivers to the latest version 5.1. If the MySQL server version is 5.5 or newer, the JDBC driver version should be 5.1.23 or newer.
Upgrade to: Connector/J 5.1.34; Teamcity 9.0; MySQL 5.6.22 (MySQL 5.0.33+, 5.1.49+, 5.5+ (Please note that due to bugs in MySQL, versions 5.0.20, 5.0.22 and 5.1 up to 5.1.34 are not compatible with TeamCity))
Have you seen this Configuration version is XXX but Database version is YYY
One of the solution is to drop all the tables in the databases.

Resources