Issues with Redo logfiles and destinations

[Adriana_andros]

we have a database servers for large application.We set initialization parameters
log_archive_dest_1="/u02/fra" and log_archive_dest_2 ="/u04/data".
But after some time the parameter "log_archive_dest_2 " changed to "/u01/get"
can u please tell me what are the operations on database that can change this parameters values? I want to keep only three destinations for the database.

[MindSpace]

Archived Redo Log :

When you perform any database operation Like insert,update,delete and much more, the changes needs to save somewhere.For that concept we use redolog procedure.

For a database, There can be 100 to 1000 user performing some operation at a time then a lot of changes made currently.They should be stored somewhere but logfile don't have much capability to contain everything.So using another procedure we place the copy of logfile in a secure place that is known as archive destination and procedure is called archiving.The generated file on the destination is called as Redo logfile.

[Modifier]

In your organization, a database is being used for a larger application and you are saying that your archiving destination parameter has been changed while you have configured something else.

It is being performed by the DBA and may be you are unknown to that person. Someone know the password of your Administrator account of database.

You need to change the password of database and then configure your database.

[Praetor]

These are the steps below through which you can specify the destination of archive log files of your database:

1. Shut down your database first using

SQL>SHUTDOWN ;
2. Open your pfile(parameter file) and change the parameter

SQL>LOG_ARCHIVE_DEST_1 = 'LOCATION = /disk1/archive';
if you are archiving to a standby database location you have to set the parameter
SQL>LOG_ARCHIVE_DEST_4 = 'SERVICE = standby1';
you can set at least 10 destinations for archiving.

3. Enter command to reflect the changes in spfile also

SQL>Create spfile from pfile;
4. Start your database using

SQL>startup