Saturday 31 August 2013

Adpatch options

Adpatch options

To change the default behaviour of patching ,we can use below options.

Non default
======                
nocopyportion
nodatabaseportion
nogenerateportion
nocompiledb
nocompilejsp
novalidate
nomaintainancemrc
noautoconfig
hotpatch



default
======
copyportion
databaseportion
generateportion
compiledb
compilejsp
validate
maintainancemrc
autoconfig
nohotpatch


Checkfile *:-
==========
The checkfile option of adpatch tells adpathc to check for already executed exec, SQL, and exectier commands. this can cause performance overheds so should be used only when specified.

$adpatch options=nocheckfile


compiledb *:-
============
Purpose: To compile invalid objects in the database after running actions in the database driver.
Default: compiledb (use ‘nocompiledb’ to skip)



compilejsp *:-
===========
Purpose: To compile out-of-date JSP files, if the patch has copy actions for at least one JSP file.
Default: compilejsp (use’nocompilejsp’ to skip)


copyportion*:-
============
Purpose: To run commands found in a copy driver. This will copy the higher version files from patch to product top.
Default: copyportion (Use ‘nocopyportion’ to skip. Use it only when mentioned in readme of patch)


databaseportion * :-
================
Purpose: To run commands found in a database driver. This portion includes applying the files (like sql, pls etc) to database.
Default: databaseportion (use ‘nodatabaseportion’ to skip. Use it only when mentioned in readme of patch).


generateportion *:-
===================

Purpose: To run commands found in a generate driver. This portion will generate new executable files from the copied code of patch. For example if will generate new forms files (fmx) from new .fmb files.
Default: generateportion (use ‘nogenerateporation’ to skip).

$adpatch options=nogenform
$adpatch options=nogenrep

integrity *:-
=============
Purpose: To perform patch integrity checking. Tells adpatch whether to perform patch integrity checking, which verifies that the version of each file referenced in a copy action matches the version present in the patch.
Default: nointegrity (By default the integrity is not checked)

$adpatch options=integrity

maintainmrc *:-
==============
Purpose: To maintain the MRC schema after running actions found in the database driver.
Default: maintainmrc (use ‘nomaintainmrc’ to skip)


autoconfig *:-
==============
Purpose: Tells adpatch to run Autoconfig after patch installation.
Default: autoconfig (use ‘noautoconfig’ to skip)


parallel * :-
=============
Purpose: To run actions that update the database or actions (like SQL) that generate files in parallel (like genform).



prereq *:-
==========
Purpose: Tells adpatch whether to perform prerequisite patch checking prior to running patch driver files that contain actions normally found in the copy driver.
Default: prereq (use ‘noprereq’ to skip)

$adpatch options=noprereq

validate *:-
=============
Purpose: To connect to all registered Oracle Applications schemas at the start of the patch. Adpatch validates the passwords for each schema.
Default: novalidate (use ‘validate’ to validate schema passwords)
Default: parallel (use ‘noparallel’ to skip)


Java Classes * :-
=============
If you wish adpatch not to copy new java classes from the patch .By default java classes are copied.

$adpatch options=nojcopy


Relinking *:-
===========
If you wish adpatch not do perform relinking you can use options=nolink.


Force Copy *:-
============
By default adpatch copies the files without check the version of the existing files already present on the system.If you do  not wish the newer version of the file to be replaced by the older version contained in the patch use options=noforcecopy.

$adpatch options=noforcecopy.


You could specify multiple options at the command line using the , delimiter.
=============================================================================
$adpatch options=nocompiledb,nocompilejsp,nojcopy


Following flags can be passed to adpatch
1) hidepw
Purpose: This argument is used to hide the passwords in log files
Default: nohidepw
2) trace
Purpose: Tells the adpatch utility whether to log all database operations to a trace file
Default: notrace
3) logging
Purpose: Tells the adpatch utility whether to create indexes using the logging or nologging mode.



What two tables adpatch creates when you apply or run adpatch session ?
FND_INSTALL_PROCESSES , AD_DEFERRED_JOBS

