Similar Questions

• ORA-01102: cannot mount database in EXCLUSIVE mode in AIX after you have installed the database using dbca

  Hello!

  I have v7 IBM AIX and cluster HACMP set up two identical nodes included

  I have a head node after the installation of database using dbca I got error with the message:

  ORA-01102: cannot mount database in EXCLUSIVE mode

  Database cannot mount)

  Here is the information from the alert log:

  MON may 25 18:00:07 2015

  Starting ORACLE instance (normal)

  LICENSE_MAX_SESSION = 0

  LICENSE_SESSIONS_WARNING = 0

  SNA system picked latch-free 3

  With the help of LOG_ARCHIVE_DEST_1 parameter value by default as USE_DB_RECOVERY_FILE_DEST

  Autotune undo retention is enabled.

  IMODE = BR

  ILAT = 84

  LICENSE_MAX_USERS = 0

  SYS audit is disabled

  Commissioning:

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

  With the options of partitioning, OLAP, Data Mining and Real Application Testing.

  ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1/

  System name: nodename

  Name of the node: nodename

  Version: 1

  Version: 7

  Machine: 0003F6E5D600

  Using the settings in /u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfiletestdb.ora side Server spfile

  Parameters of the system with default values:

  process = 500

  sessions = 772

  = 18G memory_target

  control_files = "/ ctl1/oradata/testdb/control01.ctl".

  control_files = "/ ctl2/oradata/testdb/control02.ctl".

  control_files = "/ ctl3/oradata/testdb/control03.ctl".

  DB_BLOCK_SIZE = 8192

  compatible = "11.2.0.0.0."

  db_recovery_file_dest = ' / backup/fra.

  db_recovery_file_dest_size = 100G

  undo_tablespace = 'UNDOTBS1.

  Remote_login_passwordfile = "EXCLUSIVE."

  db_domain = «»

  dispatchers = "(PROTOCOL=TCP) (SERVICE = testdbXDB)" "

  audit_file_dest = ' / u01/app/oracle/admin/testdb/adump.

  AUDIT_TRAIL = 'DB '.

  db_name = 'testdb '.

  open_cursors = 300

  diagnostic_dest = ' / u01/app/oracle '.

  MON may 25 18:00:08 2015

  PMON started with pid = 2, OS id = 14418020

  MON may 25 18:00:08 2015

  PSP0 started with pid = 3, OS id = 17891420

  MON may 25 18:00:09 2015

  VKTM started with pid = 4, OS id = 14090348 high priority

  VKTM clocked at (10) precision of milliseconds with DBRM quantum (100) ms

  MON may 25 18:00:09 2015

  GEN0 started with pid = 5, OS id = 9109714

  MON may 25 18:00:09 2015

  DIAG started with pid = 6, OS id = 16449704

  MON may 25 18:00:09 2015

  DBRM started with pid = 7, OS id = 17104928

  MON may 25 18:00:10 2015

  DIA0 started with pid = 8, OS id = 13303950

  MON may 25 18:00:10 2015

  MA started with pid = 9, OS id = 12517522

  MON may 25 18:00:10 2015

  DBW0 started with pid = 10, OS id = 11993232

  MON may 25 18:00:10 2015

  LGWR started with pid = 11, OS id = 15401010

  MON may 25 18:00:10 2015

  CKPT started with pid = 12, OS id = 6619318

  MON may 25 18:00:10 2015

  SMON started with pid = 13, OS id = 16515222

  MON may 25 18:00:10 2015

  RECCE has started with pid = 14, OS id = 13172906

  MON may 25 18:00:10 2015

  MMON started with pid = 15, OS id = 15794324

  commissioning 1 dispatcher (s) for '(ADDRESS =(PARTIAL=YES) (PROTOCOL = TCP))' network address...

  MON may 25 18:00:10 2015

  MMNL started with pid = 16, OS id = 18546742

  commissioning or shared server 1...

  Environment ORACLE_BASE = / u01/app/oracle /.

  MON may 25 18:00:11 2015

  ALTER DATABASE MOUNT

  sculkget: failed to lock /u01/app/oracle/product/11.2.0/dbhome_1//dbs/lkTESTDB exclusive

  sculkget: lock held by PID: 3670226

  ORA-09968: cannot lock file

  IBM AIX RISC System/6000 error: 13: permission denied

  Additional information: 3670226

  ORA-1102 marked during: ALTER DATABASE MOUNT...

  But if I install the darabase even dbca on node secondary, all installed and executed successfully.

  But in the two nodes even permissions, user oracle and oinstall group ID identified the same and $ORACLE_BASE and $ORACLE_HOME user owner oracle and oinstall user group.

  A someone has encountered this problem and solved?

  Thanks in advance!

  Hello

  you are using IBM AIX PowerHA for your database (active/passive) configuration. then you just install the binaries 'once' on one of the nodes. then coordinate with your operating system administrator to configure the fail the test scenarios.

  for your question. before you start the database, make sure that there are no "orphaned" oracle process using the UNIX grep command:

  $ ps - ef | grep ora

  Kill the oracle of the hanging of the process to release the lock on the database file handle:

  $ kill-9

  I hope this helps.

  Kind regards

