[ОТВЕТИТЬ]
09.06.2011 16:16
VitorJ
 
Доброго времени суток возникла проблема вот такого плана.
Кассовый документ не записывается в базу, говорит что один и тот же идентификатор принадлежит разным документам.
SQL код:
----- Ошибка приема -----
Пакет110609125101_461_1.SVP
Тип объекта
Возвраты по кассе
Идентификатор объекта
СВ20110320@6
   
-- Уровень вложения 0 --
СообщениеНевозможно обновить в БД объект «CRСВ20110320@таблица «SMDOCUMENTS»
Исключение
Sm.Core.BaseException
Источник
Sm.Post.DbLoader
Метод
Void WriteExistingObject(System.Data.OracleClient.OracleTransactionSm.Post.PostObject)
   -- 
Уровень вложения 1 --
СообщениеORA-20047Два разных объекта имеют одинаковые идентификаторы
ORA
-06512на  "SUPERMAG.CORE"line 300
ORA
-06512на  "SUPERMAG.SMDOCUMENTSBORNIN"line 17
ORA
-04088: ошибка во время выполнения триггера 'SUPERMAG.SMDOCUMENTSBORNIN' 
При проверке действительно документы с одним id но за разные числа.
Подскажите возможно ли пересоздать идентификаторы кассовых документов или как то выправить ситуацию?
Это галимотья началась за долго до моего прихода в эту организацию, все тупо положили а сейчас начали требовать.
09.06.2011 16:39
Dim
 
в id документа кодируется дата, когда документ был сформирован. как у вас могут совпасть id?
09.06.2011 16:46
VitorJ
 
Что дата кодируется я знаю.... а вот как это произошло увы нет, но это факт.
09.06.2011 16:55
VitorJ
 
Да напладил я тем... в общем сдела следующим образом удалил их в ЦО и поднял по новой, завтра будем сверять и дальше думать.
10.06.2011 08:13
Mtirt
 
Каким образом и откуда они появились в ЦО?
Из базы другого магазина? Или в ЦО их создали? Как создавали?
10.06.2011 13:22
VitorJ
 
А шут его знает... как их создавали. Ещё возникла одна проблема. Не отображаются продажи за месяц в базе магазина при попытке спустить их с верху возникает ошибка о том что один и тот же идентификатор принадлежит разным документам.
Хотя в Супермаге не отображается.
10.06.2011 13:30
Mtirt
 
У документа есть журнал истории. По нему видно где создан документ - в ЦО или прислан почтовым модулем.
У почтового модуля есть журнал приема. По нему можно понять откуда этот документ пришел.

Или речь о той же базе, что была в этой ветке: https://olegon.ru/showthread.php?t=10217 ?
10.06.2011 13:31
Mtirt
 
Цитата:
VitorJ А шут его знает... как их создавали. Ещё возникла одна проблема. Не отображаются продажи за месяц в базе магазина при попытке спустить их с верху возникает ошибка о том что один и тот же идентификатор принадлежит разным документам.
Хотя в Супермаге не отображается.
Я не верю, что В Супермаге нет документа.
Разделы - Кассовые документы - отобрать все.
Находится документ с тем же номером?
10.06.2011 13:45
VitorJ
 
Да речь именно о той самой базе. Как выяснилось она уже падала 2 раза, её кто то там востанавливал народ поменялся концов не найти. Журналов по документам соотвественно нет. Действительно при выборе Всё документы не отображаются.
10.06.2011 13:56
Mtirt
 
Значит с вероятностью 90% с ней опять что-то не так.
Идите читать логи оракла.

Кстати, в прошлый раз было похоже на проблемы с винчестером. Его заменили?
10.06.2011 15:23
VitorJ
 
Да винты заменили. Подскажите в Oracle ещё пока новичок.... где смотреть логи?
10.06.2011 15:34
Mtirt
 
Бить буду. Долго и мучительно.
Ну хотя бы FAQ в каждом разделе можно прочитать?

https://olegon.ru/showpost.php?p=48889&postcount=27
10.06.2011 15:42
VitorJ
 
Можешь побить, только в терновый куст не бросай!
10.06.2011 16:21
VitorJ
 
Вот кусок лога за сегодняшний день.
Код:
Fri Jun 10 00:11:40 2011
ALTER SYSTEM ARCHIVE LOG
Fri Jun 10 00:11:40 2011
Thread 1 cannot allocate new log, sequence 203
Private strand flush not complete
  Current log# 1 seq# 202 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO01.LOG
Fri Jun 10 00:11:42 2011
Thread 1 advanced to log sequence 203 (LGWR switch)
  Current log# 2 seq# 203 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO02.LOG
Fri Jun 10 00:13:13 2011
Starting control autobackup
Control autobackup written to DISK device
	handle 'C:\BACKUP_ORA\BALBEPAV\AUTOBACKUP\2011_06_10\O1_MF_S_753408793_6Z1RRB2Q_.BKP'
