![]() Oracle Database Catalog Views 11.1.0.6.0 VALID Oracle Workspace Manager 11.1.0.6.0 VALID Oracle Expression Filter 11.1.0.6.0 VALID Oracle Enterprise Manager 11.1.0.6.0 VALID Oracle Application Express 3.0.1.00.08 VALID Iolnxeng 11.1.0.6.0 select comp_name ,version ,status from dba_registry The command completed select instance_name ,host_name ,version ,status from v$instance Instance “ iolnxeng“, status READY, has 1 handler(s) for this service… (DESCRIPTION= (ADDRESS= (PROTOCOL=ipc )(KEY=EXTPROC1523))) Listener Log File / orcl/oracle/diag/tnslsnr/PUNISHER/listener/alert/log.xml Listener Parameter File / orcl/oracle/product/ 11.0.0/db_2/network/admin/listener. Version TNSLSNR for Linux: Version 11.1.0.6.0 – Production All rights reserved.Ĭonnecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=1523))) Inventory_loc=/ ~ ]$ cat / ~ ]$ lsnrctl status Red Hat Enterprise Linux Server release 5.10 ~ ]$ uname –p –r Pre-requisite checks ~ ]$ cat /etc/redhat-release ![]() So if anything goes wrong while upgradation we can use “SID_restore. Here, I say the safest way because, it takes the backup before starting the upgradation and creates 3 scripts at your backup location 1) startup_SID.sql 2) shutdown_SID.sql and 3) SID_restore. And DBUA is the simplest and safest way to upgrade. As per the Oracle, We can upgrade Oracle 11.1.0.6.0 onwards versions of Oracle 11.2.0.3.0 directly. Out-of-Place Upgrade- Install binaries in new ORACLE_HOME In-place Upgrade – Install binaries in same ORACLE_HOME. There are two methods to upgrade database server: Upgrading Oracle 11.1.0.6.0 to Oracle 11.2.0.3.0 Using DBUA (Database Upgrade Assistant):.Upgrading Oracle 11.1.0.6.0 to Oracle 11.2.0.3.0 Using DBUA (Database Upgrade Assistant).This document, separating into two parts: We installed Linux-el6.5 and Oracle 11.2.0.3.0 on Ironman and tried to clone the database but Oracle 11.2.0.3.0 RMAN is not compatible with RMAN 11.1.0.6.0, So we have upgraded old (Punisher) to Oracle 11.2.0.3.0 first and then clone the database on the new Ironman server. But we used the RMAN utility to clone the database on the new (Ironman) server. We could use data pump utilities to restore the dumps. The old server (Punisher) was running on a single instance ( iolnxeng) database with 367 schemes, tablespaces, users, etc. The actual scenario is : we have one Dev Oracle database server (Punisher) running on Linux-el5.10 and Oracle 11.1.0.6.0 But due to some hardware failure, we have shifted this server on brand new DELL PowerEdge R720 (Ironman). The commands may have changed for Oracle 12c.This blog is tested on DEV Oracle database servers ( and ). Please note the the commands are for Oracle 11g. You will find a list, how to safely remove a user. More information on how these users are connected to featured can be found in Oracle 12c Security-Guide and in the support note “Oracle Created Database Users: Password, Usage and Files References (Doc ID 160861.1)”.įor Oracle 11g there’s a good overview on the website. Oracle Database Packages and Types SYS APPQOSSYS,DBSNMP,DIP,GSMADMIN_INTERNAL,ORACLE_OCM,OUTLN,SYSTEM Oracle XML Database XDB ANONYMOUS,XS$NULL ![]() Spatial MDSYS MDDATA,MDSYS,SPATIAL_CSW_ADMIN_USR,SPATIAL_WFS_ADMIN_USR Oracle Multimedia ORDSYS MDSYS,ORDDATA,ORDPLUGINS,SI_INFORMTN_SCHEMA Oracle Application Express APEX_040200 FLOWS_FILES SQL> select comp_name, schema, other_schemas from dba_registry COMP_NAME SCHEMA OTHER_SCHEMAS The view DBA_REGISTRY provides some information how these users are connected to each other and to which feature they belong: SQL> select username from dba_users where oracle_maintained='Y' order by 1 Next question is: how are these users connected to database features and can the users be dropped – and if yes, how?Īfter installing a database with all options, you’ll get a long list of ORACLE_MAINTAINED users: Some time ago I wrote on ORACLE_MAINTAINED database users in Oracle 12c.
0 Comments
Leave a Reply. |