Upgrading a Corda node from CE3.2 to CE4.0 and following these documentation steps:
Running ubuntu#ip-xyz:~$ java -jar tools-database-manager-4.0.jar dry-run -b /opt/corda/
Gives error:
Exporting the current database migrations ...
Failed to create datasource.
Please check that the correct JDBC driver is installed in one of the following folders:
- /opt/corda/drivers
- plugins
- cordapps
Caused By java.nio.file.NoSuchFileException: plugins
2019-05-23 22:24:16,284 Thread-0 WARN Unable to register Log4j shutdown hook because JVM is shutting down. Using SimpleLogger
I have all the required folders in place for drivers, plugins and cordapps and have installed MS SQL drivers mssql-jdbc-6.2.2.jre8.jar.
The "jarDirs" key in the node.conf was hiding the folders required for database migration.
By removing the following lines the database manager tool successfully completed the dry run.
"jarDirs" : [
"plugins",
"cordapps"
]
Related
I am trying to deploy my application built in ASP.Net 4.6.1. So I am using HWC Buildpack.
Below is my manifest.yml
---
applications:
- name: DRSN
random-route: true
memory: 128M
buildpack:
https://github.com/cloudfoundry/hwc-buildpack.git
env:
DOTNET_CLI_TELEMETRY_OPTOUT: 1
DOTNET_SKIP_FIRST_TIME_EXPERIENCE: true
The error that I am receiving is below.
Waiting for API to complete processing files...
Staging app and tracing logs...
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 creating container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 successfully created container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Downloading app package...
Downloading build artifacts cache...
Downloaded build artifacts cache (231B)
Downloaded app package (19.5M)
Failed to compile droplet: Failed to compile droplet: fork/exec /tmp/buildpackdownloads/6c6dca8d638ac0d145d6581f9eb9a96a/bin/compile: permission denied
Exit status 223
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 stopping instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 destroying container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Error staging application: App staging failed in the buildpack compile phase
Can anyone help me resolve this issue? Am I not correct in my manifest.yml? Or is it something else?
I believe that the problem is that you're telling the system to use the HWC buildpack, but at the same time you're not setting the Windows stack (at least based on what info I can see). That means it's going to default to the Linux stack, which I believe is why you're seeing the fork/exec /tmp/buildpackdownloads/... error.
Try adding stack: windows to your manifest.yml or -s windows to your cf push command (for future reference, when you need help always include the full cf push command you're running).
PS: you shouldn't use https://github.com/cloudfoundry/hwc-buildpack.git that is telling the system to grab the master branch in whatever state it's currently in. That's a.) not reproducible and b.) not guaranteed to be in a working state. You should either use the platform provided buildpack names (from cf buildpacks) or append #<branch_or_tag> to the end of the URL so it picks a specific branch. All CF Buildpacks have tags for each release. It's strongly recommended you use a tagged release.
I am trying to create migration schemas for a CorDapp as per the instructions here. I am running the following command:
java -jar corda-tools-database-manager-3.1.jar
--base-directory /opt/User
--create-migration-sql-for-cordapp fnolUseCase.state.FNOLSchema
However, I am getting the following error:
-- 2018-08-22T13:29:23,145Z migration.tool.invoke - Creating database migration
files for schema: fnolUseCase.state.FNOLSchema into /opt/User/migration
Failed to create datasource.
Please check that the correct JDBC driver is installed in one of the following
folders:
- /opt/User/drivers
Caused By java.lang.ClassCastException: fnolUseCase.state.FNOLSchema cannot be cast
to net.corda.core.schemas.MappedSchema
What should I be doing differently?
It seems to be having trouble locating your fnolUseCase.state.FNOLSchema class. Try dropping the schema name from the end of your command. This will cause a migration schema to be created for every schema in your application:
java -jar corda-tools-database-manager-3.1.jar
--base-directory /opt/User
--create-migration-sql-for-cordapp fnolUseCase.state.FNOLSchema
getting the below error while installing spring IDE from eclipse market place
An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Unable to read repository at http: //dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/features/org.springframework.ide.eclipse.aop.feature_3.8.4.201703310634-RELEASE.jar.
Read timed out
Unable to read repository at http: //dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/plugins/org.springframework.ide.eclipse.config.graph_3.8.4.201703310634-RELEASE.jar.
Read timed out
Unable to read repository at http ://dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/features/org.springframework.ide.eclipse.roo.feature_3.8.4.201703310634-RELEASE.jar.
Read timed out
Unable to read repository at http: //dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/plugins/org.springframework.ide.eclipse.webflow.core_3.8.4.201703310634-RELEASE.jar.
Read timed out
Check for Eclipse updates at first
Goto Windows-> peferences -> Install/Update -> Available software Sites,update "http://download.springsource.com" instead of "http://dist.springsource.com". restart Eclipse, and add it back.
And select help>install new software>contact all update sites (check)
I did this for Eclipse Mars version
I am using the Eclipse Oxygen Release (4.7.0) and I followed the solution suggested by #Vasath.
In the list of Available software sites, I edited "SpringSource Update Site for Eclipse 4.7" by replacing
http://download.springsource.com/release/TOOLS/update/e4.7 with
http://dist.springsource.com/release/TOOLS/update/e4.7.
It worked, Spring IDE is installed and working fine.
I am getting below error while installing informatica 8.6:
****use the error below and catalina.out and node.log in the server/tomcat/logs directory on the current machine to get more information. Select Retry to continue the installation.
STDOUT: Installing the service '"Informatica Services 8.6.0"' on node 'node01_geettika4912'...
Using CURRENT_DIR: C:\Informatica\PowerCenter8.6.0\server\tomcat\bin
Using INFA_HOME: C:\Informatica\PowerCenter8.6.0
The service '"Informatica Services 8.6.0"' has been installed.
STDERR: The filename, directory name, or volume label syntax is incorrect.
The service name is invalid.
More help is available by typing NET HELPMSG 2185.**
EXITCODE: 2**
I am getting this error after the successful creation of domain.
Please help me in resolving this error.
Thanks!
Run services.msc to get a list of all the services.
Click properties on the service you want, there you can see the "service name" and the "display name".
The service name is what you need to use with the net command. Check if Informatica Services 8.6.0 is in the list.
Two of us made a migration script in different GIT branches. Now, I've pulled origin development branch, and I've corrected GIT merge issues, and renamed my migration script to be the last. So, the new initialization of DB and migration of DB from version of develop branch would be fine.
However, I've got a lot of data in my local testing DB, so I've manually applied new migration scripts that I've pulled in GIT. However, I can't make flyway think, that everything is okay.
So, How can I fake migrations?
When I try to migrate, I get following error:
[ERROR] Failed to execute goal org.flywaydb:flyway-maven-plugin:3.2.1:migrate (default-cli) on project db: org.flywaydb.core.api.FlywayException: Validate failed. Migration Description mismatch for migration 1.118
[ERROR] -> Applied to database : AAA
[ERROR] -> Resolved locally : BBB
[ERROR] -> [Help 1]
You will have to manually update Flyway's metadata table (called schema_version by default)