Fri Jun 10 00:13:21 2011
ALTER SYSTEM ARCHIVE LOG
Fri Jun 10 00:13:21 2011
Thread 1 cannot allocate new log, sequence 204
Private strand flush not complete
  Current log# 2 seq# 203 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO02.LOG
Fri Jun 10 00:13:22 2011
Thread 1 advanced to log sequence 204 (LGWR switch)
  Current log# 3 seq# 204 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO03.LOG
Fri Jun 10 00:15:41 2011
ALTER SYSTEM ARCHIVE LOG
Fri Jun 10 00:15:41 2011
Thread 1 cannot allocate new log, sequence 205
Private strand flush not complete
  Current log# 3 seq# 204 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO03.LOG
Fri Jun 10 00:15:43 2011
Thread 1 advanced to log sequence 205 (LGWR switch)
  Current log# 1 seq# 205 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO01.LOG
Fri Jun 10 00:15:45 2011
Starting control autobackup
Control autobackup written to DISK device
	handle 'C:\BACKUP_ORA\BALBEPAV\AUTOBACKUP\2011_06_10\O1_MF_S_753408945_6Z1RX1V1_.BKP'
Fri Jun 10 04:18:40 2011
alter tablespace "INDX" coalesce
Fri Jun 10 04:18:40 2011
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 04:18:41 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 04:18:42 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 04:18:43 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 04:19:37 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 04:21:15 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCALCERFIELDS have been marked unusable
Fri Jun 10 04:21:25 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCALCERGRAPHS have been marked unusable
Fri Jun 10 04:21:35 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAANALYTICSGROUP have been marked unusable
Fri Jun 10 04:21:46 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAANALYTICSGROUPLINK have been marked unusable
Fri Jun 10 04:21:56 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAANALYTICSTYPEFIELD have been marked unusable
Fri Jun 10 04:22:06 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAANALYTICSFORMULA have been marked unusable
Fri Jun 10 04:22:13 2011
Thread 1 advanced to log sequence 206 (LGWR switch)
  Current log# 2 seq# 206 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO02.LOG
Fri Jun 10 04:22:17 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAANALYTICSTYPEGROUP have been marked unusable
Fri Jun 10 04:49:41 2011
alter tablespace "INDX" coalesce
Fri Jun 10 04:49:41 2011
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 04:49:41 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 04:49:42 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 04:49:44 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 04:50:18 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 04:50:55 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCALCERFUNCS have been marked unusable
Fri Jun 10 04:51:05 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCALCERROUNDS have been marked unusable
Fri Jun 10 04:52:18 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSREPLIC have been marked unusable
Fri Jun 10 05:20:41 2011
alter tablespace "INDX" coalesce
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 05:20:41 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 05:20:42 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 05:20:44 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 05:21:17 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 05:22:24 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMSPECCO have been marked unusable
Fri Jun 10 05:51:40 2011
alter tablespace "INDX" coalesce
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 05:51:41 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 05:51:42 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 05:51:43 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 05:52:16 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 05:53:24 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCASHCHECKCOMPLEXITEMS have been marked unusable
Fri Jun 10 05:54:23 2011
Some indexes or index [sub]partitions of table SUPERMAG.SADOCPROPMAP have been marked unusable
Fri Jun 10 05:54:34 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSDOCGEN have been marked unusable
Fri Jun 10 06:22:39 2011
alter tablespace "INDX" coalesce
Fri Jun 10 06:22:39 2011
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 06:22:40 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 06:22:41 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 06:22:42 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 06:23:15 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 06:23:43 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPARTNERUSERLOC have been marked unusable
Fri Jun 10 06:24:24 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTREQUESTS have been marked unusable
Fri Jun 10 06:24:58 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAOPPOSITEOPS have been marked unusable
Fri Jun 10 06:25:31 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSSYSINFOBACKUP have been marked unusable
Fri Jun 10 06:53:40 2011
alter tablespace "INDX" coalesce
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 06:53:41 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 06:53:42 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 06:53:43 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 06:54:16 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 06:54:20 2011
Some indexes or index [sub]partitions of table SUPERMAG.SASCHEDULE have been marked unusable
Fri Jun 10 06:54:31 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSCONTROLFUNCTIONS have been marked unusable
Fri Jun 10 06:55:04 2011
Some indexes or index [sub]partitions of table SUPERMAG.FFDEBUGLOG have been marked unusable
Fri Jun 10 06:55:15 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSEVENTLOG have been marked unusable
Fri Jun 10 06:55:25 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTTABLE have been marked unusable
Fri Jun 10 06:55:38 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTEXCLUDECOLUMN have been marked unusable
Fri Jun 10 06:55:49 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTPKCOLUMN have been marked unusable
Fri Jun 10 06:56:25 2011
Some indexes or index [sub]partitions of table SUPERMAG.index$_join$_001 have been marked unusable
Fri Jun 10 06:56:38 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMSPECCOMPINF have been marked unusable
Fri Jun 10 06:58:19 2011
Thread 1 advanced to log sequence 207 (LGWR switch)
  Current log# 3 seq# 207 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO03.LOG
