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.

Similar Messages

Changing archive log mode without shutting down database

Hi all,
Is there any way to set the database to archive log mode before shutting down the database and when the database shuts and starts, the database should be automatically in archive log mode?
because we can not shutdown the database in weekdays and we have system reboot on weekend and we are not here on that day. So is there a way to set the database in archive log at the memory level so that when the database reboots, it should automatically start in archive log mode.
my environment is windows server 2008 R2 with oracle 11.2.0.3
Thanks in advance.
Edited by: 931643 on Dec 5, 2012 10:37 AM

931643 wrote:
thank you for the reply Max Seleznev,
First I thought of writing script in order to include in that process. But we can not run any commands in the sqlplus using the windows jobs. for eg:
you can write a batch file as below:
cd \
sqlplus / as sysdba
select name,open_mode from v$database;
when you run this, it will open until sqlplus prompt but then will not execute the query.
What did you expect? Well, actually, I know what you expected. But think about it for a second. You have a batch file with the mentioned three lines. How does that batch file get processed .. what is happening when it is being processed?
It is not being processed by sqlplus, it is being processed by the windows command processor. Just like the cmd.exe. Each line is read by the command processor and executed accordingly. So ....
cd \the command processor calls 'cd' , and passes the value '\' to do with as it sees fit. 'cd' then changes the current directory of the session to whatever is indicated by the passed parameter. in this case, that value is '\' , so the resulting current directory is the base (root, in *nix terms) of the current drive. When 'cd' has finished, it returns control to the command processor, who then reads the next line ....
sqlplus / as sysdbathe command processor calls sqlplus.exe and passes it the command line parms '/ as sysdba' to do with as it (sqlplus) sees fit. sqlplus does whatever it does with what it has been given In this case it tries to connect to whatever local database is indicated by the value of ORACLE_SID, then waits for more input. Whenever sqlplus exits (how does it know to exit?) it returns control to the command processor, who then reads the next line ....
select name,open_mode from v$database;The command processor will read this line and attempt to find an executable file named 'select' and pass it the rest of the command line 'name,open_mode from v$database;'
Hmm, what do you suppose will happen with that operation?
that is the reason I am figuring out whether there is an alternate way.yes but you have to use the proper technique. And since you are building this into a production stop/start without testing the actual stop/start commands ... what do you suppose will be the outcome if something goes wrong?
After hours and weekend work is one reason DBA's make more money than developers.
>
Thanks

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 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;

Putting a Oracle RAC in to archive log mode??

Our RAC is a 10gR2 Three(3) node RAC with a SAN as the shared storage. cluster is installed on linux. at the moment the RAC is in noarchieve log mode.
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /u01/app/oracle/product/10.2.
0/db_1/dbs/arch
Oldest online log sequence 665
Current log sequence 666
we created raw partitions in SAN and use ASM to manage shared storage.
when running DBCA at "specify locations for the database files to be created" step we selected "use oracle managed files" and gave database area = +DATA/
then at choose the recovery options for the database" step we ticked specify flash recovery area and gave Flash Recovery AREA = +BACKUP/ and flash recovery area = 10240 MB. we didnt click "enable archiving" option. hence the RAC DB is in NOARCHIEVELOG mode.
i found some guide to put RAC in archive log mode which i have given below....
ALTER SYSTEM SET log_archive_start=TRUE SCOPE=spfile;
ALTER SYSTEM SET log_archive_dest_1='location=/u01/oradata/MYSID/archive/' SCOPE=spfile;
ALTER SYSTEM SET log_archive_format='arch_%t_%s.arc' SCOPE=spfile;
Since we need to mount the database in exclusive mode we must also alter the following parameter:
ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
From the command line we can stop the entire cluster using:
srvctl stop database -d MYSID
With the cluster down we can connect to a single node and issue the following commands:
STARTUP MOUNT;
ARCHIVE LOG START;
ALTER DATABASE ARCHIVELOG;
ALTER SYSTEM SET cluster_database=TRUE SCOPE=spfile;
SHUTDOWN IMMEDIATE;
Notice that the CLUSTER_DATABASE parameter has been reset to it's original value. Since the datafiles and spfile are shared between all instances this operation only has to be done from a single node.
From the command line we can now start the cluster again using:
srvctl start database -d MYSID
my main question is about the setting of
ALTER SYSTEM SET log_archive_dest_1='location= ????? ' SCOPE=spfile;
since i have set +BACKUP/ as the FRA during installation how should i define the location of log_archive_dest_1???
many thanks in advance.
regards
Dilan

many thanks for the replies
will the command you posted send the archive logs to the "+BACKUP/" location in my SAN.
if yes how does oracle know that USE_DB_RECOVERY_FILE_DEST = BACKUP/ in my SAN. or how do i set oracle to use BACKUP/ as the USE_DB_RECOVERY_FILE_DEST??
im a newbie to RAC so pls bear with me. also at the moment i get the following outputs from my database.... pls note the bold part below, is the archive destination pointing to a location in my local server?
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /u01/app/oracle/product/10.2.0/db_1/dbs/arch
Oldest online log sequence 665
Current log sequence 666
SQL> show parameter db_recovery;
NAME TYPE VALUE
db_recovery_file_dest string
db_recovery_file_dest_size big integer 0
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string
log_archive_dest_1 string
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
NAME TYPE VALUE
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
NAME TYPE VALUE
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 2
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
standby_archive_dest string ?/dbs/arch

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

SAP DB changing the Log mode to the "Owerwrite mode is ON"

