Trace file /u02/app/diag/rdbms/ora11g/ora11g/trace/ora11g_ora_31212.trc

Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production

With the Partitioning, Automatic Storage Management, OLAP, Data Mining

and Real Application Testing options

ORACLE_HOME = /u02/app/oracle

System name:    Linux

Node name:      pc2.oracle.com

Release:        2.6.32-300.10.1.el5uek

Version:        #1 SMP Wed Feb 22 17:37:40 EST 2012

Machine:        x86_64

VM name:        VMWare Version: 6

Instance name: ora11g

Redo thread mounted by this instance: 1

Oracle process number: 35

Unix process pid: 31212, image: oracle@pc2.oracle.com (TNS V1-V3)

*** SESSION ID:(198.71) 2013-12-19 10:18:46.905

*** CLIENT ID:() 2013-12-19 10:18:46.905

*** SERVICE NAME:(SYS$USERS) 2013-12-19 10:18:46.905

*** MODULE NAME:(sqlplus@pc2.oracle.com (TNS V1-V3)) 2013-12-19 10:18:46.905

*** ACTION NAME:() 2013-12-19 10:18:46.905

-- The following are current System-scope REDO Log Archival related

-- parameters and can be included in the database initialization file.

--

-- LOG_ARCHIVE_DEST=‘‘

-- LOG_ARCHIVE_DUPLEX_DEST=‘‘

--

-- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf

--

-- DB_UNIQUE_NAME="ora11g"

--

-- LOG_ARCHIVE_CONFIG=‘SEND, RECEIVE, NODG_CONFIG‘

-- LOG_ARCHIVE_MAX_PROCESSES=4

-- STANDBY_FILE_MANAGEMENT=MANUAL

-- STANDBY_ARCHIVE_DEST=?/dbs/arch

-- FAL_CLIENT=‘‘

-- FAL_SERVER=‘‘

--

-- LOG_ARCHIVE_DEST_1=‘LOCATION=USE_DB_RECOVERY_FILE_DEST‘

-- LOG_ARCHIVE_DEST_1=‘MANDATORY NOREOPEN NODELAY‘

-- LOG_ARCHIVE_DEST_1=‘ARCH NOAFFIRM EXPEDITE NOVERIFY SYNC‘

-- LOG_ARCHIVE_DEST_1=‘NOREGISTER NOALTERNATE NODEPENDENCY‘

-- LOG_ARCHIVE_DEST_1=‘NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME‘

-- LOG_ARCHIVE_DEST_1=‘VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)‘

-- LOG_ARCHIVE_DEST_STATE_1=ENABLE

--

-- Below are two sets of SQL statements, each of which creates a new

-- control file and uses it to open the database. The first set opens

-- the database with the NORESETLOGS option and should be used only if

-- the current versions of all online logs are available. The second

-- set opens the database with the RESETLOGS option and should be used

-- if online logs are unavailable.

-- The appropriate set of statements can be copied from the trace into

-- a script file, edited as necessary, and executed when there is a

-- need to re-create the control file.

--

--     Set #1. NORESETLOGS case

--

-- The following commands will create a new control file and use it

-- to open the database.

-- Data used by Recovery Manager will be lost.

-- Additional logs may be required for media recovery of offline

-- Use this only if the current versions of all online logs are

-- available.

-- After mounting the created controlfile, the following SQL

-- statement will place the database in the appropriate

-- protection mode:

--  ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE

STARTUP NOMOUNT

CREATE CONTROLFILE REUSE DATABASE "ORA11G" NORESETLOGS  ARCHIVELOG

    MAXLOGFILES 16

    MAXLOGMEMBERS 3

    MAXDATAFILES 100

    MAXINSTANCES 8

    MAXLOGHISTORY 292

