Database Startup Error

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Database Startup Error

    After a power failure which forced a server reboot, my database will not start. See below for the log file (XXX = my database name) after restarting services.

    There are 42 blank lines in the database_CUBE_90.csv' file. I have no idea what should be in this file.

    Can you help me get my database back up?

    2014-01-24 17:30:43 INFO: starting Jedox OLAP 3.3.2 (3076)
    2014-01-24 17:30:43 INFO: using extension 'palo https interface'
    2014-01-24 17:30:43 INFO: registered system database 'System'
    2014-01-24 17:30:43 INFO: registered user info database 'Config'
    2014-01-24 17:30:43 INFO: registered database 'Demo'
    2014-01-24 17:30:43 INFO: registered database 'XXX'
    2014-01-24 17:30:43 INFO: system database not yet loaded
    2014-01-24 17:30:44 INFO: auto loading database 'Config'
    2014-01-24 17:30:44 INFO: created CubeDimension
    2014-01-24 17:30:46 INFO: setting client cache type to 0
    2014-01-24 17:30:46 INFO: setting hide elements to 1
    2014-01-24 17:30:46 INFO: auto loading database 'Demo'
    2014-01-24 17:30:46 INFO: created CubeDimension
    2014-01-24 17:30:51 INFO: setting client cache type to 0
    2014-01-24 17:30:51 INFO: setting hide elements to 0
    2014-01-24 17:30:55 INFO:auto loading database 'XXX'
    2014-01-24 17:30:55 INFO: created CubeDimension
    2014-01-24 17:31:01 WARNING: cannot load database 'XXX'
    2014-01-24 17:31:01 WARNING: message 1: Section 'CUBE' not found.
    2014-01-24 17:31:01 WARNING: message 2: file './XXX/database_CUBE_90.csv' line number '2'
    2014-01-24 17:31:11 INFO: user login is required
  • Hi,
    strange palo should be able to recover from this it saves cube data first to tmp file. Once completed it deletes old file and rename tmp file to csv.
    Could be problem with os/filesystem than didn't flush data to media before power outage.
    First of all make a copy of the database before starting the server again.
    Check if there is database_CUBE_90.bin or database_CUBE_90.tmp file.
    If you find the *.bin file you can try to delete the *.csv file and restart server.
    If you have older backup you can try to reconstruct the empty cube file and use database_CUBE_90.archived to reconstruct data.

    database_CUBE_90.csv should look like this (repplace NUMBER_OF_DIMENSIONS by real number of dimensions cube had before - if you are not sure check database.csv - look for string line loke this: 90;"CUBE_NAME";NUMBER_OF_DIMENSIONS; :(
    -------------------------------------------------------------
    # PALO CUBE DATA
    #
    # Description of data:
    # TIME_STAMP;SIZE_DIMENSIONS;
    [CUBE]
    1390817374.292834;NUMBER_OF_DIMENSIONS;
    # Description of data:
    # PATH;VALUE
    [NUMERIC]
    # Description of data:
    # PATH;VALUE
    [STRING]
    #
    # PALO CUBE DATA END
    -------------------------------------------------------------

    then you can try to copy database_CUBE_90.archived into database_CUBE_90_0.log and restart the server.
    It is possible that some of the lines from the database_CUBE_90_0.log file will have to be deleted and whole operation can take long time.

    hope it helps
    Jiri