Primary Database (Tester)

SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;

SWITCHOVER_STATUS
——————–
SESSIONS ACTIVE

Session Active status means that you have to perform a switchover from WITH SESSION SHUTDOWN clause.It means that many users are still connecting to the database, so perform a session shutdown clause.

SQL> SELECT PROGRAM, TYPE FROM V$SESSION WHERE TYPE=’USER’;

PROGRAM                                                          TYPE
—————————————————————- ———-

SQL> SELECT PROGRAM, TYPE FROM V$SESSION WHERE TYPE=’USER’;

PROGRAM                                                          TYPE
—————————————————————- ———-
emagent.exe                                                      USER
ORACLE.EXE                                                       USER
sqlplus.exe                                                      USER

SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY
  2  WITH SESSION SHUTDOWN;

Database altered.

SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP NOMOUNT
ORACLE instance started.

Total System Global Area  612368384 bytes
Fixed Size                  1250428 bytes
Variable Size             218106756 bytes
Database Buffers          385875968 bytes
Redo Buffers                7135232 bytes
SQL> ALTER DATABASE MOUNT STANDBY DATABASE;

Database altered.

SQL> SHOW PARAMETER DB_NAME

NAME                                 TYPE        VALUE
———————————— ———– ——————————
db_name                              string      tester
SQL> SELECT THREAD#, SEQUENCE#, APPLIED,to_char(COMPLETION_TIME,’DD-MON-YYYY:HH2
4:MI:SS’) FROM V$ARCHIVED_LOG;

   THREAD#  SEQUENCE# APP TO_CHAR(COMPLETION_T
———- ———- — ——————–
         1         29 NO  07-OCT-2011:20:49:17
         1         30 NO  10-OCT-2011:14:29:36
         1         31 NO  11-OCT-2011:21:41:22
         1         32 NO  11-OCT-2011:22:16:18
         1         32 NO  11-OCT-2011:22:16:19
         1         32 NO  11-OCT-2011:22:16:20
         1         33 NO  11-OCT-2011:22:47:50
         1         34 NO  12-OCT-2011:19:18:14
         1         34 NO  12-OCT-2011:19:18:15
         1         34 NO  12-OCT-2011:19:18:16
         1         35 NO  13-OCT-2011:21:06:59

   THREAD#  SEQUENCE# APP TO_CHAR(COMPLETION_T
———- ———- — ——————–
         1         36 NO  14-OCT-2011:09:55:03
         1         37 NO  14-OCT-2011:09:56:02
         1         38 NO  14-OCT-2011:09:56:23
         1         39 NO  14-OCT-2011:10:28:16
         1         39 NO  14-OCT-2011:10:28:17
         1         40 NO  14-OCT-2011:10:28:21
         1         41 NO  14-OCT-2011:21:02:05
         1         41 NO  14-OCT-2011:21:02:07
         1         42 NO  14-OCT-2011:21:02:10
         1         43 NO  14-OCT-2011:21:02:59
         1         44 NO  14-OCT-2011:22:08:59

   THREAD#  SEQUENCE# APP TO_CHAR(COMPLETION_T
———- ———- — ——————–
         1         44 NO  14-OCT-2011:22:09:00
         1         44 NO  14-OCT-2011:22:09:20
         1         41 NO  14-OCT-2011:22:09:40
         1         42 NO  14-OCT-2011:22:09:47
         1         43 NO  14-OCT-2011:22:09:54
         1         45 NO  14-OCT-2011:22:10:47
         1         45 YES 14-OCT-2011:22:11:21
         1         46 NO  15-OCT-2011:19:16:03
         1         46 NO  15-OCT-2011:19:16:04
         1         47 NO  15-OCT-2011:19:16:48
         1         48 NO  15-OCT-2011:19:17:04

   THREAD#  SEQUENCE# APP TO_CHAR(COMPLETION_T
———- ———- — ——————–
         1         49 NO  15-OCT-2011:19:19:13
         1         50 NO  15-OCT-2011:19:20:05
         1         51 NO  15-OCT-2011:19:20:08
         1         52 NO  15-OCT-2011:19:24:21
         1         53 NO  15-OCT-2011:19:24:59
         1         53 NO  15-OCT-2011:19:25:00
         1         46 NO  15-OCT-2011:19:25:11
         1         47 NO  15-OCT-2011:19:25:14
         1         48 NO  15-OCT-2011:19:25:14
         1         49 NO  15-OCT-2011:19:25:18
         1         50 NO  15-OCT-2011:19:25:18

   THREAD#  SEQUENCE# APP TO_CHAR(COMPLETION_T
———- ———- — ——————–
         1         51 NO  15-OCT-2011:19:25:23
         1         52 NO  15-OCT-2011:19:25:28
         1         54 YES 15-OCT-2011:19:26:33
         1         54 NO  15-OCT-2011:19:26:59
         1         55 YES 15-OCT-2011:19:32:00
         1         55 NO  15-OCT-2011:19:32:12
         1         56 YES 15-OCT-2011:19:49:15
         1         56 NO  15-OCT-2011:19:49:26
         1         57 NO  15-OCT-2011:20:05:05
         1         57 NO  15-OCT-2011:20:05:13
         1         58 NO  15-OCT-2011:20:06:58

   THREAD#  SEQUENCE# APP TO_CHAR(COMPLETION_T
