Copyright (c) 1982, 2013, Oracle. All rights reserved.
ORACLE instance started.
Database mounted.
My alert log file in the path C:\app\KALPATARU\diag\rdbms\orcl\orcl\trace\alert_orcl.log contents.
Fatal NI connect error 12638, connecting to:
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 11.2.0.4.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.2.0.4.0 - Production
Time: 12-JAN-2017 22:31:52
Tracing not turned on.
Tns error struct:
ns main err code: 12638
TNS-12638: Credential retrieval failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Tue Jan 17 19:10:57 2017
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 4
Number of processor cores in the system is 2
Number of processor sockets in the system is 1
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =84
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Windows NT Version V6.2
CPU : 4 - type 586, 2 Physical Cores
Process Affinity : 0x0x00000000
Memory (Avail/Total): Ph:6204M/8122M, Ph+PgF:13277M/16314M, VA:2502M/4095M
Using parameter settings in server-side spfile C:\APP\KALPATARU\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEORCL.ORA
System parameters with non-default values:
processes = 500
shared_pool_size = 1G
memory_target = 1800M
control_files = "C:\APP\KALPATARU\ORADATA\ORCL\CONTROL01.CTL"
control_files = "C:\APP\KALPATARU\FAST_RECOVERY_AREA\ORCL\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.4.0"
db_files = 600
db_recovery_file_dest = "C:\app\KALPATARU\fast_recovery_area"
db_recovery_file_dest_size= 12G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
local_listener = "LISTENER_ORCL"
session_cached_cursors = 100
smtp_out_server = "127.0.0.1:25"
audit_file_dest = "C:\APP\KALPATARU\ADMIN\ORCL\ADUMP"
audit_trail = "DB"
db_name = "orcl"
open_cursors = 800
diagnostic_dest = "C:\APP\KALPATARU"
Tue Jan 17 19:11:27 2017
PMON started with pid=2, OS id=4180
Tue Jan 17 19:11:27 2017
PSP0 started with pid=3, OS id=4184
Tue Jan 17 19:11:28 2017
VKTM started with pid=4, OS id=4192 at elevated priority
Tue Jan 17 19:11:28 2017
GEN0 started with pid=5, OS id=4196
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Tue Jan 17 19:11:28 2017
DIAG started with pid=6, OS id=4200
Tue Jan 17 19:11:28 2017
DBRM started with pid=7, OS id=4204
Tue Jan 17 19:11:28 2017
DIA0 started with pid=8, OS id=4208
Tue Jan 17 19:11:28 2017
MMAN started with pid=9, OS id=4212
Tue Jan 17 19:11:31 2017
DBW0 started with pid=10, OS id=4220
Tue Jan 17 19:11:31 2017
LGWR started with pid=11, OS id=4224
Tue Jan 17 19:11:31 2017
SMON started with pid=13, OS id=4232
Tue Jan 17 19:11:31 2017
RECO started with pid=14, OS id=4236
Tue Jan 17 19:11:31 2017
CKPT started with pid=12, OS id=4228
Tue Jan 17 19:11:31 2017
MMON started with pid=15, OS id=4240
Tue Jan 17 19:11:31 2017
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Jan 17 19:11:31 2017
MMNL started with pid=16, OS id=4244
starting up 1 shared server(s) ...
ORACLE_BASE from environment = C:\app\KALPATARU
Tue Jan 17 19:11:41 2017
alter database mount exclusive
Tue Jan 17 19:11:48 2017
Successful mount of redo thread 1, with mount id 1461298541
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Beginning crash recovery of 1 threads
Tue Jan 17 19:11:51 2017
parallel recovery started with 3 processes
Started redo scan
Completed redo scan
read 0 KB redo, 0 data blocks need recovery
Started redo application at
Thread 1: logseq 487, block 86800, scn 9344114
Recovery of Online Redo Log: Thread 1 Group 1 Seq 487 Reading mem 0
Mem# 0: C:\APP\KALPATARU\ORADATA\ORCL\REDO01.LOG
Completed redo application of 0.00MB
Completed crash recovery at
Thread 1: logseq 487, block 86800, scn 9364115
0 data blocks read, 0 data blocks written, 0 redo k-bytes read
LGWR: STARTING ARCH PROCESSES
Tue Jan 17 19:11:54 2017
ARC0 started with pid=23, OS id=4820
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Tue Jan 17 19:11:55 2017
ARC1 started with pid=24, OS id=4824
Tue Jan 17 19:11:55 2017
ARC2 started with pid=25, OS id=4828
Tue Jan 17 19:11:55 2017
ARC3 started with pid=26, OS id=4832
ARC1: Archival started
ARC2: Archival started
Errors in file C:\APP\KALPATARU\diag\rdbms\orcl\orcl\trace\orcl_ora_4716.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 12884901888 bytes is 100.00% used, and has 0 remaining bytes available.
ARC2: Becoming the 'no FAL' ARCH
************************************************************************
ARC2: Becoming the 'no SRL' ARCH
You have following choices to free up space from recovery area:
ARC1: Becoming the heartbeat ARCH
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
ARC3: Archival started
reflect the new space.
ARC0: STARTING ARCH PROCESSES COMPLETE
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************
ARCH: Error 19809 Creating archive log file to 'C:\APP\KALPATARU\FAST_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_01_17\O1_MF_1_485_%U_.ARC'
Errors in file C:\APP\KALPATARU\diag\rdbms\orcl\orcl\trace\orcl_ora_4716.trc:
ORA-16038: log 3 sequence# 485 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 3 thread 1: 'C:\APP\KALPATARU\ORADATA\ORCL\REDO03.LOG'
Errors in file C:\APP\KALPATARU\diag\rdbms\orcl\orcl\trace\orcl_arc2_4828.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 12884901888 bytes is 100.00% used, and has 0 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
USER (ospid: 4716): terminating the instance due to error 16038
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
Tue Jan 17 19:12:00 2017
System state dump requested by (instance=1, osid=4716), summary=[abnormal instance termination].
4. Delete unnecessary files using RMAN DELETE command. If an operating
System State dumped to trace file C:\APP\KALPATARU\diag\rdbms\orcl\orcl\trace\orcl_diag_4200_20170117191200.trc
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
Dumping diagnostic data in directory=[cdmp_20170117191200], requested by (instance=1, osid=4716), summary=[abnormal instance termination].
************************************************************************
Tue Jan 17 19:12:04 2017
Instance terminated by USER, pid = 4716
Tue Jan 17 22:09:10 2017
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 4
Number of processor cores in the system is 2
Number of processor sockets in the system is 1
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =84
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Windows NT Version V6.2
CPU : 4 - type 586, 2 Physical Cores
Process Affinity : 0x0x00000000
Memory (Avail/Total): Ph:5226M/8122M, Ph+PgF:12050M/16314M, VA:2464M/4095M
Using parameter settings in server-side spfile C:\APP\KALPATARU\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEORCL.ORA
System parameters with non-default values:
processes = 500
shared_pool_size = 1G
memory_target = 1800M
control_files = "C:\APP\KALPATARU\ORADATA\ORCL\CONTROL01.CTL"
control_files = "C:\APP\KALPATARU\FAST_RECOVERY_AREA\ORCL\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.4.0"
db_files = 600
db_recovery_file_dest = "C:\app\KALPATARU\fast_recovery_area"
db_recovery_file_dest_size= 12G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
local_listener = "LISTENER_ORCL"
session_cached_cursors = 100
smtp_out_server = "127.0.0.1:25"
audit_file_dest = "C:\APP\KALPATARU\ADMIN\ORCL\ADUMP"
audit_trail = "DB"
db_name = "orcl"
open_cursors = 800
diagnostic_dest = "C:\APP\KALPATARU"
Tue Jan 17 22:09:23 2017
PMON started with pid=2, OS id=8164
Tue Jan 17 22:09:23 2017
PSP0 started with pid=3, OS id=8036
Tue Jan 17 22:09:25 2017
VKTM started with pid=4, OS id=2672 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Tue Jan 17 22:09:25 2017
GEN0 started with pid=5, OS id=5408
Tue Jan 17 22:09:25 2017
DBRM started with pid=7, OS id=7736
Tue Jan 17 22:09:25 2017
DIAG started with pid=6, OS id=7196
Tue Jan 17 22:09:25 2017
MMAN started with pid=9, OS id=8408
Tue Jan 17 22:09:28 2017
DBW0 started with pid=10, OS id=6820
Tue Jan 17 22:09:28 2017
LGWR started with pid=11, OS id=7996
Tue Jan 17 22:09:25 2017
DIA0 started with pid=8, OS id=3256
Tue Jan 17 22:09:28 2017
CKPT started with pid=12, OS id=4288
Tue Jan 17 22:09:29 2017
RECO started with pid=14, OS id=1144
Tue Jan 17 22:09:29 2017
MMON started with pid=15, OS id=8340
Tue Jan 17 22:09:29 2017
SMON started with pid=13, OS id=7120
Tue Jan 17 22:09:29 2017
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = C:\app\KALPATARU
Tue Jan 17 22:09:33 2017
ALTER DATABASE MOUNT
Tue Jan 17 22:09:29 2017
MMNL started with pid=16, OS id=5360
Successful mount of redo thread 1, with mount id 1461295133
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Tue Jan 17 22:14:07 2017
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Stopping background process MMNL
Stopping background process MMON
License high water mark = 2
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
ALTER DATABASE DISMOUNT
Shutting down archive processes
Archiving is disabled
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Tue Jan 17 22:14:11 2017
Stopping background process VKTM
Tue Jan 17 22:14:14 2017
Instance shutdown complete
Tue Jan 17 22:14:24 2017
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 4
Number of processor cores in the system is 2
Number of processor sockets in the system is 1
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =84
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Windows NT Version V6.2
CPU : 4 - type 586, 2 Physical Cores
Process Affinity : 0x0x00000000
Memory (Avail/Total): Ph:5224M/8122M, Ph+PgF:12042M/16314M, VA:2459M/4095M
Using parameter settings in server-side spfile C:\APP\KALPATARU\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEORCL.ORA
System parameters with non-default values:
processes = 500
shared_pool_size = 1G
memory_target = 1800M
control_files = "C:\APP\KALPATARU\ORADATA\ORCL\CONTROL01.CTL"
control_files = "C:\APP\KALPATARU\FAST_RECOVERY_AREA\ORCL\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.4.0"
db_files = 600
db_recovery_file_dest = "C:\app\KALPATARU\fast_recovery_area"
db_recovery_file_dest_size= 12G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
local_listener = "LISTENER_ORCL"
session_cached_cursors = 100
smtp_out_server = "127.0.0.1:25"
audit_file_dest = "C:\APP\KALPATARU\ADMIN\ORCL\ADUMP"
audit_trail = "DB"
db_name = "orcl"
open_cursors = 800
diagnostic_dest = "C:\APP\KALPATARU"
Tue Jan 17 22:14:38 2017
PMON started with pid=2, OS id=7420
Tue Jan 17 22:14:38 2017
PSP0 started with pid=3, OS id=8528
Tue Jan 17 22:14:39 2017
VKTM started with pid=4, OS id=8784 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Tue Jan 17 22:14:39 2017
GEN0 started with pid=5, OS id=7376
Tue Jan 17 22:14:39 2017
DIA0 started with pid=8, OS id=6244
Tue Jan 17 22:14:39 2017
DBRM started with pid=7, OS id=6232
Tue Jan 17 22:14:39 2017
DIAG started with pid=6, OS id=5812
Tue Jan 17 22:14:39 2017
MMAN started with pid=9, OS id=7552
Tue Jan 17 22:14:42 2017
DBW0 started with pid=10, OS id=7204
Tue Jan 17 22:14:42 2017
CKPT started with pid=12, OS id=8804
Tue Jan 17 22:14:42 2017
LGWR started with pid=11, OS id=7052
Tue Jan 17 22:14:42 2017
SMON started with pid=13, OS id=7272
Tue Jan 17 22:14:42 2017
MMNL started with pid=16, OS id=2596
Tue Jan 17 22:14:42 2017
RECO started with pid=14, OS id=8504
Tue Jan 17 22:14:42 2017
MMON started with pid=15, OS id=224
Tue Jan 17 22:14:42 2017
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = C:\app\KALPATARU
Tue Jan 17 22:14:48 2017
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 1461317464
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Tue Jan 17 22:14:53 2017
ALTER DATABASE OPEN
Tue Jan 17 22:14:54 2017
LGWR: STARTING ARCH PROCESSES
Tue Jan 17 22:14:54 2017
ARC0 started with pid=19, OS id=6748
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Tue Jan 17 22:14:55 2017
ARC1 started with pid=21, OS id=4268
Tue Jan 17 22:14:55 2017
ARC2 started with pid=22, OS id=7344
Errors in file C:\APP\KALPATARU\diag\rdbms\orcl\orcl\trace\orcl_ora_7868.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 12884901888 bytes is 100.00% used, and has 0 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
ARC1: Archival started
BACKUP RECOVERY AREA command.
ARC2: Archival started
3. Add disk space and increase db_recovery_file_dest_size parameter to
ARC1: Becoming the 'no FAL' ARCH
reflect the new space.
ARC1: Becoming the 'no SRL' ARCH
4. Delete unnecessary files using RMAN DELETE command. If an operating
ARC2: Becoming the heartbeat ARCH
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************
ARCH: Error 19809 Creating archive log file to 'C:\APP\KALPATARU\FAST_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_01_17\O1_MF_1_485_%U_.ARC'
Tue Jan 17 22:14:55 2017
ARC3 started with pid=23, OS id=5216
Errors in file C:\APP\KALPATARU\diag\rdbms\orcl\orcl\trace\orcl_ora_7868.trc:
ORA-16038: log 3 sequence# 485 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 3 thread 1: 'C:\APP\KALPATARU\ORADATA\ORCL\REDO03.LOG'
USER (ospid: 7868): terminating the instance due to error 16038
Tue Jan 17 22:14:58 2017
System state dump requested by (instance=1, osid=7868), summary=[abnormal instance termination].
System State dumped to trace file C:\APP\KALPATARU\diag\rdbms\orcl\orcl\trace\orcl_diag_5812_20170117221458.trc
Dumping diagnostic data in directory=[cdmp_20170117221458], requested by (instance=1, osid=7868), summary=[abnormal instance termination].
Instance terminated by USER, pid = 7868