Thursday 29 August 2013

ORA-00265: instance recovery required, cannot set ARCHIVELOG mode


SQL> startup mount
ORACLE instance started.

Total System Global Area 6265438208 bytes
Fixed Size 2169816 bytes
Variable Size 5167383592 bytes
Database Buffers 1073741824 bytes
Redo Buffers 22142976 bytes
Database mounted.

SQL> archive log list
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination +ARCH
Oldest online log sequence 180
Current log sequence 182
SQL> alter database archivelog;
alter database archivelog
*
ERROR at line 1:
ORA-00265: instance recovery required, cannot set ARCHIVELOG mode

SQL>
SQL> shutdown immediate
ORA-01109: database not open


Database dismounted.
ORACLE instance shut down.
oratest@ctsst $ sqlplus "/as sysdba"

SQL*Plus: Release 11.2.0.2.0 Production on Fri Aug 23 19:23:31 2013

Copyright (c) 1982, 2010, Oracle. All rights reserved.

Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area 6265438208 bytes
Fixed Size 2169816 bytes
Variable Size 5167383592 bytes
Database Buffers 1073741824 bytes
Redo Buffers 22142976 bytes
Database mounted.
Database opened.
SQL>shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.

Total System Global Area 6265438208 bytes
Fixed Size 2169816 bytes
Variable Size 5167383592 bytes
Database Buffers 1073741824 bytes
Redo Buffers 22142976 bytes
Database mounted.
SQL> alter database archivelog;

Database altered.
SQL>

SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ARCH
Oldest online log sequence 180
Next log sequence to archive 182

PLS-00201: identifier 'UTL_RECOMP.RECOMP_PARALLEL' must be declared

When trying to compile invalid objects getting below error?


SQL> execute utl_recomp.recomp_parallel(4);
BEGIN utl_recomp.recomp_parallel(4); END;

*
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00201: identifier 'UTL_RECOMP.RECOMP_PARALLEL' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored

Cause : you are compling the invalid object using different schema
utlrp.sql has to be run with "sysdba"


Solution:Please login with sysdba and try it again.

ORA-28007: the password cannot be reused

SQL> alter user system identified by mufti@143;
alter user system identified by mufti@143
*
ERROR at line 1:
ORA-28007: the password cannot be reused


Check user profile
============
SQL> select USERNAME, PROFILE, ACCOUNT_STATUS from dba_users where username = 'SYSTEM';
USERNAME  PROFILE        ACCOUNT_STATUS
------------------    ------------------ --------------------------------
SYSTEM  USER_PROFILE  OPEN

SQL> select * from dba_profiles where profile='USER_PROFILE';

PROFILE RESOURCE_NAME RESOURCE LIMIT
------------------------------ -------------------------------- -------- ----------------------------------------
USER_PROFILE SESSIONS_PER_USER KERNEL DEFAULT
USER_PROFILE CPU_PER_SESSION KERNEL DEFAULT
USER_PROFILE CPU_PER_CALL KERNEL DEFAULT
USER_PROFILE LOGICAL_READS_PER_SESSION KERNEL DEFAULT
USER_PROFILE LOGICAL_READS_PER_CALL KERNEL DEFAULT
USER_PROFILE IDLE_TIME KERNEL DEFAULT
USER_PROFILE CONNECT_TIME KERNEL DEFAULT
USER_PROFILE PRIVATE_SGA KERNEL DEFAULT
USER_PROFILE FAILED_LOGIN_ATTEMPTS PASSWORD DEFAULT
USER_PROFILE PASSWORD_LIFE_TIME PASSWORD DEFAULT

PROFILE RESOURCE_NAME RESOURCE LIMIT
------------------------------ -------------------------------- -------- ----------------------------------------
USER_PROFILE PASSWORD_REUSE_TIME PASSWORD DEFAULT
USER_PROFILE PASSWORD_REUSE_MAX PASSWORD DEFAULT
USER_PROFILE PASSWORD_VERIFY_FUNCTION PASSWORD DEFAULT
USER_PROFILE PASSWORD_LOCK_TIME PASSWORD DEFAULT
USER_PROFILE PASSWORD_GRACE_TIME PASSWORD DEFAULT