———- ———- — ——————–
         1         58 NO  15-OCT-2011:20:06:59

56 rows selected.

SQL> SELECT THREAD#, MAX(SEQUENCE#) AS “LAST_APPLIED_LOG”    FROM V$LOG_HISTORY
    GROUP BY
  2  THREAD#;

   THREAD# LAST_APPLIED_LOG
———- —————-
         1               57

SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_S
TANDBY;

PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
——— ———— ———- ———- ———- ———-
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0

SQL>  alter database recover managed standby database disconnect from session;
 alter database recover managed standby database disconnect from session
*
ERROR at line 1:
ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected
SQL>  alter database recover managed standby database;
Previous standby
—————————-

 Here we are performing a switchover from standby to primary database.

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

Database altered.

SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;

SWITCHOVER_STATUS
——————–
TO PRIMARY

SQL> alter database commit to switchover to primary;

Database altered.

SQL> SHUTDOWN IMMEDIATE
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP
ORACLE instance started.

Total System Global Area  612368384 bytes
Fixed Size                  1250428 bytes
Variable Size             180358020 bytes
Database Buffers          423624704 bytes
Redo Buffers                7135232 bytes
Database mounted.
Database opened.
SQL> SHOW PARAMETER DB_NAME

NAME                                 TYPE        VALUE
———————————— ———– ——————————
db_name                              string      TESTER
SQL> SHOW PARAMETER DB_UNI

NAME                                 TYPE        VALUE
———————————— ———– ——————————
db_unique_name                       string      STANDBY
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;

SWITCHOVER_STATUS
——————–
SESSIONS ACTIVE

SQL> ALTER SYSTEM SWITCH LOGFILE;

System altered.

SQL> SELECT THREAD#, SEQUENCE#, APPLIED,to_char(COMPLETION_TIME,’DD-MON-YYYY:HH2
4:MI:SS’) FROM V$ARCHIVED_LOG;

   THREAD#  SEQUENCE# APP TO_CHAR(COMPLETION_T
———- ———- — ——————–
         1         44 YES 14-OCT-2011:22:09:37
         1         41 YES 14-OCT-2011:22:09:39
         1         42 YES 14-OCT-2011:22:09:46
         1         43 YES 14-OCT-2011:22:09:53
         1         45 YES 14-OCT-2011:22:11:23
         1         53 YES 15-OCT-2011:19:25:00
         1         46 YES 15-OCT-2011:19:25:10
         1         47 YES 15-OCT-2011:19:25:14
         1         48 YES 15-OCT-2011:19:25:14
         1         49 YES 15-OCT-2011:19:25:18
         1         50 YES 15-OCT-2011:19:25:18

   THREAD#  SEQUENCE# APP TO_CHAR(COMPLETION_T
———- ———- — ——————–
         1         51 YES 15-OCT-2011:19:25:22
         1         52 YES 15-OCT-2011:19:25:28
         1         54 YES 15-OCT-2011:19:26:46
         1         55 YES 15-OCT-2011:19:32:05
         1         56 YES 15-OCT-2011:19:49:18
         1         57 YES 15-OCT-2011:20:05:08
         1         58 YES 15-OCT-2011:20:06:57
         1         59 NO  15-OCT-2011:20:18:21

19 rows selected.

SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_S
TANDBY;

PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
——— ———— ———- ———- ———- ———-
ARCH      CLOSING               1         59          1        657
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0

SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;

SWITCHOVER_STATUS
——————–
SESSIONS ACTIVE

Now, lets perform a switchover operation using DGMGRL(Data Guard Manager Role)

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>dgmgrl
DGMGRL for 32-bit Windows: Version 10.2.0.1.0 – Production

Copyright (c) 2000, 2005, Oracle. All rights reserved.

Welcome to DGMGRL, type “help” for information.
DGMGRL> connect sys/oracle@tester
Connected.
DGMGRL> show configuration

Configuration
  Name:                primary
  Enabled:             YES
  Protection Mode:     MaxPerformance
  Fast-Start Failover: DISABLED
  Databases:
    tester  – Primary database
    standby – Physical standby database

Current status for “primary”:
SUCCESS

DGMGRL> switchover to standby
Performing switchover NOW, please wait…
Operation requires shutdown of instance “tester” on database “tester”
Shutting down instance “tester”…
ORA-01109: database not open

Database dismounted.
ORACLE instance shut down.
Operation requires shutdown of instance “standby” on database “standby”
Shutting down instance “standby”…
ORA-01109: database not open

Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance “tester” on database “tester”
Starting instance “tester”…
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor

Failed.
You are no longer connected to ORACLE
Please connect again.
Unable to start instance “tester”
You must start instance “tester” manually
Operation requires startup of instance “standby” on database “standby”
You must start instance “standby” manually
Switchover succeeded, new primary is “standby”
DGMGRL> connect sys/oracle@standby
Connected.
DGMGRL> show configuration

