Tag Archives: gnumake

Relink of module “FNDXIT.dll” failed

Posted by on June 25, 2012 No comments

Problem:

After applying patch 12964564, FNDCPASS.exe and FNDXIT.dll no longer link.

fdspwd.obj : error LNK2019: unresolved external symbol _read_db_case_sens refere
nced in function _pwdecp
fdspwd.obj : error LNK2019: unresolved external symbol _fdget_afmnu referenced i
n function _pwdecp
fdspwd.obj : error LNK2019: unresolved external symbol _fdget_afctx referenced i
n function _pwdecp
fdspwd.obj : error LNK2019: unresolved external symbol _fdinit_afmnu referenced
in function _pwdecp
fdspwd.obj : error LNK2019: unresolved external symbol _fdinit_afctx referenced
in function _pwdecp
fdspwd.obj : error LNK2019: unresolved external symbol _fdcr_afmnu referenced in
 function _pwdecp
fdspwd.obj : error LNK2019: unresolved external symbol _fdcr_afctx referenced in
 function _pwdecp
fdspwd.obj : error LNK2019: unresolved external symbol _pwdalt_merge referenced
in function _pwdalt_usrexit
C:/oracle/DEV1/apps/apps_st/appl/fnd/12.0.0/bin/FNDXIT.dll : fatal error LNK1120
: 8 unresolved externals
gnumake: *** [C:/oracle/DEV1/apps/apps_st/appl/fnd/12.0.0/bin/FNDXIT.dll] Error
96
Done with link of fnd executable 'FNDXIT.dll' on Sat Jun 23 15:32:39 SAWST 2012

Relink of module "FNDXIT.dll" failed.

Solution:

Solved by applying patch 13855823.

Installation Checklist for R12 on Windows 2003

Posted by on September 9, 2011 No comments

Installation Checklist for R12 on Windows Server 2003 Standard Edition

Here are the steps I took while installing R12.1 Vision instance on Windows:

1. Install Windows Server 2003 Standard Edition on 30GB C: partition
2. Allocate static IP address for network connection and put entry into hosts file
3. Install Windows Server 2003 Service Pack 2
4. Apply additional downloaded Windows updates from Microsoft
5. Create D: drive for downloads and additional applications
6. Create F: drive for database (146GB)
7. Create G: drive for EBS applications (146GB)
8. Ran ScanDisk on D: and F: (taking very long)
9. Installed Microsoft Visual Studio 2005 to D:MSVS (installed XML and Visual C, disabled all other applications).
10. Install Visual Studio 2005 Service Pack 1 ATL Security Update [ID 761567.1]
11. Add D:MSVSVCbin to PATH environment variable (in My Computer > Properties)
12. Downloaded gnumake fro MOS (patch 5897842) and unzipped [ID 761567.1]
13. Installed Cygwin to D:cygwin (downloaded all packages to local disk D:cygwin-install, then installed all packages to D:cygwin). [ID 414992.1]
14. Copied make-3.81WinRelgnumake.exe to D:cygwinbin [ID 414992.1]
15. Add D:cygwinbin to PATH environment variable (in My Computer > Properties) [ID 414992.1]
16. In D:cygwinbin, renamed make.exe to _make.exe and copied gnumake.exe to make.exe
17. Rename Cygwin’s rmdir executable (rmdir.exe) to _rmdir.exe [ID 414992.1]
18. In D:cygwinbin, renamed link.exe to _link.exe [ID 761567.1]
19. Staged R12.1 CDs to D:StageR12
20. Downloaded latest StartCD R12.1.1 startCD – RAPID INSTALL STARTCD 12.1.1.13 (patch 11072566) [ID 798258.1]
21. In D:StageR12, renamed startCD to _startCD and unzipped patch 11072566 into this D:StageR12 to create new startCD
22. Opened Command Prompt and ran D:StageR12startCDDisk1rapidwizrapidwiz.cmd

Parameters

New Configuration: Create a new configuration
Port Pool Number: 12
Database Type: Vision Demo Database
Database SID: VIS12
Host Name: appswindows2
Domain Name: domainname.com
Operating System: Windows (32-bit)
Database OS User: Administrator
(Database Node) Base directory: F:oracleVIS12
Data Top (ARCHIVE): G:oracleVIS12dbapps_stdata
UNIX Toolkit directory: D:cygwinbin
Visual Studio directory: D:MSVSVC
(Applications Node) Base Directory: G:oracleVIS12
(Applications Node) Instance Directory: G:oracleVIS12inst

Errors

1. If you encounter the following error:

RW-50004: Error code received when running external process. Check log file for details.
 Running APPL_TOP Install Driver for VIS12 instance

Edit $INST_TOP/temp/restart.xml and change “runProcess_2” to runProcess_2. Remember to kill the running Oracle Universal Installer before clicking Retry.

2. FRM-92050: Failed to connect to the Server: /forms/lservlet:-1

3. In Step 1 of 5

RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack

 

Log Files

Configuration file written to: G:oracleVIS12instappsVIS12_appswindows2conf_VIS12.txt
Configuration file written to: F:oracleVIS12dbtech_st11.1.0appsutilconf_VIS12.txt

Configuration file written to: G:oracleVIS12instappsVIS12_appswindows2conf_VIS12.txt
Configuration file written to: F:oracleVIS12dbtech_st11.1.0appsutilconf_VIS12.txt
Database logfile – F:oracleVIS12dbtech_st11.1.0appsutillogVIS12_appswindows29121000.log
Appltop logfile – G:oracleVIS12instappsVIS12_appswindows2logs9121000.log
Appltop logfile – G:oracleVIS12instappsVIS12_appswindows2logs9121000.log

Reference

Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.1.1) for Microsoft Windows Server (32-bit) [ID 761567.1]

Using Cygwin to Maintain Oracle E-Business Suite Release 12 on Windows [ID 414992.1]

Oracle Applications Documentation Resources, Release 12.1 [ID 790942.1]

How to Remove an Oracle E-Business Suite Release 12.x Windows Environment [ID 567507.1]

11i Pre Patching Script

Posted by on August 20, 2011 No comments

Problem: How can I minimize errors occurring while patching on the Windows platform?

Solution: Use a script to ensure that all environment variables are set and all supporting utilities are accessible.

Read more »

Project Rollup Patches Not Completing On DB Tier

Posted by on April 20, 2007 No comments

Problem: When applying Project Costing rollup patches to DB tier, the following errors are returned:

adlibout: error: cannot get table of contents in library file for product pa

File name is f:/oracle/prodappl/pa/11.5.0/lib/past.lib

Solution: mspdb60.dll not in the path.

Another issue was encountered on the system, which the application modules were relinked. While relinking, the message ‘gnumake: Error 128’ appeared. Metalink Doc ID 123595.1 and 142390.1 indicated that the mspdb60.dll file was not in the path (on the DB tier). After modifying the path, the relink completed successfully.

The Project Costing rollup patches were then reapplied, on both tiers, and all patches went through successfully. Relinking appears to be part of the patching process for the Project Costing rollup patches.