• ORA-01102: cannot mount database in EXCLUSIVE mode

  Hi I work on Windows 2007, 64-bit, with oracle 11g: 11.1.0.6.0

  Today, I created a tablespace of cancellation more as undotbs2, and then I went to undotbs2 database.

  Then, I gave the order to drop the undotdb1.  He has successfully completed.  but undo datafile has not been eliminated. So I tried to manually delete the data file it didn't ' success.

  So I stop the database & then deleted file manually

  . After giving the start command, I was getting this error

  of alert_log

  ORA-01157: cannot identify/lock data file 3 - see DBWR trace file

  ORA-01110: data file 3: ' E:\APP\ADMINISTRATOR\ORADATA\UNDOTBS01. DBF'

  ORA-27041: could not open the file

  04002 - OSD: could not open the file

  S/O-error: (OS 2) the system cannot find the file specified.

  ORA-1157 marked during: alter database open...

  Kills Jul 30 16:10:48 2013

  Starting ORACLE instance (normal)

  Then I dropped the datafile undo

  Alerts log

  ALTER database datafile ' E:\APP\ADMINISTRATOR\ORADATA\EFVAT\UNDOTBS01. DBF' offline drop

  Completed: alter database datafile ' E:\APP\ADMINISTRATOR\ORADATA\EFVAT\UNDOTBS01. DBF' offline drop

  ALTER database open; database opened successfully.

  but she was still showing undotbs1 undo_tablespace parameter, so I created a more (2nd one) undo tablespace. I'm going to this error in the alert log

  ORA-30012: undo tablespace "UNDOTBS02" there is not, or of the wrong type

  After that, I'm not able to mount the database I m getting as below

  Alerts log

  ORA-09341: scumnt: unable to mount the database

  OSD-04400: impossible to acquire the internal process semaphore

  S/O-error: (OS 183) cannot create a file when that file already exists.

  ORA-1102 marked during: ALTER DATABASE MOUNT...

  get this error when I try to start the database

  . ORA-01102: cannot mount database in EXCLUSIVE mode

  974427 wrote:

  Hi I work on Windows 2007, 64-bit, with oracle 11g: 11.1.0.6.0

  Today, I created a tablespace of cancellation more as undotbs2, and then I went to undotbs2 database.

  Then, I gave the order to drop the undotdb1.  He has successfully completed.  but undo datafile has not been eliminated. So I tried to manually delete the data file it didn't ' success.

  So I stop the database & then deleted file manually

  . After giving the start command, I was getting this error

  of alert_log

  ORA-01157: cannot identify/lock data file 3 - see DBWR trace file

  ORA-01110: data file 3: ' E:\APP\ADMINISTRATOR\ORADATA\UNDOTBS01. DBF'

  ORA-27041: could not open the file

  04002 - OSD: could not open the file

  S/O-error: (OS 2) the system cannot find the file specified.

  ORA-1157 marked during: alter database open...

  Kills Jul 30 16:10:48 2013

  Starting ORACLE instance (normal)

  Then I dropped the datafile undo

  Alerts log

  ALTER database datafile ' E:\APP\ADMINISTRATOR\ORADATA\EFVAT\UNDOTBS01. DBF' offline drop

  Completed: alter database datafile ' E:\APP\ADMINISTRATOR\ORADATA\EFVAT\UNDOTBS01. DBF' offline drop

  ALTER database open; database opened successfully.

  but she was still showing undotbs1 undo_tablespace parameter, so I created a more (2nd one) undo tablespace. I'm going to this error in the alert log

  ORA-30012: undo tablespace "UNDOTBS02" there is not, or of the wrong type

  After that, I'm not able to mount the database I m getting as below

  Alerts log

  ORA-09341: scumnt: unable to mount the database

  OSD-04400: impossible to acquire the internal process semaphore

  S/O-error: (OS 183) cannot create a file when that file already exists.

  ORA-1102 marked during: ALTER DATABASE MOUNT...

  get this error when I try to start the database

  . ORA-01102: cannot mount database in EXCLUSIVE mode

  Well, your trace file indicates that the above description is innaccurate: you did NOT create an undo tablespace undotbs2, you have created a undotbs2 permanent tablespace.

  You may be able to repair this situation, like this:

  startup nomount

  ALTER system set undo_management = manual scope = spfile;

  immediate stop

  startup

  create undo tablespace undo3 datafile ' / whatever/you.like ' size XXg;

  ALTER system set undo_tablespace is undo3 scope = spfile;.

  ALTER system set undo_management = auto scope is spfile;.

  immediate stop

  startup

• cannot mount the database exclusively on 10g

  Dear friends

  Net app cause a problem today and the volume has been removed then now the DB can not open cannot mount database in EXCLUSIVE mode

  Help, please

  

  The net app is a problem today & volume was dismantled, then now the DB cannot open cannot mount database in EXCLUSIVE mode

  1. what your volume is in place and mounted?

  2. what database mounted on netapp files?

  3. If his having control-files and database files, then logically with them you can not mount the instance.

  Please perform the verification tests of the basis of the presence of files on mounted volumes / for access to the

  -Pavan Kumar N

