FixYa.com
Technical Support, Instructions & Repair Service
Home | My Products | Sign In

Back to:
All Products > KLH > 970A Main / Stereo Speaker > Troubleshooting


Tags:
error code, ERROR MESSAGE, locked, disk error, Virus

KLH 970A Main / Stereo Speaker

DB23819C - Sharing Violation

By Bray - usenet poster
Report abuse


Hi,

I am running db2 udb EE v7 fp7 on a windows 2000 server. Recently I
have had an application that crashes the instance. The error message
I see in the db2diag.log is ...

2002-10-24-13.54.07.234000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
relation_data_serv sqlrr_dump_ffdc Probe:902 Database:MAATD
DIA3819C A file sharing violation has occurred, filename was "".

ZRC=0xFFFFF616

After this message things really go bad ending in the database being
marked as damaged, then the instance crashes.

The developers swear they are only performing normal inserts.

After reading other postings I have checked our virus scan software
settings (we use McAffee Netshield) and it appears that db2 files are
being excluded from the scan (we excluding files with extensions of
.log, .dat, .inx).

Can anyone point me in the right direction? Why don't I see a
filename listed?

Thanks,
klh

X
This Problem has been added to the Share Your Expertise Page under "My Work Queue".
Solution #1
posted on Aug 02, 2007
Not Rated (0)

Mini Me

Mini Me - usenet poster

Rank:Apprentice Apprentice
Rating: 0%, 0 votes
Thanks for the reply.

Since the original post I have found that there is a process running
on the box once a week that seems to be causing this problem. I'm
working with my network folks now to try to capture this process.

I will go ahead and post the entire db2diag.log concerning this error
so you can see the context of the message. Sorry for the length, but
thanks for the help.

klh

db2diag.log follows ...

2002-10-24-13.54.00.921000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
buffer_pool_services sqlbSMSOpenContainer Probe:820
Database:MAATD
DIA3819C A file sharing violation has occurred, filename was "".

ZRC=0xFFFFF616

2002-10-24-13.54.00.968000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
buffer_pool_services sqlbSMSOpenContainer Probe:820
Database:MAATD

Obj={pool:9;obj:2;type:0} State=x0 Cont=0
D:\DB2\MAATD\AAWRKS19\SQL00002.DAT

Data Title:SQLB_OBJECT_DESC PID:2040 TID:3112 Node:000
0900 0200 0900 0200 0000 0000 0000 0000 ...
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0101 0000 0000 0000 0000 0000
0010 0000 2000 0000 0100 0000 0900 0200 ...
b874 2c02 3000 3302 ??t,.0.3.

2002-10-24-13.54.01.390000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
buffer_pool_services sqlbSMSGetOpenInfo Probe:810 Database:MAATD
DIA3819C A file sharing violation has occurred, filename was "".

ZRC=0xFFFFF616

2002-10-24-13.54.01.437000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
buffer_pool_services sqlbSMSGetOpenInfo Probe:810 Database:MAATD

Obj={pool:9;obj:2;type:0} State=x0 Cont=0

Data Title:SQLB_OBJECT_DESC PID:2040 TID:3112 Node:000
0900 0200 0900 0200 0000 0000 0000 0000 ...
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0101 0000 0000 0000 0000 0000
0010 0000 2000 0000 0100 0000 0900 0200 ...
b874 2c02 3000 3302 ??t,.0.3.

2002-10-24-13.54.01.515000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
buffer_pool_services sqlbReadPage Probe:1130 Database:MAATD
DIA3819C A file sharing violation has occurred, filename was "".

ZRC=0xFFFFF616

2002-10-24-13.54.01.546000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
data_management loadSMSDesc Probe:1171 Database:MAATD
DIA3819C A file sharing violation has occurred, filename was "".

ZRC=0xFFFFF616

2002-10-24-13.54.01.593000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
data_management loadSMSDesc Probe:1268 Database:MAATD
DIA3819C A file sharing violation has occurred, filename was "".

ZRC=0xFFFFF616

2002-10-24-13.54.01.640000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
data_management sqldLoadTCB Probe:7 Database:MAATD
DIA3819C A file sharing violation has occurred, filename was "".

ZRC=0xFFFFF616
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLD_TCB

2002-10-24-13.54.02.015000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
data_management sqldFixTCB Probe:2704 Database:MAATD
DIA3819C A file sharing violation has occurred, filename was "".

ZRC=0xFFFFF616

2002-10-24-13.54.02.046000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
data_management sqldScanOpen Probe:800 Database:MAATD

rc=FFFFF616, P=9 O=2, ccbptr=03FACC20

