Не работает автостарт базы 11.2.0.3 : Oracle

alicedr · █ 26.09.2014 12:47

Oracle Ent. Edition 64bit 11.2.0.3
Windows Server 2008 R2 Standard 64bit
После выполнения ночного бекапа с выключением сервиса база или не стартует, или залипает. Проблема не системная, 1-2 раза в неделю, в остальные дни база старртует нормально.
Был аналогичный баг в 11.2.0.1, но в используемой мной версии он исправлен. По логам я не могу определить причину ошибки.

Код:

Windows System Log:
2014.09.26 2:07:27 The Супермаг - Сервер приложений service entered the stopped state.
2014.09.26 2:07:42 The OracleServiceDBNAME service entered the stopped state.
2014.09.26 2:08:15 The OracleOraDb11g_home1TNSListener service entered the stopped state.
2014.09.26 2:14:57 The OracleOraDb11g_home1TNSListener service entered the running state.
2014.09.26 2:16:08 The OracleServiceDBNAME service entered the running state.
2014.09.26 2:16:58 The Супермаг - Сервер приложений service entered the running state.
2014.09.26 9:05:42 The OracleServiceDBNAME service entered the stopped state.
2014.09.26 9:05:45 The OracleOraDb11g_home1TNSListener service entered the stopped state.
2014.09.26 9:06:08 The OracleServiceDBNAME service entered the running state.
2014.09.26 9:06:11 The OracleOraDb11g_home1TNSListener service entered the running state.

alicedr · █ 26.09.2014 12:57

Window Application log:

Код:

2014.09.26 2:07:38 Audit trail: LENGTH: '156' ACTION :[8] 'SHUTDOWN' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[9] 'KIBCSQL01' STATUS:[1] '0' DBID:[0] '' .
2014.09.26 2:07:38 Shutdown normal performed on instance DBNAME.
2014.09.26 2:07:39 All process in instance DBNAME stopped
2014.09.26 2:15:57 Audit trail: LENGTH: '155' ACTION :[7] 'CONNECT' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[9] 'KIBCSQL01' STATUS:[1] '0' DBID:[0] '' .
2014.09.26 2:15:58 Initializing SGA for instance DBNAME.
2014.09.26 2:16:06 Initializing PGA for process PMON in instance DBNAME.
2014.09.26 2:16:06 Initializing PGA for process PSP0 in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process VKTM in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process GEN0 in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process DIAG in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process DBRM in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process DIA0 in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process MMAN in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process DBW0 in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process LGWR in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process CKPT in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process SMON in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process RECO in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process MMON in instance DBNAME.
2014.09.26 2:16:07 Initializing PGA for process MMNL in instance DBNAME.
2014.09.26 2:16:08 Audit trail: LENGTH: '158' ACTION :[7] 'STARTUP' DATABASE USER:[1] '/' PRIVILEGE :[4] 'NONE' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[13] 'Not Available' STATUS:[1] '0' DBID:[0] '' .
2014.09.26 2:16:08 Audit trail: LENGTH: '156' ACTION :[7] 'CONNECT' DATABASE USER:[1] '/' PRIVILEGE :[4] 'NONE' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[9] 'KIBCSQL01' STATUS:[4] '1031' DBID:[0] '' .
2014.09.26 2:16:08 Audit trail: LENGTH: '156' ACTION :[7] 'CONNECT' DATABASE USER:[1] '/' PRIVILEGE :[4] 'NONE' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[9] 'KIBCSQL01' STATUS:[4] '1031' DBID:[0] '' .
2014.09.26 2:16:08 Audit trail: LENGTH: '158' ACTION :[7] 'CONNECT' DATABASE USER:[3] 'sys' PRIVILEGE :[4] 'NONE' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[9] 'KIBCSQL01' STATUS:[4] '1017' DBID:[0] '' .
2014.09.26 2:16:08 Audit trail: LENGTH: '158' ACTION :[7] 'CONNECT' DATABASE USER:[3] 'sys' PRIVILEGE :[4] 'NONE' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[9] 'KIBCSQL01' STATUS:[4] '1017' DBID:[0] '' .
2014.09.26 2:16:32 Error starting SMCash session for database DBNAME. See message that follows this one for more info.
                           General failure. Error messages follows. 
                           Запись 1. Код=80004005h (108) [Кассовый модуль Супермага]:
                           Ошибка при установке соединения с базой данных.
                           Запись 2. Код=80004005h (0) [Супермаг+]:
                           Невозможно подключиться к базе данных «DBNAME»
                           Запись 3. Код=800a0e7dh (0) [Супермаг+]:
                           Нет строки сообщения для ошибки с кодом 800A0E7Dh.
                           Запись 4. Код=80004005h (1033) [Microsoft OLE DB Provider for Oracle]:
                           ORA-01033: ORACLE initialization or shutdown in progress
