false cube being processed message in browser

[Bryan]

Hello,

We are on version 6.6. The cubing process appears to finish without errors, and no errors are apparent in the text logs. Yet we get this message in the web browser when trying to access a report:

The database or cube you are trying to access is currently being processed or contains errors. Please try again at a later time or contact your Stratum.Viewer Administrator for assistance.

Can someone suggest where I should look to rectify this issue? Thanks.

• This topic was modified 2 years, 6 months ago by Bryan. Reason: set email notify flag

[Bryan]

Checked the log files. DSLAGG is getting an error writing to the output file at least once for every sub-category. In the LoadAS log for example, getting this:

11/09 12:17:57 Driver calling ‘E:\SERVER\DTPROD\DSLAGG.EXE /DS=DSAS /FT=5 /PI=1 /LT=1 /DA=1 /OLAP=1 /LF=E:\Server\DTLOGS\LoadAS.Log /MS=10000 /MT=1 /YEAR=1998,1999,2000,2001,2002,2003,2004,2005,2006,2007,2008,2009,2010,2011,2012,2013,2014,2015,2016,2017,2018 /SI=L.312.00007.18.0000.000’
11/09 12:17:57 ***************************
11/09 12:17:57 Beginning DSLAGG 64 (6.0.2)
11/09 12:17:57 Processing L.312.00007.18.0000.000
11/09 12:17:57 Aggregating into 2 DSLs.
11/09 12:18:10 Building DSL 899 from input data (0.0MB).
11/09 12:23:55 Input records: 30722645 read, 30722631 used (3085.1MB).
11/09 12:23:55 Total input records: 30722645 read
11/09 12:23:55 Creating DSL 899 Year 2017.
11/09 12:24:03 Output records: 318341 Headers, 1784665 Details.
11/09 12:24:03 Inserting OLAP Master records.
11/09 12:24:55 Creating DSL 899 Year 2016.
11/09 12:25:10 Error: Writing to output file.
11/09 12:25:11 Unsuccessful end of DSLAGG.
11/09 12:25:11 ***************************
11/09 12:25:11 Error: Child process failed.
11/09 12:25:11 Unsuccessful end of Import Driver.
11/09 12:25:11 **********************************

[Frank]

Bryan – these types of questions are best handled via our Support Team. We’ll probably need more info than what you’ve posted and Support can help out with what you need.

[Bryan]

FYI the issue was due to characters in the master file fields that were outside of the defined Silvon range (Hex 1F – 7E), which means that all accented characters are not supported.

[Author]

Posts