RC-20200: Fatal: Could not find Unzip. At this time only Native UnZip 5.X is supported.

RC-20200: Fatal: Could not find Unzip. At this time only Native UnZip 5.X is supported.

While cloning database Tier

Error :
RC-20200: Fatal: Could not find Unzip. At this time only Native UnZip 5.X is supported.

Please make sure you have UnZip 5.X in your path and try again…

 ERROR while running Apply…

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

  Please check logfile.

Solution 1

Which unzip should point to $ORACLE_HOME/bin/unzip

Take the backup of existing unzip from $ORACLE_HOME/bin

cd $ORACLE_HOME/bin

mv unzip unzip_bkp

cp /usr/bin/unzip to $ORACLE_HOME/bin

Make sure the unzip utility under /usr/bin should be of version 5.X and not 6

Solution 2

As root user, rename the default unzip (/usr/bin/unzip) to a temporary filename (e.g. /usr/bin/unzip-ver6), perform the task, and then rename unzip-ver6 to the original name when completed.

# mv /usr/bin/unzip /usr/bin/unzip-ver6

Solution 3

unzip utility
https://oss.oracle.com/el4/unzip/unzip.html


 

While cloning, adcfgclone.pl error:RC-50014: Fatal: Execution of AutoConfig was failed in R12.

While cloning, adcfgclone.pl error:RC-50014: Fatal: Execution of AutoConfig was failed in R12.
When we check the log file we can see the error like below
AutoConfig could not successfully instantiate the following files:


adcrdb.sh INSTE8

AutoConfig is exiting with status 1

RC-50014: Fatal: Execution of AutoConfig was failed


Solution: Copy adcrdb.sh file ($ORACLE_HOME/appsutil/template) from
Source to target ($ORACLE_HOME/appsutil/template) then
we run the adcfgclone.pl dbTier again.

Oracle’s OS Watcher tool (oswbb)

Oracle’s OS Watcher tool (oswbb)

Oracle’s OS Watcher tool (oswbb) runs shell scripts that run the operating system tools (ps, top, ifconfig, mpstat, iostat, netstat, traceroute, vmstat, meminfo (Linux Only), slabinfo (Linux Only)) to collect CPU, Memory, I/O and Network usage and collate the results. OSWatcher Analyzer (oswbba) presents these results graphically.

oswbb and oswbba require installation, however this is relatively simple and there is little overhead.

By default the diagnostics are only retained for 48 hours, but this can be configured.

Note that it is a unix / linux based utility.

OSWatcher (Includes: [Video]) (Document 301137.1)

OS Watcher User's Guide (Document 1531223.1)

OSWatcher Analyzer User Guide (Document 461053.1)

Node ID does not exist for the current application server id.

Node ID  does not exist for the current application server id.

On entering Oracle Applications on the web, the following error appears:

Node ID  does not exist for the current application server id.

Cause:

There is a mismatch between server_id in the  fnd_nodes table and appl_server_id in the dbc file and
hence we are getting this  "node id does not exist" error.

Solution:

Stop application.
Run adgendbc.sh script to configure apps tier dbc file with the correct id from the database instance.
Start the application and retest.

Location of script:
11i: $COMMON_TOP/admin/install/$CONTEXT_NAME
R12: $INST_TOP/admin/install

[appl@test install]$ sh adgendbc.sh

[EXCEPTION] [OPPServiceThread0] java.sql.SQLException: ORA-00600: internal error code, arguments: [kqludp2], [0x9EAFC1B0], [0], [], [], [], [], [] ORA-06512: at "APPS.FND_CP_OPP_IPC", line 85

[EXCEPTION] [OPPServiceThread0] java.sql.SQLException: ORA-00600: internal error code, arguments: [kqludp2], [0x9EAFC1B0], [0], [], [], [], [], []
ORA-06512: at "APPS.FND_CP_OPP_IPC", line 85

OPP LOG

[EXCEPTION] [OPPServiceThread0] java.sql.SQLException: ORA-00600: internal error code, arguments: [kqludp2], [0x9EAFC1B0], [0], [], [], [], [], []
ORA-06512: at "APPS.FND_CP_OPP_IPC", line 85
ORA-06512: at line 1

at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:589)

SOLUTION

1. Shut down all services
Verify NO CP processes are running on OS. This includes FNDLIBR, FNDSM, etc.

IMPORTANT: BE SURE TO RUN THESE SCRIPTS AS THE CORRECT USERS SYSTEM and APPLSYS ONLY.

2. Run $FND_TOP/patch/115/sql/afopp001.sql as SYSTEM.

3. Run $FND_TOP/patch/115/sql/afopp002.sql as APPLSYS.  Commit.

4. Restart managers and test again.

DB link Cross platform

DB link Cross platform

Important information user have to provide:
-----------------------------------------------------------------------------------------------------------------------------------
1. Source Server Name.
2. Source DB-Name.
3. Source DB-Link Owner schema name.
4. DB-Link name
5. Target Server name.
6. Target Port number.
7. Target DB-Name.
8. Target Username/password.