Fri Jun 10 07:24:41 2011
alter tablespace "INDX" coalesce
Fri Jun 10 07:24:41 2011
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 07:24:42 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 07:24:42 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 07:24:44 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 07:25:17 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 07:25:22 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSMESSAGES have been marked unusable
Fri Jun 10 07:25:32 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSCONTROLFNTYPES have been marked unusable
Fri Jun 10 07:25:42 2011
Some indexes or index [sub]partitions of table SUPERMAG.SADOCOPERATION have been marked unusable
Fri Jun 10 07:25:53 2011
Some indexes or index [sub]partitions of table SUPERMAG.SASCALEMODELS have been marked unusable
Fri Jun 10 07:26:03 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMSTORELOCOFFEXT have been marked unusable
Fri Jun 10 07:26:51 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTPACKAGES have been marked unusable
Fri Jun 10 07:27:04 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTQUEUE have been marked unusable
Fri Jun 10 07:27:16 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTFILTERSPARAMLOC have been marked unusable
Fri Jun 10 07:27:34 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTLOCATIONS have been marked unusable
Fri Jun 10 07:27:49 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSPOSTTRANSPARAM have been marked unusable
Fri Jun 10 07:28:00 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSPOSTTRANSPORTS have been marked unusable
Fri Jun 10 07:28:10 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSPOSTFILTERSPARAM have been marked unusable
Fri Jun 10 07:28:20 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSPOSTFILTERS have been marked unusable
Fri Jun 10 07:55:40 2011
alter tablespace "INDX" coalesce
Fri Jun 10 07:55:40 2011
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 07:55:41 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 07:55:42 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 07:55:43 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 07:56:16 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 07:56:21 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTVIRTPACKS have been marked unusable
Fri Jun 10 07:56:54 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTFAILRPDATA have been marked unusable
Fri Jun 10 07:57:04 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTPARAM have been marked unusable
Fri Jun 10 07:57:37 2011
Some indexes or index [sub]partitions of table SUPERMAG.SADOMAINSCLASS have been marked unusable
Fri Jun 10 07:57:50 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAANALYTICSFIELDS have been marked unusable
Fri Jun 10 07:58:03 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCALCERLINKS have been marked unusable
Fri Jun 10 07:58:13 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCALCERCELLS have been marked unusable
Fri Jun 10 07:58:23 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCALCERBASICGRAPHS have been marked unusable
Fri Jun 10 07:58:33 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSSUGGESTORDERALG have been marked unusable
Fri Jun 10 07:59:08 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTRULES have been marked unusable
Fri Jun 10 08:26:43 2011
alter tablespace "INDX" coalesce
Fri Jun 10 08:26:43 2011
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 08:26:44 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 08:26:45 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 08:26:46 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 08:27:23 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 08:27:28 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSDOMAINMODELS have been marked unusable
Fri Jun 10 08:27:39 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSDOMAINMODELCLASS have been marked unusable
Fri Jun 10 08:27:50 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSHWDOMAINSMODELLIST have been marked unusable
Fri Jun 10 08:28:23 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTCOLUMN have been marked unusable
Fri Jun 10 08:28:34 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMOFFICELOG have been marked unusable
Fri Jun 10 08:29:08 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMFUNCDOCSTATE have been marked unusable
Fri Jun 10 08:29:19 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSINSPECTDOC have been marked unusable
Fri Jun 10 08:29:29 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMINSPECTCFG have been marked unusable
Fri Jun 10 08:29:39 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSINSPECTFUNCDETAIL have been marked unusable
Fri Jun 10 08:29:49 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSINSPECTFUNC have been marked unusable
Fri Jun 10 08:30:07 2011
Some indexes or index [sub]partitions of table SUPERMAG.index$_join$_001 have been marked unusable
Fri Jun 10 08:30:22 2011
Some indexes or index [sub]partitions of table SUPERMAG.SACARDPROPDEF have been marked unusable
Fri Jun 10 08:57:41 2011
alter tablespace "INDX" coalesce
Fri Jun 10 08:57:41 2011
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 08:57:42 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 08:57:43 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 08:57:44 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 08:58:19 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 08:58:23 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCREDCARDS have been marked unusable
Fri Jun 10 08:58:34 2011
Some indexes or index [sub]partitions of table SUPERMAG.SACOUNTRIES have been marked unusable
Fri Jun 10 08:58:47 2011
Some indexes or index [sub]partitions of table SUPERMAG.index$_join$_001 have been marked unusable
Fri Jun 10 08:59:00 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAARTICLETYPES have been marked unusable
Fri Jun 10 08:59:14 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAMEASUREMENT have been marked unusable
Fri Jun 10 08:59:38 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAMATRIXRULES have been marked unusable
Fri Jun 10 08:59:49 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPRICERTYPES have been marked unusable
Fri Jun 10 09:00:26 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAQLMISMREASON have been marked unusable
Fri Jun 10 09:01:03 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSDOCSTATES have been marked unusable
Fri Jun 10 09:01:21 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPRICECHECKRULES have been marked unusable
Fri Jun 10 09:01:35 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPRICEROUNDTHRESHOLDS have been marked unusable
Fri Jun 10 09:28:41 2011
alter tablespace "INDX" coalesce
Fri Jun 10 09:28:41 2011
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 09:28:42 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 09:28:43 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 09:28:44 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 09:29:16 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 09:29:21 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAHOLIDAYS have been marked unusable
Fri Jun 10 09:29:31 2011
Some indexes or index [sub]partitions of table SUPERMAG.SACARDNAMEFORMDEF have been marked unusable
Fri Jun 10 09:29:41 2011
Some indexes or index [sub]partitions of table SUPERMAG.SACARDNAMEFORMVAL have been marked unusable
Fri Jun 10 09:30:02 2011
Some indexes or index [sub]partitions of table SUPERMAG.SACLIENTPROPDEF have been marked unusable
Fri Jun 10 09:30:18 2011
Some indexes or index [sub]partitions of table SUPERMAG.index$_join$_001 have been marked unusable
Fri Jun 10 09:31:18 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMLOCALPRICE have been marked unusable
Fri Jun 10 09:31:28 2011
Some indexes or index [sub]partitions of table SUPERMAG.index$_join$_001 have been marked unusable
Fri Jun 10 09:31:41 2011
Some indexes or index [sub]partitions of table SUPERMAG.SABANKS have been marked unusable
Fri Jun 10 09:32:01 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAASSORTMATRIX have been marked unusable
Fri Jun 10 09:32:22 2011
Some indexes or index [sub]partitions of table SUPERMAG.SLBARDEF have been marked unusable
Fri Jun 10 10:30:41 2011
alter tablespace "INDX" coalesce
Fri Jun 10 10:30:41 2011
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 10:30:42 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 10:30:43 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 10:30:44 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 10:31:22 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 10:31:27 2011
Some indexes or index [sub]partitions of table SUPERMAG.SABARCODES have been marked unusable
Fri Jun 10 10:31:40 2011
Some indexes or index [sub]partitions of table SUPERMAG.SASTOREPROPDEF have been marked unusable
Fri Jun 10 10:31:56 2011
Some indexes or index [sub]partitions of table SUPERMAG.SASTOREPROPDEFVAL have been marked unusable
Fri Jun 10 10:32:46 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCUSTOMLABELSVAL have been marked unusable
Fri Jun 10 10:32:57 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMDOCLABELS have been marked unusable
Fri Jun 10 10:33:12 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCUSTOMLABELS have been marked unusable
Fri Jun 10 10:33:58 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMSTOREUNITS have been marked unusable
Fri Jun 10 11:01:30 2011
Thread 1 advanced to log sequence 208 (LGWR switch)
  Current log# 1 seq# 208 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO01.LOG
