Database Archiving mode

Hello all,
we are in upgrading BW 3.0B to BW 3.5 on MS Sql 2000. In the part of post upgrade activities, we need to check database archiving mode whether it is inactivation mode or disabled mode. How to check this? if it is disabled, how to activate database archive log mode?
Kindly help us.
kind regards,
Aruna,

Hi
Right click on the SAP database in Enterprise Manager - it is called the <SID> of your BW system.
There are three modes availabling - Simple, Bulk or Full.
You should set the mode to Full.
Thanks
N.P.C

Similar Messages

Test cold backup database in archive mode

Hello,
We doing every week a cold backup from Oracle database, us database is in archive mode.
We would like to test us cold backup in other server but the drive where we have to copy
the datafiles and logs and rollback are different on this server.
In the production server the oracle_home and the oracle_sid:
ORACLE_HOME=E:\oracle\product\10.2.0\db_1
ORACLE_SID=ENCY
and on the other server to test the backup are:
ORACLE_HOME=I:\oracle\product\10.2.0\db_2
ORACLE_SID=ENCY
Can somebody help me saying please the steps that I have to follow to restore the database in other server
to test if the last cold backup is fine?
My understand is copy the files(datafiles, log files, control files, pfile,...) in the new server, when everything is copied into new server,
I have to:
Modify the parameter CONTROL_FILES in the pfile
Mount the database and rename the datafiles and redolog files
Thanks.

user641364 wrote:
Hello,
We doing every week a cold backup from Oracle database, us database is in archive mode.
We would like to test us cold backup in other server but the drive where we have to copy
the datafiles and logs and rollback are different on this server.
In the production server the oracle_home and the oracle_sid:
ORACLE_HOME=E:\oracle\product\10.2.0\db_1
ORACLE_SID=ENCY
and on the other server to test the backup are:
ORACLE_HOME=I:\oracle\product\10.2.0\db_2
ORACLE_SID=ENCYThe only difference between servers is different ORACLE_HOME path?
All other directories are the same?
>
Can somebody help me saying please the steps that I have to follow to restore the database in other server
to test if the last cold backup is fine?
My understand is copy the files(datafiles, log files, control files, pfile,...) in the new server, when everything is copied into new server,
I have to:
Modify the parameter CONTROL_FILES in the pfile
Mount the database and rename the datafiles and redolog filesYou shoud modify and rename only in case if path to datafiles, redologs, controlfiles, dump, archive log directories is different on test server.
If that will be the same, then no need to rename.
If it is different, then modify pfile in order to meet correct one paths.

Cloning 10g Database in archive mode - How add new created archive files

