To meet your needs, we constantly work to improve Querix products.
This means that Lycia documentation is developing as well.
In case you have found a certain dissonance between the provided information and the actual behavior of Lycia 3 and/or your applications, please, let us know about this via documentation@querix.com so that we can introduce the necessary changes to our documentation.
Thank you for your attention and cooperation.
You can use an existing Oracle database to work with Lycia or you can create a new one. Here are the general instructions to be used for an Oracle database creation and connecting to it from Lycia.
Step 1 |
Install and configure the Oracle RDBMS. You must have the Oracle client installed regardless of whether you want to create a new database or to connect to an existing one
|
|
Step 2 |
Create a user under Oracle and provide the username and password by running the command ‘sqlplus’, and connect as a user with DBA privileges. Refer to Oracle documentation for the details on creating and managing a database
|
|
Step 3 |
Record the database connection details into the database.cfg file
|
|
Step 4 |
For the GUI server running an authenticated port, set the following environment variables in the inet.env file:
The inet.env file can be opened and edited using the Studio. To open it in LyciaStudio, go to Window-> Preferences -> 4GL -> Run/Debug -> GUI Servers, select the GUI server from the list and press the Edit Environment button.
|
|
Step 5 |
Set the database driver to "Oracle" as described here
|
Step 1 |
Install and configure the Oracle RDBMS. You must have the Oracle client installed regardless of whether you want to create a new database or to connect to an existing one
|
|
Step 2 |
Create a user under Oracle and provide the username and password by running the command ‘sqlplus’, and connect as a user with DBA privileges
|
|
Step 3 |
Set Lycia environment variables:
|
|
Step 4 |
Set the database driver to "Oracle" as described here
|
Connecting to a database in GUI mode is rather tricky, if your application is running on an application server without authentication (i.e. default).
An application using this post is run as the service owner and this means that all database connections are using the same user ID. Thus it is advisable to use the full authentication port (secure)