Fri Jun 10 11:01:44 2011
alter tablespace "INDX" coalesce
Fri Jun 10 11:01:44 2011
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 11:01:44 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 11:01:45 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 11:01:46 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 11:02:22 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 11:03:09 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMASSORTMATRIXHIST have been marked unusable
Fri Jun 10 11:04:31 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCONTRACTPACKS have been marked unusable
Fri Jun 10 11:32:46 2011
alter tablespace "INDX" coalesce
Fri Jun 10 11:32:46 2011
Completed: alter tablespace "INDX" coalesce
Fri Jun 10 11:32:47 2011
alter tablespace "SYSAUX" coalesce
Completed: alter tablespace "SYSAUX" coalesce
Fri Jun 10 11:32:48 2011
alter tablespace "SYSTEM" coalesce
Completed: alter tablespace "SYSTEM" coalesce
Fri Jun 10 11:32:49 2011
alter tablespace "USERS" coalesce
Completed: alter tablespace "USERS" coalesce
Fri Jun 10 11:33:28 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 11:34:59 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMSTDOFFICERS have been marked unusable
Dump file c:\oracle\product\10.2.0\admin\balbepav\bdump\alert_balbepav.log
Fri Jun 10 13:29:20 2011
ORACLE V10.2.0.4.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU                 : 4 - type 586, 4 Physical Cores
Process Affinity    : 0x00000000
Memory (Avail/Total): Ph:7603M/8191M, Ph+PgF:11663M/12085M, VA:1913M/2047M
Fri Jun 10 13:29:20 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on. 
IMODE=BR
ILAT =18
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                = 150
  timed_statistics         = TRUE
  __shared_pool_size       = 377487360
  __large_pool_size        = 4194304
  __java_pool_size         = 4194304
  __streams_pool_size      = 0
  trace_enabled            = FALSE
  sga_target               = 612368384
  control_files            = C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\CONTROL01.CTL, C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\CONTROL02.CTL, C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\CONTROL03.CTL
  db_block_size            = 8192
  __db_cache_size          = 218103808
  compatible               = 10.2.0.3.0
  db_recovery_file_dest    = C:\Backup_ora
  db_recovery_file_dest_size= 37580963840
  fast_start_mttr_target   = 600
  transactions_per_rollback_segment= 1
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  undo_retention           = 28800
  recyclebin               = off
  O7_DICTIONARY_ACCESSIBILITY= TRUE
  remote_login_passwordfile= EXCLUSIVE
  audit_sys_operations     = FALSE
  db_domain                = 
  dispatchers              = (PROTOCOL=TCP) (SERVICE=BALBEPAVXDB)
  job_queue_processes      = 10
  audit_file_dest          = C:\ORACLE\PRODUCT\10.2.0\ADMIN\BALBEPAV\ADUMP
  background_dump_dest     = C:\ORACLE\PRODUCT\10.2.0\ADMIN\BALBEPAV\BDUMP
  user_dump_dest           = C:\ORACLE\PRODUCT\10.2.0\ADMIN\BALBEPAV\UDUMP
  max_dump_file_size       = 5000000
  core_dump_dest           = C:\ORACLE\PRODUCT\10.2.0\ADMIN\BALBEPAV\CDUMP
  commit_write             = batch,nowait
  optimizer_features_enable= 10.2.0.4
  audit_trail              = XML
  db_name                  = BALBEPAV
  open_cursors             = 300
  query_rewrite_integrity  = stale_tolerated
  pga_aggregate_target     = 203423744
  optimizer_dynamic_sampling= 2
