Category Archives: AATT

Cloning of Production Instance

#

Step

Estimated duration

1. Prepare the test machine (echo) that shall be used as the new production machine for cloning:Remove any existing E-Business Suite instance on the machine. Ideally, reinstall the operating system, apply any required service packs, install the additional software such as JDK, Visual C++, MKS Toolkit etc. The software should be installed to the same directory paths as those on the production instance.If the test machine will not reinstalled, then remove the Oracle-related keys from the registry.

1 day

2. Carry out the pre-clone steps for the production instance (adpreclone.pl).

½ day

3. Shutdown the production E-Business Suite instance (application and database tier services) and copy the files from the production machine (delta) to the test machine (echo).

1 day

4. Disconnect the production server from the network. Change the name and IP address of the test machine (echo) to that of the production machine (delta). Update the ‘hosts’ file on the new production server, so that it now contains the new IP address and hostname.

1 hour

5. Clone the new production server. Run the clone scripts on the new production server (adcfgclone.pl).

½ day

6. Perform stress-testing of the new server to ensure that it responds suitably to the load.

1 day

7. Backup and test recovery of the instance on another server.

1 day

Please note:

1. Ensure that the Database processes are properly shut down before proceeding to copy the files; if files aren’t copied correctly, the cloning process would not be executed correctly.

2. Do not run the Gather Schema Statistics concurrent job on the new PROD instance.

Troubleshooting Custom Reports

Running Report from Command Prompt

To run the pay_register.rdf custom report from the Command Prompt, enter the following command at the prompt:

C:> C:oracleproduct10.2.0db_2binrwbuilder.exe report="C:Documents and Settingsuser01DesktopReports Tuning Issuetest.aippay_register.rdf" userid=apps/apps@vis2.world tracemode=TRACE_APPEND tracefile=c:temppay_register01.txt traceopts=(trace_SQL,TRACE_PLS,trace_prf,trace_tms)

The report loads in Reports Builder.

1. Compile the packages by typing Shift+Ctrl+K.

2. Run the Paper Layout version of the report by Shift+Ctrl+R.

3. In the Payroll ID parameter field, enter 112.

4. In the Pay Advice Date field, enter 2003/08/29.

Running SQL Code in SQL Developer

1. Open the report in Reports Developer and double-click on the Data Model icon (not word).

2. Double-click the Q_1 box. The SQL code for the Q_1 query appears.

3. Copy all the SQL code and run it in SQL Developer.

4. For the p_payroll_id, enter 112

5. For the p_pay_advice_date, enter 29-AUG-2003

11i Installation Troubleshooting

Installation of 11i instance on Windows Server 2003

1. Installed Visual C++ 6.0 and Visual Studio Service Pack 4

2. Set IP address in hosts file

3. Installed ActivePerl and Microsoft XML Parser

4. Started staging process:
cd
perl E:Disk1rapidwizadautocfg.pl

Error Encountered:
—————–
Only 12-13 files copied from Start CD

5. Uninstalled MKS Toolkit from C:Program Files and reinstalled it to C:mksnt

6. Changed TEMP environment variables to C:TEMP

7. Retried staging process:

Error Encountered:
—————–

Failed to copy adautocfg.pl to C:TEMPstaging

8. Determined which perl was being executed:
which perl

perl from MKS Toolkit being executed, because it is ahead of ActivePerl on path.

9. Uninstalled and reinstalled ActivePerl.

10. Retried staging process. Same error (Failed to copy adautocfg.pl to C:TEMPstaging)

11. Modified PATH environment variable so that ActivePerl (C:PERLbin) ahead of MKS Toolkit in path

12. Retried staging process. Staging progressing without errors.

13. Started installation by running rapidwiz

Error Encountered:
—————–

‘which’ not found

Solution:
——–

In Rapid Install, set MKS Directory to C:mksntmksnt

Error Encountered:
—————–

‘gnumake’ not found

Solution:
——–

Unzip make3.81 tar, set VC environment (VCVARS.bat), compiled gnumake (build_w32.bat) and copied gnumake.exe to C:Windowssystem32. Check that gnumake is in path by typing ‘which gnumake’

14. No errors encountered while installing. Post-install steps completed successfully.

15. After installing, logged on to application and submitted concurrent job. ‘Inactive Manager’

Error Encountered:
—————–

Active Users report completed on error:

ERR REP-3002: Error initializing printer. Please make sure a printer is installed.

Solution:
——–

Checked Metalink Doc ID: Note:365267.1 (Subject: All Requests End In Error With REP-3002: Error Initializing Printer)

Installed a local printer (Epson FX-80)

Error Encountered:
—————–

Internet Explorer crashing when forms are loaded.

Solution:
——–

Deinstall JInitiator and reinstall it.

Troubleshooting APP-FND-00500 Error

Problem:

The APP-FND-00500 error was encountered when printing TD4 slips.

Solution:

Set printer output to RAW.

Reference:

Metalink Doc ID: 200359.1 (Oracle Application Object Library Printer Setup Test), which will assist in validating the printer configuration/setup in Oracle Applications.

Recreating DBC file

Problem: While installing vision instance, the post-install check “JSP Check” fails with the message “DBC file may be invalid”.

Solution: Recreate DBC file.

Note: Run these commands from $FND_TOP/secure. Also, source environment file first.

To create a DBC file and server ID:
java oracle.apps.fnd.security.AdminAppServer apps/apps@vis ADD FNDNAM=apps GWYUID=applsyspub/pub TWO_TASK=vis SECURE_PATH=%FND_TOP%secure GUEST_USER_PWD=guest/guest APPS_JDBC_DRIVER_TYPE=THIN DB_HOST=eam.clientnetwork.com DB_PORT=1522

To check status:
java oracle.apps.fnd.security.AdminAppServer apps/apps@vis STATUS DB_HOST=eam.clientnetwork.com DB_PORT=1522

To delete DBC file:
java oracle.apps.fnd.security.AdminAppServer apps/apps@vis DELETE DB_HOST=eam.clientnetwork.com DB_PORT=1522

Also, you can run adgendbc.sh, located in $COMMON_TOP/admin/install/

For Database Connectivity problems, ensure that the hosts file is set up properly:

127.0.0.1 localhost.localdomain localhost
hostname.domainname hostname

On Windows, use java. On Linux/Unix, use JRE.

Reference:
Metalink Doc ID: 108865.1 (How To Create a Database Connection(DBC) File and Troubleshooting Common Problems)

No TNS Listener Installing Instance

Problem: In step 5 of 5 during installation of Oracle Applications instance, TNS listener does not start.

Solution: hosts file configured incorrectly.

The correct format of the hosts file is:

Under Windows:


xx.xx.xx.xx hostname.domainname alias
127.0.0.1 localhost.localdomain localhost

Another symptom that the hosts file was not set up correctly: the StartCD did not stage properly.