Skip to content

Container database creation in 19c

You need to download oracle 19c software and setup software installation. After installation, you can able to create a container database with have a pdb.

C:\Users\mazar>set ORACLE_SID=oradb

C:\Users\mazar>sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 – Production on Sun Nov 1 15:55:13 2020
Version 19.3.0.0.0

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

Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.3.0.0.0

SQL> SELECT NAME, CDB, CON_ID FROM V$DATABASE;

NAME CDB CON_ID


ORADB YES 0

SQL> select pdb_name from dba_pdbs;

PDB_NAME

ORAPDB
PDB$SEED

Apex upgrade during database upgrade

While doing upgrade from oracle database 12.2 to 19c, we need to do the upgrade apex as per preupgrade recommendation

Upgrade Oracle Application Express (APEX) manually before the database
upgrade.

  The database contains APEX version 5.0.4.00.12. Upgrade APEX to at least
  version 18.2.0.00.12.

  Starting with Oracle Database Release 18, APEX is not upgraded
  automatically as part of the database upgrade. Refer to My Oracle Support
  Note 1088970.1 for information about APEX installation and upgrades.

Solution :

Download apex

https://www.oracle.com/tools/downloads/apex-downloads.html

you can able to download older apex too.

Unzip apex software

move older apex version directory to somewhere and copy the apex to oracle 12c home path.

From command prompt, go to apex directory location and then execute the following command from sql as sysdba

before that , you need to know

There are two types of APEX installations: development and runtime only. To determine which type is currently installed, run the following query:

select count(*) from <SCHEMA>.WWV_FLOWS where id = 4000;

<SCHEMA> — curent APEX schema Example APEX_5000

If the query returns 0, it is a runtime only installation, and apxrtins.sql should be used for the upgrade. If the query returns 1, this is a development install and apexins.sql should be used.

As administrator command prompt

@apexins.sql SYSAUX SYSAUX TEMP /i/

It will take sometime to upgrade

can’t spawn cmd.exe no such file or directory Database upgrade to 19c

When i am trying to upgrade database from 12.2.0.1.0 to 19.3.0.0.0 using dbua which is running on window server 2016. I am facing the below issue during upgrade.

the database upgrade component failed during 28% of the upgrade process. So i looked the upgrade log file, the below errors occured

Can’t spawn “cmd.exe”: No such file or directory at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 11024.

DERIVED ORACLE HOME catctl = [E:\app\WINDOWS.X64_193000_db_home]
Can’t spawn “cmd.exe”: No such file or directory at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 11024.
Can’t spawn “cmd.exe”: No such file or directory at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 11024.
catctlGetOraBaseLogDir = [C:\Users\mazar\AppData\Local\Temp\5]

Analyzing file E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catupgrd.sql

Log file directory = [E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\SIEBUATDB]

catcon::set_log_file_base_path: ALL catcon-related output will be written to [E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\SIEBUATDB\catupgrd3R_catcon_26224.lst]

catcon::set_log_file_base_path: catcon: See [E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\SIEBUATDB\catupgrd3R*.log] files for output generated by scripts

catcon::set_log_file_base_path: catcon: See [E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\SIEBUATDB\catupgrd3R_*.lst] files for spool files, if any

Unexpected error encountered in catctlMain; Error Stack Below; exiting
open2: IO::Pipe: Can’t spawn-NOWAIT: No such file or directory at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin/catcon.pm line 1137.
at E:/app/WINDOWS.X64_193000_db_home/perl/lib/IPC/Open3.pm line 336, line 1.
eval {…} called at E:/app/WINDOWS.X64_193000_db_home/perl/lib/IPC/Open3.pm line 335
IPC::Open3::_open3(“open2”, GLOB(0x171befc2c88), GLOB(0x171befc2c70), “>&STDERR”, “E:\app\WINDOWS.X64_193000_db_home\bin\sqlplus.EXE /nolog”) called at E:/app/WINDOWS.X64_193000_db_home/perl/lib/IPC/Open2.pm line 117
IPC::Open2::open2(GLOB(0x171befc2c70), GLOB(0x171befc2c88), “E:\app\WINDOWS.X64_193000_db_home\bin\sqlplus.EXE /nolog”) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin/catcon.pm line 1137
catcon::exec_DB_script(ARRAY(0x171befc3bc0), “C:A:T:C:O:N”, “\x{a}host sqlplus/nolog -v >”, “E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\S”…, “E:\app\WINDOWS.X64_193000_db_home\bin\sqlplus.EXE”) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin/catcon.pm line 1408
catcon::get_instance_status_and_name(ARRAY(0x171bf4b9e78), “\x{a}host sqlplus/nolog -v >”, “E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\S”…, “E:\app\WINDOWS.X64_193000_db_home\bin\sqlplus.EXE”) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin/catcon.pm line 13012
catcon::catconInit2(HASH(0x171bf91a8f0)) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin/catcon.pm line 12249
catcon::catconInit(“sys”, undef, “E:\app\WINDOWS.X64_193000_db_home\rdbms\admin”, “E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\S”…, “catupgrd3R”, 0, 0, 4, …) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 3696
main::catctlDBLogon(“E:\app\WINDOWS.X64_193000_db_home\rdbms\admin”, “E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\S”…, “catupgrd3R”, 0, 0, 4) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 3774
main::catctlLogon() called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 1414
main::catctlMain() called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 1362
eval {…} called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 1360
at E:/app/WINDOWS.X64_193000_db_home/perl/lib/IPC/Open2.pm line 117, line 1.
IPC::Open2::open2(GLOB(0x171befc2c70), GLOB(0x171befc2c88), “E:\app\WINDOWS.X64_193000_db_home\bin\sqlplus.EXE /nolog”) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin/catcon.pm line 1137
catcon::exec_DB_script(ARRAY(0x171befc3bc0), “C:A:T:C:O:N”, “\x{a}host sqlplus/nolog -v >”, “E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\S”…, “E:\app\WINDOWS.X64_193000_db_home\bin\sqlplus.EXE”) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin/catcon.pm line 1408
catcon::get_instance_status_and_name(ARRAY(0x171bf4b9e78), “\x{a}host sqlplus/nolog -v >”, “E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\S”…, “E:\app\WINDOWS.X64_193000_db_home\bin\sqlplus.EXE”) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin/catcon.pm line 13012
catcon::catconInit2(HASH(0x171bf91a8f0)) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin/catcon.pm line 12249
catcon::catconInit(“sys”, undef, “E:\app\WINDOWS.X64_193000_db_home\rdbms\admin”, “E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\S”…, “catupgrd3R”, 0, 0, 4, …) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 3696
main::catctlDBLogon(“E:\app\WINDOWS.X64_193000_db_home\rdbms\admin”, “E:\app\oracle\cfgtoollogs\dbua\upgrade2020-10-07_04-54-01PM\S”…, “catupgrd3R”, 0, 0, 4) called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 3774
main::catctlLogon() called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 1414
main::catctlMain() called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 1362
eval {…} called at E:\app\WINDOWS.X64_193000_db_home\rdbms\admin\catctl.pl line 1360