Example

-----------------------------------------------------------------------------------------------------------------------------------
1. Source Server Name            -    ora1.svr.us.abc.net
2. Source DB-Name.            -    ABCD
3. Source DB-Link Owner schema name.    -    PUBLIC
4. DB-Link name                -    GLOBAL_MX_DTCC_2
5. Target Server name.            -    TARGET.uk.ABC.com
6. Target Port number.            -    1551
7. Target DB-Name.            -    GLOBAL_MX_DTCC_PHASE2
8. Target Username/password.        -    GLOBAL_MX_DTCC2_USER/"Password".


DB-Link Creation Process:

1. Create pfile as << initdg4DATABASENAME.ora >> under directory location << $ORACLE_HOME/dg4msql/admin >>:
EXAMPLE:
-------------------------
XXXXXXXX: /export/NRD/oracle/product/11.1.0/db_1/dg4msql/admin>
-rw-r--r-- 1 oracle dba   397 Aug 20 09:26 initdg4GLOBAL_MX_DTCC_PHASE2.ora

$ cat initdg4GLOBAL_MX_DTCC_PHASE2.ora
------------------------------------------------------------------------------------------------------------------------------------
# This is a customized agent init file that contains the HS parameters
# that are needed for the Database Gateway for Microsoft SQL Server

#
# HS init parameters
#
HS_FDS_CONNECT_INFO=TARGET.uk.ABC.com:1433
# alternate connect format is hostname/serverinstance/databasename
HS_FDS_TRACE_LEVEL=OFF
HS_FDS_RECOVERY_ACCOUNT=RECOVER
HS_FDS_RECOVERY_PWD=RECOVER


2. Update tnsnames.ora under $ORACLE_HOME?network/admin with ADDRESS/CONNECT_DATA as mentioned below in example:

Tnsnames.ora entry example:
--------------------------------------------------------------------------------------------
dg4DATABASE-Name =
    (DESCRIPTION=
        (ADDRESS=(PROTOCOL=tcp)(HOST= ora1.svr.us.abc.net)(PORT=1551))
        (CONNECT_DATA=(SID=dg4GLOBAL_MX_DTCC_PHASE2))
        (HS=OK)
     )


3. create cross platform DB-Link using below command on sqlplus:

DDL for Cross platform DB-Link:
---------------------------------------------------------------------------------------------
CREATE PUBLIC DATABASE LINK "GLOBAL_MX_DTCC_2" CONNECT TO "GLOBAL_MX_DTCC2_USER" IDENTIFIED BY password USING '(DESCRIPTION= (ADDRESS=PROTOCOL=tcp)(HOST= ora1.svr.us.abc.net)(PORT=1551)) (CONNECT_DATA=(SID=dg4GLOBAL_MX_DTCC_PHASE2)) (HS=OK))';


4. Restart listener associated with Database in which this DB link is created Note: restarting listener is the requirement for creating crossplatform listener.


5. Check status of restarted listener it should show entry like below:
--------------------------------------------------------------------------------------------------
Service "dg4GLOBAL_MX_DTCC_PHASE2" has 1 instance(s).
  Instance "dg4GLOBAL_MX_DTCC_PHASE2", status UNKNOWN, has 1 handler(s) for this service...


6. check if the DB-Link is working fine, using below on sqlplus:
---------------------------------------------------------------------------------------------------
SQL> select sysdate from dual@GLOBAL_MX_DTCC_2;

SYSDATE
---------
20-Aug-15

Explain plan for an Old Query

Explain plan for an Old Query

set pages 9999 lines 300
select SESSION_ID,SESSION_SERIAL#,SQL_ID,SQL_PLAN_HASH_VALUE from DBA_HIST_ACTIVE_SESS_HISTORY where SESSION_ID=<session_id> and SESSION_SERIAL#=<session_serial>;

SELECT * FROM TABLE(dbms_xplan.display_awr('&SQL_ID'));

SELECT * FROM TABLE(dbms_xplan.display_awr('&SQL_ID','&plan_hash_value'));

select * from table(dbms_xplan.display_awr('&sql_id',null,null,'advanced +peeked_binds'));

SELECT * FROM TABLE(dbms_xplan.display_cursor('&SQL_ID'));

SELECT * FROM TABLE(dbms_xplan.display_cursor('&SQL_ID', '&child_number'));

R12: Error "Java Exception in Thread 'Main' java.lang.OutOfMemoryError: Java Heap Space

R12: Error "Java Exception in Thread 'Main' java.lang.OutOfMemoryError: Java Heap Space

Increase the amount of memory available as follows:

a. Login to the instance as system administrator
b. Go to Concurrent -> Program -> Define
c. Search for the following concurrent program
d. In the 'Executable' group, there is a field named 'Options'.
Enter the value '-ms2048m -mx2048m' as the value for this field.
This will set the heap space min and max size to 2GB.
Bounce the concurrent managers.

e. Save the change and retest the issue.