Deat all
I want to clone oracle 10g database using hot backup. database in archive mode.
Database is running user data entry contifue, during hot backup there are aproximatly 3 to 5 new archive log created. Please guide me how add these new created archive log in cloning process.
Thanks
Alter system switch logfile;
SQL> select max(first_change#) scn from v$archived_log;
SCN
8592924
alter tablespace tablespace1 begin backup;
alter tablespace tablespace2 begin backup;
alter tablespace tablespace3 begin backup;
alter tablespace tablespace1 end backup;
alter tablespace tablespace2 end backup;
alter tablespace tablespace3 end backup;
select name from v$archived_log where first_change# >= 8592924 order by name
NAME
F:\ARCHIVELOGS\ARC00390_0664080689.001
F:\ARCHIVELOGS\ARC00391_0664080689.001
F:\ARCHIVELOGS\ARC00392_0664080689.001
create pfile='init<new database sid>.ora' from spfile;
alter database backup controlfile to trace as '/home/oracle/cr_<new sid>.sql'
STARTUP NOMOUNT
CREATE CONTROLFILE SET DATABASE "ORCL" RESETLOGS FORCE LOGGING NOARCHIVELOG
MAXLOGFILES 50
MAXLOGMEMBERS 5
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 453
LOGFILE
GROUP 1 'E:\oracle/oradata/dg9a/redo01.log' SIZE 100M,
DATAFILE
Edited by: Naeem Sheeraz on Nov 15, 2008 12:54 PM

When you attempt to startup the cloned database on the new server you will find that it needs recovery -- because it was taken in hot backup mode.
That is why you need to copy the archivelogs that are generated from the first archivelog after the first "alter tablespace begin backup" to the first archivelog after the last "alter tablespace end backup".
I see that you are also including a CREATE CONTROLFILE script.
You would run that at the cloned environment.
Then you would issue the RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL command to make the clone consistent.
You can, of course, use the same method to copy these archivelogs as you use to copy database files -- tar, cpio, tape, etc.

CONFIGURE DATABASE IN ARCHIVE MODE

Hai
I am just trying to change the database to archive mode.As part of this I need to set the parameter LOG_ARCHIVE_START to TRUE in the init.ora file.But I am not able to find this parameter in the init.ora file(any of the archive parameter for that matter).Please advise where can I find and set LOG_ARCHIVE_START parameter.
Thanks
Jay

LOG_ARCHIVE_DEST
Parameter type
String
Syntax
LOG_ARCHIVE_DEST = filespec
Default value
Null
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any valid path or device name, except raw partitions
Real Application Clusters
Multiple instances can have different values.
Note:
For Enterprise Edition users, this parameter has been deprecated in favor of the LOG_ARCHIVE_DEST_n parameters. If Oracle Enterprise Edition is not installed or it is installed, but you have not specified any LOG_ARCHIVE_DEST_n parameters, this parameter is valid.
LOG_ARCHIVE_DEST is applicable only if you are running the database in ARCHIVELOG mode or are recovering a database from archived redo logs. LOG_ARCHIVE_DEST is incompatible with the LOG_ARCHIVE_DEST_n parameters, and must be defined as the null string ("") or (' ') when any LOG_ARCHIVE_DEST_n parameter has a value other than a null string. Use a text string to specify the default location and root of the disk file or tape device when archiving redo log files. (Archiving to tape is not supported on all operating systems.) The value cannot be a raw partition.
If LOG_ARCHIVE_DEST is not explicitly defined and all the LOG_ARCHIVE_DEST_n parameters have null string values, LOG_ARCHIVE_DEST is set to an operating system-specific default value on instance startup.
To override the destination that this parameter specifies, either specify a different destination for manual archiving or use the SQL*Plus statement ARCHIVE LOG START filespec for automatic archiving, where filespec is the new archive destination. To permanently change the destination, use the statement ALTER SYSTEM SET LOG_ARCHIVE_DEST = filespec, where filespec is the new archive destination.
Neither LOG_ARCHIVE_DEST nor LOG_ARCHIVE_FORMAT have to be complete file or directory specifiers themselves; they only need to form a valid file path after the variables are substituted into LOG_ARCHIVE_FORMAT and the two parameters are concatenated together.
See Also:
Oracle9i User-Managed Backup and Recovery Guide
"LOG_ARCHIVE_DUPLEX_DEST", "LOG_ARCHIVE_MIN_SUCCEED_DEST", and "V$ARCHIVE_DEST" for more information on setting this parameter
Your Oracle operating system-specific documentation for the default value and for an example of how to specify the destination path or filename using LOG_ARCHIVE_DEST
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch191.htm#REFRN10085
Joel Pérez

"Database log mode" & "Automatic archival"

I was asked to do the below
"Database log mode" should be set to
"No Archive Mode" now.
Do not mix up "Database log mode" with
"Automatic archival".
Can you please tell me how to "disable databse log mode", with Automatic Archival enabled.
Regards,
Susan

From documentation:
ARCHIVELOG mode
The mode of the database in which Oracle copies filled online redo logs to disk. Specify the mode at database creation or by using the ALTER DATABASE statement. You can enable automatic archiving either dynamically using the ALTER SYSTEM statement or by setting the initialization parameter LOG_ARCHIVE_START to TRUE.
Running the database in ARCHIVELOG mode has several advantages over NOARCHIVELOG mode. You can:
* Back up the database while it is open and being accessed by users.
* Recover the database to any desired point in time.
To protect the ARCHIVELOG mode database in case of failure, back up the archived logs.
Configuring ARCHIVELOG Mode For the Database<a>
 
Or you can check this tutorial from Oracle:
Disabling Automatic Archiving
 
 
Or something like this: 
sqlplus /nolog
connect / as sysdba
shutdown
startup mount exclusive
alter database noarchivelog
alter database open
 
And I don't know if it's needed to have automatic archival enabled since the database will not be in archive mode.

Archive mode in destination database for own way stream

Hi Experts,
I set up a one way stream for oracle 10GR2 in window 2003.
I know that i need to turn on archive mode for capture and propagation in source database machine.
Do we need to turn on archive mode on in destination database machine? It is only running apply process.
Any suggestion?
Thanks,
Jim

No Jim, If you are using one way stream replication, that it doesn't need archiving to be enabled at destination site.
Only the site from where changes are being captures need archiving to be on.
Regards,
Dipali..

How to recover the data from a dropped table in production/archive mode

How to recover the data/change on a table that was dropped by accident.
The database is on archive mode.

Oracle Version. ? If 10g.
Try this Way
SQL> create table taj as select * from all_objects where rownum <= 100;
Table created.
SQL> drop table taj ;
Table dropped.
SQL> show recyclebin
ORIGINAL NAME RECYCLEBIN NAME OBJECT TYPE DROP TIME
TAJ BIN$b3MmS7kYS9ClMvKm0bu8Vw==$0 TABLE 2006-09-10:16:02:58
SQL> flashback table taj to before drop;
Flashback complete.
SQL> show recyclebin;
SQL> desc taj;
Name Null? Type
OWNER VARCHAR2(30)
OBJECT_NAME VARCHAR2(30)
SUBOBJECT_NAME VARCHAR2(30)
OBJECT_ID NUMBER
DATA_OBJECT_ID NUMBER
OBJECT_TYPE VARCHAR2(19)
CREATED DATE
LAST_DDL_TIME DATE
TIMESTAMP VARCHAR2(19)
STATUS VARCHAR2(7)
TEMPORARY VARCHAR2(1)
GENERATED VARCHAR2(1)
SECONDARY VARCHAR2(1)
SQL>M.S.Taj

Recovery in archive mode, but no archived logs

Hi,
I hope someone can help me with the following question.
I have a 9.2 database in archive mode. Suppose on t=t0 I make an online backup. At the end of this run, I will do an "alter system switch logfile" statement to capture the latest transactions (more or less also at t=t0). Later, at t=t1 we do some transaction and more archived redologs are created. At t-t2 I need to restore the complete database, but I have LOST all the archive files as from t=t0. Now the question is, is it still possible to recover (even it means to go back to t=t0)? I have tried it, but always the system suggests to apply the (missing) archived redo's, and it seems I cannot escape this. But, Is it possible to get back to t=t0?
Thanks a lot, for any clue or pointer !

If you take a hot backup and you lose the redo logs, you have a fundamentally inconsistent backup. Each tablespace will be internally consistent, but they probably won't have the same SCN as the control files, so you'll get this message.
Do you have an earlier hot backup and the archived logs that would restore that backup to the point in time (t=0) where you took the latest hot backup? Personally, I generally like to keep at least 2 or 3 old backups, with archived log files, just in case something goes wrong with the most recent backup.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

How can I set my Database in mode ARCHIVELOG?

Hello,
I was reading that I need to set my Database on mode ARCHIVELOG to make backups.
How can I do it?

You need to be in archivelog mode to do hot (online) backups. You can take cold (offline) backups if the database is in archivelog mode or not.
Below are steps to enable archivelog mode
Start Archive log mode
1. connect / as sysdba
2. startup mount exclusive
3. alter system set log_archive_dest=<archive destination> scope=both;
4. alter database archivelog;
5. alter database open;
6. shutdown immediate
7. backup database
If you are using a database prior to 10g, you need to set log_archive_start = true in order to enable automatic archiving.

Looking for an advice in changing to archive mode my DB

Hello buddies!
I'm going to change a DB from no archive mode to archive mode. It's a RAc with ASM, 2 nodes.
What I need that somebody verify these steps and give me suggestions.
1. Login to one of the nodes (i.e. linux1) and disable the cluster instance parameter by setting
cluster_database to FALSE from the current instance:
ORACLE_HOME=/home/oracle/product/10.2.0/db
export ORACLE_HOME
ORACLE_SID=YAWIDB1
export ORACLE_SID
2. sqlplus "/ as sysdba"
SQL> alter system set cluster_database=false scope=spfile sid='YAWIDB1';
3. Shutdown all instances accessing the clustered database:
$ srvctl stop database -d YAWIDB
Using the local instance, MOUNT the database:
$ sqlplus "/ as sysdba"
SQL> startup mount
Enable archiving:
SQL> alter database archivelog;
Re-enable support for clustering by modifying the instance parameter cluster_database to TRUE from the current instance:
• SQL> alter system set cluster_database=true scope=spfile sid=’YAWIDB1’;
• Shutdown the local instance:
• SQL> shutdown immediate
• Bring all instance back up using srvctl:
• $ srvctl start database -d YAWIDB
Since the archive destination is pointing to this path: Archive destination /home/oracle/product/10.2.0/db/dbs/arch
I think I should do the next steps to change that to ASM disk group, but in these steps I'm not sure. Please let me know If I'm wrong or correct? Or if I need to add something else.
ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='+DG_DB1_ASM' SID='yawidb';
ALTER SYSTEM SWITCH LOGFILE;
The order of the complete steps, are correct or shoud be different?
Thanks for your comments and suggestions ;
Al

You do not need to change cluster parameter, see steps below:
On node1:
$ srvctl stop database -d <db_name>
$ srvctl status database -d <db_name>
Instance <instance1> is not running on node <node1>
Instance <instance2> is not running on node <node2>
$ srvctl start instance -d <db_name> -i <instance1> -o mount
$ srvctl status database -d <db_name>
Instance <instance1> is running on node <node1>
Instance <instance2> is not running on node <node2>
SQL> conn / as sysdba
Connected.
SQL> alter database archivelog;
Database altered.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination <arch_dest>
Oldest online log sequence 67
Next log sequence to archive 68
Current log sequence 68
SQL> alter database open;
Database altered.
$ srvctl start instance -d <db_name> -i <instance2> -o open
$ srvctl status database -d <db_name>
Instance <instance1> is running on node <node1>
Instance <instance2> is running on node <node2>
SQL> conn / as sysdba
Connected.
SQL> select inst_id, log_mode from gv$database;
 INST_ID LOG_MODE
 1 ARCHIVELOG
 2 ARCHIVELOGArchive log destination could be change any time.
Regards.

File Adapter archiving mode....

Putting message into send queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID a7cbcf00-4e00-11db-bd7f-0018717400ed(OUTBOUND) already exists in database: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00135467) violated.
2006-09-27 17:17:47 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID a7cbcf00-4e00-11db-bd7f-0018717400ed(OUTBOUND) already exists in database: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00135467) violated
2006-09-27 17:17:47 Error Attempt to archive file "D:\SSNEDI\test\in\queue\20060926070906359.txt" after processing failed. Retry
source directory : D:\SSNEDI\test\in\queue
target directory : D:\SSNEDI\test\in\queue\FB
But, source directory not deleted 20060926070906359.txt.
Target directory exist file too.
what's the matter?

