Oracle and ListManager (Linux/Solaris)
Note: Although ListManager may use Oracle, Lyris does not support the Oracle database itself. These instructions are provided for the convenience of those using ListManager with Oracle. For complete Oracle documentation, go to http://oracle.com/.
Before installing ListManager, you’ll need to install the Oracle Client Tools (or Basic Client Software) on the machine which will be running ListManager. Then, you’ll create a user and password to be used by ListManager. When you’re done, you’re ready to install ListManager. Your DBA (database administrator) can assist you in installing the client software on the server that will be running ListManager.
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 you've installed.
Permissions Needed to run ListManager against your Oracle database
The DBA will need to know the common permissions required for Oracle users. The following is 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 ListManager will use special accent characters, such as ˙ or á. If your server has this problem, ListManager will give you one of these errors when starting it in the foreground:
Your database is not configured to store all data exactly as it was sent. This will 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.
Your database and/or client configuration will cause problems, as errors were generated when special characters (such as used by foreign languages) were sent and/or retrieved from the database. This will VERY LIKELY CAUSE ERRORS and should be corrected before continuing.
To solve this problem, create your Oracle instance with an 8-bit ASCII character set. If you don't
have a preference, we recommend you use:
WE8ISO8859P1
However, if you choose a different character set, the data will be translated into the client character
set, which will almost certainly cause 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_LANG
Once you have determined which one is the correct one, you should configure the appropriate startup file (e.g., /etc/profile or similar) to set NLS_LANG so that ListManager will have it set properly at startup.
Database Server Password Security
As the database password is saved unencrypted in a file (lmcfg.txt), you may later remove the password saved in this file and then specify that the password be provided on startup by altering this file.
|
|