Archive log mode required for async. CDC?

Hello there,
I have tried to set up asyn. HotLog CDC on my 10g database but after creating a publisher I get the following error Message when creating a change set with the publisher:
BEGIN
DBMS_CDC_PUBLISH.CREATE_CHANGE_SET(
change_set_name => 'MY_CHANGESET',
description => 'First Change set',
change_source_name => 'HOTLOG_SOURCE',
stop_on_ddl => 'y',
begin_date => sysdate,
end_date => sysdate+20);
END;
following Error-Message:
BEGIN
ERROR at line 1:
ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
ORA-06512: at "SYS.DBMS_CAPTURE_ADM_INTERNAL", line 115
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 57
ORA-06512: at line 2
Does this mean that I have to activate the ARCHIVE LOG-mode, and if yes, how do I do this with the Enterprise Manager?
I already set the LOG_ARCHIVE_START initparam to "true".
Klaus

To place a database in archivelog mode you must:
Be sure that the log_archive_start and log_archive_dest
parameters are set in the init file.
Shut the instance down.
startup mount;
alter database archivelog;
alter database open;

Similar Messages

Running in Non-Archive log mode?

Hi,
I know that the documentation states in numerous places that a server must be running in ArchiveLog mode if you want to configure streams but is it essential? We will be running a server under heavy traffic and our disk space is very limited. If we set our redo datafiles to a size that should give a days worth of redo we would remove the need to constantly clean up our archive directory.
Cheers,
Warren

The requirement for ARCHIVE LOG mode is for source sites (ie, any database with a CAPTURE process). If the database is a target site only(ie, an apply destination with no CAPTURE process defined) then archive logging is not a requirement.

For streams , database in Archive log mode or non archive log mode?

Hello ,
I have a basic question,
To set up oracle streams, what should be the the database mode (archive log or non archive log mode)?
Thanks in advance,
Raj

It needs to be in archive log mode..thts the place frm where it captures the necessary information....
Kapil

Question about import in archive log mode

Hello.
I am a developer, I have ordered to write a script that makes the import of a schema of a database (release 9.2.0.7). That import will be done once a day. I have seen that in my development environment the import creates 54 archivers files (10M aprox. each), that means more that half a Gb a day, it seems too much to me.
I cannot see why all those archivers can be useful. Would a good way of proceeding the following?
1. Forcing an archiver just before the import (I do not know how to do that) so that a backup could be done to the state before the import.
2. Disabling archive log mode during the import and enabling it just after the import (I do not know how to do that).
3. Forcing a new archiver just after the import (I do not know how to do that).
Thanks in advance.

540M is not that much.
One would question why you need to import every day,
there must be better ways to do this.
The three steps you propose look like an awful
scenario, as it would require the database to switch
from archivelog to noarchivelog and vice versa.
This would require the database to close twice a
day.
The scenario is also incomplete as one would need to
take a backup after the import
If you can convince your DBA to close the database
twice a day, he should write the script, which he can
easily derive from the docs.
But likely he will visit Billy Verreynne to borrow
his lead pipe, and rightly so ;)
Sybrand Bakker
Senior Oracle DBAThanks for the answer.
A few things:
- Sorry for my ignorance, I have no experience in database backups, I do not understand why I need to backup just after the import.
- That database is not critical, it is just for a team who will test on that database several applications, so the database will only need to be open during the office schedule.
- I have no dba. The client has a dba for several databases but I have no contact with him/her nor my boss has.

Disabling Log_Archive_Start in Archive Log Mode

Guys,
I have a Database running in Archive Log mode.
I have a situation where in I have to do bunch of bulk updates for which I dont want any logs generated.
sO I was thinking to set the intialization parameter log_archive_start to false before I run the DML updates
ALTER SYSTEM SET log_archive_start = false
after the DML is run I will turn it back on
ALTER SYSTEM SET log_archive_start = True
Do you think if this is the right to go about or would I have to switch from Archive Log Mode to No Archive Log Mode
run the DML update and then switch back to Archive Log Mode
Any comments/suggestions/inputs woo