SQL>alter profile USER_PROFILE limit password_verify_function NULL;

SQL> alter profile USER_PROFILE limit PASSWORD_REUSE_MAX unlimited;

Profile altered.

SQL> alter user system identified by mufti@143;

User altered.

SQL> select * from dba_profiles where profile='USER_PROFILE';

PROFILE RESOURCE_NAME RESOURCE LIMIT
------------------------------ -------------------------------- -------- ----------------------------------------
USER_PROFILE SESSIONS_PER_USER KERNEL DEFAULT
USER_PROFILE CPU_PER_SESSION KERNEL DEFAULT
USER_PROFILE CPU_PER_CALL KERNEL DEFAULT
USER_PROFILE LOGICAL_READS_PER_SESSION KERNEL DEFAULT
USER_PROFILE LOGICAL_READS_PER_CALL KERNEL DEFAULT
USER_PROFILE IDLE_TIME KERNEL DEFAULT
USER_PROFILE CONNECT_TIME KERNEL DEFAULT
USER_PROFILE PRIVATE_SGA KERNEL DEFAULT
USER_PROFILE FAILED_LOGIN_ATTEMPTS PASSWORD DEFAULT
USER_PROFILE PASSWORD_LIFE_TIME PASSWORD DEFAULT

PROFILE RESOURCE_NAME RESOURCE LIMIT
------------------------------ -------------------------------- -------- ----------------------------------------
USER_PROFILE PASSWORD_REUSE_TIME PASSWORD DEFAULT
USER_PROFILE PASSWORD_REUSE_MAX PASSWORD UNLIMITED
USER_PROFILE PASSWORD_VERIFY_FUNCTION PASSWORD NULL
USER_PROFILE PASSWORD_LOCK_TIME PASSWORD DEFAULT
USER_PROFILE PASSWORD_GRACE_TIME PASSWORD DEFAULT

16 rows selected.

SQL>


Once the password is changed make it to default...
SQL>alter profile USER_PROFILE limit password_verify_function DEFAULT;

SQL>alter profile USER_PROFILE limit PASSWORD_REUSE_MAX DEFAULT;

Thursday 22 August 2013

what happens when you apply already applied patch?

Warning:

The description for the entity 'cle' in the patch driver
does not match with the current description.

The current description is :'EMEA Consulting Localizations'
The description in the patch is :'EMEA Add-on Localizations'

The current description will not be changed.


This Patch seems to have been applied already.
Would you like to continue anyway [N] ? No

You should check the file
/appsebiz/erpapp/appl/admin/appsebiz/log/16806251.log

for errors.

you have mail in /var/spool/mail/appebiz
$

How to apply a patch in no autoconfig mode?

appdev@ctssd $ adpatch options=noautoconfig

Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA

Oracle Applications AutoPatch

Version 11.5.0

NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.


Attention: AutoPatch no longer checks for unapplied pre-requisite patches.
You must use OAM Patch Wizard for this feature. Alternatively, you can
review the README for pre-requisite information.


Your default directory is '/erpdev/erpapp/appl'.
Is this the correct APPL_TOP [Yes] ?

AutoPatch records your AutoPatch session in a text file
you specify. Enter your AutoPatch log file name or press [Return]
to accept the default file name shown in brackets.

Filename [adpatch.log] : UP0251241.log

Options = "noautoconfig".

You can be notified by email if a failure occurs.
Do you wish to activate this feature [No] ?

Please enter the batchsize [1000] : 

you fired adpatch and forget to enable maintainance then what happen?

Reading FND_LANGUAGES to see what is currently installed.
Currently, the following language is installed:

Code Language Status
---- --------------------------------------- ---------
US American English Base 

Your base language will be AMERICAN.