LOGFILE

  GROUP 1 (

    ‘+DATA/ora11g/onlinelog/group_1.262.833721677‘,

    ‘+DATA/ora11g/onlinelog/group_1.263.833721679‘

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 2 (

    ‘+DATA/ora11g/onlinelog/group_2.264.833721681‘,

    ‘+DATA/ora11g/onlinelog/group_2.265.833721683‘

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 3 (

    ‘+DATA/ora11g/onlinelog/group_3.266.833721683‘,

    ‘+DATA/ora11g/onlinelog/group_3.267.833721685‘

  ) SIZE 50M BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

  ‘+DATA/ora11g/datafile/system.256.833721555‘,

  ‘+DATA/ora11g/datafile/sysaux.257.833721555‘,

  ‘+DATA/ora11g/datafile/undotbs1.258.833721555‘,

  ‘+DATA/ora11g/datafile/users.259.833721555‘,

  ‘+DATA/ora11g/datafile/example.269.833721711‘

CHARACTER SET WE8MSWIN1252

;

-- Commands to re-create incarnation table

-- Below log names MUST be changed to existing filenames on

-- disk. Any one log file from each branch can be used to

-- re-create incarnation records.

-- ALTER DATABASE REGISTER LOGFILE ‘+DATA‘;

-- ALTER DATABASE REGISTER LOGFILE ‘+DATA‘;

-- Recovery is required if any of the datafiles are restored backups,

-- or if the last shutdown was not normal or immediate.

RECOVER DATABASE

-- All logs need archiving and a log switch is needed.

ALTER SYSTEM ARCHIVE LOG ALL;

-- Database can now be opened normally.

ALTER DATABASE OPEN;

-- Commands to add tempfiles to temporary tablespaces.

-- Online tempfiles have complete space information.

-- Other tempfiles may require adjustment.

ALTER TABLESPACE TEMP ADD TEMPFILE ‘+DATA/ora11g/tempfile/temp.268.833721699‘

     SIZE 20971520  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;

-- End of tempfile additions.

--

--     Set #2. RESETLOGS case

--

-- The following commands will create a new control file and use it

-- to open the database.

-- Data used by Recovery Manager will be lost.

-- The contents of online logs will be lost and all backups will

-- be invalidated. Use this only if online logs are damaged.

-- After mounting the created controlfile, the following SQL

-- statement will place the database in the appropriate

-- protection mode:

--  ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE

STARTUP NOMOUNT

CREATE CONTROLFILE REUSE DATABASE "ORA11G" RESETLOGS  ARCHIVELOG

    MAXLOGFILES 16

    MAXLOGMEMBERS 3

    MAXDATAFILES 100

    MAXINSTANCES 8

    MAXLOGHISTORY 292

LOGFILE

  GROUP 1 (

    ‘+DATA/ora11g/onlinelog/group_1.262.833721677‘,

    ‘+DATA/ora11g/onlinelog/group_1.263.833721679‘

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 2 (

    ‘+DATA/ora11g/onlinelog/group_2.264.833721681‘,

    ‘+DATA/ora11g/onlinelog/group_2.265.833721683‘

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 3 (

    ‘+DATA/ora11g/onlinelog/group_3.266.833721683‘,

    ‘+DATA/ora11g/onlinelog/group_3.267.833721685‘

  ) SIZE 50M BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

  ‘+DATA/ora11g/datafile/system.256.833721555‘,

  ‘+DATA/ora11g/datafile/sysaux.257.833721555‘,

  ‘+DATA/ora11g/datafile/undotbs1.258.833721555‘,

  ‘+DATA/ora11g/datafile/users.259.833721555‘,

  ‘+DATA/ora11g/datafile/example.269.833721711‘

CHARACTER SET WE8MSWIN1252

;

-- Commands to re-create incarnation table

-- Below log names MUST be changed to existing filenames on

-- disk. Any one log file from each branch can be used to

-- re-create incarnation records.

-- ALTER DATABASE REGISTER LOGFILE ‘+DATA‘;

-- ALTER DATABASE REGISTER LOGFILE ‘+DATA‘;

-- Recovery is required if any of the datafiles are restored backups,

-- or if the last shutdown was not normal or immediate.

RECOVER DATABASE USING BACKUP CONTROLFILE

-- Database can now be opened zeroing the online logs.

ALTER DATABASE OPEN RESETLOGS;

-- Commands to add tempfiles to temporary tablespaces.

-- Online tempfiles have complete space information.

-- Other tempfiles may require adjustment.

ALTER TABLESPACE TEMP ADD TEMPFILE ‘+DATA/ora11g/tempfile/temp.268.833721699‘

     SIZE 20971520  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;

-- End of tempfile additions.

--

#cat ora11g_ora_.trc