ALTER SYSTEM ARCHIVELOG CURRENT

Greeting to all ;
I am trying to froce log switch but i am getting error.
My db version is 10.2.0.4 on Oracle Linux 5.5.
SQL> select GROUP# , ARCHIVED , MEMBERS , STATUS , FIRST_CHANGE# from v$LOG;
    GROUP# ARC    MEMBERS STATUS          FIRST_CHANGE#
         1 YES          1 INACTIVE              1499347
         2 NO           1 CURRENT               1499349
         3 YES          1 INACTIVE              1499344
SQL> ALTER SYSTEM ARCHIVELOG CURRENT;
ALTER SYSTEM ARCHIVELOG CURRENT
ERROR at line 1:
ORA-02065: illegal option for ALTER SYSTEM
SOURCE_LINK : ALTER SYSTEM SWITCH LOGFILE vs ALTER SYSTEM ARCHIVELOG CURRENT
Question 2 :
Each online or archived redo log file is uniquely identified by its log sequence number
Online redo log file LSN and archived redo log LSN - should be same or may different ?
For ex :
Suppose , online redo logfile have bunch of redo entries , - > when log switch occurs , LSN is created.
When those entries reaching archive destination    - > does oracle change LSN ?
Thanks ..

replace yours sequence 16604 with my sequence 46
RMAN> backup validate archivelog from sequence 46 until sequence 46
2> ;
Starting backup at 27-FEB-09
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=143 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=46 recid=42 stamp=679883682
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 27-FEB-09After doing it i opened the archivelog of sequence 46 at editor and deleted some binary info from that and then saved that file.
RMAN> backup validate archivelog from sequence 46 until sequence 46
2> ;
Starting backup at 27-FEB-09
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 02/27/2009 03:05:58
RMAN-06059: expected archived log not found, lost of archived log compromises re
coverability
ORA-19625: error identifying file F:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\P
ROD\ARCHIVELOG\2009_02_27\O1_MF_1_46_4TH9F0OH_.ARC
ORA-27046: file size is not a multiple of logical block size
OSD-04012: file size mismatch (OS 10622798)Khurram

Similar Messages

Remove alter system checkpoint from Backup script

We are seeing high response time when we run alter system checkpoint and when we run "BEGIN BACKUP". Can we remove that from the script currently it's something like:
alter system checkpoint
alter system archive current
begin backup
Also would suspend/resume help if we have it after "begin backup" in response time?
Edited by: user628400 on Mar 26, 2009 5:06 PM

Hi;
It says;
"SQL-induced checkpoints are heavyweight. This means that Oracle records the checkpoint in a control file shared by all the redo threads. Oracle also updates the datafile headers. SQL-induced checkpoints move the checkpoint position to the point that corresponded to the end of the log when the statement was initiated. These checkpoints can adversely affect performance, because the additional writes to the datafiles increase system overhead."
According to my experiences, manually checkpointing has never been a quick operation.
How long it takes to finish checkpoint?

Alter system archive log current

Hi everyone,
I write code to alter system archive log current in PL/SQL as following:
declare
start_sequence number;
end_sequence number;
begin
--- get start sequence# ---
select SEQUENCE# into start_sequence from v_$log where status='CURRENT';
--- get end sequence# ---
alter system archive log current;
select SEQUENCE# into end_sequence from v_$log where status='CURRENT';
end;
When I run it, I got the following error:
alter system archive log current;
ERROR at line 11:
ORA-06550: line 11, column 6:
PLS-00103: Encountered the symbol "ALTER" when expecting one of the following:
begin case declare end exception exit for goto if loop mod
null pragma raise return select update while with
<an identifier> <a double-quoted delimited-identifier>
<a bind variable> << close current delete fetch lock insert
open rollback savepoint set sql execute commit forall merge
pipe
What does it mean? How can I fix it/
Thanks!

That is because you are trying to issue a DDL call in PL/SQL. The only way you can achieve this is to use DYNAMIC SQL.
If you change your ALTER statement to:
EXECUTE IMMEDIATE 'ALTER SYSTEM ARCHIVE LOG CURRENT';It should work.
HTH!

Question about ALTER SYSTEM ARCHIVE LOG START

