Извините, не подумал
Tue Sep 22 08:36:50 2015
Instance terminated by USER, pid = 1840
Tue Sep 22 08:42:40 2015
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
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.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile D:\APP\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEAUTOSPRUT.ORA
System parameters with non-default values:
processes = 500
sessions = 772
memory_target = 9856M
control_files = "D:\ORADATA\AUTOSPRUT\CONTROL01.CTL"
control_files = "D:\FLASH\AUTOSPRUT\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.0.0"
log_archive_format = "ARC%S_%R.%T"
db_files = 4096
db_recovery_file_dest = "D:\flash"
db_recovery_file_dest_size= 100G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=AUTOSPRUTXDB)"
parallel_max_servers = 32
audit_file_dest = "D:\APP\ADMIN\AUTOSPRUT\ADUMP"
audit_trail = "DB"
db_name = "AUTOSPRUT"
open_cursors = 300
star_transformation_enabled= "TRUE"
diagnostic_dest = "D:\APP"
Tue Sep 22 08:42:48 2015
PMON started with pid=2, OS id=2436
Tue Sep 22 08:42:48 2015
VKTM started with pid=3, OS id=2440 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Tue Sep 22 08:42:48 2015
GEN0 started with pid=4, OS id=2444
Tue Sep 22 08:42:48 2015
DIAG started with pid=5, OS id=2448
Tue Sep 22 08:42:48 2015
DBRM started with pid=6, OS id=2452
Tue Sep 22 08:42:48 2015
PSP0 started with pid=7, OS id=2456
Tue Sep 22 08:42:48 2015
DIA0 started with pid=8, OS id=2460
Tue Sep 22 08:42:48 2015
MMAN started with pid=9, OS id=2464
Tue Sep 22 08:42:48 2015
DBW0 started with pid=10, OS id=2468
Tue Sep 22 08:42:48 2015
LGWR started with pid=11, OS id=2472
Tue Sep 22 08:42:48 2015
CKPT started with pid=12, OS id=2476
Tue Sep 22 08:42:48 2015
SMON started with pid=13, OS id=2480
Tue Sep 22 08:42:48 2015
RECO started with pid=14, OS id=2484
Tue Sep 22 08:42:48 2015
MMON started with pid=15, OS id=2488
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = D:\app
Tue Sep 22 08:42:48 2015
MMNL started with pid=16, OS id=2492
Tue Sep 22 08:42:51 2015
alter database mount exclusive
Successful mount of redo thread 1, with mount id 1585599179
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Tue Sep 22 08:42:59 2015
LGWR: STARTING ARCH PROCESSES
Tue Sep 22 08:42:59 2015
ARC0 started with pid=20, OS id=2704
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Tue Sep 22 08:43:01 2015
ARC1 started with pid=21, OS id=2708
Tue Sep 22 08:43:01 2015
ARC2 started with pid=22, OS id=2712
Tue Sep 22 08:43:01 2015
ARC3 started with pid=23, OS id=2716
ARC1: Archival started
ARC2: Archival started
ARC2: Becoming the 'no FAL' ARCH
ARC2: Becoming the 'no SRL' ARCH
ARC1: Becoming the heartbeat ARCH
sksasmowrt WriteConsole error 6
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Errors in file d:\app\diag\rdbms\AUTOSPRUT\AUTOSPRUT\trace\AUTOSPRUT_arc2_2712.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 107374182400 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
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
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.
************************************************************************
Errors in file d:\app\diag\rdbms\AUTOSPRUT\AUTOSPRUT\trace\AUTOSPRUT_arc2_2712.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 167480832 bytes disk space from 107374182400 limit
ARC2: Error 19809 Creating archive log file to 'D:\FLASH\AUTOSPRUT\ARCHIVELOG\2015_09_22\O1_MF_1_569_%U_.ARC'
Tue Sep 22 08:43:04 2015
Errors in file d:\app\diag\rdbms\AUTOSPRUT\AUTOSPRUT\trace\AUTOSPRUT_ora_2508.trc:
ORA-19815: ??????????????. db_recovery_file_dest_size ?? 107374182400 ???? 100.00% ????????????, ? 0 ???? ???????? ??????????.
************************************************************************
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
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
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.
************************************************************************
Errors in file d:\app\diag\rdbms\AUTOSPRUT\AUTOSPRUT\trace\AUTOSPRUT_ora_2508.trc:
ORA-19809: ????????? ?????? ??? ?????? ??????????????
ORA-19804: ?????????? ???????????? ???????? ???????????? ?????? 168771584 ??-?? ??????????? 107374182400
ARCH: Error 19809 Creating archive log file to 'D:\FLASH\AUTOSPRUT\ARCHIVELOG\2015_09_22\O1_MF_1_568_%U_.ARC'
ARCH: Archival stopped, error occurred. Will continue retrying
Errors in file d:\app\diag\rdbms\AUTOSPRUT\AUTOSPRUT\trace\AUTOSPRUT_arc2_2712.trc:
ORA-16038: log 2 sequence# 569 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1: 'D:\ORADATA\AUTOSPRUT\REDO02.LOG'
Errors in file d:\app\diag\rdbms\AUTOSPRUT\AUTOSPRUT\trace\AUTOSPRUT_ora_2508.trc:
ORA-16038: ?????? 1 ? ??????? ?????????????????? 568 ?? ????? ???? ???????????
ORA-19809: ????????? ?????? ??? ?????? ??????????????
ORA-00312: ??????????? ???????? 1 ???????? 1: 'D:\ORADATA\AUTOSPRUT\REDO01.LOG'
USER (ospid: 2508): terminating the instance due to error 16038
Instance terminated by USER, pid = 2508