2014.09.26 9:05:39 Audit trail: LENGTH: '155' ACTION :[7] 'CONNECT' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[9] 'KIBCSQL01' STATUS:[1] '0' DBID:[0] '' .
2014.09.26 9:05:45 General failure. Error messages follows. 
                           Запись 1. Код=80004005h (108) [Кассовый модуль Супермага]:
                           Ошибка при установке соединения с базой данных.
                           Запись 2. Код=80004005h (0) [Супермаг+]:
                           Невозможно подключиться к базе данных «DBNAME»
                           Запись 3. Код=800a0e7dh (0) [Супермаг+]:
                           Нет строки сообщения для ошибки с кодом 800A0E7Dh.
                           Запись 4. Код=80004005h (12518) [Microsoft OLE DB Provider for Oracle]:
                           ORA-12518: TNS:listener could not hand off client connection
                           Запись 5. Код=80004005h (108) [Кассовый модуль Супермага]:
                           Ошибка при установке соединения с базой данных.
                           Запись 6. Код=80004005h (0) [Супермаг+]:
                           Невозможно подключиться к базе данных «DBNAME»
                           Запись 7. Код=800a0e7dh (0) [Супермаг+]:
                           Нет строки сообщения для ошибки с кодом 800A0E7Dh.
                           Запись 8. Код=80004005h (1033) [Microsoft OLE DB Provider for Oracle]:
                           ORA-01033: ORACLE initialization or shutdown in progress
                           Запись 1. Код=80004005h (108) [Кассовый модуль Супермага]:
                           Ошибка при установке соединения с базой данных.
                           Запись 2. Код=80004005h (0) [Супермаг+]:
                           Невозможно подключиться к базе данных «DBNAME»
                           Запись 3. Код=800a0e7dh (0) [Супермаг+]:
                           Нет строки сообщения для ошибки с кодом 800A0E7Dh.
                           Запись 4. Код=80004005h (12518) [Microsoft OLE DB Provider for Oracle]:
                           ORA-12518: TNS:listener could not hand off client connection
                           Запись 5. Код=80004005h (108) [Кассовый модуль Супермага]:
                           Ошибка при установке соединения с базой данных.
                           Запись 6. Код=80004005h (0) [Супермаг+]:
                           Невозможно подключиться к базе данных «DBNAME»
                           Запись 7. Код=800a0e7dh (0) [Супермаг+]:
                           Нет строки сообщения для ошибки с кодом 800A0E7Dh.
                           Запись 8. Код=80004005h (1033) [Microsoft OLE DB Provider for Oracle]:
                           ORA-01033: ORACLE initialization or shutdown in progress
2014.09.26 9:05:54 Audit trail: LENGTH: '155' ACTION :[7] 'CONNECT' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[9] 'KIBCSQL01' STATUS:[1] '0' DBID:[0] '' .
2014.09.26 9:05:54 Initializing SGA for instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process PMON in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process PSP0 in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process VKTM in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process GEN0 in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process DIAG in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process DBRM in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process DIA0 in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process MMAN in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process DBW0 in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process LGWR in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process CKPT in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process SMON in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process RECO in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process MMON in instance DBNAME.
2014.09.26 9:05:59 Initializing PGA for process MMNL in instance DBNAME.
2014.09.26 9:06:00 Audit trail: LENGTH: '158' ACTION :[7] 'STARTUP' DATABASE USER:[1] '/' PRIVILEGE :[4] 'NONE' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[13] 'Not Available' STATUS:[1] '0' DBID:[0] '' .
2014.09.26 9:06:00 Audit trail: LENGTH: '155' ACTION :[7] 'CONNECT' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[9] 'KIBCSQL01' STATUS:[1] '0' DBID:[0] '' .
2014.09.26 9:06:05 Initializing PGA for process ARC0 in instance DBNAME.
2014.09.26 9:06:05 Initializing PGA for process ARC1 in instance DBNAME.
2014.09.26 9:06:05 Initializing PGA for process ARC2 in instance DBNAME.
2014.09.26 9:06:05 Initializing PGA for process ARC3 in instance DBNAME.
2014.09.26 9:06:07 Initializing PGA for process QMNC in instance DBNAME.
2014.09.26 9:06:09 Initializing PGA for process CJQ0 in instance DBNAME.
2014.09.26 9:06:36 Activated database DBNAME.
2014.09.26 9:11:13 Initializing PGA for process SMCO in instance DBNAME.
2014.09.26 9:15:00 Audit trail: LENGTH: '166' ACTION :[7] 'CONNECT' DATABASE USER:[3] 'SYS' PRIVILEGE :[4] 'NONE' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[9] 'KISPMAG01' STATUS:[1] '0' DBID:[10] '1262647574' .
2014.09.26 9:23:00 Audit trail: LENGTH: '166' ACTION :[7] 'CONNECT' DATABASE USER:[3] 'SYS' PRIVILEGE :[4] 'NONE' CLIENT USER:[6] 'SYSTEM' CLIENT TERMINAL:[9] 'KISPMAG01' STATUS:[1] '0' DBID:[10] '1262647574' .

