Direct log data to separate Oracle databases

If SecureTransport Server uses an external Oracle database, you can direct transfer log (file tracking) data and server log data to different databases from the one used for the rest of the SecureTransport configuration and data.

You can direct the transfer log data and server log data to the same database or to different databases. When you change the database used to store log data, SecureTransport does not copy the data from its current location to the new location.

SecureTransport continues to operate when the external server log database is unavailable. SecureTransport directs the server log data to <FILEDRIVEHOME>/var/logs/serverlog-fallback.log. The Server Log page indicates that the log is unavailable and provides a link you can use to download the file.

  1. Make sure the Oracle databases have the characteristics listed in the Database installation prerequisites topic of the SecureTransport Installation Guide . Depending on the log data you direct to a database, you must define the ST_FILETRACKING tablespace or the ST_SERVERLOG tablespace.
  2. Select Setup > Database Settings.
  3. The Database Setting page is displayed with the external database settings under Large Enterprise Clustering - Oracle External Database.
  4. Select Show Advanced Settings.
  5. The settings for the two additional databases are displayed.
  6. Under Large Enterprise Clustering - Oracle External Database - Transfer Log and Large Enterprise Clustering - Oracle External Database - Server Log, type the values necessary to connect to the external databases. To continue to use the primary database, retain the default values.
  7. For description of the required values, see Switch from the embedded database to an external Oracle database.
  8. For each database, click Test Connection to Oracle Database.
  9. If SecureTransport displays a failure message, correct the network, Oracle, or other error reported and try again.
  10. Type the passwords again and click Save.
  11. The first time the new database is referenced, SecureTransport creates the tables for the log data. SecureTransport does not copy the log data from the previous database to the new database and does not display the log entries from the previous database in the File Tracking and Server Log pages.
  12. Select Operations > Server Control.
  13. On the Server Control page, stop and restart all the protocol servers and the TM Server.
  14. Log out of the Administration Tool.
  15. Log on to the SecureTransport server and stop and restart the Administration Tool service using the stop_admin and start_admin commands in <FILEDRIVEHOME>/bin.
  16. In a large enterprise cluster, repeat steps 2 though 10 for all SecureTransport Servers.

Related topics:

Related Links