https://blogs.oracle.com/database/post/getting-started-on-odsa-with-exadata-database-service?source=:so:ch:or:awr::::Cloud&SC=:so:ch:or:awr::::Cloud&pcode=
Sunday, 27 November 2022
Monday, 7 November 2022
SSH setup command
ssh-keygen -t rsa -b 2048
Generating public/private rsa key pair.
Enter file in which to save the key (/home/applprod/.ssh/id_rsa):
Created directory '/home/applprod/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/applprod/.ssh/id_rsa.
Your public key has been saved in /home/applprod/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:RLHzdreCS+aIzLM1WYr3GacsLpauHLTHTRTJcwdbOmQ applprod@opcprdapp01
The key's randomart image is:
+---[RSA 2048]----+
| .+oE.. |
| .+=.+. |
| =o+. |
| o o . |
| . S + . . |
| . o + = o . . |
| o +.B = o . |
| . ==+.O * . |
| o+*=o.B |
+----[SHA256]-----+
Thursday, 8 September 2022
Oracle Data Pump – Export Import ( Expdp Impdp ) Tutorial with Examples
https://ittutorial.org/category/oracle/datapump/
https://ittutorial.org/oracle-data-pump-export-import-expdp-impdp-tutorial-with-examples-3/
Monday, 22 August 2022
Cloud Premigration Advisor Tool (CPAT)
Cloud Premigration Advisor Tool (CPAT) Analyzes Databases for Suitability of Cloud Migration (Doc ID 2758371.1)
Sunday, 21 August 2022
19c DB clone DBTechSTack - error - Exception String: Error in invoking target 'libasmclntsh19.ohso libasmperl19.ohso client_sharedlib' of makefile
Issue during ApplyTechStack in db tier during clone - While runnning DBTechSTack
Error in inventory log
make: *** [/vijapp/VIJ4/oracle/product/19c/rdbms/lib/ins_rdbms.mk:56: client_sharedlib] Error 1
Exception String: Error in invoking target 'libasmclntsh19.ohso libasmperl19.ohso client_sharedlib' of makefile '/vijapp/VIJ4/oracle/product/19c/rdbms/lib/ins_rdbms.mk'. See '/vijapp/VIJ4/oraInventory/logs/InstallActions2021-05-24_02-29-33AM/installActions2021-05-24_02-29-33AM.log' for details.
1) Below verified and was correct
rpm -q --whatprovides /usr/lib64/crti.o
glibc-devel-2.28-189.1.el8.x86_64
rpm -q --whatprovides /usr/lib64/libpthread_nonshared.a
glibc-devel-2.28-189.1.el8.x86_64
2) Check in make.log
running genclntsh...
genclntsh: genclntsh: Could not locate /vijapp/VIJ4/oracle/product/19c/network/admin/shrept.lst
Failed to generate client shared library on
Solutiton ;
/vijapp/VIJ4/oracle/product/19c/network/admin/shrept.lst file did not exist , restored from backcup or from source and issue is resolved.
---------------------------------------Other references-----
19c Database Installation fails with :"Error in invoking target 'libasmclntsh19.ohso libasmperl19.ohso client_sharedlib' of makefile ins_rdbms.mk " (Doc ID 2760289.1)
E-Business Suite Applications Manager RapidClone Attempts Fail With Error 'RC-00110 Fatal: Error occurred while relinking of ApplyDBTechStack' Running adlnkoh.sh ( Doc ID 330469.1 )
Findings: In this case the problem is a missing file from "$ORACLE_HOME/rdbms/admin/shrept.lst", this file is used by the "genclntsh", a shell script that builds the shared libraries. The "genclntsh" requires "shrept.lst" so when it is missing that will cause adlnkoh.sh to fail, which in turn causes the clone to fail.
Rapid Clone for 19c DB Tier Failed by RC-50013 in ApplyDBTechStack_<MMDDYYMI>.log and "make: *** [/u10/EBS12/XXX/db/tech_st/19.0.0/rdbms/lib/drdactl] Error 1" in installActionsYYYY-MM-DD_HH-MI-SSPM.log ( Doc ID 2729752.1 )
Findings: $ORACLE_HOME(19c)/network/admin/shrept.lst was not perfect.
--other queries
SQL> select * from v$version where banner like 'Oracle Database%';
SQL> select INSTANCE_NUMBER ,INSTANCE_NAME ,DATABASE_TYPE from v$instance;
SQL> select release_name from apps.fnd_product_groups;
SQL> select abbreviation, codelevel FROM AD_TRACKABLE_ENTITIES WHERE abbreviation in ('txk','ad','atg_pf','fwk');
SQL> select platform_name from v$database;
SQL> select * from v$version where banner like 'Oracle Database%';
BANNER
--------------------------------------------------------------------------------
BANNER_FULL
-----------------------------------------------------------------------------------------------------------------------------BANNER_LEGACY CON_ID
-------------------------------------------------------------------------------- ----------
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.13.0.0.0
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production 0
SQL> select INSTANCE_NUMBER ,INSTANCE_NAME ,DATABASE_TYPE from v$instance;
INSTANCE_NUMBER INSTANCE_NAME DATABASE_TYPE
--------------- ---------------- ---------------
1 CVIJ41 RAC
SQL> select platform_name from v$database;
PLATFORM_NAME
-----------------------------------------------------------------------------------------------------
Linux x86 64-bit
12c to 19c RAC Upgrade with EBS R12.2 - Linux
EBS R12.2 supports single pluggable database (PDB) under CDB architecture.
Requirements for Installing Oracle Database/Client 19c on OL8 or RHEL8 64-bit (x86-64) (Doc ID 2668780.1)
-Download the Oracle Database 19c software from OTN -
https://www.oracle.com/database/technologies/oracle19c-linux-downloads.html
Below steps mentions 12c 12102 to 19c (19.13) RAC Upgrade latest steps - OEL8
Step 1 )
Setup ssh password less between RAC nodes node1 and node2
Step 2)
export ORACLE_BASE=/oraapp/VIJ/oracle/product/
export ORACLE_HOME=/oraapp/VIJ/oracle/product/19c
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$ORACLE_HOME/OPatch:$PATH
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
export PERL5LIB=/oraapp/VIJ/oracle/product/19c/perl/bin/perl5.28.1:/oraapp/VIJ/oracle/product/19c/perl/lib/site_perl/5.28.1
export CV_ASSUME_DISTID=OL7
[oracle@vijidb01 ~]$ cd $ORACLE_HOME
[oracle@vijidb01 19c]$ pwd
/oraapp/VIJ/oracle/product/19c
--runInstaller and install CDB without PDB
Oracle Data Guard per Pluggable Database is available today! - July 19, 2022
https://blogs.oracle.com/maa/post/dgpdb-available-today
DGPDB is available in 21c today, with the July 2022 release update (21.7).
Tuesday, 16 August 2022
Backup Based RMAN DUPLICATE Without Connecting To Target Database For Both Disk & Tape Backups
Perform Backup Based RMAN DUPLICATE Without Connecting To Target Database For Both Disk & Tape Backups (Doc ID 1375864.1)
Monday, 15 August 2022
OCI Network Firewall - Palo Alto VM Series - Transit Routing Using DRG2
https://docs.oracle.com/en/solutions/oci-network-firewall/#GUID-875E911C-8D7D-4205-952B-5E8FAAD6C6D3
https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/transitrouting.htm
Friday, 12 August 2022
Migrating 12102 to 19c - exacs
Migrating Oracle E-Business Suite Release 12.2 with Oracle Database 12.1.0.2 to Oracle Exadata Cloud@Customer Gen 2 (Doc ID 2758998.1)
Tuesday, 12 April 2022
Cloning Oracle E-Business Suite Release 12.2 with Multitenant Database using Rapid Clone (Doc ID 2552208.1)
Cloning Oracle E-Business Suite Release 12.2 with Multitenant Database using Rapid Clone (Doc ID 2552208.1)
Using Oracle 19c RAC Multitenant (Single PDB) with Oracle E-Business Suite Release 12.2 (Doc ID 2530665.1)
Business Continuity for Oracle E-Business Release 12.1 Using Oracle 11g Release 2 Physical Standby Database (Doc ID 1070033.1)
Example Manual Migration of Oracle E-Business Suite Release 12.2 with Oracle Database 19c to VM DB Systems and Compute Cloud Service in Oracle Cloud Infrastructure (Doc ID 2743151.1)
Monday, 4 April 2022
Manual Migration 12.2 with 19c on VM DB System OCI
Example Manual Migration of Oracle E-Business Suite Release 12.2 with Oracle Database 19c to VM DB Systems and Compute Cloud Service in Oracle Cloud Infrastructure (Doc ID 2743151.1)
Tuesday, 22 February 2022
tar -cvzf - apps tier
cd /apps/PROD
ls
applcsf EBSapps.env fs1 fs2 fs_ne nohup.out pairsfile webgate11g
Mention full directory where you wanted to take the backup in screen or tmux.
nohup tar -czvf /bkp/appstier.tar.gz *
nohup: ignoring input and appending output to 'nohup.out'
cd /u01/app/oracle/product/19.0.0.0
nohup tar -cvzf /stage/vijp/tar/DB_OH_clone_vijp_1Jan23.tar.gz dbhome_1 &
xzvf
cd /data/vij/product/19.0.0.0
nohup tar -xzvf /stage/vijp/tar/DB_OH_clone_vijp_1Jan23.tar.gz dbhome_1 &
cd /prdapps/vijp/apps/fs1
nohup tar -cvzf /stage/CLONE/1Jan23/vijp_EBSapps_run_1Jan23.tar.gz EBSapps &
--on target
/sitapps/REISIT/apps/fs1
$ nohup tar
-xzvf //stage/CLONE/1Jan23/vijp_EBSapps_run_1Jan23.tar.gz EBSapps &
$ jobs
[1]+ Running nohup tar -xzvf
Sunday, 20 February 2022
EBS - R12.2 install_group_num should be always 1
-----------At this point it updates install_group_num to 0 (Zeor
select oracle_username, install_group_num from APPS.fnd_oracle_userid
where read_only_flag='U';
If it is 0 , update below.
update fnd_oracle_userid
set install_group_num = 1
where install_group_num = '0'
and read_only_flag = 'U';
--------------
Friday, 28 January 2022
EBS R12.2 - concurrent manager not coming up -Could not initialize the Service Manager FNDSM_app01_VIJ1
Issue : In the $APPLCSF/log/
Unable to contact Applications TNS Listener for FNDSM_NODEAPP01_VIJ4 on $NODE.
Cause - Missing entry of FNDSM_NODEAPP01 in FND_CONCURRENT_QUEUES
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';
It should show some thing like - NODEAPP01 is the hostname of the application server.
FNDSM_NODEAPP01
Solution :
1)
Run below script as apps user from application node.
$FND_TOP/patch/115/sql/afdcm037.sql
And verify
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';
2)
If its not updating afdcm037.sql or giving error , restore table FND_CONCURRENT_QUEUES from backup
-take backup of existing table
create table applsys.FND_CONCURRENT_QUEUES_BKP as select * from applsys.fnd_concurrent_queues;
truncate table applsys.fnd_concurrent_queues;
select count(1) from applsys.fnd_concurrent_queues;
insert into applsys.fnd_concurrent_queues select * from applsys.fnd_concurrent_queues_oldbkbp_table;
--Verify
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';
It should return - FNDSM_NODEAPP01
--Start the concurrent manager.......
---------------------Enjoy----
Exact Error in .mgr file while starting concurrent manager using adcmctl.sh
----------------------------
-------Error-------
Process monitor session ended : 27-JAN-2022 09:09:36
27-JAN-2022 09:10:06
Request : 86188175
Priority : 0
Program : 0/5
State : Q
Process monitor session started : 27-JAN-2022 09:10:06
Unable to contact Applications TNS Listener for FNDSM_NODEAPP01_VIJ4 on $NODE. The Listener may be down or the TNS address is not properly configured for this name. (NODE=NODEAPP01)
An error occured in client-side routine afpsmccs for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 144.
Check for preceding errors and as well as the service manager log file for further details."
AFPPSPL-- 27-JAN-2022 09:10:06
Call to PingProcess failed for FNDOPP
AFPPSPL-- 27-JAN-2022 09:10:06
Node:(NODEAPP01), Service Manager:(FNDSM_NODEAPP01_VIJ4) currently unreachable by TNS
Unable to contact Applications TNS Listener for FNDSM_NODEAPP01_VIJ4 on $NODE. The Listener may be down or the TNS address is not properly configured for this name. (NODE=NODEAPP01)
An error occured in client-side routine afpsmccs for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 144.
Check for preceding errors and as well as the service manager log file for further details."
AFPPSPL-- 27-JAN-2022 09:10:06
Call to PingProcess failed for FNDOPP
AFPPSPL-- 27-JAN-2022 09:10:06
Node:(NODEAPP01), Service Manager:(FNDSM_NODEAPP01_VIJ4) currently unreachable by TNS
Unable to contact Applications TNS Listener for FNDSM_NODEAPP01_VIJ4 on $NODE. The Listener may be down or the TNS address is not properly configured for this name. (NODE=NODEAPP01)
..................
An error occured in client-side routine afpsmccs for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 144.
Check for preceding errors and as well as the service manager log file for further details."
AFPPSPL-- 27-JAN-2022 09:12:07
Call to PingProcess failed for FNDOPP
Process monitor session ended : 27-JAN-2022 09:12:07
========================================================================
Starting VIJ4_0127@VIJ4 Internal Concurrent Manager -- shell process ID 3458568
logfile=/mount/CVIJ4/fs_ne/inst/VIJ4_NODEAPP01/logs/appl/conc/log/VIJ4_0127.mgr
PRINTER=noprint
mailto=applmgr
restart=N
diag=N
sleep=30
pmon=4
quesiz=1
Reviver is ENABLED
+---------------------------------------------------------------------------+
Application Object Library: Concurrent Processing version 12.2
Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
Internal Concurrent Manager started : 27-JAN-2022 09:13:55
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
27-JAN-2022 09:13:55 - Checking ICM sleep
27-JAN-2022 09:13:55
Unsuccessful in TNS ping of node AZVMEBSDEVAPP02, error reported: Listener Not Found.
Could not contact Service Manager FNDSM_AZVMEBSDEVAPP02_VIJ4. The TNS alias could not be located, the listener process on AZVMEBSDEVAPP02 could not be contacted, or the listener failed to spawn the Service Manager process.
Process monitor session started : 27-JAN-2022 09:13:55
Starting PODAMGR Concurrent Manager : 27-JAN-2022 09:13:55
Could not initialize the Service Manager FNDSM_NODEAPP01_VIJ4. Verify that NODEAPP01 has been registered for concurrent processing.
An error occured in client-side routine afpsmcsm for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 126.
Check for preceding errors and as well as the service manager log file for further details."
Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library /mount/CVIJ4/fs1/EBSapps/appl/po/12.0.0/bin/POXCON.
Check that your system has enough resources to start a concurrent manager process. Contact your system admin : 27-JAN-2022 09:13:55
Starting RCVOLTM Concurrent Manager : 27-JAN-2022 09:13:55
Could not initialize the Service Manager FNDSM_NODEAPP01_VIJ4. Verify that NODEAPP01 has been registered for concurrent processing.
An error occured in client-side routine afpsmcsm for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 126.
Check for preceding errors and as well as the service manager log file for further details."
Routine AFPEIM encountered an error while starting concurrent manager RCVOLTM with library /mount/CVIJ4/fs1/EBSapps/appl/po/12.0.0/bin/RCVOLTM.
Check that your system has enough resources to start a concurrent manager process. Contact your system admi : 27-JAN-2022 09:13:56
Starting INVTMRPM Concurrent Manager : 27-JAN-2022 09:13:56
Could not initialize the Service Manager FNDSM_NODEAPP01_VIJ4. Verify that NODEAPP01 has been registered for concurrent processing.
An error occured in client-side routine afpsmcsm for Service Manager FNDSM_NODEAPP01_VIJ4. The routine returned code 126.
------------------------
Friday, 14 January 2022
-
Issue : In the $APPLCSF/log/ Unable to contact Applications TNS Listener for FNDSM_NODEAPP01_VIJ4 on $NODE. Cause - Missing entry of FNDSM...
-
19c Refreshable Clone - Alternate to Data Guard and High Availability Solution for Oracle Standard Edition Use Cases 1) Only HA solution for...
-
Issue ERROR: ORA-44787: Service cannot be switched into. Sol: QL> show con_name CON_NAME ------------------------------ CDB$ROOT SQL...