Changing the Hostname and Gateway in Linux Environment

Add IP to the Linux Machine.

Verify the IP current settings

[root@xxx] $route -n

Add IP to the
[root@xxx] $sudo ifconfig eth0 172.16.74.10 netmask 255.255.255.0

Add Default Gateway
[root@xxx] $sudo route add default gw 172.16.74.1 eth0

Add Hostname
Modify the below file as below.
/etc/sysconfig/network

NETWORKING=yes
HOSTNAME="plain.domainname.com"
GATEWAY="172.16.74.1"
GATEWAYDEV="eth0"
FORWARD_IPV4="yes"

Retest the issue.
Reboot the server

VNCSERVER "Command Not Found" in Solaris 11

root@labsys2:/software# pkg install --accept solaris-desktop
           Packages to install: 322
            Services to change:  12
       Create boot environment:  No
Create backup boot environment: Yes

DOWNLOAD                                PKGS         FILES    XFER (MB)   SPEED
Completed                            322/322   46542/46542  556.9/556.9    0B/s


PHASE                                          ITEMS
Installing new actions                   77190/77190
Updating package state database                 Done
Updating package cache                           0/0
Updating image state                            Done
Creating fast lookup database                working -Dec 27 17:35:40 labsys2 sendmail[22098]: [ID 702911 mail.alert] unable to qualify my own domain name (labsys2) -- using short name
Creating fast lookup database                   Done
Updating package cache                           1/1
You have new mail in /var/mail/root
root@labsys2:/software#
root@labsys2:/software# vncserver

You will require a password to access your desktops.

Password:
Verify:
xauth:  file /root/.Xauthority does not exist

New 'labsys2:1 (root)' desktop is labsys2:1

Creating default startup script /root/.vnc/xstartup
Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/labsys2:1.log

root@labsys2:/software#

Debugging RMAN Utility

rman target xx/xx@xx debug all log=mylog trace=mytrace --with catalog 

execute the backup command of controlfile and crosscheck 

rman target / debug all log=mylog trace=mytrace --without catalog 


execute the backup command of controlfile and crosscheck 

Out Of memory , Not Enough Space Solaris 11

Issue:

SQL> startup nomount pfile='initXXX.ora' ;
ORA-27102: out of memory
SVR4 Error: 12: Not enough space
Additional information: 1671
Additional information: 16106127360
Additional information: 64424509440

The Above error appeared When trying to start Oracle 12c on Solaris 11.3, this is published bug

Bug:20635316 - 12C DATABASE INSTANCE STARTUP FAILS WITH ORA-27102: OUT OF MEMORY

Cause:

Solaris using something called OSM , Optimized Shared memory.

Solution:

To avoid this error as workaround just set the parameter in the pfile and retest the issue.

_use_osm=FALSE

Exception occurred: java.sql.SQLException: ORA-28040: No matching authentication protocol

Issue:

while I was running adcfgclone.pl on appsTier and could not connect my database which was upgraded from 10.2.0.5 to 12.1.0.2 

Workaround:

Add SQLNET.ALLOWED_LOGON_VERSION=8 in sqlnet.ora on the db side. 

Retest the issue.

Found running request 37175313 attached to dead manager process.

Issue:
Internal Concurrent Manager was not starting.

PID not found with ID
An error occured in client-side routine afpsmckp for Service Manager FNDSM.  The routine returned code 1.
Check for preceding errors and as well as the service manager log file for further details."

Found running request 37175313 attached to dead manager process.
 Attempting to restart request.

Found dead process: spid=(11181), cpid=(287127), ORA pid=(49), manager=(0/0)

Workaround Tried:

Tried to run the cmclean.sql but it was hanging while updating the table FND_CONCURRENT_PROCESSES

It was found further that the table was locked for DML Operations, identified the lock using below query.

Run as sys user.

select

   c.owner,

   c.object_name,

   c.object_type,

   b.sid,

   b.serial#,

   b.status,

   b.osuser,

   b.machine

from

   v$locked_object a ,

   v$session b,

   dba_objects c

where

   b.sid = a.session_id

and

   a.object_id = c.object_id;

and a.object_name='FND_CONCURRENT_PROCESSES';

Identified the Sid and Serial# and killed the session,

alter system kill session 'sid, serial#' immediate;

Run the cmclean.sql;

Start the Concurrent Managers.

Workflow emails not working for specific users

Issue: After the migration of the ERP from Solaris 10 to Solaris 11, the workflow notication Mails are sending to few users.

Cause: After the migration it was observed that the notification_preference value was changed to DISABLED.

Solution:

Step 1: Verify the value of the notification_preference in the workflow table wf_local_roles as below for all the users affected.

select notification_preference from the wf_local_roles where user_name in 'AFFECTED USER, ','user2'.......;

If the value is DISABLED proceed to the next step.

