Oracle and Aurea List Manager for Linux
Aurea List Manager may use Oracle, but Lyris does not support the Oracle database itself. These instructions are provided for the convenience of those using Aurea List Manager with Oracle. For complete Oracle documentation, go to http://oracle.com/.
It is mandatory to install Oracle Client Tools or Basic Client Software on the machine which is going to be running Aurea List Manager before installing Aurea List Manager. A user and password need to be created to be used by Aurea List Manager, then Aurea List Manager can now be installed.
Note
Be sure that LD_LIBRARY_PATH is set to point to Oracle's libraries before installing and that you select the installer that matches the version of client tools installed.
Permissions required on Aurea List Manager for Oracle database
The DBA (Database Administrator) needs to know the standard permissions required for Oracle users. The following is used as an example only.
You may use any username or a different tablespace if desired:
drop user username cascade;
create user username identified by password default tablespace users quota unlimited on users;
grant connect, resource to username;Changing the Character Set of your Oracle Instance
Oracle servers, by default, do not install with a character set that allows 8-bit ASCII characters to be represented correctly. Any high ASCII characters (greater than 127) are translated into other characters.
This can cause a problem if you expect that any mail flowing through Aurea List Manager is going to use special accent characters, such as ÿ or á.
When this happens the Aurea List Manager server gives one of these errors when starting it in the foreground:
Warning
Your database is not configured to store all data correctly as it was sent. This is going to cause some messages, especially those in foreign languages, to be incorrectly saved. It is recommended that you change your database configuration to ensure that this is not a problem.
Or,
Your database and/or client configuration is going to cause problems, as errors were generated when special characters (such as used by foreign languages) were sent and/or retrieved from the database. This is going to cause likely error s and should be corrected before continuing.
To solve this problem, create your Oracle instance with an 8-bit ASCII character set. If you do not have a preference, we recommend you use: WE8ISO8859P1
However, if you choose a different character set, the data is translated into the client character set, which almost certainly causes problems. The client character set can be configured using an environmental variable called NLS_LANG.
The syntax of the variable is <language>_<country>.<char set>, such as American_America.US8PC437
Setting the Environment Variable for Unix
For a UNIX client, set the environment variable in this manner. Try each one until the error message no longer appears on boot up.
csh/tcsh: setenv NLS_LANG 'AMERICAN_AMERICA'
setenv NLS_LANG 'AMERICAN_AMERICA.WE8ISO8859P1'
setenv NLS_LANG 'American_America.US8PC437'
sh/bash: NLS_LANG='AMERICAN_AMERICA'; export NLS_LANG
NLS_LANG='AMERICAN_AMERICA.WE8ISO8859P1'; export NLS_LANG
NLS_LANG='American_America.US8PC437'; export NLS_LANGOnce you have determined which one is the correct one, you should configure the appropriate startup file(For example, /etc/profile or similar) to set NLS_LANG so that Aurea List Manager is going to have it set properly at startup.
Database Server Password Security
As the database password is saved unencrypted in a file lmcfg.txt, it is recommended to remove the password saved in this file and then specify that the password is provided on startup by altering this file.