Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:Documents and Settingsoracle>f: F:>cd oracleproddb9.2.0 F:oracleproddb9.2.0>PROD_hostname.cmd ECHO is off. ECHO is off. Tue 05/19/2009 09:49 AM PROD_hostname.cmd exiting with status 0 F:oracleproddb9.2.0>sqlplus apps/apps SQL*Plus: Release 9.2.0.7.0 - Production on Tue May 19 09:49:27 2009 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. ERROR: ORA-01033: ORACLE initialization or shutdown in progress Enter user-name: / as sysdba Connected to: Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.7.0 - Production SQL> shutdown immediate ORA-01109: database not open Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. Total System Global Area 831725752 bytes Fixed Size 454840 bytes Variable Size 411041792 bytes Database Buffers 409600000 bytes Redo Buffers 10629120 bytes Database mounted. ORA-01113: file 1 needs media recovery ORA-01110: data file 1: 'E:ORACLEPRODDATASYSTEM01.DBF' SQL> recover automatic database Media recovery complete. SQL> alter database open; Database altered. SQL> select * from v$database; NAME --------- PROD SQL>
Category Archives: 11i - Page 4
Database Media Recovery of 11i Instance
Checking for Prerequisite Patches and Patch Levels
In a patch’s README file, the prerequisite patches and patch levels that must be in place before that patch is applied are listed. Patches are indicated by a patch number (usually seven digits long), for example, 4712852. Patch levels are usually of the form 11i.<PRODUCT CODE>.<LETTER>, for example, 11i.GL.H.
To determine if a particular prerequisite patch has already been applied to the system, query the AD_BUGS table.
Step 1: Source the environment to load SQL*Plus. Either the applications tier environment or database tier environment can be sourced.
[applmgr@appslinux /]$ cd /u2/oracle/vis2appl/ [applmgr@appslinux vis2appl]$ . APPSORA.env
Step 2: Load SQL*Plus:
[applmgr@appslinux vis2appl]$ sqlplus apps/apps
Step 3: To determine whether a particular patch has been applied, query the BUG_NUMBER column of the AD_BUGS table for the patch number. For example, to determine if the patch 4712852 has been applied to the system, issue this SQL query:
SQL> select bug_number, creation_date from ad_bugs where bug_number = '4712852'; BUG_NUMBER CREATION_DATE ------------------------------ ------------- 4712852 16-MAR-07
If the query returns a row, the patch has been applied, whereas if the query does not return any rows, then the patch has not been applied.
Step 4: To determine the patch level of a product, query the PATCH_LEVEL columns of the FND_PRODUCT_INSTALLATIONS table. For example, to determine the patch level for the GL product, issue this SQL query:
SQL> select patch_level, status from fnd_product_installations where patch_level like '%GL%'; PATCH_LEVEL S ------------------------------ - 11i.GL.H I
Unable to connect from client machine to new 11.5.10.2 instance
Problem:
After configuring TNS names on the client, tried to connect to new 11.5.10.2 instance but failed.
Solution:
Managed SQL Access enabled. To disable, follow these steps:
Step 1: Login to E-Business Suite with the ‘System Administrator’ Responsibility.
Step 2: Go to : Profile –> System
Step 3: Query the Profile “SQLNet Access’ at Site Level.
Step 4: Set the Profile with the Value : ALLOW_ALL
Step 5: Save and Exit Oracle Applications
Step 6: Run Autoconfig on the 9i ORACLE_HOME
cd <9i ORACLE_HOME>/appsutil/scripts/$CONTEXT_NAME
adautocfg.sh
Step 7: Bounce the 9i SQLNet Listener :
cd <9i ORACLE_HOME>/appsutil/scripts/$CONTEXT_NAME
addlnctl.sh stop <SID>
addlnctl.sh start <SID>
Metalink Reference:
Subject: 11.5.10 New Features : Managed SQL*Net Access from Hosts
Doc ID: Note:291897.1
ERR ‘REP-3002: Error initializing printer’
Problem:
After installing Oracle Applications 11.5.10.2, submitted Active Users report. Concurrent request fails with message
‘REP-3002: Error initializing printer’
Solution:
To implement the solution, please execute the following steps:
1. Define a dummy printer on the server to be defined as local printer.
2. Set this dummy printer to be the default.
3. Make the following updates in the registry, before making any changes to the registry you should always make a backup copy:
Complete path Regedit:
HKEY_USERSS-1-5-...............SoftwareMicrosoftWindows NTCurrentVersionDevices
You will find String value with name as the newly defined printer
Same goes to:
HKEY_USERSS-1-5-...............SoftwareMicrosoftWindows NTCurrentVersionPrinterPorts
You will find String value with name as the newly defined printer
HKEY_USERSS-1-5-...............SoftwareMicrosoftWindows NTCurrentVersionWindows
You will find String value with name “Device” and has value including the printer name as defined
All the above string values should also be set under the following paths for the valid printer to be seen by all users
HKEY_USERS.DEFAULTSoftwareMicrosoftWindows NTCurrentVersionDevices HKEY_USERS.DEFAULTSoftwareMicrosoftWindows NTCurrentVersionPrinterPorts HKEY_USERS.DEFAULTSoftwareMicrosoftWindows NTCurrentVersionWindows
Post-install checks fail after installing
Problem:
After installing Oracle Applications E-Business Suite 11.5.10.2 on Windows, the post installation checks (HTTP Check, JSP Check, PHP Check) fail.
Solution:
Install Microsoft XML (msxml3.msi) located in downloadsXML.
Could not start Service Manager
Problem:
Concurrent manager not starting on ebusinesstest. Checked Metalink Doc ID: Note:104452.1 (Subject: Troubleshooting Concurrent Manager (Unix specific). Changed to /u0/oracle/testcomn/admin/log/TEST_ebusinesstest ($APPLCSF/$APPLLOG) and check last .mgr file (TEST_0424.mgr). It showed the following error message:
Starting PASMGR Concurrent Manager : 24-APR-2009 12:29:17 Spawned Process 18408 Could not start Service Manager FNDSM_EBUSINESSTEST_TEST. The TNS alias could not be located, the listener process on EBUSINESSTEST could not be contacted, or the listener failed to spawn the Service Manager process. Routine AFPEIM encountered an error while starting concurrent manager PASMGR with library /u0/oracle/testappl/pa/11.5.0/bin/PALIBR. Check that your system has enough resources to start a concurrent manager process. Contact your system admi : 24-APR-2009 12:29:17 Process monitor session ended : 24-APR-2009 12:29:17
Solution:
Checked Metalink for message ‘Could not start Service Manager’. Checked Metalink Doc ID: 423170.1 (Subject: Concurrent Manager Fails to Start Because of a ‘Could not start Service Manager FNDSM__’ Error)
To implement the solution, please execute the following steps:
1. Download and apply patch 3830807: ” PATCH 3293983 NEEDS TO INCLUDE ALL THE MAKEFILES UNDER THE 8.0.6 ORACLE_HOME”.
2. Launch adadmin and choose the task to relink all product executables.
3. Startup the Concurrent Manager.
The Concurrent Manager should start without any errors. There should be no errors in the 8.0.6 listener log file.
AC-50480: Internal error occurred: java.sql.SQLException: ORA-00001: unique constraint (APPLSYS.FND_TNS_ALIASES_U2) violated
Problem:
When running AutoConfig on database tier, the follow error appears in the log file:
======================================================= [ Config tool : /u0/oracle/testdb/9.2.0/appsutil/bin/adgentns.pl ] Command : /u0/oracle/testdb/9.2.0/Apache/perl/bin/perl -I /u0/oracle/testdb/9.2.0/Apache/perl/lib/5.00503:/u0/oracle/testdb/9.2.0/Apache/perl/lib/site_perl/5.005:/u0/oracle/testdb/9.2.0/appsutil/perl /u0/oracle/testdb/9.2.0/appsutil/bin/adgentns.pl PASSWORD contextfile=/u0/oracle/testdb/9.2.0/appsutil/TEST_ebusinesstest.xml Action : execute SCRIPT RETURNED: ####################################################### Generate Tns Names ####################################################### Using java command: /u0/oracle/testdb/9.2.0/jdk/bin/java JAVA_HOME : Java version : 1.3.1_11 Classpath : /u0/oracle/testdb/9.2.0/jdk/jre/lib/rt.jar:/u0/oracle/testdb/9.2.0/jdk/jre/lib/i18n.jar:/u0/oracle/testdb/9.2.0/jdk/lib/dt.jar:/u0/oracle/testdb/9.2.0/jdk/lib/tools.jar:/u0/oracle/testdb/9.2.0/jdbc/lib/classes12.jar:/u0/oracle/testdb/9.2.0/appsutil/java/xmlparserv2.zip:/u0/oracle/testdb/9.2.0/appsutil/java Loading ORACLE_HOME environment from /u0/oracle/testdb/9.2.0 Logfile: /u0/oracle/testdb/9.2.0/appsutil/log/TEST_ebusinesstest/04061541/NetServiceHandler.log AC-50480: Internal error occurred: java.sql.SQLException: ORA-00001: unique constraint (APPLSYS.FND_TNS_ALIASES_U2) violated ORA-06512: at "APPS.FND_APP_SYSTEM", line 931 ORA-06512: at "APPS.FND_NET_SERVICES", line 399 ORA-06512: at "APPS.FND_NET_SERVICES", line 675 ORA-06512: at "APPS.FND_NET_SERVICES", line 1097 ORA-06512: at line 1 Error generating tnsnames.ora from the database, temperory tnsnames.ora will be generated using templates Instantiating templates tnsnames.ora instantiated listener.ora instantiated adgentns.pl exiting with status 2 ERRORCODE = 2 ERRORCODE_END
Solution:
To implement the solution, please execute the following steps:
1. Be sure to have a valid backup.
2. Open an environment shell and set the Applications Environment
3. cd $AD_TOP/bin
4. perl <AD_TOP>/bin/adgentns.pl appspass=<APPSpwd> contextfile=<CONTEXT> -removesystem
5. Open a new shell and set the Database Environment
6. Run adconfig at the dbTier
7. Open a new shell and set the Applications Environment and also run autoconfig at the appsTier
Subject: Autoconfig Fails with:ORA-00001: unique constraint (APPLSYS.FND_TNS_ALIASES_U2) violated
Doc ID: 416182.1
AC-50207: Fatal: Failed to execute one or more of the config tools during Context Value Management
Problem:
When running AutoConfig on application tier:
AC-50207: Fatal: Failed to execute one or more of the config tools during Context Value Management Deactivating Context Value Management System. Restored the Context file in : /u0/oracle/testappl/admin/TEST_ebusinesstest.xml Aborting the running of Context Value Management Error occured before Context Value Management could be completed ERROR: Context Value Management Failed. Terminate.
Solution:
LD_ASSUME_KERNEL not set.
export LD_ASSUME_KERNEL=2.4.19
Error updating master archive
Problem:
When applying patch 4104924, the following error appears:
AutoPatch error: ERROR [code language="1"][/code] [/code] Running adjopy.class AutoPatch error: Error updating master archive
Solution:
LD_ASSUME_KERNEL not set
export LD_ASSUME_KERNEL=2.4.19
Unable to initialize threads
Problem:
Running adstpall.sh returns the following error: [applmgr@ebusinesstest TEST_ebusinesstest]$ ./adstpall.sh apps/apps You are running adstpall.sh version 115.17 /u0/oracle/testcomn/util/jre/1.1.8/bin/../lib/i686/green_threads/libzip.so: symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference (libzip.so) Unable to initialize threads: cannot find class java/lang/Thread Could not create Java VM Check logfile /u0/oracle/testcomn/admin/log/TEST_ebusinesstest/04061425.log for details Exiting with status 1 [applmgr@ebusinesstest TEST_ebusinesstest]$
Solution:
Subject: GLIBC_2.0 not defined in file libc.so.6
Note:275161.1
export LD_ASSUME_KERNEL=2.4.19
Recent Comments