String Title:SQLD_CCB: PID:2040 Node:000
pool(TID)=9, obj(FID)=2, indexid(IID)=0, class=0
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLD_CCB
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLI_IXPCR
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLD_IXINFO
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLD_IXKEY
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLD_IXKEY

2002-10-24-13.54.02.453000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
data_management sqldScanOpen Probe:800 Database:MAATD
DIA3819C A file sharing violation has occurred, filename was "".

ZRC=0xFFFFF616

2002-10-24-13.54.02.499000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
data_management sqldScanOpen Probe:800 Database:MAATD

Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLE_DBCB
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLD_DBCB
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000
Data:SQLD_AGENT_CB
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLD_TRAN_CB

Data Title:SQLD_AGENT_CB Pointer: PID:2040 TID:3112 Node:000
3000 fc03 0.??.

Data Title:SQLD_AGENT_CB PID:2040 TID:3112 Node:000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0010 0000 f0d9 e903 ??????.
0010 0000 00ea e903 0010 0000 30c0 f803 ????0????.
0000 0000 0000 0000 0080 0000 3040 e903 ???..0@??.
0010 0000 40c0 e903 0000 0000 0000 0000 ????

Data Title:SQLD_TRAN_CB Pointer PID:2040 TID:3112 Node:000
e0c0 fa03 ??????.

