Search results

Insufficient disk space or Write access denied with error 291 when lots of disk space is available https://community.progress.com/s/article/insufficient-disk-space-or-write-access-denied-with-error-291-when-lots-of-disk-space-is-available Cause There are many "old" temporary files present in...

Are there a lot of records in the mfg-tagm table? It looks like it's a sorting of BY phrase that causes the error. What is the -T directory?

Can you check debug-list of get_stock_detail inv/inv310spsx3p.p? What is a operator in line 6684?

Is the error 291 the only one that is reported in db log? No errors 6072?

Exactly. xcode is a part of any development version of OpenEdge. I guess the evaluation versions include it as well. The size of the file: 10.2B 47,456 11.7 54,472 12.2 54,984 12.8 57,368 It's not exactly the same but I still believe the xcode.exe works for all versions.

Start a session with the -rx option and Data Administration will allow you to dump data definition files. Run-time license allows to compile the xcoded sources. "Encrypted Compiler Mode" = "the -rx client startup parameter". Do you have xcode.exe in DLC directory? Update: I can be wrong but...

What version of the operating system? Can you install the recent evaluation version of OpenEdge? Then you can convert your database and dump data using new version. Do you have a run-time license installed? Then you can dump and upload the .df files. And somebody can compile the dump programs...

SUPPROMSGS/gre contains only 2 df's: gre851.df CODEPAGE-NAME IBM851 COLLATION-NAME GREEK gre1253.df CODEPAGE-NAME 1253 COLLATION-NAME GREEK Both these codepages you are already used. Internet gives other codepages for Greek language: 737 Code page 737 - Wikipedia 869 Code page 869 -...

Long time ago I wrote a script (logsem.sh) to read the database login semaphore. It was tested only on Linux and AIX but not on HP-UX. I don't know if HP-UX has the commands to get the requested information but why not? When nobody can't connect a database it's good idea to check what is going...

Some self-service process tried to log out. It took the USR latch and freed the slot in Connection Table. Then something gone wrong - the process hung and did not release the latch. I bet the process was still running while you tried to stop the database. For such situations watchdog can't...

BTW, 11.7.10 update provides a. Additional Usr latch protection at logout and login, b. Additional checking for USR latch at user disconnect c. Additional information is written to the database lg file should these be encountered This information is recorded in the following public Articles...

Most likely, a login semaphore or USR latch was locked. promon -F would connect the database (like proshut -F did) and would allow to find out a process that hold the USR latch. If it was the login semaphore, then OS commands would help.

Use the "try and check" method. For Greek: CODEPAGE-CONVERT(string, "UTF-8", "1253"). If the conversion corrupts data then use "IBM851" instead of "1253".

What is the value of SEESION:CPSTREAM? I18N: Code Pages and Possible Conversions Baltic - 1257 Greek - 1253, IBM851 Western Europe (*) - 1252, ISO8859-1, IS8859-15, IBM850, IBM037, IBM273, IBM277, IBM278 *German

Recent thread: https://www.progresstalk.com/threads/getting-details-from-ai-files.203024/

IMHO, _Servers._SrvParam-* is a minor problem compared to the _ActBuffer._Buffer-<block_types> disaster.

DbParam.p merges _DbParams and _Servers.._SrvParam-* for version 11.5 and higher or imitates _DbParams for versions before 11.5.

Wouldn't it be easy to get the non-default startup parameters using _DbParams VST (since v11.5)? BTW, it’s easy to write a program-watchdog that would persistently monitor the online changes of the startup parameters. I’m not sure if DBAs are often changing the parameters online. But if they do...

How often were the latch conflicts resolved during the spinning phase - without getting the naps? The quotes from above: "Every transaction in ATM tests locks the (MTX) latch exactly 8 times and forces to nap on the latch 0.30 times in average." "MTX latch was busy only 14% of the time." So at...

> The -spin value does not seem to have any effect. What did I miss? Stupid me! The contribution of the spinning phase was expected about 100 nanoseconds or 0.1 ms. Only bonehead will set the -nap to the hundreds ms! I added the results for the -spin 9999999 - the max value allowed to be set...