on 2014 May 30 10:07 PM
Dear all,
We are facing the prd server down issue from last 3 days on the daily basis , each time error is coming like below in db2diag , pls help us on how to resolve the issue,
014-05-28-22.37.28.010000+330 I100653749F452 LEVEL: Error
PID : 4032 TID : 3240 PROC : db2syscs.exe
INSTANCE: DB2PRD NODE : 000
EDUID : 3240 EDUNAME: db2loggw (PRD) 0
FUNCTION: DB2 UDB, data protection services, sqlpgolf, probe:220
RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing violation." DIA8519C A file sharing violation has occurred, filename was
"".
2014-05-28-22.37.28.010000+330 I100654203F591 LEVEL: Error
PID : 4032 TID : 3240 PROC : db2syscs.exe
INSTANCE: DB2PRD NODE : 000
EDUID : 3240 EDUNAME: db2loggw (PRD) 0
FUNCTION: DB2 UDB, data protection services, sqlpgolf, probe:220
MESSAGE : Filename :
DATA #1 : Hexdump, 40 bytes
0x0000000011FEF57C : 4B3A 5C64 6232 5C50 5244 5C6C 6F67 5F64
K:\db2\PRD\log_d
0x0000000011FEF58C : 6972 5C4E 4F44 4530 3030 305C 5330 3037
ir\NODE0000\S007
0x0000000011FEF59C : 3234 3836 2E4C 4F47 2486.LOG2014-05-28-22.37.28.010000+330 I100654796F368 LEVEL: Error
PID : 4032 TID : 3240 PROC : db2syscs.exe
INSTANCE: DB2PRD NODE : 000
EDUID : 3240 EDUNAME: db2loggw (PRD) 0
FUNCTION: DB2 UDB, data protection services, sqlpgole, probe:1710
MESSAGE : Error -2029060074 opening database log extent 72486:
Regards
RK
Hi,
We are using SAN, We can see the SAN log also
RK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rableen,
Try to do a ScanDisk with Repair mode if your OS is Windows or FSCK for Linux or Unix. chkdsk /r /f
It can helps, We had faced the same issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
From sap we got the reply as below....
so, it is clear that there is something holding these logs, so the
database cannot write to them and so it stops as the database first
checks if it can write to logs before it starts up.
Please ensure not to copy or move any active logfiles while the db is
online as this can cause inconsistencies in the logs.
Please restart the server machine to clear any file access and then
try to start the db and sap system.
But no copy was going on ....
and we don,t have antivirus also.
Regards,
RK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
66 | |
10 | |
10 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.