Data Title:SQLD_TRAN_CB PID:2040 TID:3112 Node:000
60c0 8101 0000 0000 0000 0000 0000 0000 `??
0000 0000 0000 0000 0000 0000 0000 0000
0100 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 80e7 fa03 3040 f803 ???????.0@??.
0100 0000 0100 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000

String Title: OPEN PERM CURSORS:
String Title:<< End CURSOR dump: PID:2040 Node:000
OPEN PERM CURSORS: <<

String Title: OPEN TEMP CURSORS:
String Title:<< End CURSOR dump: PID:2040 Node:000
OPEN TEMP CURSORS: <<

String Title: CLOSED CURSORS:
String Title:SQLD_CCB: PID:2040 Node:000
pool(TID)=3, obj(FID)=2, indexid(IID)=0, class=0
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLD_CCB

String Title:<< End CURSOR dump: PID:2040 Node:000
CLOSED CURSORS: <<

Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLI_CB
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLE_ACB

2002-10-24-13.54.03.687000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
global_services sqlzerdm Probe:40 Database:MAATD

16f6 ffff .??????

2002-10-24-13.54.03.984000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
relation_data_serv sqlrr_dump_ffdc Probe:17 Database:MAATD
DIA3819C A file sharing violation has occurred, filename was "".

2002-10-24-13.54.04.031000 Instance:WFFSAD Node:000
PID:2040(db2syscs.exe) TID:3112 Appid:A5DD1036.970A.021024133349
relation_data_serv sqlrr_dump_ffdc Probe:17 Database:MAATD
DIA9999E An internal error occurred. Report the following error code :
"0xFFFFF616".

Data Title:SQLCA PID:2040 TID:3112 Node:000
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 2
sqlerrmc: 22
sqlerrp : sqlrita ??
sqlerrd : (1) 0xFFFFF616 (2) 0x00000016 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:SQLCA
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:DB2RA

Data Title:CREATOR PID:2040 TID:3112 Node:000
4e55 4c4c 4944 2020 NULLID

Data Title:PACKAGE PID:2040 TID:3112 Node:000
5351 4c4c 4630 3030 SQLLF000

Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:CREATOR
Dump File:\\WEBSPRDBT\DB2-WFFSAD\WFFSAD\20403112.000 Data:PACKAGE
Dump ...
read more »

Was this solution helpful? Show your Appreciation by rating it:

Inappropriate Thanks for Trying Helpful FixYa!
Solution #2
posted on Aug 02, 2007
Not Rated (0)

Mini Me

Mini Me - usenet poster

Rank:Apprentice Apprentice
Rating: 0%, 0 votes
Hello... Do you believe that the virus scan was running during the time
of this crash? There are many more files than just ones with .dat, .inx,
.log...

Is there anything prior to this message in the db2diag.log? How about the
messages that follow... we may be able to determine what type of file had
the problem from some of the subsequent db2diag.log entries.

--

Bohdan Taramina
DB2 UDB Consulting Services

Was this solution helpful? Show your Appreciation by rating it:

Inappropriate Thanks for Trying Helpful FixYa!
Solution #3
posted on Aug 02, 2007
Not Rated (0)

Gary10

Gary10 - usenet poster

Rank:Apprentice Apprentice
Rating: 0%, 0 votes
Hi,

I have seen this many times, but not on a FP as high as fp7. What generally
happens is that some "other2 process is accessing your db2 files (whether
that be LOGS or applications data) when DB2 wants to (I have seen this the
most times where the logs are concerned). Is this happening around the same
time each day? If so it's obviously a "regular" process other than DB2.

Are the servers being backed up (using some form of NT backup) and the DB2
directories are NOT excluded from that copy? There is also software (Compaq
Insight manager for one) that regularly runs on NT and interferes with DB2
files (speak to your IBM rep/support - they know about this).

If you cannot track the offender down easily, you should setup an AUDIT
policy under Windows (see you Server Admin people) and track who and what is
accessing the DB2 files other than DB2 and then nail the offender. As I say
I have seen this many times with Windows/DB2 and usually the LOGS directory
is being backed up by a non-db2 product - you should exclude ALL DB2
directories from any backup other than from DB2 imho.

A word of warning - this can get far worse (don't know about FP7, but deffo
on FP3 and less) and if not tracked down, can force DB2 to crash and you'll
have to bounce the server - there's also a chance of data corruption/loss.
The problem is due to access violations (the file sharing violation) and
when this happens memory leaks occur and we all know what happens to windows
when you run out of memory

As I say, check the obvious out and put an AUDIT trace on if you still can't
track the culprit down...

Please feel free to feedback

Martin

...

Was this solution helpful? Show your Appreciation by rating it:

Inappropriate Thanks for Trying Helpful FixYa!
Solution #4
posted on Aug 02, 2007
Not Rated (0)

Green1

Green1 - usenet poster

Rank:Apprentice Apprentice
Rating: 0%, 0 votes
KLH:

You're probably going to need a trace for this one. I suspect you should
exclude a lot more than you are, BTW. DB2 does NOT like to have it's
files locked by outside processes. But that's an aside.

Example of Tracing to a File

Tracing to a file is useful when the problem being re-created suspends
the workstation, preventing you from dumping the trace to a file. When
you trace to a file, each trace entry is written to disk when it happens.
The information in the file captures those events leading up to (but not
including) the suspension.

In this example, the size of the file is specified as 4 MB and the name
of the file is db2trc.dmp:

1. Shut down all other applications.
2. Turn the trace on, using the following command:

db2trc on -l 4000000 -e -1 -f db2trc.dmp

3. Reproduce the problem scenario.

The db2trc.dmp file will be present when you reboot your
workstation. It will contain the events leading up to the event that
caused the system to crash.

That's from the DB2 doc that you can query using a browser. Located in
\SQLLIB\DOC\HTML. You should have a DB2 INFORMATION menu Item below IBM
DB2 on the START\PROGRAMS option. The trace will give you lots more
information about who and what has caused the error. Just remember to
leave the trace off once you have recovered from the crash! :)

If you post the results, I'm certain a nice IBM-type person will assist
you with interpreting it, or you can email it to me and I'll give it a
bash.

(klh) wrote in

Was this solution helpful? Show your Appreciation by rating it:

Inappropriate Thanks for Trying Helpful FixYa!

Can you Help with these Home Theater Speakers and Subwoofers problems?

Home Theater Speakers and Subwoofers
Home Theater Speakers and Subwoofers
Need to replace one of the 5.25
I bought a used Boston... Answer This...
Home Theater Speakers and Subwoofers
Home Theater Speakers and Subwoofers
sts96 speaker wire
speaker wire's not long enough Answer This...
Home Theater Speakers and Subwoofers
Home Theater Speakers and Subwoofers
turning off the speakers on my...
Iwant to turn off my speakers... Answer This...
Home Theater Speakers and Subwoofers
Home Theater Speakers and Subwoofers
Popping sound
Sub has an auto off when not... Answer This...
KLH 970A Main / Stereo Speaker
KLH 970A Main / Stereo Speaker
KLH 970A Speakers
I cannot find an istruction /... Answer This...
Repair Service
Find Home Theater Spe. Repairman Near You:

FixYa does not evaluate or guarantee the accuracy of any information provided through its proposed solutions, posts, or Expert Assistance Sessions. By entering this site you declare you read and agreed to its Terms. You may NOT copy or distribute the content that appears on this site without written permission from FixYa Inc.
© 2005-2008, FixYa, Inc. or its affiliates
When the original poster rates a solution that was given to his own problem, that rating is locked!
X

Are you sure the solution content is Inappropriate?
   
Tech buddies can communicate directly to answer questions. Become a Tech Buddy and have direct access to your favorite expert for FREE!