Setting up module information.
Reading database for information about the modules.
Saving module information.
Reading database for information about the products.
Reading database for information about how products depend on each other.
Reading topfile.txt ...

Saving product information.

AD code level : [B.3]

AutoPatch error:
You must be in Maintenance Mode to apply patches.
You can use the AD Administration Utility to set Maintenance Mode.

You should check the file
/u01/erpapp/appl/admin/erptest/log/up0259281.log for errors.

[apptest@ctsst 11808198]$

what happens when we apply different base line patch?

what happens when we apply different base line patch in oracle applications?


The patch  will failed with the below error.
============================
AutoPatch error:
--------
This patch is not compatible with your current codelines.



Current target release is 12.1.3

AutoPatch error:
--------
This patch is not compatible with your current codelines.

This patch is compatible with: entity 'ar' - codeline 'R12.AR.A'.
Your current on-site codeline for the entity 'ar' is: 'R12.AR.B'.

You should not apply this patch.

Apply an equivalent patch that is compatible with your
current codelines instead.
--------


AutoPatch error:
--------
A fatal error related to codelines or codelevels has occurred.

See messages above for details.
--------
You should check the file
/u01/erpapp/appl/admin/erptest/log/11808198.log

for errors.

[apptest@ctsst 11808198]$

Tuesday 20 August 2013

PATCH MODES

PATCHES MODE
============

We can apply adpatch in four modes.They are

1)Interactive
2)Non - Interactive
3)Pre-install mode
4)Test  mode



1)Interactive *:-
==============

Providing all the inputs at the time of applying a patch.

Syntax: $adpatch ==> followed by inputs.

2)Non - Interactive *:-
====================
Providing  the inputs for adpatch in a file is said to be Non-interactive mode.

It is a text file.

Location of the defaluts file is $APPL_TOP/admin/<SID>

While working with defaults file for the first time we need to provide all the inputs.From next time onwards
we have to provide only limited information like Patch location,driver file,patch log file and number of works.


Example:
===========

$adpatch defaultsfile=/u01/erpapp/appl/admin/ebsofdb/adpatchdef.txt

From next time onwards no need to provide all the inputs,its enough to provide below inputs.
1)Logfile
2)Patch directory location
3)Driver file
4)Workers

Advantage: Reduce patch timing.


3)Pre-install mode *--
====================
In this mode,Only copy portion is applied.('C' Driver is applied)
Database portion and generate portion will not be executed.('D' and 'G' Driver will  not be executed).
Default it is set to no adpatch preinstall=n
This would be done normally during an upgrade or consolidated update. When a patch is applied in a preinstall mode then all the AD utilities are updated before the upgrade or update.

if you wish to apply a patch in preinstall mode then use below syntax.

$adpatch preinstall=y


4)Test  mode * :-
===============
BY using this mode,We can see the effects of applying this patch will have on your system before applying the patch.
The default is adpatch apply=y.
If you want to apply a patch in test mode follow below syntax.

Syntax: adpatch apply=no

In this mode just file comparision will be done between PATCH_TOP and APPL_TOP and that will be reported in .lgi file.
It is located under $APPL_TOP/adminn/<SID>/log/adpatch.lgi

==>No files are modified,no sql's are executed and no forms and reports are changed.

Advantage *:- Will get to know what patch is doing before applying the patch on our system.

----------------------------------------------------------------
-Script to find out Patch level of mini Pack
------------------------------------------------------------------
Select product_version,patch_level from fnd_product_installations where patch_level like '%FND%'; 
I.e.
PATCH_LEVEL
===========
11i.FND.H
11i.AX.I
11i.AK.G
11i.XLA.H
11i.GL.J
11i.FA.O

My dear friend, clear your mind of can't.
        Thanks for visiting my blog!!!!!!!!!!

Monday 12 August 2013

How to drop and recreate TEMP Tablespace in Oracle ?

1. Create Temporary Tablespace Temp2.