• ORA-01507: database not mounted

  Hello

  It's 11.2.0.3 on Windows 2008,

  a node 3 RAC ASM.

  After restarting the server that hosts third instance,

  I have the following situation, everything is in place except the database

  on the third node in the database of node 1 and 2 is open, any other service is also running.

  crsctl res stat - you

  ORA.bigdb.db

  1 LINE intermediate bigdb3 dismantled, up in

  itiated

  2 bigdb2 open online

  3 bigdb1 open online

  When I try to query from the third node database, I got the message that the database is not mounted,

  C:\ > sqlplus / as sysdba

  SQL * more: Production of the version 11.2.0.3.0 on Mon Oct 26 15:47:25 2015

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

  Connected to:

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

  With Real Application Clusters and Automatic Storage Management options

  SQL > select count (*) from the database of v$.

  Select count (*) from the database of v$

  *

  ERROR on line 1:

  ORA-01507: database not mounted

  Seems that there is nothing wrong when querying ASM instance on that node, all disks are mounted.

  C:\ > set ORACLE_SID = + ASM3

  
  

  C:\ > sqlplus / as sysasm

  SQL * more: Production of the version 11.2.0.3.0 on Mon Oct 26 15:49:51 2015

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

  Connected to:

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

  With Real Application Clusters and Automatic Storage Management options

  SQL > select name, status from v$ asm_diskgroup;

  NAME STATE

  ------------------------------ -----------

  BOW MOUNTED

  MOUNTED CRS

  DG1 MOUNTED

  DG2 MOUNTED

  QG3 MOUNTED

  SQL >

  And it is of the Journal of the third instance alerts.

  ORA-00210: could not open the specified control file

  ORA-00202: control file: "+ ARC/control02.ctl".

  ORA-17503: ksfdopn:2 could not open the file + ARC/control02.ctl

  ORA-15001: diskgroup 'ARC' does not exist or is not mounted

  ORA-15077: could not locate instance ASM serving a required diskgroup

  ORA-00210: could not open the specified control file

  ORA-00202: control file: "+ DG3/bigdb/control01.ctl".

  ORA-17503: ksfdopn:2 could not open the file +DG3/bigdb/control01.ctl

  ORA-15001: diskgroup 'DG3' does not exist or is not mounted

  ORA-15077: could not locate instance ASM serving a required diskgroup

  ORA - 205 marked during: alter exclusive of installation of database...

  Please suggest what can be done to open the database of the third node.

  Thanks to all for trying to help.

  What I did then, it's a sign the db as sysdba on the third node,.

  immediate stop and then start.

  SQL > shutdown immediate;

  ORA-01507: database not mounted

  ORACLE instance stops.

  SQL >

  SQL >

  SQL >

  SQL >

  SQL > startup

  ORACLE instance started.

  System Global area 1.4531E + 10 bytes

  Bytes of size 2269104 fixed

  5905580112 variable size bytes

  Buffers data 8589934592 bytes

  Redo buffers 33673216 bytes

  Mounted database.

  Open database.

  It seems that it is a question of cluster, Oracle obivously (sometimes) will automatically start all resources, as is expected.

  I guess that Windows as operating system contributes significantly to the

• The database recovery

  Hi all

  EBS R12.2.4

  OEL6

  I play with the recovery of database > restore database using backup controlfile until cancel;

  but I encountered error:

  ORA-00279: change 5965308871319 September at 29/11/2015 10:49:20 needed to

  thread 1

  ORA-00289: suggestion: /home/ARCH/1_212_894234402.dbf

  ORA-00280: change 5965308871319 thread 1 is in sequence #212

  ORA-00278: log file ' / home/ARCH/1_211_894234402.dbf' is no longer necessary for this

  recovery

  ORA-00283: cool cancelled due to errors

  ORA-01244: datafile (s) without a name added to the control file by the media recovery

  ORA-01110: data file 42: ' / home/oraprod/PROD/data/a_txn_ind10.dbf'

  ORA-01112: media recovery not started

  SQL > shutdown immediate;

  ORA-01109: database is not open

  The database is dismounted.

  ORACLE instance stops.

  SQL > bootable media.

  ORACLE instance started.

  Total System Global Area 2137886720 bytes

  Bytes of size 2230072 fixed

  452987080 variable size bytes

  1660944384 of database buffers bytes

  Redo buffers 21725184 bytes

  Mounted database.

  SQL > restore database using backup controlfile until cancel;

  ORA-00283: cool cancelled due to errors

  ORA-01111: 42 data file name is unknown - rename it to the correct file

  ORA-01110: data file 42: ' / home/oraprod/PROD/11.2.0/dbs/UNNAMED00042'

  ORA-01157: cannot identify/lock data file of 42 - see DBWR trace file

  ORA-01111: 42 data file name is unknown - rename it to the correct file

  ORA-01110: data file 42: ' / home/oraprod/PROD/11.2.0/dbs/UNNAMED00042'

  SQL >

  Help, please...

  Thank you

  JC

  You cannot copy directly, but you can save only data file with rman "backup datafile 42. However, the RCS in the header of the data file would be different now, and you cannot recover.

  You said in one of the message that the file without a NAME no longer exists? You rename it using 'alter database rename file '?

  You can use:

  ALTER database create datafile 42 as ' / home/oraprod/PROD/data/a_txn_ind10.dbf';

  Then run:

  RECOVER THE DATABASE AUTOMATICALLY USING BACKUP CONTROLFILE UNTIL CANCEL

