Output files

The following command reads the database and outputs it as ASCII to filename. The history data is not output. The file is tab-delimited.

WCCOAascii -out filename

• In a heterogeneous system with a remote UI, it is not possible to run a Windows ASCII Manager with a Linux DB (due to the different binary formats of the database). Thus, if the remote UI project runs on a different platform than the server project, the ASCII manager must be run on the server.

• Note that if you edit the ASCII file via Excel, Excel generates doubled apostrophes for the entries, which you have to delete.

• If you edit ASCII output files in Excel, you must specify Text format for all columns and "none" as the text delimiter.

• When editing files output from the ASCII Manager in Excel, you must not re-input the _Users entries otherwise the users and passwords will be changed resulting in authorization problems.

• The name of the ASCII file must only contain ASCII encoded characters!

• The ASCII manager limit for import and export of large values (e.g. BLOBs) is 1MB.

• RAIMA is started in a single user mode when the Data Manager starts. The mode is switched to multi-user automatically as soon as the DataBG is started. If an ASCII export is started during this single user phase, the database cannot be opened. In this case, an error message is shown saying that a WinCC OA project is just starting and an ASCII export cannot be realized.

• Note that an ASCII output after an ASCII input, executed via a script, should be delayed a few seconds, so that the Data Manager can write the changed values from the input into the database (an ASCII output is made directly from the database)!