PMON started with pid=2, OS id=3524
PSP0 started with pid=3, OS id=3528
MMAN started with pid=4, OS id=3532
DBW0 started with pid=5, OS id=3536
LGWR started with pid=6, OS id=3540
CKPT started with pid=7, OS id=3544
SMON started with pid=8, OS id=3548
RECO started with pid=9, OS id=3552
CJQ0 started with pid=10, OS id=3556
MMON started with pid=11, OS id=3560
Fri Jun 10 13:29:21 2011
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Fri Jun 10 13:29:21 2011
starting up 1 shared server(s) ...
Fri Jun 10 13:29:21 2011
alter database mount exclusive
MMNL started with pid=12, OS id=3564
Fri Jun 10 13:29:25 2011
Setting recovery target incarnation to 1
Fri Jun 10 13:29:26 2011
Successful mount of redo thread 1, with mount id 2010787761
Fri Jun 10 13:29:26 2011
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Fri Jun 10 13:29:26 2011
alter database open
Fri Jun 10 13:29:26 2011
Beginning crash recovery of 1 threads
 parallel recovery started with 3 processes
Fri Jun 10 13:29:28 2011
Started redo scan
Fri Jun 10 13:29:28 2011
Completed redo scan
 14568 redo blocks read, 703 data blocks need recovery
Fri Jun 10 13:29:29 2011
Started redo application at
 Thread 1: logseq 208, block 38910
Fri Jun 10 13:29:29 2011
Recovery of Online Redo Log: Thread 1 Group 1 Seq 208 Reading mem 0
  Mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO01.LOG
Fri Jun 10 13:29:29 2011
Completed redo application
Fri Jun 10 13:29:29 2011
Completed crash recovery at
 Thread 1: logseq 208, block 53478, scn 2697180
 703 data blocks read, 703 data blocks written, 14568 redo blocks read
Fri Jun 10 13:29:30 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=20, OS id=356
ARC1 started with pid=21, OS id=352
Fri Jun 10 13:29:30 2011
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
Fri Jun 10 13:29:31 2011
Thread 1 advanced to log sequence 209 (thread open)
Thread 1 opened at log sequence 209
  Current log# 2 seq# 209 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO02.LOG