Hello,
I would use some other way to get a full nologing behaviour.
First, ensure your tablespace is in force logging mode.
ALTER TABLESPACE data FORCE LOGGING NOLOGGING;
ALTER TABLESPACE index FORCE LOGGING NOLOGGING;
This will ensure that you're usually logging.
Set all tables/indexes to be nologging
BEGIN
FOR vRes IN (SELECT OWNER,TABLE_NAME FROM DBA_TABLES WHERE TABLESPACE_NAME='data')
LOOP
EXECUTE IMMEDIATE 'ALTER TABLE ' || vRes.OWNER || '.' || vRes.TABLE_NAME ' NOLOGGING';
END LOOP;
END;
Do even for indexes.
From now on, when you want to do your huge amount of updates/... targetting objects in tablespaces data and index, jou just have to:
ALTER TABLESPACE data NO FORCE LOGGING;
ALTER TABLESPACE indexes NO FORCE LOGGING;
- Your DML
ALTER TABLESPACE data FORCE LOGGING;
ALTER TABLESPACE indexes FORCE LOGGING.
4 commands to disable logging for every object in the tablespace.
Beware, when in NOLOGGING mode, you won't be able to "RECOVER" any of the tables. Thiis is not crash-friendly, but you'll have no redo info generated, which is what you require.
Regards,
Yoann.

Archive log mode doubt

Hi All,
We have 10g R2 database running on RHEL 4 OS. In order to set the archive log mode for the database, if we set only log_archive_dest_n parameter is only enough or we have to set db_recovery_file_dest_size and db_recovery_file_dest also? i know that these 2 parameters are required to configure the flash_recovery_area. my doubt is whether, do we need to set flash_recovery_area parameters and log_archive_dest_n parameters to take backup of databases or set only the log_archive_dest_n parameter and enable archive log mode and take backup using RMAN?
Thanks,
Praveen.

Hi,
To use RMAN to take a hot backup you need only set LOG_ARCHIVE_DEST_n and place the database in archive log mode. RMAN can be used to backup changed data even after a nologging operation, and you can move away from archivelog mode.
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10726/configbp.htm
There is also the new "block change tracking" B&R that does not need archivelog mode:
http://www.dba-oracle.com/t_block_change_tracking.htm

Clone database with no archive log mode and downtime with new file structure

We need to clone database with following business requirements :
No downtime at all can be afford
databases are in no archive log mode
data-file locations need to be change to new mount points while cloning for space management factor
Please suggest the best possible methods for same ?

Can you post your version of oracle in 4 digits and OS for better understandig
I dont think you can move the No Archive database to a new location without shutting down.
You just want to move them to the new mount points is it?
1. How big are your datafiles are?
2.How do you backup this DB?
When you move the datafilles then it becomes inconsistent and you need redo logs and probably archive logs to be there to make the file consistent or else it would be prompting for recovery. The chances are your redolog will be overwritten and hence you wont be able to recover.
You need downtime.

Change Archive Log Mode, Restart instance, show ORA-12505 error!!!

We are still use Oracle 9i.
Now we want to use Symantec Backupexec 12 to backup oracle 9i.
In accordance with Backupexec's requirements. must change recovery mode to Archive Log Mode.
I use the Enterprise manager console to change it. and select restart immediately.
a error message be display in the step 2 (starting up the database). see below
ORA-12505: TNS:listener could not resolve SID given in connect descriptor
I'm a new oracle user. Hope you give me some suggestion.
THK.

If database is down, then start it up directly login to server and
sqlplus "/ as sysdba"
startup;
Read this thread for first:
Re: ORA-12505, TNS:listener does not currently know of SID given in connect
The main problem is Your listner doesn't know the sid in connect descriptor.
Check
lsnrctl services
and look in tnsnames.ora file - is there such sercive defined in Your connection description.
issue tnsping in order to check is it able to read and connect correctly tnsnames.ora entry.

