Текущее время: Пт, июл 18 2025, 23:37

Часовой пояс: UTC + 3 часа


Правила форума


ВНИМАНИЕ! Прежде чем задавать вопрос, ознакомьтесь со ссылками ниже:

Вопросы по отличиям версий SAP, Add-On, EHP - сюда
Вопросы по SAP Front End (SAPlogon, SAPgui, guiXT и т.д.) - сюда
Вопросы по LSMW - сюда
Вопросы по архивации в SAP - сюда
Вопросы по SAP GRC - сюда
Вопросы по SAP Business Workplace (почте SAP) и SAP Office - сюда
Вопросы по miniSAP (SAP mini basis) - сюда
Вопросы по SAP HANA - сюда
Вопросы по лицензированию продуктов SAP - сюда



Начать новую тему Ответить на тему  [ Сообщений: 15 ] 
Автор Сообщение
 Заголовок сообщения: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Чт, янв 20 2011, 20:21 
Ассистент
Ассистент

Зарегистрирован:
Вт, окт 26 2010, 15:00
Сообщения: 32
Пол: Мужской
Solaris 10 Oracle 10-2-0-2 SAR ERP 2005 SR2 ABAP+JAVA Central Instance
Имется копия системы созданная Whole dfatabase offline backup (выполняется ежедневно) и 1 redolog после ее.
Восстановление системы после отказа винчестера с oracle. Информация по сап инстанции все сохранилась.
На текущий момент на новом оборудовании установил заново ERP6.0 SR3 ABAP+JAVA Central Instance Solaris 10 Oracle 10-2-0-4. Из backup в /oracle/SID/102_64/dbs скопировал spfileSID.ora initSID.ora initSID.sap
Удалил все из /oracle/SID из каталогов origlog sapdata mirrlog
Запустил под orasid BRTOOLS восстановил все из Whole после восстановления контрольных файлов и данных на следующем шаге дает ошибку запуска оракловой инстанции.
lsnrctl start успешен. R3trans -d базу не видит.
При попытке запуска по startsap монтируется база и вылетает по 12 ошибке.
Спасибо за помощь.

_________________
Человек рождается уставшим и живет чтобы отдохнуть


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Чт, янв 20 2011, 22:05 
Почетный гуру
Почетный гуру
Аватара пользователя

Зарегистрирован:
Чт, сен 28 2006, 11:36
Сообщения: 1365
Откуда: Москва
Пол: Мужской
чо за ошибка то?

номер 12 мало информативен

sqlplus "/as sysdba"
startup;

что тут пишет?


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 09:14 
Менеджер
Менеджер

Зарегистрирован:
Вт, июл 24 2007, 14:52
Сообщения: 603
Откуда: Казахстан
Пол: Мужской
serg1973 написал:
R3trans -d базу не видит.

покажите trans.log
лежит в той же директории где запускали R3trans -d


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 09:29 
Ассистент
Ассистент

Зарегистрирован:
Вт, окт 26 2010, 15:00
Сообщения: 32
Пол: Мужской
$ sqlplus "/as sysdba"
startup

SQL*Plus: Release 10.2.0.4.0 - Production on Fri Jan 21 07:58:16 2011
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area 2365587456 bytes
Fixed Size 2085744 bytes
Variable Size 1191185552 bytes
Database Buffers 1157627904 bytes
Redo Buffers 14688256 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced

