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
Related
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"
]
My current version of Artifactory Pro 6.5.2. I can upgrade incrementally from 6.5.2 to 6.5.9 to 6.0.0. If I try to upgrade beyond 6.0.0, I receive a 404 error when attempting to access Artifactory.
HTTP Status 404 – Not Found
Type Status Report
Message /artifactory/webapp/
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
Apache Tomcat/8.5.32
I see the following errors in /var/opt/jfrog/artifactory/logs/catalina/catalina.out
Failed to ensure db table 'master_key_status' exists
Error creating bean with name 'accessJdbcHelperImpl': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Could not initialize database: Not supported
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/access]]
The database I'm using is MySQL
mysql Ver 15.1 Distrib 5.5.60-MariaDB, for Linux (x86_64) using readline 5.1
Has any encountered a similar issue when upgrading Artficatory Pro?
Thanks
Just marking down the answer.
The issue was with the JDBC driver version of the Maria DB.
One more update done by you was adding the timezone value.
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
In icCube 6.1 I want to connect to a MsAccess file stored locally on the icCube server. When I try to connect I get the error message:
Failed to establish the connection due to the error: JDBC driver class
'sun.jdbc.odbc.JdbcOdbcDriver' not found in the classpath
This is what I provide in the connection:
Name : Clients
Visibility :
Driver Type : Access (JDK JDBC/ODBC Bridge)
Server Name : localhost
Port Number :
DB Name : C:\data\Clients.accdb
User :
Password :
When I Google on this error I get the message (dated from 2015) that:
in JDK 8, jdbc odbc bridge is no longer used and thus removed from the
JDK.
Help.
As you mentioned you cannot use anymore the JDBC ODBC bridge from JRE 8.
As an alternative you can use a MS Access JDBC driver. For example: UCanAccess. To install this driver in icCube unzip the file and copy the following files into the /lib directory of the icCube install directory:
ucanaccess-4.0.2.jar
jackcess-2.1.6.jar
hsqldb.jar
Then in the builder data source, select a generic JDBC driver and configure the Server Name and DB Name as following:
> Server Name : net.ucanaccess.jdbc.UcanaccessDriver
> DB Name : jdbc:ucanaccess://c:/your-file.accdb
Hope that helps.
[edit] Depending on how icCube is started you might need to update the CLASSPATH with the three new JARs. To avoid CLASSPATH edition, you can use the following in the icCube.sh for example to start icCube using all the JARs in the /lib directory:
> $JAVA $JAVA_OPTS -cp "$ICCUBE/lib/*" crazydev.iccube.server.IcCubeServer
Am getting below error after installing ODP.net.
ORA-12154: TNS:could not resolve the connect identifier specified
Before installing ODP.net i was able to connect with database using plsql developer.But ODP.net is required to run .net application so i installed ODP.net.But after installing ODP.net am unable to connect with database using plsql develper and .net code. Error am getting is "
ORA-12154: TNS:could not resolve the connect identifier specified "
Let me know if anyone knows the solution for this.
When you installed the latest ODP.net the Oracle Installer may have created a new Oracle_Home. You need to find the sqlnet.ora and tnsnames.ora files from your original home and copy them to the new Oracle Home.
For example. If your first ODP.net installation was to:
C:\app\oracle\product\12.1.0\client_1
and if your second ODP.net installation was to
C:\app\oracle\product\12.1.0\client_2
then you need to copy the files from
C:\app\oracle\product\12.1.0\client_1\Network\Admin
to
C:\app\oracle\product\12.1.0\client_2\Network\Admin