Successful open of redo thread 1
Fri Jun 10 13:29:31 2011
SMON: enabling cache recovery
Fri Jun 10 13:29:31 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Fri Jun 10 13:29:31 2011
ARC1: Becoming the heartbeat ARCH
Fri Jun 10 13:29:31 2011
db_recovery_file_dest_size of 35840 MB is 3.78% 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 Jun 10 13:29:35 2011
Successfully onlined Undo Tablespace 1.
Fri Jun 10 13:29:35 2011
SMON: enabling tx recovery
Fri Jun 10 13:29:35 2011
Database Characterset is CL8MSWIN1251
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 4
Fri Jun 10 13:29:36 2011
SMON: Parallel transaction recovery tried
Fri Jun 10 13:29:37 2011
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=26, OS id=3620
Fri Jun 10 13:29:44 2011
Completed: alter database open
Fri Jun 10 13:36:54 2011
ALTER SYSTEM SET optimizer_mode='FIRST_ROWS_100' SCOPE=MEMORY;
Fri Jun 10 13:36:55 2011
ALTER SYSTEM SET db_recovery_file_dest_size='1507374182400' SCOPE=MEMORY;
Fri Jun 10 13:36:56 2011
ALTER SYSTEM SET optimizer_index_cost_adj=50 SCOPE=MEMORY;
Fri Jun 10 13:36:56 2011
ALTER SYSTEM SET optimizer_index_caching=60 SCOPE=MEMORY;
Dump file c:\oracle\product\10.2.0\admin\balbepav\bdump\alert_balbepav.log
Fri Jun 10 17:08:23 2011
ORACLE V10.2.0.4.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU                 : 4 - type 586, 4 Physical Cores
Process Affinity    : 0x00000000
Memory (Avail/Total): Ph:7622M/8191M, Ph+PgF:11663M/12085M, VA:1913M/2047M
Fri Jun 10 17:08:23 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on. 
IMODE=BR
ILAT =18
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                = 150
  timed_statistics         = TRUE
  __shared_pool_size       = 377487360
  __large_pool_size        = 4194304
  __java_pool_size         = 4194304
  __streams_pool_size      = 0
  trace_enabled            = FALSE
  sga_target               = 612368384
  control_files            = C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\CONTROL01.CTL, C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\CONTROL02.CTL, C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\CONTROL03.CTL
  db_block_size            = 8192
  __db_cache_size          = 218103808
  compatible               = 10.2.0.3.0
  db_recovery_file_dest    = C:\Backup_ora
  db_recovery_file_dest_size= 37580963840
  fast_start_mttr_target   = 600
  transactions_per_rollback_segment= 1
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  undo_retention           = 28800
  recyclebin               = off
  O7_DICTIONARY_ACCESSIBILITY= TRUE
  remote_login_passwordfile= EXCLUSIVE
  audit_sys_operations     = FALSE
  db_domain                = 
  dispatchers              = (PROTOCOL=TCP) (SERVICE=BALBEPAVXDB)
  job_queue_processes      = 10
  audit_file_dest          = C:\ORACLE\PRODUCT\10.2.0\ADMIN\BALBEPAV\ADUMP
  background_dump_dest     = C:\ORACLE\PRODUCT\10.2.0\ADMIN\BALBEPAV\BDUMP
  user_dump_dest           = C:\ORACLE\PRODUCT\10.2.0\ADMIN\BALBEPAV\UDUMP
  max_dump_file_size       = 5000000
  core_dump_dest           = C:\ORACLE\PRODUCT\10.2.0\ADMIN\BALBEPAV\CDUMP
  commit_write             = batch,nowait
  optimizer_features_enable= 10.2.0.4
  audit_trail              = XML
  db_name                  = BALBEPAV
  open_cursors             = 300
  query_rewrite_integrity  = stale_tolerated
  pga_aggregate_target     = 203423744
  optimizer_dynamic_sampling= 2
PMON started with pid=2, OS id=1616
PSP0 started with pid=3, OS id=1552
MMAN started with pid=4, OS id=2680
DBW0 started with pid=5, OS id=2844
CJQ0 started with pid=10, OS id=3240
MMON started with pid=11, OS id=3244
Fri Jun 10 17:08:31 2011
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Fri Jun 10 17:08:31 2011
starting up 1 shared server(s) ...
LGWR started with pid=6, OS id=2856
SMON started with pid=8, OS id=3148
RECO started with pid=9, OS id=3152
MMNL started with pid=12, OS id=3236
CKPT started with pid=7, OS id=3124
Fri Jun 10 17:08:33 2011
alter database mount exclusive
Fri Jun 10 17:08:37 2011
Setting recovery target incarnation to 1
Fri Jun 10 17:08:37 2011
Successful mount of redo thread 1, with mount id 2010858769
Fri Jun 10 17:08:37 2011
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Fri Jun 10 17:08:37 2011
alter database open
Fri Jun 10 17:08:37 2011
Beginning crash recovery of 1 threads
 parallel recovery started with 3 processes
Fri Jun 10 17:08:38 2011
Started redo scan
Fri Jun 10 17:08:38 2011
Completed redo scan
 712 redo blocks read, 131 data blocks need recovery
Fri Jun 10 17:08:38 2011
Started redo application at
 Thread 1: logseq 209, block 77330
Fri Jun 10 17:08:38 2011
Recovery of Online Redo Log: Thread 1 Group 2 Seq 209 Reading mem 0
  Mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO02.LOG
Fri Jun 10 17:08:38 2011
Completed redo application
Fri Jun 10 17:08:39 2011
Completed crash recovery at
 Thread 1: logseq 209, block 78042, scn 2737779
 131 data blocks read, 131 data blocks written, 712 redo blocks read