Configuration
  Name:                primary
  Enabled:             YES
  Protection Mode:     MaxPerformance
  Fast-Start Failover: DISABLED
  Databases:
    tester  – Physical standby database
    standby – Primary database

Current status for “primary”:
SUCCESS

DGMGRL>

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>set oracle_sid=tester

C:\Documents and Settings\Administrator>sqlplus “/as sysdba”

SQL*Plus: Release 10.2.0.1.0 – Production on Wed Oct 19 18:24:36 2011

Copyright (c) 1982, 2005, Oracle.  All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – Production
With the Partitioning, OLAP and Data Mining options

SQL> exit
ERROR:
ORA-03113: end-of-file on communication channel
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – P
oduction
With the Partitioning, OLAP and Data Mining options (with complications)

C:\Documents and Settings\Administrator>sqlplus “/as sysdba”

SQL*Plus: Release 10.2.0.1.0 – Production on Wed Oct 19 18:35:31 2011

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup nomount
ORACLE instance started.

Total System Global Area  612368384 bytes
Fixed Size                  1250428 bytes
Variable Size             197135236 bytes
Database Buffers          406847488 bytes
Redo Buffers                7135232 bytes
SQL> alter database mount standby database;

Database altered.

SQL> show parameter db_uniq

NAME                                 TYPE        VALUE
———————————— ———– ——————————
db_unique_name                       string      tester
SQL>

SQL> select database_role from v$database;

DATABASE_ROLE
—————-
PHYSICAL STANDBY

SQL>
Previous  Standby Database

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>set oracle_sid=standby

C:\Documents and Settings\Administrator>sqlplus “/as sysdba”

SQL*Plus: Release 10.2.0.1.0 – Production on Wed Oct 19 18:26:09 2011

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup nomount
ORACLE instance started.

Total System Global Area  612368384 bytes
Fixed Size                  1250428 bytes
Variable Size             184552324 bytes
Database Buffers          419430400 bytes
Redo Buffers                7135232 bytes
SQL> alter database mount standby database;

Database altered.

SQL> startup
ORA-03113: end-of-file on communication channel
SQL> conn / as sysdba
Connected to an idle instance.
SQL> startup
ORACLE instance started.

Total System Global Area  612368384 bytes
Fixed Size                  1250428 bytes
Variable Size             184552324 bytes
Database Buffers          419430400 bytes
Redo Buffers                7135232 bytes
Database mounted.
Database opened.
SQL> select database_role from v$database;

DATABASE_ROLE
—————-
PRIMARY

See, in the above we can see that Database Role here has been switched from Standby Role to Primary Role.

SQL> show parameter db_name

NAME                                 TYPE        VALUE
———————————— ———– ——————————
db_name                              string      TESTER
SQL>

SQL> Select Low_Sequence#,High_Sequence# From V$Archive_Gap;

LOW_SEQUENCE# HIGH_SEQUENCE#
————- ————–
         1641           1646

If you are not having the archive logs at your standby database, the just copy or ftp the logs from primary to standby database.

SQL> alter database register logfile ‘/arch/icai/icai_1_1641.dbf’;

Database altered.

SQL> alter database register logfile ‘/arch/icai/icai_1_1642.dbf’;

Database altered.

SQL> alter database register logfile ‘/arch/icai/icai_1_1643.dbf’;

Database altered.

SQL> alter database register logfile ‘/arch/icai/icai_1_1644.dbf’;

Database altered.

SQL> alter database register logfile ‘/arch/icai/icai_1_1645.dbf’;

Database altered.

SQL> alter database register logfile ‘/arch/icai/icai_1_1646.dbf’;

Database altered.

After the redo logs have been registered on the physical standby database, the DBA can restart the managed recovery operations. For example, to put the physical standby database into automatic recovery managed mode:

SQL> alter database recover managed standby database disconnect from session;
 

SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_S
TANDBY;
PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
——— ———— ———- ———- ———- ———-
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
MRP0      APPLYING_LOG          1       1641     307197     307198
RFS       RECEIVING             0          0          0          0

I was facing one issue at the time of log applying to physical standby database.I am getting a message in alert log file “restarting dead background process qmn0 “.MRP is not able to applying the specific log to the standby database.

Tue May  3 13:18:38 2011
alter database recover managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process
MRP0 started with pid=15, OS id=29345
MRP0: Background Managed Standby Recovery process started
Media Recovery Waiting for thread 1 seq# 1641
Fetching gap sequence for thread 1, gap sequence 1641-1646
Trying FAL server: prim
Tue May  3 13:18:44 2011
Completed: alter database recover managed standby database di
Tue May  3 13:18:59 2011
Failed to request gap sequence. Thread #: 1, gap sequence: 1641-1646
All FAL server has been attempted.
Tue May  3 13:22:51 2011
Restarting dead background process QMN0
QMN0 started with pid=14, OS id=29398
Tue May  3 13:28:54 2011
Restarting dead background process QMN0