CREATE TEMPORARY TABLESPACE TEMP2 TEMPFILE  '/u01/dbdata/oradata/temp101.dbf' SIZE 2000M, '/u01/dbdata/oradata/temp102.dbf' SIZE 2000M';

2. Move Default temp tablespace to newly created one.

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp2;


3. Drop temp tablespace

DROP TABLESPACE temp INCLUDING CONTENTS AND DATAFILES;

4. Recreate Tablespace Temp

CREATE TEMPORARY TABLESPACE TEMP TEMPFILE '/u01/dbdata/temp/temp01.dbf' SIZE 2000M;

5 Move Tablespace Temp, back to new temp tablespace

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp;

6. Drop temporary for tablespace temp

DROP TABLESPACE temp2 INCLUDING CONTENTS AND DATAFILES;


Recap
====

1)Create Temporary Tablespace Temp2
2)Move Default temp tablespace to newly created one
3)Drop temp tablespace TEMP
4)Recreate Tablespace Temp
5) Make the default tablepsace to Temp
6)Drop temporary tablespace temp2

All about crontab utility .

crontab is a unix utility that allows tasks (shell programs/commands) to be automatically run in the background at according to the specified intervals.
It is one of essential utility which has been used by DBAs on day to day basis.

Syntax:
~~~~~~
o crontab [filename] -- This will overwrite an existing crontab entry for the user that invokes it.

o crontab -elr [username]
    e - Edits a copy of the current user's crontab file, or creates an empty file to edit if crontab does not exist
    l - Lists the crontab file for the invoking user
    r - Removes a user's crontab from the crontab directory


Supporting Files:
~~~~~~~~~~~~~~~~
o /etc/cron.d             : main cron directory
o /etc/cron.d/cron.allow  : list of allowed users
o /etc/default/cron       : contains cron default settings
o /etc/cron.d/cron.deny   : list of denied users
o /var/cron/log           : accounting information
o /var/spool/cron/crontabs: spool area for crontab


Access permission (Scenarios):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Users: Access to crontab is allowed:
  o if the user's name appears in /etc/cron.d/cron.allow.
  o if cron.allow  does  not  exist  and  the user's name is not in cron.deny

Users: Access to crontab is denied:
  o if cron.allow exists and the user's name is not in it.
  o if cron.allow does not exist and user's name is in cron.deny
  o if neither file exists, only a user with the solaris.jobs.user authorization is allowed to submit a job.
  o If BSM audit is enabled, the user's shell is not audited and the user is not the crontab owner. This can occur if the user logs in via a program, such as some versions of SSH, which does not set audit parameters.



Crontab Pattern:
~~~~~~~~~~~~~~~

*  *  *  *  * [nohup] script (full path) [> logfile location]
_  _  _  _  _
|  |  |  |  |
|  |  |  |  |
|  |  |  |  |
|  |  |  |  |
|  |  |  |  +----------> Day of the week (0-6 with 0=Sun)
|  |  |  |
|  |  |  +-------------> Month of the year (1-12)
|  |  |
|  |  +----------------> Day of the month (1-31)
|  |
|  +-------------------> Hour (0-23)
|
+----------------------> Minute (0-59)


Symbols:
~~~~~~~
- Used to specify the range between two integers
, Used to specifiy the multiple integers


Examples:
~~~~~~~~
00 13 * * *
--> Runs at 1 PM on every day

00 13 7 * *
--> Runs at 1 PM on every 7th day of all months

00 13 1-10 1,2 *
--> Runs at 1 PM during 1st to 10th days of Jan & Feb months

00 14 * * 1-5
--> Runs at 2 PM on all business days (Mon to Fri)

00 11 * * 6,0
--> Runs at 11 AM on weekends (Sat & Sun)

0,10,20,30,40,50 * * * *
--> Runs every 10 mins

Hope you have a gained some knowledge about Unix Job Scheduler. Have a nice day. 

Saturday 3 August 2013

Perl lib version (v5.8.4) doesn't match executable version (v5.10.0) at /usr/perl5/5.8.4/lib/sun4-solaris-64int/Con fig.pm line 32.