Fri Jun 10 17:08:39 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=19, OS id=3320
ARC1 started with pid=20, OS id=3312
Fri Jun 10 17:08:39 2011
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
Fri Jun 10 17:08:39 2011
Thread 1 advanced to log sequence 210 (thread open)
Thread 1 opened at log sequence 210
  Current log# 3 seq# 210 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO03.LOG
Successful open of redo thread 1
Fri Jun 10 17:08:40 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Fri Jun 10 17:08:40 2011
ARC1: Becoming the heartbeat ARCH
db_recovery_file_dest_size of 35840 MB is 3.89% 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 Jun 10 17:08:41 2011
SMON: enabling cache recovery
Fri Jun 10 17:08:44 2011
Successfully onlined Undo Tablespace 1.
Fri Jun 10 17:08:44 2011
SMON: enabling tx recovery
Fri Jun 10 17:08:44 2011
Database Characterset is CL8MSWIN1251
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 4
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=21, OS id=3388
Fri Jun 10 17:08:51 2011
Completed: alter database open
Fri Jun 10 17:13:53 2011
ALTER SYSTEM SET optimizer_mode='FIRST_ROWS_100' SCOPE=MEMORY;
Fri Jun 10 17:13:53 2011
ALTER SYSTEM SET db_recovery_file_dest_size='1507374182400' SCOPE=MEMORY;
Fri Jun 10 17:13:54 2011
ALTER SYSTEM SET optimizer_index_cost_adj=50 SCOPE=MEMORY;
Fri Jun 10 17:13:55 2011
ALTER SYSTEM SET optimizer_index_caching=60 SCOPE=MEMORY;
Fri Jun 10 17:32:14 2011
Thread 1 advanced to log sequence 211 (LGWR switch)
  Current log# 1 seq# 211 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO01.LOG
Fri Jun 10 17:52:04 2011
Thread 1 advanced to log sequence 212 (LGWR switch)
  Current log# 2 seq# 212 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO02.LOG
Fri Jun 10 18:07:20 2011
Thread 1 advanced to log sequence 213 (LGWR switch)
  Current log# 3 seq# 213 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO03.LOG
Fri Jun 10 18:27:27 2011
Thread 1 advanced to log sequence 214 (LGWR switch)
  Current log# 1 seq# 214 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO01.LOG
Fri Jun 10 18:47:38 2011
Thread 1 advanced to log sequence 215 (LGWR switch)
  Current log# 2 seq# 215 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO02.LOG
Fri Jun 10 19:03:14 2011
Thread 1 advanced to log sequence 216 (LGWR switch)
  Current log# 3 seq# 216 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO03.LOG
Fri Jun 10 19:23:35 2011
Thread 1 advanced to log sequence 217 (LGWR switch)
  Current log# 1 seq# 217 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO01.LOG
Fri Jun 10 19:43:38 2011
Thread 1 advanced to log sequence 218 (LGWR switch)
  Current log# 2 seq# 218 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO02.LOG
Fri Jun 10 19:59:33 2011
Thread 1 advanced to log sequence 219 (LGWR switch)
  Current log# 3 seq# 219 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO03.LOG
Fri Jun 10 20:19:35 2011
Thread 1 advanced to log sequence 220 (LGWR switch)
  Current log# 1 seq# 220 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO01.LOG
Fri Jun 10 20:34:11 2011
Thread 1 advanced to log sequence 221 (LGWR switch)
  Current log# 2 seq# 221 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\BALBEPAV\REDO
10.06.2011 16:26
Dim
 
я бы в первую очередь прогнал оптимайзер...
10.06.2011 16:29
VitorJ
 
Работает как и положено, запускается переодический прогоняет базу.
10.06.2011 16:30
Mtirt
 
Цитата:
Some indexes or index [sub]partitions of table SUPERMAG.SSLOCKS have been marked unusable
Fri Jun 10 07:56:21 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTVIRTPACKS have been marked unusable
Fri Jun 10 07:56:54 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTFAILRPDATA have been marked unusable
Fri Jun 10 07:57:04 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTPARAM have been marked unusable
Fri Jun 10 07:57:37 2011
Some indexes or index [sub]partitions of table SUPERMAG.SADOMAINSCLASS have been marked unusable
Fri Jun 10 07:57:50 2011
Some indexes or index [sub]partitions of table SUPERMAG.SAANALYTICSFIELDS have been marked unusable
Fri Jun 10 07:58:03 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCALCERLINKS have been marked unusable
Fri Jun 10 07:58:13 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCALCERCELLS have been marked unusable
Fri Jun 10 07:58:23 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMCALCERBASICGRAPHS have been marked unusable
Fri Jun 10 07:58:33 2011
Some indexes or index [sub]partitions of table SUPERMAG.SSSUGGESTORDERALG have been marked unusable
Fri Jun 10 07:59:08 2011
Some indexes or index [sub]partitions of table SUPERMAG.SMPOSTRULES have been marked unusable
Вот из-за этого легко может не отбираться.
Я тоже за оптимайзер.
10.06.2011 16:36
Dim
 