Switching to Archive Log Mode

If I have an application that hooks into an Oracle 8.1.7 database running in noarchive mode, would it be transparent to that application if I were to switch oracle to archive log mode? I can't think of anything that would require configuration changes for an application that connects via Net8 but just want to be somewhat sure.
Stu

I agree. However, if you have a problem with the archive like archive dest running out of space, or you forgetting to turn on auto archiving, the application will hang on a log switch. But, these are not problems caused by archivelog mode itself, but rather by improper configuration/administration.

Standby Database (Archive Log Mode)

I'm going to be setting up a standby database.
I understand that the primary database must be in archive log mode.
Is there any reason for the standby database to be in archivelog mode?

Since your primary Db is in archive log mode, so will be your standby, when it is made primary.But. you can use STANDBY REDO LOGS from 9i version, where these Standby Redo Logs then store the information received from the Primary Database.
As per metalink:-
>
Standby Redo Logs are only supported for the Physical Standby Database in Oracle 9i and as well for Logical Standby Databases in 10g. Standby Redo Logs are only used if you have the LGWR activated for archival to the Remote Standby Database.If you have Standby Redo Logs, the RFS process will write into the Standby RedoLog as mentioned above and when a log switch occurs, the Archiver Process of the Standby Database will archive this Standby Redo Log to an Archived Redo Log, while the MRP process applies the information to the Standby Database. In a Failover situation, you will also have access to the information already written in the Standby Redo Logs, so the information will not be lost.
>
Check metalink Doc ID: Note:219344.1
Regards,
Anand

Is the only way to import large amount of data and database objects into a primary database is to shutdown the standby, turn off archive log mode, do the import, then rebuild the standby?

I have a primary database that need to import large amount of data and database objects. 1.) Do I shutdown the standby? 2.) Turn off archive log mode? 3.) Perform the import? 4.) Rebuild the standby? or is there a better way or best practice?

Instead of rebuilding the (whole) standby, you take an incremental (from SCN) backup from the Primary and restore it on the Standby. That way, if, for example
a. Only two out of 12 tablespaces are affected by the import, the incremental backup would effectively be only the blocks changed in those two tablespaces (and some other changes in system and undo) {provided that there are no other changes in the other ten tablespaces}
b. if the size of the import is only 15% of the database, the incremental backup to restore to the standby is small
Hemant K Chitale

Archive log mode in oracle 10g

Hi,
I would like to know the archive log mode in oracle 10g and I use this code in SQLPlus
select log_mode from v$database
But it displayed: "2" not : NOARCHIVELOG or ARCHIVELOG
It displayed a number, not a String.
How could I know this?
Thanks

Hi Paul
Because I am a newbie in DBA Oracle so I got many difficulties.
You are very kind to help me.
So I have some more questions:
1. when I executed this code, it always reported error:
$ tmp=`${ORACLE_HOME}/bin/sqlplus -s / as sysdba << EOF
set heading off feedback off;
exit
EOF`
tmp='ERROR:
ORA-01031: insufficient privileges
SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
where <logon> ::= <username>[<password>][@<connect_identifier>] | /
SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
where <logon> ::= <username>[<password>][@<connect_identifier>] | /
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus'
so when I updated like this:
tmp=`${ORACLE_HOME}/bin/sqlplus -s sys/syspass@db02 as sysdba <<EOF
               set heading off feedback off;
               exit
               EOF`
It run correctly.
2. With Paul's guide:
Do not execute Oracle commands from root, execute them as oracle user. This works to me :
$ tmp=`${ORACLE_HOME}/bin/sqlplus -s / as sysdba << EOF
set heading off feedback off
alter database backup controlfile to '${CONTROLFILE_DIR}/<file name>';
alter database backup controlfile to trace;
exit
EOF`
Of course CONTROLFILE_DIR must be set to a directory with write permission for oracle user.
For ex: I have an Unix account: unix/unix
and a Sys Oracle account: oracle/oracle
I login with Unix acount (unix/unix) and call script file that contains above code.
tmp=`${ORACLE_HOME}/bin/sqlplus -s oracle/oracle@db02 as sysdba <<EOF
               set heading off feedback off
               alter database backup controlfile to '${CONTROLFILE_DIR}/backup_control.ctl';
               alter database backup controlfile to trace;
               exit
               EOF`