alicedr · █ 26.09.2014 13:00

Oracle Alert.log

Код:

Fri Sep 26 02:07:19 2014
Shutting down instance (immediate)
Stopping background process SMCO
Shutting down instance: further logons disabled
Stopping background process QMNC
Fri Sep 26 02:07:21 2014
Stopping background process CJQ0
Stopping background process MMNL
Stopping background process MMON
License high water mark = 86
All dispatchers and shared servers shutdown

Fri Sep 26 02:07:32 2014
alter database close normal
Fri Sep 26 02:07:32 2014
SMON: disabling tx recovery
SMON: disabling cache recovery
Fri Sep 26 02:07:34 2014
Shutting down archive processes
Archiving is disabled
Fri Sep 26 02:07:34 2014
ARCH shutting down
ARC2: Archival stopped
Fri Sep 26 02:07:34 2014
ARCH shutting down
ARC0: Archival stopped
Fri Sep 26 02:07:34 2014
ARCH shutting down
ARC3: Archival stopped
Fri Sep 26 02:07:34 2014
ARCH shutting down
ARC1: Archival stopped
Thread 1 closed at log sequence 576
Successful close of redo thread 1
Completed: 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
Fri Sep 26 02:07:39 2014
Stopping background process VKTM
Fri Sep 26 02:07:42 2014
Instance shutdown complete
Fri Sep 26 02:15:57 2014
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 =51
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Windows NT Version V6.1 Service Pack 1 
CPU                 : 4 - type 8664, 4 Physical Cores
Process Affinity    : 0x0x0000000000000000
Memory (Avail/Total): Ph:12989M/16338M, Ph+PgF:24350M/32675M 
Using parameter settings in server-side spfile C:\SM2000\ORASRV11203\DATABASE\SPFILEDBNAME.ORA
System parameters with non-default values:
  processes                = 300
  nls_language             = "AMERICAN"
  nls_territory            = "AMERICA"
  sga_target               = 4912M
  control_files            = "D:\DATA\SUPERMAG\DBNAME\DBNAME\CONTROL01.CTL"
  control_files            = "D:\DATA\SUPERMAG\DBNAME\DBNAME\CONTROL02.CTL"
  db_block_size            = 8192
  compatible               = "11.2.0.0.0"
  db_recovery_file_dest    = "d:\ora_archivelog\"
  db_recovery_file_dest_size= 45G
  undo_tablespace          = "UNDOTBS1"
  O7_DICTIONARY_ACCESSIBILITY= TRUE
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=DBNAMEXDB)"
  audit_file_dest          = "D:\DATA\SUPERMAG\DBNAME\ADMIN\DBNAME\ADUMP"
  audit_trail              = "DB"
  audit_trail              = "EXTENDED"
  db_name                  = "DBNAME"
  open_cursors             = 300
  pga_aggregate_target     = 1633M
  diagnostic_dest          = "D:\DATA\SUPERMAG\DBNAME"
Fri Sep 26 02:16:06 2014
PMON started with pid=2, OS id=6132 
Fri Sep 26 02:16:06 2014
PSP0 started with pid=3, OS id=6852 
Fri Sep 26 02:16:07 2014
VKTM started with pid=5, OS id=5824 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Fri Sep 26 02:16:07 2014
GEN0 started with pid=6, OS id=1832 
Fri Sep 26 02:16:07 2014
DIAG started with pid=7, OS id=1004 
Fri Sep 26 02:16:07 2014
DBRM started with pid=8, OS id=4256 
Fri Sep 26 02:16:07 2014
DIA0 started with pid=9, OS id=5400 
Fri Sep 26 02:16:07 2014
MMAN started with pid=4, OS id=972 
Fri Sep 26 02:16:07 2014
DBW0 started with pid=11, OS id=4440 
Fri Sep 26 02:16:07 2014
LGWR started with pid=10, OS id=1140 
Fri Sep 26 02:16:07 2014
CKPT started with pid=13, OS id=5836 
Fri Sep 26 02:16:07 2014
SMON started with pid=14, OS id=6012 
Fri Sep 26 02:16:07 2014
RECO started with pid=15, OS id=1836 
Fri Sep 26 02:16:07 2014
MMON started with pid=12, OS id=3032 
Fri Sep 26 02:16:07 2014
MMNL started with pid=16, OS id=1888 
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Fri Sep 26 02:16:08 2014
starting up 1 shared server(s) ...
ORACLE_BASE from environment = d:\DATA\supermag\DBNAME