а мейнтенс тайм есть?

select * from olegon_params where name='MaintenanceTime' что говорит?
10.06.2011 16:47
VitorJ
 
Цитата:
select * from olegon_params where name='MaintenanceTime'
MaintenanceTime
23:30,8
10.06.2011 16:51
VitorJ
 
Может пересоздать индексы?
10.06.2011 18:16
Dim
 
а в логе оптимайзера ничего подозрительного нет?
11.06.2011 05:28
VitorJ
 
В логах отимайзера ничего подозрительного пока не увидел
13.06.2011 12:53
John Doe
 
я бы структуру БД проверил. какие-то непонятные объекты моргают в логах...
14.06.2011 04:44
VitorJ
 
Каким образом???? Если стандартными средствами Супермаг сделано ничего не сказал, вроде всё ГУД.
14.06.2011 05:30
VitorJ
 
Вот что говорит запрос
Код:
SQL>  select * from supermag.SMDOCUMENTS where ID='NZ20101129@6';

DO ID
-- --------------------------------------------------
BORNIN                           CREATEDA   DOCSTATE     OPCODE     USEROP
-------------------------------- -------- ---------- ---------- ----------
CLIENTINDEX LOCATIONFROM LOCATIONTO   LOCATION CURRENCYTYPE CURRENCYRATE
----------- ------------ ---------- ---------- ------------ ------------
CURRENCYMULTORDER   TOTALSUM TOTALSUMCUR PRICEROUNDMODE I
----------------- ---------- ----------- -------------- -
COMMENTARY
--------------------------------------------------------------------------------
CS NZ20101129@6
F538F75C841644EEA1AE85A14F85FF8D 29.11.10          1          1
                       6                                  1            1

DO ID
-- --------------------------------------------------
BORNIN                           CREATEDA   DOCSTATE     OPCODE     USEROP
-------------------------------- -------- ---------- ---------- ----------
CLIENTINDEX LOCATIONFROM LOCATIONTO   LOCATION CURRENCYTYPE CURRENCYRATE
----------- ------------ ---------- ---------- ------------ ------------
CURRENCYMULTORDER   TOTALSUM TOTALSUMCUR PRICEROUNDMODE I
----------------- ---------- ----------- -------------- -
COMMENTARY
--------------------------------------------------------------------------------
                0     1800,5      1800,5              3 1
14.06.2011 05:32
VitorJ
 
На самом деле сумма продажи в ЦО 1384.5
14.06.2011 07:18
Mtirt
 
А тоже самое из ЦО?
14.06.2011 07:41
VitorJ
 
Вот из ЦО
Код:
SQL> select * from supermag.SMDOCUMENTS where ID='NZ20101129@6';

DO ID
-- --------------------------------------------------
BORNIN                           CREATEDA   DOCSTATE     OPCODE     USEROP
-------------------------------- -------- ---------- ---------- ----------
CLIENTINDEX LOCATIONFROM LOCATIONTO   LOCATION CURRENCYTYPE CURRENCYRATE
----------- ------------ ---------- ---------- ------------ ------------
CURRENCYMULTORDER   TOTALSUM TOTALSUMCUR PRICEROUNDMODE I
----------------- ---------- ----------- -------------- -
COMMENTARY
--------------------------------------------------------------------------------
CS NZ20101129@6
81F37629EE974DADB88CF558BF056AE0 29.11.10          3          1
                       6                                  1            1

DO ID
-- --------------------------------------------------
BORNIN                           CREATEDA   DOCSTATE     OPCODE     USEROP
-------------------------------- -------- ---------- ---------- ----------
CLIENTINDEX LOCATIONFROM LOCATIONTO   LOCATION CURRENCYTYPE CURRENCYRATE
----------- ------------ ---------- ---------- ------------ ------------
CURRENCYMULTORDER   TOTALSUM TOTALSUMCUR PRICEROUNDMODE I
----------------- ---------- ----------- -------------- -
COMMENTARY
--------------------------------------------------------------------------------
                0     1384,5      1384,5              3 1
14.06.2011 08:04
Mtirt
 
Разные ID баз создания документа: F538F75C841644EEA1AE85A14F85FF8D и 81F37629EE974DADB88CF558BF056AE0.

Интересно мне, о чем думала тех поддержка, когда предлагала тебе пересоздать базу...

Я бы удалила в ЦО, пересоздала документы в магазине и удостоверилась в том, что они поднялись в ЦО.
А потом бы еще и долго и мучительно проверяла документы других типов :(

Второй вопрос, почему суммы документов разные.
Что используется в качестве фронт-офиса? Кассовой программы?


Опции темы


Часовой пояс GMT +3, время: 23:26.

 

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