Hi Kim,
If it is in test mode,the file wont get deleted in your source direcory. So the adpater will keep polling the file and the server will be flooded with messages. If it is in the delete mode file will be deleted,archive mode it will be moved in to the archived directory but in the test mode file will not be deleted from your source directory and will be polled continously by the adapter.
Also go thro' this link:-
Re: Archiving ftp files
Hope this provides a solution.
Regards.
Praveen

Noarchive mode to archive mode

Hi,
I'm trying to backup my database in online mode. I've 2 instances: BDPROD and BDPROD2. BDPROD is already in archive mode. I'm trying to change BDPROD2, but when I shutdown the database and run startup mount, I received the error: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. After trying again, I received 2 new errors: ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
Anyone have any ideia for help me?
Thanks

11abcd94-7f56-4836-a39d-63d0d0de41d9 wrote:
Hi,
My Oracle runs in Linux.
My ORACLE_SID = BDPROD
My ORACLE_HOME = /usr/local/oracle/product/10.2.0/db_1
I've to change the ORACLE_SID?
It depends on how you are connecting to the database to do the shutdown/startup.
You should be doing it as a local connection. Log on to the linux server using the os account that owns the oracle installation, probably 'oracle'
set your environment variables correctly by using the oraenv utility as this:
oracle: . oraenv
That's "dot" "space" "oraenv"
You will be prompted for the correct ORACLE_SID.
After that you should be able to connect with a simple
oracle: sqlplus / as sysdba

