ERROR: Flyway Teams Edition upgrade required: jdbc-secretsmanager is not supported by Flyway Community Edition - flyway

I am using flyway community edition v-7.0.4.
while trying to work it out with AWS jdbc-secretsmanager, ref. https://flywaydb.org/documentation/configuration/secretsManagement#dapr-secret-store, it throughs error ERROR: Flyway Teams Edition upgrade required: jdbc-secretsmanager is not supported by Flyway Community Edition
does AWS secretsmanager only supported for flyway teams which is commercial edition?
Thanks
Tried installing version 9 but have had same issue

Related

Liquibase with Maven using Teradata

I am getting the following error, while running the command: mvn liquibase:update
liquibase.exception.databaseexception:connection could not be created to jdbc:teradata://org.sys.db.com/database=sample_DEV with driver com.teradata.jdbc.TestDriver [Teradata Database] [Terajdbc 16.20.00.00] [Error] [SQLState HY000] Logons are only enabled for user DBC.
We are using maven version:3.6.3, Liquibase version:4.3.0 and teradata ver:16.20.00.00 with dbchangelog.sql
The same code is working fine for nornal project, i mean without maven.
"com.teradata.jdbc.TestDriver" is not the class name for the Teradata JDBC Driver. The actual class name is "com.teradata.jdbc.TeraDriver".
Version 16.20.00.00 of the Teradata JDBC Driver was not released to the public. That was a pre-release build.
You can download the current supported version of the Teradata JDBC Driver from here:
https://downloads.teradata.com/download/connectivity/jdbc-driver
Here is a link to the Teradata documentation for database error 3055 "Logons are only enabled for user DBC."
https://docs.teradata.com/r/GVKfXcemJFkTJh_89R34UQ/Si5mPxDLg2vugG5MnDbBoQ

IBM Websphere Application Server installer error "Adding zip com.ibm.websphere.IHS.ihsonly_z_dist.all_x_y to repository failed"

While trying to install IBM Websphere Application Server developer edition though IBM Installation Manager, getting following issue:
The following errors were generated while installing.
Adding zip com.ibm.websphere.IHS.ihsonly_z_dist.all_x_y to repository
C:\opt\jas\iap\IMshared failed.
Resumable download failed for:
C:\tmp1\was\IBM\WAS\8.5\repository\native\com.ibm.websphere.IHS.ihsonly_z_dist.all_x_y.zip.
'zip com.ibm.websphere.IHS.ihsonly_z_dist.all_x y' does not exist
I don't find com.ibm.websphere.IHS.ihsonly_z_dist.all_x_y.zip in the installable bundles
Am I missing anything?

Reverse Engineer Fails EF Core Power Tools

System.MissingMethodException: Method not found:
'Microsoft.Extensions.DependencyInjection.IServiceCollection
Microsoft.EntityFrameworkCore.Design.ServiceCollectionExtensions.AddHandlebarsScaffolding(Microsoft.Extensions.DependencyInjection.IServiceCollection,
Microsoft.EntityFrameworkCore.Design.ReverseEngineerOptions,
System.ValueTuple2>[])'.
at
ReverseEngineer20.EfCoreReverseEngineer.GenerateFiles(ReverseEngineerOptions
reverseEngineerOptions) at
EFCorePowerTools.Handlers.ReverseEngineerHandler.d__2.MoveNext() in
C:\projects\efcorepowertools\src\GUI\EFCorePowerTools\Handlers\ReverseEngineerHandler.cs:line
154
Database engine: (SQL Server)
Visual Studio version: (e.g. Visual Studio 2017 15.7.5)
EF Core Powe Tools version: 1.0.604.0
This is fixed in the latest daily build, download instructions here: https://github.com/ErikEJ/EFCorePowerTools#downloadsbuilds

VS 2017 Community ver and VS 2017 Enterprise debug issue: Found conflicts between different versions

I m having 2 version of VS2017 and a mac with latest macOS.
I transfer my Xamarin forms App file from VS2017 enterprise to a machine(more than 3 years old but running win10 pro) with VS2017 Community version. When I debug ( with selecting Android project and VS-android-23 X86 tablet as emulator ) this App in VS2017 Community version , I have no compilation error but have these message:
Found conflicts between different versions of the same dependent assembly
that could not be resolved.
These reference conflicts are listed in the build log when log verbosity is set to detailed.
I could not understand this message. I have no problem running the same app in VS2017 Enterprize ver but I have this error message in VS2017 Community ver.
Update
Click View > Output --> this will show the error
1>Starting deploy VisualStudio_android-23_x86_tablet ...
1>Starting emulator VisualStudio_android-23_x86_tablet ...
1>C:\Users\xxxxx\AppData\Local\Android\ANDROI~1\tools\emulator.EXE -partition-size 512 -no-boot-anim -avd VisualStudio_android-23_x86_tablet -prop monodroid.avdname=VisualStudio_android-23_x86_tablet
1>emulator: ERROR: x86 emulation currently requires hardware acceleration!
1>Please ensure Intel HAXM is properly installed and usable.
1>CPU acceleration status: Please disable Hyper-V before using the Android Emulator. Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.
1>Emulator VisualStudio_android-23_x86_tablet cannot be started.
Please help.

usage:jag java.lang.IndexOutOfBoundsException in wso2 apim 1.10 and DAS 3.1.0

I have followed below procedure for publishing statistics. I have setup in desktop with standalone configurations and no clustering, database is installed.
https://docs.wso2.com/display/AM1100/Publishing+API+Runtime+Statistics+Using+REST+Client
I'm getting below error in the apim logs and not able to see statistcis.
ERROR - usage:jag java.lang.IndexOutOfBoundsException:
Index: 0, Size: 0
ERROR - usage:jag java.lang.IndexOutOfBoundsException:
Index: 0, Size: 0
error i see in statistics page
i have searched old stackoverflow tickets but couldn't find the correct solution. can anybody please help on this
This issue is already reported and you can find the relevant jira in [1]. Please note that WSO2 API Manager 1.10 only supports WSO2 DAS 3.0.X versions. Based on the jira this issue is already fixed in WSO2 DAS 3.1.0. I am not sure why you are getting this in DAS 3.1.0. Anyway, you cannot use DAS 3.1.0 with APIM 1.10 due to other complexities.
The root cause for this issue when you start the server in the daemon mode the Spark variables are not loaded and Spark cluster does not function properly. To avoid this you can start the DAS servers in nohup mode as follows.
nohup ./wso2server.sh &

Resources