• ORA-38760: this database instance could not turn on the flashback database

  Hi guys

  Without knowing it, I deleted all the files in the directory "fra" where "flashback" folder was there because of space issues. Now am facing the error.

  It's my practical database.

  SQL > startup

  ORACLE instance started.

  Total System Global Area 608174080 bytes

  Bytes of size 1268920 fixed

  184550216 variable size bytes

  419430400 of database buffers bytes

  Redo buffers 2924544 bytes

  Mounted database.

  ORA-38760: this database instance could not turn on the flashback database

  SQL > alter flashback database;

  Database altered.

  SQL > SHUTDOWN IMMEDIATE;

  SQL > STARTUP MOUNT

  SQL > select flashback_on from database v$.

  FLASHBACK_ON

  ------------------

  RESTORE POINT ONLY

  Am not able to extinguish the flame.

  SQL > select * from v$ restore_point;

  Select * from v$ restore_point

  *

  ERROR on line 1:

  ORA-38701: Flashback database log 1 seq 1 wire 1:

  "/ u01/fra/PROD/flashback/o1_mf_c1l5n3lq_.flb".

  ORA-27037: unable to get file status

  Linux error: 2: no such file or directory

  Additional information: 3

  SQL > select flashback_on from database v$.

  FLASHBACK_ON

  ------------------

  RESTORE POINT ONLY

  I also tried to create a restore point and the flashback there.

  SQL > create restore point guaranteed rspt1 flashback database;

  Restore point created.

  SQL > select * from v$ restore_point;

  Select * from v$ restore_point

  *

  ERROR on line 1:

  ORA-00600: internal error code, arguments: [krfg_get_keepseq_2], [1], [0], [0,]

  [0], [0], [0], [0]

  SQL > flashback data base to restore the point rspt1;

  flashback database to restore the rspt1 point

  *

  ERROR on line 1:

  ORA-38729: not enough flashback database data log do FLASHBACK.

  Please help me in this regard.

  Alert log file:

  ...

  ...

  ...

  Mount of redo thread 1, with mount id 305866694

  Sun 25 Oct 10:13:30 2015

  Bytes allocated of 3981204 in the shared pool for the generation of flashback buffer

  From RVWR background process

  RVWR started with pid = 16, OS id = 15486

  Sun 25 Oct 10:13:30 2015

  Errors in the /u01/oracle/product/10.2.0/db_1/admin/prod/bdump/prod_rvwr_15486.trc file:

  ORA-38701: seq 11 Flashback database log 11 1 thread: ' / u01/fra/PROD/flashback/o1_mf_c2oqypb0_.flb '.

  ORA-27037: unable to get file status

  Linux error: 2: no such file or directory

  Additional information: 3

  Sun 25 Oct 10:13:30 2015

  Database mounted in exclusive Mode

  Completed: ALTER DATABASE MOUNT

  Sun 25 Oct 10:13:30 2015

  ALTER DATABASE OPEN

  ORA-38760 marked during: ALTER DATABASE OPEN...

  Trace file:

  ...

  ...

  ...

  :() 2015-10-25 10:13:30.087 SERVICE NAME

  SESSION ID: (156.1) 2015-10-25 10:13:30.087

  ORA-38701: seq 11 Flashback database log 11 1 thread: ' / u01/fra/PROD/flashback/o1_mf_c2oqypb0_.flb '.

  ORA-27037: unable to get file status

  Linux error: 2: no such file or directory

  Additional information: 3

  1. Thank you.

  you experience serious problem... because usually it works very well.

  Try the following:

  SQL > shutdown immediate;

  SQL > bootable media.

  SQL > alter flashback database;

  SQL > alter database backup controlfile to trace noresetlogs;

  SQL > shutdown immediate;

  go to the trace file generated from running (alter database backup controlfile to trace noresetlogs ;)

  location of the trace file is located in the query:

  SQL > select * from v$ diag_info;

  It will contain the script with the SQL commands, you can rename the file with the extension ".sql".

  SQL > startup nomount

  SQL > @trace_file. SQL

  SQL > restore database;

  SQL > alter database open;

  So basically you are going to recreate the files of control again...