Unix report as following: Linux error: 13: Permission denied.
CONTROLFILE_DIR directory is read,write,execute for account unix/unix.
Of course CONTROLFILE_DIR must be set to a directory with write permission for oracle user. You mean I have to create a Unix user is the same to Oracle user so that Oracle user can have permission to write.
Please guilde more detail.
Thanks for your attention.
Message was edited by:
user481034

Archive log mode Turn off

Hi all DBA guys, Have a Nice day all
If i change archive log mode to no archive log mode, internally whats happen my database?.
Is this old archive log backup use for future if again convert no archive to archive log mode?
What's happen flashback if i change archive log mode to no archive log mode?
Regards
S.Azar

azarmohds wrote:
Thanx lot,
why i asked this question means, rightnow you posted, this is feature of 10g i.e flashback database confiured when archive log mode is enabled...,so in this case
What's happen flashback if i change archive log mode to no archive log mode?S.Azar,
You should be clear about things that when you read notes from web, there can be a language mismatch. So the best is that search first over the oracle docs.
Now about your doubt, its a terminology mismatch which is happening here. To enable Flashback Database feature which is more persistent copy of the undo data , stored seperately in a FLB file, you MUST have to have archivelog mode configured in your db. Without this, you can't enable the Flashback Database feature. And you can't switch to noarchive log mode as well if you have Flashback Database mode on.
The other thing ( which I guess Anurag was mentioning ) is the normal Flashback feature which relies on Undo data stored in the undo tablespace. This solely is based on teh undo data and doesn't depend on the archive/nonarchive log mode of the database. But this is limited to that data and to that time period up till which you can store the undo data in your undo tablespace.
HTH
Aman....

Archive log mode in 3 node rac database

Sir I am using oracle 10.2.0.1 and created 3 node cluster setup on.OS i am using linux 4
I am too much confuse in setting up this cluster in archive log mode bec why we need to false cluater_database parameter to setup cluster in archive log mode.
I have search lot of documents but all are saying we not need setting this parameter flase perior to 10.2.But what is the actual concept behind setting this parameter to false in early release and why we need not to set it false.Please help me.
I know how to set up in archive log mode but this parameter create confusion.
Thanks sir in advance

I also dont't know all the details about this but I'll try to explain what I know. Setting cluster_database to false in a rac environment is usually done when you need to mount the database from one instance exclusively. This is still needed when you upgrade the catalog, for example during release update (from 10.2.0.1 to 10.2.0.4 for example). Now with switching archivelog mode someone at oracle must have discovered that it is sufficient when the database is mounted by only one instance and you can actually save one step.
As I (and propably most of you) don't switch archiving on or off on a daily basis, I don't worry about this a lot, simply turn this on when I create a new database and then leave it on forever.
Bjoern

SGEN & database archive log mode

Hi Experts,
To apply ABAP support packs, I disabled archive log mode of databse and successfully applied support packs.
As post processing, I kicked off SGEN.
Is it required that database be in "NO Archive log mode" while SGEN is running or can I enable it.
Thanks
Putla

Not sure what database it is.. but if it is ORACLE...
$sqlplus / as sysdba
SQL> shutdown immediate;
SQL> startup mount;
SQL> Alter database noarchivelog;
SQL> alter database open;
After the completion of SGEN.....
$sqlplus / as sysdba
SQL> shutdown immediate;
SQL> alter database mount;
SQL> alter database archivelog;
SQL> alter database open;

Archive log mode required for async. CDC?

Similar Messages

Maybe you are looking for