QMN0 started with pid=14, OS id=29404
Tue May  3 13:34:57 2011
Restarting dead background process QMN0
QMN0 started with pid=14, OS id=29406
Tue May  3 13:41:00 2011
Restarting dead background process QMN0
QMN0 started with pid=14, OS id=29408
Tue May  3 13:47:03 2011
Restarting dead background process QMN0
QMN0 started with pid=14, OS id=29410
Tue May  3 13:53:04 2011
Restarting dead background process QMN0
QMN0 started with pid=14, OS id=29412
Tue May  3 13:59:07 2011
Restarting dead background process QMN0
QMN0 started with pid=14, OS id=29414
Tue May  3 14:05:10 2011
Restarting dead background process QMN0
QMN0 started with pid=14, OS id=29418
Tue May  3 14:11:13 2011
Restarting dead background process QMN0
QMN0 started with pid=14, OS id=29420
Tue May  3 14:17:16 2011
Restarting dead background process QMN0

Solution:

If you don’t use Advanced Queueing you can set it to 0:

alter system set aq_tm_processes=0 scope=both;

The LOG_ARCHIVE_DEST_n database initialization parameter (where n is an integer from 1 to 10) is used to specify the location of a local archive redo log or to specify a redo transport destination. This section describes the latter use of this parameter.

There is a LOG_ARCHIVE_DEST_STATE_n database initialization parameter (where n is an integer from 1 to 10) that corresponds to each LOG_ARCHIVE_DEST_n parameter. This parameter is used to enable or disable the corresponding redo destination. Table 6-1 shows the valid values that can be assigned to this parameter.

A redo transport destination is configured by setting the LOG_ARCHIVE_DEST_n parameter to a character string that includes one or more attributes. This section briefly describes the most commonly used attributes. See Chapter 15 for a full description of all LOG_ARCHIVE_DEST_n parameter attributes.

The SERVICE attribute, which is a mandatory attribute for a redo transport destination, must be the first attribute specified in the attribute list. The SERVICE attribute is used to specify the Oracle Net service name used to connect to a redo transport destination. See the Oracle Database Net Services Administrator’s Guide for information about Oracle Net service names.

The SYNC attribute is used to specify that the synchronous redo transport mode be used to send redo data to a redo transport destination.

The ASYNC attribute is used to specify that the asynchronous redo transport mode be used to send redo data to a redo transport destination. The asynchronous redo transport mode will be used if neither the SYNC nor the ASYNC attribute is specified.

The NET_TIMEOUT attribute is used to specify how long the LGWR process will block waiting for an acknowledgement that redo data has been successfully received by a destination that uses the synchronous redo transport mode. If an acknowledgement is not received within NET_TIMEOUT seconds, the redo transport connection is terminated and an error is logged.

Oracle recommends that the NET_TIMEOUT attribute be specified whenever the synchronous redo transport mode is used, so that the maximum duration of a redo source database stall caused by a redo transport fault can be precisely controlled. SeeSection 6.3.2 for information about monitoring synchronous redo transport mode response time.

The AFFIRM attribute is used to specify that redo received from a redo source database is not acknowledged until it has been written to the standby redo log. The NOAFFIRM attribute is used to specify that received redo is acknowledged without waiting for received redo to be written to the standby redo log.

The DB_UNIQUE_NAME attribute is used to specify the DB_UNIQUE_NAME of a redo transport destination. The DB_UNIQUE_NAMEattribute must be specified if the LOG_ARCHIVE_CONFIG database initialization parameter has been defined and its value includes a DG_CONFIG list.

If the DB_UNIQUE_NAME attribute is specified, its value must match one of the DB_UNIQUE_NAME values in the DG_CONFIG list. It must also match the value of the DB_UNIQUE_NAME database initialization parameter at the redo transport destination. If either match fails, an error is logged and redo transport will not be possible to that destination.

The VALID_FOR attribute is used to specify when redo transport services transmits redo data to a redo transport destination. Oracle recommends that the VALID_FOR attribute be specified for each redo transport destination at every site in a Data Guard configuration so that redo transport services will continue to send redo data to all standby databases after a role transition, regardless of which standby database assumes the primary role.

The REOPEN attribute is used to specify the minimum number of seconds between automatic reconnect attempts to a redo transport destination that is inactive because of a previous error.

The COMPRESSION attribute is used to specify that redo data is transmitted to a redo transport destination in compressed form when resolving redo data gaps. Redo transport compression can significantly improve redo gap resolution time when network links with low bandwidth and high latency are used for redo transport. Redo gap resolution is discussed in Section 6.3.3.

The following example uses all of the LOG_ARCHIVE_DEST_n attributes described in this section. Two redo transport destinations are defined and enabled. The first destination uses the asynchronous redo transport mode. The second destination uses the synchronous redo transport mode with a 30-second timeout. A DB_UNIQUE_NAME has been specified for both destinations, as has the use of compression when resolving redo gaps. If a redo transport fault occurs at either destination, redo transport will attempt to reconnect to that destination, but not more frequently than once every 60 seconds.

