Oracle Utilities & Beyond: 2024

Oracle C2M 2.8 Complete Installation on Windows (Part - V) - Final Step

Installing Oracle C2M product:

Download the below from Oracle Software Delivery Cloud: https://edelivery.oracle.com/osdc/faces/SoftwareDelivery

Below are the steps for C2M Application installation:

· Install Oracle Utilities Application Framework V4.4.0.3.0

· Update Keystore

· Install Oracle Utilities Application Framework V4.4.0.3.0 Prerequisite Single Fixes

· Install Oracle Utilities Customer Care and Billing V2.8.0.0.0

· Install Oracle Utilities Customer Care and Billing V2.8.0.0.0 Post-release Patches

· Install Oracle Utilities Meter Data Management V2.4.0.0.0

· Install Oracle Utilities Operational Device Management V2.3.0.0.0

· Install Oracle Utilities Customer To Meter V2.8.0.0.0

· Install Oracle Utilities Customer To Meter V2.8.0.0.0 Post-release Patches

Framework installation:

C:\Users\.....\Downloads\V1006661-01.zip

Copy the file FW-V4.4.0.3.0-MultiPlatform.jar from the delivered package to the

cd C:\temp\V1006661-01

jar -xvf FW-V4.4.0.3.0-MultiPlatform.jar

cd FW-V4.4.0.3.0

run install.cmd

Oracle C2M 2.8 Complete Installation on Windows (Part - III)

Oracle Database 19c Installation:

Download link: https://edelivery.oracle.com/osdc/faces/SoftwareDelivery

After unzipping the file V982656-01.zip in C:\app\product\19.0.0\dbhome_1

Start installing Oracle Database 19c, follow the below steps

Create a Database using Database Config Assistance

Admin Password = CISADM

Click YES

After installation completes, check below services are in Running status:

Create Listener Configuration

Run on SQL Developer:

CREATE TABLESPACE CISTS_01 LOGGING DATAFILE 'C:/c2m/database/C2M/oradata/C2M2800/cists01.dbf' SIZE 1024M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

CREATE ROLE CIS_USER;

CREATE ROLE CIS_READ;

GRANT CREATE SYNONYM to CIS_USER;

GRANT CREATE SYNONYM to CIS_READ;

CREATE USER CISADM IDENTIFIED BY CISADM DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP PROFILE DEFAULT;

GRANT UNLIMITED TABLESPACE TO CISADM WITH ADMIN OPTION;

GRANT SELECT ANY TABLE TO CISADM;

GRANT CREATE DATABASE LINK TO CISADM;

GRANT CONNECT TO CISADM

GRANT RESOURCE TO CISADM;

GRANT DBA TO CISADM WITH ADMIN OPTION;

GRANT CREATE ANY SYNONYM TO CISADM;

GRANT SELECT ANY DICTIONARY TO CISADM;

CREATE USER CISUSER PROFILE DEFAULT IDENTIFIED BY CISUSER DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP;

GRANT SELECT ANY TABLE TO CISUSER;

GRANT CIS_USER TO CISUSER;

GRANT CIS_READ TO CISUSER;

GRANT CONNECT TO CISUSER;

CREATE USER CISOPR PROFILE DEFAULT IDENTIFIED BY OPRPLUS DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP;

GRANT CONNECT, RESOURCE, EXP_FULL_DATABASE TO CISOPR;

CREATE USER CISREAD IDENTIFIED BY CISREAD DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP;

GRANT SELECT ANY TABLE TO CISREAD;

GRANT CIS_READ TO CISREAD;

GRANT CONNECT TO CISREAD;

Now disconnect from Database in SQL Developer.

Run the below commands in SQL Plus:

All the SQL Plus Run and Results:

SQL*Plus: Release 19.0.0.0.0 - Production on Tue Oct 22 16:01:54 2024
Version 19.3.0.0.0

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

Enter user-name: sys as sysdba
Enter password:

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

SQL> SHUTDOWN NORMAL
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP UPGRADE
ORACLE instance started.

Total System Global Area 5083495440 bytes
Fixed Size 9038864 bytes
Variable Size 922746880 bytes
Database Buffers 4143972352 bytes
Redo Buffers 7737344 bytes
Database mounted.
Database opened.
SQL> alter system set max_string_size='EXTENDED';

System altered.

SQL> @C:\app\product\19.0.0\dbhome_1\rdbms\admin\utl32k.sql

Session altered.

Session altered.

DOC>#######################################################################
DOC>#######################################################################
DOC> The following statement will cause an "ORA-01722: invalid number"
DOC> error if the database has not been opened for UPGRADE.
DOC>
DOC> Perform a "SHUTDOWN ABORT" and
DOC> restart using UPGRADE.
DOC>#######################################################################
DOC>#######################################################################
DOC>#

no rows selected

DOC>#######################################################################
DOC>#######################################################################
DOC> The following statement will cause an "ORA-01722: invalid number"
DOC> error if the database does not have compatible >= 12.0.0
DOC>
DOC> Set compatible >= 12.0.0 and retry.
DOC>#######################################################################
DOC>#######################################################################
DOC>#

PL/SQL procedure successfully completed.

Session altered.

0 rows updated.

Commit complete.

System altered.

PL/SQL procedure successfully completed.

Commit complete.

System altered.

Session altered.

Session altered.