• How to COPY a BACKUP as the... CONTROLFILE can be used for the OPEN database

  I create a document such as a "How To" to move a position for a Junior DBA controlfile.

  But it seems that I'm the Junior because I am facing the following...

  Action plan:

  Move/rename a Controlfile

  Version of the database: 11.2.0.3

  Controlfiles moving of:

  / goldengate/ORCL/ORADATA /.

  TO:

  / GoldenGate/ORCL/controlfile

  Step 1: Set up environment variables

  $> export ORACLE_SID = ORCL1 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- $> echo $ORACLE_SID ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ORCL1 $> export ORACLE_BASE = / u01/app/oracle ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- $> echo $ORACLE_BASE ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- / u01/app/Oracle $> export ORACLE_HOME=$ORACLE_BASE/product/11.2.0.3/dbhome_1 -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  $ echo $ORACLE_HOME

  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  /U01/app/Oracle/product/11.2.0.3/dbhome_1

  Step 2: Check control_files parameter

  $> echo "see THE PARAMETER control_files | sqlplus-s "virtue sysdba". ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- VALUE OF TYPE NAME ------------------------------------ ----------- ------------------------------ control_files string/goldengate/ORCL/ORADATA/control ol01. CTL, / goldengate/ORCL/ORA DATA/control02.ctl

  Step 3: Closing the open database

  $> echo 'SHUTDOWN IMMEDIATE'; | sqlplus-s "virtue sysdba". ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The database is closed. The database is dismounted. ORACLE instance stops.

  Step 4: Editing of the database

  $> echo "STARTUP MOUNT"; | sqlplus-s "virtue sysdba". ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ORACLE instance started. Total System Global Area 4275781632 bytes Bytes of size 2235208 fixed

  822084792 variable size bytes

  3439329280 of database buffers bytes

  Redo buffers 12132352 bytes

  Mounted database.

  Step 5: Creating a copy of the current controlfile

  $> echo "AS BACKUP COPY CURRENT CONTROLFILE FORMAT ' / goldengate/ORCL/CONTROLFILE/control01.copy.ctl'; ' | RMAN target / nocatalog ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Recovery Manager: release 11.2.0.3.0 - Production Fri Oct 22 17:03:27 2015 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: ORCL (DBID = 1420762587, is not open) using the control file of the target instead of recovery catalog database RMAN > From 22 October 15 backup allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID = 58 type of device = DISK channel ORA_DISK_1: from data file copy copy the current control file tag name=/goldengate/ORCL/CONTROLFILE/control01.copy.ctl output file = RECID = 1 STAMP = 893783011 TAG20151022T170329 channel ORA_DISK_1: datafile copy complete, duration: 00:00:03 Backup finished at 22 October 15 RMAN >

  Complete recovery manager.

  Step 6: Change of parameter control_files

  $> echo "ALTER SYSTEM SET control_files='/goldengate/ORCL/CONTROLFILE/control01.copy.ctl' SCOPE = SPFILE;" | sqlplus-s "virtue sysdba". -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  Modified system.

  Step 7: Closing of the mounted database

  $> echo 'SHUTDOWN IMMEDIATE'; | sqlplus-s "virtue sysdba". ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ORA-01109: database is not open The database is dismounted. ORACLE instance stops.

  Step 8: Installation of the database

  $> echo "STARTUP MOUNT"; | sqlplus-s "virtue sysdba". ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ORACLE instance started. Total System Global Area 4275781632 bytes Bytes of size 2235208 fixed 822084792 variable size bytes 3439329280 of database buffers bytes Redo buffers 12132352 bytes Mounted database.

  Step 9: Check control_files parameter

  $> echo "see THE PARAMETER control_files | sqlplus-s "virtue sysdba". ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- VALUE OF TYPE NAME ------------------------------------ ----------- ------------------------------ control_files string/goldengate/ORCL/CONTROLFILE/c ontrol01. Copy.CTL

  Step 10: Open the mounted database

  $> echo "ALTER DATABASE OPEN"; | sqlplus-s "virtue sysdba". ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ALTER DATABASE OPEN * ERROR on line 1: ORA-01589: must use RESETLOGS or NORESETLOGS option of database open $> echo "ALTER DATABASE OPEN NORESETLOGS"; | sqlplus-s "virtue sysdba". ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ALTER DATABASE OPEN NORESETLOGS * ERROR on line 1: ORA-01610: recovery using BACKUP CONTROLFILE option must be

  Then...

  $> sqlplus/nolog ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- SQL * more: Production release 11.2.0.3.0 the game Oct 22 17:14:43 2015 Copyright (c) 1982, 2011, Oracle.  All rights reserved. SQL > CONNECT sysdba virtue ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Connected. SQL > RECOVER DATABASE with the HELP of BACKUP CONTROLFILE until CANCEL; -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  ORA-00279: change 621941 September at 22/10/2015 16:57:33 needed to screw 1

  ORA-00289: suggestion:

  /U01/app/Oracle/product/11.2.0.3/dbhome_1/DBS/arch1_11_892981851.dbf

  ORA-00280: change 621941 thread 1 is in sequence #11

  Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}

  Cancel

  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  Cancelled media recovery.

  SQL > ALTER DATABASE OPEN;

  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  ALTER DATABASE OPEN

  *

  ERROR on line 1:

  ORA-01589: must use RESETLOGS or NORESETLOGS option of database open

  Issues related to the:

  What am I misunderstanding? BACKUP COPY THAT isn't really a COPY.

  Why I can't use the 'copy' of the controlfile created by RMAN?

  Note:

  If I just copy the controlfile to the new location when the database shuts down everything works fine.

  Thanks in advance.

  Juan M

  
  

  Recovery Manager (RMAN)

  It is also mentioned in https://docs.oracle.com/cd/E11882_01/server.112/e25494/control.htm#ADMIN11288

  Create additional Copies, rename and move the control files

• Problem of temporary file in the database takes a while to start the database

  Legends of dear,

  I am facing the warning next or problem with R12.0.6 64 bit and 10.2.0.3 databases in a linux environment

  Mar 20 18:24:23 Oct 2015

  *********************************************************************

  ATTENTION: The following temporary tablespaces do not contain any file.

  This condition can occur when a backup controlfile

  been restored.  It may be necessary to add files to these

  storage spaces.  This can be done using the SQL statement:

  ALTER TABLESPACE < nom_tablespace > ADD TEMPFILE

  Furthermore, if these temporary tablespaces are no longer

  necessary, then they can be recessed.

  Temporary tablespace is empty: TEMP3

  *********************************************************************

  When I questioned my database_properties

  Select * from database_properties where name like '% TEMP % ";

  

  Journal Alerts

  Mar 20 18:24:23 Oct 2015

  Completed: ALTER DATABASE OPEN

  Mar 20 18:24:25 Oct 2015

  Additional checkpoint up to RBA to RBA [0x68e.5c2b5.0] [0x68e.5c26c.0], current journal line

  Details of the Temp file

  /Oracle/prod/DB/apps_st/data/temp03.dbf	1	TMP4
  /Oracle/prod/DB/apps_st/data/temp04.dbf	2	TMP4

  Because of the warning above when I give 'start-up' in "sqlplus" or start the database using the addbctl.sh script there is a huge gap between the following

  SQL > startup;

  ORACLE instance started.

  Total System Global Area 2147483648 bytes

  Bytes of size 2074112 fixed

  872417792 variable size bytes

  1258291200 of database buffers bytes

  Redo buffers 14700544 bytes

  Mounted database.

  ..............

  ................

  ..............

  .............

  ...........

  .......... (LOCAL TIME - 10 to 15 minutes)

  ...............

  ...............

  .................

  ........

  Open database.

  Please suggest how to deal with this.

  Thank you

  Knockaert

  Hello

  It is a question of pure database. Not much relationship to the EBS.

  Anyway, as stated in the warning, you must add a temporary file in the tablespace TEMP3 or drop the tablespace if you do not need.

  Can you post the full alerts log part, which takes 10 to 15 minutes?

  Kind regards

  Bashar

