Results 1 to 6 of 6
  1. #1
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1

    Unanswered: log_archive_dest_n

    Hello all,

    I have an Oracle 8.1.6 EE database on Solaris.

    My question is about setting log_archive_dest_n paremeter "on the fly". Documentation states that this parameter is "dynamic", which I understand should change archiver behaviour without restarting the database.

    The database was started with "log_archive_dest_1='location=..." in its init file. Now I want to add another location for archiving. I issue "alter system set log_archive_dest_2='location=...", see "System altered" message and, after looking at V$ARCHIVE_DEST, observe that the new destination is enabled (valid). However, the archived logs are still being copied to a single destination, the one specified at database startup.

    Do I need to do something else to start copying files to the new location?

    Thanks,

    Nick
    ---
    "It does not work" is not a valid problem statement.

  2. #2
    Join Date
    Sep 2003
    Location
    The Netherlands
    Posts
    311
    hi,

    have you tried to change the value of the original parameter (archive_log_dest) instead of creating a new one?
    Edwin van Hattem
    OCP DBA / System analyst

  3. #3
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Originally posted by evanhattem
    hi,

    have you tried to change the value of the original parameter (archive_log_dest) instead of creating a new one?
    I want to "duplex" archived logs onto two different devices (it has not been done originally). So, no, I haven't tried to change the existing destination.

    It's "log_archive_dest_1", by the way - I understand "log_archive_dest" is not compatible with "log_archive_dest_n"...
    ---
    "It does not work" is not a valid problem statement.

  4. #4
    Join Date
    Sep 2003
    Location
    The Netherlands
    Posts
    311
    hi,

    agreed about the naming.

    Your problem is i thin k in the archivers, just restart them:
    SQL> ALTER SYSTEM ARCHIVE LOG STOP;
    System altered.
    SQL> ALTER SYSTEM ARCHIVE LOG START;
    System altered.

    The newly created archiver procecess will now recognize all the destinations

    Hope this helps
    Edwin van Hattem
    OCP DBA / System analyst

  5. #5
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Originally posted by evanhattem
    Your problem is i thin k in the archivers, just restart them:
    SQL> ALTER SYSTEM ARCHIVE LOG STOP;
    System altered.
    SQL> ALTER SYSTEM ARCHIVE LOG START;
    System altered.
    Thanks, I'll try it later.
    ---
    "It does not work" is not a valid problem statement.

  6. #6
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Just confirming that, as evanhattem suggested, I restarted the archiver processes ("alter system archive log stop" then "alter system archive log start"), and the new destination was recognized.

    Thanks evanhattem!
    ---
    "It does not work" is not a valid problem statement.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •