Enable diagnostic in ATP inquiry ASCP

What does the enable diagnostic do if checked when performing an ATP inquiry in ASCP-land?
Thanks in advance

Please see these docs.
Getting ATP Inquiry Debug Files - The Session Files [ID 122372.1]
FAQ - How to Use Debug Tools and Scripts for the VCP (aka APS) and EBS Applications [ID 245974.1]
Getting Started With R12 - Advanced Planning and Scheduling (APS) - Support Enhanced RCD [ID 414332.1]
Thanks,
Hussein

Similar Messages

  • ATP Inquiry Supply/Demand

    Running 11.5.9 Advanced Supply Chain Planner>>>ATP>>>ATP Inquiry. It would appear that this inquiry takes its supply and demand information from the ascp plan. Is this a correct assumption? If this is true is there anyway of this inquiry capturing supply that is created through the workday or do you always have to wait until the plan runs again?

    Yes. The ATP Inquiry Form always takes information from the Plan. If there is any new supply created in the worday, you will have to wait till the Plan runs

  • ATP Inquiry

    Running 11.5.9. Advanced Supply Chain Planner>>>ATP>>>ATP Inquiry. Choose an org. Enter an item and quantity and hit the ATP Details button. After data is returned with date looking to drill into the details. Right-click on item and see choices such as EXPAND, SUPPLY/DEMAND etc. However the SHOW CONSTRAINTS is not highlighted. Any thoughts??? Thanks in advance!

    Hi
    In OM module, you have to set up the instances too.The option ATP based on collected data will give the result for ATP inquiry for the OM whereas in APS you can get ATP inquiry based on planning output.In OM, you cannot see the component availability whereas you can see it in APS.
    The ATP/CTP based planning ouput option is chosen if you are running a collection program in the ASCP module and a plan based on the collected data pulled ealier.In this case you have to define a plan and check ATP flag and define options and then run the plan.Then the option ATP/CTP based planning oputput will give you the output based on the above plan.Without that it is as same as the ATP based on collection data(as in OM).
    Hope it helps.

  • Inconsistency between ATP and ASCP

    Thanks for looking at this message. Bit lengthy but will be interesting :-)
    In our implementation we use ATP based on planning output and its a constrained ASCP plan (ECC) .
    Assuming that sale sorders are available in the system and they have been entered say last month/ or even few months before with request date as the sale order entry date . We did nt have onhand at the time due to which the promise dates have been Sep-09.
    Assume that we have made a receipt from supplier/or there is PO in receiving (considered as available date of today by ATP) . In this situation in case a new sales order is entered today with request date of today provided the onhand or expected receipt today is more than sales order qty , the promise date upon sales order entry is today. We do OM loopback and send back sch ship date from ASCP which gives correct dates (Sep or Oct based on lead times). But issue is in the promise date .
    Issue 1: customer is questioning while there are so many existing sales orders which are already in arrears and their request dates are all in past months why does a new sales order get a promise date of today?
    When ASCP runs overnight it plans based on request date and the onhand/exp receipt is pegged to earliest sales order and not the new one put in today(which is fine and as expected) , but due to the mismatch between ATP and ASCP always there is going to be mismatch in meeting promise date and Sales performance measures go for a task.
    Also there all the customers are sent Order Acknowledgement (emailed upon booking order) based on the wrong promise date which causes lot of issues in explaining to each customer.
    Issue 2:lets say onhand is 2 and there are 2 sales order lines one for qty 8 (req date 21-jul) and other for qty 2 (req date 23-jul) . I schedule order line 8 (req date 21-jul) first then ATP promises line after LT (say Sep-09) and the qty 2 line is promised today but when ASCP is scheduling it has ability to see request date due to which it can peg 2 onhand to earlier request date and then wait for new supply till Sep-09. The one with later request date will show ship date in Sep-09.
    Have attached the screen shots explaining the issue 1 and 2
    Best regards
    Vinay

    Hi Vinayak
    Both of your observations are correct. As I managed ATP development for several years, let me help explain these things to you:
    1. For 1st issue, where a new incoming sales order can get better date than earlier promised sales order, please understand that ATP is based on supply/demand picture at a point in time when SO was originally processed. If supply/demand picture has changed significantly, you need to use a tool like Oracle Backlog WB to manage and re-process currently scheduled SO to re-assess where they should be promised. Once Sales Order is promised, ATP uses schedule ship date to see when material is needed and uses a supply closes to ship date (JIT). If earlier supplies are available, they're up for grabs by new SO.
    Thus, the behavior is working as designed and you need to develop your business process to ensure that backlog management is practiced on a regular basis to avoid such issues.
    2. For 2nd issue where you see that ATP isn't using supply to satisfy smaller qty sales order, please understand that ATP is "First-come-First-Serve" and it is working on 1 specific order at a time. When initial order of qty=8 came in, it had no way to know what lies in future or if another SO with qty=2 will come later. Compare this with ASCP which is working a complete set of supplies and demands and can analyze this picture in totality.
    I'm sure you'll like your ATP request to come back in few seconds (or may be a min or so) and not take a few hours while you enjoy the hourglass on your screen. No surprise that ASCP plan run takes few hours since it needs to go thru such hoops and try to optimize across these ideas while ATP is a quick answer as what can be done for this in-coming demand considering everything else in the system is frozen.
    Please note ATP and ASCP plan serve very different purpose and business process needs to be enahnced to take advantage of best of both these tools.
    Please feel free to contact me directly for any further issues in this respect.
    Regards
    Navneet Goel
    [email protected]

  • ATP Inquiry in OM

    I don;t have the APS modules installed, Can I still perform the ATP inquiry in 11i instance? Is the functionality the same as the one in the previous version.
    Can I use the ATP rules to do inquiry at the Order Header level

    Is there anything stuck in your Inventory transaction interface? (I assume you've checked this when you say you've looked at pending transactions).
    Did the ITS for the shipped order(s) complete? Have you checked for any unprocessed stops in the ITS submission?
    Are there any obvious anomalies for the item(s) concerned when you do an Inventory Supply/Demand query which might explain 'hidden' demand?
    Do you have any uncancelled and unprocessed pick release allocations for the item(s) concerned (check the Release Sales Order form)?

  • Can "ATP Inquiry" (Global Availability) works without GOP

    Could anyone please tell me what are the GOP (or ASCP) functionalities we lose if we remove these modules?
    Thanks,
    Senthil

    Right. That approach is the simplest. Or you can make an application Run Only by exporting it with that setting and importing/installing it leaving that setting as Run Only. Or you can export it with either setting and change the status to Run Only when you import/install it. Either way it makes the application un-editable by developers/workspace admins. You can also make the entire installation runtime-only where you don't even get an admin interface other than an API with which you can run to do administration. I think you have to use SQL*Plus or SQL Developer to install the applications in that situation.
    Scott

  • ATP FUNCTIONALITY NOT WORKING CORRECTLY FOR ATO Model

    Guru's,
    Currently I am facing issue in ATP Inquiry to arrive at schedule ship date, we have set up an ATO Model and its low-level parts for multi level ATP, including ATP rules, item attributes, bom attributes, and lead times and ATP check is based on planned output and enabled 24X7 plan.
    When try to perform ATP inquiry either from ASCP/OM responsibility, Instead of showing complete drill down of material constraint at the part level, it "stops" at the model level and shows no availability until the inifinte supply timefence, then unlimited availability after that.
    I was earlier able to view the complete ATP pegging details with ATP dates well within ITF, but however when we re run the plan to include additional SO the above behavior is observed.
    Can some one help me to reslove the issue, as I am not sure what exactly which is triggering this behavior.
    Thanks,

    Thanks for the reply, but this note was not addressing the above stated issue. In this note for matched configuration, they are not able to view pegging else they are able to perform multilevel atp check.
    Can anyone help me to reslove this issue.
    Thanks
    Edited by: user604737 on Jun 18, 2011 4:48 AM
    Edited by: user604737 on Jun 19, 2011 11:50 PM

  • ASCP Instance setup - DB LInk Creation in decentralized configuration

    I came across this question on setting up the APS for decentralized configuration and really couldn't find why? The question was why do we need to create two DB links (One in Source for destination db and other one in destination for source db) and can we setup ASCP instance by creating only one DB Link, either at destination or at source?
    Thanks
    Madhavi

    Hello,
    The reason for this is that there is 2 way communication for the planning products.
    On the planning instance the dblink is required when you run collections and release recommendations from the workbench (amongst other actions)
    on the source, when you perform for instance an ATP inquiry, data is being read from the aps instance.
    This is the design of ASCP. Both links are required.
    regards
    Geert

  • Information needed on ATP functinality based on collected data.

    Hi,
    we need to use ATP fuctionality in some of our ASCP scenarios.
    I have created FG items and components under them.
    Created onhand for components.
    Now if I do ATP inquiry for FG item , expecting it should give ATP quantity based on its component availabilty.
    But it is showing 0 only for whatever quantities or dates i query for .
    I had done setups like item ATP attributes,BOM check ATP,Profile option INV:Capable to promise based on collected data,Routing check CTP.
    Can any one confirm me whether it is the way it works or I need to do any specific setup.
    Thanks
    Vasudha.

    Hi
    Do want to use priority based on demand class? The prioritization of ASCP is diffrent from demand class prioritization. You will need to have a customization to assign demand class based prioity and update the demand lines to respect it by ASCP .
    Please try to use Allocated ATP . The use allocated ATP profile needs to be set to yes. There should be proper allcoation rule also setup based on demand class. But you cannot guarantee that the ASCP and ATP will be in sync
    Thnx
    partha

  • ATP across orgs

    Hi,
    Need a help in understanding ATP functionality in ASCP (unconstraint), please see example below.
    Org 1
    Item A , Item Type = Make to Order Item , Check ATP= Material Only ,ATP Components=Material Only , Forecast Control =Consume & Derive
    Item B Item Type =Internal Buy, Check ATP= Material Only, ATP Components=Material Only, Forecast Control =None, Sourcing Rule = Transfer from Org 2
    Org 2
    Item B Item Type =Internal Make, Check ATP= Material Only, ATP Components=Material Only, Forecast Control =CONSUME &DERIVE
    Item C Item Type = Buy, Check ATP= Material Only, ATP Components=Material Only
    When we perform ATP Inquiry for Item A in Org 1 (there is no material On hand for Item A & B in Org1), ATP just looking materials in org 1 up to item B then it's returning date with Material Constraint with out looking material availability in Org 2, so it's not checking across orgs my testing shows it's due to Forecast Control =CONSUME &DERIVE set for Item B in Org 2.
    I have similar items for which Forecast Control flag at Org 2 set to none; ATP is working fine by looking all supply in two orgs before returning ship date.
    Since item B is forecasted using ODP in Org 2 we set flag to Consume & Derive but not understanding why it will stop ATP to look across orgs.
    Please advice.
    Thanks,
    Sudhakar

    Have you got your sourcing rules and sourcing rule assignments set up so they model your entire supply chain? Eg in the org from which you are selling from, you need have a rule which says something like buy from another org and in that other org you need a sourcing rule and assignment which states where that org gets it from. Eg buy from a supplier.
    Also try ATP in trace mode (available from tools menu) and ATP with planned data (vs collected data).

  • OM 11i ATP Checking

    I have questions regarding ATP checking in Order Management R11i. I have defined an item with Check ATP = Material only. The ATP Rule attached to this item has Infinite Supply = 15 days. There is no Supply or Demand for this item at this point.
    When I perform Scheduling from the Sales Order form Availability Button, it indicates that the ordered qty is available even though there is no Supply.
    However, when I perform an ATP Inquiry from the Inventory form - I do receive an ATP date which is 15 days into the future.
    Does anyone have similar experiences with OM Scheduling functionality.
    Thanks for your help.
    Mike Kudo

    1. Make sure you have run the ATP Data Collection as a complete refresh since creating or assigning or updating any ATP Rules.
    2. Check the following defaulting rules:-
    -Order Line, Schedule Ship Date = Related Record, Ship Set
    - Order Header, Latest Acceptable Date = Constant Value, 500 (use whatever value you like but at least this will cover most cases). Null behaves as zero days and means that no schedule date is good enough.
    - Run the 'Defaulting Generator' from OM (Run Requests) after updating these rules.
    3. For the ATPable items, make sure that the ATP Components item attribute is set to 'No'. The system can get confused if this is wrong & give such unpredictable results.
    4. Try the following system profile option setting:-
    INV: Capable to Promise = Enable PL/SQL based ATP without Planning Output
    5. What is the value of the OM: AutoSchedule profile option ... YES or NO ? From what you have described, I assume you are manually scheduling so this would be set to 'NO'.
    This is based on having very recently set up a heavily patched 11.5.3 (more like 11.5.4) instance.

  • Substitute components for ATP

    Hi All,
    I have substitute components set in BOM. Substitute component has enough excess onhand. ATP plan is considering component substitution whereever required to satisfy demand. But ATP inquiry is considering only primary component(if no supply for primary then its using primary component lead time even if substitute components have enough onhand). I have set MRP: Include Substitute Components profile option to yes. We are using 11.5.10.2.
    Am i missing any setup?
    Regards,
    Deepak

    Hi Deepak
    Please try using 'Diagnostics ATP' to see why your request isn't being met on-time. It can be possible due to Lead Time or capacity issues and when these issues are resolved, you may already have primary components available.
    Thanks
    Navneet Goel

  • ATP Not Applicable.

    I am getting following message while doing an ATP enquiry.
    I have set-up ATP Rules and enabled items for ATP check.
    What are the other set-ups required to remove this message ?

    Check out the log for your Pick Release List Generation. Also check to see if a picklist was generated and if it has data. View/Requests - Find all requests.
    How did you release the order - Did you use the OM SuperUser/Shipping/Release Sales Order? If so, did you specify a pick release rule that picks from the place where you have the inventory? Did you the Shipping/Transactions form? That uses the default pick release rule you have in your org setup.
    Ready to Release means it has not been release yet. It should either backorder or stage if the picking actually happens.

  • Same dates for GA and GR in ATP

    Hi All,
    This is my very first post. I have a situation where for an Inbound delivery. I should have 2 days difference in Goods arrival and goods receipt in plant. For some reason system is showing the same dates for Goods arrival and goods Receipt. Can someone help me what all tolook for?
    Many thanks
    YS

    ATO Items/ Models have significant complex requirements and behavior when ATP check is called. While this is handled appropriately in ATP from OM interface, direct ATP Inquiry either from APS responsibility or similar form in OM--> Scheduling menu option.
    I'll highly suggest not to use either of these ATP Inquiry forms for anything related to CTO (ATO, PTO etc) and only use OM UI for such availability checks. This is by design unless Oracle makes significant changes to how these forms are built, please note there is no configurator support from these 2 forms for similar reasons.
    Thanks
    Navneet Goel

  • --enable-compat185 problem?

    I am installing dsniff on Linux (Fedora 10) to test a private network and the installation requires Berkeley DB, 1.85 application compatible. I followed instructions found in the installation guide and Oracle website and did:
    +[root@alphaone build_unix]# ../dist/configure --enable-compat185+
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking if building in the top-level or dist directories... no
    +checking if --disable-cryptography option specified... no+
    +checking if --disable-hash option specified... no+
    +checking if --disable-mutexsupport option specified... no+
    +checking if --disable-queue option specified... no+
    +checking if --disable-replication option specified... no+
    +checking if --disable-statistics option specified... no+
    +checking if --disable-verify option specified... no+
    +checking if --enable-compat185 option specified... yes+
    +checking if --enable-cxx option specified... no+
    +checking if --enable-debug option specified... no+
    +checking if --enable-debug_rop option specified... no+
    +checking if --enable-debug_wop option specified... no+
    +checking if --enable-diagnostic option specified... no+
    +checking if --enable-dump185 option specified... no+
    +checking if --enable-java option specified... no+
    +checking if --enable-mingw option specified... no+
    +checking if --enable-o_direct option specified... no+
    +checking if --enable-posixmutexes option specified... no+
    +checking if --enable-pthread_api option specified... no+
    +checking if --enable-rpc option specified... no+
    +checking if --enable-smallbuild option specified... no+
    +checking if --enable-tcl option specified... no+
    +checking if --enable-test option specified... no+
    +checking if --enable-uimutexes option specified... no+
    +checking if --enable-umrw option specified... no+
    +checking if --with-mutex=MUTEX option specified... no+
    +checking if --with-tcl=DIR option specified... no+
    +checking if --with-uniquename=NAME option specified... no+
    checking for chmod... chmod
    checking for cp... cp
    checking for ln... ln
    checking for mkdir... mkdir
    checking for rm... rm
    checking for sh... /bin/sh
    checking for a BSD-compatible install... /usr/bin/install -c
    checking for cc... cc
    checking for C compiler default output file name... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables...
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether cc accepts -g... yes
    checking for cc option to accept ISO C89... none needed
    checking for an ANSI C-conforming const... yes
    checking for inline... inline
    checking whether we are using gcc version 2.96... no
    checking whether g+ requires -fhandle-exceptions... no+
    checking for a sed that does not truncate output... /bin/sed
    checking for grep that handles long lines and -e... /bin/grep
    checking for egrep... /bin/grep -E
    checking for ld used by cc... /usr/bin/ld
    checking if the linker (/usr/bin/ld) is GNU ld... yes
    checking for /usr/bin/ld option to reload object files... -r
    checking for BSD-compatible nm... /usr/bin/nm -B
    checking whether ln -s works... yes
    checking how to recognise dependent libraries... pass_all
    checking how to run the C preprocessor... cc -E
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for g77... no
    checking for xlf... no
    checking for f77... no
    checking for frt... no
    checking for pgf77... no
    checking for cf77... no
    checking for fort77... no
    checking for fl32... no
    checking for af77... no
    checking for xlf90... no
    checking for f90... no
    checking for pgf90... no
    checking for pghpf... no
    checking for epcf90... no
    checking for gfortran... no
    checking for g95... no
    checking for xlf95... no
    checking for f95... no
    checking for fort... no
    checking for ifort... no
    checking for ifc... no
    checking for efc... no
    checking for pgf95... no
    checking for lf95... no
    checking for ftn... no
    checking whether we are using the GNU Fortran 77 compiler... no
    checking whether  accepts -g... no
    checking the maximum length of command line arguments... 32768
    checking command to parse /usr/bin/nm -B output from cc object... ok
    checking for objdir... .libs
    checking for ar... ar
    checking for ranlib... ranlib
    checking for strip... strip
    checking if cc supports -fno-rtti -fno-exceptions... no
    checking for cc option to produce PIC... -fPIC
    checking if cc PIC flag -fPIC works... yes
    checking if cc static flag -static works... yes
    checking if cc supports -c -o file.o... yes
    checking whether the cc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
    checking whether -lc should be explicitly linked in... no
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    configure: creating libtool
    appending configuration tag "CXX" to libtool
    appending configuration tag "F77" to libtool
    checking SOSUFFIX from libtool... .so
    checking MODSUFFIX from libtool... .so
    checking JMODSUFFIX from libtool... .so
    checking whether stat file-mode macros are broken... no
    checking whether time.h and sys/time.h may both be included... yes
    checking for dirent.h that defines DIR... yes
    checking for library containing opendir... none required
    checking execinfo.h usability... yes
    checking execinfo.h presence... yes
    checking for execinfo.h... yes
    checking sys/select.h usability... yes
    checking sys/select.h presence... yes
    checking for sys/select.h... yes
    checking sys/socket.h usability... yes
    checking sys/socket.h presence... yes
    checking for sys/socket.h... yes
    checking sys/time.h usability... yes
    checking sys/time.h presence... yes
    checking for sys/time.h... yes
    checking for struct stat.st_blksize... yes
    checking for inttypes.h... (cached) yes
    checking for stdint.h... yes
    checking stddef.h usability... yes
    checking stddef.h presence... yes
    checking for stddef.h... yes
    checking for unistd.h... (cached) yes
    checking for char... yes
    checking size of char... 1
    checking for unsigned char... yes
    checking size of unsigned char... 1
    checking for short... yes
    checking size of short... 2
    checking for unsigned short... yes
    checking size of unsigned short... 2
    checking for int... yes
    checking size of int... 4
    checking for unsigned int... yes
    checking size of unsigned int... 4
    checking for long... yes
    checking size of long... 8
    checking for unsigned long... yes
    checking size of unsigned long... 8
    checking for long long... yes
    checking size of long long... 8
    checking for unsigned long long... yes
    checking size of unsigned long long... 8
    checking for char *... yes
    checking size of char *... 8
    checking for u_char... yes
    checking for u_short... yes
    checking for u_int... yes
    checking for u_long... yes
    checking for u_int8_t... yes
    checking for u_int16_t... yes
    checking for int16_t... yes
    checking for u_int32_t... yes
    checking for int32_t... yes
    checking for u_int64_t... yes
    checking for int64_t... yes
    checking for FILE *... yes
    checking for off_t... yes
    checking for pid_t... yes
    checking for size_t... yes
    checking for time_t... yes
    checking for size_t... (cached) yes
    checking size of size_t... 8
    checking for ssize_t... yes
    checking for uintmax_t... yes
    checking for uintptr_t... yes
    checking for socklen_t... yes
    checking for ANSI C exit success/failure values... yes
    checking for getopt optreset variable... no
    checking for mutexes... POSIX/pthreads/library/x86_64/gcc-assembly
    checking for main in -lpthread... yes
    checking for library containing sched_yield... none required
    checking for library containing fdatasync... none required
    checking for library containing getaddrinfo... none required
    checking for library containing hstrerror... none required
    checking for main in -lm... yes
    checking for main in -lnsl... yes
    checking for main in -lpthread... (cached) yes
    checking for main in -lsocket... no
    checking for abort... yes
    checking for atoi... yes
    checking for atol... yes
    checking for getcwd... yes
    checking for getenv... yes
    checking for getopt... yes
    checking for isalpha... yes
    checking for isdigit... yes
    checking for isprint... yes
    checking for isspace... yes
    checking for memcmp... yes
    checking for memcpy... yes
    checking for memmove... yes
    checking for printf... yes
    checking for qsort... yes
    checking for raise... yes
    checking for rand... yes
    checking for strcasecmp... yes
    checking for strcat... yes
    checking for strchr... yes
    checking for strdup... yes
    checking for strerror... yes
    checking for strncat... yes
    checking for strncmp... yes
    checking for strrchr... yes
    checking for strsep... yes
    checking for strtol... yes
    checking for strtoul... yes
    +checking for _fstati64... no+
    checking for backtrace... yes
    checking for backtrace_symbols... yes
    checking for directio... no
    checking for fchmod... yes
    checking for fclose... yes
    checking for fcntl... yes
    checking for fdatasync... yes
    checking for fgetc... yes
    checking for fgets... yes
    checking for fopen... yes
    checking for fwrite... yes
    checking for getgid... yes
    checking for getrusage... yes
    checking for getuid... yes
    checking for hstrerror... yes
    checking for mprotect... yes
    checking for pstat_getdynamic... no
    checking for pthread_yield... yes
    checking for sched_yield... yes
    checking for select... yes
    checking for setgid... yes
    checking for setuid... yes
    checking for sigaction... yes
    checking for snprintf... yes
    checking for stat... yes
    checking for sysconf... yes
    checking for vsnprintf... yes
    checking for yield... no
    checking for gettimeofday... yes
    checking for localtime... yes
    checking for time... yes
    checking for strftime... yes
    checking for clock_gettime... no
    checking for clock_gettime monotonic clock... no
    checking for ctime_r... yes
    checking for 2 or 3 argument version of ctime_r... 2-argument
    checking for ftruncate... yes
    checking for pread... yes
    checking for pwrite... yes
    checking for getaddrinfo... yes
    checking for fcntl/F_SETFD... yes
    checking for special C compiler options needed for large files... no
    +checking for FILEOFFSET_BITS value needed for large files... no+
    checking for mlock... yes
    checking for munlock... yes
    checking for mmap... yes
    checking for munmap... yes
    checking for shmget... yes
    checking for shmctl... yes
    checking for 64-bit integral type support for sequences... yes
    configure: creating ./config.status
    config.status: creating Makefile
    config.status: creating db_cxx.h
    config.status: creating db_int.h
    config.status: creating clib_port.h
    config.status: creating include.tcl
    config.status: creating db.h
    config.status: creating db_185.h
    config.status: creating db185_int.h
    config.status: creating db_config.h
    config.status: db_config.h is unchanged
    +[root@alphaone build_unix]# make+
    +/bin/sh ./libtool --mode=compile cc -c -I. -I../dist/..  -D_GNU_SOURCE -D_REENTRANT -O3  ../dist/../db185/db185.c+
    cc -c -I. -I../dist/.. -D_GNU_SOURCE -D_REENTRANT -O3 ../dist/../db185/db185.c  -fPIC -DPIC -o .libs/db185.o
    cc -c -I. -I../dist/.. -D_GNU_SOURCE -D_REENTRANT -O3 ../dist/../db185/db185.c -o db185.o >/dev/null 2>&1
    +/bin/sh ./libtool --mode=link cc -avoid-version -O3  -rpath /usr/local/BerkeleyDB.4.7/lib  -o libdb-4.7.la db185.lo mut_tas.lo mut_pthread.lo  bt_compare.lo bt_conv.lo bt_curadj.lo bt_cursor.lo bt_delete.lo bt_method.lo bt_open.lo bt_put.lo bt_rec.lo bt_reclaim.lo bt_recno.lo bt_rsearch.lo bt_search.lo bt_split.lo bt_stat.lo bt_compact.lo bt_upgrade.lo btree_auto.lo hash.lo hash_auto.lo hash_conv.lo hash_dup.lo hash_meta.lo hash_method.lo hash_open.lo hash_page.lo hash_rec.lo hash_reclaim.lo hash_stat.lo hash_upgrade.lo hash_verify.lo qam.lo qam_auto.lo qam_conv.lo qam_files.lo qam_method.lo qam_open.lo qam_rec.lo qam_stat.lo qam_upgrade.lo qam_verify.lo rep_auto.lo rep_backup.lo rep_elect.lo rep_lease.lo rep_log.lo rep_method.lo rep_record.lo rep_region.lo rep_stat.lo rep_util.lo rep_verify.lo os_addrinfo.lo repmgr_auto.lo repmgr_elect.lo repmgr_method.lo repmgr_msg.lo repmgr_net.lo repmgr_posix.lo repmgr_queue.lo repmgr_sel.lo repmgr_stat.lo repmgr_util.lo db_ovfl_vrfy.lo db_vrfy.lo db_vrfyutil.lo bt_verify.lo lock.lo lock_deadlock.lo lock_failchk.lo lock_id.lo lock_list.lo lock_method.lo lock_region.lo lock_stat.lo lock_timer.lo lock_util.lo mut_alloc.lo mut_failchk.lo mut_method.lo mut_region.lo mut_stat.lo  aes_method.lo crypto.lo mt19937db.lo rijndael-alg-fst.lo rijndael-api-fst.lo crdel_auto.lo crdel_rec.lo db.lo db_am.lo db_auto.lo db_byteorder.lo db_cam.lo db_cds.lo db_conv.lo db_dispatch.lo db_dup.lo db_err.lo db_getlong.lo db_idspace.lo db_iface.lo db_join.lo db_log2.lo db_meta.lo db_method.lo db_open.lo db_overflow.lo db_pr.lo db_rec.lo db_reclaim.lo db_remove.lo db_rename.lo db_ret.lo db_setid.lo db_setlsn.lo db_shash.lo db_stati.lo db_truncate.lo db_upg.lo db_upg_opd.lo dbm.lo dbreg.lo dbreg_auto.lo dbreg_rec.lo dbreg_stat.lo dbreg_util.lo dbt.lo env_alloc.lo env_config.lo env_failchk.lo env_file.lo env_globals.lo env_method.lo env_name.lo env_open.lo env_recover.lo env_region.lo env_register.lo env_sig.lo env_stat.lo fileops_auto.lo fop_basic.lo fop_rec.lo fop_util.lo hash_func.lo hmac.lo hsearch.lo log.lo log_archive.lo log_compare.lo log_debug.lo log_get.lo log_method.lo log_put.lo log_stat.lo mkpath.lo mp_alloc.lo mp_bh.lo mp_fget.lo mp_fmethod.lo mp_fopen.lo mp_fput.lo mp_fset.lo mp_method.lo mp_mvcc.lo mp_region.lo mp_register.lo mp_resize.lo mp_stat.lo mp_sync.lo mp_trickle.lo openflags.lo os_abort.lo os_abs.lo os_alloc.lo os_clock.lo os_cpu.lo os_ctime.lo os_config.lo os_dir.lo os_errno.lo os_fid.lo os_flock.lo os_fsync.lo os_getenv.lo os_handle.lo os_map.lo os_method.lo os_mkdir.lo os_open.lo os_pid.lo os_rename.lo os_root.lo os_rpath.lo os_rw.lo os_seek.lo os_stack.lo os_stat.lo os_tmpdir.lo os_truncate.lo os_uid.lo os_unlink.lo os_yield.lo seq_stat.lo sequence.lo sha1.lo snprintf.lo txn.lo txn_auto.lo txn_chkpt.lo txn_failchk.lo txn_method.lo txn_rec.lo txn_recover.lo txn_region.lo txn_stat.lo txn_util.lo xa.lo xa_db.lo xa_map.lo zerofill.lo -lpthread+
    rm -fr  .libs/libdb-4.7.a .libs/libdb-4.7.la .libs/libdb-4.7.lai .libs/libdb-4.7.so
    cc -shared  .libs/db185.o .libs/mut_tas.o .libs/mut_pthread.o .libs/bt_compare.o .libs/bt_conv.o .libs/bt_curadj.o .libs/bt_cursor.o .libs/bt_delete.o .libs/bt_method.o .libs/bt_open.o .libs/bt_put.o .libs/bt_rec.o .libs/bt_reclaim.o .libs/bt_recno.o .libs/bt_rsearch.o .libs/bt_search.o .libs/bt_split.o .libs/bt_stat.o .libs/bt_compact.o .libs/bt_upgrade.o .libs/btree_auto.o .libs/hash.o .libs/hash_auto.o .libs/hash_conv.o .libs/hash_dup.o .libs/hash_meta.o .libs/hash_method.o .libs/hash_open.o .libs/hash_page.o .libs/hash_rec.o .libs/hash_reclaim.o .libs/hash_stat.o .libs/hash_upgrade.o .libs/hash_verify.o .libs/qam.o .libs/qam_auto.o .libs/qam_conv.o .libs/qam_files.o .libs/qam_method.o .libs/qam_open.o .libs/qam_rec.o .libs/qam_stat.o .libs/qam_upgrade.o .libs/qam_verify.o .libs/rep_auto.o .libs/rep_backup.o .libs/rep_elect.o .libs/rep_lease.o .libs/rep_log.o .libs/rep_method.o .libs/rep_record.o .libs/rep_region.o .libs/rep_stat.o .libs/rep_util.o .libs/rep_verify.o .libs/os_addrinfo.o .libs/repmgr_auto.o .libs/repmgr_elect.o .libs/repmgr_method.o .libs/repmgr_msg.o .libs/repmgr_net.o .libs/repmgr_posix.o .libs/repmgr_queue.o .libs/repmgr_sel.o .libs/repmgr_stat.o .libs/repmgr_util.o .libs/db_ovfl_vrfy.o .libs/db_vrfy.o .libs/db_vrfyutil.o .libs/bt_verify.o .libs/lock.o .libs/lock_deadlock.o .libs/lock_failchk.o .libs/lock_id.o .libs/lock_list.o .libs/lock_method.o .libs/lock_region.o .libs/lock_stat.o .libs/lock_timer.o .libs/lock_util.o .libs/mut_alloc.o .libs/mut_failchk.o .libs/mut_method.o .libs/mut_region.o .libs/mut_stat.o .libs/aes_method.o .libs/crypto.o .libs/mt19937db.o .libs/rijndael-alg-fst.o .libs/rijndael-api-fst.o .libs/crdel_auto.o .libs/crdel_rec.o .libs/db.o .libs/db_am.o .libs/db_auto.o .libs/db_byteorder.o .libs/db_cam.o .libs/db_cds.o .libs/db_conv.o .libs/db_dispatch.o .libs/db_dup.o .libs/db_err.o .libs/db_getlong.o .libs/db_idspace.o .libs/db_iface.o .libs/db_join.o .libs/db_log2.o .libs/db_meta.o .libs/db_method.o .libs/db_open.o .libs/db_overflow.o .libs/db_pr.o .libs/db_rec.o .libs/db_reclaim.o .libs/db_remove.o .libs/db_rename.o .libs/db_ret.o .libs/db_setid.o .libs/db_setlsn.o .libs/db_shash.o .libs/db_stati.o .libs/db_truncate.o .libs/db_upg.o .libs/db_upg_opd.o .libs/dbm.o .libs/dbreg.o .libs/dbreg_auto.o .libs/dbreg_rec.o .libs/dbreg_stat.o .libs/dbreg_util.o .libs/dbt.o .libs/env_alloc.o .libs/env_config.o .libs/env_failchk.o .libs/env_file.o .libs/env_globals.o .libs/env_method.o .libs/env_name.o .libs/env_open.o .libs/env_recover.o .libs/env_region.o .libs/env_register.o .libs/env_sig.o .libs/env_stat.o .libs/fileops_auto.o .libs/fop_basic.o .libs/fop_rec.o .libs/fop_util.o .libs/hash_func.o .libs/hmac.o .libs/hsearch.o .libs/log.o .libs/log_archive.o .libs/log_compare.o .libs/log_debug.o .libs/log_get.o .libs/log_method.o .libs/log_put.o .libs/log_stat.o .libs/mkpath.o .libs/mp_alloc.o .libs/mp_bh.o .libs/mp_fget.o .libs/mp_fmethod.o .libs/mp_fopen.o .libs/mp_fput.o .libs/mp_fset.o .libs/mp_method.o .libs/mp_mvcc.o .libs/mp_region.o .libs/mp_register.o .libs/mp_resize.o .libs/mp_stat.o .libs/mp_sync.o .libs/mp_trickle.o .libs/openflags.o .libs/os_abort.o .libs/os_abs.o .libs/os_alloc.o .libs/os_clock.o .libs/os_cpu.o .libs/os_ctime.o .libs/os_config.o .libs/os_dir.o .libs/os_errno.o .libs/os_fid.o .libs/os_flock.o .libs/os_fsync.o .libs/os_getenv.o .libs/os_handle.o .libs/os_map.o .libs/os_method.o .libs/os_mkdir.o .libs/os_open.o .libs/os_pid.o .libs/os_rename.o .libs/os_root.o .libs/os_rpath.o .libs/os_rw.o .libs/os_seek.o .libs/os_stack.o .libs/os_stat.o .libs/os_tmpdir.o .libs/os_truncate.o .libs/os_uid.o .libs/os_unlink.o .libs/os_yield.o .libs/seq_stat.o .libs/sequence.o .libs/sha1.o .libs/snprintf.o .libs/txn.o .libs/txn_auto.o .libs/txn_chkpt.o .libs/txn_failchk.o .libs/txn_method.o .libs/txn_rec.o .libs/txn_recover.o .libs/txn_region.o .libs/txn_stat.o .libs/txn_util.o .libs/xa.o .libs/xa_db.o .libs/xa_map.o .libs/zerofill.o  -lpthread  -Wl,-soname -Wl,libdb-4.7.so -o .libs/libdb-4.7.so
    ar cru .libs/libdb-4.7.a  db185.o mut_tas.o mut_pthread.o bt_compare.o bt_conv.o bt_curadj.o bt_cursor.o bt_delete.o bt_method.o bt_open.o bt_put.o bt_rec.o bt_reclaim.o bt_recno.o bt_rsearch.o bt_search.o bt_split.o bt_stat.o bt_compact.o bt_upgrade.o btree_auto.o hash.o hash_auto.o hash_conv.o hash_dup.o hash_meta.o hash_method.o hash_open.o hash_page.o hash_rec.o hash_reclaim.o hash_stat.o hash_upgrade.o hash_verify.o qam.o qam_auto.o qam_conv.o qam_files.o qam_method.o qam_open.o qam_rec.o qam_stat.o qam_upgrade.o qam_verify.o rep_auto.o rep_backup.o rep_elect.o rep_lease.o rep_log.o rep_method.o rep_record.o rep_region.o rep_stat.o rep_util.o rep_verify.o os_addrinfo.o repmgr_auto.o repmgr_elect.o repmgr_method.o repmgr_msg.o repmgr_net.o repmgr_posix.o repmgr_queue.o repmgr_sel.o repmgr_stat.o repmgr_util.o db_ovfl_vrfy.o db_vrfy.o db_vrfyutil.o bt_verify.o lock.o lock_deadlock.o lock_failchk.o lock_id.o lock_list.o lock_method.o lock_region.o lock_stat.o lock_timer.o lock_util.o mut_alloc.o mut_failchk.o mut_method.o mut_region.o mut_stat.o aes_method.o crypto.o mt19937db.o rijndael-alg-fst.o rijndael-api-fst.o crdel_auto.o crdel_rec.o db.o db_am.o db_auto.o db_byteorder.o db_cam.o db_cds.o db_conv.o db_dispatch.o db_dup.o db_err.o db_getlong.o db_idspace.o db_iface.o db_join.o db_log2.o db_meta.o db_method.o db_open.o db_overflow.o db_pr.o db_rec.o db_reclaim.o db_remove.o db_rename.o db_ret.o db_setid.o db_setlsn.o db_shash.o db_stati.o db_truncate.o db_upg.o db_upg_opd.o dbm.o dbreg.o dbreg_auto.o dbreg_rec.o dbreg_stat.o dbreg_util.o dbt.o env_alloc.o env_config.o env_failchk.o env_file.o env_globals.o env_method.o env_name.o env_open.o env_recover.o env_region.o env_register.o env_sig.o env_stat.o fileops_auto.o fop_basic.o fop_rec.o fop_util.o hash_func.o hmac.o hsearch.o log.o log_archive.o log_compare.o log_debug.o log_get.o log_method.o log_put.o log_stat.o mkpath.o mp_alloc.o mp_bh.o mp_fget.o mp_fmethod.o mp_fopen.o mp_fput.o mp_fset.o mp_method.o mp_mvcc.o mp_region.o mp_register.o mp_resize.o mp_stat.o mp_sync.o mp_trickle.o openflags.o os_abort.o os_abs.o os_alloc.o os_clock.o os_cpu.o os_ctime.o os_config.o os_dir.o os_errno.o os_fid.o os_flock.o os_fsync.o os_getenv.o os_handle.o os_map.o os_method.o os_mkdir.o os_open.o os_pid.o os_rename.o os_root.o os_rpath.o os_rw.o os_seek.o os_stack.o os_stat.o os_tmpdir.o os_truncate.o os_uid.o os_unlink.o os_yield.o seq_stat.o sequence.o sha1.o snprintf.o txn.o txn_auto.o txn_chkpt.o txn_failchk.o txn_method.o txn_rec.o txn_recover.o txn_region.o txn_stat.o txn_util.o xa.o xa_db.o xa_map.o zerofill.o
    ranlib .libs/libdb-4.7.a
    creating libdb-4.7.la
    +(cd .libs && rm -f libdb-4.7.la && ln -s ../libdb-4.7.la libdb-4.7.la)+
    rm -f libdb.a
    ln -s .libs/libdb-4.7.a libdb.a
    +/bin/sh ./libtool --mode=link cc -O3  -o db_archive  \+
    +     db_archive.lo util_sig.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_archive .libs/db_archive.o .libs/util_sig.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_archive
    +/bin/sh ./libtool --mode=execute true db_archive+
    +/bin/sh ./libtool --mode=link cc -O3  -o db_checkpoint  \+
    +     db_checkpoint.lo util_log.lo util_sig.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_checkpoint .libs/db_checkpoint.o .libs/util_log.o .libs/util_sig.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_checkpoint
    +/bin/sh ./libtool --mode=execute true db_checkpoint+
    +/bin/sh ./libtool --mode=link cc -O3  -o db_codegen  \+
    +     db_codegen.lo code_capi.lo code_parse.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_codegen .libs/db_codegen.o .libs/code_capi.o .libs/code_parse.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_codegen
    +/bin/sh ./libtool --mode=execute true db_codegen+
    +/bin/sh ./libtool --mode=link cc -O3  -o db_deadlock  \+
    +     db_deadlock.lo util_log.lo util_sig.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_deadlock .libs/db_deadlock.o .libs/util_log.o .libs/util_sig.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_deadlock
    +/bin/sh ./libtool --mode=execute true db_deadlock+
    +/bin/sh ./libtool --mode=link cc -O3  -o db_dump  \+
    +     db_dump.lo util_cache.lo util_sig.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_dump .libs/db_dump.o .libs/util_cache.o .libs/util_sig.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_dump
    +/bin/sh ./libtool --mode=execute true db_dump+
    +/bin/sh ./libtool --mode=link cc -O3  -o db_hotbackup  \+
    +     db_hotbackup.lo util_sig.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_hotbackup .libs/db_hotbackup.o .libs/util_sig.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_hotbackup
    +/bin/sh ./libtool --mode=execute true db_hotbackup+
    +/bin/sh ./libtool --mode=link cc -O3  -o db_load  \+
    +     db_load.lo util_cache.lo util_sig.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_load .libs/db_load.o .libs/util_cache.o .libs/util_sig.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_load
    +/bin/sh ./libtool --mode=execute true db_load+
    +/bin/sh ./libtool --mode=link cc -O3  -o db_printlog  \+
    +     db_printlog.lo btree_autop.lo crdel_autop.lo db_autop.lo dbreg_autop.lo fileops_autop.lo hash_autop.lo qam_autop.lo txn_autop.lo util_sig.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_printlog .libs/db_printlog.o .libs/btree_autop.o .libs/crdel_autop.o .libs/db_autop.o .libs/dbreg_autop.o .libs/fileops_autop.o .libs/hash_autop.o .libs/qam_autop.o .libs/txn_autop.o .libs/util_sig.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_printlog
    +/bin/sh ./libtool --mode=execute true db_printlog+
    +/bin/sh ./libtool --mode=link cc -O3  -o db_recover  \+
    +     db_recover.lo util_sig.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_recover .libs/db_recover.o .libs/util_sig.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_recover
    +/bin/sh ./libtool --mode=execute true db_recover+
    +/bin/sh ./libtool --mode=link cc -O3  -o db_stat  \+
    +     db_stat.lo util_cache.lo util_sig.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_stat .libs/db_stat.o .libs/util_cache.o .libs/util_sig.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_stat
    +/bin/sh ./libtool --mode=execute true db_stat+
    +/bin/sh ./libtool --mode=link cc -O3  -o db_upgrade  \+
    +     db_upgrade.lo util_sig.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_upgrade .libs/db_upgrade.o .libs/util_sig.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_upgrade
    +/bin/sh ./libtool --mode=execute true db_upgrade+
    +/bin/sh ./libtool --mode=link cc -O3  -o db_verify  \+
    +     db_verify.lo util_cache.lo util_sig.lo libdb-4.7.la -lpthread+
    cc -O3 -o .libs/db_verify .libs/db_verify.o .libs/util_cache.o .libs/util_sig.o  ./.libs/libdb-4.7.so -lpthread  -Wl,--rpath -Wl,/usr/local/BerkeleyDB.4.7/lib
    creating db_verify
    +/bin/sh ./libtool --mode=execute true db_verify+
    You have new mail in /var/spool/mail/root
    +[root@alphaone build_unix]# make install+
    Installing DB include files: /usr/local/BerkeleyDB.4.7/include ...
    Installing DB library: /usr/local/BerkeleyDB.4.7/lib ...
    cp -p .libs/libdb-4.7.so /usr/local/BerkeleyDB.4.7/lib/libdb-4.7.so
    cp -p .libs/libdb-4.7.lai /usr/local/BerkeleyDB.4.7/lib/libdb-4.7.la
    cp -p .libs/libdb-4.7.a /usr/local/BerkeleyDB.4.7/lib/libdb-4.7.a
    chmod 644 /usr/local/BerkeleyDB.4.7/lib/libdb-4.7.a
    ranlib /usr/local/BerkeleyDB.4.7/lib/libdb-4.7.a
    cp -p libdb.a /usr/local/BerkeleyDB.4.7/lib/libdb.a
    chmod 644 /usr/local/BerkeleyDB.4.7/lib/libdb.a
    ranlib /usr/local/BerkeleyDB.4.7/lib/libdb.a
    PATH="$PATH:/sbin" ldconfig -n /usr/local/BerkeleyDB.4.7/lib
    Libraries have been installed in:
    +/usr/local/BerkeleyDB.4.7/lib+
    If you ever happen to want to link against installed libraries
    in a given directory, LIBDIR, you must either use libtool, and
    specify the full pathname of the library, or use the `-LLIBDIR'
    flag during linking and do at least one of the following:
    - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
    during execution
    - add LIBDIR to the `LD_RUN_PATH' environment variable
    during linking
    - use the `-Wl,--rpath -Wl,LIBDIR' linker flag
    - have your system administrator add LIBDIR to `/etc/ld.so.conf'
    See any operating system documentation about shared libraries for
    more information, such as the ld(1) and ld.so(8) manual pages.
    Installing DB utilities: /usr/local/BerkeleyDB.4.7/bin ...
    cp -p .libs/db_archive /usr/local/BerkeleyDB.4.7/bin/db_archive
    cp -p .libs/db_checkpoint /usr/local/BerkeleyDB.4.7/bin/db_checkpoint
    cp -p .libs/db_codegen /usr/local/BerkeleyDB.4.7/bin/db_codegen
    cp -p .libs/db_deadlock /usr/local/BerkeleyDB.4.7/bin/db_deadlock
    cp -p .libs/db_dump /usr/local/BerkeleyDB.4.7/bin/db_dump
    cp -p .libs/db_hotbackup /usr/local/BerkeleyDB.4.7/bin/db_hotbackup
    cp -p .libs/db_load /usr/local/BerkeleyDB.4.7/bin/db_load
    cp -p .libs/db_printlog /usr/local/BerkeleyDB.4.7/bin/db_printlog
    cp -p .libs/db_recover /usr/local/BerkeleyDB.4.7/bin/db_recover
    cp -p .libs/db_stat /usr/local/BerkeleyDB.4.7/bin/db_stat
    cp -p .libs/db_upgrade /usr/local/BerkeleyDB.4.7/bin/db_upgrade
    cp -p .libs/db_verify /usr/local/BerkeleyDB.4.7/bin/db_verify
    Installing documentation: /usr/local/BerkeleyDB.4.7/docs ...
    Which all looks well until I try and finish the dsniff installation and get:
    +[root@alphaone build_unix]# cd+
    +[root@alphaone ~]# cd dsniff-2.3+
    +[root@alphaone dsniff-2.3]# ./configure+
    loading cache ./config.cache
    +............+
    checking for Berkeley DB with 1.85 compatibility... configure: error: Berkeley DB with 1.85 compatibility not found
    Have I done something wrong or is there a compatibility issue here?
    Thanks in advance for any help.

    Hi,
    If you are replacing an existing build that didn't include --enable-compat185 the first time, you'll want to do a 'make realclean' before reconfiguring and rebuilding Berkeley DB.
    On the other hand, you should know that it is possible that the program looking for Berkeley DB is not looking in the place in which you installed the Berkeley DB build. You can ask the support group for the software using DB how their software finds the DB library, they should be able to help you with this question.
    Please let me know if this worked.
    Thanks,
    Bogdan

Maybe you are looking for