• What do I need to use the database shall begin backup mode to perform the backup?

  Hi all

  I have a primary database to 10g (10.2.0.4) with intelligence on a solaris platform. I need to create a different primary eve for the same database.

  I stopped the recovery based on standby and began copy (copy of the os) the existing files pending at the 2nd backup server. But I didn't keep the (mounted) existing standby database into begin backup mode. Is this right?

  Thank you

  Arun

  For a mounted database backup mode?

  orclz >

  orclz > startup mount

  ORACLE instance started.

  Total System Global Area 788529152 bytes

  Bytes of size 3050600 fixed

  373293976 variable size bytes

  406847488 of database buffers bytes

  Redo buffers 5337088 bytes

  Mounted database.

  orclz >

  orclz > alter database begin backup;

  ALTER database begin backup

  *

  ERROR on line 1:

  ORA-01109: database is not open

  orclz >

• Change of database time zone

  Hello

  I tried to change the time zone database, but does not...

  SQL > select systimestamp from double;

  SYSTIMESTAMP

  ---------------------------------------------------------------------------

  12.45.51.697459 9 MARCH 15: + 00:00

  SQL > ALTER DATABASE SET TIME_ZONE = '+ 05:30 ';

  Database altered.

  SQL > shutdown immediate;

  The database is closed.

  The database is dismounted.

  ORACLE instance stops.

  SQL > startup;

  ORACLE instance started.

  Total System Global Area 6766444544 bytes

  Bytes of size 2171144 fixed

  3959430904 variable size bytes

  2785017856 of database buffers bytes

  Redo buffers 19824640 bytes

  Mounted database.

  Open database.

  SQL > select systimestamp from double;

  SYSTIMESTAMP

  ---------------------------------------------------------------------------

  12.47.11.521921 9 MARCH 15: + 00:00

  Help, please

  database gets the operating system time zone