Good morning,
I'm trying (unsuccessfully) to get my database to be in archive log mode.
These are the steps I followed:
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size                  1375792 bytes
Variable Size             377487824 bytes
Database Buffers          150994944 bytes
Redo Buffers                5804032 bytes
Database mounted.
SQL> select log_mode from v$database;
LOG_MODE
ARCHIVELOG
SQL> show parameter log_archive_start;
NAME                                 TYPE        VALUE
log_archive_start                    boolean     FALSE
SQL> alter system archive log start;
System altered.
SQL> show parameter log_archive_start;
NAME                                 TYPE        VALUE
log_archive_start                    boolean     FALSE
SQL>I've gone thru that process twice but, I don't seem to be able to get the ARCH process to start. (newbie mistake I'm sure...)
Thank you for your help (again!),
John.

The parameter log_archive_start is no more needed John (as suggested already) and the best way to check the archive options is through the archive log list command.
[oracle@edhdr2p0-orcl oui]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Tue Aug 10 10:51:57 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> archive log list
Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     11
Current log sequence           13
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 418484224 bytes
Fixed Size                  1336932 bytes
Variable Size             318769564 bytes
Database Buffers           92274688 bytes
Redo Buffers                6103040 bytes
Database mounted.
SQL> select process,status from V$archive_processes;
   PROCESS STATUS
         0 STOPPED
         1 STOPPED
         2 STOPPED
         3 STOPPED
         4 STOPPED
         5 STOPPED
         6 STOPPED
         7 STOPPED
         8 STOPPED
         9 STOPPED
        10 STOPPED
   PROCESS STATUS
        11 STOPPED
        12 STOPPED
        13 STOPPED
        14 STOPPED
        15 STOPPED
        16 STOPPED
        17 STOPPED
        18 STOPPED
        19 STOPPED
        20 STOPPED
        21 STOPPED
   PROCESS STATUS
        22 STOPPED
        23 STOPPED
        24 STOPPED
        25 STOPPED
        26 STOPPED
        27 STOPPED
        28 STOPPED
        29 STOPPED
30 rows selected.
SQL>
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
archive log list;
Database altered.
SQL> Database log mode         Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     11
Next log sequence to archive   13
Current log sequence           13
SQL>
SQL> select * from V$archive_processes where status <> 'STOPPED';
   PROCESS STATUS     LOG_SEQUENCE STAT
         0 ACTIVE                0 IDLE
         1 ACTIVE                0 IDLE
         2 ACTIVE                0 IDLE
         3 ACTIVE                0 IDLEHTH
Aman....

RMAN ALert Log Message: ALTER SYSTEM ARCHIVE LOG

Created a new Database on Oracle 10.2.0.4 and now seeing "ALTER SYSTEM ARCHIVE LOG" in the Alert Log only when the online RMAN backup runs:
Wed Aug 26 21:52:03 2009
ALTER SYSTEM ARCHIVE LOG
Wed Aug 26 21:52:03 2009
Thread 1 advanced to log sequence 35 (LGWR switch)
Current log# 2 seq# 35 mem# 0: /u01/app/oracle/oradata/aatest/redo02.log
Current log# 2 seq# 35 mem# 1: /u03/oradata/aatest/redo02a.log
Wed Aug 26 21:53:37 2009
ALTER SYSTEM ARCHIVE LOG
Wed Aug 26 21:53:37 2009
Thread 1 advanced to log sequence 36 (LGWR switch)
Current log# 3 seq# 36 mem# 0: /u01/app/oracle/oradata/aatest/redo03.log
Current log# 3 seq# 36 mem# 1: /u03/oradata/aatest/redo03a.log
Wed Aug 26 21:53:40 2009
Starting control autobackup
Control autobackup written to DISK device
handle '/u03/exports/backups/aatest/c-2538018370-20090826-00'
I am not issuing a log swiitch command. The RMAN commands I am running are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/exports/backups/aatest/%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u03/exports/backups/aatest/%d_%U';
BACKUP DATABASE PLUS ARCHIVELOG;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT ARCHIVELOG UNTIL TIME 'SYSDATE-2';
I do not see this message on any other 10.2.0.4 instances. Has anyone seen this and if so why is this showing in the log?
Thank you,
Curt Swartzlander

There's no problem with log switch. Please refer to documentation for more information on syntax "PLUS ARCHIVELOG"
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup003.htm#sthref377
Adding BACKUP ... PLUS ARCHIVELOG causes RMAN to do the following:
*1. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.*
*2. Runs BACKUP ARCHIVELOG ALL. Note that if backup optimization is enabled, then RMAN skips logs that it has already backed up to the specified device.*
*3. Backs up the rest of the files specified in BACKUP command.*
*4. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.*
*5. Backs up any remaining archived logs generated during the backup.*
This guarantees that datafile backups taken during the command are recoverable to a consistent state.

Alter system with scope=both

Hi,
I am trying to enable automatic log archiving at instance start up. I have tried to use the "scope=both" parameter to change both the current session and have it also update the spfile. I tried using this command:
alter system archive log start to 'C:\oracle\ora92\database\dbname\archive' SCOPE=spfile;
However it give me an error at the keyword SCOPE saying:
ERROR at line 1:
ORA-00933: SQL command not properly ended
Any ideas on how to do this or do I have to export the spfile to a pfile, make the changes there and then create the pfile from the spfile ?
Thanks in advance,
Ned

If I change to archivelog mode in Mount state using alter database archivelog;
Will that also automatically set those parameter. Take 10g for example?
By default the destination of archive log files are stored in flash recovery area without any additional configuration. In that case i also assume now that those parameter such as log_archive_start=true will also be automatically be set when the DB is set to archivelog mode (in reference of 10g).
Correct me if i'm wrong...

Alter system set nls_length_semantics

Hi all,
my question concerns the scope in the change of NLS_LENGTH_SEMANTICS can be performed.
The 10gR2 documentation only the
"Modifiable ALTER SESSION"
But what about altering the system and making your own setting to default for all sessions? With which scope?
I tried
alter system set nls_length_semantics='CHAR';
alter system set nls_length_semantics='CHAR' scope=spfile;
alter system set nls_length_semantics='CHAR' scope=both;
None had really any effect. Do I have to bounce the database?

Hello,
Do I have to bounce the database?Yes, you have to shutdown and startup the database.
Else the NLS_LENGTH_SEMANTICS change won't be effective.
You may have more details on the following thread:
nls_database_parameters->nls_length_semantics Help!
There's also an interesting Note from MOS:
Examples and limits of BYTE and CHAR semantics usage (NLS_LENGTH_SEMANTICS) [ID 144808.1]They give many information about NLS_LENGTH_SEMANTICS and the following Bug:
Bug 1488174
Problem: ALTER SYSTEM does not change the setting of NLS_LENGTH_SEMANTICS for the current and new (!) sessions.
Workaround: Don't use ALTER SYSTEM SET NLS_LENGTH_SEMANTICS scope=both; but set NLS_LENGTH_SEMANTICS as a init.ora parameter or issue ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=CHAR scope=spfile; and bounce the database.Hope this help.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on May 27, 2010 2:06 PM

Alter system set shared_pool_size extremely slow.

I am trying to increase my shared_pool_size from 60m to 200m by simply typing alter system set shared_pool_size=200m;
I did alter system flush shared_pool; before to clear out the current shared_pool.
I'm on 9i and my SGA_MAX_SIZE is 3g and I have plenty room to grow.
show sga
Total System Global Area 3222769016 bytes
Fixed Size 744824 bytes
Variable Size 2382364672 bytes
Database Buffers 838860800 bytes
Redo Buffers 798720 bytes
My event in v$session_wait is background parameter adjustment.
Any help would be appreciated. I know that I can bounce the server and let it read it from the init.ora. However, I'm trying to fix some current 4031s in my shared pool. The flush did fix them temporarily.

Are you sure your instance was in the state you thought it was ? This is what you reported from show sga:
Total System Global Area 3222769016 bytes
Fixed Size                    744824 bytes
Variable Size             2382364672 bytes
Database Buffers           838860800 bytes
Redo Buffers                  798720 bytesYou say your shared_pool_size is 60M and you want to grow it to 200M, but the Variable Size in the output above suggests that your shared pool had already grown to about 2.3 GB, so your command would have been trying to shrink it quite dramatically. (And 9i isn't very good at shrinking the shared pool because of the problems of pinned and "KEEP"ed objects in the library cache.
Things to check (from another session):
v$sga_current_resize_ops to see if your resize operation is still running, and what it's trying to do.
v$sga_resize_ops to see i f your resize operation completed some time ago - leaving your session stuck somewhere else. (There's a convenient query I wrote against this view published here: http://jonathanlewis.wordpress.com/2007/04/16/sga-resizing/ )
v$session_wait (for the resize session) to see if the session is waiting or working
v$sesstat (for the resize session) to see if it gives you any clues about current activity
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

Alter system set control_files

when we use this command to multiplex the control files
should we list all the current controls files as well the copied once If yes ,should i performe alter database backup controlfile to trace command ?
Thanks in Advance

If you are working in Oracle8i you can not apply that exact command. That exact command is applicable from Oracle9i. I clarify: The comand ALTER SYSTEM SET ... exists prior to 9i but in 8i that parameter is not dinamic. In order to modify that parameter you have to do so:
1.- Realize what controlfiles you have
2.- Apply the command with the controlfiles that you have additioning the new controlfiles to duplicate. You have to apply this command with SCOPE=SPFILE;
3.- Shutdown the database
4.- Copy the controlfiles with OS
5.- Start the database
Joel Pérez
http://otn.oracle.com/experts

Alter system set events Question

Version 10202 on AIX
sql> alter system set events '4030 trace name heapdump level 536870917; name errorstack level 3';
Questions about this statement..
what this command is doing, i guess creating tracefile for event 4030...& the location of trace file would be the current direcotry?
& how to setup same kind of event trace for other events, any tips....& what to check in tracefile for problem?

The values for level I have record are 1, 2, 3, 8, and 32 so I am guessing the number shown is the address of a specific heap to be dumped. The address of a heap would potentially change with a change in the shared pool storage parameters. Where did you get the address value?
The dump should go to the user background dump destination and not the current directory.
PS - if you have metalink look at document: #218105.1 Introduction to ORACLE Diagnostic EVENTS
HTH -- Mark D Powell --
Message was edited by: MDP add PS to Metalink Doc
mpowel01

Regarding Alter System Kill Session

Hi Guys,
I have to do db refresh from the build .For this I have to kill the sessions and drop the users and recreate the users with the latest build.As the application is running and there are some idle sessions, I have to kill the sessions and drop the users for that I am using a code as below
DECLARE
v_alt_stmt VARCHAR2(1000) := 'ALTER SYSTEM KILL SESSION ''';
v_kill_stmt VARCHAR2(1000);
CURSOR cur_session IS
SELECT s.type type,
s.sid sid,
s.serial# srl_no,
s.username user_name,
s.PROGRAM prog_name
FROM v$session s JOIN gv$process p ON p.addr = s.paddr and s.type='USER';
BEGIN
EXECUTE IMMEDIATE 'ALTER SYSTEM ENABLE RESTRICTED SESSION';
DBMS_OUTPUT.PUT_LINE('The Session has been put in the restricted mode');
FOR v_cur_ssn IN cur_session
LOOP
BEGIN
v_kill_stmt := v_alt_stmt || v_cur_ssn.sid || ',' || v_cur_ssn.srl_no || '''';
DBMS_OUTPUT.PUT_LINE(v_kill_stmt);
EXECUTE IMMEDIATE v_kill_stmt;
EXCEPTION
WHEN others THEN
-- DBMS_OUTPUT.PUT_LINE('The current sessions sid is ' || v_cur_ssn.sid || ' and the srl no is ' || v_cur_ssn.srl_no || ' can not be killed');
END;
END LOOP;
EXECUTE IMMEDIATE 'ALTER SYSTEM DISABLE RESTRICTED SESSION';
DBMS_OUTPUT.PUT_LINE('The restricted mode of the system has been removed');
END;
But sometimes after killing the sessions there are some os processes are going on,to avoid that I have to use 'ALTER SYSTEM DISCONNECT SESSION ''' and 'MMEDIATE' it is workig fine .
Can Any one tell me the logical difference between kill sessions and disconnect
Any information will be highly appreciated.
Thanks in advance
Prafulla

>
Can Any one tell me the logical difference between kill sessions and disconnect
>
Disconnect can be used to disconnect immediately without waiting for any ongoing transactions to complete and recovers all session resousrces.
Kill rolls back ongoing transactions and partially recovers session resources.
Kill is simiilar to SHUTDOWN IMMEDIATE while disconnect is more like SHUTDOWN ABORT.
See DISCONNECT SESSION Clause in the SQL Language doc
http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_2013.htm
>
Use the DISCONNECT SESSION clause to disconnect the current session by destroying the dedicated server process (or virtual circuit if the connection was made by way of a Shared Sever).
•The IMMEDIATE setting disconnects the session and recovers the entire session state immediately, without waiting for ongoing transactions to complete.
>
And KILL SESSION in the same doc next section
>
The KILL SESSION clause lets you mark a session as terminated, roll back ongoing transactions, release all session locks, and partially recover session resources.
IMMEDIATE Specify IMMEDIATE to instruct Oracle Database to roll back ongoing transactions, release all session locks, recover the entire session state, and return control to you immediately.

Alter System Kill Session Not Working

I'm not certain as to what the problem may be, but the following code does not work in that the session is not being disconnected.
The attempt is to have this trigger kill a user's logon session if the user is attempting to run a program named 'ex_oc.exe'
I've tested the code (getting the values back to the table as expected) and it appears to be working but it doesn't execute.
I've also tried ''ALTER SYSTEM DISCONNECT SESSION'.
Database is 11g.
Any ideas?
Thanks
CREATE OR REPLACE TRIGGER SYS.DENY_MSB_TRIGGER_UPDATEDD
AFTER LOGON ON Database
DECLARE
v_programname varchar2(64);
v_logontime date;
v_process varchar2(24);
v_machine varchar2(64);
v_sid number;
v_serialnum number;
v_username varchar2(30);
v_stmt2run VARCHAR2(327);
cur INTEGER;
ret INTEGER;
v_string VARCHAR2(500);
BEGIN
SELECT PROGRAM, PROCESS, MACHINE, SID, SERIAL#, USERNAME
INTO v_programname, v_process, v_machine, v_sid, v_serialnum, v_username
FROM V$SESSION
WHERE PROGRAM = LOWER('ex_oc.exe');
INSERT INTO SAUDIT.DENYMSB (PROGRAM, PROCESS, MACHINE, SID, SERIALNUM, USERNAME)
VALUES (v_programname, v_process, v_machine, v_sid, v_serialnum, v_username );
v_string := 'ALTER SYSTEM KILL SESSION' || CHR(39)||v_sid||','||v_serialnum|| CHR(39)||' IMMEDIATE';
EXECUTE IMMEDIATE v_string;
END;
Edited by: user12451703 on Jan 14, 2010 8:57 AM
Edited by: user12451703 on Jan 14, 2010 8:58 AM

user12451703 wrote:
I'm not trying to kill my own session.
Trigger written by Sys and running it as a generic user.You completely misunderstand triggers. Same as SP/SF trigger is always executed in invoking session on behalf of trigger owner. Below is a slighly modified version of your trigger that does not allow user U1 to connect by killing user U1 session:
SQL> connect scott as sysdba
Enter password: *****
Connected.
SQL> CREATE OR REPLACE TRIGGER SYS.DENY_MSB_TRIGGER_UPDATEDD
2 AFTER LOGON ON Database
3 DECLARE
4 v_programname varchar2(64);
5 v_logontime date;
6 v_process varchar2(24);
7 v_machine varchar2(64);
8 v_sid number;
9 v_serialnum number;
10 v_username varchar2(30);
11 v_stmt2run VARCHAR2(327);
12 cur INTEGER;
13 ret INTEGER;
14 v_string VARCHAR2(500);
15 BEGIN
16 SELECT PROGRAM, PROCESS, MACHINE, SID, SERIAL#, USERNAME
17 INTO v_programname, v_process, v_machine, v_sid, v_serialnum, v_username
18 FROM V$SESSION where username = 'U1';
19 EXECUTE IMMEDIATE ('ALTER SYSTEM KILL SESSION ''' || v_sid || ',' || v_serialnum || '''');
20 EXCEPTION
21 WHEN OTHERS THEN
22 RAISE_APPLICATION_ERROR(-20001, 'Execution of this program not allowed', TRUE);
23 END;
24 /
Trigger created.
SQL> create user u1 identified by u1
2 /
User created.
SQL> grant create session to u1
2 /
Grant succeeded.
SQL> connect u1/u1
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-20001: Execution of this program not allowed
ORA-06512: at line 20
<font color=red size =2>ORA-00027: cannot kill current session</font>
Warning: You are no longer connected to ORACLE.
SQL>
Also, user not that keen to change the name of the exe.Is cex_soc.exe client side executable? If so what prevents user from renaming it?
SY.

Ora-02065:Illegal option for alter system.

Hi Dba's,
I want to setup my database oracle 9i to use "FlashBack".
My database is running in archivelog mode.
First I've shutdown the DB and start it in mount mode.
Then I tried:
SQL> alter system set DB_FLASHBACK_RETENTION_TARGET=1800;
But it doesn't work, I always got the same error:
ora-02065:illegal option for alter system.
I tried to connect as SYS,SYSTEM, everyone, the same error. The users must have FlashBack Privilege and Execute
DBMS_FlashBack privileges. They're OK.
I don't know how to solve this problem?!
If someone could help me. Tks a lot.
Marcello

Marcello:
See this:
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=275083.1
to make sure you have other parameters setup correctly.
Tom Best

Alter system flushed shared pool in RMAN backup

Hi,
I am trying to take RMAN backup of 11.2.0.1 Database in IBM AIX 6.1 server.
The RMAN is hanging .
Though the backup gets completed, The channels allocated doesnt get released and the RMAN gets hanging.
In earlier RMAN backup Scripts,
the DBA was using alter system flush shared pool in RMAN backup script and the backup was getting succesful.
Now my question is , is using ALTER SYSTEM FLUSH SHARED POOL have any performance impact on the database.
Regards,
TEJAS

TEJAS_DBA wrote:
Hi,
I am trying to take RMAN backup of 11.2.0.1 Database in IBM AIX 6.1 server.
The RMAN is hanging .
Though the backup gets completed, The channels allocated doesnt get released and the RMAN gets hanging.Are you setting the large pool? If you don't, then rman uses the shared pool. Read about tuning rman performance in the docs.
>
In earlier RMAN backup Scripts,
the DBA was using alter system flush shared pool in RMAN backup script and the backup was getting succesful.
Now my question is , is using ALTER SYSTEM FLUSH SHARED POOL have any performance impact on the database.Yes, you are allowing the components in there to be loaded in the random order of whatever is called first. This may have a good impact if you had some fragmentation in there, or it could be mildly bad if everything was well sorted, or it could be very bad if you are unlucky or have some pattern of invalidations or should be pinning something or who-knows-what. It generally is considered not a good thing to do as a habit. You wind up with [url http://tkyte.blogspot.com/2012/05/another-debugging-story.html]rainy Monday scenarios.
Edit: I notice there are some bugs, including very slow performance when using a catalog. When you say hang, how long are you waiting? Have you considered current patches?
Edited by: jgarry on Aug 8, 2012 11:09 AM

ALTER SYSTEM

I'm fairly new to Oracle, but i'm enjoying learning these new tips and tricks. When i need to change a parameter which will affect the whole database, what I used to do is to edit the pfile and restart the database. However, lately I got to know that I can do the same thing without restarting the database by using the ALTER SYSTEM technique. Then why we don't all use this technique? Are there some disadvantages? In a particular forum there was also stated that when using this technique on Oracle9i/Oracle10g one must set scope to both. Can someone explain me what this means please? Thanks.
(Ah, my ultimate scope is to be able to set the archive redo log to on, and the 07_DICTIONARY_ACCESSIBILITY parameter to true to be able to use sys - and i want to change these parameters without possibly restarting the database)

There are two types of initialization parameters 1. Dynamic and 2. Static.
Only with the dynamic parameters you don?t have to restart the Database.
For static parameters you have to restart the Database. Moreover the technique of ALTER SYSTEM can be used only with spfile.
Scope = SPFILE: means that the change is effective at the next startup
SCOPE = MEMORY: means that the change is applied in memory only
SCOPE = BOTH: is the default value. The change is applied in both the server parameter file and memory
For static parameters SCOPE = MEMORY and SCOPE = BOTH are not allowed.
Following are the steps to enable archiving.
1. Shut down the database instance.
SHUTDOWN
2. Start the instance and mount, but do not open, the database
STARTUP MOUNT
3. Switch the database's no archiving mode. Then open the database for normal operations.
ALTER DATABASE ARCHIVELOG;
ALTER DATABASE OPEN;
4. Shut down the database.
SHUTDOWN IMMEDIATE
5. Back up the database
To change O7_DICTIONARY_ACCESSIBILITY parameter
ALTER SYSTEM SET O7_DICTIONARY_ACCESSIBILITY = true SCOPE=spfile
Manu

ALTER SYSTEM ARCHIVELOG CURRENT

Similar Messages

Maybe you are looking for