Metalink id:
========
Rapid Clone Error : 11gR2 Database : Perl lib Version (v5.8.5) Doesn't Match Executable Version (v5.10.0) [ID 1276455.1] 



Issue while running perl adcfgclone.pl dbTechStack
===================================
/erpdev/oracle/11.2.0/appsutil/clone/bin/../jre/bin/java -Xmx600M -DCONTEXT_VALIDATED=true -Doracle.installer.oui_loc=/erpdev/oracle/11.2.0/oui -classpath /erpdev/oracle/11.2.0/appsutil/clone/jlib/xmlparserv2.jar:/erpdev/oracle/11.2.0/appsutil/clone/jlib/ojdbc5.jar:/erpdev/oracle/11.2.0/appsutil/clone/jlib/java:/erpdev/oracle/11.2.0/appsutil/clone/jlib/oui/OraInstaller.jar:/erpdev/oracle/11.2.0/appsutil/clone/jlib/oui/ewt3.jar:/erpdev/oracle/11.2.0/appsutil/clone/jlib/oui/share.jar:/erpdev/oracle/11.2.0/appsutil/clone/jlib/oui/srvm.jar:/erpdev/oracle/11.2.0/appsutil/clone/jlib/ojmisc.jar oracle.apps.ad.clone.ApplyDBTechStack -e /erpdev/oracle/11.2.0/appsutil/clone/context/db/erpdev_erpdev.xml -stage /erpdev/oracle/11.2.0/appsutil/clone -showProgress
APPS Password : Log file located at /erpdev/oracle/11.2.0/appsutil/log/erpdev_erpdev/ApplyDBTechStack_07292320.log
- 0% completed RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack

ERROR while running Apply...
Mon Jul 29 23:22:43 2013

ERROR: Failed to execute /erpdev/oracle/11.2.0/appsutil/clone/bin/adclone.pl

Please check logfile.
you have mail in /usr/mail/oratest2
oratest2@ctsst $

Error in adcfgclone logfile
===================
.end std out.
Perl lib version (v5.8.4) doesn't match executable version (v5.10.0) at /usr/perl5/5.8.4/lib/sun4-solaris-64int/Config.pm line 32.Compilation failed in require at/erpdev/oracle/11.2.0/appsutil/clone/ouicli.pl line 35.
BEGIN failed--compilation aborted at /erpdev/oracle/11.2.0/appsutil/clone/ouicli.pl line 35.
.end err out.


Solution *:--

export ORACLE_HOME=/erpdev/oracle/11.2.0 
exportPERL5LIB=/erpdev/oracle/11.2.0/perl/lib/5.10.0:/erpdev/oracle/11.2.0/perl/site_perl/5.10.0:/erpdev/oracle/11.2.0/appsutil/perl 
export PATH=$ORACLE_HOME/perl:$ORACLE_HOME/perl/lib:$ORACLE_HOME/perl/bin:$PATH 

Quote of the day
==========
It's nice to be important, but it's more important to be nice.  ~Author Unknown

How to add a resposiblity from back end?When you don't have access to front end?

BEGIN
apps.fnd_user_pkg.addresp ('USERNAME','SYSADMIN','SYSTEM_ADMINISTRATION','STANDARD','System Administration Responsibility',SYSDATE,SYSDATE + 2);
COMMIT;
END;

what happens when we apply already applied patch?

Warning:
The description for the entity 'cle' in the patch driver
does not match with the current description.

The current description is :'EMEA Consulting Localizations'
The description in the patch is :'EMEA Add-on Localizations'

The current description will not be changed.

This Patch seems to have been applied already.
Would you like to continue anyway [N] ? No

You should check the file
/appsebiz/erpapp/appl/admin/appsebiz/log/16806251.log

for errors.

you have mail in /var/spool/mail/appsebiz

Internal Manager Creates Zero Byte Log File/Concurrent Manager showing Status=INACTIVE Phase=No manager

