Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Partial message trace from frozen installation Oracle 12c v. 1 Windows

2b165028-c901-4d76-a153-212308f2742eMar 24 2017 — edited Mar 26 2017

Sorry, output of Alert from popup installation is below :

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

Clearing online log 2 of thread 1 sequence number 0

Fri Mar 24 17:24:25 2017

Errors in file C:\APP\TMARONSON\diag\rdbms\orcl\orcl\trace\orcl_ora_8084.trc:

ORA-00313: open failed for members of log group 2 of thread 1

ORA-00312: online log 2 thread 1: 'C:\APP\TMARONSON\ORADATA\ORCL\REDO02.LOG'

ORA-27041: unable to open file

OSD-04002: unable to open file

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

Fri Mar 24 17:24:25 2017

Errors in file C:\APP\TMARONSON\diag\rdbms\orcl\orcl\trace\orcl_ora_8084.trc:

ORA-00313: open failed for members of log group 2 of thread 1

ORA-00312: online log 2 thread 1: 'C:\APP\TMARONSON\ORADATA\ORCL\REDO02.LOG'

ORA-27041: unable to open file

OSD-04002: unable to open file

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

Clearing online redo logfile 2 complete

Fri Mar 24 17:24:26 2017

Errors in file C:\APP\TMARONSON\diag\rdbms\orcl\orcl\trace\orcl_ora_8084.trc:

ORA-00313: open failed for members of log group 3 of thread 1

ORA-00312: online log 3 thread 1: 'C:\APP\TMARONSON\ORADATA\ORCL\REDO03.LOG'

ORA-27041: unable to open file

OSD-04002: unable to open file

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

Fri Mar 24 17:24:26 2017

Errors in file C:\APP\TMARONSON\diag\rdbms\orcl\orcl\trace\orcl_ora_8084.trc:

ORA-00313: open failed for members of log group 3 of thread 1

ORA-00312: online log 3 thread 1: 'C:\APP\TMARONSON\ORADATA\ORCL\REDO03.LOG'

ORA-27041: unable to open file

OSD-04002: unable to open file

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

Clearing online redo logfile 3 C:\APP\TMARONSON\ORADATA\ORCL\REDO03.LOG

Clearing online log 3 of thread 1 sequence number 0

Fri Mar 24 17:24:26 2017

Errors in file C:\APP\TMARONSON\diag\rdbms\orcl\orcl\trace\orcl_ora_8084.trc:

ORA-00313: open failed for members of log group 3 of thread 1

ORA-00312: online log 3 thread 1: 'C:\APP\TMARONSON\ORADATA\ORCL\REDO03.LOG'

ORA-27041: unable to open file

OSD-04002: unable to open file

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

Fri Mar 24 17:24:26 2017

Errors in file C:\APP\TMARONSON\diag\rdbms\orcl\orcl\trace\orcl_ora_8084.trc:

ORA-00313: open failed for members of log group 3 of thread 1

ORA-00312: online log 3 thread 1: 'C:\APP\TMARONSON\ORADATA\ORCL\REDO03.LOG'

ORA-27041: unable to open file

OSD-04002: unable to open file

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

Clearing online redo logfile 3 complete

Online log C:\APP\TMARONSON\ORADATA\ORCL\REDO01.LOG: Thread 1 Group 1 was previously cleared

Online log C:\APP\TMARONSON\ORADATA\ORCL\REDO02.LOG: Thread 1 Group 2 was previously cleared

Online log C:\APP\TMARONSON\ORADATA\ORCL\REDO03.LOG: Thread 1 Group 3 was previously cleared

Fri Mar 24 17:24:28 2017

Setting recovery target incarnation to 2

Fri Mar 24 17:24:28 2017

Ping without log force is disabled

.

Initializing SCN for created control file

Database SCN compatibility initialized to 1

Starting background process TMON

Fri Mar 24 17:24:29 2017

Assigning activation ID 1467260354 (0x57749dc2)

Thread 1 opened at log sequence 1

  Current log# 1 seq# 1 mem# 0: C:\APP\TMARONSON\ORADATA\ORCL\REDO01.LOG

Successful open of redo thread 1

Fri Mar 24 17:24:29 2017

SMON: enabling cache recovery

Fri Mar 24 17:24:29 2017

TMON started with pid=25, OS id=4376

Fri Mar 24 17:24:31 2017

[8084] Successfully onlined Undo Tablespace 2.

Undo initialization finished serial:0 start:3004508961 end:3004510179 diff:1218 ms (1.2 seconds)

Dictionary check beginning

Tablespace 'TEMP' #3 found in data dictionary,

but not in the controlfile. Adding to controlfile.

Dictionary check complete

Verifying minimum file header compatibility (11g) for tablespace encryption..

Verifying 11g file header compatibility for tablespace encryption completed

Fri Mar 24 17:24:31 2017

SMON: enabling tx recovery

Starting background process SMCO

Fri Mar 24 17:24:31 2017

SMCO started with pid=26, OS id=5236

Fri Mar 24 17:24:31 2017

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

WARNING: The following temporary tablespaces in container(CDB$ROOT)

         contain no files.

         This condition can occur when a backup controlfile has

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

         tablespaces.  That can be done using the SQL statement:

         ALTER TABLESPACE <tablespace_name> ADD TEMPFILE

         Alternatively, if these temporary tablespaces are no longer

         needed, then they can be dropped.

           Empty temporary tablespace: TEMP

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

Database Characterset is US7ASCII

Opening with Resource Manager plan: DEFAULT_CDB_PLAN

replication_dependency_tracking turned off (no async multimaster replication found)

AQ Processes can not start in restrict mode

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Apr 23 2017
Added on Mar 24 2017
1 comment
358 views