DB_UNIQUE_NAME=BOSTON
LOG_ARCHIVE_CONFIG='DG_CONFIG=(BOSTON,CHICAGO,DENVER)'
LOG_ARCHIVE_DEST_2='SERVICE=CHICAGO ASYNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILE,  PRIMARY_ROLE) REOPEN=60 COMPRESSION=ENABLE  DB_UNIQUE_NAME=CHICAGO'
LOG_ARCHIVE_DEST_STATE_2='ENABLE'
LOG_ARCHIVE_DEST_3='SERVICE=DENVER SYNC AFFIRM NET_TIMEOUT=30 VALID_FOR=(ONLINE_LOGFILE,PRIMARY_ROLE) REOPEN=60 COMPRESSION=ENABLE  DB_UNIQUE_NAME=DENVER'
LOG_ARCHIVE_DEST_STATE_3='ENABLE'

Taken from http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/log_transport.htm

To display a list of networks
oifcfg getif
eth1  10.0.2.0  global  cluster_interconnect
eth0  10.0.1.0.  global  public

display a list of current subnets
oifcfg iflist
etho  10.0.1.0
ethl  10.0.2.0

To include a description of the subnet, specify the -p option:
oifcfg iflist -p
ethO  10.0.1.0  PRIVATE
ethl  10.0.2.0 PRIVATE

In 10.2 public interfaces are UNKNOWN.
To include the subnet mask, append the -n option to the -p option:
oifcfg if list -p -n
etho  10.0.1.0  PRIVATE  255.255.255.0
ethl  10.0.2.0 PRIVATE   255.255.255.0

$srvctl add service -d racdb -s oltp -r rac1 -a rac2

$lsnrctl services |grep oltp

Not Found

$srvctl start service -d racdb -s oltp

$./crs_stat

NAME=ora.racdb.oltp.cs

TYPE=application

TARGET=ONLINE

STATE=ONLINE on rac1

NAME=ora-racdb.racdb1.srv

TYPE=application

TARGET=ONLINE

STATE=ONLINE on rac1

NAME                                 TYPE        VALUE
———————————— ———– ——————————
control_file_record_keep_time        integer     7
control_files                        string      +DATA/dbtest/controlfile/curre
nt.261.720140771
SQL> alter system checkpoint;

System altered.

SQL> select name from v$controlfile;

NAME
——————————————————————————–
+DATA/dbtest/controlfile/current.261.720140771

SQL> alter system set control_files=’+DATA/dbtest/controlfile/current.261.720140771′,’+DATA’ scope=spfile;

System altered.

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount
ORACLE instance started.

Total System Global Area  167772160 bytes
Fixed Size                  2019288 bytes
Variable Size              88080424 bytes
Database Buffers           71303168 bytes
Redo Buffers                6369280 bytes
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – 64bit Production
With the Partitioning, OLAP and Data Mining options
-bash-3.2$ export ORACLE_SID=+ASM
-bash-3.2$ asmcmd
ASMCMD> cd data
ASMCMD> cd dbtest
ASMCMD> ls
ARCHIVELOG/
CONTROLFILE/
DATAFILE/
FLASHBACK/
ONLINELOG/
PARAMETERFILE/
TEMPFILE/
spfiledbtest.ora
ASMCMD> cd controlfile
ASMCMD> ls
Current.260.720140773
Current.261.720140771
backup.311.723005013
backup.324.722927111
ASMCMD> ls -l
Type         Redund  Striped  Time             Sys  Name
CONTROLFILE  HIGH    FINE     JUN 29 05:00:00  Y    Current.260.720140773
CONTROLFILE  HIGH    FINE     JUN 30 02:00:00  Y    Current.261.720140771
CONTROLFILE  HIGH    FINE     JUN 30 02:00:00  Y    backup.311.723005013
CONTROLFILE  HIGH    FINE     JUN 29 05:00:00  Y    backup.324.722927111
ASMCMD> exit
-bash-3.2$ sqlplus “/as sysdba”

SQL*Plus: Release 10.2.0.1.0 – Production on Wed Jun 30 02:45:48 2010

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

alte
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – 64bit Production
With the Partitioning, OLAP and Data Mining options

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – 64bit Production
With the Partitioning, OLAP and Data Mining options
-bash-3.2$ export ORACLE_SID=dbtest
-bash-3.2$ sqlplus “/as sysdba”

SQL*Plus: Release 10.2.0.1.0 – Production on Wed Jun 30 02:46:12 2010

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – 64bit Production
With the Partitioning, OLAP and Data Mining options

SQL> alter database open;

Database altered.

SQL> alter system set control_files=’+DATA/dbtest/controlfile/current.261.720140771′,’+data/dbtest/controlfile/backup.311.723005013′ scope=spfile;

System altered.

SQL> select name from v$cnotrolfile;
select name from v$cnotrolfile
*
ERROR at line 1:
ORA-00942: table or view does not exist

SQL> select name from v$controlfile;

NAME
——————————————————————————–
+DATA/dbtest/controlfile/current.261.720140771
+DATA/dbtest/controlfile/backup.311.723005013

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area  167772160 bytes
Fixed Size                  2019288 bytes
Variable Size              92274728 bytes
Database Buffers           67108864 bytes
Redo Buffers                6369280 bytes
Database mounted.
Database opened.
SQL> select name from v$controlfile;

