Kbase P140068: Database started via bat files launched via BackupExec's pre and post processing tasks, intermittent
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  16/08/2010 |
|
Status: Verified
SYMPTOM(s):
SYSTEM ERROR: <function>: Bad file descriptor was used during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9446)
<function>:Insufficient disk space during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9450)
SYSTEM ERROR: read wrong dbkey at offset <offset> in file <file> found <dbkey>, expected <dbkey>, retrying. area <number> (9445)
Corrupt block detected when reading from database. (4229)
<func-name>: Error occurred in area <num>, block number: <num>, extent<name>: . (10560)
Writing block <num> to log file. Please save and send the log file to Progress Software Corp. for investigation. (10561)
SYSTEM ERROR: Wrong dbkey in block. Found <dbkey>, should be <dbkey2> in area <num>. (1124)
Begin ABNORMAL shutdown code (2249)
First user that goes to perform a write against the database fails with the 9446 error.
The block dumped within the database log file shows all zeros "0"
Database shutdown script / bat file is being initiated in the pre-processing portion o the BackupExec utility
Database startup script / bat file is being initiated within the post processing portion of the BackupExec utility
The protrace files associated with the database's abnormal shutdown are located in C:\Program files\Veritas\BackupExec\NT subfolder
FACT(s) (Environment):
Database being shutdown and started via a scripts / bat files.
Disabled Volume Shadow Copy of Backup Exec and issue still occurred.
Windows
OpenEdge 10.0B02 Service Pack
FIX:
1. Set BackupExec so that it does not backup any open files.
2. Removed the database startup and shutdown scripts from the BackupExec utility and have them run as a different user under Scheduled Tasks.