DB : MEMORY_MAX_TARGET & MEMORY_TARGET are set to 0

When MEMORY_MAX_TARGET & MEMORY_TARGET are set to 0 , database will run on a variation of ASMM or manual.

If MEMORY_TARGET is set to a non-zero value:

If SGA_TARGET and PGA_AGGREGATE_TARGET are set, they will be considered the minimum values for the sizes of SGA and the PGA respectively. MEMORY_TARGET values can range from SGA_TARGET + PGA_AGGREGATE_TARGET to MEMORY_MAX_TARGET.
If SGA_TARGET is set and PGA_AGGREGATE_TARGET is not set, we will still auto-tune both parameters. PGA_AGGREGATE_TARGET will be initialized to a value of MEMORY_TARGET - SGA_TARGET.
If PGA_AGGREGATE_TARGET is set and SGA_TARGET is not set, we will still auto-tune both parameters. SGA_TARGET will be initialized to the minimum non-zero value of MEMORY_TARGET - PGA_AGGREGATE_TARGET and SGA_MAX_SIZE and will auto tune its components.
If neither is set, they will be auto-tuned without any minimum or default values. We will have a policy of distributing the total memory set by MEMORY_TARGET parameter in a fixed ratio to the the SGA and PGA during initialization. The policy is to give 60% to the SGA and 40% to the PGA at startup.

If MEMORY_MAX_TARGET has not been explicitly set, but MEMORY_TARGET has, the instance automatically sets MEMORY_MAX_TARGET to the same value as MEMORY_TARGET. If MEMORY_TARGET has not been explicitly set, but MEMORY_MAX_TARGET has, then MEMORY_TARGET defaults to 0. After instance startup, it then is possible to dynamically change MEMORY_TARGET to a non-zero value, provided that it does not exceed the value of MEMORY_MAX_TARGET.

If MEMORY_TARGET is not set or set to set to 0 explicitly (default value is 0 for 11g):

If SGA_TARGET is set we will only auto-tune the sizes of the components of the SGA. PGA will be autotuned independent of whether it is explicitly set or not. However, the combination of SGA and PGA will not be auto-tuned, i.e. the SGA and PGA will not share memory and resize as with the case of MEMORY_TARGET being set to a non-zero value.
If neither SGA_TARGET nor PGA_AGGREGATE_TARGET is set, we will follow the same policy as we have today; PGA will be auto-tuned and the SGA will not be auto-tuned and parameters for some of the SGA components will have to be set explicitly (for SGA_TARGET).
If only MEMORY_MAX_TARGET is set, MEMORY_TARGET will default to 0 and we will not auto tune the SGA and PGA. It will default to 10gR2 behavior.
If SGA_MAX_SIZE is not user set, it is internally set to MEMORY_MAX_TARGET. 

EBS : Concurrent manager not starting after cloning R12.1

Error:

CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD


Solution:
Step 1:

Stop the Concurrent Manager

Step 2:

SQL> select count(*) from fnd_nodes;

  COUNT(*)
----------
         2

SQL> select unique(node_name) from fnd_concurrent_queues;

NODE_NAME
------------------------------
PROD
DEV

SQL> update fnd_concurrent_queues set node_name='DEV' where node_name='PROD';

43 rows updated.

SQL> commit;

Commit complete.

Step 3:

Start the Concurrent Manager

RMAN : Clear archivelogs from flash_recovery_area

Manually delete the archive log in the flash_recovery_area and run the below commands.

$ rman target /

RMAN> crosscheck archivelog all;

RMAN> delete expired archivelog all;

POSTGRES: Deinstall

[root@slave 9.4]# ./uninstall-postgresql
Do you want to uninstall PostgreSQL and all of its modules? [Y/n]: Y

----------------------------------------------------------------------------
Uninstall Status

 Uninstalling PostgreSQL
 0% ______________ 50% ______________ 100%
 ########################################Warning: The data directory (/Database/Postgres/9.4/data) and service user
account (postgres) have not been removed.
Press [Enter] to continue:
#

Info: Uninstallation completed
Press [Enter] to continue:
Segmentation fault (core dumped)
[root@slave 9.4]#

DB : ORA-01804: failure to initialize timezone information

Error:

[oracle@localhost ~]$ sqlplus / as sysdba
ERROR:
ORA-01804: failure to initialize timezone information


SP2-0152: ORACLE may not be functioning properly

Solution:

[oracle@localhost ~]$ unset ORA_TZFILE

[oracle@localhost ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Thu Sep 28 15:46:48 2017

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

Connected to an idle instance.

SQL>

DB : Oracle 11.2.0.3 Patch number

Patch 10404530: 11.2.0.3.0 PATCH SET FOR ORACLE DATABASE SERVER

EBS : Update Workflow System Administartor to * backend

Issue:

Unable to check the workflow status

Solution:

As APPS user run the below command.

update wf_resources set text='*' where name='WF_ADMIN_ROLE';

commit;

Or

Login as SYSADMIN --> Workflow Administrator --> Administration Workflow --> Administration --> Set Workflow System Administrator to *