Backup of the SCAI MAS database

SAP DB:
Differing from the manual in the documentation, backup medias should not be named with "BACKUP" at the beginning. This is only for SAP DB backups. We recommend to use the OracleXe or equivalent database system.

Oracle DB:
Here you'll find a script to backup the Oracle instance:
@Echo on
c:
cd c:\SCAI
mkdir OraExport
cd OraExport
exp massys/massys@XE
pause

After the backup finished without errors, you will find the backup file named EXPDAT.DMP in the folder OraExport.

The corresponding import command for Oracle databases looks like:
imp system/massys@XE fromuser=massys touser=massys EXPDAT.DMP '

Document analyzing
The information complexity of the document analysis will be improved extremely, if you have installed the Sun StarOffice Migration Tools on the system. Currently these tools are available only for Sun StarOffice migration partners.

Starting and stopping the SCAI MAS robots
The robots (processes) can be stopped or restarted at any time. But if you intend to delete analysis tasks from the database, you should first stop the analysis robot. Than you can delete the analysis tasks using theQuick task manager.

Installation in a Windows / Novell infrastruktur
If you are using Novell Network Server and you intend to run the analysis, than you should use the following syntax for registration the shares:

Client: <Client Name>
Domain: <Client Name>

For the shares please use:

Share name: <Share Name>
Local path: empty
Domain: empty
User name: <User Name>

If you use the whole UNC path including the DNS name like: servername.scai.de than you will have no access to the entered share. Not later than starting the analysis errors might occur.

Problems and workaround during analyzing

If an ActivX component is beeing executed during analyzing the document, errors might ocure. For example: Microsoft Graph and / or Microsoft Photo Edit.
Workaround: Deinstall the related MSO tools, for example Photo Edit and Graph by using the Software Control Panel.

Error by writing to tbl_issue_prop_name (only Oracle databases)

NULL not allowed in ISSUE_PROPERTY_NAME

Workaround:
Using Toad for Oracle you should enter the following SQL statement:
alter table tbl_issue_prop_name modify(issue_property_name NULL);

File not found during analyzing

Sometimes it might happen, that files can not be found by the FileMover service. Often this is because of using different coding (Ascii7, Unicode) when saving the files. For this the VBA-Macro of the ProAnalysisWizard has to be fixed. The following source code is already implemented:

Concerned documents:
_SO8DocAnalysisExcelDriver.xls
_SO8DocAnalysisPPDriver.ppt und
_SO8DocAnalysisWordDriver.doc

OTH in Novell infrastructure without supporting the SMB protocol

Adding files found by the OTH to the database:
Server is NFS- or Netware-Server, or the file will be saved local and there is no client access.

Workaround/Scenario 1: Saving the file on a NFS- or Netware-Server
In SCAI MAS files allways have to be assigned to a share, so that these documents can be accessed using the UNC-filenames. Furthermore files will be assigned to that share, which is on top of the folder hierarchy.

Example:
Client name: MYFILESERVER
ShareA = C:\myshares\departmenta
ShareB = C:\myshares\departmenta\workgroupX

Now the OTH will add a document to the database: \\MYFILESERVER\ShareB\test.doc
This file now will be assigned to ShareA because ShareA is on a higher level of the folder hierarchy.

Files accessed by SCAI MAS with admin rights have to be assigned to the right share. If this is not possible there is no way to find out, if the file assigned to the right share to get access tio the file. Also with admin rights it is sometimes impossible to get the right share names (NFS, Netware). But for Samba shares it will work.

In this case (you don't have access) you should add "C:\DEBUGHACK\" + SHARENAME into the table TBL_CLIENT_SHARE (field LOCAL_PATH_REP_API). For example: "C:\DEBUGHACK\ShareA"

Now files from ShareA can be assigned correctly in the database. But no verification will be made, if a top level share exists.

Attention: All this is only necessary, if MYFILESERVER will be accessed using a share via the network.

Workaround/Scenario 2: Saving a file on the local disk of a client, where SCAI MAS has no access:

For this two things are necessary:

1. The following registry entry must exist on the client: \\HKLM\Software\Scai\Mas\DONOTCONNECTTOCLIENT = 1

2. The local drive has to be added as a share to the database. Currently SCAI MAS has no front end support to add this share. Use the following SQL statement:

SQL Statement:
Insert into TBL_CLIENT_SHARE (PK_CLIENT_SHAREID, FK_CLIENTID, FK_LOGONID, SHARENAME, LOCAL_PATH_PHYS, LOCAL_PATH_REP_API) values (SEQ_PK_CLIENT_SHAREID.NEXTVAL, :PARAM_ERSETZEN_PK_CLIENTID, null,'C$','C:\','C:\');

Now the file will be added to the database including file size and date. All this data is send from the OTH to the server, so that no response from the server (server -> client connection) is necessary.

Attention: This is necessary if and only if a file has to be added to the database which is saved on the client drive. Furthermore the Workaround/Scenario 1 can be used for file servers, where it is not possible to get the UNC path, because of missing permissions or depending on the infrastructure. If there are local users working on the server and you want that these files also appear in the SCAI MAS database, than you have to add the share twice. First using DEBUGHACK (Workaround/Scenario 1) and second as described in Workaround/Scenario 2.