Home > database >  Open the oracle database to ora - 01092; Ora00704; Ora00600 error
Open the oracle database to ora - 01092; Ora00704; Ora00600 error

Time:09-23

The error log is as follows:

1. Alert_ora11. Log

Mon Apr 23 15:25:04 2018
Adjusting the default value of the parameter parallel_max_servers
From 1280 to 120 due to the value of the parameter the processes (150)
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION=0
LICENSE_SESSIONS_WARNING=0
The Initial number of CPU is 32
Number of processor cores in the system is 16
Number of processor sockets in the system is 2
Picked latch - free SCN scheme 3
Mon Apr 23 15:25:23 2018
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned off.
LICENSE_MAX_USERS=0
SYS auditing is disabled
NUMA system with 2 nodes detected
Starting up:
Oracle Database 11 g Enterprise Edition Release 11.2.0.4.0-64 - bit Production
With the Partitioning, OLAP, Data Mining, and Real Application Testing options.
Windows NT Version V6.2
CPU: 32 - type, 8664, 16 Physical Cores
The Process Affinity: 0 x0x0000000000000000
The Memory (the Avail/Total) : Ph: 178047 m/261741 m, Ph + PgF: 215729 m/300653 m
Using the parameter Settings in the server - side spfile D: \ APP \ PRODUCT \ 11.2.0 \ DBHOME_1 \ DATABASE \ SPFILEORA11 ORA
The System parameters with non - the default values:
The processes=150
Sga_target=78592 m
The control_files="D: \ APP \ ORADATA \ ORA11 \ CONTROL01 CTL"
The control_files="D: \ APP \ FAST_RECOVERY_AREA \ ORA11 \ CONTROL02 CTL"
Db_block_size=8192
Compatible="11.2.0.4.0"
Db_files=600
Db_recovery_file_dest="D: \ app \ fast_recovery_area"
Db_recovery_file_dest_size=400 g
Undo_management="MANUAL"
Undo_tablespace="UNDOTBS1"
Remote_login_passwordfile="EXCLUSIVE"
Db_domain="unicom. Db2"
Dispatchers="(TCP) PROTOCOL=(SERVICE=ora11XDB)"
Audit_file_dest="D: \ \ ADMIN \ ORA11 \ APP ADUMP"
Audit_trail="DB"
Db_name="ora11"
Open_cursors=300
Pga_aggregate_target=26174 m
Diagnostic_dest="D: \ APP"
Mon Apr 23 15:25:34 2018
PMON started with pid=2, OS id=4924
Mon Apr 23 15:25:34 2018
PSP0 started with pid=3, OS id=2512
Mon Apr 23 15:25:35 2018
VKTM started with pid=4, OS id=4640 at elevated priority
VKTM running at (10) millisec precision with DBRMS quantum (100) ms
Mon Apr 23 15:25:35 2018
Get started with pid=5, OS id=4820
Mon Apr 23 15:25:35 2018
DIAG started with pid=6, OS id=2792
Mon Apr 23 15:25:35 2018
DBRMS started with pid=7, OS id=4732
Mon Apr 23 15:25:35 2018
DIA0 started with pid=8, OS id=1564
Mon Apr 23 15:25:35 2018
MMAN started with pid=9, OS id=1688
Mon Apr 23 15:25:35 2018
DBW0 started with pid=10, OS id=4528
Mon Apr 23 15:25:35 2018
DBW1 started with pid=11, OS id=4480
Mon Apr 23 15:25:35 2018
DBW2 started with pid=12, OS id=3588
Mon Apr 23 15:25:35 2018
DBW3 started with pid=13, OS id=624
Mon Apr 23 15:25:35 2018
LGWR started with pid=14, OS id=2208
Mon Apr 23 15:25:35 2018
CKPT started with pid=15, OS id=3608
Mon Apr 23 15:25:35 2018
SMON started with pid=16, OS id=3376
Mon Apr 23 15:25:35 2018
RECO started with pid=17, OS id=4544
Mon Apr 23 15:25:35 2018
MMON started with pid=18, OS id=4288
Mon Apr 23 15:25:35 2018
MMNL started with pid=19, OS id=4740
Mon Apr 23 15:25:35 2018
Starting up a dispatcher (s) for the network address '(address=(PARTIAL=YES) (TCP) PROTOCOL=)'...
Starting up a Shared server (s)...
ORACLE_BASE from environment=D: \ app
Mon Apr 23 15:25:35 2018
The ALTER DATABASE MOUNT
Successful mount of redo thread 1, with the mount id 918190256
The Database mounted in Exclusive Mode
Lost the write protection, disabled
Completed: the ALTER DATABASE MOUNT
Mon Apr 23 15:25:40 2018
The ALTER DATABASE OPEN
Beginning crash recovery of threads 1
The parallel recovery started with 31 the processes
Started redo scan
Completed redo scan
Read 0 KB, redo 0 data blocks need recovery
Started redo application at
Thread 1: logseq 17, block 3, SCN 5833380769
Recovery of the Online Redo Log: Thread 1 Group, 2 Seq 17 Reading mem 0
Mem# 0: D: \ APP \ ORADATA \ ORA11 \ REDO02 LOG
Completed redo application of 0.00 MB
Completed crash recovery at
Thread 1: logseq 17, block 3, SCN 5833400770
0 data blocks read, 0 data blocks written, 0 redo k - bytes read
Mon Apr 23 15:25:48 2018
LGWR: STARTING the ARCH the PROCESSES
Mon Apr 23 15:25:48 2018
ARC0 started with pid=54, OS id=4336
ARC0: Archival started
LGWR: STARTING the ARCH the PROCESSES COMPLETE
ARC0: STARTING the ARCH the PROCESSES
Mon Apr 23 15:25:49 2018
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull
  • Related