далее файл trans.log
4 ETW000 ./R3trans version 6.14 (release 700 - 23.07.10 - 09:23:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 21.01.2011 - 08:07:54
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: ./R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc ,00000] Fri Jan 21 08:07:54 2011 178 0.000178
4 ETW000 [dev trc ,00000] db_con_init called 21 0.000199
4 ETW000 [dev trc ,00000] create_con (con_name=R/3) 91 0.000290
4 ETW000 [dev trc ,00000] Loading DB library '/usr/sap/QAS/SYS/exe/run/dboraslib.so' ... 82 0.000372
4 ETW000 [dev trc ,00000] DlLoadLib() success: dlopen("/usr/sap/QAS/SYS/exe/run/dboraslib.so"), hdl 0
4 ETW000 17474 0.017846
4 ETW000 [dev trc ,00000] Library '/usr/sap/QAS/SYS/exe/run/dboraslib.so' loaded 65 0.017911
4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library /usr/sap/QAS/SYS/exe/run/dboraslib.so
4 ETW000 33 0.017944
4 ETW000 [dev trc ,00000] Version of '/usr/sap/QAS/SYS/exe/run/dboraslib.so' is "700.08", patchlevel (0.271)
4 ETW000 413 0.018357
4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library /usr/sap/QAS/SYS/exe/run/dboraslib.so
4 ETW000 30 0.018387
4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library /usr/sap/QAS/SYS/exe/run/dboraslib.so
4 ETW000 69 0.018456
4 ETW000 [dev trc ,00000] New connection 0 created 35 0.018491
4 ETW000 [dev trc ,00000] 000: name = R/3, con_id = -000000001, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,
4 ETW000 reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 44 0.018535
4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3) 27 0.018562
4 ETW000 [dev trc ,00000] find_con_by_name found the following connection for reuse: 18 0.018580
4 ETW000 [dev trc ,00000] 000: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,
4 ETW000 reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 41 0.018621
4 ETW000 [dev trc ,00000] -->oci_init1 456 0.019077
4 ETW000 [dev trc ,00000] Oracle Client Version: '10.2.0.4.0', (dbsl 700 140910) 130 0.019207
4 ETW000 [dev trc ,00000] Default connection: tnsname ='QAS' 29 0.019236
4 ETW000 [dev trc ,00000] -->oci_initialize(con_hdl=0, char='', nchar='') 20 0.019256
4 ETW000 [dev trc ,00000] application info callback registered 48 0.019304
4 ETW000 [dev trc ,00000] (-) OCIEnvCreate(mode=16384=OCI_UTF16) returned 0 (for default NLS handle)
4 ETW000 17214 0.036518
4 ETW000 [dev trc ,00000] OCIHandleAlloc(OCI_HTYPE_ERROR, con_hdl=0, ErrHp=0x1c5b320) 45 0.036563
4 ETW000 [dev trc ,00000] OCIHandleAlloc(OCI_HTYPE_ERROR, con_hdl=0, ErrBt=0x1c6be78) 50 0.036613
4 ETW000 [dev trc ,00000] NLS env. settings: lang=41004D00450052004900430041004E0000000000000000000000000000000000
4 ETW000 177 0.036790
4 ETW000 [dev trc ,00000] terr=41004D0045005200490043004100000000000000000000000000000000000000
4 ETW000 35 0.036825
4 ETW000 [dev trc ,00000] char=5500540046003100360000000000000000000000000000000000000000000000
4 ETW000 34 0.036859
4 ETW000 [dev trc ,00000] Client character set UTF16 -> UTF8 18 0.036877
4 ETW000 [dev trc ,00000] Client NLS setting (OCINlsGetInfo): connection handle 0 -> 'AMERICAN_AMERICA.UTF8'
4 ETW000 36 0.036913
4 ETW000 [dev trc ,00000] charset='', chset='UTF8', UNI_ASC=FALSE/FALSE 19 0.036932
4 ETW000 [dev trc ,00000] Logon as OPS$-user to get SAPSR3's password 129 0.037061
4 ETW000 [dev trc ,00000] Connecting as /@QAS on connection 0 (nls_hdl 0) ... (dbsl 700 140910)
4 ETW000 47 0.037108
4 ETW000 [dev trc ,00000] Nls CharacterSet NationalCharSet EnvHp ErrHp ErrHpBatch
4 ETW000 45 0.037153
4 ETW000 [dev trc ,00000] 0 UTF8 0x1c53880 0x1c5b320 0x1c6be78
4 ETW000 35 0.037188
4 ETW000 [dev trc ,00000] Allocating service context handle for con_hdl=0 48 0.037236
4 ETW000 [dev trc ,00000] Allocating server context handle 32 0.037268
4 ETW000 [dev trc ,00000] Attaching to DB Server QAS (con_hdl=0,svchp=0x1c6bda8,srvhp=0x1c6fb68)
4 ETW000 93 0.037361
4 ETW000 [dev trc ,00000] Assigning server context 0x1c6fb68 to service context 0x1c6bda8 34469 0.071830
4 ETW000 [dev trc ,00000] Allocating user session handle 78 0.071908
4 ETW000 [dev trc ,00000] Starting user session: OCISessionBegin(con_hdl=0, usr='/',svchp=0x1c6bda8, srvhp=0x1c6fb68, usrhp=0x1ccdbc0)
4 ETW000 70 0.071978
4 ETW000 [dev trc ,00000] OCISessionBegin(OCI_DEFAULT) failed with -1=OCI_ERROR 4771 0.076749
4 ETW000 [dev trc ,00000] OCISessionBegin(OCI_DEFAULT) failed with SQL error 1034: 114 0.076863
4 ETW000 [dev trc ,00000] ORA-01034: ORACLE not available 27 0.076890
4 ETW000 ORA-27101: shared memory realm does not exist
4 ETW000 Solaris-AMD64 Error: 2: No such file or dire
4 ETW000 [dev trc ,00000] ctory
4 ETW000 46 0.076936
4 ETW000 [dev trc ,00000] server_detach(con_hdl=0,stale=1,svrhp=0x1c6fb68) 20 0.076956
4 ETW000 [dev trc ,00000] Detaching from DB Server (con_hdl=0,svchp=0x1c6bda8,srvhp=0x1c6fb68)
4 ETW000 55 0.077011
4 ETW000 [dev trc ,00000] Deallocating server context handle 0x1c6fb68 from con_hdl=0 175 0.077186
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1034' 54 0.077240
4 ETW000 [dev trc ,00000] set_ocica() -> SQL error code 1034 33 0.077273
4 ETW000 [dev trc ,00000] -->oci_get_errmsg (con_hdl=0, rc=1034) 30 0.077303
4 ETW000 [dev trc ,00000] OCIErrorGet -> SQL error code: 1034 57 0.077360
4 ETW000 [dev trc ,00000] ORA-01034: ORACLE not available 23 0.077383
4 ETW000 ORA-27101: shared memory realm does not exist
4 ETW000 Solaris-AMD64 Error: 2: No such file or dire
4 ETW000 [dev trc ,00000] ctory
4 ETW000 58 0.077441
4 ETW000 [dev trc ,00000] SAPUSER or connect error 99=DBSL_ERR_DB, oerr=1034. 46 0.077487
4 ETW000 [dblink ,00433] ***LOG BY2=>sql error 1034 performing CON [dblink#8 @ 433] 77 0.077564
4 ETW000 [dblink ,00433] ***LOG BY0=>ORA-01034: ORACLE not available 26 0.077590
4 ETW000 ORA-27101: shared memory realm does not exist
4 ETW000 Solaris-AMD64 Error: 2: No such file or directory [dblink#8 @ 433]
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'QAS'"

_________________
Человек рождается уставшим и живет чтобы отдохнуть


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 09:32 
Начинающий
Начинающий

Зарегистрирован:
Ср, янв 12 2011, 06:57
Сообщения: 1
Цитата:
Запустил под orasid BRTOOLS восстановил все из Whole после восстановления контрольных файлов и данных на следующем шаге дает ошибку запуска оракловой инстанции.


Проверьте версии контрольных файлов, в большинстве случаев версии не совпадают и необходимо вручную разнести их в 3 места, которые указаны initSID файле, т.к. обычно бэкап копирует только один из них, следовательно и восстанавливает тоже один.


Пометить тему как нерешенную
Вернуться к началу
 Профиль Отправить email  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 09:52 
Почетный гуру
Почетный гуру
Аватара пользователя

Зарегистрирован:
Чт, сен 16 2004, 17:10
Сообщения: 2229
Откуда: Moscow, кажется...
Пол: Мужской
Переменные окружения для юзера, параметры ядра?
Посмотреть alert.log, может там что интересное на старте.

_________________
Я бы хотел поглядеть на эффективную армию, состоящую из эффективных менеджеров.
BRGDS,
Aleks Изображение


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 10:06 
Ассистент
Ассистент

Зарегистрирован:
Вт, окт 26 2010, 15:00
Сообщения: 32
Пол: Мужской
версии контрольных файлов соответственные. при sapstart проходят проверку если не соответствуют то дает ошибку. (Уже с этим столкнулся)
файл alert
Thu Jan 20 16:08:22 2011
Starting ORACLE instance (normal)
Thu Jan 20 16:08:24 2011
Specified value of sga_max_size is too small, bumping to 2365587456
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 2365587456
shared_pool_size = 1157627904
shared_pool_reserved_size= 114152177
filesystemio_options = setall
control_files = /oracle/QAS/origlogA/cntrl/cntlrQAS.dbf, /oracle/QAS/origlogB/cntrl/cntrlQAS.dbf, /oracle/QAS/sapdata1/cntrl/cntrlQAS.dbf
control_file_record_keep_time= 30
db_block_size = 8192
db_cache_size = 1157627904
compatible = 10.2.0
log_archive_dest = /oracle/QAS/oraarch/QASarch
log_buffer = 14242816
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes = 1
background_dump_dest = /oracle/QAS/saptrace/background
user_dump_dest = /oracle/QAS/saptrace/usertrace
core_dump_dest = /oracle/QAS/saptrace/background
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = QAS
open_cursors = 800
_optim_peek_user_binds = FALSE
pga_aggregate_target = 1522029035
workarea_size_policy = AUTO
statistics_level = typical
PMON started with pid=2, OS id=1860
PSP0 started with pid=3, OS id=1862
MMAN started with pid=4, OS id=1864
DBW0 started with pid=5, OS id=1866
LGWR started with pid=6, OS id=1868
CKPT started with pid=7, OS id=1870
SMON started with pid=8, OS id=1872
RECO started with pid=9, OS id=1874
CJQ0 started with pid=10, OS id=1876
MMON started with pid=11, OS id=1878
MMNL started with pid=12, OS id=1880
Thu Jan 20 16:08:42 2011
ALTER DATABASE MOUNT
Thu Jan 20 16:08:47 2011
Setting recovery target incarnation to 1
Thu Jan 20 16:08:47 2011
Successful mount of redo thread 1, with mount id 2130371146
Thu Jan 20 16:08:47 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Shutting down instance: further logons disabled
Thu Jan 20 16:09:20 2011
Stopping background process CJQ0
Thu Jan 20 16:09:20 2011
Stopping background process MMNL
Thu Jan 20 16:09:21 2011
Stopping background process MMON
Thu Jan 20 16:09:22 2011
Shutting down instance (immediate)
License high water mark = 1
Thu Jan 20 16:09:22 2011
Stopping Job queue slave processes, flags = 7
Thu Jan 20 16:09:22 2011
Job queue slave processes stopped
Thu Jan 20 16:09:22 2011
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Thu Jan 20 16:09:22 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thu Jan 20 16:09:25 2011
Starting ORACLE instance (normal)
Thu Jan 20 16:09:25 2011
Specified value of sga_max_size is too small, bumping to 2365587456
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 2365587456
shared_pool_size = 1157627904
shared_pool_reserved_size= 114152177
filesystemio_options = setall
control_files = /oracle/QAS/origlogA/cntrl/cntlrQAS.dbf, /oracle/QAS/origlogB/cntrl/cntrlQAS.dbf, /oracle/QAS/sapdata1/cntrl/cntrlQAS.dbf
control_file_record_keep_time= 30
db_block_size = 8192
db_cache_size = 1157627904
compatible = 10.2.0
log_archive_dest = /oracle/QAS/oraarch/QASarch
log_buffer = 14242816
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes = 1
background_dump_dest = /oracle/QAS/saptrace/background
user_dump_dest = /oracle/QAS/saptrace/usertrace
core_dump_dest = /oracle/QAS/saptrace/background
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = QAS
open_cursors = 800
_optim_peek_user_binds = FALSE
pga_aggregate_target = 1522029035
workarea_size_policy = AUTO
statistics_level = typical
PMON started with pid=2, OS id=1927
PSP0 started with pid=3, OS id=1929
MMAN started with pid=4, OS id=1931
DBW0 started with pid=5, OS id=1933
LGWR started with pid=6, OS id=1935
CKPT started with pid=7, OS id=1937
SMON started with pid=8, OS id=1939
RECO started with pid=9, OS id=1941
CJQ0 started with pid=10, OS id=1943
MMON started with pid=11, OS id=1945
MMNL started with pid=12, OS id=1947
Thu Jan 20 16:09:26 2011
ALTER DATABASE MOUNT
Thu Jan 20 16:09:31 2011
Setting recovery target incarnation to 1
Thu Jan 20 16:09:31 2011
Successful mount of redo thread 1, with mount id 2130377078
Thu Jan 20 16:09:31 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Jan 20 16:09:31 2011
ALTER DATABASE OPEN
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '/oracle/QAS/sapdata1/system_1/system.data1'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: '/oracle/QAS/sapdata3/undo_1/undo.data1'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: '/oracle/QAS/sapdata1/sysaux_1/sysaux.data1'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: '/oracle/QAS/sapdata1/sr3_1/sr3.data1'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: '/oracle/QAS/sapdata1/sr3_2/sr3.data2'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: '/oracle/QAS/sapdata1/sr3_3/sr3.data3'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
ORA-01110: data file 7: '/oracle/QAS/sapdata1/sr3_4/sr3.data4'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
ORA-01110: data file 8: '/oracle/QAS/sapdata1/sr3_5/sr3.data5'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: '/oracle/QAS/sapdata2/sr3_6/sr3.data6'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
ORA-01110: data file 10: '/oracle/QAS/sapdata2/sr3_7/sr3.data7'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 11 - see DBWR trace file
ORA-01110: data file 11: '/oracle/QAS/sapdata2/sr3_8/sr3.data8'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 12 - see DBWR trace file
ORA-01110: data file 12: '/oracle/QAS/sapdata2/sr3_9/sr3.data9'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '/oracle/QAS/sapdata2/sr3_10/sr3.data10'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 14 - see DBWR trace file
ORA-01110: data file 14: '/oracle/QAS/sapdata3/sr3_11/sr3.data11'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 15 - see DBWR trace file
ORA-01110: data file 15: '/oracle/QAS/sapdata3/sr3_12/sr3.data12'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 16 - see DBWR trace file
ORA-01110: data file 16: '/oracle/QAS/sapdata3/sr3_13/sr3.data13'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 17 - see DBWR trace file
ORA-01110: data file 17: '/oracle/QAS/sapdata3/sr3_14/sr3.data14'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 18 - see DBWR trace file
ORA-01110: data file 18: '/oracle/QAS/sapdata3/sr3_15/sr3.data15'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 19 - see DBWR trace file
ORA-01110: data file 19: '/oracle/QAS/sapdata4/sr3_16/sr3.data16'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 20 - see DBWR trace file
ORA-01110: data file 20: '/oracle/QAS/sapdata4/sr3_17/sr3.data17'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 21 - see DBWR trace file
ORA-01110: data file 21: '/oracle/QAS/sapdata4/sr3_18/sr3.data18'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 22 - see DBWR trace file
ORA-01110: data file 22: '/oracle/QAS/sapdata4/sr3_19/sr3.data19'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 23 - see DBWR trace file
ORA-01110: data file 23: '/oracle/QAS/sapdata4/sr3_20/sr3.data20'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 24 - see DBWR trace file
ORA-01110: data file 24: '/oracle/QAS/sapdata1/sr3700_1/sr3700.data1'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 25 - see DBWR trace file
ORA-01110: data file 25: '/oracle/QAS/sapdata1/sr3700_2/sr3700.data2'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 26 - see DBWR trace file
ORA-01110: data file 26: '/oracle/QAS/sapdata1/sr3700_3/sr3700.data3'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 27 - see DBWR trace file
ORA-01110: data file 27: '/oracle/QAS/sapdata1/sr3700_4/sr3700.data4'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 28 - see DBWR trace file
ORA-01110: data file 28: '/oracle/QAS/sapdata2/sr3700_5/sr3700.data5'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 29 - see DBWR trace file
ORA-01110: data file 29: '/oracle/QAS/sapdata2/sr3700_6/sr3700.data6'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 30 - see DBWR trace file
ORA-01110: data file 30: '/oracle/QAS/sapdata2/sr3700_7/sr3700.data7'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 31 - see DBWR trace file
ORA-01110: data file 31: '/oracle/QAS/sapdata2/sr3700_8/sr3700.data8'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 32 - see DBWR trace file
ORA-01110: data file 32: '/oracle/QAS/sapdata3/sr3700_9/sr3700.data9'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 33 - see DBWR trace file
ORA-01110: data file 33: '/oracle/QAS/sapdata3/sr3700_10/sr3700.data10'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 34 - see DBWR trace file
ORA-01110: data file 34: '/oracle/QAS/sapdata3/sr3700_11/sr3700.data11'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 35 - see DBWR trace file
ORA-01110: data file 35: '/oracle/QAS/sapdata3/sr3700_12/sr3700.data12'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 36 - see DBWR trace file
ORA-01110: data file 36: '/oracle/QAS/sapdata4/sr3700_13/sr3700.data13'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 37 - see DBWR trace file
ORA-01110: data file 37: '/oracle/QAS/sapdata4/sr3700_14/sr3700.data14'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 38 - see DBWR trace file
ORA-01110: data file 38: '/oracle/QAS/sapdata4/sr3700_15/sr3700.data15'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 39 - see DBWR trace file
ORA-01110: data file 39: '/oracle/QAS/sapdata4/sr3700_16/sr3700.data16'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 40 - see DBWR trace file
ORA-01110: data file 40: '/oracle/QAS/sapdata1/sr3usr_1/sr3usr.data1'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 41 - see DBWR trace file
ORA-01110: data file 41: '/oracle/QAS/sapdata4/sr3db_1/sr3db.data1'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 42 - see DBWR trace file
ORA-01110: data file 42: '/oracle/QAS/sapdata4/sr3db_2/sr3db.data2'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 43 - see DBWR trace file
ORA-01110: data file 43: '/oracle/QAS/sapdata4/sr3db_3/sr3db.data3'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 44 - see DBWR trace file
ORA-01110: data file 44: '/oracle/QAS/sapdata4/sr4db_1/sr4db.data1'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 45 - see DBWR trace file
ORA-01110: data file 45: '/oracle/QAS/sapdata4/sr4db_2/sr4db.data2'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
Thu Jan 20 16:09:31 2011
Errors in file /oracle/QAS/saptrace/background/qas_dbw0_1933.trc:
ORA-01157: cannot identify/lock data file 46 - see DBWR trace file
ORA-01110: data file 46: '/oracle/QAS/sapdata4/sr4db_3/sr4db.data3'
ORA-27037: unable to obtain file status
Solaris-AMD64 Error: 2: No such file or directory
Additional information: 3
ORA-1157 signalled during: ALTER DATABASE OPEN...
Shutting down instance: further logons disabled
Thu Jan 20 16:10:08 2011
Stopping background process MMNL
Thu Jan 20 16:10:08 2011
Stopping background process CJQ0
Thu Jan 20 16:10:09 2011
Stopping background process MMON
Thu Jan 20 16:10:10 2011
Shutting down instance (immediate)
License high water mark = 1
Thu Jan 20 16:10:10 2011
Stopping Job queue slave processes, flags = 7
Thu Jan 20 16:10:10 2011
Job queue slave processes stopped
Thu Jan 20 16:10:10 2011
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Thu Jan 20 16:10:10 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thu Jan 20 16:10:48 2011
Starting ORACLE instance (normal)
Thu Jan 20 16:10:48 2011
Specified value of sga_max_size is too small, bumping to 2365587456
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 2365587456
shared_pool_size = 1157627904
shared_pool_reserved_size= 114152177
filesystemio_options = setall
control_files = /oracle/QAS/origlogA/cntrl/cntlrQAS.dbf, /oracle/QAS/origlogB/cntrl/cntrlQAS.dbf, /oracle/QAS/sapdata1/cntrl/cntrlQAS.dbf
control_file_record_keep_time= 30
db_block_size = 8192
db_cache_size = 1157627904
compatible = 10.2.0
log_archive_dest = /oracle/QAS/oraarch/QASarch
log_buffer = 14242816
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes = 1
background_dump_dest = /oracle/QAS/saptrace/background
user_dump_dest = /oracle/QAS/saptrace/usertrace
core_dump_dest = /oracle/QAS/saptrace/background
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = QAS
open_cursors = 800
_optim_peek_user_binds = FALSE
pga_aggregate_target = 1522029035
workarea_size_policy = AUTO
statistics_level = typical
PMON started with pid=2, OS id=2004
PSP0 started with pid=3, OS id=2006
MMAN started with pid=4, OS id=2008
DBW0 started with pid=5, OS id=2010
LGWR started with pid=6, OS id=2012
CKPT started with pid=7, OS id=2014
SMON started with pid=8, OS id=2016
RECO started with pid=9, OS id=2018
CJQ0 started with pid=10, OS id=2020
MMON started with pid=11, OS id=2022
MMNL started with pid=12, OS id=2024
Thu Jan 20 16:10:49 2011
ALTER DATABASE MOUNT
Thu Jan 20 16:10:55 2011
Setting recovery target incarnation to 1
Thu Jan 20 16:10:56 2011
Successful mount of redo thread 1, with mount id 2130363593
Thu Jan 20 16:10:56 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Shutting down instance: further logons disabled
Thu Jan 20 16:50:31 2011
Stopping background process MMNL
Thu Jan 20 16:50:31 2011
Stopping background process CJQ0
Thu Jan 20 16:50:32 2011
Stopping background process MMON
Thu Jan 20 16:50:33 2011
Shutting down instance (immediate)
License high water mark = 1
Thu Jan 20 16:50:33 2011
Stopping Job queue slave processes, flags = 7
Thu Jan 20 16:50:33 2011
Job queue slave processes stopped
Thu Jan 20 16:50:33 2011
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Thu Jan 20 16:50:33 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thu Jan 20 16:50:39 2011
Starting ORACLE instance (normal)
Thu Jan 20 16:50:40 2011
Specified value of sga_max_size is too small, bumping to 2365587456
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 2365587456
shared_pool_size = 1157627904
shared_pool_reserved_size= 114152177
filesystemio_options = setall
control_files = /oracle/QAS/origlogA/cntrl/cntlrQAS.dbf, /oracle/QAS/origlogB/cntrl/cntrlQAS.dbf, /oracle/QAS/sapdata1/cntrl/cntrlQAS.dbf
control_file_record_keep_time= 30
db_block_size = 8192
db_cache_size = 1157627904
compatible = 10.2.0
log_archive_dest = /oracle/QAS/oraarch/QASarch
log_buffer = 14242816
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes = 1
background_dump_dest = /oracle/QAS/saptrace/background
user_dump_dest = /oracle/QAS/saptrace/usertrace
core_dump_dest = /oracle/QAS/saptrace/background
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = QAS
open_cursors = 800
_optim_peek_user_binds = FALSE
pga_aggregate_target = 1522029035
workarea_size_policy = AUTO
statistics_level = typical
PMON started with pid=2, OS id=2646
PSP0 started with pid=3, OS id=2648
MMAN started with pid=4, OS id=2650
DBW0 started with pid=5, OS id=2652
LGWR started with pid=6, OS id=2654
CKPT started with pid=7, OS id=2656
SMON started with pid=8, OS id=2658
RECO started with pid=9, OS id=2660
CJQ0 started with pid=10, OS id=2662
MMON started with pid=11, OS id=2664
MMNL started with pid=12, OS id=2666
Thu Jan 20 16:50:44 2011
ALTER DATABASE MOUNT
Thu Jan 20 16:50:49 2011
Setting recovery target incarnation to 1
Thu Jan 20 16:50:49 2011
Successful mount of redo thread 1, with mount id 2130356260
Thu Jan 20 16:50:49 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Jan 20 16:50:49 2011
ALTER DATABASE OPEN
Thu Jan 20 16:50:50 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=14, OS id=2670
Thu Jan 20 16:50:50 2011
ARC0: Archival started
ARC1 started with pid=15, OS id=2672
Thu Jan 20 16:50:50 2011
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
Thread 1 opened at log sequence 11071
Current log# 3 seq# 11071 mem# 0: /oracle/QAS/origlogA/log_g13m1.dbf
Current log# 3 seq# 11071 mem# 1: /oracle/QAS/mirrlogA/log_g13m2.dbf
Successful open of redo thread 1
Thu Jan 20 16:50:51 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Jan 20 16:50:51 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Thu Jan 20 16:50:51 2011
ARC1: Becoming the heartbeat ARCH
Thu Jan 20 16:50:51 2011
SMON: enabling cache recovery
Thu Jan 20 16:50:52 2011
Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_2668.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Thu Jan 20 16:50:52 2011
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 2668
ORA-1092 signalled during: ALTER DATABASE OPEN...
Thu Jan 20 16:51:37 2011
Starting ORACLE instance (normal)
Thu Jan 20 16:51:37 2011
Specified value of sga_max_size is too small, bumping to 2365587456
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 2365587456
shared_pool_size = 1157627904
shared_pool_reserved_size= 114152177
filesystemio_options = setall
control_files = /oracle/QAS/origlogA/cntrl/cntlrQAS.dbf, /oracle/QAS/origlogB/cntrl/cntrlQAS.dbf, /oracle/QAS/sapdata1/cntrl/cntrlQAS.dbf
control_file_record_keep_time= 30
db_block_size = 8192
db_cache_size = 1157627904
compatible = 10.2.0
log_archive_dest = /oracle/QAS/oraarch/QASarch
log_buffer = 14242816
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes = 1
background_dump_dest = /oracle/QAS/saptrace/background
user_dump_dest = /oracle/QAS/saptrace/usertrace
core_dump_dest = /oracle/QAS/saptrace/background
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = QAS
open_cursors = 800
_optim_peek_user_binds = FALSE
pga_aggregate_target = 1522029035
workarea_size_policy = AUTO
statistics_level = typical
PMON started with pid=2, OS id=2809
PSP0 started with pid=3, OS id=2811
MMAN started with pid=4, OS id=2813
DBW0 started with pid=5, OS id=2815
LGWR started with pid=6, OS id=2817
CKPT started with pid=7, OS id=2819
SMON started with pid=8, OS id=2821
RECO started with pid=9, OS id=2823
CJQ0 started with pid=10, OS id=2825
MMON started with pid=11, OS id=2827
MMNL started with pid=12, OS id=2829
Thu Jan 20 16:51:38 2011
ALTER DATABASE MOUNT
Thu Jan 20 16:51:42 2011
Setting recovery target incarnation to 1
Thu Jan 20 16:51:42 2011
Successful mount of redo thread 1, with mount id 2130370394
Thu Jan 20 16:51:42 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Jan 20 16:51:42 2011
ALTER DATABASE OPEN
Thu Jan 20 16:51:43 2011
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Thu Jan 20 16:51:44 2011
Started redo scan
Thu Jan 20 16:51:44 2011
Completed redo scan
1 redo blocks read, 0 data blocks need recovery
Thu Jan 20 16:51:44 2011
Started redo application at
Thread 1: logseq 11071, block 79631, scn 158994942
Thu Jan 20 16:51:44 2011
Recovery of Online Redo Log: Thread 1 Group 3 Seq 11071 Reading mem 0
Mem# 0: /oracle/QAS/origlogA/log_g13m1.dbf
Mem# 1: /oracle/QAS/mirrlogA/log_g13m2.dbf
Thu Jan 20 16:51:44 2011
Completed redo application
Thu Jan 20 16:51:44 2011
Completed crash recovery at
Thread 1: logseq 11071, block 79632, scn 159014944
0 data blocks read, 0 data blocks written, 1 redo blocks read
Thu Jan 20 16:51:45 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=2837
Thu Jan 20 16:51:45 2011
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=2839
Thu Jan 20 16:51:45 2011
Thread 1 advanced to log sequence 11072 (thread open)
Thread 1 opened at log sequence 11072
Current log# 4 seq# 11072 mem# 0: /oracle/QAS/origlogB/log_g14m1.dbf
Current log# 4 seq# 11072 mem# 1: /oracle/QAS/mirrlogB/log_g14m2.dbf
Successful open of redo thread 1
Thu Jan 20 16:51:45 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Jan 20 16:51:45 2011
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Thu Jan 20 16:51:45 2011
ARC0: Becoming the heartbeat ARCH
Thu Jan 20 16:51:45 2011
SMON: enabling cache recovery
Thu Jan 20 16:51:46 2011
Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_2831.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Thu Jan 20 16:51:46 2011
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 2831
ORA-1092 signalled during: ALTER DATABASE OPEN...
Thu Jan 20 16:53:53 2011
Starting ORACLE instance (normal)
Thu Jan 20 16:53:53 2011
Specified value of sga_max_size is too small, bumping to 2365587456
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 2365587456
shared_pool_size = 1157627904
shared_pool_reserved_size= 114152177
filesystemio_options = setall
control_files = /oracle/QAS/origlogA/cntrl/cntlrQAS.dbf, /oracle/QAS/origlogB/cntrl/cntrlQAS.dbf, /oracle/QAS/sapdata1/cntrl/cntrlQAS.dbf
control_file_record_keep_time= 30
db_block_size = 8192
db_cache_size = 1157627904
compatible = 10.2.0
log_archive_dest = /oracle/QAS/oraarch/QASarch
log_buffer = 14242816
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes = 1
background_dump_dest = /oracle/QAS/saptrace/background
user_dump_dest = /oracle/QAS/saptrace/usertrace
core_dump_dest = /oracle/QAS/saptrace/background
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = QAS
open_cursors = 800
_optim_peek_user_binds = FALSE
pga_aggregate_target = 1522029035
workarea_size_policy = AUTO
statistics_level = typical
PMON started with pid=2, OS id=2976
PSP0 started with pid=3, OS id=2978
MMAN started with pid=4, OS id=2980
DBW0 started with pid=5, OS id=2982
LGWR started with pid=6, OS id=2984
CKPT started with pid=7, OS id=2986
SMON started with pid=8, OS id=2988
RECO started with pid=9, OS id=2990
CJQ0 started with pid=10, OS id=2992
MMON started with pid=11, OS id=2994
MMNL started with pid=12, OS id=2996
Thu Jan 20 16:53:55 2011
ALTER DATABASE MOUNT
Thu Jan 20 16:53:59 2011
Setting recovery target incarnation to 1
Thu Jan 20 16:53:59 2011
Successful mount of redo thread 1, with mount id 2130338275
Thu Jan 20 16:53:59 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Jan 20 16:53:59 2011
ALTER DATABASE OPEN
Thu Jan 20 16:53:59 2011
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Thu Jan 20 16:54:00 2011
Started redo scan
Thu Jan 20 16:54:00 2011
Completed redo scan
1 redo blocks read, 0 data blocks need recovery
Thu Jan 20 16:54:00 2011
Started redo application at
Thread 1: logseq 11072, block 2, scn 159014946
Thu Jan 20 16:54:00 2011
Recovery of Online Redo Log: Thread 1 Group 4 Seq 11072 Reading mem 0
Mem# 0: /oracle/QAS/origlogB/log_g14m1.dbf
Mem# 1: /oracle/QAS/mirrlogB/log_g14m2.dbf
Thu Jan 20 16:54:00 2011
Completed redo application
Thu Jan 20 16:54:00 2011
Completed crash recovery at
Thread 1: logseq 11072, block 3, scn 159034948
0 data blocks read, 0 data blocks written, 1 redo blocks read
Thu Jan 20 16:54:00 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=3004
Thu Jan 20 16:54:00 2011
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=3006
Thu Jan 20 16:54:01 2011
Thread 1 advanced to log sequence 11073 (thread open)
Thread 1 opened at log sequence 11073
Current log# 1 seq# 11073 mem# 0: /oracle/QAS/origlogA/log_g11m1.dbf
Current log# 1 seq# 11073 mem# 1: /oracle/QAS/mirrlogA/log_g11m2.dbf
Successful open of redo thread 1
Thu Jan 20 16:54:01 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Jan 20 16:54:01 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Thu Jan 20 16:54:01 2011
ARC1: Becoming the heartbeat ARCH
Thu Jan 20 16:54:01 2011
SMON: enabling cache recovery
Thu Jan 20 16:54:02 2011
Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_2998.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Thu Jan 20 16:54:02 2011
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 2998
ORA-1092 signalled during: ALTER DATABASE OPEN...
Thu Jan 20 16:55:10 2011
Starting ORACLE instance (normal)
Thu Jan 20 16:55:10 2011
Specified value of sga_max_size is too small, bumping to 2365587456
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 2365587456
shared_pool_size = 1157627904
shared_pool_reserved_size= 114152177
filesystemio_options = setall
control_files = /oracle/QAS/origlogA/cntrl/cntlrQAS.dbf, /oracle/QAS/origlogB/cntrl/cntrlQAS.dbf, /oracle/QAS/sapdata1/cntrl/cntrlQAS.dbf
control_file_record_keep_time= 30
db_block_size = 8192
db_cache_size = 1157627904
compatible = 10.2.0
log_archive_dest = /oracle/QAS/oraarch/QASarch
log_buffer = 14242816
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes = 1
background_dump_dest = /oracle/QAS/saptrace/background
user_dump_dest = /oracle/QAS/saptrace/usertrace
core_dump_dest = /oracle/QAS/saptrace/background
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = QAS
open_cursors = 800
_optim_peek_user_binds = FALSE
pga_aggregate_target = 1522029035
workarea_size_policy = AUTO
statistics_level = typical
PMON started with pid=2, OS id=3062
PSP0 started with pid=3, OS id=3064
MMAN started with pid=4, OS id=3066
DBW0 started with pid=5, OS id=3068
LGWR started with pid=6, OS id=3070
CKPT started with pid=7, OS id=3072
SMON started with pid=8, OS id=3074
RECO started with pid=9, OS id=3076
CJQ0 started with pid=10, OS id=3078
MMON started with pid=11, OS id=3080
MMNL started with pid=12, OS id=3082
Thu Jan 20 16:55:11 2011
ALTER DATABASE MOUNT
Thu Jan 20 16:55:16 2011
Setting recovery target incarnation to 1
Thu Jan 20 16:55:16 2011
Successful mount of redo thread 1, with mount id 2130362159
Thu Jan 20 16:55:16 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Jan 20 16:55:16 2011
ALTER DATABASE OPEN
Thu Jan 20 16:55:16 2011
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Thu Jan 20 16:55:16 2011
Started redo scan
Thu Jan 20 16:55:16 2011
Completed redo scan
1 redo blocks read, 0 data blocks need recovery
Thu Jan 20 16:55:16 2011
Started redo application at
Thread 1: logseq 11073, block 2, scn 159034950
Thu Jan 20 16:55:16 2011
Recovery of Online Redo Log: Thread 1 Group 1 Seq 11073 Reading mem 0
Mem# 0: /oracle/QAS/origlogA/log_g11m1.dbf
Mem# 1: /oracle/QAS/mirrlogA/log_g11m2.dbf
Thu Jan 20 16:55:16 2011
Completed redo application
Thu Jan 20 16:55:16 2011
Completed crash recovery at
Thread 1: logseq 11073, block 3, scn 159054952
0 data blocks read, 0 data blocks written, 1 redo blocks read
Thu Jan 20 16:55:17 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=3090
Thu Jan 20 16:55:17 2011
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=3092
Thu Jan 20 16:55:17 2011
Thread 1 advanced to log sequence 11074 (thread open)
Thread 1 opened at log sequence 11074
Current log# 2 seq# 11074 mem# 0: /oracle/QAS/origlogB/log_g12m1.dbf
Current log# 2 seq# 11074 mem# 1: /oracle/QAS/mirrlogB/log_g12m2.dbf
Successful open of redo thread 1
Thu Jan 20 16:55:17 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Jan 20 16:55:17 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Thu Jan 20 16:55:17 2011
ARC1: Becoming the heartbeat ARCH
Thu Jan 20 16:55:17 2011
SMON: enabling cache recovery
Thu Jan 20 16:55:17 2011
Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_3084.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Thu Jan 20 16:55:17 2011
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 3084
ORA-1092 signalled during: ALTER DATABASE OPEN...
Fri Jan 21 07:58:16 2011
Starting ORACLE instance (normal)
Fri Jan 21 07:58:16 2011
Specified value of sga_max_size is too small, bumping to 2365587456
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 2365587456
shared_pool_size = 1157627904
shared_pool_reserved_size= 114152177
filesystemio_options = setall
control_files = /oracle/QAS/origlogA/cntrl/cntlrQAS.dbf, /oracle/QAS/origlogB/cntrl/cntrlQAS.dbf, /oracle/QAS/sapdata1/cntrl/cntrlQAS.dbf
control_file_record_keep_time= 30
db_block_size = 8192
db_cache_size = 1157627904
compatible = 10.2.0
log_archive_dest = /oracle/QAS/oraarch/QASarch
log_buffer = 14242816
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes = 1
background_dump_dest = /oracle/QAS/saptrace/background
user_dump_dest = /oracle/QAS/saptrace/usertrace
core_dump_dest = /oracle/QAS/saptrace/background
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = QAS
open_cursors = 800
_optim_peek_user_binds = FALSE
pga_aggregate_target = 1522029035
workarea_size_policy = AUTO
statistics_level = typical
PMON started with pid=2, OS id=3630
PSP0 started with pid=3, OS id=3632
MMAN started with pid=4, OS id=3634
DBW0 started with pid=5, OS id=3636
LGWR started with pid=6, OS id=3638
CKPT started with pid=7, OS id=3640
SMON started with pid=8, OS id=3642
RECO started with pid=9, OS id=3644
CJQ0 started with pid=10, OS id=3646
MMON started with pid=11, OS id=3648
MMNL started with pid=12, OS id=3650
Fri Jan 21 07:58:17 2011
ALTER DATABASE MOUNT
Fri Jan 21 07:58:23 2011
Setting recovery target incarnation to 1
Fri Jan 21 07:58:23 2011
Successful mount of redo thread 1, with mount id 2130388441
Fri Jan 21 07:58:23 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Fri Jan 21 07:58:23 2011
ALTER DATABASE OPEN
Fri Jan 21 07:58:23 2011
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Fri Jan 21 07:58:24 2011
Started redo scan
Fri Jan 21 07:58:24 2011
Completed redo scan
1 redo blocks read, 0 data blocks need recovery
Fri Jan 21 07:58:24 2011
Started redo application at
Thread 1: logseq 11074, block 2, scn 159054954
Fri Jan 21 07:58:24 2011
Recovery of Online Redo Log: Thread 1 Group 2 Seq 11074 Reading mem 0
Mem# 0: /oracle/QAS/origlogB/log_g12m1.dbf
Mem# 1: /oracle/QAS/mirrlogB/log_g12m2.dbf
Fri Jan 21 07:58:24 2011
Completed redo application
Fri Jan 21 07:58:24 2011
Completed crash recovery at
Thread 1: logseq 11074, block 3, scn 159074956
0 data blocks read, 0 data blocks written, 1 redo blocks read
Fri Jan 21 07:58:25 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=3658
Fri Jan 21 07:58:25 2011
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=3660
Fri Jan 21 07:58:25 2011
Thread 1 advanced to log sequence 11075 (thread open)
Thread 1 opened at log sequence 11075
Current log# 4 seq# 11075 mem# 0: /oracle/QAS/origlogB/log_g14m1.dbf
Current log# 4 seq# 11075 mem# 1: /oracle/QAS/mirrlogB/log_g14m2.dbf
Successful open of redo thread 1
Fri Jan 21 07:58:25 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Jan 21 07:58:25 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Fri Jan 21 07:58:25 2011
ARC1: Becoming the heartbeat ARCH
Fri Jan 21 07:58:25 2011
SMON: enabling cache recovery
Fri Jan 21 07:58:26 2011
Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_3652.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Fri Jan 21 07:58:26 2011
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 3652
ORA-1092 signalled during: ALTER DATABASE OPEN...
Fri Jan 21 08:02:39 2011
Starting ORACLE instance (normal)
Fri Jan 21 08:02:39 2011
Specified value of sga_max_size is too small, bumping to 2365587456
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 2365587456
shared_pool_size = 1157627904
shared_pool_reserved_size= 114152177
filesystemio_options = setall
control_files = /oracle/QAS/origlogA/cntrl/cntlrQAS.dbf, /oracle/QAS/origlogB/cntrl/cntrlQAS.dbf, /oracle/QAS/sapdata1/cntrl/cntrlQAS.dbf
control_file_record_keep_time= 30
db_block_size = 8192
db_cache_size = 1157627904
compatible = 10.2.0
log_archive_dest = /oracle/QAS/oraarch/QASarch
log_buffer = 14242816
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes = 1
background_dump_dest = /oracle/QAS/saptrace/background
user_dump_dest = /oracle/QAS/saptrace/usertrace
core_dump_dest = /oracle/QAS/saptrace/background
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = QAS
open_cursors = 800
_optim_peek_user_binds = FALSE
pga_aggregate_target = 1522029035
workarea_size_policy = AUTO
statistics_level = typical
PMON started with pid=2, OS id=3816
PSP0 started with pid=3, OS id=3818
MMAN started with pid=4, OS id=3820
DBW0 started with pid=5, OS id=3822
LGWR started with pid=6, OS id=3824
CKPT started with pid=7, OS id=3826
SMON started with pid=8, OS id=3828
RECO started with pid=9, OS id=3830
CJQ0 started with pid=10, OS id=3832
MMON started with pid=11, OS id=3834
MMNL started with pid=12, OS id=3836
Fri Jan 21 08:02:40 2011
ALTER DATABASE MOUNT
Fri Jan 21 08:02:45 2011
Setting recovery target incarnation to 1
Fri Jan 21 08:02:45 2011
Successful mount of redo thread 1, with mount id 2130441696
Fri Jan 21 08:02:45 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Fri Jan 21 08:02:45 2011
ALTER DATABASE OPEN
Fri Jan 21 08:02:45 2011
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Fri Jan 21 08:02:45 2011
Started redo scan
Fri Jan 21 08:02:46 2011
Completed redo scan
1 redo blocks read, 0 data blocks need recovery
Fri Jan 21 08:02:46 2011
Started redo application at
Thread 1: logseq 11075, block 2, scn 159074958
Fri Jan 21 08:02:46 2011
Recovery of Online Redo Log: Thread 1 Group 4 Seq 11075 Reading mem 0
Mem# 0: /oracle/QAS/origlogB/log_g14m1.dbf
Mem# 1: /oracle/QAS/mirrlogB/log_g14m2.dbf
Fri Jan 21 08:02:46 2011
Completed redo application
Fri Jan 21 08:02:46 2011
Completed crash recovery at
Thread 1: logseq 11075, block 3, scn 159094960
0 data blocks read, 0 data blocks written, 1 redo blocks read
Fri Jan 21 08:02:47 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=3844
Fri Jan 21 08:02:47 2011
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=3846
Fri Jan 21 08:02:47 2011
Thread 1 advanced to log sequence 11076 (thread open)
Thread 1 opened at log sequence 11076
Current log# 1 seq# 11076 mem# 0: /oracle/QAS/origlogA/log_g11m1.dbf
Current log# 1 seq# 11076 mem# 1: /oracle/QAS/mirrlogA/log_g11m2.dbf
Successful open of redo thread 1
Fri Jan 21 08:02:47 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Jan 21 08:02:47 2011
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Fri Jan 21 08:02:47 2011
ARC0: Becoming the heartbeat ARCH
Fri Jan 21 08:02:48 2011
SMON: enabling cache recovery
Fri Jan 21 08:02:48 2011
Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_3838.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Fri Jan 21 08:02:48 2011
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 3838
ORA-1092 signalled during: ALTER DATABASE OPEN...

_________________
Человек рождается уставшим и живет чтобы отдохнуть


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 10:12 
Старший специалист
Старший специалист
Аватара пользователя

Зарегистрирован:
Ср, июн 11 2008, 09:41
Сообщения: 340
Пол: Мужской
Версии оракля точно совпадают? Что - то меня терзают смутные сомненья.

_________________
SAP Basis, SAP Security Audit/Pentest, РФ, Москва


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 10:21 
Почетный гуру
Почетный гуру
Аватара пользователя

Зарегистрирован:
Чт, сен 16 2004, 17:10
Сообщения: 2229
Откуда: Moscow, кажется...
Пол: Мужской
ZeUsM написал:
Версии оракля точно совпадают? Что - то меня терзают смутные сомненья.

ORA-39700: database must be opened with UPGRADE option

Cause: A normal database open was attempted, but the database has not been upgraded to the current server version.

_________________
Я бы хотел поглядеть на эффективную армию, состоящую из эффективных менеджеров.
BRGDS,
Aleks Изображение


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 10:24 
Старший специалист
Старший специалист
Аватара пользователя

Зарегистрирован:
Ср, июн 11 2008, 09:41
Сообщения: 340
Пол: Мужской
avlag написал:
ZeUsM написал:
Версии оракля точно совпадают? Что - то меня терзают смутные сомненья.

ORA-39700: database must be opened with UPGRADE option

Cause: A normal database open was attempted, but the database has not been upgraded to the current server version.


Так и я про это =)

_________________
SAP Basis, SAP Security Audit/Pentest, РФ, Москва


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 10:26 
Старший специалист
Старший специалист
Аватара пользователя

Зарегистрирован:
Ср, июн 11 2008, 09:41
Сообщения: 340
Пол: Мужской
Ооооо, батенька, только заметил
Цитата:
Solaris 10 Oracle 10-2-0-2 SAR ERP 2005 SR2 ABAP+JAVA Central Instance
установил заново ERP6.0 SR3 ABAP+JAVA Central Instance Solaris 10 Oracle 10-2-0-4. Из backup в /oracle/SID/102_64/dbs скопировал spfileSID.ora initSID.ora initSID.sap

Ничего не смущает?

_________________
SAP Basis, SAP Security Audit/Pentest, РФ, Москва


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 10:27 
Ассистент
Ассистент

Зарегистрирован:
Вт, окт 26 2010, 15:00
Сообщения: 32
Пол: Мужской
Я в brtools menu 120 Restory files from BRBACKUP backup там выбрал control_file затем в меню 11 Whole database reset восстановил все файлы.
Переменные окружения для юзера скопировал с своей системы (которая полетела) и поверху заново проинсталировал сап.,новая инсталяция отличается только host name и ip адрес но это не существенно.
Ядро сейчас
Solaris 10 10/09 s10x_u8wos_08a X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 16 September 2009

было на старом сервере
Solaris 10 6/06 s10x_u2wos_09a X86
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 09 June 2006

_________________
Человек рождается уставшим и живет чтобы отдохнуть


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 10:33 
Ассистент
Ассистент

Зарегистрирован:
Вт, окт 26 2010, 15:00
Сообщения: 32
Пол: Мужской
Наш спец по oracle уверил меня что все будет гут. Я сейчас установил на упавшем сервере новый винт и заново Database Instance Solaris 10 Oracle 10-2-0-2 SAR ERP 2005 SR2 потом повторю всю процедуру восстановления из бакаппазаново.
Не подскажете а что сделать с текущим сервером где не совпадают уровни патча базы.Oracle 10-2-0-2 была база с которой созали бакапп а установил на Oracle 10-2-0-4.
Подскажите плиз что надо делать)))
ORA-39700: database must be opened with UPGRADE option