Step 2: Update the notification_preference value to MAILHTML using the below package.

exec FND_PREFERENCE.put('affected_user', 'WF', 'MAILTYPE', 'MAILHTML');

Step 3: Restart the Workflow Mailer from the Service Component window.

Note: Do not restart workflow mailer containers.

This should resolve the issue.

Unable to find an Output Post Processor service to post-process request 37175438.

Issue:

When any custom report is executed the report is not generated in PDF instead the output file returns in xml file.

Concurrent Request log reports below erro.

Unable to find an Output Post Processor service to post-process request 37175438.

Cause: AQTABLES contains huge number of records.

AQs tables are used to look for "subscriptions" by FNDSMs. That is, when ICM calls for FNDSM to start, they "subscribe" to this queue to identify its status. The time taken for the process cleanup prior to the internal manager start up with the regular CMs is correlated to the number of processes that were not stopped cleanly. In case of un-clean shutdown, the process to restart will be longer as manager spends extra cycles to perform housekeeping tasksRun the following as SYS:.

Solution:

1. Do a clean Shutdown of the concurrent managers.

2. Ensure no FNDLIBR processes are running.

3. Check the number of records in the table :

SQL> select count(*) from applsys.FND_CP_GSM_OPP_AQTBL;

  COUNT(*)

----------

     85596

4. Run the following as SYS:

SQL> DECLARE

po dbms_aqadm.aq$_purge_options_t;

BEGIN

po.block := FALSE;

DBMS_AQADM.PURGE_QUEUE_TABLE(

queue_table => 'APPLSYS.FND_CP_GSM_OPP_AQTBL',

purge_condition => NULL,

purge_options => po);

END;

/  2    3    4    5    6    7    8    9   10

PL/SQL procedure successfully completed.

SQL> commit;

Commit complete.

5. Re-check again the number of records in the table

SQL> select count(*) from applsys.FND_CP_GSM_OPP_AQTBL;

  COUNT(*)

----------

         0

5. Restart the concurrent managers

"unable to create shared memory segment" occurred in Solaris 11

Issue: While Starting the database "unable to create shared memory segment" occurred in Solaris 11

RMAN> startup mount pfile=initINTP.ora.plug;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 10/04/2017 13:04:47
RMAN-04014: startup failed: ORA-27125: unable to create shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 2640
Additional information: 33554432
Additional information: 8192
RMAN-04017: startup error description: ORA-32006: SEC_CASE_SENSITIVE_LOGON initialization parameter has been deprecated

RMAN> exit

Cause: Memory is not allocated in the OS level for the USER.

Solution:
Verify as root user if the user name is available in the projects file, if the user is not found, add the user with attributes as below.

Run as root user.

#projects -l
#projadd -p 104 -U intpora -G dba,oinstall -K 'project.max-shm-memory=(priv,161061273600,deny)' user.intpora

RMAN> startup mount pfile=initINTP.ora.plug;

Oracle instance started
database mounted

Total System Global Area   10737418240 bytes

Fixed Size                     2925344 bytes
Variable Size               6375349472 bytes
Database Buffers            4328521728 bytes
Redo Buffers                  30621696 bytes

RMAN>

Retest the issue.

PRCR-1079 : Failed to start resource ora.asm

Issue:

PRCR-1079 : Failed to start resource ora.asm
ORA-01017: invalid username/password; logon denied
CRS-5017: The resource action "ora.asm start" encountered the following error:
ORA-01017: invalid username/password; logon denied
. For details refer to "(:CLSN00107:)" in "/ebspgrid/app/12.1.0.2/diag/crs/euxhoerpdbtn/crs/trace/ohasd_oraagent_grid.trc".

CRS-2674: Start of 'ora.asm' on 'euxhoerpdbtn' failed

Cause: The ASM OS Authentication was failing due to the config.o was corrupted under $GRID_HOME/rdbms/lib

Solution:

$ORACLE_HOME/rdbms/lib

$rm config.o

$ make -f ins_rdbms.mk $ORACLE_HOME/rdbms/lib/config.o

$ relink all

NOte: The solutions is applicable while connecting to the oracle database to an idle instance.

Oracle error 922: has been detected in alterpassword2.

Issue while changing the APPS password in R12.1.3

cat L6460833.log
+---------------------------------------------------------------------------+
Application Object Library: Version : 12.1

Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.

FNDCPASS:
+---------------------------------------------------------------------------+

Current system time is 04-OCT-2017 10:43:17

+---------------------------------------------------------------------------+

Working...
APP-FND-02704: Unable to alter user APPS to change password.
Oracle error 922:  has been detected in alterpassword2.

+---------------------------------------------------------------------------+
Concurrent request completed
Current system time is 04-OCT-2017 10:43:45

+------------------------

Cause: Password contains invalid character "$", password can contain only characters _, $, and #. 


Solution:

Remove Special Characters and retry.