Fri Sep 26 09:05:39 2014
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-1507 signalled during: alter database close normal...

Fri Sep 26 09:05:54 2014
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 =51
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Windows NT Version V6.1 Service Pack 1 
CPU                 : 4 - type 8664, 4 Physical Cores
Process Affinity    : 0x0x0000000000000000
Memory (Avail/Total): Ph:12987M/16338M, Ph+PgF:24438M/32675M 
Using parameter settings in server-side spfile C:\SM2000\ORASRV11203\DATABASE\SPFILEDBNAME.ORA
System parameters with non-default values:
  processes                = 300
  nls_language             = "AMERICAN"
  nls_territory            = "AMERICA"
  sga_target               = 4912M
  control_files            = "D:\DATA\SUPERMAG\DBNAME\DBNAME\CONTROL01.CTL"
  control_files            = "D:\DATA\SUPERMAG\DBNAME\DBNAME\CONTROL02.CTL"
  db_block_size            = 8192
  compatible               = "11.2.0.0.0"
  db_recovery_file_dest    = "d:\ora_archivelog\"
  db_recovery_file_dest_size= 45G
  undo_tablespace          = "UNDOTBS1"
  O7_DICTIONARY_ACCESSIBILITY= TRUE
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=DBNAMEXDB)"
  audit_file_dest          = "D:\DATA\SUPERMAG\DBNAME\ADMIN\DBNAME\ADUMP"
  audit_trail              = "DB"
  audit_trail              = "EXTENDED"
  db_name                  = "DBNAME"
  open_cursors             = 300
  pga_aggregate_target     = 1633M
  diagnostic_dest          = "D:\DATA\SUPERMAG\DBNAME"
Fri Sep 26 09:05:59 2014
PMON started with pid=2, OS id=21248 
Fri Sep 26 09:05:59 2014
PSP0 started with pid=3, OS id=20488 
Fri Sep 26 09:05:59 2014
VKTM started with pid=4, OS id=18724 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Fri Sep 26 09:05:59 2014
GEN0 started with pid=5, OS id=20772 
Fri Sep 26 09:05:59 2014
DIAG started with pid=6, OS id=1620 
Fri Sep 26 09:05:59 2014
DBRM started with pid=7, OS id=21036 
Fri Sep 26 09:05:59 2014
DIA0 started with pid=8, OS id=19788 
Fri Sep 26 09:05:59 2014
MMAN started with pid=9, OS id=20548 
Fri Sep 26 09:05:59 2014
DBW0 started with pid=10, OS id=20000 
Fri Sep 26 09:05:59 2014
LGWR started with pid=11, OS id=20456 
Fri Sep 26 09:05:59 2014
CKPT started with pid=12, OS id=20948 
Fri Sep 26 09:05:59 2014
SMON started with pid=13, OS id=20628 
Fri Sep 26 09:05:59 2014
RECO started with pid=14, OS id=18748 
Fri Sep 26 09:05:59 2014
MMON started with pid=15, OS id=20020 
Fri Sep 26 09:05:59 2014
MMNL started with pid=16, OS id=21240 
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = d:\DATA\supermag\DBNAME
Fri Sep 26 09:06:00 2014
alter database mount exclusive
Successful mount of redo thread 1, with mount id 1266036600
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
LGWR: STARTING ARCH PROCESSES
Fri Sep 26 09:06:05 2014
ARC0 started with pid=20, OS id=20760 
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Fri Sep 26 09:06:05 2014
ARC1 started with pid=21, OS id=20752 
Fri Sep 26 09:06:05 2014
ARC2 started with pid=22, OS id=5532 
Fri Sep 26 09:06:05 2014
ARC3 started with pid=23, OS id=21416 
ARC1: Archival started
ARC2: Archival started
Thread 1 opened at log sequence 576
  Current log# 3 seq# 576 mem# 0: D:\DATA\SUPERMAG\DBNAME\DBNAME\REDO03.LOG
