Search results

You need to create an add.st file that will change the current variable extent to fixed and add a new fixed and a new variable. the command is prostrct add dbname add.st Please see the Progress knowledge base (P7697) or read the Database Administration manual for examples.

Sounds like a grant problem on production database, are you connecting as sysprogress or the owner of the database, if not you or your dba need to, and the grant select privledges to your id or to public. Search for "grant select" in the Progress KB for examples

If your propath differs your r-code size may differ. /app/test and /app/devel are different sizes, if you are in a unix environment you can use the "strings" command to view the r-code

Read about the prostruct command, you need to do a prostruct add to add a new variable extent. You can not just modify the .st and restore the database.

Correct the file-type is determined by the O/S and can not be set.

Look in the Progress knowledge base P18482

The -n is decreasing because you do not have enough semaphores allocated, you need to tune your kernel

Pretty much so, other things are, extents can not exceed 2GB so set bi and ai threshold, and you can not convert a workgroup database to a different blocksize.

Extents can not exceed 2GB and you can not convert a db to a different blocksize (i.e. prostrct convert)

Unless you have purposely created a name server named lin using the default name server port, you should do: nsman -name NS1 -start then nsman -name NS1 -query If you created a name server lin, the lin name server should be define in the $DLC/properties/ubroker.properties file. As for...

eB2 SP9 requires Progress 9.1. It is not certified for OpenEdge until SP10

Rebuild the desktop

I think the problem may be with either the \windows\drivers\etc lmhosts.sam or \windows\drivers\etc\protocols. Compare these in XP to the win98 ones (located in the windows directory).

The reason MFG/PRO switched from find first to for first was to use "field lists" with eb desktop. A find will return all fields in a record, for first with a field list will only return the fields identified in the list.

http://resources.progresstalk.com/ I thing there is a kill user script in Backmans DBA scripts. But I would also go to the user's login script and make sure the "trap" settings are right (do not use "trap 1") so the processes die gracefully.

You need to start a broker on the server machine by adding an entry in the services file, and adding a -S and -N in it's startup script. You then make an equivlent entry in the client's startup .pf or script with a -H, -S and -N entry. If the server is NT you might also use ProControl.

In the data dictionary the trigger file should be "trig\trig-name.p" The propath should include "c:\drive", or -trig "c:\drive" to extented the propath ,