Forum Orisinil
OtomaX - Orisinil Topup Machine => Tips dan Trik => Topic started by: Yusuf on September 11, 2010, 10:09:31 AM
-
Ini ada sumbangan dari rekan kita yg sudah mengalaminya:
Untuk memperbaiki database yg suspect, jalankan perintah-perintah ini pada Query Analyzer atau SQL Server Management Studio:
EXEC sp_resetstatus ‘yourDBname’;
ALTER DATABASE yourDBname SET EMERGENCY
DBCC checkdb(‘yourDBname’)
ALTER DATABASE yourDBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (‘yourDBname’, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE yourDBname SET MULTI_USER
Sumber: http://gargmanoj.wordpress.com/2008/07/17/how-to-repair-a-sql-server-2005-suspect-database/
-
Mantab...
makasih BOS..
jadi nambah ilmu....
-
yourDBname diganti jadi otomax:
EXEC sp_resetstatus ‘otomax’;
ALTER DATABASE otomax SET EMERGENCY
DBCC checkdb(‘otomax’)
ALTER DATABASE otomax SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (‘otomax’, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE otomax SET MULTI_USER
-
Mantabbb BIG BOSS ;D ;D
bookmark dulu ahhh, belum ada kasus neehh
-
finally... berbagi uang, uang habis.... berbagi ilmu, ilmu nambah teruuss... ;D ;D
-
kok ndk bisa ya ???
replay nya
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near '‘'.
Msg 102, Level 15, State 1, Line 3
Incorrect syntax near '‘'.
Msg 102, Level 15, State 1, Line 5
Incorrect syntax near '‘'.
knp ya???
-
tanda ' nya coba bos hapus, ketik ulang...
-
The suspect flag on the database "otomax" is already reset.
DBCC results for 'Otomax'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
DBCC results for 'sys.sysrowsetcolumns'.
There are 834 rows in 8 pages for object "sys.sysrowsetcolumns".
DBCC results for 'sys.sysrowsets'.
There are 120 rows in 1 pages for object "sys.sysrowsets".
DBCC results for 'sysallocunits'.
There are 131 rows in 2 pages for object "sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
DBCC results for 'sys.syshobtcolumns'.
There are 834 rows in 10 pages for object "sys.syshobtcolumns".
DBCC results for 'sys.syshobts'.
There are 120 rows in 1 pages for object "sys.syshobts".
DBCC results for 'sys.sysftinds'.
There are 0 rows in 0 pages for object "sys.sysftinds".
DBCC results for 'sys.sysserefs'.
There are 131 rows in 1 pages for object "sys.sysserefs".
DBCC results for 'sys.sysowners'.
There are 14 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysprivs'.
There are 120 rows in 1 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 166 rows in 4 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 663 rows in 12 pages for object "sys.syscolpars".
DBCC results for 'sys.sysnsobjs'.
There are 1 rows in 1 pages for object "sys.sysnsobjs".
DBCC results for 'sys.syscerts'.
There are 0 rows in 0 pages for object "sys.syscerts".
DBCC results for 'sys.sysxprops'.
There are 1 rows in 1 pages for object "sys.sysxprops".
DBCC results for 'sys.sysscalartypes'.
There are 27 rows in 1 pages for object "sys.sysscalartypes".
DBCC results for 'sys.systypedsubobjs'.
There are 0 rows in 0 pages for object "sys.systypedsubobjs".
DBCC results for 'sys.sysidxstats'.
There are 332 rows in 6 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 465 rows in 3 pages for object "sys.sysiscols".
DBCC results for 'sys.sysbinobjs'.
There are 23 rows in 1 pages for object "sys.sysbinobjs".
DBCC results for 'sys.sysobjvalues'.
There are 393 rows in 118 pages for object "sys.sysobjvalues".
DBCC results for 'sys.sysclsobjs'.
There are 14 rows in 1 pages for object "sys.sysclsobjs".
DBCC results for 'sys.sysrowsetrefs'.
There are 0 rows in 0 pages for object "sys.sysrowsetrefs".
DBCC results for 'sys.sysremsvcbinds'.
There are 0 rows in 0 pages for object "sys.sysremsvcbinds".
DBCC results for 'sys.sysxmitqueue'.
There are 0 rows in 0 pages for object "sys.sysxmitqueue".
DBCC results for 'sys.sysrts'.
There are 1 rows in 1 pages for object "sys.sysrts".
DBCC results for 'sys.sysconvgroup'.
There are 0 rows in 0 pages for object "sys.sysconvgroup".
DBCC results for 'sys.sysdesend'.
There are 0 rows in 0 pages for object "sys.sysdesend".
DBCC results for 'sys.sysdercv'.
There are 0 rows in 0 pages for object "sys.sysdercv".
DBCC results for 'sys.syssingleobjrefs'.
There are 157 rows in 1 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 105 rows in 1 pages for object "sys.sysmultiobjrefs".
DBCC results for 'sys.sysdbfiles'.
There are 2 rows in 1 pages for object "sys.sysdbfiles".
DBCC results for 'sys.sysguidrefs'.
There are 0 rows in 0 pages for object "sys.sysguidrefs".
DBCC results for 'sys.sysqnames'.
There are 91 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 93 rows in 1 pages for object "sys.sysxmlcomponent".
DBCC results for 'sys.sysxmlfacet'.
There are 97 rows in 1 pages for object "sys.sysxmlfacet".
DBCC results for 'sys.sysxmlplacement'.
There are 17 rows in 1 pages for object "sys.sysxmlplacement".
DBCC results for 'sys.sysobjkeycrypts'.
There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".
DBCC results for 'sys.sysasymkeys'.
There are 0 rows in 0 pages for object "sys.sysasymkeys".
DBCC results for 'sys.syssqlguides'.
There are 0 rows in 0 pages for object "sys.syssqlguides".
DBCC results for 'sys.sysbinsubobjs'.
There are 0 rows in 0 pages for object "sys.sysbinsubobjs".
DBCC results for 'jawaban'.
There are 124 rows in 2 pages for object "jawaban".
DBCC results for 'transaksi'.
There are 1794961 rows in 45225 pages for object "transaksi".
DBCC results for 'mutasi'.
There are 3054402 rows in 33120 pages for object "mutasi".
DBCC results for 'parameter'.
There are 210 rows in 3 pages for object "parameter".
DBCC results for 'pengirim'.
There are 765 rows in 4 pages for object "pengirim".
DBCC results for 'produk'.
There are 129 rows in 1 pages for object "produk".
DBCC results for 'sms_sender'.
There are 2 rows in 1 pages for object "sms_sender".
DBCC results for 'operator'.
There are 15 rows in 1 pages for object "operator".
DBCC results for 'inbox'.
There are 6880967 rows in 127211 pages for object "inbox".
DBCC results for 'terminal'.
There are 33 rows in 1 pages for object "terminal".
DBCC results for 'biaya'.
There are 63 rows in 1 pages for object "biaya".
DBCC results for 'tiket_deposit'.
There are 24463 rows in 138 pages for object "tiket_deposit".
DBCC results for 'data_bank'.
There are 24693 rows in 386 pages for object "data_bank".
DBCC results for 'level'.
There are 20 rows in 1 pages for object "level".
DBCC results for 'komisi'.
There are 172 rows in 1 pages for object "komisi".
DBCC results for 'hlr'.
There are 1 rows in 1 pages for object "hlr".
DBCC results for 'log_sistem'.
There are 82605 rows in 1239 pages for object "log_sistem".
DBCC results for 'sms_center'.
There are 19 rows in 1 pages for object "sms_center".
DBCC results for 'produk_level'.
There are 144 rows in 1 pages for object "produk_level".
DBCC results for 'outbox'.
There are 7238473 rows in 169880 pages for object "outbox".
DBCC results for 'parsing'.
There are 268 rows in 6 pages for object "parsing".
DBCC results for 'modul'.
There are 41 rows in 1 pages for object "modul".
DBCC results for 'reseller'.
There are 392 rows in 7 pages for object "reseller".
DBCC results for 'sys.queue_messages_1977058079'.
There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".
DBCC results for 'sys.queue_messages_2009058193'.
There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".
DBCC results for 'sys.queue_messages_2041058307'.
There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".
DBCC results for 'fisik'.
There are 60 rows in 1 pages for object "fisik".
DBCC results for 'auto_respon'.
There are 14 rows in 1 pages for object "auto_respon".
CHECKDB found 0 allocation errors and 0 consistency errors in database 'Otomax'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
DBCC results for 'Otomax'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
DBCC results for 'sys.sysrowsetcolumns'.
There are 834 rows in 8 pages for object "sys.sysrowsetcolumns".
DBCC results for 'sys.sysrowsets'.
There are 120 rows in 1 pages for object "sys.sysrowsets".
DBCC results for 'sysallocunits'.
There are 131 rows in 2 pages for object "sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
DBCC results for 'sys.syshobtcolumns'.
There are 834 rows in 10 pages for object "sys.syshobtcolumns".
DBCC results for 'sys.syshobts'.
There are 120 rows in 1 pages for object "sys.syshobts".
DBCC results for 'sys.sysftinds'.
There are 0 rows in 0 pages for object "sys.sysftinds".
DBCC results for 'sys.sysserefs'.
There are 131 rows in 1 pages for object "sys.sysserefs".
DBCC results for 'sys.sysowners'.
There are 14 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysprivs'.
There are 120 rows in 1 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 166 rows in 4 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 663 rows in 12 pages for object "sys.syscolpars".
DBCC results for 'sys.sysnsobjs'.
There are 1 rows in 1 pages for object "sys.sysnsobjs".
DBCC results for 'sys.syscerts'.
There are 0 rows in 0 pages for object "sys.syscerts".
DBCC results for 'sys.sysxprops'.
There are 1 rows in 1 pages for object "sys.sysxprops".
DBCC results for 'sys.sysscalartypes'.
There are 27 rows in 1 pages for object "sys.sysscalartypes".
DBCC results for 'sys.systypedsubobjs'.
There are 0 rows in 0 pages for object "sys.systypedsubobjs".
DBCC results for 'sys.sysidxstats'.
There are 332 rows in 6 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 465 rows in 3 pages for object "sys.sysiscols".
DBCC results for 'sys.sysbinobjs'.
There are 23 rows in 1 pages for object "sys.sysbinobjs".
DBCC results for 'sys.sysobjvalues'.
There are 393 rows in 118 pages for object "sys.sysobjvalues".
DBCC results for 'sys.sysclsobjs'.
There are 14 rows in 1 pages for object "sys.sysclsobjs".
DBCC results for 'sys.sysrowsetrefs'.
There are 0 rows in 0 pages for object "sys.sysrowsetrefs".
DBCC results for 'sys.sysremsvcbinds'.
There are 0 rows in 0 pages for object "sys.sysremsvcbinds".
DBCC results for 'sys.sysxmitqueue'.
There are 0 rows in 0 pages for object "sys.sysxmitqueue".
DBCC results for 'sys.sysrts'.
There are 1 rows in 1 pages for object "sys.sysrts".
DBCC results for 'sys.sysconvgroup'.
There are 0 rows in 0 pages for object "sys.sysconvgroup".
DBCC results for 'sys.sysdesend'.
There are 0 rows in 0 pages for object "sys.sysdesend".
DBCC results for 'sys.sysdercv'.
There are 0 rows in 0 pages for object "sys.sysdercv".
DBCC results for 'sys.syssingleobjrefs'.
There are 157 rows in 1 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 105 rows in 1 pages for object "sys.sysmultiobjrefs".
DBCC results for 'sys.sysdbfiles'.
There are 2 rows in 1 pages for object "sys.sysdbfiles".
DBCC results for 'sys.sysguidrefs'.
There are 0 rows in 0 pages for object "sys.sysguidrefs".
DBCC results for 'sys.sysqnames'.
There are 91 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 93 rows in 1 pages for object "sys.sysxmlcomponent".
DBCC results for 'sys.sysxmlfacet'.
There are 97 rows in 1 pages for object "sys.sysxmlfacet".
DBCC results for 'sys.sysxmlplacement'.
There are 17 rows in 1 pages for object "sys.sysxmlplacement".
DBCC results for 'sys.sysobjkeycrypts'.
There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".
DBCC results for 'sys.sysasymkeys'.
There are 0 rows in 0 pages for object "sys.sysasymkeys".
DBCC results for 'sys.syssqlguides'.
There are 0 rows in 0 pages for object "sys.syssqlguides".
DBCC results for 'sys.sysbinsubobjs'.
There are 0 rows in 0 pages for object "sys.sysbinsubobjs".
DBCC results for 'jawaban'.
There are 124 rows in 2 pages for object "jawaban".
DBCC results for 'transaksi'.
There are 1794961 rows in 45225 pages for object "transaksi".
DBCC results for 'mutasi'.
There are 3054402 rows in 33120 pages for object "mutasi".
DBCC results for 'parameter'.
There are 210 rows in 3 pages for object "parameter".
DBCC results for 'pengirim'.
There are 765 rows in 4 pages for object "pengirim".
DBCC results for 'produk'.
There are 129 rows in 1 pages for object "produk".
DBCC results for 'sms_sender'.
There are 2 rows in 1 pages for object "sms_sender".
DBCC results for 'operator'.
There are 15 rows in 1 pages for object "operator".
DBCC results for 'inbox'.
There are 6880967 rows in 127211 pages for object "inbox".
DBCC results for 'terminal'.
There are 33 rows in 1 pages for object "terminal".
DBCC results for 'biaya'.
There are 63 rows in 1 pages for object "biaya".
DBCC results for 'tiket_deposit'.
There are 24463 rows in 138 pages for object "tiket_deposit".
DBCC results for 'data_bank'.
There are 24693 rows in 386 pages for object "data_bank".
DBCC results for 'level'.
There are 20 rows in 1 pages for object "level".
DBCC results for 'komisi'.
There are 172 rows in 1 pages for object "komisi".
DBCC results for 'hlr'.
There are 1 rows in 1 pages for object "hlr".
DBCC results for 'log_sistem'.
There are 82605 rows in 1239 pages for object "log_sistem".
DBCC results for 'sms_center'.
There are 19 rows in 1 pages for object "sms_center".
DBCC results for 'produk_level'.
There are 144 rows in 1 pages for object "produk_level".
DBCC results for 'outbox'.
There are 7238473 rows in 169880 pages for object "outbox".
DBCC results for 'parsing'.
There are 268 rows in 6 pages for object "parsing".
DBCC results for 'modul'.
There are 41 rows in 1 pages for object "modul".
DBCC results for 'reseller'.
There are 392 rows in 7 pages for object "reseller".
DBCC results for 'sys.queue_messages_1977058079'.
There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".
DBCC results for 'sys.queue_messages_2009058193'.
There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".
DBCC results for 'sys.queue_messages_2041058307'.
There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".
DBCC results for 'fisik'.
There are 60 rows in 1 pages for object "fisik".
DBCC results for 'auto_respon'.
There are 14 rows in 1 pages for object "auto_respon".
CHECKDB found 0 allocation errors and 0 consistency errors in database 'Otomax'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
kok ada error nya ya???
-
@ atasku
Memang ada pesan Error tapi sukses, suspect hilang
tested pada pasien
-
ikut liat perkembangan dolo..
-
Database Suspect apa ya ??? ???
kesini ga ngerti http://gargmanoj.wordpress.com/2008/07/17/how-to-repair-a-sql-server-2005-suspect-database/
maklum newbie jarang makan roti ;D
-
mohon dicek pak bigboss, beberapa kali benerin database otomax yg bermasalah ( terutama yg salah installan dari awal => maksudnya folder otomax.exe dan file .mdf / .ldf nya jadi satu folder), saya coba pake script ini, alhamdulillah sukses terus ;D,
USE master;
GO
ALTER DATABASE otomax SET EMERGENCY
GO
ALTER DATABASE otomax SET SINGLE_USER
GO
DBCC CHECKDB (otomax, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS;
GO
USE otomax;
DBCC CHECKDB WITH NO_INFOMSGS;
GO
USE otomax
ALTER DATABASE [otomax] SET RECOVERY SIMPLE
GO
DBCC SHRINKFILE ([otomax_log])
GO
ALTER DATABASE [otomax] SET RECOVERY FULL
DBCC SHRINKFILE (otomax, 1) WITH NO_INFOMSGS
ALTER DATABASE otomax SET MULTI_USER
kalo ada yg salah mohon dikoreksi ... maklum nubie
-
(http://img826.imageshack.us/img826/8869/incorrectl.jpg) (http://img826.imageshack.us/i/incorrectl.jpg/)
penyakitnya apa ya??
sudah coba semua trik di atas hasilnya masih nihil...
harus gimana ya ??? ??? ???
di tab Produk juga begitu...
-
oh iya, nambah produk juga ga mau
Mmmm Sepertinya kasus ini lumayan berat :( :( :(
didatabase sich ga ada indikasi suspect
Help me pleaseeeeee
-
case solved
dengan cara menghapus
(http://img524.imageshack.us/img524/6650/64306932.jpg) (http://img524.imageshack.us/i/64306932.jpg/)
;D ;D ;D
bagi yang mempunyai masaalah yang sama jangan lupa backup DB sebelum modifikasi tabel
-
finally... berbagi uang, uang habis.... berbagi ilmu, ilmu nambah teruuss... ;D ;D
Setuju...
new bie mw blajar dulu sama all big boss..
-
tolong bantuan nya bos
(http://i1193.photobucket.com/albums/aa360/uyan_kids/ERORQUERY1.jpg)
http://i1193.photobucket.com/albums/aa360/uyan_kids/ERORQUERY1.jpg (ftp://http://i1193.photobucket.com/albums/aa360/uyan_kids/ERORQUERY1.jpg)
-
tolong bantuan nya bos
(http://i1193.photobucket.com/albums/aa360/uyan_kids/ERORQUERY1.jpg)
http://i1193.photobucket.com/albums/aa360/uyan_kids/ERORQUERY1.jpg (ftp://http://i1193.photobucket.com/albums/aa360/uyan_kids/ERORQUERY1.jpg)
itu yang saya alami bos, tolong bantuan nya...help me
-
Ini ada sumbangan dari rekan kita yg sudah mengalaminya:
Untuk memperbaiki database yg suspect, jalankan perintah-perintah ini pada Query Analyzer atau SQL Server Management Studio:
EXEC sp_resetstatus ‘yourDBname’;
ALTER DATABASE yourDBname SET EMERGENCY
DBCC checkdb(‘yourDBname’)
ALTER DATABASE yourDBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (‘yourDBname’, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE yourDBname SET MULTI_USER
Sumber: http://gargmanoj.wordpress.com/2008/07/17/how-to-repair-a-sql-server-2005-suspect-database/
Nambah dikit...
(http://spaces.live.com/rte/emoticons/lightbulb.gif)
You should keep one thing in mind while using the above queries that the repair mode used here , REPAIR_ALLOW_DATA_LOSS, is a one way operation i.e. once the database is repaired all the actions performed by these queries can’t be undone. There is no way to go back to the previous state of the database. So as a precautionary step you should take backup of your database before executing above mentioned queries.
-
tanda ' nya coba bos hapus, ketik ulang...
pakai ini
EXEC sp_resetstatus ‘otomax’;
ALTER DATABASE otomax SET EMERGENCY
DBCC checkdb(‘otomax’)
ALTER DATABASE otomax SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (‘otomax’, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE otomax SET MULTI_USER
hasilnya :
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near '‘'.
Msg 102, Level 15, State 1, Line 3
Incorrect syntax near '‘'.
Msg 102, Level 15, State 1, Line 5
Incorrect syntax near '‘'.
saya udah coba hapus '
EXEC sp_resetstatus otomax;
ALTER DATABASE otomax SET EMERGENCY
BCC checkdb(otomax)
ALTER DATABASE otomax SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (otomax, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE otomax SET MULTI_USER
hasilnya
Msg 102, Level 15, State 6, Line 3
Incorrect syntax near 'checkdb'.
-
mohon dicek pak bigboss, beberapa kali benerin database otomax yg bermasalah ( terutama yg salah installan dari awal => maksudnya folder otomax.exe dan file .mdf / .ldf nya jadi satu folder), saya coba pake script ini, alhamdulillah sukses terus ;D,
saya coba jurus ini hasilnya
[attachment deleted by admin]
-
data basr suspect,, :'( :'( :'( help
-
Kok suspect lagi bos ?
bukankah beberapa hari lalu suspect juga ?
http://forum.orisinil.com/index.php?topic=1794.msg79113#msg79113
-
Kok suspect lagi bos ?
bukankah beberapa hari lalu suspect juga ?
http://forum.orisinil.com/index.php?topic=1794.msg79113#msg79113
mungkin perlu dikurangi akses ke database otomax selain aplikasi resmi dari orisinil
maaf kalau salah
-
harus ak coba nih, siapa tau format trx cek saldo ke donlen per RS bisa jadi normal.
-
apa betul prosesnya lama bgt ya mpe 20menit lebih lom slese
-
Kok suspect lagi bos ?
bukankah beberapa hari lalu suspect juga ?
http://forum.orisinil.com/index.php?topic=1794.msg79113#msg79113
database suspect beruntun,, 1hari 1x terjadi,, akhirnya sy coba ganti HD mudah2an tdk trjadi lagi.. amin..
-
data base suspect,, :'( :'( :'( help
-
Apa penyebab DB suspect yah ?????
ane alhamdulillah ga sampe ngalamin .karena tiap malam selalu rutin jalankan query DB suspect +reindex + Shrink .... Manual tanpa SW ;D biar ga lemmot .....
-
Apa penyebab DB suspect yah ?????
ane alhamdulillah ga sampe ngalamin .karena tiap malam selalu rutin jalankan query DB suspect +reindex + Shrink .... Manual tanpa SW ;D biar ga lemmot .....
sepenggal tulisan The Big Bos
" saya pribadi kesulitan kalo nemu kasus suspect. kesalahan yang umum adalah lepasnya link database ke file2 yang dibutuhkan. biasanya user lupa naruh file .mdf dan .ldfnya.
perlu diingat bahwa .mdf dan .ldf adalah sebuah pasangan yang ga bisa ditukar2 sembarangan.
namun kalo suspect karena hal lain, misal file corrupt. bingung juga. tool2 yg ada digoogle belum proven benar bisa menangani masalah tsb. maka dari itu tindakan pencegahan menjadi sangat penting, yaitu BACKUP.
tool2 untuk backup sudah sangat banyak. ada yg dr luar ada juga yg buatan para user otomax yg super kreatif. (salute)
beberapa tool terbukti mengganggu kinerja otomax krn sebab yg blm jelas. bbrp lagi aman. jadi hanya masalah pilah dan pilih.
coba pilih tool yang fungsinya hanya backup, tanpa memiliki akses lebih jauh seperti memonitor sql service apalagi sampai start/stop/restart service. start/stop/restart service sebaiknya dilakukan manual dari tools bawaan windows.
user harus rajin memelihara servernya. siapa yg rajin belajar dia yg jadi juara kelasnya. betul?
peace "
lengkapnya antum waos ewed http://forum.orisinil.com/index.php/topic,1794.msg79113.html#msg79113
-
sepenggal tulisan The Big Bos
" saya pribadi kesulitan kalo nemu kasus suspect. kesalahan yang umum adalah lepasnya link database ke file2 yang dibutuhkan. biasanya user lupa naruh file .mdf dan .ldfnya.
perlu diingat bahwa .mdf dan .ldf adalah sebuah pasangan yang ga bisa ditukar2 sembarangan.
namun kalo suspect karena hal lain, misal file corrupt. bingung juga. tool2 yg ada digoogle belum proven benar bisa menangani masalah tsb. maka dari itu tindakan pencegahan menjadi sangat penting, yaitu BACKUP.
tool2 untuk backup sudah sangat banyak. ada yg dr luar ada juga yg buatan para user otomax yg super kreatif. (salute)
beberapa tool terbukti mengganggu kinerja otomax krn sebab yg blm jelas. bbrp lagi aman. jadi hanya masalah pilah dan pilih.
coba pilih tool yang fungsinya hanya backup, tanpa memiliki akses lebih jauh seperti memonitor sql service apalagi sampai start/stop/restart service. start/stop/restart service sebaiknya dilakukan manual dari tools bawaan windows.
user harus rajin memelihara servernya. siapa yg rajin belajar dia yg jadi juara kelasnya. betul?
peace "
lengkapnya antum waos ewed http://forum.orisinil.com/index.php/topic,1794.msg79113.html#msg79113
OOoooo ..... OK ...
siapp kemendaaannnnnn >:(
-
WAH TERNYATA SAAT TERJADI DB SUSPECT ADA TRX TERAKHIR YG SUKSES,TP TDK ADA DATA DI TABEL TRX, JD RUGI SKTR 40 RIBUAN :( :(
-
apa betul prosesnya lama bgt ya mpe 20menit lebih lom slese
berapa lama bos ?!
-
berapa lama bos ?!
SUSPECT memang agak lama kadang kalo DB udah full bisa 30 mnt an lbh
-
maaf para juragan mohon bantuan nya server sy sebelumnya agak berat jd sy restart komputernya tp setelah di on jd kendala database nokonek ato pasword salah, mohon bantuan dan pengarahannya..
-
Saya sempat remote, dan sayangnya koneksi lambat sekali keburu ngantar tetangga ke RS.
Coba bos attach db, setelah berhasil baru ditangani dengan script dbsuspect
-
Saya sempat remote, dan sayangnya koneksi lambat sekali keburu ngantar tetangga ke RS.
Coba bos attach db, setelah berhasil baru ditangani dengan script dbsuspect
iya mas jaringan konek sini agak lambat maklum diplosok perbatasan di pegunungan meratus kalimantan, padahal warnet tsb koneksinya speedy klo ada yg bersedia bantu sy siap ngikuti ketentuan beaya dr dealer maupun juragan senior di forum ini yg bersedia dan sy siapkan koneksi insya Allah lumayan, ini demi kepercayaan mitra RS yg sipa trx di server sy berumur itungan jari....maklum juragan dan momod sy masih awan utk dunia server maupun programnya yg tdnya bertahun2 cm sbg md/PENGECER/pengumpul recean di berbagai serve rcoba belajar mandiri, jgn sungkan contekan ilmunya ya agan2 dan momod....
-
coba bawa PC server ke warnet dan minta ke penjaga 1 line untuk PC server tersebut mudahan lancar diremote.
nb : server usahakan khusus server tidak ada aplikasi lain, termauk tidak untuk browsing, chatting.
-
coba bawa PC server ke warnet dan minta ke penjaga 1 line untuk PC server tersebut mudahan lancar diremote.
nb : server usahakan khusus server tidak ada aplikasi lain, termauk tidak untuk browsing, chatting.
inggih makasih atas kesediannya, sy coba ke warnet selesai zhuhur jam sini sdh masuk mas...sy coba bawa semua peralatan server tsb...klo emang sdh error database sblmnya mohon dibantu pengarahan utk memulai dr awal agar server sy bs jalan minimal demikian shg RS sy lega dg kendala tsb insya Allah bs memaklumi keawaman sy...buat para senior yg tlh tergagnggu oleh sy moga bs menjadi silahturahmi yg berkah...mariiiiiiiiiiiiiiiiiiiiii
-
mksh buat para senior dan dealer atas supportnya malam ini terutama mas abitamim, bustamim dan semua yg menyempatin waktu dan pikirannya dalam memberi pengarahan dr kendala sy terutama mas andi pramono wlo database sy gak bs diselamatin tp pelayanan sampean adalah semangat buat sy ...wlo sdh niat sy mo kasih cendol malah di tolak, jd sy wakafin ke mushala...maafin pabila sy merepotkan, sy bs mencontek dr sampean senior...jgn sungkan berbagi ilmu demi silahturahmi dan recehan moga berkah...mariiiiiiiiiiiiiiiiiiiiiiiiiiiiii
-
mksh buat para senior dan dealer atas supportnya malam ini terutama mas abitamim, bustamim dan semua yg menyempatin waktu dan pikirannya dalam memberi pengarahan dr kendala sy terutama mas andi pramono wlo database sy gak bs diselamatin tp pelayanan sampean adalah semangat buat sy ...wlo sdh niat sy mo kasih cendol malah di tolak, jd sy wakafin ke mushala...maafin pabila sy merepotkan, sy bs mencontek dr sampean senior...jgn sungkan berbagi ilmu demi silahturahmi dan recehan moga berkah...mariiiiiiiiiiiiiiiiiiiiiiiiiiiiii
AAMIN....
-
maaf mau tanya nih, kalo misalkan terjadi data suspect gara2x mysql tsb, apa yang harus kita lakukan kepada pelanggan kita yg sudah 1000 Transaksi lebih,,, untuk menjalaskan kepada mereka sedangkan server mengalami masalah data mysql suspect,,, maka dari itu min kita harus bsa belajar mengenai data base mysql apa pun judul dan masalah nya,,,, jangan cari keuntungan saja...
-
ada yg bisa bantu, otomax saya suspect
-
ada yg bisa bantu, otomax saya suspect
Di halaman 1 ada itu boss,
-
otomaxnya sudah bisa terbuka
setiap transaksi yg dikirim ulang manual
di log sistemnya keluar penampakan
Violation of PRIMARY KEY constraint 'PK_sistem_log'. Cannot insert duplicate key in object 'dbo.sistem_log'.
The statement has been terminated.
-
Ini ada sumbangan dari rekan kita yg sudah mengalaminya:
Untuk memperbaiki database yg suspect, jalankan perintah-perintah ini pada Query Analyzer atau SQL Server Management Studio:
EXEC sp_resetstatus ‘yourDBname’;
ALTER DATABASE yourDBname SET EMERGENCY
DBCC checkdb(‘yourDBname’)
ALTER DATABASE yourDBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (‘yourDBname’, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE yourDBname SET MULTI_USER
Sumber: http://gargmanoj.wordpress.com/2008/07/17/how-to-repair-a-sql-server-2005-suspect-database/
-
setelah suspect hampir 2 jam lama nya ada sintax yg berubah
pulsa reguler ke proses pulsa sms itu kira 2 knapa ya bos ku
dulu memang pernah salah pasang sintax itu tpi stlh suspect knpa sintax nya kembali lagi
peprintah sql untuk hapus sintax yg sdh di del tdk terpakai yg mana ya bos ???
-
Apa penyebab DB suspect yah ?????
ane alhamdulillah ga sampe ngalamin .karena tiap malam selalu rutin jalankan query DB suspect +reindex + Shrink .... Manual tanpa SW ;D biar ga lemmot .....
siap laksanakan bos
tak garis bwh i INI PENTING saran nya si bos
menjaga lebih baik dr pd mengobati xixixxxiii
-
siap laksanakan bos
tak garis bwh i INI PENTING saran nya si bos
menjaga lebih baik dr pd mengobati xixixxxiii
;D ;D ;D ;D
ya ya ya ...
-
bantuan dong bos ku
jln kan
use otomax
EXEC sp_resetstatus 'otomax';
ALTER DATABASE otomax SET EMERGENCY
DBCC checkdb('otomax')
ALTER DATABASE otomax SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB ('otomax', REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE otomax SET MULTI_USER
Msg 229, Level 14, State 5, Procedure sp_resetstatus, Line 1
The EXECUTE permission was denied on the object 'sp_resetstatus', database 'mssqlsystemresource', schema 'sys'.
DBCC results for 'otomax'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
DBCC results for 'sys.sysrowsetcolumns'.
There are 913 rows in 10 pages for object "sys.sysrowsetcolumns".
DBCC results for 'sys.sysrowsets'.
There are 126 rows in 1 pages for object "sys.sysrowsets".
DBCC results for 'sysallocunits'.
There are 139 rows in 2 pages for object "sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
hasil ada eror
saya coba hapus outbox juga eror tdk bisa
hapus mutasi juga error
NB: sblm nya saya hapus LEVEL krna ada sistem markup di 3.4.2 alat bantu>> ubah grup reseller
dan nama level 14 saya hapus
bantu ya gan :((
saya hrs lakukan apa ini
apa bikin grup LEVEL14 lagi gt ya ??
-
helepp :) :)
-
The suspect flag on the database "otomax" is already reset.
Msg 5064, Level 16, State 1, Line 2
Changes to the state or options of database 'otomax' cannot be made at this time. The database is in single-user mode, and a user is currently connected to it.
Msg 5069, Level 16, State 1, Line 2
ALTER DATABASE statement failed.
Msg 924, Level 14, State 1, Line 3
Database 'otomax' is already open and can only have one user at a time.
:'( :'( :'(
help
-
Alhamdulillah eror (Database diagram support objects cannot be installed because this database does not have a valid owner)
pakai jurus ini normal kembali.
EXEC sp_resetstatus otomax;
ALTER DATABASE otomax SET EMERGENCY
DBCC checkdb(otomax)
ALTER DATABASE otomax SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (otomax, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE otomax SET MULTI_USER
-
Wih mungkin itu udh kelas advance kali ya.... sy msh newbie masih belum kali ya..
-
Ikut belajar yah omz :)