NAME
——————————————————————————–
+DATA/dbtest/controlfile/current.261.720140771
+DATA/dbtest/controlfile/backup.311.723005013

SQL>

STARTED EMCA at Jun 9, 2010 11:47:51 PM
EM Configuration Assistant, Version 10.2.0.1.0 Production
Copyright (c) 2003, 2005, Oracle.  All rights reserved.

Enter the following information:
Database SID: dbtest
Listener port number: 1521
Password for SYS user:
Password for SYSMAN user:

Do you wish to continue? [yes(Y)/no(N)]: Yes
Jun 9, 2010 11:48:28 PM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/app/oracle/product/10.1.0/db_1/cfgtoollogs/emca/dbtest/emca_2010-06-09_11-47-50-PM.log.
Jun 9, 2010 11:48:31 PM oracle.sysman.emcp.util.DBControlUtil stopOMS
INFO: Stopping Database Control (this may take a while) …
Jun 9, 2010 11:48:48 PM oracle.sysman.emcp.EMReposConfig dropRepository
INFO: Dropping the EM repository (this may take a while) …
Jun 9, 2010 11:55:17 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully dropped
Enterprise Manager configuration completed successfully
FINISHED EMCA at Jun 9, 2010 11:55:20 PM
-bash-3.2$ emca -deconfig dbcontrol db -repos create;

STARTED EMCA at Jun 9, 2010 11:55:46 PM
EM Configuration Assistant, Version 10.2.0.1.0 Production
Copyright (c) 2003, 2005, Oracle.  All rights reserved.

Incorrect usage.  Run ‘emca -help’ for more details.
-bash-3.2$ emca -deconfig dbcontrol db -repos create

STARTED EMCA at Jun 9, 2010 11:55:53 PM
EM Configuration Assistant, Version 10.2.0.1.0 Production
Copyright (c) 2003, 2005, Oracle.  All rights reserved.

Incorrect usage.  Run ‘emca -help’ for more details.
-bash-3.2$ emca -config dbcontrol db -repos create

STARTED EMCA at Jun 9, 2010 11:56:02 PM
EM Configuration Assistant, Version 10.2.0.1.0 Production
Copyright (c) 2003, 2005, Oracle.  All rights reserved.

Enter the following information:
Database SID: dbtest
Listener port number: 1521
Password for SYS user:
Password for DBSNMP user:
Password for SYSMAN user:
Email address for notifications (optional):
Outgoing Mail (SMTP) server for notifications (optional):
ASM ORACLE_HOME [ /u01/app/oracle/product/10.1.0/db_1 ]:
ASM SID [ +ASM ]:
ASM port [ 1521 ]:
ASM user role [ SYSDBA ]:
ASM username [ SYS ]:
ASM user password:
—————————————————————–

You have specified the following settings

Database ORACLE_HOME ……………. /u01/app/oracle/product/10.1.0/db_1

Database hostname ……………. localhost.localdomain
Listener port number ……………. 1521
Database SID ……………. dbtest
Email address for notifications ……………
Outgoing Mail (SMTP) server for notifications ……………
ASM ORACLE_HOME ……………. /u01/app/oracle/product/10.1.0/db_1
ASM SID ……………. +ASM
ASM port ……………. 1521
ASM user role ……………. SYSDBA
ASM username ……………. SYS

—————————————————————–
Do you wish to continue? [yes(Y)/no(N)]: Y
Jun 9, 2010 11:58:37 PM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/app/oracle/product/10.1.0/db_1/cfgtoollogs/emca/dbtest/emca_2010-06-09_11-56-02-PM.log.
Jun 9, 2010 11:58:42 PM oracle.sysman.emcp.EMReposConfig createRepository
INFO: Creating the EM repository (this may take a while) …
Jun 10, 2010 12:06:15 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully created
Jun 10, 2010 12:07:02 AM oracle.sysman.emcp.util.DBControlUtil startOMS
INFO: Starting Database Control (this may take a while) …
Jun 10, 2010 12:09:41 AM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: Database Control started successfully
Jun 10, 2010 12:10:02 AM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: >>>>>>>>>>> The Database Control URL is http://localhost.localdomain:5500/em <<<<<<<<<<<
Enterprise Manager configuration completed successfully
FINISHED EMCA at Jun 10, 2010 12:10:04 AM

NAME
——————————
SYSTEM
UNDOTBS1
SYSAUX
USERS
TEMP

SQL> select name from v$datafile;

NAME
——————————————————————————–
+DATA1/nonasmtoasm/datafile/system.259.721108803
+DATA1/nonasmtoasm/datafile/undotbs1.261.721108865
+DATA1/nonasmtoasm/datafile/sysaux.260.721108841
+DATA1/nonasmtoasm/datafile/users.262.721108873

You have to define diskgroup name while adding datafile

SQL> select name from v$asm_diskgroup;

NAME
——————————
DATA1
DATA