Solution :

system32 path variable not set properly. Even If i tried to run as administrator in command prompt from explorer, its not work. usually if we’re open run as administrator from explorer, it will go to C:\Windows\System32> path. but my system, its gone to default path my user.

go to

C:\Windows\System32\cmd as run as administrator, now its working.

Get last 500 lines from a file on windows powershell

Get last 500 lines from a file on windows power shell

Get-Content <File location> -Wait -Tail 500

Oracle E-Business Suite 12.2.10 Now Available

https://blogs.oracle.com/ebstech/oracle-e-business-suite-12210-now-available

 

Upgrade Oracle Application Express (APEX) manually before the database upgrade

While doing upgrade database from 12c to 19c

Upgrade Oracle Application Express (APEX) manually before the database upgrade.

The database contains APEX version 5.0.4.00.12. Upgrade APEX to at least version 18.2.0.00.12.

Starting with Oracle Database Release 18, APEX is not upgraded automatically as part of the database upgrade. Refer to My Oracle Support Note 1088970.1 for information about APEX installation and upgrades.

 

Solution :

Download APEX  18.2

https://www.oracle.com/tools/downloads/apex-v182-archive-downloads.html

 

Install & Upgrade’

move the OLD apex to different location or renam apex to apex_old

Extract the apex and copy to oracle home path.

as administrator

@apexins.sql SYSAUX SYSAUX TEMP /i/

 

Best Practices for Minimizing Oracle E-Business Suite Release 12.2.n Upgrade Downtime

refer

Best Practices for Minimizing Oracle E-Business Suite Release 12.2.n Upgrade Downtime (Doc ID 1581549.1)

Oracle Linux 7.4 harddisk partition

You have two HDD and need to make two partition with separate during installation

 

 

 

 

 

 

 

 

 

 

 

 

REST ISG_SERVICE_EXECUTION_ERROR getting error

When we’re trying to post the data using REST service after we add some parameter in existing package, we’re getting the error while post

 

{
“ISGServiceFault”: {
“Code”: “ISG_SERVICE_EXECUTION_ERROR”,
“Message”: “Error while executing service”,
“Resolution”: “System error, please see service log trace for details”,
“ServiceDetails”: {
“ServiceName”: “XXACE_AP_INV_CMS_SOA_PKG”,
“OperationName”: “xxace_main”,
“InstanceId”: “0”
}
}
}

 

Log in error while deploy REST service

PLS-00306: wrong number or types of arguments in call to ‘HAS_DEFAULT’
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored

 

Solution :

Functional Administrator –> clear cache

restart service

undeploy and deploy the service again

Now we can able to post data

 

EBS 12.2 Only Allow Access to Oracle WebLogic Server Administration Ports from Trusted Hosts

When i am trying to access the weblogic server console from one of client machine, I am getting the below error

 

 

Solution :

 

If you have applied the Critical Patch Update (CPU) released in April 2019, then you can use the context variable s_wls_admin_console_access_nodes to specify the trusted hosts used by administrators that require access to the Oracle WebLogic Server Administration Console and Fusion Middleware Control. Set this context variable to a list of trusted hosts that are allowed to access the consoles using the Oracle WebLogic Server Administration ports.

 

Run file system, we need to add the client ip or hostname lists in context file

<s_wls_admin_console_access_nodes oa_var=”s_wls_admin_console_access_nodes”>10.0.XX.XX</s_wls_admin_console_access_nodes>

run autoconfig

stop and start service

Now we can able to reach the weblogic server console URL

adop phase=fs_clone