How to change from archive mode to noarchive mode

Hi,
I am running 10gR2 on Windows.
Does any one know the steps to change the database which is current in archive mode to noarchive mode?
Thanks

shutdown immediate
startup mount
alter database noarchivelog;
alter databae open;
archvie log list -- to check whether the archive mode is turned off or no.
Make sure you backup the database before and after.
Jaffar

How to change DB into ARCHIVE mode

How can we switch a 10g DB into archive mode
on Unix?
Should the DB be shut down?
Any help
Regads

Jane,
How can we switch a 10g DB into archive mode on Unix?Please refer to:
Note: 69739.1 - How to Turn Archiving ON and OFF
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=69739.1
Should the DB be shut down?Yes, you need to bounce the database.

Converting DB in archive mode

hi buddies;
I got, three DBs with ASM in Oracle RAC (2 nodes). Two of these DBs are in archive mode, but one of them, no. So, I'm going to convert this one (DATABASE3) in archivemode now. I got the instructions to do this, but still I have some doubts, So I need your 'inputs' to be sure that I'm right.
These are the steps I understand I should follow.
1. Login to one of the nodes (i.e. linux1) and disable the cluster instance parameter by setting
cluster_database to FALSE from the current instance:
2. $sqlplus "/ as sysdba"
SQL> alter system set cluster_database=false scope=spfile sid='DATABASE3_1';
3. Shutdown all instances accessing the clustered database:
$ srvctl stop database -d DATABASE3
Using the local instance, MOUNT the database:
$ sqlplus "/ as sysdba"
SQL> startup mount
Enable archiving:
SQL> alter database archivelog;
Re-enable support for clustering by modifying the instance parameter cluster_database to TRUE from the current instance:
•     SQL> alter system set cluster_database=true scope=spfile sid='DATABASE3_1';
•     Shutdown the local instance:
•     SQL> shutdown immediate
•     Bring all instance back up using srvctl:
•     $ srvctl start database -d DATABASE3
My databases are:
+ASM
DATABASE1
DATABASE2
DATABASE3 --- This is the DB in noarchivemode.
My doubts are:
In step 3, says 'shutdown all instances', means all instances in both nodes, except the instance I'm going to change and ASM in that node?
Any recomendation, or suggestions, you understand I should be alert?
Regards;
ANG

Hi,
You do not need to shutdown any other database than the database which you want to change to archive log. The target database needs to be shutdown on all nodes to folow your instruction. All other database running in archivelog will stay up.
Regards

Database Archiving mode

Similar Messages

Maybe you are looking for