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
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 2024Version 19.3.0.0.0Copyright (c) 1982, 2019, Oracle. All rights reserved.Enter user-name: sys as sysdbaEnter password:Connected to:Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - ProductionVersion 19.3.0.0.0SQL> SHUTDOWN NORMALDatabase closed.Database dismounted.ORACLE instance shut down.SQL> STARTUP UPGRADEORACLE instance started.Total System Global Area 5083495440 bytesFixed Size 9038864 bytesVariable Size 922746880 bytesDatabase Buffers 4143972352 bytesRedo Buffers 7737344 bytesDatabase 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.sqlSession 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" andDOC> restart using UPGRADE.DOC>#######################################################################DOC>#######################################################################DOC>#no rows selectedDOC>#######################################################################DOC>#######################################################################DOC> The following statement will cause an "ORA-01722: invalid number"DOC> error if the database does not have compatible >= 12.0.0DOC>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.649000000PL/SQL procedure successfully completed.No errors.PL/SQL procedure successfully completed.Session altered.Session altered.0 rows created.no rows selectedno rows selectedDOC>#######################################################################DOC>#######################################################################DOC> The following statement will cause an "ORA-01722: invalid number"DOC> error if we encountered an error while modifying a column toDOC> account for data type length change as a result of enabling orDOC> 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> SHUTDOWNDatabase closed.Database dismounted.ORACLE instance shut down.SQL> STARTUPORACLE instance started.Total System Global Area 5083495440 bytesFixed Size 9038864 bytesVariable Size 922746880 bytesDatabase Buffers 4143972352 bytesRedo Buffers 7737344 bytesDatabase mounted.Database opened.SQL> @C:\app\product\19.0.0\dbhome_1\rdbms\admin\utlrp.sqlSession altered.TIMESTAMP--------------------------------------------------------------------------------COMP_TIMESTAMP UTLRP_BGN 2024-10-22 16:22:45DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalidDOC> objects in the database. Recompilation time is proportional to theDOC> number of invalid objects in the database, so this command may takeDOC> a long time to execute on a database with a large number of invalidDOC> objects.DOC>DOC> Use the following queries to track recompilation progress:DOC>DOC> 1. Query returning the number of invalid objects remaining. ThisDOC> 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 numberDOC> should increase with time.DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;DOC>DOC> This script automatically chooses serial or parallel recompilationDOC> based on the number of CPUs available (parameter cpu_count) multipliedDOC> 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 parallelDOC> recompilation. Jobs are created without instance affinity so that theyDOC> can migrate across RAC nodes. Use the following queries to verifyDOC> whether UTL_RECOMP jobs are being created and run correctly:DOC>DOC> 1. Query showing jobs created by UTL_RECOMPDOC> SELECT job_name FROM dba_scheduler_jobsDOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';DOC>DOC> 2. Query showing UTL_RECOMP jobs that are runningDOC> SELECT job_name FROM dba_scheduler_running_jobsDOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';DOC>#PL/SQL procedure successfully completed.TIMESTAMP--------------------------------------------------------------------------------COMP_TIMESTAMP UTLRP_END 2024-10-22 16:22:47DOC> The following query reports the number of invalid objects.DOC>DOC> If the number is higher than expected, please examine the errorDOC> messages reported with each object (using SHOW ERRORS) to see if theyDOC> point to system misconfiguration or resource constraints that must beDOC> fixed before attempting to recompile these objects.DOC>#OBJECTS WITH ERRORS-------------------0DOC> The following query reports the number of exceptions caught duringDOC> recompilation. If this number is non-zero, please query the errorDOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errorsDOC> are due to misconfiguration or resource constraints that must beDOC> fixed before objects can compile successfully.DOC> Note: Typical compilation errors (due to coding errors) are notDOC> logged into this table: they go into DBA_ERRORS instead.DOC>#ERRORS DURING RECOMPILATION---------------------------0Function 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
No comments:
Post a Comment