Meta link id:
Unable to Start Concurrent Manager, Internal Manager Creates Zero Byte Log File [ID 1305892.1]

Cause: No space left in the mount point .

-rw-r--r-- 1 apptest dbatest 3.9K Jul 9 21:21 ebstest_0709.mgr
-rw-r--r-- 1 apptest dbatest 3.9M Jul 18 06:04 ebstest_0703.mgr
-rw-r--r-- 1 apptest dbatest 0 Jul 19 18:49 ebstest_0719.mgr
-rw-r--r-- 1 apptest dbatest 2.7M Jul 31 23:59 ebstest_0721.mgr
-rw-r--r-- 1 apptest dbatest 0 Aug 1 03:33 ebstest_0801.mgr

apptest@ctsst $ df -h .
Filesystem size used avail capacity Mounted on
/dev/vx/dsk/ebstestdg/erpcsf

64G 64G 0K 100% /ebstest/ebscsf


Solution: Remove unwanted files (or) clear .req/.out/.log from $APPLCSF/$APPLLOG and try it now.


The ones that takes ownership of their lives are likely to be more successful.

- GBatiste

Cause: fdudat failed due to ORA-01041: internal error. hostdef extension doesn't exist.

I was in morning shift user  pinged me and he told me that any request which they are sumbitting
it is showing Phase=INACTIVE and Status=No manager and i replied aries let me check the issue.
i checked the Concurrent manager logs the cm is not running and it contain below error message.


CM LOG CONTAIN BELOW ERROR
===========================
Shutting down Internal Concurrent Manager : 29-JUL-2013 08:05:11

Reviver is not enabled, not spawning a reviver process.

List of errors encountered:
.............................................................................
_ 1 _
Routine AFPCMT encountered an ORACLE error. ORA-01041: internal error.
hostdef extension doesn't exist
Review your error messages for the cause of the error. (=)_ 2 _
Routine AFPSMG encountered an ORACLE error. ORA-03114: not connected
to ORACLE
.
Review your error messages for the cause of the error. (=)
_ 3 _
Routine FDPCRQ encountered an ORACLE error. ORA-03113: end-of-file on
communication channel
.
Review your error messages for the cause of the error. (=)
.............................................................................
APP-FND-01564: ORACLE error 1041 in fdudat
APP-FND-01564: ORACLE error 1041 in fdudat

Cause: fdudat failed due to ORA-01041: internal error. hostdef extension doesn't exist.
The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.

List of errors encountered:
.............................................................................
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
.............................................................................
The ebsoltp_0707@ebsoltp internal concurrent manager has terminated with status 1 - giving up.

When i check concurrent manager at OS level i was able to see hardly two or three processes and started
searching in meta link and google it on  google and did not find any information and then i check server logs i found below message in messages log file.

vi /var/adm/mesages

Jul 29 16:50:11 ctssp automountd[7033]: [ID 748625 daemon.error] 3.27.139.50 server not responding: RPC: Timed o
ut
Jul 29 17:40:14 ctssp last message repeated 1 time
Jul 29 17:50:11 ctssp automountd[7033]: [ID 748625 daemon.error] 3.27.139.50 server not responding: RPC: Timed o
ut
Jul 29 18:20:13 ctssp last message repeated 1 time
Jul 29 18:30:17 ctssp automountd[7033]: [ID 748625 daemon.error] 3.27.139.50 server not responding: RPC: Timed o
ut
Jul 29 21:37:00 ctssp last message repeated 1 time


Cause:Issue with the network or server .

Any program accessing a soft mounted resource whose server is not responding may or may not check the return conditions. If it does, it prints an error message in the form
   ... hostname server not responding: RPC: Timed out

Read more information on http://uw714doc.sco.com/en/NET_nfs/nfsT.clearing_servers.html


Solution:
Check the database connectivity and start Concurrent Manager.

tnsping <SID>   ==> i was able to do it.
sqlplus apps/*********@SID from concurrent Manager Tier.

adcmcctl.sh start apps/<***>