29.10.2018 15:29
Sullen
 
Alert.log
Mon Oct 29 18:11:38 2018
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 2
Number of processor cores in the system is 1
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 =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Mon Oct 29 18:11:52 2018
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.1 Service Pack 1
CPU : 2 - type 586, 1 Physical Cores
Process Affinity : 0x0x00000000
Memory (Avail/Total): Ph:1901M/3025M, Ph+PgF:4054M/6050M, VA:890M/2047M
Using parameter settings in server-side spfile C:\APP\1\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEDBOSHA06.ORA
System parameters with non-default values:
processes = 150
nls_language = "RUSSIAN"
nls_territory = "RUSSIA"
memory_target = 1504M
control_files = "C:\DBOSHA06\DBOSHA06\CONTROL01.CTL"
control_files = "C:\APP\1\FAST_RECOVERY_AREA\DBOSHA06\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.4.0"
log_archive_format = "ARC%S_%R.%T"
db_recovery_file_dest = "C:\app\1\fast_recovery_area"
db_recovery_file_dest_size= 20960M
undo_tablespace = "UNDOTBS1"
O7_DICTIONARY_ACCESSIBILITY= TRUE
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=DBOSHA06XDB)"
audit_file_dest = "C:\APP\1\ADMIN\DBOSHA06\ADUMP"
audit_trail = "DB"
db_name = "DBOSHA06"
open_cursors = 300
diagnostic_dest = "C:\APP\1"
Mon Oct 29 18:12:27 2018
PMON started with pid=2, OS id=2684
Mon Oct 29 18:12:27 2018
PSP0 started with pid=3, OS id=2756
Mon Oct 29 18:12:27 2018
VKTM started with pid=4, OS id=2792 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Mon Oct 29 18:12:27 2018
GEN0 started with pid=5, OS id=2800
Mon Oct 29 18:12:27 2018
DIAG started with pid=6, OS id=2736
Mon Oct 29 18:12:27 2018
DBRM started with pid=7, OS id=2796
Mon Oct 29 18:12:27 2018
DIA0 started with pid=8, OS id=2836
Mon Oct 29 18:12:27 2018
MMAN started with pid=9, OS id=2856
Mon Oct 29 18:12:27 2018
DBW0 started with pid=10, OS id=2844
Mon Oct 29 18:12:27 2018
LGWR started with pid=11, OS id=2840
Mon Oct 29 18:12:27 2018
CKPT started with pid=12, OS id=2832
Mon Oct 29 18:12:27 2018
SMON started with pid=13, OS id=2828
Mon Oct 29 18:12:28 2018
RECO started with pid=14, OS id=2780
Mon Oct 29 18:12:28 2018
MMON started with pid=15, OS id=2932
Mon Oct 29 18:12:28 2018
MMNL started with pid=16, OS id=2920
Mon Oct 29 18:12:28 2018
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\1
Mon Oct 29 18:12:28 2018
alter database mount exclusive
Successful mount of redo thread 1, with mount id 3969194508
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
LGWR: STARTING ARCH PROCESSES
Mon Oct 29 18:12:33 2018
ARC0 started with pid=20, OS id=3064
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Mon Oct 29 18:12:34 2018
ARC1 started with pid=21, OS id=296
Mon Oct 29 18:12:34 2018
ARC2 started with pid=22, OS id=3068
Mon Oct 29 18:12:34 2018
ARC3 started with pid=23, OS id=108
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 C:\APP\1\diag\rdbms\dbosha06\dbosha06\trace\dbosha06_ora_2968.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 21978152960 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.
************************************************************************
ARCH: Error 19809 Creating archive log file to 'C:\APP\1\FAST_RECOVERY_AREA\DBOSHA06\ARCHIVELOG\2018_10_29\O1_MF_1_379_%U_.ARC'
Errors in file C:\APP\1\diag\rdbms\dbosha06\dbosha06\trace\dbosha06_arc2_3068.trc:
ORA-19815: ПРЕДУПРЕЖДЕНИЕ. db_recovery_file_dest_size из 21978152960 байт 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.
************************************************************************
ARC2: Error 19809 Creating archive log file to 'C:\APP\1\FAST_RECOVERY_AREA\DBOSHA06\ARCHIVELOG\2018_10_29\O1_MF_1_380_%U_.ARC'
Errors in file C:\APP\1\diag\rdbms\dbosha06\dbosha06\trace\dbosha06_ora_2968.trc:
ORA-16038: log 2 sequence# 379 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1: 'C:\DBOSHA06\DBOSHA06\REDO02.LOG'
USER (ospid: 2968): terminating the instance due to error 16038
System state dump requested by (instance=1, osid=2968), summary=[abnormal instance termination].
System State dumped to trace file C:\APP\1\diag\rdbms\dbosha06\dbosha06\trace\dbosha06_diag_2736_20181029181236.trc
Dumping diagnostic data in directory=[cdmp_20181029181236], requested by (instance=1, osid=2968), summary=[abnormal instance termination].
Mon Oct 29 18:12:39 2018
Instance terminated by USER, pid = 2968

т.е. база жива, а подконнектиться не могу.
целый день воюю,а толку 0!
Помогите пожалуйста!
29.10.2018 15:33
Mtirt
 
Так на чистом английском написано, что можно сделать:
Цитата:
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.
***************************
Рекомендую начать с пункта № 3.
Т.е.

sqlplus /nolog
conn / as sysdba;
shutdown immediate;
startup mount;
alter system set db_recovery_file_dest_size=50G scope=both;
alter database open;

Потом запустить скрипт rman-бэкапа и убедиться, что он работает
29.10.2018 15:33
OlegON
 
Еще вариант, чтобы не погружаться в дальнейшие вопросы: https://olegon.ru/showthread.php?t=19224
29.10.2018 15:36
Sullen
 
Пробовал уже - oradim -STARTUP -SID DBO -STARTTYPE inst -PFILE pfile="C:\APP\1\admin\DBO\Pfile\init.ora.42920181516"
ORA-01017 invalid username/password; logon denied
29.10.2018 15:39
Sullen
 
как раз не могу подключиться...
29.10.2018 15:42
Mtirt
 
Цитата:
Sullen как раз не могу подключиться...
Результат можно увидеть?

Так подключится?
sqlplus sys/пароль_sys@имя_базы as sysdba
29.10.2018 15:43
Sullen
 
один секунд Танюша...
29.10.2018 15:45
Mtirt
 
Цитата:
Sullen Пробовал уже - oradim -STARTUP -SID DBO -STARTTYPE inst -PFILE pfile="C:\APP\1\admin\DBO\Pfile\init.ora.42920181516"
ORA-01017 invalid username/password; logon denied
И слава богу. Не трогайте oradim, пожалуйста.
Можно базу и с концами удалить.
А восстановится ли она у вас из бэкапа - очень большой вопрос.
29.10.2018 15:46
Sullen
 
На листенер обругивается (по адресу хоста то же самое)

Форум на базе vBulletin®
Copyright © Jelsoft Enterprises Ltd.
В случае заимствования информации гипертекстовая индексируемая ссылка на Форум обязательна.