Table created.

Table created.

Table created.

Table truncated.

0 rows created.

PL/SQL procedure successfully completed.

STARTTIME
--------------------------------------------------------------------------------
10/22/2024 16:17:08.649000000

PL/SQL procedure successfully completed.

No errors.

PL/SQL procedure successfully completed.

Session altered.

Session altered.

0 rows created.

no rows selected

no rows selected

DOC>#######################################################################
DOC>#######################################################################
DOC> The following statement will cause an "ORA-01722: invalid number"
DOC> error if we encountered an error while modifying a column to
DOC> account for data type length change as a result of enabling or
DOC> disabling 32k types.
DOC>
DOC> Contact Oracle support for assistance.
DOC>#######################################################################
DOC>#######################################################################
DOC>#

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Commit complete.

Package altered.

Package altered.

Session altered.

SQL> SHUTDOWN
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP
ORACLE instance started.

Total System Global Area 5083495440 bytes
Fixed Size 9038864 bytes
Variable Size 922746880 bytes
Database Buffers 4143972352 bytes
Redo Buffers 7737344 bytes
Database mounted.
Database opened.
SQL> @C:\app\product\19.0.0\dbhome_1\rdbms\admin\utlrp.sql

Session altered.

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN 2024-10-22 16:22:45

DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC> objects in the database. Recompilation time is proportional to the
DOC> number of invalid objects in the database, so this command may take
DOC> a long time to execute on a database with a large number of invalid
DOC> objects.
DOC>
DOC> Use the following queries to track recompilation progress:
DOC>
DOC> 1. Query returning the number of invalid objects remaining. This
DOC> number should decrease with time.
DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC> 2. Query returning the number of objects compiled so far. This number
DOC> should increase with time.
DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC> This script automatically chooses serial or parallel recompilation
DOC> based on the number of CPUs available (parameter cpu_count) multiplied
DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC> On RAC, this number is added across all RAC nodes.
DOC>
DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC> recompilation. Jobs are created without instance affinity so that they
DOC> can migrate across RAC nodes. Use the following queries to verify
DOC> whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC> 1. Query showing jobs created by UTL_RECOMP
DOC> SELECT job_name FROM dba_scheduler_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC> 2. Query showing UTL_RECOMP jobs that are running
DOC> SELECT job_name FROM dba_scheduler_running_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#

PL/SQL procedure successfully completed.

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END 2024-10-22 16:22:47

DOC> The following query reports the number of invalid objects.
DOC>
DOC> If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#

OBJECTS WITH ERRORS
-------------------
0

DOC> The following query reports the number of exceptions caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC> Note: Typical compilation errors (due to coding errors) are not
DOC> logged into this table: they go into DBA_ERRORS instead.
DOC>#

ERRORS DURING RECOMPILATION
---------------------------
0

Function created.

PL/SQL procedure successfully completed.

Function dropped.

PL/SQL procedure successfully completed.

Run Commands:

Connect to sqlplus

Connect using sys as sysdba

Shutdown database

SHUTDOWN NORMAL

Start database in upgrade mode

STARTUP UPGRADE

Update value to EXTENDED

alter system set max_string_size='EXTENDED';

Run script

@C:\app\product\19.0.0\dbhome_1\rdbms\admin\utl32k.sql

Restart DB in Normal Mode

SHUTDOWN

STARTUP

Run script @C:\app\product\19.0.0\dbhome_1\rdbms\admin\utlrp.sql

Run SQL on SQL Dev:

SELECT directory_name, directory_path FROM dba_directories where directory_name = 'DATA_PUMP_DIR';

DP Dump Directory: C:\app\admin\c2m2800\dpdump/

Unzip using 7zip and send from

To C:\app\admin\c2m2800\dpdump/

Now, run the following import command:

impdp directory=data_pump_dir dumpfile=exp_demo.dmp logfile=exp_demo.log schemas=CISADM

Creating Synonyms for CISUSER and CISREAD:

Extract the files in V1006660-01

F:\C2M2.8InstallationFile\OracleC2M2.8\V1006660-01\jarfiles

SET CLASSPATH=F:\C2M2.8InstallationFile\OracleC2M2.8\V1006660-01\jarfiles\*

"%JAVA_HOME%"\bin\java -Xmx1500M com.oracle.ouaf.oem.install.OraGenSec -d CISADM,CISADM,jdbc:oracle:thin:@localhost:1521/C2M2800 -u CISUSER,CISREAD -r CIS_USER,CIS_READ -a A -p CISUSER,CISREAD -l output.log

Step 3 is completed.

For step - 4 (next step), follow this link: Native installation on Weblogic

For step - 5, follow this link: Installing Oracle C2M product

Oracle Utilities & Beyond

Saturday, November 9, 2024

Oracle C2M 2.8 Installation on Windows (Part - II)

Downloading C2M product, Oracle DB 19c and WebLogic Server 12

Oracle C2M 2.8 Installation on Windows (Part - V)

Installing Oracle C2M product:

Oracle C2M 2.8 Installation on Windows (Part - IV)

Oracle C2M 2.8 Complete Installation on Windows (Part - IV)

Oracle C2M 2.8 Installation on Windows (Part - III)

Oracle C2M 2.8 Complete Installation on Windows (Part - III)

Oracle C2M 2.8 Installation on Windows (Part - II)