• Database of flashback through RMAN (10 g)

  Hi all;

  How can get a rear base using database of flashback (rman) in 10 g.

  SQL > select current_scn, to_char (SYSTIMESTAMP, "YYYY-MM-DD HH24:MI:SS) database v$.

  TO_CHAR (SYSTIMESTAM CURRENT_SCN

  ----------- -------------------

  1153432 2014-05-25 00:07:35

  SQL > select * from tab;

  TNOM TABTYPE CLUSTERID

  ------------------------------ ------- ----------

  TAB6 TABLE

  TABLE TAB1

  TABLE TAB2

  SQL > delete from tab2.

  2048 deleted rows.

  SQL > truncate table tab1;

  Table truncated.

  SQL > drop table tab6.

  Deleted table.

  SQL > commit;

  Validation complete.

  SQL > conn / as sysdba

  Connected.

  SQL > drop user cascade of sam;

  Deleted user.

  SQL > shutdown immediate;

  The database is closed.

  The database is dismounted.

  ORACLE instance stops.

  SQL > bootable media.

  ORACLE instance started.

  Total System Global Area 465567744 bytes

  Bytes of size 1274308 fixed

  96472636 variable size bytes

  364904448 of database buffers bytes

  Redo buffers 2916352 bytes

  Mounted database.

  SQL > exit

  Disconnected from the database to Oracle 10 g Enterprise Edition Release 10.2.0.5.0 - Production

  With partitioning, OLAP, Data Mining and Real Application Testing options

  [oracle@oel5 ~] target rman $ /.

  Recovery Manager: Release 10.2.0.5.0 - Production on Sun may 25 00:10:21 2014

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

  connected to target database: ORCL (DBID = 1373939619, is not open)

  
  

  RMAN > FLASHBACK DATABASE TO TIME timestamp ('2014-05-25 00:07:35 ');

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-00558: error occurred during parsing of order entry

  RMAN-01009: syntax error: found 'identifier': expected an a: 'double-quoted-string, equal, single-quoted-string '.

  RMAN-01008: the bad ID was: timestamp

  RMAN-01007: in the file column 28 line 1: entry standard

  Recovery Manager: Release 10.2.0.5.0 - Production on Sun may 25 00:10:21 2014

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

  connected to target database: ORCL (DBID = 1373939619, is not open)

  FLASHBACK DATABASE IN TIME ' TO_DATE ('2014-05-25 00:07:35 ',' YYYY-MM-DD HH24:MI:SS') ";

• Problem with the restoration of the database

  Hello world

  I have a strange problem while restoring the database with rman. The problem is that the data are not restored at all.

  Let me show you what I do step by step:

  1. create the test table:

  $ sqlplus / as sysdba

  SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 22:51:58 2014

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

  Connected to:

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

  With partitioning, OLAP, Data Mining and Real Application Testing options

  SQL > create table test (ID);

  Table created.

  SQL > insert into values test (1);

  1 line of creation.

  SQL > commit;

  Validation complete.

  2. backup the current database:

  rman target $ /.

  Recovery Manager: release 11.2.0.1.0 - Production Fri Apr 17 22:56:44 2014

  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

  connected to target database: ORACLE (DBID = 1672007929)

  RMAN > backup database;

  From 17 April 14 backup
  using the control file of the target instead of recovery catalog database
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = 6 type of device = DISK
  channel ORA_DISK_1: starting full datafile from backup set
  channel ORA_DISK_1: specifying datafile (s) in the backup set
  Enter a number of file datafile = 00001 name=/u01/app/oracle/oradata/oracle/system01.dbf
  Enter a number of file datafile = name=/u01/app/oracle/oradata/oracle/sysaux01.dbf 00002
  Enter a number of file datafile = name=/u01/app/oracle/oradata/oracle/undotbs01.dbf 00003
  Enter a number of file datafile = 00005 name=/u01/app/oracle/oradata/oracle/example01.dbf
  Enter a number of file datafile = name=/u01/app/oracle/oradata/oracle/users01.dbf 00004
  channel ORA_DISK_1: from room 1 to 17 April 14
  channel ORA_DISK_1: finished piece 1 to 17 April 14
  piece handle=/u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_nnndf_TAG20140417T230734_9o1j980f_.bkp tag = TAG20140417T230734 comment = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:57
  channel ORA_DISK_1: starting full datafile from backup set
  channel ORA_DISK_1: specifying datafile (s) in the backup set
  including the current control in the backup set file
  including current SPFILE in the backup set
  channel ORA_DISK_1: from room 1 to 17 April 14
  channel ORA_DISK_1: finished piece 1 to 17 April 14
  piece handle=/u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_ncsnf_TAG20140417T230734_9o1jc09s_.bkp tag = TAG20140417T230734 comment = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:01
  Backup finished on 17 April 14

  3. change the data in the test table

  $ sqlplus / as sysdba

  SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 23:10:16 2014

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

  
  Connected to:
  Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
  With partitioning, OLAP, Data Mining and Real Application Testing options

  SQL > select * from test;

  ID
  ----------
  1

  SQL > update test set ID = 2;

  1 line update.

  SQL > commit;

  Validation complete.

  4. restore the database

  RMAN target /.

  Recovery Manager: release 11.2.0.1.0 - Production Fri Apr 17 23:11:15 2014

  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

  connected to target database: ORACLE (DBID = 1672007929)

  RMAN > shutdown immediate;

  using the control file of the target instead of recovery catalog database

  database closed

  dismounted database

  Instance Oracle to close

  RMAN > bootable media.

  connected to the database target (not started)

  Oracle instance started

  mounted database

  Total System Global Area 835104768 bytes

  Bytes of size 2217952 fixed

  629147680 variable size bytes

  197132288 of database buffers bytes

  Redo buffers 6606848 bytes

  RMAN > restore database;

  From restoration to April 17, 14

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 156 type device = DISK

  channel ORA_DISK_1: from the restore backup set data file

  channel ORA_DISK_1: specifying datafile (s) to restore from backup set

  channel ORA_DISK_1: restore datafile 00001 to /u01/app/oracle/oradata/oracle/system01.dbf

  channel ORA_DISK_1: restore datafile 00002 to /u01/app/oracle/oradata/oracle/sysaux01.dbf

  channel ORA_DISK_1: restore datafile 00003 to /u01/app/oracle/oradata/oracle/undotbs01.dbf

  channel ORA_DISK_1: restore datafile 00004 in /u01/app/oracle/oradata/oracle/users01.dbf

  channel ORA_DISK_1: restore datafile 00005 to /u01/app/oracle/oradata/oracle/example01.dbf

  channel ORA_DISK_1: backup /u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_nnndf_TAG20140417T230734_9o1j980f_.bkp piece reading

  channel ORA_DISK_1: room handle=/u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_nnndf_TAG20140417T230734_9o1j980f_.bkp tag = TAG20140417T230734

  channel ORA_DISK_1: restored the backup part 1

  channel ORA_DISK_1: restore complete, duration: 00:00:55

  Restoration finished in 17 April 14

  RMAN > restore database;

  To go back to April 17, 14

  using channel ORA_DISK_1

  starting media recovery

  media recovery complete, duration: 00:00:03

  Finished recover at April 17, 14

  RMAN > sql 'alter database open;

  SQL statement: alter database open

  5. check if the data has been restored

  sqlplus / as sysdba

  SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 23:14:39 2014

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

  
  Connected to:
  Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
  With partitioning, OLAP, Data Mining and Real Application Testing options

  SQL > select * from test;

  ID
  ----------
  2

  Summary:

  Data has not changed. Provided the ID is 1, but after the success of data recovery is not restored (ID is always 2).

  Can someone help me? What I am doing wrong?

  Database is Oracle 11 g with archivelog active

  Ol6 2.6.39 Linux OS - 300.17.2.el6uek.x86_64

  RMAN > restore database;

  To go back to April 17, 14

  using channel ORA_DISK_1

  starting media recovery

  media recovery complete, duration: 00:00:03

  Finished recover at April 17, 14

  RMAN > sql 'alter database open;

  SQL statement: alter database open

  5. check if the data has been restored

  sqlplus / as sysdba

  SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 23:14:39 2014

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

  Connected to:
  Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
  With partitioning, OLAP, Data Mining and Real Application Testing options

  SQL > select * from test;

  ID
  ----------
  2

  Summary:

  Data has not changed. Provided the ID is 1, but after the success of data recovery is not restored (ID is always 2).

  Can someone help me? What I am doing wrong?

  Database is Oracle 11 g with archivelog active

  the recovery was successful, but achieved your goal.

  There are several options to reach your goal to recover your database to a particular State that is point in time.

  1 restore the file of control as noted above. you restore the control file must not be aware of the generated once archivelog that you update your table. IE backup controlfile prior you updatedyour table.

  2. do not apply archivelog all during recovery. You can use SNA, SEQUENCE, RESTORE POINT option of the recover command. This option requires that you open your database with resetlog.

  read: scene of Flashback and the database Point-in - time recovery

  After a restore successful your database (before the recover command), you can "alter database open read-only" to check and confirm the values in the table.

  HTH

  Tobi

• Duplication of database problem

  
  Hello

  I cloned my production oracle db (11.2.0.1) to a test system (11.2.0.3) using the backup. I had an incomplete recovery.

  When I tried to open the database with reselogs he asked me to start the database with the upgrade option. And the open database.

  But whenever I restart the database, that he wants me to use the UPGRADE option

  Please suggest what to do

  SQL > startup;
  ORACLE instance started.

  Total System Global Area 1068937216 bytes
  Bytes of size 2232840 fixed
  616566264 variable size bytes
  444596224 of database buffers bytes
  Redo buffers 5541888 bytes
  Mounted database.
  ORA-01092: ORACLE instance is complete. Disconnection forced
  ORA-00704: bootstrap failure process
  ORA-39700: database must be opened with the UPGRADE option
  Process ID: 11766
  Session ID: 96 serial number: 3

  SQL > startup upgrade;
  ORACLE instance started.

  Total System Global Area 1068937216 bytes
  Bytes of size 2232840 fixed
  616566264 variable size bytes
  444596224 of database buffers bytes
  Redo buffers 5541888 bytes
  Mounted database.
  Open database.
  SQL >

  Thank you

  1 always read the installation to come with an upgrade instructions. Your question is redundant, because you need to do is described in the instructions

  2 as stated in the notes

  Connect / as sysdba

  start upgrade

  @?/rdbms/admin/catupgrd.sql

  That's all there is to it.

  Next time, PLEASE read the documentation before asking a redundant question.

  -------------

  Sybrand Bakker

  Senior Oracle DBA

• Effects of the opening of a primary database in resetlogs on the standby database

  Hi all

  Operating system: Solaris

  DB: 11 gR 2

  Can anyone throw some light below the explanation is given in case of recovery through the OPEN RESETLOGS Statement oracle documentation

  If the database pending...	Then...	Perform these steps...
  Not asked to redo data beyond the new resetlogs SCN (after the start of the new branch of data recovery)	Redo apply automatically takes the new branch of the roll forward.	No manual intervention is required. The MRP automatically resynchronizes the database pending with the new branch of data recovery.

  Here is the link of the source:

  Manage a database of physical standby

  Kind regards

  Just to give a concrete example, I did a test on one of my VM boxes. The database currently shows:

  SQL > select sequence #, the journal of v status $;

  SEQUENCE # STATUS

  ---------- ----------------

  34 ACTIVE

  CURRENT 35

  ACTIVE 33

  While on the eve, I stopped the redo apply so the standby status is:

  SQL > select sequence #, used from v$ archived_log;

  SEQUENCE # APPLIED

  ---------- ---------

  YES 30

  31 YES

  32 YES

  33 NO.

  34 NO.

  The database ensures in a few newspapers behind the primary.

  On the primary, I moved the journal a few sequences, close, the bootable media and restored and recovered 37 sequence:

  RMAN > run

  2 > {}

  3 > restore database;

  4 > up 37 sequence;

  5 > restore database;

  6 > alter database open resetlogs;

  {7 >}

  During the open resetlogs operation, I have to tail the log of alerts on the standby database and the following output shown:

  RFS [11]: identified the type of database such as 'physical' standby: customer is ARCH pid 17192

  RFS [11]: new branch archives REDO: 844006029 current: 843649185

  RFS [11]: Journal selected 102 for thread 1 1 dbid-204899919 branch of the 844006029 sequence

  RFS [11]: new Branch (resetlogs_id) of archive REDO: before 844006029: 843649185

  RFS [11]: ID of Activation of archives: current 0xf3d44942: 0xf3cf5ac3

  RFS [11]: effect of primary database OPEN RESETLOGS

  RFS [11]: entry of Incarnation added to Branch (resetlogs_id): 844006029 (ORCL11PS)

  Fri Apr 04 14:07:39 2014

  Definition of embodiment of recovery target 2

  Fri Apr 04 14:07:39 2014

  Archived journal 21 additional for each sequence 1 1 0xf3d44942 dest ID thread entry 1:

  So as you can see, the log shows the standby detects the resetlogs on the primary operation and the new branch of the roll forward and received the next archivelog with sequence 1.

  Audit on the eve, it shows the status following the archivelogs:

  SEQUENCE # APPLIED

  ---------- ---------

  31 YES

  32 YES

  33 NO.

  34 NO.

  35 NO.

  36 NO.

  37 NO.

  38 NO.

  1 NO.

  2 NO.

  And after restart the managed recovery process, it now shows:

  SEQUENCE # APPLIED

  ---------- ---------

  31 YES

  YES 30

  YES 19

  YES 33

  34 YES

  35 YES

  YES 36

  37 NO.

  38 NO.

  1 YES

  2 YES

  Archivelogs with sequence 37 and 38 were not implemented because of the CAMILLE on the main sequence until (but not including!) 37 and then properly applied the next archivelogs of the new branch of the roll forward, with sequence 1 and 2.