• Replies 2 replies
  • Subscribers 4 subscribers
  • Views 30 views
  • Users 0 members are here
Options
Related

Database error 51

Satyavarapu VenkataSaiSiva

Hi All,

I am running an MTO. When running the report I am getting below error. Before running the MTO. I done DICE Check no issues found. If I ran individual extraction for each site also no issues found. When I took extracting MTO in bulk. Then encountering the below issue. Anyone has any idea on the same.

Current element was =19890/4371 %INST /PV-2091-12 in Db , numbe

Unhandled Database error 51 from DSAVE
Message System not initialized
Message number : (6:51)
Extra info:
Last Dabacon routines called:
DGOTO =19890/4371 %INST /PV-2091-12 in Db , number 3506
DGETI =19890/4371
DGTNTS =19890/4371
DFTONO =19890/4371
DSAVE =19890/4371
This error was set in call 164883712 to DABKER

Parents

  • It sounds like there may be too many read/write operations for the Dabacon Kernel to keep up with, and is a core software function.

    DSAVE ( and DSERVE ) are basically dabacon data requests/receives for the project DB for information.

    There’s a limit to the amount of these in a single operation, so if you’ve got a report or macro that’s performing an astronomical amount of checks, you may be hitting that limit.

    You may need to split up your report or macro into multiple stages and combine the resultant reports later.

Reply

  • It sounds like there may be too many read/write operations for the Dabacon Kernel to keep up with, and is a core software function.

    DSAVE ( and DSERVE ) are basically dabacon data requests/receives for the project DB for information.

    There’s a limit to the amount of these in a single operation, so if you’ve got a report or macro that’s performing an astronomical amount of checks, you may be hitting that limit.

    You may need to split up your report or macro into multiple stages and combine the resultant reports later.

Children