Successful open of redo thread 1
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
ARC2: Becoming the heartbeat ARCH
SMON: enabling cache recovery
[20720] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:1461777088 end:1461777291 diff:203 (2 seconds)
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is CL8MSWIN1251
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Fri Sep 26 09:06:07 2014
QMNC started with pid=24, OS id=6132 
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Completed: alter database open
Starting background process CJQ0
Fri Sep 26 09:06:09 2014
CJQ0 started with pid=25, OS id=5836 
Fri Sep 26 09:06:09 2014
db_recovery_file_dest_size of 46080 MB is 3.90% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Fri Sep 26 09:11:13 2014
Starting background process SMCO
Fri Sep 26 09:11:13 2014
SMCO started with pid=61, OS id=21432 
Fri Sep 26 10:54:24 2014
Thread 1 advanced to log sequence 577 (LGWR switch)
  Current log# 1 seq# 577 mem# 0: D:\DATA\SUPERMAG\DBNAME\DBNAME\REDO01.LOG

alicedr · █ 26.09.2014 13:08

Это вариант залипания.
Другой вариант-БД вообще не шевелится. Системный лог пишет, что служба БД запущена (успешно), а в алерт-логе за этот период вообще пусто.

alicedr · █ 26.09.2014 13:17

вот еще нашлось, совсем уже непонятны причины выборочного несрабатывания пароля к БД, в oradim.log:

Код:

Fri Sep 26 02:07:17 2014
c:\SM2000\oraSRV11203\bin\oradim.exe -shutdown -sid DBNAME -usrpwd * -shutmode immediate -log oradim.log 

Fri Sep 26 02:15:57 2014
c:\SM2000\oraSRV11203\bin\oradim.exe -startup -sid DBNAME -usrpwd *  -log oradim.log -nocheck 0 
Fri Sep 26 02:16:08 2014
ORA-01017: invalid username/password; logon denied


Fri Sep 26 09:05:38 2014
c:\SM2000\oraSRV11203\bin\oradim.exe -shutdown -sid DBNAME -usrpwd * -shutmode immediate -log oradim.log 
Fri Sep 26 09:05:42 2014
ORA-01507: database not mounted


Fri Sep 26 09:05:54 2014
c:\SM2000\oraSRV11203\bin\oradim.exe -startup -sid DBNAME -usrpwd *  -log oradim.log -nocheck 0

bayan · █ 26.09.2014 15:30

1. Я бы не рекомендовал "холодный" бэкап с остановкой сервиса использовать вообще
2. Вы бы вместо логов лучше скрипт приложили, которым бэкап делаете

alicedr · █ 26.09.2014 17:37

1. Восстановление с холодного бекапа гораздо быстрее и не требует особых знаний. И занимает всего 10-20 минут в то время, когда бд все равно не используется.
2. Зачем? Есть факт запуска сервиса. Сервис запустился, о чем есть системная запись. Почему не поднялась база? Почему ей не подошел пароль, который 380 раз до этого подходил? И почему при следующем запуске пароль опять подошел?
Если уж совсем невмоготу-бекап делаю с помощью программы Cobian Backup, которая умеет останавливать и запускать сервисы, а также копировать папочки с папки 1 в папку 2 в указанное время.

OlegON · █ 26.09.2014 19:13

1. Когда обнаружите, что БД уже совсем не БД - поймете, сбойные блоки не приводят к моментальной смерти БД, но целостности данных не добавляют. Почитайте тему "Увеличение доступности БД" тут же, на форуме. Восстановление с горячей копии быстрее и меньше телодвижений. А Cobian пусть сам бекап таскает.
2. Затем, что вариантов повалить БД для копирования мильон. Перед остановкой сервиса делайте в sqlplus команду shutdown immediate, в Windows сервис не бесконечно останавливается, а вот ждать завершения shutdown immediate можно достаточно долго.

alicedr · █ 29.09.2014 11:58

Обе темы замечательны для дальнейших горячих дискуссий, однако мы ушли в сторону от главного вопроса: При старте база рандомно 1-2 раза в неделю ругается на файл паролей и не стартует.
А решение не останавливать базу чтобы не было ошибки при старте решением собственно не является.

Еще раз повторюсь: процедуры останова и старта, а также файл паролей остаются неизменными во всех случаях: и когда бд залипает, и когда стартует нормально.

OlegON · █ 29.09.2014 12:29

И я повторюсь.

Цитата:

OlegON ➤ Перед остановкой сервиса делайте в sqlplus команду shutdown immediate, в Windows сервис не бесконечно останавливается, а вот ждать завершения shutdown immediate можно достаточно долго.

Предлагаю и стартовать так же вручную плюсом. Кстати, какой-нибудь гадости, вроде домена, нет?