_________________
Человек рождается уставшим и живет чтобы отдохнуть


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle  Тема решена
СообщениеДобавлено: Пт, янв 21 2011, 10:36 
Старший специалист
Старший специалист
Аватара пользователя

Зарегистрирован:
Ср, июн 11 2008, 09:41
Сообщения: 340
Пол: Мужской
serg1973 написал:
Наш спец по oracle уверил меня что все будет гут. Я сейчас установил на упавшем сервере новый винт и заново Database Instance Solaris 10 Oracle 10-2-0-2 SAR ERP 2005 SR2 потом повторю всю процедуру восстановления из бакаппазаново.
Не подскажете а что сделать с текущим сервером где не совпадают уровни патча базы.Oracle 10-2-0-2 была база с которой созали бакапп а установил на Oracle 10-2-0-4.
Подскажите плиз что надо делать)))
ORA-39700: database must be opened with UPGRADE option

К патчсету оракла есть readme.html там вроде подробно расписано каким образом провести upgrade базы.
Я не настолько часто этим занимался, поэтому не помню все тонкости =)
Но там не сложно.

_________________
SAP Basis, SAP Security Audit/Pentest, РФ, Москва


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
 Заголовок сообщения: Re: Восстановление системы после отказа винчестера с oracle
СообщениеДобавлено: Пт, янв 21 2011, 11:57 
Ассистент
Ассистент

Зарегистрирован:
Вт, окт 26 2010, 15:00
Сообщения: 32
Пол: Мужской
SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catupgrd.sql
SQL> SPOOL OFF

в данный момент скрипт выполняется...

далее нужно будет запустить еще только один скрипт, если не используется RAC:
SQL> @?/rdbms/admin/utlrp.s


Всем огромное спасибо за помощь.

_________________
Человек рождается уставшим и живет чтобы отдохнуть


Пометить тему как нерешенную
Вернуться к началу
 Профиль  
 
Показать сообщения за:  Поле сортировки  
Начать новую тему Ответить на тему  [ Сообщений: 15 ] 

Часовой пояс: UTC + 3 часа


Кто сейчас на конференции

Сейчас этот форум просматривают: нет зарегистрированных пользователей


Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете добавлять вложения

Найти:
Перейти:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Русская поддержка phpBB