Hi!
I would like to know, which consequences do I have, changing the Log mode to the "Owerwrite mode is ON".
Is that comparable with Oracle's archive mode?
What should I note proccessing so (e.g. to make back up)
I don't use the system in productive mode and would like to save/spare free space on my server....
Thank you very much!
regards
Axel

Hi Marcus,
once again to clarify: I know it from oracle: Is it right that , If I activate in SAP DB "Owerwrite mode is. ON" no new logfiles will be created.
Only the existing logfiles will be overwrtiten.
It means I "save" space, because no new log files a 4,5 GB will be created, is not?
I am not familiar with SAP DB.
How should I proceed with Backup (online, offlne)?
Thank you
regards

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 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

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

When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode

Question :
When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode ?
Example:
Create Tablespace
CREATE SMALLFILE TABLESPACE "TEST_DATA"
LOGGING
DATAFILE '+DG_TEST_DATA_01(DATAFILE)' SIZE 10G
AUTOEXTEND ON NEXT 500K MAXSIZE 31000M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
LOGGING: Generate redo logs for creation of tables, indexes and partitions, and for subsequent inserts. Recoverable
Are they not logged and not recoverable if we do not enable LOGGING? What is that ARCHIVELOG mode does?

What is that ARCHIVELOG Mode Does?
Whenever your database is in archive log mode , Oracle will backup the redo log files in the form of Archives so that we can recover the database to the consistent state in case of any failure.
Archive logging is essential for production databases where the loss of a transaction might be fatal.
Why Logging?
Logging is safest method to ensure that all the changes made at the tablespace will be captured and available for recovery in the redo logs.
It is just the level at which we defines:
Force Logging at DB level
Logging at Tablespace Level
Logging at schema Level
Before the existence of FORCE LOGGING, Oracle provided logging and nologging options. These two options have higher precedence at the schema object level than the tablespace level; therefore, it was possible to override the logging settings at the tablespace level with nologging setting at schema object level.

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.

Help!! I changed my log in screen to show a blank name and pw. Now I cannot open the computer???

Help!! I changed my log in screen to show a blank name and pw. Now I cannot open the computer???

1.Turn on the computer and when you hear the startup chime hold CMD+S. This boots the computer into single-user mode, giving you root access.
2.Once single-user mode loads (it looks like a black screen with white text) mount the hard drive. So at the prompt type in:
/sbin/mount -uw /
3. Now that the drive is mounted we can edit the file system. We need to delete a file that tells your computer that you have completed setup. So type in:
rm /var/db/.applesetupdone
4.We need the system to reboot so it can check for the file and not find it. Type in:
reboot
5.Continue setup
Be sure to select “DO NOT TRANSFER MY DATA”.
6.Finish setup and login.
7. Go to system preferences and edit that account so it HAS A NAME.

ARCHIVED logs mode

hi
how to verify what the the ARCHIVED logs mode of my oracle server?
how to change that mode?
thank you

hi,
sql> select log_mode from v$database;
log_mode
NOARCHIVELOG
And follow these steps to change database mode to archivelog mode.
Issue the following commands to put a database into ARCHVELOG mode:
1) Take Back up of Present SPfile by creating pfile F:\oracle\admin\pfile from present spfile.
2) Shutdown the database by SUTDOWN IMMEDIATE.
3) Take Cold backup of the database in B:\DBBACKUP\NOARCHBKP27_06_07 .
4) Change the parameter in the pfile.
log_archive_start = TRUE
log_archive_dest_1 = 'LOCATION=F:\Backup\Archive'
log_archive_dest_state_1 = ENABLE
log_archive_format = %d_%t_%s.arc
5) And make a spfile from the modified pfile in default location .
6) Start the database with spfile.
SQL> CONNECT sys AS SYSDBA
SQL> STARTUP MOUNT ;
SQL> ALTER DATABASE ARCHIVELOG;
SQL> ARCHIVE LOG START;
SQL> ALTER DATABASE OPEN;
regards
Jafar

After setting the db to archive log mode what to do?

Hi All,
We have a database which is being used as production database since one week and running in NoArchive Log mode. Now i wanted to change that to Archive Log mode because i want to take hot backup using RMAN daily/weekly. My doubt is..after changing the db to Archive Log mode, can i take backup using RMAN (i got a RMAN script to take a hot backup of db)? which will contain all the backup with control files and spfiles? or do i have to do anything before taking hotbackup.
Thanks,
Praveen.

Yes you are fine. BTW, how many archive destinations did you configure.
Usually it is more than 1 on two different Disks.
TEST CASE:
NOARCHIVELOG Database
Change it ARCHIVELOG
Take a hot backup and try to restore/recover it.
STATUS=SUCCES
Can someone explain this to me please:-
Ensure DB in noarchivelog mode
SQL> archive log list
Database log mode No Archive Mode
SQL> startup mount;
SQL> alter database archivelog;
SQL> alter database open;
-- DID Not take a COLD BACKUP
-- Right after switching the mode I am taking hot backup
RMAN> backup incremental level=0 database ;
RMAN> backup archivelog all delete all input;
Nuke the datafiles
RMAN> SET DBID=1299283748;
RMAN> restore controlfile from autobackup;
run
set until logseq=79 ;
restore database;
recover database;
sql 'alter database open resetlogs';
Database is opened restored / recovered?
I totally agree we should take a cold backup right after switching the mode. Can someone explain the above though.
Message was edited by:
gopalora

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

Similar Messages

Maybe you are looking for