When connecting to the Local repository on the SAP Data Service Designer, the Visual C++ Runtime Library “Runtime Error” as shown in Fig1 below.
One of the reasons for such an error is when the transaction log for the repository database is full. this can be checked by logging into another repository and then switching to the affected repository. If the issue is with the transaction log then the Switch Object Library option will display error message similar to the one show below
The error simulated in this document is with Sybase ASE. The transaction log issue however is common for all databases where the transaction logging is not configured properly.
Apart from clearing down the transaction log, there are logging options that can be set for a given database in any database software (ORACLE, MS SQL Server, SYBASE ASE, etc., ). In Sybase ASE one option that for logging that will be useful to consider in case of Database local repositories is the “trunc log on chkpt” option.
trunc log on chkpt
When trunc log on chkpt is true (on), the transaction log is truncated (committed transactions are removed) when the checkpoint checking process occurs (usually more than once per minute), if 50 or more rows have been written to the log. The log is not truncated if less than 50 rows were written to the log, or if the Database Owner runs the checkpoint command manually.
You may want to turn this option on while doing development work during which backups of the transaction log are not needed. If this option is off (the default), and the transaction log is never dumped, the transaction log continues to grow, and you may run out of space in your database.
When trunc log on chkpt is on, you cannot dump the transaction log because changes to your data are not recoverable from transaction log dumps. Use dump database instead.
By default, the trunc log on chkpt option is off in newly created databases. To change the default, turn this option on in the model database.
WARNING! If you set trunc log on chkpt on in model, and you need to load a set of database and transaction logs into a newly created database, be sure to turn the option off in the new database.
Based on the policies in the IT infrastructure of your organisation, the DBA can set the logging option accordingly to ensure that these errors can be prevented.