Android Question Is it possible to connect to an oracle database with a wallet file?

[BernhardS]

Is it possible to connect to an oracle database with a wallet file?

 

[Erel]

Check this: https://docs.oracle.com/en/cloud/pa...tml#GUID-5ED3C08C-1A84-4E5A-B07A-A5114951AA9E

 

[BernhardS]

Thank you, Erel!

I have successfully tested the database connection with B4J.
But unfortunately I cannot establish a connection with B4A.

Can someone help me?
My code is (jSQL Version 1.61 used and the additional Jars from Oracle Website):

#Region  Project Attributes
    #ApplicationLabel: B4A Example
    #VersionCode: 1
    #VersionName:
    #SupportedOrientations: unspecified
    #CanInstallToExternalStorage: False
    #AdditionalJar: ojdbc10.jar
    #AdditionalJar: osdt_cert.jar
    #AdditionalJar: oraclepki.jar
    #AdditionalJar: osdt_core.jar
#End Region

#Region  Activity Attributes
    #FullScreen: False
    #IncludeTitle: True
#End Region

Sub Process_Globals
    Private Conn As SQL '
End Sub

Sub Globals
End Sub

Sub Activity_Create(FirstTime As Boolean)
    Conn.Initialize2( "oracle.jdbc.OracleDriver","jdbc:oracle:thin:@dbschaefer1_high?TNS_ADMIN=WALLET_DIRECTORY","USERNAME","PASSWORD!")
End Sub

Sub Activity_Resume

End Sub

Sub Activity_Pause (UserClosed As Boolean)

End Sub

 

[Erel]

But unfortunately I cannot establish a connection with B4A.

How can we help if you don't tell us what exactly happened...

 

[BernhardS]

The following error occurs during compilation:
The additional Jar-Files are from the original oracle website.

B4A Version: 9.80
Java Version: 11
Parse den Code. (0.02s)
Building folders structure. (0.12s)
Kompiliere den Code. (0.03s)
Kompiliere Layoutcode. (0.01s)
Organisiere Libraries. (0.00s)
(AndroidX SDK)
Generiere R Datei. (0.88s)
Kompiliere Debugger-Code (2.67s)
Kompiliere generierten Java Code. (2.75s)
Byte-Code konvertieren - optimiert dex. Error
PARSE ERROR:
unsupported class file version 54.0
...while parsing oracle/core/lmx/CoreException.class
warning: Ignoring InnerClasses attribute for an anonymous inner class
(oracle.security.crypto.core.f) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(oracle.security.crypto.fips.b) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(oracle.security.crypto.fips.c) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(oracle.security.crypto.provider.c) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(oracle.security.crypto.provider.d) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(oracle.security.crypto.provider.a) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(oracle.security.crypto.provider.b) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(oracle.security.crypto.util.a) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(oracle.security.crypto.util.b) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(oracle.security.crypto.util.c) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(oracle.security.crypto.util.d) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
1 error; aborting

 

[Erel]

The jars are compiled with Java 10. They will not be supported on Android.

Look for an older version of the JDBC driver.