Above we are having two asm diskgorup

SQL> alter tablespace users add datafile ‘+data1′ size 5M;

Tablespace altered.

SQL> select name from v$datafile;

NAME
——————————————————————————–
+DATA1/nonasmtoasm/datafile/system.259.721108803
+DATA1/nonasmtoasm/datafile/undotbs1.261.721108865
+DATA1/nonasmtoasm/datafile/sysaux.260.721108841
+DATA1/nonasmtoasm/datafile/users.262.721108873
+DATA1/nonasmtoasm/datafile/users.269.721187971

SQL>

[root@localhost ~]# su – oracle
-bash-3.2$ export ORACLE_SID=+asm
-bash-3.2$ sqlplus “/as sysdba”

SQL*Plus: Release 10.2.0.1.0 – Production on Mon Jun 7 02:51:44 2010

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup mount
ASM instance started

Total System Global Area  130023424 bytes
Fixed Size                  2019032 bytes
Variable Size             102838568 bytes
ASM Cache                  25165824 bytes
ASM diskgroups mounted
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – 64bit Production
With the Partitioning, OLAP and Data Mining options
-bash-3.2$ export ORACLE_SID=dbtest
-bash-3.2$ sqlplus “/as sysdba”

SQL*Plus: Release 10.2.0.1.0 – Production on Mon Jun 7 02:52:26 2010

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area  167772160 bytes
Fixed Size                  2019288 bytes
Variable Size              96469032 bytes
Database Buffers           62914560 bytes
Redo Buffers                6369280 bytes
Database mounted.
ORA-16038: log 3 sequence# 13 cannot be archived
ORA-19504: failed to create file “”
ORA-00312: online log 3 thread 1:
‘+DATA/dbtest/onlinelog/group_3.266.720140799′
ORA-00312: online log 3 thread 1:
‘+DATA/dbtest/onlinelog/group_3.267.720140805′

Cause of The Problem:
—————————————-
There was an attempt to archived the online log 3 but it could not archive the online log in the available archived log destination. The most common of happening the error is the archive log destination if full. You have flash recovery area configured and rman retention policy is failed to delete any archived or incremental backups and so can’t archived new online log.

Solution – Increase dynamically (without shutdown/startup database) the parameter db_recovery_file_dest_size and delete unwanted archivel log files to free up the space.
SQL> select * from v$asm_client;

GROUP_NUMBER INSTANCE_NAME
———— —————————————————————-
DB_NAME  STATUS
——– ————
SOFTWARE_VERSION
————————————————————
COMPATIBLE_VERSION
————————————————————
1 +asm
dbtest   CONNECTED
10.2.0.1.0
10.2.0.0.0

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – 64bit Production
With the Partitioning, OLAP and Data Mining options
-bash-3.2$ asmcmd
asmcmd: command disallowed by current instance type
-bash-3.2$ sqlplus “/as sysdba”

SQL*Plus: Release 10.2.0.1.0 – Production on Mon Jun 7 02:57:53 2010

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – 64bit Production
With the Partitioning, OLAP and Data Mining options

SQL> select * from v$logfile;

GROUP# STATUS  TYPE
———- ——- ——-
MEMBER
——————————————————————————–
IS_
—
3         ONLINE
+DATA/dbtest/onlinelog/group_3.266.720140799
NO

3         ONLINE
+DATA/dbtest/onlinelog/group_3.267.720140805
YES

GROUP# STATUS  TYPE
———- ——- ——-
MEMBER
——————————————————————————–
IS_
—

2 STALE   ONLINE
+DATA/dbtest/onlinelog/group_2.264.720140789
NO

2 STALE   ONLINE
+DATA/dbtest/onlinelog/group_2.265.720140793

GROUP# STATUS  TYPE
———- ——- ——-
MEMBER
——————————————————————————–
IS_
—
YES

1         ONLINE
+DATA/dbtest/onlinelog/group_1.262.720140777
NO

1         ONLINE

GROUP# STATUS  TYPE
———- ——- ——-
MEMBER
——————————————————————————–
IS_
—
+DATA/dbtest/onlinelog/group_1.263.720140783
YES

6 rows selected.

SQL> SELECT * FROM V$RECOVERY_FILE_DEST;

NAME
——————————————————————————–
SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
———– ———- —————– —————
+DATA
5368709120  684480000                 0              24

SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     13
Next log sequence to archive   13
Current log sequence           15
SQL> show parameter db_rec

NAME                                 TYPE        VALUE
———————————— ———– ——————————
db_recovery_file_dest                string      +DATA
db_recovery_file_dest_size           big integer 5G
db_recycle_cache_size                big integer 0
SQL> SELECT * FROM V$RECOVERY_FILE_DEST;

NAME
——————————————————————————–
SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
———– ———- —————– —————
+DATA
5368709120  684480000                 0              24

SQL> alter system set db_recovery_file_dest =”" scope=both;
alter system set db_recovery_file_dest =”" scope=both
*
ERROR at line 1:
ORA-01741: illegal zero-length identifier

