Recent content by balebob

  1. B

    Error PRO_ELEMENT when using field with extent

    We have a Progress table with a few fields that are using extent (about 4 extents for each field with different data format). When I use PRO_ELEMENT such as shown below: ..., PRO_ELEMENT("table"."field",1,1), PRO_ELEMENT("table"."field",2,2), PRO_ELEMENT("table"."field",3,3)...
  2. B

    ODBC Progress Syntax Error 7587

    Thanks, Casper. Please correct me if I am wrong... From SQL 2000 query: with (INDEX("PUB"."Table_Name"."Index_Name")) Am I safe to say that this is correct syntax? Thanks, Bob.
  3. B

    ODBC Progress Syntax Error 7587

    I try to run the DTS package which has th following statement from my SQL2000 server and get the syntax error. select * from PUB."table_name" with (index=index##name) We have Progress 9.1E SP4 on AIX 5.2 machine. The SQL2000 server is on Windows 2003 which has a DataDirect ODBC driver to...
  4. B

    openedge installation is AIX

    Sound like you miss the bos.adt.debug toolset from BOS. BoB.
  5. B

    AIX 5.2 64-bit kernel enable with QAD MFGPRO eb 32-bit application

    Hi All, I just enabled 64-bit kernel on one of my AIX 5.2 test server to see if I can run my QAD MFGPRO eB 32-bit application or not. I was able to bring the QAD db up and test all the functionality and the system ran flawlessly. I am wondering if anyone has run QAD MFGPRO 32-bit application...
  6. B

    -B parameter

    Quick Calculation: Physical Mem = -B value x Data Block Size Ex.: Let assume that you data block size is 8192, the current -B that you have will use: 2000 x 8192 = 15.6 MB Depend on what operating system that you use and if you are using 32-bit or 64-bit application/progress. For...
  7. B

    Why size of index area reduced after dump and load?

    1. Yes, the index utilization increase over the year before d&l. In fact, I did a dbanalys before dump. Some of the table in the data area did have a very high scater factor (between 2 to 5). I ran another dbanalys after load and full index rebuild... and notice that the scater factor in the...
  8. B

    Why size of index area reduced after dump and load?

    I noticed that after my first dump and load of the database with full index rebuild. The size of some index area is reduced to almost half of its size before d&l even though the data area for that index has never been archived. This is great but I would like to know why the size of the index...
  9. B

    How to load multiple binary dump files

    We use binary dump to dump all data on one of our bigest table called 'customer' which is about 13 GB. We got about 7 binary dump files with suffix like .db1, .bd2 etc. My question is how do we load all these bin file back into the table? And should we load the last file first (.bd13) or...
  10. B

    In-place conversion problem

    Thanks, 80% full limit... is it a system file size of the dump data directory? Is this in Progress document or QAD document? Bob
  11. B

    In-place conversion problem

    Hi All, I am testing an in-place coversion on the production db from MFGPRO eB SP5 to eb 2.1 SP5 with Progress OE10.1A02. I am following QAD eB2.1 Conversion Guide - Progress Database and run into a strange problem... The conversion fail to update the source schema using the delta schema file...
  12. B

    Can rfutil roll forward done while db is online?

    Hi All, We have a warm-spare db on a different server. I am wondering if I can ship the filled AI extents over and roll forward while the db on this warm-spare server is online. The reason is that warm-spare database is also being used for running report during the day (before the next refresh...
  13. B

    Please Help! Conversion invalid for datatypes when using pro_element

    All I got is "?". The data-type on the Progress field is also date. That is why I do not understand why SQL think it is a string data type when pulling over the data (pro_element). Thanks, BoB.
  14. B

    Please Help! Conversion invalid for datatypes when using pro_element

    Hi All, I try to pull the data from a Progress array (9.1E) over to a SQL 2000 table using PRO_ELEMENT and I recevied to following error: "...Conversion invalid datatypes on column pair 1 (source column 'pro_element(item_date,1,1)'(DBTYPE_STR), destination column...
  15. B

    Progress 9.1E on AIX 5.3

    Hi All, Do you know that Progress 9.1E has been tested on AIX 5.3 yet? Thanks, Bob.
Top