Bugs item #2929830, was opened at 2010-01-11 14:10
Message generated for change (Comment added) made by userbob99
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2929830&group_id=129076

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: Sedna (current)
Status: Open
Resolution: Accepted
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Ivan Shcheklein (shcheklein)
Summary: Sedna Database Unable to start 3.1

Initial Comment:
Hi, the attached DB is unable to start i have attached the logs entries and the 
exception is a standard windows exception which initially crashed on se_sm and 
now crashes se_rcv.



----------------------------------------------------------------------

Comment By: Richard Holt (userbob99)
Date: 2010-01-11 15:26

Message:
the last event log file is below. i cannot seem to attach more artifacts to
this call

INFO  11/01/2010 14:01:10 (GOV pid=4764) [gov.cpp:main:231]: SEDNA version
is 3.1.175
INFO  11/01/2010 14:01:10 (GOV pid=4764)
[gov_functions.cpp:log_out_system_information:79]: System: Windows 6.0.6002
(SP2.0) x86
INFO  11/01/2010 14:01:10 (GOV pid=4764)
[gmm.cpp:create_global_memory_mapping:129]: Layer address space start addr
= 0x22380000
INFO  11/01/2010 14:01:10 (GOV pid=4764)
[gmm.cpp:create_global_memory_mapping:130]: Layer address space boundary  
= 0x62380000
INFO  11/01/2010 14:01:10 (GOV pid=4764)
[gmm.cpp:create_global_memory_mapping:131]: Persistent heap start addr    
= 0x1bf80000
LOG   11/01/2010 14:01:10 (GOV pid=4764) [gov.cpp:main:240]: Process ping
server is ready
LOG   11/01/2010 14:01:10 (GOV pid=4764)
[listener.cpp:client_listener:67]: GOVERNOR is ready
LOG   11/01/2010 14:01:14 (SM vision_xchange pid=5020) [sm.cpp:main:547]:
Event log is ready
LOG   11/01/2010 14:01:14 (SM vision_xchange pid=5020) [sm.cpp:main:560]:
Ping client has been started
LOG   11/01/2010 14:01:14 (SM vision_xchange pid=5020) [sm.cpp:main:566]:
VMM region values determined
SYS   11/01/2010 14:01:14 (SM vision_xchange pid=5020)
[uprocess.c:uGetEnvironmentVariable:67]: GetEnvironmentVariable (code =
203): The system could not find the environment option that was entered.
SYS   11/01/2010 14:01:14 (SM vision_xchange pid=5020)
[uprocess.c:uGetEnvironmentVariable:67]: GetEnvironmentVariable (code =
203): The system could not find the environment option that was entered.
LOG   11/01/2010 14:01:14 (SM vision_xchange pid=5020)
[sm.cpp:recover_database_by_physical_and_logical_log:830]: Event log in
recovery procedure is ready
LOG   11/01/2010 14:01:14 (SM vision_xchange pid=5020)
[sm.cpp:recover_database_by_physical_and_logical_log:834]:
init_transaction_ids_table done
LOG   11/01/2010 14:01:14 (SM vision_xchange pid=5020)
[sm.cpp:recover_database_by_physical_and_logical_log:838]:
init_checkpoint_sems done
LOG   11/01/2010 14:01:15 (SM vision_xchange pid=5020)
[sm.cpp:recover_database_by_physical_and_logical_log:844]: Logical log is
started
LOG   11/01/2010 14:01:16 (SM vision_xchange pid=5020)
[sm.cpp:recover_database_by_physical_and_logical_log:859]: Persistent heap
has been recovered
LOG   11/01/2010 14:01:16 (SM vision_xchange pid=5020)
[sm.cpp:recover_database_by_physical_and_logical_log:864]:
start_chekpoint_thread done
LOG   11/01/2010 14:01:22 (SM vision_xchange pid=5020)
[sm.cpp:recover_database_by_physical_and_logical_log:886]: Buffer manager
is started
LOG   11/01/2010 14:03:09 (SM vision_xchange pid=5020)
[blk_mngmt.cpp:extend_tmp_file:619]: Temp file has been extended, size:
6400000
LOG   11/01/2010 14:03:09 (SM vision_xchange pid=5020)
[sm.cpp:recover_database_by_physical_and_logical_log:893]: Database has
been recovered by physical log successfully
LOG   11/01/2010 14:03:09 (SM vision_xchange pid=5020)
[sm.cpp:recover_database_by_physical_and_logical_log:898]: Checkpoints are
disabled
LOG   11/01/2010 14:03:09 (SM vision_xchange pid=5020)
[sm.cpp:recover_database_by_physical_and_logical_log:902]:
lm_table.init_lock_table done
LOG   11/01/2010 14:03:10 (SM vision_xchange pid=5020)
[sm.cpp:recover_database_by_physical_and_logical_log:925]: Wu is
initialized
LOG   11/01/2010 14:03:10 (UNK vision_xchange pid=5640)
[rcv_db.cpp:TRmain:81]: recovery process by logical log started


----------------------------------------------------------------------

Comment By: Ivan Shcheklein (shcheklein)
Date: 2010-01-11 15:08

Message:
Hi Richard,

Unfortunatelly, I don't know what we can do in this situation. Can you
send us event log files at least? Do you have backups of your data? Is this
issue reproducible?

----------------------------------------------------------------------

Comment By: Richard Holt (userbob99)
Date: 2010-01-11 14:18

Message:
se_gov starts correctly and when running se_sm against the db either se_sm
or se_rcv crashes.

i am unable to access the db therefore to export the data

----------------------------------------------------------------------

Comment By: Richard Holt (userbob99)
Date: 2010-01-11 14:17

Message:
unfortunately i am unable to upload the appropriate data as it contains
customer data.

attached is 1 log 

the other from SM5020.log is 

SEDNA soft fault message:
SEDNA GOVERNOR is down
SM command line arguments: C:\Development\Tools\sedna\bin\se_sm.exe
vision_xchange

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2929830&group_id=129076

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Sedna-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sedna-discussion

Reply via email to