SQL> alter system set db_recovery_file_dest =” ” scope=both;
alter system set db_recovery_file_dest =” ” scope=both
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-38775: cannot disable flash recovery area – flashback database is enabled

SQL> select name,total_mb,free_mb from v$asm_diskgroup;

NAME                             TOTAL_MB    FREE_MB
—————————— ———- ———-
DATA                                 6589       2667

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-16014: log 3 sequence# 13 not archived, no available destinations
ORA-00312: online log 3 thread 1:
‘+DATA/dbtest/onlinelog/group_3.266.720140799′
ORA-00312: online log 3 thread 1:
‘+DATA/dbtest/onlinelog/group_3.267.720140805′

SQL> show parameter db_rec

NAME                                 TYPE        VALUE
———————————— ———– ——————————
db_recovery_file_dest                string      +DATA
db_recovery_file_dest_size           big integer 5G
db_recycle_cache_size                big integer 0
SQL> alter system set db_recovery_file_dest_size=10G scope=both;

System altered.

SQL>  alter system set db_recovery_file_dest_size=15G scope=both;

System altered.
-bash-3.2$ export ORACLE_SID=dbtest
-bash-3.2$ sqlplus “/as sysdba”

SQL*Plus: Release 10.2.0.1.0 – Production on Mon Jun 7 03:06:26 2010

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – 64bit Production
With the Partitioning, OLAP and Data Mining options

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – 64bit Production
With the Partitioning, OLAP and Data Mining options
-bash-3.2$ rman target /

Recovery Manager: Release 10.2.0.1.0 – Production on Mon Jun 7 03:06:38 2010

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

connected to target database: DBTEST (DBID=1113003619, not open)

RMAN> delete archivelog all;

using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=144 devtype=DISK

List of Archived Log Copies
Key     Thrd Seq     S Low Time  Name
——- —- ——- – ——— —-
1       1    1       A 27-MAY-10 +DATA/dbtest/archivelog/2010_05_31/thread_1_seq_1.272.720416503
2       1    2       A 31-MAY-10 +DATA/dbtest/archivelog/2010_06_01/thread_1_seq_2.278.720499021
3       1    3       A 01-JUN-10 +DATA/dbtest/archivelog/2010_06_02/thread_1_seq_3.281.720579491
4       1    4       A 02-JUN-10 +DATA/dbtest/archivelog/2010_06_03/thread_1_seq_4.282.720747463
5       1    5       A 03-JUN-10 +DATA/dbtest/archivelog/2010_06_04/thread_1_seq_5.283.720755633
6       1    6       A 04-JUN-10 +DATA/dbtest/archivelog/2010_06_04/thread_1_seq_6.284.720755869
7       1    7       A 04-JUN-10 +DATA/dbtest/archivelog/2010_06_04/thread_1_seq_7.285.720756011
8       1    8       A 04-JUN-10 +DATA/dbtest/archivelog/2010_06_04/thread_1_seq_8.286.720756141
9       1    9       A 04-JUN-10 +DATA/dbtest/archivelog/2010_06_04/thread_1_seq_9.287.720756203
10      1    10      A 04-JUN-10 +DATA/dbtest/archivelog/2010_06_04/thread_1_seq_10.288.720756277
11      1    11      A 04-JUN-10 +DATA/dbtest/archivelog/2010_06_04/thread_1_seq_11.289.720756341
12      1    12      A 04-JUN-10 +DATA/dbtest/archivelog/2010_06_04/thread_1_seq_12.290.720756447

Do you really want to delete the above objects (enter YES or NO)? yes
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_05_31/thread_1_seq_1.272.720416503 recid=1 stamp=720416516
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_06_01/thread_1_seq_2.278.720499021 recid=2 stamp=720499030
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_06_02/thread_1_seq_3.281.720579491 recid=3 stamp=720579496
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_06_03/thread_1_seq_4.282.720747463 recid=4 stamp=720747471
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_06_04/thread_1_seq_5.283.720755633 recid=5 stamp=720755682
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_06_04/thread_1_seq_6.284.720755869 recid=6 stamp=720755886
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_06_04/thread_1_seq_7.285.720756011 recid=7 stamp=720756036
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_06_04/thread_1_seq_8.286.720756141 recid=8 stamp=720756155
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_06_04/thread_1_seq_9.287.720756203 recid=9 stamp=720756218
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_06_04/thread_1_seq_10.288.720756277 recid=10 stamp=720756287
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_06_04/thread_1_seq_11.289.720756341 recid=11 stamp=720756356
deleted archive log
archive log filename=+DATA/dbtest/archivelog/2010_06_04/thread_1_seq_12.290.720756447 recid=12 stamp=720756502
Deleted 12 objects

RMAN> exit

SQL> show parameter db_rec

NAME                                 TYPE        VALUE
———————————— ———– ——————————
db_recovery_file_dest                string      +DATA
db_recovery_file_dest_size           big integer 15G
db_recycle_cache_size                big integer 0

SQL> alter database open;

Database altered.

SQL>

NOw you can try to run asmcmd also:

-bash-3.2$ asmcmd
ASMCMD> ls
DATA/